socram8888 / tonyhax

PS1 savegame exploit
Do What The F*ck You Want To Public License
437 stars 24 forks source link

40 Winks #123

Closed NuSynth closed 1 year ago

NuSynth commented 2 years ago

tonyhax version:

Installation method:

Console model:

Integrity check: If it boots, does the built-in integrity check succeed?

BIOS version: If you can get to boot, which version of the BIOS does it report?

Target game:

Bug explanation:

I have made two copies of this game. Every other game I have burned works. Most of them work great on these CD's that I'm using. But the TonyHax CD only prints this to the screen when I try to boot 40 Winks:

Initializing CD Disc error type D code 12 (x11) Init failed Reinitializing kernel Copying patches to 000009EC Installing modchip patch Installing FreePSXBoot patch Swap CD now

socram8888 commented 2 years ago

So what you are doing is booting Unirom from the memory card using FreePSXBoot, then booting into tonyhax, and then into 40 Winks?

NuSynth commented 2 years ago

Yeah.

I've had issues with games not working well with Unirom's version of FreePSXboot. The memory card I was able to transfer files from on my computer is too slow for FreePSXboot, but not TonyHax. So I used TonyHax on that memory card, to boot into the Unirom cd and install FreePSXboot from there, onto the faster card that I couldn't transfer files onto completely from my Arduino due to pin 3's power requirement.

alex-free commented 1 year ago

Alright, so I went ahead and burned a CD-R of 40 winks USA. Booted correctly and works (used tonyhax v1.4.4. Boot CD and CD Player Swap Trick on my stock SCPH-1001).

Since @Dartomic is also having issues booting games in UniRom (hence their weird booting setup of using unirom first to boot the tonyhax boot cd, although that doesn't matter in this case AFAICT), this really seems like a hardware issue, similar to https://github.com/socram8888/tonyhax/issues/114 .

socram8888 commented 1 year ago

Perfect, thanks for the testing! That means either something I changed magically fixed it, or it's (most probably) a hardware issue. Either way, closing!