Hacking *~Auto Injectuwad Injector~* -kept updated-

[Nightstalker]

no offense at all, but it couldn't possibly be any more self explanatory

well something must be wrong with me then, care to explain it for me?

I tried to make Auto Injectuwad Injector as user friendly as possible.

What do you need help with specifically?

 

[JJBro1]

no offense at all, but it couldn't possibly be any more self explanatory

well something must be wrong with me then, care to explain it for me?

I tried to make Auto Injectuwad Injector as user friendly as possible.

What do you need help with specifically?

how do i pick a rom? Where do i go to fetch my rom?

 

[Arakon]

no offense at all, but it couldn't possibly be any more self explanatory

well something must be wrong with me then, care to explain it for me?

I tried to make Auto Injectuwad Injector as user friendly as possible.

What do you need help with specifically?

how do i pick a rom? Where do i go to fetch my rom?

it's called "clicking". you utilize the "mouse" device for that.

 

[creffca]

no offense at all, but it couldn't possibly be any more self explanatory

well something must be wrong with me then, care to explain it for me?

I tried to make Auto Injectuwad Injector as user friendly as possible.

What do you need help with specifically?

how do i pick a rom? Where do i go to fetch my rom?

-Find common-key.bin somewhere on teh interweb
-Put the host wad and rom in the same folder as auto injectuwad
-Make sure the files names do not have spaces

 

[JJBro1]

no offense at all, but it couldn't possibly be any more self explanatory

well something must be wrong with me then, care to explain it for me?

I tried to make Auto Injectuwad Injector as user friendly as possible.

What do you need help with specifically?

how do i pick a rom? Where do i go to fetch my rom?

it's called "clicking". you utilize the "mouse" device for that.

ya i click on pick rom and i get this dotted rectangle and nothing happens.

 

[creffca]

Your roms will appear in the list box after you've chosen a console mode.

 

[JJBro1]

ok all i need is the common key.bin, where do i get that?

 

[teq]

I usually hate coming to a new board and immediately begin asking for things, but I'll do so anyway:

I've been playing around with rom injection for a while now, mostly trying to get games that don't work properly to work, but before I can continue doing this, I have to fix the ones I've already installed.

That is, I mistakenly thought the wad uninstallation process wouldn't require the wads and deleted them. Since then, I've decided to log everything by the rom I inject, what I inject it into, and the custom titleid I used.

My understanding of the injector is that if it gives wads a random title id, it'll be 3 digits instead of 4.

Is this always true, or does it sometimes use 4 digits?

If not, what is used to pad the last digit of the title id?

 

[teq]

ok all i need is the common key.bin, where do i get that?

Google it or look on a torrent search engine.

 

[hemanthegreat]

I usually hate coming to a new board and immediately begin asking for things, but I'll do so anyway:

I've been playing around with rom injection for a while now, mostly trying to get games that don't work properly to work, but before I can continue doing this, I have to fix the ones I've already installed.

That is, I mistakenly thought the wad uninstallation process wouldn't require the wads and deleted them. Since then, I've decided to log everything by the rom I inject, what I inject it into, and the custom titleid I used.

My understanding of the injector is that if it gives wads a random title id, it'll be 3 digits instead of 4.

Is this always true, or does it sometimes use 4 digits?

If not, what is used to pad the last digit of the title id?

It always creates a four-letter code as far as I know. N = N64 games, F = NES games. The other 3 letters are random if that is the option you have set in the .ini

I just posted a short guide on how to fix this very issue you are having, as I had the same problem (never again will I delete the wad until I uninstall it >.>) http://gbatemp.net/index.php?showtopic=86252 It was obvious once I realized it, but I had to spend a few days acutally looking at it and thinking haha.

 

[teq]

It always creates a four-letter code as far as I know. N = N64 games, F = NES games. The other 3 letters are random if that is the option you have set in the .ini

I just posted a short guide on how to fix this very issue you are having, as I had the same problem (never again will I delete the wad until I uninstall it >.>) http://gbatemp.net/index.php?showtopic=86252 It was obvious once I realized it, but I had to spend a few days acutally looking at it and thinking haha.

Sadly, I deleted a few channels to free up space, so I have to use Title Lister.


I have a few title ids that are ".XXX" (period and three random letters). Title Lister luckily also lists the IOS version and both title ids are IOS33, which is used with Sin and Punishment.

Am I on to something or do these title ids belong to something else?

 

[hemanthegreat]

It always creates a four-letter code as far as I know. N = N64 games, F = NES games. The other 3 letters are random if that is the option you have set in the .ini

I just posted a short guide on how to fix this very issue you are having, as I had the same problem (never again will I delete the wad until I uninstall it >.>) http://gbatemp.net/index.php?showtopic=86252 It was obvious once I realized it, but I had to spend a few days acutally looking at it and thinking haha.

Sadly, I deleted a few channels to free up space, so I have to use Title Lister.


I have a few title ids that are ".XXX" (period and three random letters). Title Lister luckily also lists the IOS version and both title ids are IOS33, which is used with Sin and Punishment.

Am I on to something or do these title ids belong to something else?

That I don't know about, my understanding was that there were hex values that represented the tickets, but I don't know about anything else representing those same tickets. I'll try and play around with it and see what I can find, if anything.

 

[Kazuma77]

creffca, you need testers, I'm here. Put it up and I'll try it. BTW, tested with TG16 and SNES now, the wads come out the same, I can take out the 64 bytes and Terranigma really seems to want to work (locks up after naming my character and showing that Chapter I text. I really thought it would work as mine's had the protection removed for my SWC DX2 already). Oh well.

All Turbografx injections failed, not with the initial 4100 (I haven't seen that one since I started manually cleaning up the .wad files), the one that occurs after the initial OK that tells you the ROM's most likely messed up. So, what format do these need to be in? MSG straight copies as contained in the GoodPCE set should work I would think, but maybe I should try scrambling them since that's technically how the US TG works, what I think I need is a genuine PC Engine wad so I can just inject them as is. Also, I tried injecting Order of the Griffin into both Bomberman 93 and R-Type. The ROMs are the same size. I should not be getting an error saying the file is too big. Unless ... I need to strip headers or something.

I was surprised to read the VC doesn't do SMD (and I'm surprised that's an interlaced format, the SWC DX2 and SMG provide normal byte-for-byte copies so it doesn't make sense that FFE went with interlaced on the SMD, and since my DPF uses .SMD, this is not good, means keeping an extra copy of the set in a different format, oh well).

I noticed something odd. The resulting wad from injecting into Toejam and Earl 2 yields a completely different set of bytes at the beginning of the wad file than is normal. The 0Ds aren't even in the same place (I'm not even sure I deleted the right ones that time, was trying to get The Immortal to work and was getting nothing but a red screen from Comix Zone, so I decided to try a newer Genesis release, in hopes that compatibility had improved).

I still haven't tried N64 injection. I know better than to try. I own the backup units, I know what it took to get them working on those. I'm sure they coded the emulators to be boot chip (and most likely save RAM type) specific as an extra protection measure. i. e. you inject a rom into Zelda, if it isn't also using a 6105 boot chip it's going to fail. You could try patching the boot chip in the ROM itself, but that never worked on the backup units so it's unlikely to work here either (now, if you could attach a copy of Lac's Bootemu patched to work with the corresponding chip to the ROM before injecting it, you could get around this). Oh and, there's exactly one game you could get away with injecting Banjo Tooie into and have a snowball's chance in hell of it working -- and it's even less likely they'll put out Conker's Bad Fur Day than Banjo Tooie (trust me, Conker is the only boot cart aside from Banjo Tooie itself you can use with the game, fortunately I chose well and picked up an extra Conker cart for use with the double eeprom games on my V64 Jr, unlike the Z64, which likes the "standard" 6102, it seems to prefer working with 6105 boot carts, which is why you have to use Jet Force Gemini to save flash games instead of C&C).

 

[creffca]

Lots of good stuff.

Awesome, pm sent. I'm hoping you can poke around in the resulting wad with a hex editor for clues as to what went wrong.

 

[Kazuma77]

Just tried your test fix. Had missed the PM from before. Well, it seems to work correctly. I just had it inject Shingen The Ruler into Kirby's Adventure (NES). It installed and ran perfectly. So far, so good. Very informative output while it's doing it as well.

CODEWARNING: Incorrect wad detected, please wait while correcting...
Correcting: 0%...
Correcting: 7.99017%...
Correcting: 15.9803%...
Correcting: 23.9705%...
Correcting: 31.9607%...
Correcting: 39.9508%...
Correcting: 47.941%...
Correcting: 55.9312%...
Correcting: 63.9213%...
Correcting: 71.9115%...
Correcting: 79.9017%...
Correcting: 87.8919%...
Correcting: 95.882%...
Correcting: 100%!
1 file(s) copied.
1 file(s) copied.

 

[creffca]

I've sent you two pm's now. Version 3.2b and 3.3b I believe. The latter has a better algorithm.

 

[Kazuma77]

I see, well, what can I say, you've apparently fixed it, I updated my previous post with a copy of the displayed output so you could see how it looks. The word WARNING is actually in yellow in the original DOS box. So, it seems to be doing everything right so far.

 

[creffca]

I think NES roms are fixed. Other systems still seem to fail with other testers.

EDIT: Are you able to manually correct snes wads etc... using the same correction method you use?

 

[teq]

Creffca, I was curious as to the formatting of the Title IDs when they're assigned randomly.


I've injected a few N64 roms with a random Title ID and on my Title Lister, there are some titles with a period. They show up as ".XXX", where X is the random title.

Are these the result of the random title algorithm and is this consistent for all 3 digit title ids?

 

[Kazuma77]

Seems to work on them all, I got Phantasy Star 2 working, but since I used Comix Zone, it couldn't save, maybe now an option for injecting into Genesis wads with SRAM is needed. Injecting into Sonic 3 fails even after it's cleaned up. And that seems to be the largest game with save RAM that's out. Terranigma tried to run. It did lock up, but I think it may be a PAL formatting thing, I killed the protection, it works on an SWC DX2.