What do you mean in the readme by a PS2 ASIA (non NTSC-J)?

[CristobalPenaloza]

I'm planning on getting a new PS2, and I don't know if it will be fully compatible with all regions (I want PS2 and also PS1 compatibility from all regions).

The model I saw is a SCPH-50006, it says NTSC-J on the back.

I read that it's from south asia, not from Japan.

My question would be, is this an ASIA PS2? Will be able to play american PS1 games with MechaPwn installed? Or it's another model you are referring to?

[ghost]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended.

P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

[israpps]

IIRC asian units are 05, 06, 07, 09

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended.

P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

[israpps]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably

Yet it's a 90k...

Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably

Yet it's a 90k...

Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

No my console doesnt have a modchip but the other one have modchip scph 77004 but i only use usb to it for a reason but im still happy playing with it ,plus i bought the 90000 console for very cheap price which is a very lucky buy so i could play on disc which we have many burned disc and the main reason is jak and daxter precursor legacy and i tried the dtl 90000 and i tried to autoboot it but the ps2 logo never appear and somehow it sends me rsod which kind of anger me but it can boot with gundam musou which is the only original ps2 game i ever had plus if you wanna know about the problem of dtl 90001 here is the video https://www.reddit.com/r/ps2/comments/ucrph5/so_my_scph_90000_turned_dtl90001_wont_autoboot_as/?utm_medium=android_app&utm_source=share

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably

Yet it's a 90k...

Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

[israpps]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably Yet it's a 90k... Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

Reinstall with my custom Installers https://israpps.github.io/FreeMcBoot-Installer/test/8_Downloads.html

ender the normal install menu and choose the option that says "For all PS2"

This will load FreeMcBoot into all possible region paths, however, the console will only use American system

You can leave that one along the uropean folder, since you also have a 77004...

In my installers you´ll easily differentiate region folders from the browser, since the icons are named with their region

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably Yet it's a 90k... Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

Reinstall with my custom Installers https://israpps.github.io/FreeMcBoot-Installer/test/8_Downloads.html

ender the normal install menu and choose the option that says "For all PS2"

This will load FreeMcBoot into all possible region paths, however, the console will only use American system

You can leave that one along the uropean folder, since you also have a 77004...

In my installers you´ll easily differentiate region folders from the browser, since the icons are named with their region

Ok i''ll try that tomorrow.

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably Yet it's a 90k... Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

Reinstall with my custom Installers https://israpps.github.io/FreeMcBoot-Installer/test/8_Downloads.html

ender the normal install menu and choose the option that says "For all PS2"

This will load FreeMcBoot into all possible region paths, however, the console will only use American system

You can leave that one along the uropean folder, since you also have a 77004...

In my installers you´ll easily differentiate region folders from the browser, since the icons are named with their region

Now it wont boot up on both consoles i have to buy a fortuna card

[israpps]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably Yet it's a 90k... Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

Reinstall with my custom Installers https://israpps.github.io/FreeMcBoot-Installer/test/8_Downloads.html ender the normal install menu and choose the option that says "For all PS2" This will load FreeMcBoot into all possible region paths, however, the console will only use American system You can leave that one along the uropean folder, since you also have a 77004... In my installers you´ll easily differentiate region folders from the browser, since the icons are named with their region

Now it wont boot up on both consoles i have to buy a fortuna card

Are you sure you made a installation compatible with all consoles??

You should see 4 FreeMcBoot icons on browser

[israpps]

Yep it wont boot up just black screen even the fmcb logo wont appear and i follow your instruction and yes i see the four icons

This is extremely odd...

Unless the console has a modchip

[mobuis09]

I think it's an chinese region lockout called NTSC-C(China). If you're planning to buy a new PS2 for MechaPwn, I suggest buying the NTSC-U/C(USA and Canadian) version starting from 50000 model cause NTSC-J models have an issue of unable to play PAL PS2 games and PS1 games other than NTSC-J PS1 game. The Github says 75000 model and later doesn't have this issue, but it seems it's not true. I think every NTSC-J model has this glitch of some sort unless if this is intended. P.S. The Github also says PAL version of PS2 has this some kind of an issue, but I can't assure you if that's actually true.

Plus the ntsc j scph 90000 i owned converted to dtl 90001 wont autoboot and the fmcb keeps appearing everytime it bypass the ps2 logo which is my only way to play disc with ps2 logo innit which that disappoints me

After being patched your console started using the American system update folder instead of the Japanese one probably Yet it's a 90k... Probably it is incompatible with FreeMcBoot and you had a DEV1 launcher working with a modchip??

And i updated my fmcb 1.965 to 66

Reinstall with my custom Installers https://israpps.github.io/FreeMcBoot-Installer/test/8_Downloads.html ender the normal install menu and choose the option that says "For all PS2" This will load FreeMcBoot into all possible region paths, however, the console will only use American system You can leave that one along the uropean folder, since you also have a 77004... In my installers you´ll easily differentiate region folders from the browser, since the icons are named with their region

Now it wont boot up on both consoles i have to buy a fortuna card

Are you sure you made a installation compatible with all consoles??

You should see 4 FreeMcBoot icons on browser

Yep it wont boot up just black screen even the fmcb logo wont appear and i follow your instruction and yes i see the four icons and it was stuck from dtl 9

Yep it wont boot up just black screen even the fmcb logo wont appear and i follow your instruction and yes i see the four icons

This is extremely odd...

Unless the console has a modchip

Well i press the r1 button so i could launch myself to ulaunchelf on the other one while i dont need that to that to my 90000 one and my console is now stuck dtl 90001 fortuna is the only way now to reinstall my fmcb again but i have to wait for days but anyway thanks again.

[israpps]

If you managed access to uLaunchELF install FunTuna Fork...

It has latest OpenTun (better than Fortuna)

That should work on both slim consoles!

[mobuis09]

If you managed access to uLaunchELF install FunTuna Fork...

It has latest OpenTun (better than Fortuna)

That should work on both slim consoles!

My plan is fmcb is on my 90000 and the funtuna is on my 77004 since i launch it directly to ulaunchelf since fmcb wont boot up and freeze on bios which because my modchip is fake toxic dms4 when my fmcb mem card is still not bricked yet

[mobuis09]

If you managed access to uLaunchELF install FunTuna Fork...

It has latest OpenTun (better than Fortuna)

That should work on both slim consoles!

Good thing my modchip have MC devolution which have ability to launch boot.elf i and i manage to make it work again but 1.953 works better your version of fmcb ofcourse cross region

[mobuis09]

If you managed access to uLaunchELF install FunTuna Fork... It has latest OpenTun (better than Fortuna) That should work on both slim consoles!

My plan is fmcb is on my 90000 and the funtuna is on my 77004 since i launch it directly to ulaunchelf since fmcb wont boot up and freeze on bios which because my modchip is fake toxic dms4 when my fmcb mem card is still not bricked yet

Honestly your fmcb icn was better than the official one