Snes ROM help!

Discussion in 'Nintendo Game Development' started by cataluna, Dec 27, 2006.

  1. cataluna

    cataluna Guest

    I have a prototype game for SNES that has four EPROMs on the PCB board. Since I could remove the EPROMs, I dumped the data with an EPROM programmer. Now, I have four splitted files because I had to dump each EPROM, so I wonder how you assemble the .bin-files into a single .rom file? Also, when I open each of the .bin files in Tile Layer Pro, I can see that the prototype version lacks a 16 square long string of data in the beginning of every EPROM's data. It's hard to explain, but I first thought that this maybe could be some sort of header, or missing data that (in the final version) is there to compose all the data into one file. Besides that, all the data seems to be byte-for-byte identical. Hope anyone understands what I'm trying to say.. Thankful for any help!
     
    Last edited by a moderator: Dec 27, 2006
  2. Barc0de

    Barc0de Mythical Member from Time Immemorial

    Joined:
    Oct 29, 2005
    Messages:
    11,205
    Likes Received:
    23
    ..you can use DOS command prompt to do such a thing. Try copy /b.

    EDIT: in more detail, make a BAT file containing the following:

    copy / b *.bin FILE.bin

    (make sure to name each file with .bin in the end)

    To create a BAT file, go to notepad, and type the above line. Then save the file, and rename its extension from TXT to BAT.

    Place the file in the folder containing the .bin files (and no other files to keep it clear) and run the .BAT

    EDIT2: it may be better to work with 2 files at a time. i.e: file 1+2-> fileA, then combine FileA+file3-> resulting in FileB and finally FileB+file4=> FinalFile
     
    Last edited: Dec 27, 2006
  3. cataluna

    cataluna Guest

    Ok, will try to do that. Thank you very much for the info!

    Any idea why there are these strings of data in the final and not in the prototype? They are in the beginning of each EPROM's data. Are they headers or anything? Unfortunately, I know sh*t about these things :S
     
  4. Importaku

    Importaku Import Maniac

    Joined:
    Mar 13, 2004
    Messages:
    1,265
    Likes Received:
    2
    can the snestool program help out.

    I know it has splitting & joining functions, Its worth a try.
     
  5. cataluna

    cataluna Guest

    Thanks for the help everyone!
    I've now managed to put the files together into an smc file. Still, when extracting NAPIT images from the smc file they still lack this data in the beginning in each of the four EPROM's data compared to the final version. However, the Header Checksum as well as the CRC32 are identical to the released version. Does that information mean that it is exactly the same version, even though the ROM image looks slightly different? Could someone explain this for me :)

    Thanks!
     
  6. d4s

    d4s Robust Member

    Joined:
    Jan 28, 2005
    Messages:
    287
    Likes Received:
    3
    no matter if you dumped and reassembled the rom file correctly, if the internal header checksum is the same for both your and the retail rom, you can be pretty sure that they are identical.
     
  7. MottZilla

    MottZilla Champion of the Forum

    Joined:
    Feb 1, 2006
    Messages:
    5,066
    Likes Received:
    102
    The "missing data" from the final version, is probably a copier/backup device header if you did not dump the final version yourself. Most programs will identify if a header is attached to the ROM in order to properly handle it. This also means that programs like UCON64 will report the internal ROM checksum to be good because it is.

    I think that's all it is as to why they are different. One has a copier header and the other does not as you just dumped the raw eprom data yourself.
     
sonicdude10
Draft saved Draft deleted
Insert every image as a...
  1.  0%

Share This Page