Unknown game on Defender bootleg

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
Since coming back to UKVAC I have been frustrated by a bootleg Outrun for a while, followed by a couple of easy successes with Konami 88 and a bootleg Pengo.

While waiting for some non-JEDEC EPROMS to come in the post for my Pacmania, I bought the following unknown board from Alpha1. I was of course warned about the condition, but at least the dirt tells me that it probably hasn't been messed with since the 80s.

Before.jpg


It looked to me like Defender bootleg hardware but not the same as my Defense Command. There are pictures of a similar board online, Defence Command by Outer Limits, but with one extra ROM and buttons for Advance etc.

I started by lifting all the socketed chip as carefully as I could. Or course, many legs broke off and were left behind in sockets, but not as bad as could have been. A few hours later I had soldered on replacement legs from a donor faulty EPROM.

Next I decided it was time to dust off my trusty old Data I/O 29b, but had to clear some stuff from in front of it on the shelf first. This included my Ikari Warriors, a SFII B board I didn't know I had (is anyone producing replica C boards yet ?), and a pile of random sub boards from old bootlegs which I might upload pictures of to ID at some point. I powered up the 29b and was greeted with a beep and a flash of the screen before just fan noise alone, thats now all I get from power on. If I have problems fixing this later, I may post for help. So I'll leave reading the decoder PROMs for now and dig out an alternative programmer. Powered up the old 486 laptop, beeeep beeeep !. The perished rubber feet had glued it to the shelf so I pryed it off and cleaned up. Pulling out a faulty memory module brought it back to life, and it runs fine on 20MB.

Because ZIF sockets grip the edges of chip legs, I found I had to put some of the ROMs in a regular DIL socket first before they'd read and verify reliably. Only one would read but not verify consistently no matter what I tried, so I saved one of the resulting reads anyway.

So, the sound ROM matches Defender, no great surprise. The three ROMS with the orange labels identify as Black Beauty (Shuffle) in MAME. All the remaining ROMS are not recognised, although interestingly, these all have the same white labels as the sound ROM. The hardware doesn't seem to match Black Beauty, but all the ROMs have been in the board for about the same amount of time I'd say, they all have the same level of dirt and corrosion.

If anyone would like a copy to mess about with, please let me know, I'd be interested to know what you can find.

cliff_poole2022-04-08 13:34:54
 

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
I have figured out why the three ROMs ID as Black Beauty. Whoever dumped and uploaded these ROMs, dumped a blank image. So my ROMs with the orange labels are all blank. We may never know what this board was
smiley6.gif
.

I'll carry on with putting it back together anyway. I guess I could burn a set of Defence command ROMs but it seems a shame to do that, I'll leave it as it is and add it as another unknown to my database.
 

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
It is now back together in one piece. My question is, does anyone either recognise this board, or know of a Defender hardware game, with Defender sounds, which uses only 7 * 2K ROMs, and does not utilise the Advance etc. Push buttons ?.

Complete.jpg
 

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
Thanks, that's very interesting.

I got hold of the Mayday ROMs and all the images are 4K. My PCB is silkscreened with 2716 under all the sockets but the markings on the chips are all worn off. I'll try to re-read them all as 2732s and see what I get. One of my existing images does contain the text "drone", so it seems likely.
 

cliff_poole

Active member
vacBacker
Feedback
6 (100%)
Credits
1,069CR
Since I fixed my programmer yesterday, I have managed to burn some new ROMs

It powers up with a yellow screen and constant reset. The main processor isn't outputting any addresses.

At this point I dug out my 6809 Fluke pod. This is unusual in that it has an external processor socket so it can be switched between 6809 6809E variants that are quite different.

Plugging the Mayday processor into the pod and running the self test gives me a pod connection error, so the chip is faulty.

I next plugged the pod into the PCB. Bus test passes. Short RAM test ran for a while before failing at various addresses. The fluke gives you the option to loop the test when it encounters a read back error. When I put the test into a loop, sometimes it passes and sometimes it fails. There is a short beep with each read error, so you can imagine an erratic beeping.

Remembering a recent post regarding turning down the supply voltage, I gave it a go. As I slowly wound it down, the beeping got slower (more test passes). At 4.4V it the beeping stopped, every loop of the test passes. Continuing the tests of course fails further down the line and RUN UUT doesn't work.

I am going to shelve this for now. One day I'll buy a bulk load of 16pin sockets and desolder all the 4116s.
 
Top