Arcade Rom Patcher (V15)
- Thread starter GadgetFreak
- Start date
GadgetFreak
Active member
It isFlinnster said:Damn, I thought there was a version update!
I just updated the first post and the title
yorkshire_spam
Active member
- Credits
- 763CR
Awesome work on the Atari System 1 stuff.
GadgetFreak
Active member
It's a standard WinRAR V5.70 64 bit created file, works fine on a Windoze PC.
BTW The app is a windows app so you would need to use Parallels or something simliar.
BTW The app is a windows app so you would need to use Parallels or something simliar.
Hello,
I found my way from the "arcade-projects" forums.
I've been trying to fix some graphic issues with a Magic Sword PCB. I ran the patch program against the ROMs I dumped on the board, and burned the files produced. When I booted the game up with a B-21 based "C" board I got a scroll ram error.
Complete details are here:
https://www.arcade-projects.com/threads/magic-sword-completely-missing-text.17658/
The patch program seems very straightforward to use, but am I doing something wrong?
duffcon2021-06-30 22:19:41
I found my way from the "arcade-projects" forums.
I've been trying to fix some graphic issues with a Magic Sword PCB. I ran the patch program against the ROMs I dumped on the board, and burned the files produced. When I booted the game up with a B-21 based "C" board I got a scroll ram error.
Complete details are here:
https://www.arcade-projects.com/threads/magic-sword-completely-missing-text.17658/
The patch program seems very straightforward to use, but am I doing something wrong?
duffcon2021-06-30 22:19:41
duffcon said:
What happens when you put the old c board and original roms back in ?? The c board wont cause a ram error (as far as i am aware). There may be a rsm error causing your graphical issues.
Have you tried a good known working A board ?? Make sure voltages are good as these boards can get cranky.
Dave.
P.s there is a new members post page , so you can say hello and introduce yourself. Not mandatory though.
Hello, with the original roms and C board the system boots up fine. It's missing a lot of the text elements, top and bottom status bars, basically just the character sprites in the middle of the screen.
I suspect the A board is faulty as well. If I test it with a known good SFII b+c boards there are graphical issues. However it also boots fine.
With another good A board, the graphic issues remain the same, so I suspect the B or C boards.
I suspect the A board is faulty as well. If I test it with a known good SFII b+c boards there are graphical issues. However it also boots fine.
With another good A board, the graphic issues remain the same, so I suspect the B or C boards.
If i get chance i will have a look tomorrow. Its very easy to patch the roms and providing you have burnt the correct roms any C board can be used. I would think it has to be the roms you have burnt. You tried it with converted roms and original C board ??
Dave.
Dave.
I believe I have tried with patched roms and original C board and it didn't boot at all. I'll give it another try. Based on MAME my rom set is
ms30.bin = msu_30.11f mswordu Magic Sword: Heroic Fantasy (USA 900725)
ms35.bin = msu_35.11h mswordu Magic Sword: Heroic Fantasy (USA 900725)
This was identified as 'mswordu' by the rompatcher.
I'll try the patched roms with original C board and start my own thread in the technical thread(?) Thanks for the help
ms30.bin = msu_30.11f mswordu Magic Sword: Heroic Fantasy (USA 900725)
ms35.bin = msu_35.11h mswordu Magic Sword: Heroic Fantasy (USA 900725)
This was identified as 'mswordu' by the rompatcher.
I'll try the patched roms with original C board and start my own thread in the technical thread(?) Thanks for the help
GadgetFreak
Active member
I presumne you did have the De-Protect box ticked and the CustomB NOT ticked when you patched?
If so then the patched roms would work with any C board for certain.
Was the board originally a Magic Sword?
Was it the same version? As a lot of the games/versions do not all do the full start up tests on ram etc.
The pachter could not cause a ram test failure. It is possible that rom speed could be a factor, certainly with Strider the rom speed makes a big difference. On my Strider I had to use -85's.
If so then the patched roms would work with any C board for certain.
Was the board originally a Magic Sword?
Was it the same version? As a lot of the games/versions do not all do the full start up tests on ram etc.
The pachter could not cause a ram test failure. It is possible that rom speed could be a factor, certainly with Strider the rom speed makes a big difference. On my Strider I had to use -85's.
Yes, I clicked "de-protect"
Board is a factory Magic Sword for sure
Mame romident says it was a mswordu Magic Sword: Heroic Fantasy (USA 900725)
which the patcher also agreed to.
The rom type is questionable. I asked in the other forums. The original chips are HN27C301G-20 the replacement is MX27C1000DC-15 which according to:
https://wiki.arcadeotaku.com/w/EPROM
May not be right; similar B boards (final fight) use 27c010 chips which apparently are a different pin out. I'll get some 27c010 and find out.
Board is a factory Magic Sword for sure
Mame romident says it was a mswordu Magic Sword: Heroic Fantasy (USA 900725)
which the patcher also agreed to.
The rom type is questionable. I asked in the other forums. The original chips are HN27C301G-20 the replacement is MX27C1000DC-15 which according to:
https://wiki.arcadeotaku.com/w/EPROM
May not be right; similar B boards (final fight) use 27c010 chips which apparently are a different pin out. I'll get some 27c010 and find out.
GadgetFreak
Active member
If the originals were 301's then 1000's should be correct.
I did just reply on KLOV where I also mention an issue that a few people have had when trying to patch roms on their Windows C drive. There is some kind of protection setting in Windows that can cause issues depending on your windows settings. To be sure I would make sure the folder with the roms files in is on a D drive is you have one. Also you are burning the '.patched' file that the ARP creates?
I did just reply on KLOV where I also mention an issue that a few people have had when trying to patch roms on their Windows C drive. There is some kind of protection setting in Windows that can cause issues depending on your windows settings. To be sure I would make sure the folder with the roms files in is on a D drive is you have one. Also you are burning the '.patched' file that the ARP creates?
Like most other releases Japan is non-JEDEC vs world/us which are a different B board. A JAPAN board should use 27c100 for program roms while WORLD/US should use 27c010.
World/us board: https://www.mvs-scans.com/index.php/CPS1_-_B_Board_89624B-3
Japan board: https://www.mvs-scans.com/index.php/CPS1_-_B_Board_89625B-1
World/us board: https://www.mvs-scans.com/index.php/CPS1_-_B_Board_89624B-3
Japan board: https://www.mvs-scans.com/index.php/CPS1_-_B_Board_89625B-1
Here's something I just noticed. So at 18,19,31,&36 I have 27c301 (hitachi). At 30 I have M5M27c100k (mitsubishi) an at 35 I have D27C1000D (NEC)
My 2 chips I have tried are as follows:
MX27C1000DC (Macronix) & NM27C010Q (National Semi). I based this choice on the Final Fight board pictured in the A board thread having AM27C010
What stands out to me is that the Output enable is on pin 2 on the original chips, but is on pin 24 on my selections. Could this be the cause?
*edit based on your info I looked at the link and it looks like my chips are non-JEDEC, and I bought JEDEC chips
I bought some 27c301 hitachi chips to try.
My 2 chips I have tried are as follows:
MX27C1000DC (Macronix) & NM27C010Q (National Semi). I based this choice on the Final Fight board pictured in the A board thread having AM27C010
What stands out to me is that the Output enable is on pin 2 on the original chips, but is on pin 24 on my selections. Could this be the cause?
*edit based on your info I looked at the link and it looks like my chips are non-JEDEC, and I bought JEDEC chips
I bought some 27c301 hitachi chips to try.