PS2 Open PS2 Loader v1.1.0

[sp193]

this launchelf actually detected my hard disk,but it shows "loading hdd modules" forever

Actually, LaunchELF will always try to load the HDD modules, even on consoles that have no HDD unit installed.
Since it freezes at "Loading HDD Modules" and not "Reading HDD Information", I think we can assume that something changed and now it's getting stuck when it loads (HDPro) ATAD.IRX, HDD.IRX or PFS.IRX.
Since PFS.IRX will not do anything with the HDD on its own, it should be either HDD.IRX or HDPro ATAD.IRX. I think this may also explain why OPL cannot boot, if you usually set the HDD option to "AUTO".

Are you still able to play games with the HDPro HDLoader? If you are unable to use the HDPro HDLoader anymore, then your HDD may be corrupted (a format should resolve this). If you must format the HDD and booting OPL again corrupts the HDD, then perhaps HDPro cannot be used to write data. If that actually happens, then I'll disable the creation of hdd0:+OPL to confirm this later on.

Unfortunately, I have checked through the HDPro ATAD module again and it seems like we now have quite a good copy of the original...

 

[sonic0467]

yes,i can use hdloader to play games

 

[sp193]

yes,i can use hdloader to play games

Okay, then this means that the problem is still with HDPro ATAD.

Here are some things to test. Run them in this order, but stop when you can see your games listed:
1. Removed extra operations for OPL's HDPro probe code: https://www.sendspace.com/file/d9jvoa
2. Only enable LBA for sector I/O: https://www.sendspace.com/file/830n76
3. Always write twice to the ATA registers: https://www.sendspace.com/file/p6cq8d

There is no need to test whether you can boot games because I did not update the in-game code. As long as you can successfully see the games being listed, it should be fine.

I have a feeling that (2) or (3) should help. (3) will probably only make a difference if your HDD is an older disk (i.e. 40GB).
(1) is here again, just in case the two extra steps were causing the HDPro device to become confused.

 

[sonic0467]

Okay, then this means that the problem is still with HDPro ATAD.

Here are some things to test. Run them in this order, but stop when you can see your games listed:
1. Removed extra operations for OPL's HDPro probe code: https://www.sendspace.com/file/d9jvoa
2. Only enable LBA for sector I/O: https://www.sendspace.com/file/830n76
3. Always write twice to the ATA registers: https://www.sendspace.com/file/p6cq8d

There is no need to test whether you can boot games because I did not update the in-game code. As long as you can successfully see the games being listed, it should be fine.

I have a feeling that (2) or (3) should help. (3) will probably only make a difference if your HDD is an older disk (i.e. 40GB).
(1) is here again, just in case the two extra steps were causing the HDPro device to become confused.

i recreated the config file,and it boots up,but still not showing game list (no errors,just a circle keep turning)

 

[sp193]

i recreated the config file,and it boots up,but still not showing game list (no errors,just a circle keep turning)

Did this happen for all three tests? Thank you for making the tests.

Does the HDPro have a HDD activity indicator? If it does, is there any activity while the loading icon (the rotating circle) is active?

 

[sonic0467]

Did this happen for all three tests? Thank you for making the tests.

Does the HDPro have a HDD activity indicator? If it does, is there any activity while the loading icon (the rotating circle) is active?

it all happens on 3 tests.
yes,there is an indicator,and when it's loading,it's a red lamp,but not flashed

 

[kozarovv]

it all happens on 3 tests.
yes,there is an indicator,and when it's loading,it's a red lamp,but not flashed

So is like OPL not accessing HDD after detecting it. My bet is HDD.IRX, as ATAD.IRX is detecting HSS @sp193 I remember that @sonic0467 HDD is 500GB if that help.

@sonic0467 do HDD access led is blinking while HDD is detected (booting OPL)? Maybe is some weird PFS.IRX problem if your ansfer is yes. But need to be mean that modified HD Loader use custom PFS implementation/access way, which I highly doubt.

 

[sonic0467]

So is like OPL not accessing HDD after detecting it. My bet is HDD.IRX, as ATAD.IRX is detecting HSS @sp193 I remember that @sonic0467 HDD is 500GB if that help.

