Printable View
Hi,
Is it possible in FMCB to configure item that are located on hdd0 device (hard disk) instead of just mc0, mc1 and mass option that I see in FMCB configurator. Is there IRX module for hard disk?
Currently I use uLE to automatically launch at startup and program my items there, but it will be more convenient to have it directly in FMCB OSD.
Thanks.
No. Not with the current design.Quote:
Originally Posted by matrone21
IRX modules for HDD do exist (several are required for HDD to work), but the preferred FMCB boot KELF does not have free room for those modules. We only have two possible KELF files to choose between for this purpose, and switching to the bigger one would waste appx 1.4 MB of MC space, as well as a lot of bootup time (since that 1.5 MB file would have to be loaded from MC at each boot, instead of the normal 75KB file).Quote:
Is there IRX module for hard disk?
But it would not be more convenient to lose 1.4 MB on every bootable MC, and also get a much slower boot response...Quote:
Currently I use uLE to automatically launch at startup and program my items there, but it will be more convenient to have it directly in FMCB OSD.
So you'll do better using your present method.
Best regards: dlanor
Not to argue here (goodness knows this has been hashed around enough), but I'm curious if there's enough space in the boot KELF to add in the hooks to let the HDD IRX be loaded as seperate modules, much as the USB modules currently are.
Not that I'd use the functionality myself, but I must admit I'm curious. The USB modules were seperated for space reasons, and the only arguments I've seen against HDD support are lack of space.
So it is possible though?
If you replace the USB modules with the HDD ones, and use a bigger DVDELF.BIN (I have an old V7 myself), it would work? Or was HDD support just not coded in?
Right now I'm using my second memory card to hold all my ELF files (and one .02 file(HDTV Player)), and it comes to a grand total of 7.3 MB, which leaves no other use for the memory card. (I could use a USB stick, but I'm picky about looks and prefer not to have it sticking out... LoL)
And for me, 1.5MB is a MC saver compared the big 7.3! :wow:
No, just swapping the modules wouldn't work; support for it would have to added into the loader.Quote:
Originally Posted by MidniteAssassin
If its just the look of an extra device sticking out of your console thats a bother, you might want to invest in a larger MC. There are 32 MB and 64 MB cards available and pretty cheap on E-Bay, some around $10US.Quote:
Originally Posted by MidniteAssassin
This way you retain the same look you have and gain more space to use, the only drawback is the longer time it takes to read it by games and apps, but its not a problem as long as you dont pull out the card or turn off the console while it is being written to.
Try pack Your programs. ;]Quote:
Originally Posted by MidniteAssassin
Second solution for You is replace some gfx by images with one color (good for packing). i.e. Code Brekaer v9.3 could be fit in 300KB. ;]
The cases are quite different. USB is a fileio device, as is the MC driver, so a lot of the EE-side libs and IRX module loading code is already present. HDD is a fileXio device, requiring the loading of multiple unique IRX modules not otherwise used in FMCB, and the EE-side libs are also more complex.Quote:
Originally Posted by Azhrael
Summing up:
I find it highly doubtful that there can be sufficient free room in the payload section of the 75KB KELF for the additional EE-side code needed to load and use HDD modules, even if they are stored as external IRX files. It is still untested AFAIK, but extremely doubtful.
I think an HDD booter would require an external elf, and then there's no point.
We can already get HDD-capable menus through external elfs.
No, it would not work.Quote:
Originally Posted by MidniteAssassin
USB is a fileio device requiring fileio libs defining "fio_*" functions.
HDD is a fileXio device requiring fileXio libs defining "fileXio_*" functions.
Plus the additional requirement of 'mounting' partitions,
and the fact that HDD access is always split over two separate fileXio drivers.
(One for hdd0: and another for pfs0: through pfs9:.)
Summing up:
There is no way ever to make any elf use HDD instead of USB, simply by driver replacement.
If you insist on having an ELF collection on MC, then of course it will take up a lot of the available space. You should then consider getting a larger MC, to cope with that.Quote:
Right now I'm using my second memory card to hold all my ELF files (and one .02 file(HDTV Player)), and it comes to a grand total of 7.3 MB, which leaves no other use for the memory card. (I could use a USB stick, but I'm picky about looks and prefer not to have it sticking out... LoL)
And for me, 1.5MB is a MC saver compared the big 7.3! :wow:
The 32MB Datel Max Memory MCs are a good choice as they are compatible with just about everything and yet not as slow as the 64MB models. (Thinking back, I think I'd rather have four more 32MB cards than the two 64MB cards I recently bought. They are too slow for comfort.)
Best regards: dlanor
I think I may have left out some detail in my previous post...
I actually have a 32MB memory card in my 1st slot, which is how I can use my entire 2nd memory card for ELF files and such.
But I thought that using HDD would be faster, and not having to have a USB drive in the PS2 when it's turned on. (And in my case, more MC memory.)
Seriously? Mine is 3MB right now... Do you have a link to a tutorial on how to do that?Quote:
Second solution for You is replace some gfx by images with one color (good for packing). i.e. Code Brekaer v9.3 could be fit in 300KB. ;]
I don't know how to unpack CB. ;] It's not a "standard compression" which using i.e ps2packer or sjcrunch.
Some about two years ago I've seen that's version, but ALL images are black and of course looks ugly.