[Help needed] fmcb v1.7 -urgent-

[Syed]

I have freemcb.cnf on mc not in mass ok i will to put it on mass thanks

[drcatj18]

JNABK is probably right. you may also want to check your CNF file to ensure that you saved it to mc0: before you close configurator.

[Syed]

Same prob happening too.. Actually what is the prob?My ps2 or fmcb?Or my ps2 does compatible with fmcb 1.7?Or my mc prob?I have try to 4mat but prob too..

[JNABK]

Well maybe you could explain what exactly you mean by "happen back", as this seems to imply the CNF is reverting back to a default state, which doesnt make sense.

Tell us what it is you do to fix the CNF and what you did when it "happens back".

[propered]

from what i understood "happen back" could mean

XXX.ELF
sometimes changes back to
XXX.elf
without him actually manually changing it

(I just wanted to give syed another way of explaining it - if indeed he meant this, if he didnt apologies lol)

and maybe he can confirm this or not.

[Syed]

'happen back' i mean that the problem is come again(cant launch anything ulaunchelf,ers,fmcb configurator)..I have open the cnf and the setting is set like i manually set. I dont have any way to fix the CNF file coz it correctly like i want ..But still can launch anything..When launch,it come back to fmcb menu .. I sure that work ELF not change to elf bro..

[JNABK]

It seems as if its not saving when you edit it, or your not selecting the "Save to mc0:, mc1: or mass: and if you are, maybe your not waiting long enough for it to say "Saved to mc0:, mc1: or mass: at the top in red.

It cant just go back to the old settings all by itself. Make sure it says that at the top before you go out of the configurator screen.

[dlanor]

It seems as if its not saving when you edit it, or your not selecting the "Save to mc0:, mc1: or mass: and if you are, maybe your not waiting long enough for it to say "Saved to mc0:, mc1: or mass: at the top in red.

It cant just go back to the old settings all by itself.

Not really, of course, but it might still seem that way to him when he does things the wrong way.

For example: Some posts back Syed said that he was going to follow your advice about putting a CNF on a USB device, which was a misunderstanding, as you just mentioned the possibility of having a CNF there, and that it could affect things.

I think that he originally had other problems, but that some of his present problems may be due to his mistake in following what he misinterpreted as advice from you.

Because if he did store a CNF in mass:/ at that time, then everytime he happens to have that USB stick inserted during the boot, FMCB will be reading its settings from that CNF. And no matter how many times he then attempts to save new settings to MC0 the console will still "go back" to the same settings from the Mass CNF at each new boot with that USB device present.

Ironic isn't it, that your original advice about avoiding this problem may have misled him (through his own misunderstanding) into creating that very problem.

But he probably does make some tests without the USB device too, and those are probably the occasions when it seems to work for him.

The advice you gave about what to do normally is perfectly fine, but he also needs more explicit advice about what not to do. Such as NOT having any CNF on a USB device normally, since that will make the console dependent on that CNF, instead of using the one on MC.


Consistently using a CNF on USB instead of MC will work of course, but it makes the FMCB setup dependent on that USB device, which is inappropriate IMHO.

So the setups we should advise people to use should always have the CNF on the same MC as FMCB itself, and never on any USB devices, so that the console will boot consistently regardless of whether or not any USB devices are inserted at boot time.

Using a CNF on the USB device is IMO for emergencies only, much like the RESCUE.ELF method of recovering from bad setups. (And redundant since RESCUE.ELF is more powerful)


@Syed:
What I discussed with JNABK above can be summed up in a single sentence for you:
Delete any "FREEMCB.CNF" file you may have in the root of your USB device(s) !

Best regards: dlanor

[JNABK]

Yep, your right dlanor, i should have given more specific advise.

This is one confusing thread and we still dont know what he has been doing with the CNFs. He seems to have missed my sentence:

Tell us what it is you do to fix the CNF and what you did when it "happens back".

But deleting the USB CNF or simply not using the USB stick {if all apps are on the MC} should help isolate the problem to just one CNF to work with.

[Syed]

Last night,i have tested install using cd and all usb is unplugged from my ps2.. But the same prob happen too..What do u think is the prob?My ps2?Mc?