@sonic0467 do HDD access led is blinking while HDD is detected (booting OPL)? Maybe is some weird PFS.IRX problem if your ansfer is yes. But need to be mean that modified HD Loader use custom PFS implementation/access way, which I highly doubt.

it's not blinking.

 

[sp193]

it's not blinking.

I think I found the mistake; it's because I made a typo for the type of the READ SECTORS EXT command. Please try this build.

So is like OPL not accessing HDD after detecting it. My bet is HDD.IRX, as ATAD.IRX is detecting HSS @sp193 I remember that @sonic0467 HDD is 500GB if that help.

Thanks, but it seems to be a problem with the HDPro driver because the other modules work fine when the genuine HDD unit is used.

@sonic0467 do HDD access led is blinking while HDD is detected (booting OPL)? Maybe is some weird PFS.IRX problem if your ansfer is yes. But need to be mean that modified HD Loader use custom PFS implementation/access way, which I highly doubt.

Unfortunately, it does not. But I really wish that it did (even in-game), since partitions without PFS do not totally work properly on the PSX (since the PSX was designed to expect icons within the PFS partition).
The HDLoader filesystem also breaks the APA specification by hardcoding the LBAs of each partition, so defragmenting the HDD with the HDD Utility Disc can break HDLoader games.

 

[sonic0467]

thank you for your support!!it finally loads up my game list!!!!
only one problem to fix:how do i fix the graphics on opl?

 

[sp193]

thank you for your support!!it finally loads up my game list!!!!

Thank you for reporting this issue because I broke it in 2013 and it stayed broken. And would have probably stayed broken if you did not.

I will make a new pull request for OPL soon.

only one problem to fix:how do i fix the graphics on opl?

Are you using a language other than English (i.e. Chinese)? If you are using an external language file, you also need a suitable font file (I.e. if your language file is named lang_TChinese.lng, the font should be font_TChinese.ttf or font_TChinese.otf).

If you need a recommendation for a font (if not given one), the contributor for the Traditional Chinese language suggested the Chinese Google Noto font.

The font file is placed in the OPL folder on memory card, root directory of USB disk or +OPL partition on the HDD unit.

I know that LaunchELF currently cannot support HDPro, but that can be changed.

 

[sonic0467]

Thank you for reporting this issue because I broke it in 2013 and it stayed broken. And would have probably stayed broken if you did not.

I will make a new pull request for OPL soon.



Are you using a language other than English (i.e. Chinese)? If you are using an external language file, you also need a suitable font file (I.e. if your language file is named lang_TChinese.lng, the font should be font_TChinese.ttf or font_TChinese.otf).

If you need a recommendation for a font (if not given one), the contributor for the Traditional Chinese language suggested the Chinese Google Noto font.

The font file is placed in the OPL folder on memory card, root directory of USB disk or +OPL partition on the HDD unit.

I know that LaunchELF currently cannot support HDPro, but that can be changed.

no,i use internal english

 

[sp193]

Okay, I think the issue is caused by recent updates to gsKit, but I have not updated my gsKit revision yet.

I will make a new build later on.

By the way, if I made the effort to improve the design of the HDPro driver, would you be willing to make more tests? Right now, it works fine, but there is a very strange design; all exported functions must call hdpro_io_start and hdpro_io_end, which also means that we cannot extend on the functionality of this driver easily.

However, depending on why the original driver had this weird design, there is no guarantee that this restriction can be lifted. Although I have a good feeling that it can be.

 

[sonic0467]

Okay, I think the issue is caused by recent updates to gsKit, but I have not updated my gsKit revision yet.

I will make a new build later on.

By the way, if I made the effort to improve the design of the HDPro driver, would you be willing to make more tests? Right now, it works fine, but there is a very strange design; all exported functions must call hdpro_io_start and hdpro_io_end, which also means that we cannot extend on the functionality of this driver easily.

However, depending on why the original driver had this weird design, there is no guarantee that this restriction can be lifted. Although I have a good feeling that it can be.

i can do tests even i got my 50006 today(network adapter is still on the way though).

 

[sp193]

While the forums were down, I made some other changes after consulting wisi (the genius who cloned HDPro):

