Bug reports

[Bootlegninja]

circle and cross. The rest of the world is a bit 'backwards' on the button configuration compared to the Japanese setup.

[katananja]

Originally Posted by TnA

Can you explain that a bit?
Which buttons are "reversed"?

Is just like Bootlegninja said, circle and cross.
I've told the guys at the time that the hacked OSD doesn't work with 10K when it was just a beta test, the hack did not change anything and did not crash the controllers,

Maybe the lack of necessary libs or whatever fails to make this hack happen in the 10k.

If this will not be implemented in the 10K for now (i hope it will loading external modules) a new function could be added to check if the system you are installing is 10k or not, if it is, don't hack the OSD so we can use the system.

[TnA]

So you have a EU/US-Buttonlayout, instead of JAP yes?
I'm not sure about, but I assume it has something to do with the init-loader (a.k.a. RUNME.ELF).

Edit: But it also can be launcher2, or something other. Sorry, I don't know it for sure,...

[katananja]

Originally Posted by TnA

So you have a EU/US-Buttonlayout, instead of JAP yes?

Yeap.

Originally Posted by TnA

I'm not sure about, but I assume it has something to do with the init-loader (a.k.a. RUNME.ELF).

Edit: But it also can be launcher2, or something other. Sorry, I don't know it for sure,...

I'm not following the hack it self, don't know if has to do with the files you mention but it was working fine before.

[nickatron]

Originally Posted by Spado

jimmikaelkael, I investigated about this problem...
I have a V9 and a V4 scph 50004 and scph 35004 and it works perfect with them...

My uncle has a V3 scph 30004 and a friend of mine has a 30004 too...
When I tested in my friend ps2 I had the same problem that I had with my uncle ps2: it loads Ule but when launching ESR it shows the logo but then there is only a black screen...

So I investigated about this problem, I tried to install all old versione of fmcb including 1.2c with ffgriever runme.elf...
At the end I got that the multi-version 1.5 is the best...
Anyway... It's strange that I tested it with about 10 games and ONLY ONE worked fine (Need For Speed Most Wanted in english)...
All other games didn't work...
So I tried to discover which is the problem and I found that when ESR remains black it doesn't find the disc...
So I tried to read the disc with other elf as Ule and SMS and I think I got the problem: also with them the CDVD doesn't read!

Not happy again, I tried to rip DVDELF.bin from the V3 (but I installed the multi version in the v3 too, so it has to be not useful..) and to put it in my USB Stick INJECT folder, also if I think I made some error, because nothing changed (as I thought)...

Now I am trying to discover if I can do something with modules but I don't know them a lot...

What do you think?

Did you ever find a solution to this problem? It seems to be the same thing that's happening to me.

I have a V4 SCPH-35001. I've burned 4 different games on 3 different types of media. All I get is a black screen when I load ESR.

[hans0l0]

I have a FreeMCBoot 1.6 card configured and working properly on a DMS4PRO SE V5/6 PS2 and an unchipped V4. I used this same card on a v7 with a disabled Crystal Chip 2.0 and it wouldn't show the hacked OSDSYS. The card worked but I had to hold down the BOOT.ELF key to start directly to ULE or HDLoader. It just stayed on Black Screen if nothing was held, and on the other systems it worked as configured, boot to hacked OSDSYS. I have booted this system before with 1.4 and 1.5 again without the hacked OSDSYS. The only other possibility I can think of is this system is configured to use the Y-Pb-Pr progressive scan 480P. Does the hacked OSDSYS work with 480P setting from the original system settings made prior to installing the hacked one?

Thanks for all your hard work.

-Han

[Neme]

Originally Posted by hans0l0

I have a FreeMCBoot 1.6 card configured and working properly on a DMS4PRO SE V5/6 PS2 and an unchipped V4. I used this same card on a v7 with a disabled Crystal Chip 2.0 and it wouldn't show the hacked OSDSYS. The card worked but I had to hold down the BOOT.ELF key to start directly to ULE or HDLoader. It just stayed on Black Screen if nothing was held, and on the other systems it worked as configured, boot to hacked OSDSYS. I have booted this system before with 1.4 and 1.5 again without the hacked OSDSYS. The only other possibility I can think of is this system is configured to use the Y-Pb-Pr progressive scan 480P. Does the hacked OSDSYS work with 480P setting from the original system settings made prior to installing the hacked one?

Thanks for all your hard work.

-Han

Thanks for testing. In theory the system settings should not affect the hacked OSD but nevertheless it's unknown whether it works with 480p or not. Can you check if it works without 480p on that same system, so we can make sure that it's indeed the 480p that causes the black screen?

[slicer74]

Are u sure the PS2 use 480p with the regular cable. It's not 480i ?

[katananja]

One more bug report, this time is with the 90K model:

Can't boot game from browser.

1 - Turn on PS2 with MC + FMCB (1.6) and let it go to browser.
2 - Put any game in, select it and press 'X' to start the disc
3 - PS2 will go to black screen, the game will not start and FMCB restart (with the boot screen and everything) going back to PS2 browser.

To launch the game or you start the PS2 without the FMCB MC or start uLE and boot the game from there, patched game or not, chip on/off makes no difference.

[dlanor]

Originally Posted by katananja

One more bug report, this time is with the 90K model:

Can't boot game from browser.

1 - Turn on PS2 with MC + FMCB (1.6) and let it go to browser.
2 - Put any game in, select it and press 'X' to start the disc
3 - PS2 will go to black screen, the game will not start and FMCB restart (with the boot screen and everything) going back to PS2 browser.

Ok, I'm with you so far...

To launch the game or you start the PS2 without the FMCB MC or start uLE and boot the game from there, patched game or not, chip on/off makes no difference.

But here you lost me completely...

In the first section quoted above you describe a problem specific to the Sony Browser, but then in the second section you describe a generic problem where the console is suddenly unable to boot the game by any method at all, not in any way specific to the Sony Browser. You even say that it makes no difference (meaning the game won't boot) even when you "start the PS2 without the FMCB MC", meaning that FMCB is not involved in that boot attempt at all. So any failure you then suffer has NOTHING to do with FMCB.

So when I add all of that up the sum seems to claim that using FMCB has ruined your PS2 so that it is now unable to boot a normal game by any method at all, even when booting with the FMCB MC removed (like you described).

I find that extremely hard to believe, and I think you must have left out some really important things from your report.

For one thing you never even mentioned what kind of disc it is that you are trying to boot.
(Pressed original or normal CD/DVD backup or ESR-patched backup.)

Best regards: dlanor

[TnA]

Originally Posted by katananja

One more bug report, this time is with the 90K model:

...not sure, if it is only there...
I believe, it is still fixed in Betas, because how it works now is different,...

To launch the game or you start the PS2 without the FMCB MC or start uLE and boot the game from there, patched game or not, chip on/off makes no difference.

Well,... chip on/off sometimes make a difference.
My DMS3 will not recognized PSX-Discs, if I start it in PS2-Mode (Normal OSD-Start). I must reach the OSD for that with PSX-OSD-Mode, or disable my chip.
Not a fault on FMCB, but of the chip (it simply won't recognize PSX-Disc in standart boot-mode). I must hold circle, but I also can hold circle (before FMCB-Logo is shown), then the FMCB-Logo comes up, I have time to leave the button off and it rejects me to the hacked OSD.
I also could load PSX-Backups with this method on my old DMS3 V2 and also Fastboot works in newest Betas with this way,...

[katananja]

Originally Posted by dlanor

But here you lost me completely...

In the first section quoted above you describe a problem specific to the Sony Browser, but then in the second section you describe a generic problem where the console is suddenly unable to boot the game by any method at all, not in any way specific to the Sony Browser. You even say that it makes no difference (meaning the game won't boot) even when you "start the PS2 without the FMCB MC", meaning that FMCB is not involved in that boot attempt at all. So any failure you then suffer has NOTHING to do with FMCB.

So when I add all of that up the sum seems to claim that using FMCB has ruined your PS2 so that it is now unable to boot a normal game by any method at all, even when booting with the FMCB MC removed (like you described).

I find that extremely hard to believe, and I think you must have left out some really important things from your report.

For one thing you never even mentioned what kind of disc it is that you are trying to boot.
(Pressed original or normal CD/DVD backup or ESR-patched backup.)

Best regards: dlanor

My pure guess is that the OSD hack does something it shouldn't because it has issues with 10K and now with 90K. My console is working fine, there is no damage what so ever, it just doesn't boot ANY PS2 game (original, backup, patched or not patched, CD or DVD) from browser if i let FMCB boot first, this problem is 100% eliminated if i remove the MC with FMCB, booting discs from browser works just fine.

Nothing important was left out, the bug report is simple as that.

Game start fine from browser if i don't use fmcb 1.6.
Game doesn't start from browser if i let fmcb 1.6 boot.
Looks like a loop, start game from browser > goes to black screen > return to browser.

The chip (Matrix 1.93) been on/off makes no difference, so is not my chip that is causing interference with the boot process. I've also made a few tests with previous fmcb (1.5) and there is no problem with that version, since osd hack was included at 1.6 that is why i'm guessing that is OSD hack attached to fmcb that is making this happen, if that hack can reverse the buttons order in JP browser you have a suspect right there.

A similar effect/bug/error can be reproduced with uLE:

1 - Start FMCB (any version) and boot uLE (my last is v4.26)
2 - Run PS2Browser.
3 - System goes to black screen and return to uLE, if fmcb version is 1.6 you will see the logo and return to uLE.

To this day, if you start uLE from fmcb, uLE is unable to launch the PS2Browser, unless you start uLE from fmcb and remove the MC right away from the slot, than uLE will run PS2Browser.

Similar problem is now happening with fmcb.

[katananja]

Originally Posted by TnA

...not sure, if it is only there...
I believe, it is still fixed in Betas, because how it works now is different,...

I hope they got the bug there, is terrible when the bug happens on specific models only.

Originally Posted by TnA

Well,... chip on/off sometimes make a difference.
My DMS3 will not recognized PSX-Discs, if I start it in PS2-Mode (Normal OSD-Start). I must reach the OSD for that with PSX-OSD-Mode, or disable my chip.
Not a fault on FMCB, but of the chip (it simply won't recognize PSX-Disc in standart boot-mode). I must hold circle, but I also can hold circle (before FMCB-Logo is shown), then the FMCB-Logo comes up, I have time to leave the button off and it rejects me to the hacked OSD.
I also could load PSX-Backups with this method on my old DMS3 V2 and also Fastboot works in newest Betas with this way,...

I use Matrix here and never found a problem, yet because i can boot anything so far, fmcb is doing his job just fine, i think is something attached to it that makes this problem happen.

[TnA]

While I read your bug-description, I think about the rejecting from OSDSYS back to FMCB, or the hack which is applied to the OSDSYS, to have the possibility to reject back is not working,...

About your Auto-Rejecting,...
Erm,... Did you set an ELF as Auto-Launch/Boot-ELF?
Because if uLE is your Auto-ELF it ever starts, regardless if you start PS2-Browser through ule's option, or the same function in other apps.

[jimmikaelkael]

Originally Posted by katananja

My pure guess is that the OSD hack does something it shouldn't because it has issues with 10K and now with 90K. My console is working fine, there is no damage what so ever, it just doesn't boot ANY PS2 game (original, backup, patched or not patched, CD or DVD) from browser if i let FMCB boot first, this problem is 100% eliminated if i remove the MC with FMCB, booting discs from browser works just fine.

Nothing important was left out, the bug report is simple as that.

Game start fine from browser if i don't use fmcb 1.6.
Game doesn't start from browser if i let fmcb 1.6 boot.
Looks like a loop, start game from browser > goes to black screen > return to browser.

The chip (Matrix 1.93) been on/off makes no difference, so is not my chip that is causing interference with the boot process. I've also made a few tests with previous fmcb (1.5) and there is no problem with that version, since osd hack was included at 1.6 that is why i'm guessing that is OSD hack attached to fmcb that is making this happen, if that hack can reverse the buttons order in JP browser you have a suspect right there.

A similar effect/bug/error can be reproduced with uLE:

1 - Start FMCB (any version) and boot uLE (my last is v4.26)
2 - Run PS2Browser.
3 - System goes to black screen and return to uLE, if fmcb version is 1.6 you will see the logo and return to uLE.

To this day, if you start uLE from fmcb, uLE is unable to launch the PS2Browser, unless you start uLE from fmcb and remove the MC right away from the slot, than uLE will run PS2Browser.

Similar problem is now happening with fmcb.

This is a known bug... (seems to happen on fat ps2)
When starting the ps2 with ps2 dvd disc on some versions, it fails to run the game from OSDSYS.
It doesn't happens with a ps2 cd game.

The strange thing is that the OSDSYS calls the same function for ps2 cd or ps2 dvd.

But we can't test it on normal OSDSYS because when you have a disc inserted it will be imediately booted...

The only explanation we have with Neme is that the old OSDSYS is buggy.

By patching the PS2 dvd launching (so then reading the SYSTEM.CNF ourselves and then run main elf) in last betas it fixes this bug

[TnA]

Originally Posted by TnA

While I read your bug-description, I think about the rejecting from OSDSYS back to FMCB, or the hack which is applied to the OSDSYS, to have the possibility to reject back is not working,...

Well,... I forgot, it was done in another way, by FMCB 1.6Final.
There wasn't even osd-disc-stop implemented,...
But it really SHOULD work now.

[dlanor]

Originally Posted by katananja

My pure guess is that the OSD hack does something it shouldn't because it has issues with 10K and now with 90K. My console is working fine, there is no damage what so ever, it just doesn't boot ANY PS2 game (original, backup, patched or not patched, CD or DVD) from browser if i let FMCB boot first, this problem is 100% eliminated if i remove the MC with FMCB, booting discs from browser works just fine.

Nothing important was left out,

Apparently not, but something incorrect slipped in, misleading me. Because in the post I replied to then you did say that starting the console with the MC removed made no difference, which in that context would mean that the game did not boot. Now it is clear that this is not what you meant, which changes the entire 'picture' of your problem for me.

A similar effect/bug/error can be reproduced with uLE:

1 - Start FMCB (any version) and boot uLE (my last is v4.26)
2 - Run PS2Browser.
3 - System goes to black screen and return to uLE, if fmcb version is 1.6 you will see the logo and return to uLE.

Are you sure this is the same problem ? (dubious, since no disc is involved in this)

Of course, if you have set up uLE as 'auto' boot elf in FMCB, then it will automatically relaunch uLE instead of going to the OSDSYS menu or Sony Browser. But that is easily fixed by holding down one of the buttons for which you have not defined any FMCB launch keys. By default all undefined keys point to OSDSYS, so that should get you into the OSDSYS menu or the Sony Browser (I get one result on my v7 and the other on my v15).