I will give this a try and report possibly tomorrow. Thank you for the effort!
If you want to use the version where you can enable/disable the cdvd init fix, yes, you have to manually edit the CNF to add the new variable and save it.
Problem is that from this point you should manually edit the cnf, because configurator won't respect this new variable, erasing it.
As you don't plan to use the lens I suggest you using the first version I uploaded, as it is always disabled there and you don't have to bother with the cnf file.
Tried both EMBED.ELF you provided in two different re-installations of fmcb 1.7. Placed one in the inject folder and ran fmcb1.7, did an uninstall of multiversion, then new multiversion install. In both instances, exactly same behavior as before...HDL only successfully lauches games is tray is ejected when hdl is launched! I see what you were saying about the cnf'er erasing the manual entry of the enable/disable choice or the cd/dvd init. fix now.
Same problems here on 2 V9 models, hdloader patched with dvd fix that worked well on my DMS3 chipped V9 model dont work with the same hdloader launched by freemcboot. This one happens in a strange manner, flash screen of hdloader is shown and that begin the search of list of the games on the hard disk but this never finish (i waitedd 15 min). I must say that this happen on my Maxtor 500 gb and a have no problem on a Maxtor 120 gb on wich hdloader lauched by freemcboot works well (its the same hdloader patched 0.8c i have always used.....).
I just had a thought concerning these v9-specific problems with FMCB.
We already know that the OSDSYS console initialization of FMCB (reviving old System Configuration settings etc) is incomplete, which causes some problems with realtime clock and colour setup for component cables, which effects also vary depending on how the games/homebrews are launched.
Suppose that the side effects of missing initialization go further on the v9 models, and also cause this problem for HDLoader. I'm not saying that's it, but it's a possibility, and one of the few things that could make sense at this stage.
If that is the cause of it, then there's good hope that it may be fixed in v1.8, since jimmi has already made successful experiments with how to preserve all system configuration settings (at least all I'm aware of).
Best regards: dlanor
My biggest question is why would v9 and HDL work fine with fmcb 1.1b, but not the newer ones? I know somewhere between 1.1b and the newer RUNME.ELF that followed, hdl stopped working for me. If it wasn't the cd/dvd intit. fix, what else could it be?
It would be unreasonable to expect jimmi and Neme to now go back to v1.1b and start over.
The best we can hope for is that continued work towards full compatibility, based on improvements to the current version, will eventually eliminate the v9-specific problems.
So far these v9-specific problems are confirmed by only two users in this thread. Surely this site must have more FMCB-users with v9 consoles than just two. So it would be extremely useful to have more reports from other such users, reporting how/if FMCB works on their v9 consoles.
We absolutely need to know if the problems apply to all v9 consoles, or just to some.
Best regards: dlanor
What drives me mad is my v9 having the same behaviour, but depending on the cdvdfix and hdloader patching, which doesn't seem to apply to his one.
Maybe i have understand where is the problem with my Maxtor 500gb (because maxtor 120gb have no prblems with hdloader loaded from magiccard); i have tried to load hdloader from a partition of 500gb hd (the same that i have always done with dms3 in dev2 mode) and loaded perfect (from ulaunchelf not directly from ps2 browser on V9 not chipped).....what a strange thing?
Is your HDL 28Bit patched?
It should be 48Bit-LBA patched, thought. :rolleyes: