Asure
Grand Master
Just to check: Are you using /p for load2?
During my toilet break i had the same idea, i had used this ***> before to set up the start of entries for bldctl in IMGTBL.ASM and see where it would align.
And offcourse, we have the original IRW right? We could determine the start of MUG1 from the IMG container, check in the ROBOY.IRW and figure it out from there.
My main thoughts were, what is up with V5.00 being in the root and V8 being in the backup folders.
V5 looks like some wierd in-between version but still seems to want V8 GFX roms.
Why multiple LOD files (It seems they built at least ROBO and ROBOY lod files since the IRW's are there.)
4.50 4/27/90 is the header for the version of load.exe we are missing.
03/14/95 is load2.exe version we're using.
If i search for 28 38 12 12 (0x11B in MUTEXP.IMG) in the IRW we built, it's at 0x4D in my roboy.irw
I guess that's MUG1 data.
If i check for this in the original, there's something else there i didn't yet recognize. Also 28 38 12 12 did not appear in the original IRW.
Maybe different encoding for the DMA2 platform?
Looking at the IMGTBL.ASM generated with the new parameters, i see it going wrong at PHEAD8
OLD .long 02124560
NEW.long 021225e0 (+0x70)
(And everything is fudged after this offcourse.)
Blueguy and fingrnt are right after that. I tried forcing the adress at this point in the LOD but it didn't care and still wrote a broke .asm file.
Fon150
OLD 02193E40H
NEW 02192560H (0x18E0 short)
Arrow12
OLD 0213A980H
NEW 0213a300H (0x680 short)
Looking forward to your reverse engineering thoughts and calculations
Edit: More RE'ing ASM..
During my toilet break i had the same idea, i had used this ***> before to set up the start of entries for bldctl in IMGTBL.ASM and see where it would align.
And offcourse, we have the original IRW right? We could determine the start of MUG1 from the IMG container, check in the ROBOY.IRW and figure it out from there.
My main thoughts were, what is up with V5.00 being in the root and V8 being in the backup folders.
V5 looks like some wierd in-between version but still seems to want V8 GFX roms.
Why multiple LOD files (It seems they built at least ROBO and ROBOY lod files since the IRW's are there.)
4.50 4/27/90 is the header for the version of load.exe we are missing.
03/14/95 is load2.exe version we're using.
If i search for 28 38 12 12 (0x11B in MUTEXP.IMG) in the IRW we built, it's at 0x4D in my roboy.irw
I guess that's MUG1 data.
If i check for this in the original, there's something else there i didn't yet recognize. Also 28 38 12 12 did not appear in the original IRW.
Maybe different encoding for the DMA2 platform?
Looking at the IMGTBL.ASM generated with the new parameters, i see it going wrong at PHEAD8
OLD .long 02124560
NEW.long 021225e0 (+0x70)
(And everything is fudged after this offcourse.)
Blueguy and fingrnt are right after that. I tried forcing the adress at this point in the LOD but it didn't care and still wrote a broke .asm file.
Fon150
OLD 02193E40H
NEW 02192560H (0x18E0 short)
Arrow12
OLD 0213A980H
NEW 0213a300H (0x680 short)
Looking forward to your reverse engineering thoughts and calculations

Edit: More RE'ing ASM..
Last edited: