L.S.D Posted November 15, 2004 Posted November 15, 2004 Yeah, I'm using that one. But it still say can't detect P1 and P2!! This is what it says
James Posted November 15, 2004 Author Posted November 15, 2004 (edited) Yeah, I'm using that one. But it still say can't detect P1 and P2!! This is what it says<{POST_SNAPBACK}> I will say this again and it will be that last time I will say this There is no P rom patches on this thread.There is only M rom patches. Edited November 15, 2004 by James
L.S.D Posted November 15, 2004 Posted November 15, 2004 (edited) Yeah, I'm using that one. But it still say can't detect P1 and P2!! This is what it says<{POST_SNAPBACK}> I will say this again and it will be that last time I will say this There is no P rom patches on this thread.<{POST_SNAPBACK}> I know! And the patch that you post here is supposed to patch the M rom! But that is the message I get when I am using your patch! Pls see attached! Edited November 15, 2004 by L.S.D
James Posted November 15, 2004 Author Posted November 15, 2004 (edited) Yeah, I'm using that one. But it still say can't detect P1 and P2!! This is what it says<{POST_SNAPBACK}> I will say this again and it will be that last time I will say this There is no P rom patches on this thread.<{POST_SNAPBACK}> I know! And the patch that you post here is supposed to patch the M rom! But that is the message I get when I am using your patch! Pls see attached!<{POST_SNAPBACK}> its a IPS patch and is meant to be used with Lunar IPS (LIPS) - IPS patch utility http://fusoya.cg-games.net/lips/ Edited November 15, 2004 by James
Abster Posted November 15, 2004 Posted November 15, 2004 I patched my M rom with the crc32 update in this thread, but it didn't really fix anything.
Agozer Posted November 15, 2004 Posted November 15, 2004 I patched my M rom with the crc32 update in this thread, but it didn't really fix anything. Was your M1 512kB in size with the CRC of ADEEBF40? If it was, you still have borked V roms.
Abster Posted November 15, 2004 Posted November 15, 2004 It was 128k in size with a CRC of B5ABDA07 Lets see if that second patch fixes it...
Agozer Posted November 15, 2004 Posted November 15, 2004 (edited) It was 128k in size with a CRC of B5ABDA07 Lets see if that second patch fixes it...Then your M1 is fine. There's something wrong with your V roms. Edited November 15, 2004 by Agozer
Abster Posted November 15, 2004 Posted November 15, 2004 Lets see how my V roms are... 272d-v1.bin CRC32: 32156CFE272d-v2.bin CRC32: 0E46D2F8272d-v3.bin CRC32: 9AA45090272d-v4.bin CRC32: AD8FABB4
pestilence Posted November 15, 2004 Posted November 15, 2004 Lets see how my V roms are... 272d-v1.bin CRC32: 32156CFE272d-v2.bin CRC32: 0E46D2F8272d-v3.bin CRC32: 9AA45090272d-v4.bin CRC32: AD8FABB4<{POST_SNAPBACK}> Those are fine....dunno what could be the problem...
Recommended Posts