I think there would be enough space for HD&Net-Stuff, if the loader is compressed in another way/with another compression + IRXs would be external.
Originally Posted by dlanor
That is true.
There would be room if using the DVDELF.BIN files from fat consoles, but those KELF files are not available on a slim console. And even on a fat console those files will waste an extra 1.4 MB (appx) for each installed MC, and the HDD boot feature just isn't worth that much (17.5% of a normal 8MB MC...).
Best regards: dlanor
I don´t think, Slim-Users would need the HD-Support anyway (o.k., there is an exception... the V12/13-Users with a HD.).
I think it won´t hurt, if users have the choice between two loaders.
Simple. If the DVDELF.bin, which is provided by the user or console offers enough space to embed the big loader, it should request if the big, or the small loader should be embedded.
If a small dvdelf.bin (be it from BIOS, or INJECT-Folder) is provided, it wouldn´t ask and install the standard-mini-loader.
If a big dvdelf.bin (be it from BIOS, or INJECT-Folder) is provided, it requests the user which version of the loader to choose (since for example the big-loader can have bugs).
If a big dvdelf.bin is provided for the embeddion, the mc-space is wasted anyway... But the user still should have the choice, which loader to choose.
PS2 V7/DMS3 V2 (FW:2.4b7); Seagate Baracuda 200GB
PS2 V7/CC1.0 (FW:34 hacked v2 BM:2.1.6); Maxtor DiamondMAX9 PLUS 160GB
PS2 SCPH-30004R; NoMod+NoLaser
3xSony MC 8MB
MAX/Datel 16MB with Boot-CD
Custom FMCB 1.8b+ Beta-Build, my AIO 0.5, Sony&xRhino-Linux