Bug reports

[KnoWei]

Humm, i cannot experiment this myself while my ps2 do not use component cable.

It was a good idea to check the different SMS launch technique all the same. Thanks.

Let hope others can try and solve the problem.

If anyone could confirm they are (or are not) having this problem when using SMS in 1080i and launching from FMCB that would be useful to me. If your TV or projector is synching up properly I can write off my problem to local HW issues and add that to my reasons for replacing this projector.

~KnoWei

[psi88]

I think 2.9rev2 fixes the 1080i "issues"

have you confirmed you still have them with this version..

nvm, saw your "EDIT" above....

Can you not "force" fix the output of the projector at 1080i rather than letting it detect the signal and upscale the initial 480i image this way..

[KnoWei]

Can you not "force" fix the output of the projector at 1080i rather than letting it detect the signal and upscale the initial 480i image this way..

That's a thought. I'll tinker with it and see what happens.

I'm not sure but if I can nail-up the projector at 1080i I think lower resolutions may appear as small displays in the middle of the screen rather than being "upscaled" by the projector. I have four sources switched on the component input with different resolutions from each. Resolutions on the digitial cable in particular jump all over the place depending on the channel and content. I think the Wii is 480p.

If nothing else it will be another data point to think about.

~KnoWei

[slicer74]

Can someone take a look at this !

I'll try this myself this afternoon and reports !

Thanks.

[dlanor]

Can someone take a look at this !

I assume that this refers to the InfoNES-HD revisions by Kaylakaze, as the InfoNES revisions that I made have no HDD support at all.

I've just tested her "InfoNES-HD v1b.elf" in a way similar to how I think TATTOZIT did it, and it is true that the program spends an extremely long time showing only:
"Please wait while the hard drive is loaded."
and this probably means that the program is completely hung.

When booting the console with FMCB active, I get this hanging result regardless of whether I launch the program from MC using the FMCB OSDSYS menu, or by using the uLE FileBrowser. The results for those two tests are identical. It is only when I use uLE to launch InfoNES-HD from an HDD partition that the emulator starts properly, showing the 'wait' message only during a brief delay before proceeding to show the HDD root partition list.

However, if I boot the same console with modchip active, and let it launch the same copy of uLE (mc0:/BOOT/BOOT.ELF is used both for FMCB and modchip Dev1 boot), and use this to start InfoNES-HD from the same MC file that failed above then it does not hang, but only delays briefly as described above, and then continues on to display the HDD root partition list, as it should.

I'm not sure what it is that happens here, but apparently something goes wrong in the HDD access initialization of InfoNES-HD when FMCB was used for the initial boot, and the application that launches InfoNES-HD (whether FMCB or uLE) does so from MC, rather than from HDD (only with uLE of course).

This led me to suspect that some initialization of HDD access is missing, which the modchip boot might provide (as it is HDD-aware) but the FMCB boot does not (has no HDD awareness). So I decided to test this as follows:

1: Boot FMCB and launch uLE
2: In uLE FileBrowser first browse to hdd0: (just to the root)
3: Still in same FileBrowser session, back to root device list and browse to mc0:
4: Continue browsing mc0: to find and launch the InfoNES-HD elf from MC

The result of this test was an error-free launch of the program, showing the HDD root partition list, just as when booting with modchip or when launching the program from HDD.


Conclusion:
InfoNES-HD is dependent on something unknown for its HDD access initialization. Whatever that 'something' is, it will be provided by either a DMS4pro modchip Dev1 boot or by any access made to HDD by uLE or similar homebrew before launching InfoNES-HD. In my opinion this means that it is InfoNES-HD which is in the wrong here, but if it is possible to fix this by some minor change to FMCB, that would be the better choice, since such a fix could also benefit other applications.


User advice:
I recommend using the FCEU NES emulator instead, as it seems to work perfectly here for the same kind of operation where InfoNES-HD failed. I tested FCEU by doing the following:

1: Copied FCEU v0.92 Rev2 (the latest bug-free release that I know of)
2: Configured FMCB to launch that FCEU elf
3: Booted FMCB and launched that FCEU elf from the OSDSYS menu
4: Checked that FCEU was capable of correctly running NES rom files loaded from HDD.

It is not at all surprising that FCEU works better for this HDD initialization, since it has borrowed some of its rom browser code and console initialization code from an earlier version of uLE.

Best regards: dlanor

[slicer74]

Thanks a lot m. dlanor

I have the same conclusion here... Use FCEU from OSDSYS without a problem here.

Let hope that Ragnarok can solve the problem regarding InfoNES.

It was just to be sure that FMCB didn't but wiht HDD access.

[dlanor]

Let hope that Ragnarok can solve the problem regarding InfoNES.

Why should he do that ? I'm not even sure if the latest sources for InfoNES-HD are available. Kaylakaze did post some sources, but I'm not sure if they're fully up to date. In any case, it should really be her decision whether or not to continue development on it.

As for ragnarok2040, he has his own NES emulator to continue development on. It would be a bit much to also ask him to fix the competitors...

To be quite honest, I consider the FCEU v0.92 rev 2 beta to be so much better than any of the InfoNES versions that I consider it a waste of time to develop my own InfoNES revisions any further. It is unfortunate that some of his later improvements to FCEU introduced bugs that have still not been completely fixed (at least not in a released version). But even with its current limitations (lack of config menus for many CNF-file configurable features) FCEU v0.92 rev 2 is still by far the best NES emulator available for the PS2.

It was just to be sure that FMCB didn't but wiht HDD access.

I don't think there is anything formally wrong with what FMCB does, so the problem only arises with applications developed and tested on modchipped consoles, as they may have become dependent on something done by such a modchip, though not done by an enhanced OSDSYS (which is what FMCB really is).

So if it can be done by some minor effort/addition, it would be better to do the same thing as part of the FMCB initialization, to ensure compatibility with software developed on/for such chipped consoles.

Best regards: dlanor

[slicer74]

I'm talking about his own release actually !

I though that the guy has tried this one, not the girl release

[DaRKcLoUD-X]

FMCB 1.8b has worked great for me, i have used it on 2 different consoles so far and it worked perfectly but i had some issues on a different console. The console i just installed it on was a slimline and the install went fine on the console. FMCB loads up like it should and I can load programs from the OSD menu but the direct ESR function wont work on this console. I even used my own memory card that works with both of the working consoles ( a fat ps2 and a slimline) on this console and it wont use the direct ESR function. There is no directory issue, the path to the elf is perfectly set up and I know my set up works (as i said before it works on two other consoles). So im not sure what is going on, I dont think it is one of the newest ps2's that cant load FMCB because FMCB loads up on this console. When I try to load a dvd-patch game it goes into dvd mode and shows that error message that it can't load the dvd. It doesn't even switch over to ESR. The discs are patched and all of the discs are burned at 4x speed. Perhaps the direct ESR function doesnt work on newer slimlines.

[kevstah2004]

^ Try loading ESR_GUI_test2 manually with uLE, FMCB's osdmenu or button launcher instead of using FMCB's FASTBOOT feature for some reason with certain patched discs the PS2 reads them as normal DVD-Video's.