brissmas said:wat file in the patch do i use to arm9 patch after unpacking?
cory1492 said:Long way to go for a 2 byte change... again, if you can use a hex editor you could just...
@ 0x100B3E on a clean dump change
00100B30 1C 26 56 43 13 AA 12 78 00 90 01 91 03 92 11 9A
to
00100B30 1C 26 56 43 13 AA 12 78 00 90 01 91 03 92 32 22
Without any unpacking/repacking/swapping tricks. Trim after, if you like (or wait for a cheat code which will do the same thing.)
Gigen said:Should i be worried about something since i replaced both arm7 and arm9?!?! (it works fine though)
The offset is on the clean rom, not the unpacked arm9, so yeah it's easier. An xdelta for a 2 byte patch would also have no questionably legal content in it like the current xdelta (v2 still has a replacement arm7 in it, which from what I saw also causes some stuttering ingame meaning unpacking both and swapping back to the original arm7 whilst praying ndstool is aligning things properly for cards that don't need arm7 replaced.)corf said:Its not really easier than using .bat cause you have to unpack, hex edit and repack. I dont think thats easier than running a single .bat filecory1492 said:Long way to go for a 2 byte change... again, if you can use a hex editor you could just...
@ 0x100B3E on a clean dump change
00100B30 1C 26 56 43 13 AA 12 78 00 90 01 91 03 92 11 9A
to
00100B30 1C 26 56 43 13 AA 12 78 00 90 01 91 03 92 32 22
Without any unpacking/repacking/swapping tricks. Trim after, if you like (or wait for a cheat code which will do the same thing.)
Is this any different to just the arm9 file replacement?
Nope, aside from the fact the ROM doesn't have to be rebuilt (which there is room for error as ndstool doesn't always conform to putting things back in their original places.)
QUOTE(iNFiNiTY @ Mar 14 2009, 08:16 PM)
Phazonsk said:When I execute the bat it makes a 0kb rom. Any idea what went wrong?