EDIT: Issue solved. It was my USB Flash Drive. Went to another one and everything works perfectly now. Original Post: Hi everyone. I'm trying to load Open PS2 Loader on my PS2. I was running OPL 0.9.2 VMC on my PS2 using FMCB. I decided to update to the latest version and use OPL 0.9.3 VMC+GSM. I downloaded the files, copied it to a USB flash drive, and tried to run it in both uLaunchELF v4.42e_HDD and FMCB itself. It loads a black screen every time and not OPL. I was told by others to delete the OPL 0.9.2 files on my FMCB memory card. So I deleted the OPL config file and the old OPL ELF and it still wouldn't load off USB. I then decided to go back to 0.9.2 because it worked before and now 0.9.2 won't even load. What am I missing or doing wrong? uLaunchELF and the PS2 freeze when I try copying the OPL files to my memory card or HDD from my USB flash drive.
For starters, I'd try another USB drive. If you can't even simply copy a file from there something's not kosher with it.
I'll try another USB drive. The drive works fine on everything except uLaunchELF. It was originally an 8GB drive but after running it through the Windows 10 Media Creation tool and freezing at 47%, I can only format it to 454MB. Even DISKPART says it's 454MB max. EDIT: Tried another USB Flash Drive and it works fine now. Can't believe I didn't think about using another USB drive. Guess this is what happens when you aren't on a normal sleep schedule....
I've already fixed it. The issue was the USB flash drive I was using. I went to another USB flash drive and everything works now. Thanks for responding though.
Just to let you know, the PS2 homebrew SDK has problems with the USB MASS STORAGE driver and some USB flash drives actually get corrupted when written by a PS2 running homebrew apps. I suggest you format the flash drive you were using when it failed. Funny enough the flash drive you tried which didn't work would work just fine if you perform only reads from it.
That might be actually a compatibility problem with the PlayStation 2 USB OHCI controller. Personally, I observed reading from my Toshiba 16GB disk to have occasionally failed. However, the OP's disk seemed to be having some problem, as it wouldn't even work properly with Windows. I eventually attempted to improve the error-handling code within the USB drivers, so older drivers may be actually less reliable.
