Running things on the PS2 with style ...

interesting. plans for a slim version too, or it's just impossible to perform it?

 

I have plans of testing if it works on a SLIM model that has a real SPEED chip (Network Adapter MAC/ATA interface) built in (SCPH-700xx) by using the PCMCIA OSD update driver "System Driver" ...

Don't keep your hopes up and definitely the built in ROM don't even try to detect if there's a HDD on it...

 

Great work l_oliveira!

 

Impressive, to say the least. Too bad I'm stuck with the sucky slim model

 

Replying this post again, I made a interesting discovery about the slims.

SONY purposely messed up the iLINK MAC ADDRESS (since these units have no iLINK port, they don't need to have a valid MAC ADDRESS stored on the eeprom) that is saved on the eeprom and that prevents the HDD unlock command (the HDD is not really locked to prevent any data access, it's lock is simply used to control the DRM) from working properly.

That command failing causes data corruption, forcing you to re-format the drive. (Hence the drive being detected as unformatted after the error happens)

Same reason why you needed to use a modified version of HD Loader for being able to use HDD on the PS2 SLIM.

I copied the "MAC ADDRESS" of my SLIM with HDD connected for a SCPH-30001 FAT PS2 and it became just as mad as the SLIM when I tried the SONY OSD.

Since it's impossible to modify the PS2 SLIM EEPROM and hacking the OSD boot program to make it compatible isn't very interesting (very few slims can use a real internal HDD) and how the issue happens even with a original SONY HDD I decided that making this stuff work in the SLIMs is not really worth the hassle...

 

The modification needs to be made to homebrew PS2HDD.IRX. The Sony APA driver has to be replaced/patched.

I don't believe that that it causes data corruption - unless you are saying that attempting to access the HDD on such a slimline corrupts the contents of the drive. When the i.Link ID used to secure the drive does not match the console's i.Link ID, the drive cannot be unlocked and will have to be erased.

When retrieving the i.Link ID fails, I think that the Sony driver does what the homebrew driver does - bail out.

Anyway, it makes no sense to use a Sony DRM-protected HDD with the SCPH-70000 series, as it's i.Link hardware is 'incomplete' and every DRM-protected software will have to be patched properly.

The reason why a modified version of HDLoader needed to be used was because the homebrew APA driver (PS2HDD.IRX) bails out when sceCdRI() fails. It won't even bother accessing the drive after that.

 

Well FFXI passes DNAS authentication but dies while installing:



And No, it was not SONY HDD that got corrupted, was the generic one. SONY one works (mostly as you can see above, it failed when the installer for the game tried to create the partition) ...

So HDD on a PS2 SLIM is good for nothing, save HD Loader ...

Edit:

Additionally, this happens on a PS2 SLIM with the HDD OSD loaded:


Apparently SONY changed the mechanisms the built in OSD use to load the PS1 Driver (perhaps due
to the PS1 driver exploit ?) and the DVD Player... And of course the HDD OSD does not have the code
to find them. Yet, PS1 games work just fine...

Oh and this is the first time I ever seen this message:

 

If I'm not mistaken, the software that you tested with have the Sony drivers retained... but the ATAD driver was ATAD-patched.

But what about the functions that invoke the special Sony commands? I don't think that the standard ATAD patch disables those functions lol.

If you are still using the Sony ATAD and APA drivers, maybe I can help you to patch them for proper support on the slimline.

By the way, do NOT substitute the Sony ATAD driver with the homebrew driver.... as the homebrew driver will invoke the retarded ATA SECURITY set password function on standard ATA drives if the Sony software DRM-locks the device. :mad-new:

You know what the Sony DRM functions do. Apparently, the guy who added the code to invoke the standard ATA SECURITY set password function in place of the Sony DRM equivalent didn't know what that was for.... and that is now a hazard.

If your non-Sony drive gets locked by the homebrew ATA driver, good luck trying to get it unlocked.

EDIT: You know... now that this topic was mentioned, I used to wonder whether it would be possible to patch the OSD to support USB devices. Maybe I'll try that as part of a small side-experiment...

And homebrew, probably. But with some fixes to the Sony software, I'm sure that even those consoles with the crappy HDPro kit can do something... although I don't like the design of the HDPro kit as doesn't seem to have DMA support.

This is the USA HDDOSD, isn it?

Well, the DVD player KELF was renamed in slimlines, so perhaps that's why it cannot detect the DVD player?

Sorry, but you've lost me here. What has the photographs you uploaded got to do with the PS1 driver? The only thing I can see is that the HDDOSD cannot launch the DVD player. :concern:

The only change to the PS1DRV module that I remember was that they fixed the buffer overflow vulnerability in it.

When did you get this message? When you inserted a DVD Video disc?

 

Awesome man:excitement:. Been waiting for this since you mentioned it ages ago to me. If you need a beta tester for Oceanic consoles please let me know. Got a console sitting here just itching for HDDOSD. :loyal:

 

This image should have 2 more lines of version information - one mentioning the version number of the PS1 driver, one mentioning the version number of the DVD Software. The fact that they are both missing may mean that the PS2 can't find them.

 

Maybe it's a PS2 vs PStwo filenaming issue :

PS2 = rom0S1VER, rom1VDVERR
Slimline = rom0S1VERR, rom1VDVERR (where R is the territory letter, can be A, C, E, J, M, O, R or U)


DVD Player launch is probably messed up because of the badly named EROM driver (rom1:EROMDRV for fat, rom1:EROMDRVR for slim), no access to the erom + the DVD Player KELF is also impacted (erom0VDELF for fat, erom0VDPLR for slims).

 

This is awesome. I realy need to work this out the follow this "hacking". This is changing its doings to do something different just bacause it better/awesome because you can. Is there a plan to make this public, or hands out to do it our selfs?

 

That is most likely. The HDDOSD was never designed to be installed on nor run on slimline consoles anyway.

I guess that the best way would be to alter the path to the PS1 driver and DVD ROM, based on the boot ROM version.

 

what that here the silence, anybody doesn't interest any more normal work of HDD OSD on PS2 Slim? :smile-new:

 

We're thinking what to do with standard PS2s. I don't think the PS2 slim will be supported, because it cannot boot from the hard drive due to it's ROM having no code for that.