Because with the VM everything is ready for compiling so everyone can compile OPL.
On windows is little complicated and still there is no info how to update the sdk on windows(I was only able to compile anything newer than r587 just because yoshi314 uploaded what I needed to update my ps2sdk)
That also makes me wonder...if a VM is uploaded with the PS2SDK already set for compiling OPL,why no one is uploading the windows version of what you need to compile OPL.
You(the one who already have a working windows version of mingw and msys)just have to archive the mingw and msys folder and upload it,that's all.Then the one who is going to use that version,just have to extract the archive in the C:\ drive.
I'm using my minGW and msys that way.You only need need the environment variables paths if you are directly using cmd to compile opl but if you run the msys.bat file in C:\msys\1.0,you don't need any environment variables paths(the ps2sdk search for the needed files by reading the C:\msys\1.0\etc\profile file)
I had r640
I found the bug. In OPL's Display Settings I had switched Video Mode to NTSC--it used to be set to AUTO, but after reading your ChangeLog, I set it to see if that would improve starting OPL quicker--since I thought it is trying to scan what type of Region TV I have and etc.
So, if I leave it set to NTSC, no matter how many times I choose my custom theme (from ETH connection), and save the settings. When I turn OPL back on, it will load the default theme. So Video Mode NTSC = bad!! :)
Question: What does ETH prefix path accomplish?
I am finding this version r641 a bit buggy. Here is what I have encountered so far:
Sometimes my theme don''t load completely (missing icons, background [main_frame], etc)--this happens frequently. I then go to Network and do a reconnect and everything is back to normal. Keep in mind that with r640 -- I was not having this issue before, since I've spent quite some hours working on my recent themes that I released for OPL 9 in another topic.
Another time, I was getting a Network error and I could not connect to my ETH connection. I turned off PS2 and turned off switch in the back.
I tried one time to load ps2rd first and then launch OPL afterward, and I got Network Errors. I then tried again, and just got the default theme, but I was still connected to my network.
I am going to try to delete the elf file and copy it over once again. Perhaps the transfer of the elf to my mc card got corrupted? But then it wouldn't load if it did right? Just guessing?
I will keep on tinkering with it, but if I keep getting these bad issues, I may revert back to r640--which was 99% reliable. I hope others can report also, hopefully together we can figure out what is wrong with it. Hopefully it's only on my side...
My PC is not having any issues with network connection, nor am I running any applications in the background that could make issues with the connection to the PS2.
Yes, there is something definitely wrong with this one. I reverted back to r640 and rebooted like dozen of times, and my custom themes appear normal as they should. As soon as I load r641, lots of issues.
I compared the code between the two, and yep, there are lots of changes between the two (hex code). Plus r640 is [675 KB (691,405 bytes) and r641 is [674 KB (690,881 bytes)] Hopefully you can figure it out.
Try downloading one of my themes, and notice that it doesn't load main_frame.png when you restart OPL several times.
Oh the bug that I encountered with r641 about switching to NTSC mode and it would default back to the original OPL theme is also present in r640 -- at least that is not a new bug, perhaps it's been around, and nobody has noticed it, until now. Bug sniffer is what I am--man, that sounds bad! :)
Simple question...since the thread name is renamed to 0.9 and there is a binary download on the first page,does that mean that this is the official 0.9
PS.You forgot to edit include\usbld.h
it still says 0.8
Jay-Jay the doctorxyz fork(the newest rev)don't have any changes compared to the original r640 that can affect anything about how OPL work(at least the source,I don't know if there are any changed in the binary not included in the source)so maybe you encounter an older bug
In fact compiled (binary) files (i.e. the .ELF ones) made from Bitbucket are the same for these three revisions:
ifcaro's rev640 = doctorxyz's rev641 = doctorxyz's rev642 (0.9)
What I did: I got the rev640 from icaro's repo, created fork* (doctorxyz's repo) from it, then I added updated CHANGELOG and DETAILED_CHANGELOG files, added "hominem.te.esse" in About Dialog box as an active OPL developer (he/she deserves our respect ;-) and made related HG Mercurial commit and tag commands. So, it wasn't much, I just did it!!!
*I don't have write access to the ifcaro's repo.
Then I compiled the binary and release it into the first post of this thread (same approach done previously by the OPL team).
Why I did? Well, I just decided to update the above files and release the binary "as is" an a benefit for PSX-Scene community, since not all members have (or wish to have) skill to compile OPL by themselves, and many time has passed by since 0.8. I thought it was time to release 0.9.
I don't have all the skills needed to evolve OPL in all directions, I have few time to work on code, and much less to answer questions that are far beyond my knowledge limits. I'm just doing my best here, like some of you.
I hope you got my point.