Any darn way to fix a (b1) rom??

[Mekanikles]

Hi y'all!

Is there anyway to fix a rom thats tagged (b1)?

ye' see, i'm home stuck with a crappy 56K and just got my own DONKEY KONG 64 rom:satisfied:

but alas, it was an (b1) rom with the error: "Stuck in a unexitable loop" (on the PJ5)

I've heard of something called Bad2Good pather, does this work and, if so, where can I get it?





-the one and only, Mekanikles

 

[Doomulation]

You've heard right!
Check out the link where you download goodn64 in my sig to get these wonderful patches and make it work!

 

[Clements]

I've heard about these... Can someone tell me that if you patch a bad rom, it will become identical to the 'Good Dump' of the rom? It just seems too good to be true! Great for me as a lot my roms are bad and I have a 56k connection only!

/me thinks Nemu netplay becoming viable...

 

[Lillymon]

It should become identicle to a good dump, since that's the aim of the patches.

 

[Clements]

It works great! It fixed four of my seven bad roms!

 

[scotty]

I was not aware that GoodN64 patched up roms, I want to know how you do this

 

[Clements]

GoodN64 doesn't patch the roms, IPSWin does. You use GoodN64 afterwards to check if the patch worked or not.

Patches:
http://www.smiff.clara.net/utilities/rom/Bad-to-Good_N64_ROMs_Patches.exe

IPSWin:
http://www.smiff.clara.net/utilities/rom/IPSWin_v2.0.zip

Follow the instructions you get. Its so easy even I could do it

 

[Doomulation]

Just remember to backup your roms before doing it! Failure will cause a corrupt non-fixable rom!(!)

 

[Mekanikles]

Hi again

thanx for the tip, i'm sure it works wonderful on some games but I still can't get DK64 to work!

I've tried two different versions but the result is all the same:
IPSWIN + patch turns the rom into something thats totally incomprehencible to me i.e the name is a bunch of symbols and random characters... plus the emulator doesn't recognice the chip nor the countrycode.

please help me, I don't want do DL the 27 Meg's again! (still stuck with 56K):getlost:

my current version of the rom is: Donkey Kong 64[E](b1).rom

:x

 

[Plisco]

Did you rename it after patching?

 

[Mekanikles]

qe?

whadda ye mean renaming it, the file itself or is there another way?

I'ts not the "cannot find chip or countrycode" problem that is the main nail in my eye... After these error messages the game still hangs up!

And as a disclaimer: Good64 recogniced the patched rom as a valid rom (i'm frequently puzzled)

 

[Clements]

And as a disclaimer: Good64 recogniced the patched rom as a valid rom (i'm frequently puzzled)

Did it rename it to 'Donkey Kong 64 (E) [!]' ? Or did it stay the same? (Donkey Kong 64 (E) [b1])

 

[Slougi]

Also, GoodN64 has been known to tag bad roms as [!] in the past, especially fixed ones, that are not really fixed

 

[Plisco]

qe?
And as a disclaimer: Good64 recogniced the patched rom as a valid rom (i'm frequently puzzled)

Using Good N64 to rename it after patching is what I meant,, as I recently patched a version of mario kart and had to used Good
N64 before it was recognised

 

[Clements]

Also, GoodN64 has been known to tag bad roms as [!] in the past, especially fixed ones, that are not really fixed

So, is there another way/program of verifying roms that could be used double check patched roms?

 

[Hacktarux]

Yup, mupen64 should be able to do that

 

[Doomulation]

Pj. It will mostly recognize good roms and not bad. Well, some but not much. Your best bet is actually goodn64.

Heh, hack.

 

[Hacktarux]

Hmm don't hear doom, he fails to understand that pj64 don't check roms even if i know that he'll answer in a minute to say it does...

mupen64 is checking every single bits of your rom when you use the audit option, it'll take time (not that much actually but still) but it's the only way to be sure...

 

[Clements]

Thanks Hacktarux. It works great!

 

[Doomulation]

Hmm don't hear doom, he fails to understand that pj64 don't check roms even if i know that he'll answer in a minute to say it does...

mupen64 is checking every single bits of your rom when you use the audit option, it'll take time (not that much actually but still) but it's the only way to be sure...

Haha. You're wrong here. I don't say it does. But sometimes it lists that it's not a recognized rom.
But as i said, it's not a utility to check if it's ok or not.