(Help) How to add Icons to HDLoader/KERMIT Games on PS2 HDD-OSD

So in other words, we should not assume, or we may risk screwing up the user's disk if the partition was actually placed somewhere else.

 

Nope, the MBR apparently has to be inside of __mbr partition... But my point is, they could put the MBR KELF anywhere inside the MBR partition.

 

I know. But my original question was whether we can assume that __mbr is at the start of the disk. 0x2000 is the data area for any APA partition, after the reserved area.

The offset and size fields are relative to the start of the disk.

 

Ohhhh

That's a given so yes you can assume that. It's hard wired. The only partition that is 100% fixed on SONY APA standard is __mbr .......

 

Sorry, That was me.... (Don't kill me....)

Sorry that was me.... I was only trying to help out some people that was trying to get uLELF, ESR and OPL on a PS2 HDD and boot the elf. I only named it "Free HD Boot" so the people that know what "Free McBoot" is, will know that is was more or less set up just like it but on a HDD.

If I upload any more, I'll be happy to name it "Pirate HDDOSD Boot". If you like I'll stop doing it... (I only made two.. 1 that's only HDD-OSD and the 2nd was HDD-OSD and PSBBN 0.32).

P.S. I PM KrHACKen and it seems that I was not the one doing it and I only uploaded to the TheISOZone.com

 

Hi!

I get a strange effect:
When switching on my v7 the system starts the hdd, does his checks and boots the hhd-osd.
The same hdd in a V10 starts the hdd, switch it off and starts the hdd a second time before boot to the hdd-osd.

Any ideas?



Thanks.

 

AFAIK this has something to do with the checks the HDDOSD runs, on my V4 PAL ps2 with unofficial 300GB hdd it starts the disk (while displaying the known BIOS screen), restarts the disk (while displaying a black screen) and then boots into OSDSYS.
i read somewhere (probably here on the forums?) that the newer PS2s run 2 checks, a newer check and if that fails a second older check, hence the second spinup. weird that my V4 does that but your V7 doesnt do it...

but except the longer startup time (which may be annoying) it seems to have no effects

 

http://www.assemblergames.com/forum...on-PS2-HDD-OSD&p=623416&viewfull=1#post623416
My V7 doesn't switch the HDD off during the boot sequence either.

 

Your console has the HDD boot function disabled. Although, unlike on the PSX, it will still boot from the HDD.

There isn't a second check. That was what l_Oliveira said, based on his own observations. But examining the code has proved that it was a matter of configuring the console to fully enable HDD booting.

On the retail Playstation 2s (At least, within the SCPH-30000 to SCPH-39000 series), the HDD booting support being disabled will only result in the HDD powering off after the MBR is loaded. On other consoles like the PSX, rom0:HDDLOAD won't even run.

Mine does (SCPH-39006), and yes: that post is exactly what I was looking for to answer the original question (Thanks!).

Here was what I found out at the end: http://www.assemblergames.com/forum...on-PS2-HDD-OSD&p=623463&viewfull=1#post623463

If we cleared your console's config, I'm quite sure that it'll behave like mine... unless our consoles have different rom0:HDDLOAD modules.

 

Hi!

Okay, i get it. What a horror!

First open the ps2 to swap via ule. Arggh. So i started the sudc3 dvd. Got i rsod as i try to install the us hdd utilities.
The second time i chose the 95216 installation package directly and then it runs until the end, but finally failed !?!...

Then comparing the eprom backups for before and after installation shows me the ata support was enabled.


What made me cry was the offsets at http://ichiba.geocities.jp/ysai187/PS2/OSDConfig.htm.
I tried to compare them with my eprom backups from the v7 and the v10.
Doesn't really fit at all and i noticed i knew this stuff but forget it...


Here's the interesting part from the v10 nvram:

With dev9 bit set it's 03, right? Or "12"?



Rgds.

 

RSOD at utility startup = Bad jumper settings, incompatible DMA mode, damaged HDD, damaged Network Adaptor or one damn crappy clone, unmodified ATA device driver
RSOD at the begining of the installation = Shit happened whilst summing the __mbr : Format your HDD with uLe and try again (SUDC3 ? Press L1+L2+R1+R2 then "More...").
RSOD at x% of the installation = Bad copy, damaged disc / Low capacity HDD, damaged HDD.

Mah NVM :


EDIT : Got ! Fµck yeah !

 

I like the SN of your console ... FACEOFF !

 

Hehehe, congrats!
:congratulatory:

Okay, it was a wrong alart.
I tested with an old hdd (30gb crap), because i have to wait for the lowlevel format of the normally used hdd.
So, the 120gb one works with the us hdd utilities.
:biggrin-new:


Rgds.

PS: My V7 looks like this.
000001A0 53 43 50 48 2D 33 39 30 30 34 20 44 4D 53 34 XX SCPH-39004 DMS4.

 

Not my real one, as such HWID shouldn't pass the DNAS. I gave Zony enough MAC addresses in my vids, won't give my iLinkID. The large PSBBN 0.32 dump that has been leaked out of PSX Planet is stamped with my official HDD ID:nightmare:.

Mwahahah, cool stuff. Is it displayed in the version info menu of OSDSYS ? I've edited this thing, with something like SUCK-D##KS and it was displayed as... "SCPH-30004":concern:. Forgot a sum or something...

 

Okay, it's 15 byte plus checksum. In this case the checksum is 00.
Above is the correct line.
And, yes, the osd shows this model version.
:wink-new:



Greets.

 

Thx.

Couldn't show it in the ver inf screen

Maybe the DMS4 pokes something else...

 

I may be off-topic but under PCSX2 it works

 

It's plain OLD 8 bit checksum. Add ALL values then store the value on the last byte of the string.


Dampro (of lenschanger fame) told me about this in 2005 ... lol

 

Sorry, made a mistake. The Checksum is 93 for the string.
It's too long ago...

 

Oh, indeed. Thank you guys:cool-new:.




Looks like my corruption tool has found the corruption point for changing the dvdplayer.irx load path (BIEXEC-DVDPLAYER) in the MG encrypted dvdplayer.elf 3.04J... Can't wait to verify that.
EDIT : Holy SHIET ! That corruption point affects both mc0 and mc1 paths.
EDIT2 : Located in an unencrypted block for great justice:victorious:
EDIT3 : Got E and A ! OK, time for some PPF...