|
Title: Checking code on EPROMS Post by: lacerta1974 on May 15, 2014, 06:11:33 pm I've watched the video's John has posted about reading eproms and comparing that with romident. I'm working on a 10 pin deluxe arcade. I found roms on coolroms and used those to test against romident to make sure it would find them in the database of roms. So then I started reading the eproms from my 10 pin deluxe board and then saved the bin files and when I check against romident it isn't finding any matches. As I understand it that would mean that the code on the chips is bad? Or could it also be that the rom itself is bad? I was also wondering about the eproms from this game. They are Intel D2763-3. On klov I read that it was ok to read these using the gc-4x reader device setting of 2764. If I need to buy replacement roms to write too do I have to stick with D2763's or can I buy 2764's? The 2764's look more readily available.
Thanks for any help. Title: Re: Checking code on EPROMS Post by: John's Arcade on May 15, 2014, 06:40:16 pm I've watched the video's John has posted about reading eproms and comparing that with romident. I'm working on a 10 pin deluxe arcade. I found roms on coolroms and used those to test against romident to make sure it would find them in the database of roms. So then I started reading the eproms from my 10 pin deluxe board and then saved the bin files and when I check against romident it isn't finding any matches. As I understand it that would mean that the code on the chips is bad? Or could it also be that the rom itself is bad? I was also wondering about the eproms from this game. They are Intel D2763-3. On klov I read that it was ok to read these using the gc-4x reader device setting of 2764. If I need to buy replacement roms to write too do I have to stick with D2763's or can I buy 2764's? The 2764's look more readily available. Thanks for any help. IT's possible. It's also possible that you have a version of ROMs on your game that is not in ROMIDENT. Title: Re: Checking code on EPROMS Post by: lacerta1974 on May 19, 2014, 06:43:13 pm Just as a follow up on this. Anyone know if it's acceptable to use the 2764 as a replacement for 2763 eproms?
Title: Re: Checking code on EPROMS Post by: iankellogg on May 20, 2014, 07:05:21 am from research 2763s are just factory programmed 2764s. You should be fine to replace them with 2764's.
Also if you have the roms available, you should check your eproms directly instead of using romident, as romident kind of sucks. Using the software open up the rom file you want to verify with, load that same eprom into the reader and click verify. Title: Re: Checking code on EPROMS Post by: John's Arcade on May 20, 2014, 08:44:48 am from research 2763s are just factory programmed 2764s. You should be fine to replace them with 2764's. Also if you have the roms available, you should check your eproms directly instead of using romident, as romident kind of sucks. Using the software open up the rom file you want to verify with, load that same eprom into the reader and click verify. How does it suck? I don't get that. Title: Re: Checking code on EPROMS Post by: iankellogg on May 20, 2014, 08:47:10 am I've had a few false negatives already with romident. Plus reading + saving + uploading kind of sucks compared to just loading in the rom file you want to check against. I've had far more luck verifying directly.
Title: Re: Checking code on EPROMS Post by: John's Arcade on May 20, 2014, 09:59:05 am I've had a few false negatives already with romident. Plus reading + saving + uploading kind of sucks compared to just loading in the rom file you want to check against. I've had far more luck verifying directly. There are windows versions of romident and there is a way to have it run with the emp software in DOS. Verifying directly is only good if you have a good known file and if you know what ROM you actually have. Title: Re: Checking code on EPROMS Post by: iankellogg on May 20, 2014, 10:01:23 am I think I did say that if you have the roms available to do the check directly.
|