• While probing, added missing check on nsector (bug in original HDPro module).
• While probing, added check on LCYL and HCYL. wisi wrote that it may be a check on whether the ATA device is connected properly (i.e. no shorted lines).
• Replaced all unsupported exports with a function that returns -1, except for the unlock function (HDD can always be unlocked).

So here is a new build for you to test. If there are no problems, then this should be all the tests we will need to make and you can keep this file to use. If you wish to have a special version (i.e. with VMC), please feel free to let me know.

***

As for the "future testing" that I mentioned earlier, I think I might not want to go through with it because it does not seem to have much of a future. I have actually written the code, but I don't know whether it is a good thing.
It may be not very reliable. One access to the BOOT ROM when HDPro is enabled and there can be an error. :|
(HDPro hijacks the BOOT ROM address + data lines)

So even if I allow ata_io_start and ata_io_finish to be exported, other developers must be very careful while using them. Also because I think there is a very low chance of other people issuing commands outside of ATAD. I think that the only person who does that is me, for HDDChecker.

Thank you for volunteering to make the HDPro driver great, however!

i can do tests even i got my 50006 today(network adapter is still on the way though).

Thanks, but the modules for HDPro and the normal network adaptor are different.
Our modules for the normal network adaptor were based on the official SONY modules, so they are quite reliable.

 

[sonic0467]

While the forums were down, I made some other changes after consulting wisi (the genius who cloned HDPro):

• While probing, added missing check on nsector (bug in original HDPro module).
• While probing, added check on LCYL and HCYL. wisi wrote that it may be a check on whether the ATA device is connected properly (i.e. no shorted lines).
• Replaced all unsupported exports with a function that returns -1, except for the unlock function (HDD can always be unlocked).

So here is a new build for you to test. If there are no problems, then this should be all the tests we will need to make and you can keep this file to use. If you wish to have a special version (i.e. with VMC), please feel free to let me know.

***

As for the "future testing" that I mentioned earlier, I think I might not want to go through with it because it does not seem to have much of a future. I have actually written the code, but I don't know whether it is a good thing.
It may be not very reliable. One access to the BOOT ROM when HDPro is enabled and there can be an error. :|
(HDPro hijacks the BOOT ROM address + data lines)

So even if I allow ata_io_start and ata_io_finish to be exported, other developers must be very careful while using them. Also because I think there is a very low chance of other people issuing commands outside of ATAD. I think that the only person who does that is me, for HDDChecker.

Thank you for volunteering to make the HDPro driver great, however!


Thanks, but the modules for HDPro and the normal network adaptor are different.
Our modules for the normal network adaptor were based on the official SONY modules, so they are quite reliable.

error:221:hdd not formatted

 

[sp193]

error:221:hdd not formatted

Please use this file instead. I built the wrong branch.

 

[sonic0467]

Please use this file instead. I built the wrong branch.

everything's fine and no problems.

 

[littlebalup]

@Jay-Jay, @sp193

First of all, thank you very mutch for all your great work on the PS2.

I have an issue launching POPStarter elf's from OPL since Jay-Jay's daily build 1007. Each time it open the system browser instead to start the VCD... Seems it doesn't find the VCD.Works great with DB 1005 and earlier with the same config.
I have everything installed to the internal HDD (I'm not using MC or USB at all) and i'm booting to the HDD using a matrix infinity chip.
So, my VCD's are inside __.POPS partition. POPS.ELF and IOPRP252.IMG inside __COMMON/POPS/.

Another thing, language file and font (french) doesn't work for me (files are inside the HDD, +OPL partition).

 

[sp193]

I have an issue launching POPStarter elf's from OPL since Jay-Jay's daily build 1007. Each time it open the system browser instead to start the VCD... Seems it doesn't find the VCD.Works great with DB 1005 and earlier with the same config.

Are you using a compatible/clone network adaptor? Due to changes in the design of DEV9 and ATAD, some clone/compatible adaptors that are not 100% compatible have stopped being compatible.

Another thing, language file and font (french) doesn't work for me (files are inside the HDD, +OPL partition).

Did you set HDD mode to AUTO?