Update FMCB from FMCB

[dlanor]

I tried this and think it works ok, but I do not think it allows for you to inject you own DVDELF.bin.

I have tested that it does work, by installing with a 75KB DVDELF.BIN from a slim PStwo on a fat PS2, which does not have such a file in ROM. Since the resulting installation did use the 75KB osdmain.elf file this proves that the injection worked.

I may be wrong but I did not see it in the install.

Fortunately you are wrong, and the injection worked fine.

Possibly you were looking for the wrong text, as I believe the messages may have varied a little between versions.

FMCB v1.7 has three alternate texts shown to indicate the injection target.

when using DVDELF.BIN from the INJECT/ folder this text is:
"Reading your own DVDELF.BIN"

And when using a file from the PS2/PStwo bios rom that text is replaced by:
"Reading erom0:DVDELF" for a fat PS2, but

"Reading erom0:DVDPLx" on a slim PStwo and with the final 'x' replaced by a region letter

Best regards: dlanor

[pcklfshpd]

I have tested that it does work, by installing with a 75KB DVDELF.BIN from a slim PStwo on a fat PS2, which does not have such a file in ROM. Since the resulting installation did use the 75KB osdmain.elf file this proves that the injection worked.

Fortunately you are wrong, and the injection worked fine.

Possibly you were looking for the wrong text, as I believe the messages may have varied a little between versions.

FMCB v1.7 has three alternate texts shown to indicate the injection target.

when using DVDELF.BIN from the INJECT/ folder this text is:
"Reading your own DVDELF.BIN"

And when using a file from the PS2/PStwo bios rom that text is replaced by:
"Reading erom0:DVDELF" for a fat PS2, but

"Reading erom0:DVDPLx" on a slim PStwo and with the final 'x' replaced by a region letter

Best regards: dlanor

When I ran the install from my memory card in slot 2 with the DVDELF.bin in the inject folder using my slim ps2 I never saw the text "Reading your own DVDELF.BIN" I have installed from a usb stick and have seen the text.

If I need to set up the dir. different for some reason I am at lost as to what I may be doing wrong.

[dlanor]

When I ran the install from my memory card in slot 2 with the DVDELF.bin in the inject folder using my slim ps2 I never saw the text "Reading your own DVDELF.BIN" I have installed from a usb stick and have seen the text.

Are you sure that you have everything set up correctly in the installation package on the MC ? I ask that partly because I can't help noticing that you used the wrong names for both of the filesystem objects you mentioned in your first sentence above.

ie: "DVDELF.bin" must be "DVDELF.BIN" to work, and "inject" must be "INJECT"
If you made similar mistakes on the MC as well, that would explain your problem.

If I need to set up the dir. different for some reason I am at lost as to what I may be doing wrong.

I simply copied the folder in which I had the entire FMCB installer package, from the USB device I previously used for installs to the MC I wanted to use for running the installer, without changing a single file inside. And this worked perfectly for me.

I even tried removing the DVDELF.BIN for one of the installation tests, to check that I did get the expected change in the text displayed, and the even more significant increase of the osdmain.elf file, from 75KB to 1,462KB. And that too checked out correctly.

Something must be wrong with your MC setup, as you get different results. Have you double-checked that the package you stored on the MC really is complete, and with correct filesize for all components ?

Edit:
Since you said you made your test on a slim PStwo, I've now repeated my test on my unmodded v15 PStwo (the previous tests were made on a modded v7 PS2), and I still get the same fully working result, with the text "Reading your own DVDELF.BIN" being displayed during installation there too.

Best regards: dlanor

[pcklfshpd]

Are you sure that you have everything set up correctly in the installation package on the MC ? I ask that partly because I can't help noticing that you used the wrong names for both of the filesystem objects you mentioned in your first sentence above.

ie: "DVDELF.bin" must be "DVDELF.BIN" to work, and "inject" must be "INJECT"
If you made similar mistakes on the MC as well, that would explain your problem.

I simply copied the folder in which I had the entire FMCB installer package, from the USB device I previously used for installs to the MC I wanted to use for running the installer, without changing a single file inside. And this worked perfectly for me.

I even tried removing the DVDELF.BIN for one of the installation tests, to check that I did get the expected change in the text displayed, and the even more significant increase of the osdmain.elf file, from 75KB to 1,462KB. And that too checked out correctly.

Something must be wrong with your MC setup, as you get different results. Have you double-checked that the package you stored on the MC really is complete, and with correct filesize for all components ?

Edit:
Since you said you made your test on a slim PStwo, I've now repeated my test on my unmodded v15 PStwo (the previous tests were made on a modded v7 PS2), and I still get the same fully working result, with the text "Reading your own DVDELF.BIN" being displayed during installation there too.

Best regards: dlanor

I just retested install after changing my DVDELF.bin to DVDELF.BIN, my inject folder was named INJECT and that was it.

Funny thing was it worked fine before when I installed from usb, I guess when you install from a usb source the installer is not case sensitive.

Thxs alot for your help.

I will now be able to do my free install service with out having to bring my usb drive.

I am the guy who does free installs from my car in Las Vegas.

We have drive in weddings in vegas, so why not have drive in PS2 modding!

Best regards: pcklfshpd - Sin City

[dlanor]

I just retested install after changing my DVDELF.bin to DVDELF.BIN, my inject folder was named INJECT and that was it.

I suspected as much. Character casing is the most common error of all.

Funny thing was it worked fine before when I installed from usb, I guess when you install from a usb source the installer is not case sensitive.

This is probably related to the fact that the FAT32 filesystem is incapable of differentiating between differently cased names. That is part of this standard.

So if you store three files in the same folder named "Tst.Txt", "tSt.tXt", and "tsT.txT" in that order, then only "tsT.txT" will be there when you go look for them, as the other two will have been overwritten.

However, the casing of names that you used in creating new files is stored, so if you later copy that file to some other device, with a filesystem that does differentiate casing properly, then the name will use the character case of the original file. So it always matters that you use the correct casing, even on a device where the filesystem can't make full use of it.

Thxs alot for your help.

I'm glad that I could help, and also that we could find the definite reason for your problem, as I think this MC-only installation method will be preferred by many participating in the free installation services.

I will now be able to do my free install service with out having to bring my usb drive.

Precisely, and that was the whole point of this method.

It wouldn't make much sense for the average user though, who only needs to run the installation package once for each of his bootable MCs. Then he won't need it again until theres a new FMCB release, so it wouldn't make sense to let the installer package take up MC space constantly.

I am the guy who does free installs from my car in Las Vegas.

Oh yes, I remember seeing that earlier, in the free service thread.

We have drive in weddings in vegas, so why not have drive in PS2 modding!

Personally I find the latter much less inappropriate than the former

Best regards: dlanor