PS2 How to properly combine HDD-OSD and FreeHdBoot 1.966

PCSX2 not supporting encrypted executables for "__mbr" and "PP." partitions. Or it does? In v1.6 didn't. ;p

And besides that, if you replacing bootstrap (payload is wrong term here), you must update sector count it occupying. Sector count taking whole XLF size + padding.

You can use PS2HDH, it allows you to inject/backup/clear __mbr from bootstrap but it must be with padding.
 
No official pcsx2 doesn't support magicgate at all everything needs to be decrypted beforehand in order to run, same with the .VOB files from the update & utility discs.
It seems to be able to run extracted erom dvd & osd kelfs that have been decrypted & resigned to dnasload load as regionfree but mbr without the elf header it doesn't know what do with it.

I did have a decrypted osdsys / osdmain.elf of fmcb that worked on v1.6 but i've since lost it, it was from my fat v7 or v9 ps2 iirc before I swapped it for a ps3.

The unsigned binaries work for both fmcb & fhdb launched from uLE but not as osdmain.elf replacements.

There's an arcade fork that supports magicgate but it only runs under windows10, v1.7 & onwards needs some python .dll ?
api-ms-win-core-memory-l1-1-6.dll
that only windows 10 supports, I tried backporting the Qt-x64 build with https://github.com/crystalidea/qt6windows7 but it's still missing some files for .svga & mousepad etc.

Last pcsx2 build I have working is a hacked v1.7.3581-windows-64bit-SSE4-wxWidgets, the decrypted 3GB polyviewer & hddosd image works on it.

Edit: pcsx2, Funtuna works but it slow grinds to around 5fps after the code gets injected, I didn't try running any other elfs off the osd menu with it yet to see if it returns to normal speed after a iop reset in uLE.
 
Last edited:
  • Like
Reactions: TnA
PCSX2 not supporting encrypted executables for "__mbr" and "PP." partitions. Or it does? In v1.6 didn't. ;p

And besides that, if you replacing bootstrap (payload is wrong term here), you must update sector count it occupying. Sector count taking whole XLF size + padding.

You can use PS2HDH, it allows you to inject/backup/clear __mbr from bootstrap but it must be with padding.

Can I run the extracted PS2HDH .tar shell scripts with Cygwin on a VHD?, I don't have a Linux setup unless I run it with a VM.

The batch installer allows me to access the VHD as if it where a real drive, idk about the updated BBN English patch.

I can't mount freshly uLE formatted pcsx2 DEV9HDD.raw files with VHD but I can rename VHD to .raw an they'll work in pcsx2.
I can also mount the hdd in pcsx2 an access it via network.

HDDRawCopy won't work with a VHD on windows7 something about hashes for md5 or sha, the usual broken windows runtime enviroment update bs or bios security.
 
Last edited:
Cygwin is API translator. To use PS2HDH, you need more than that, full Linux environment because partition recognition base on exposed mappers by hdldump, which means you need kernel and multipath-tools.

VHD isn't raw disk image. It is native, dedicated, and bloated by garbage, a MS disk image format. PCSX2 supporting sector by sector disk images but also *.vhd (I dunno if *.vhdx, and dunno if both cases dynamic images).

Your last sentence is total nonsense. ;p
 
Technically MBR should work, because it is ROM/DISC signed (it can do it with the DVD-Player [erom] after all) and the rest CAN be there in decrypted form, sooo...
 
https://github.com/pcm720/protopwn/tree/main/utils/osdpack
I found osdpack but it's go script, no compiled release.

Unrelated to hosdsys.
I've managed to rebuild the bios using the osd files from softemu on netemu, it still works as the netemu bios fastbooting into uLE but can't run the browser yet, it gets as far as the reboot command but then doesn't seem to be able to trigger the gpu to display before loading the ATAD & HDDLoad modules.
I also swapped the KERNAL but I think it might also need the LOADFILE & EE CNFs from softemu before it can trigger the video display like uLE does.
 
Here's what I found so far with that decrypted osd110 hosdsys elf.
I renamed all the osd110 entries to osd100 because that's what the working decrypted pcsx2 hdd image uses.
If all the entries aren't the same as the actual loaded hosdsys hdd elf it won't load, as far as I can tell it just uses the same current dictionary or working dictionary as the loaded hdd elf without telling it a new pathway to load the modules.

The hdd is detached an pcsx2 complaing it can't find the module files.
It does say something about loading a larger modules.cnf list from pfs0:/ though before it lists them FNTOSD being the first, it also includes the icon's eg ICOIMAGE & others from the extracted scud pak.
 

Attachments

  • IMG_20251017_004342~2.jpg
    IMG_20251017_004342~2.jpg
    626.1 KB · Views: 30
Last edited:

Similar threads

Back
Top