HDDOSD Issues

@ Vash32:

For the HDDOSD to work properly partition names must be PP.ABCD-12345.whatever.anythinggoes (up to 32 characters on the whole line).

Good examples could be:

PP.SLPS-20001.HDL.RIDGERACERV
PP.SLPS-25050.HDL.FFX
PP.SCPS-11001.HDL.IQREMIXPLUS
PP.SCPS-15001.HDL.THESCANDAL

PP.SCUS-97501.HDL.APESCAPE3
PP.SCUS-97113.HDL.ICO
PP.SCUS-97472.HDL.COLOSSUS
PP.SCUS-97203.HDL.WILDARMS3

These names break HDL but why the heck people would want to use HDL nowadays, anyway? By the way do you notice the patterns on the numbers used for the game IDs?

 

Oh I was just adding a lot of games and then was going to rename then all to just the game IDs as it was just making its own names & the only HDLGameInstaller setup the names right easy but I was using them HDD on the PC and it only work on the PS2 or Network right now. (Maybe a local hdd part will be added someday.)
I'm starting a new HDD anyway. So the best way is to have a "PP." something like a game ID then have a "dot" something then a other "dot" something or can it just be like "PP.SLUS-21782B" or does it need the dots in it.

What how the names are setup for JP, US, or the numbers themselves? I think know the pattern but now that you said that.. I'm not sure anymore.

 

Patterns for Japanese title IDs go kind of like this:

20xxx NAMCO (CD)
25xxx Square Co. (DVD)
11xxx SCEI (CD)
15xxx SCEI (DVD)

 

What does naming them like this do anyway? (for HDDOSD) Or is it just the way Sony says to do it?
Like the 16 char. for game names in HDDOSD, as it works over it?


Edit: I was just thinking maybe using child partition will help speed up HDDOSD slow downs.
I'm thinking making a lot of PP. Parent Partition as 128MB then add the game & just rename it to CP. Parent Partition.. but that may not help any?

The hard part is that I'm thinking it will only work if they are added 1st... so then you have to make a list of all the games that will be added & making the 128Mb PP.s before adding the games then rename the partition in uLE.

 

The HDD OSD will store ".HDL." (first item between dots after the PP part) as the title ID. That is what happens. You won't have towers grow on the boot screen.

 

So its the play log or what ever its name is as I don't know anymore. So my setup right now is stopping it from see more then one game being played.
I was thinking it was something bigger then that.. well I'll working on my new setup once I get my 400GB SSD I just got for $60.

P.S. As for using child partitions, both the parent partition & child partition need to have the same ID & boot info & icons?

 

So I tried another image (vash32_48Bit_PS2_HDD_Dump) and the hard drive is working fine. I seriously think that its something small wrong with the new images partition table that WinHIIP doesnt like, but thats a deal breaker for me as I am constantly adding and removing batches of games and network install and disc install are too slow for me. Thanks for the help.

 

@vash32 :
I can confirm the issue that Masamune has reported with your new HDDOSD image.
The image itself works with the PS2, but when using Winhiip for installing games it clashes right after a game installation. Running WinHiip again, need to use scan/repair to restore the partition structure.
That problem doesn't happen if using HDL Dump.

 

Ah, I see. Thanks though.

BTW, I lifted the restriction of the HDDChecker optimize function on HDLoader games. It is still quite experimental though, given the size of its user base (especially when it previously wouldn't optimize disks containing HDLoader games).

Call it whatever it you want, as nobody actually knows its realname.

The ID has to be the same, otherwise it will be considered an orphan.
I don't think that there was a requirement for the icon and other files to be the same though.

 

@vash32
SCEI required (TRC) that child partitions had the exact same patinfo data as their parent. That is because when a child partition is orphaned it is treated as a parent so the user can see it's icon and description at the osd hdd screen. (food for the thought)

If it has no patinfo data, it will show as a purple cube of "corrupted data".

 

The TRC says Required: The title does not write anything to the partition attribute area of the "PC (pfs-child)" partition.

 

Uh lol so it was the complete opposite? I remember reading the TRC and I even tested that stuff. Perhaps I read something different? Both approaches make sense if the intent is:

Child partition has patinfo data - Make sure the user knows what he/she is deleting. OSD shows partition name/icon

Child partition has no patinfo data - Make sure the user can not know what he/she is deleting as it will surely appear as corrupted data.

Perhaps with their final stance about this being "in case of error destroy data and reinstall fresh" I agree with you that not having patinfo data was better.

But we're not SCEI and we prefer to not destroy data. What you think of this?

P.S.: I'll look where I saw what I wrote and try to report back. It's very likely I neglected to read the newer TRC and am basing myself on old, outdated preliminary information.

 

The documentation did say that deleting the application with the system will cause both the parent and all child partitions to be deleted, so I guess that the logic is that leaving a child partition behind is considered an error and the child partition is part of a broken installation.

Perhaps you read the part on the PSX resources? Both the parent and child partitions are to have those resources, although the child partition will have slightly different files.

If there is such a difference, please share.

 

BTW I was researching this some time ago.

 

I've confirm it too myself.. it only does it on the one that has the apps on it.. however both are made the same. I don't see why it does not like it... maybe the date of the partition or something... I'm working on a new one to see if I can get by this error.

I also have a update for you guys who are thinking of buying SSDs to use on HDDOSD. Its does more or less get by/removes the slow down bug/error. I have my 400GB SSD using the same HDD img as before plus 105games games on it. only like 180gb free.

 

I'm finally getting some time to get back to messing with my PS2 setup, and I am having a issue with hdl_dumb. I have my drive plugged into my laptop through an adapter, and other tools like winhiip see it no problem, but for some reason hdl_dumb just responds with Unexpected Problem the device is not ready

 

vash32, did you ever get a chance to fix the new image, I can test anything if you need me to

 

Hello?

 

this. which is why i only use hdl dump helper gui now

 

You could just change it back.
It probably doesn't modify your game, BTW. Unless AKuHAK has found that it actually does. The HDLoader has the startup path stored in the game data structure.