Btw.: @JNABK: Just because of the SYS-CONF-Folder, where the CNF is present, along with the Drivers,...
I re-created the worst case scenario (I have a chip to recover,...).
I only leave the installed files and the USB-Drivers on my MC on my MC.
This way, all works like it should.
But,... If I delete the SYS-CONF, just to let FMCB use hard-coded strings, the USB-Drivers are also away.
You see the problem, if the drivers are in the same folder as the config?
Just 1 question.
Why, do you want to "prevent" the creation of a "new" folder.
I think, we can make an "Inquiry" (babelfish ), who has this folder on his MC.
I'm pretty sure, that nearly EVERYONE has this folder (B?DATA-SYSTEM) on his MC,...
It is the "Your system-configuration"-Icon, you will see in your MC anyway,...
...and if you don't like to see more Icons in FMCB-Browser, we can hide FMCBs Icons in 2 ways.
-...or a new function, that hides FMCBs ICONs.
Btw.2: I think a real "rescue-function" is better, when it is not related IN ANY case, to the CNF (like FMCB handles the loading).
Also, that it shouldn't be in the same folder,...
...and this way, it does now it isn't a standard.
Sorry, that I replied it again here, but this is the perfect place for it. ^^
FMCB should work after install, without the need of another way, to recover it (e.g. Modchip, Swap, other things...).
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