nemesis has died

vib_ribbon

Active member
Feedback
5 (100%)
Credits
488CR
anyone know where i can find the schems for nemesis? thanks.

game plays like this with full sound... but just with blocky graphics

15849716461_8ac6e23d18_z.jpg

vib_ribbon2014-11-27 20:46:27
 

vib_ribbon

Active member
Feedback
5 (100%)
Credits
488CR
i'm looking at womble's repair log for this.

he said:
This pcb has so much different types of ram on it its crazy.

Character ram: 8 4416's
Scroll Ram: 2 6116's D22 and 25
Vram1: TC5533 @ A15 and C15
Vram2: TC5533 @ D15
Sprite: 16x 4164
Sound: 6116 @9A
Program: 6264 @17A and C and 16 A and C
Colour Ram: 6116 @ 14K and 15K

i know i'm not doing this the proper way, i'm just trying to guess what it is.
i've tried piggybacking the 4416s without success.
based on the photo posted, does anyone know what might be the likely culprit from the list above? i still have a hunch that it's a ram chip that's the cause of the problem.

oh, let me add that the game was working fine, then i turned my head and all the graphics became blocky.
vib_ribbon2014-11-27 20:47:17
 

RGP

Meeter & Greeter
Feedback
5 (100%)
Credits
2,039CR
Daft question, have you verified the ROMs on an EEPROM reader? I know the board goes through a self test but you never know how deep they go.

If the ROMs all read good then its either a RAM or a counter.

Look at the lower half of the screen and note that the K and N's bottom half are shifted right.

In fact, looking at the rest of the screen it looks like there are several fragments that are shifted by what looks like 7 or 8 character spaces.
 

shep

Active member
vacBacker
Feedback
10 (100%)
Credits
377CR
The game stays stuck on the test screen on startup if there is s RAM problem so I doubt it's that. I can tell you that this game does a thorough and proper RAM check because I have looked at the code in MAME debug mode in the past. Notice that there are no graphic ROMs on the video (bottom) board. The graphics data is transferred from the ROMs on the CPU board to the Character RAM on the video board at startup. All of the characters and sprites are then displayed from the Character RAM. Because of this you can easily end up with corruption of all graphics if something goes wrong. My guess is there is a problem displaying the graphics out of the Character RAM. That's where I would be looking.
 

vib_ribbon

Active member
Feedback
5 (100%)
Credits
488CR
I piggied all 8 character rams without any noticeable changes. Maybe time to check all the address lines? I don't think either of my ic checker or EPROM writer can verify rams though once they are pulled.
 

shep

Active member
vacBacker
Feedback
10 (100%)
Credits
377CR
Yeah I think the address lines to the Character RAM would be a good place to start. At least check the address signals generated by the graphics hardware. The address lines from the CPU to the Character RAM should be ok otherwise the RAM test would fail.
 

RGP

Meeter & Greeter
Feedback
5 (100%)
Credits
2,039CR
I'm going with a counting or buffer issue here now i've seen that picture, I reckon the address lines from the graphics hardware will be ok at least upto the buffer between them and the main CPU lines.

If we assume that the addressing from CPU to character ram is ok and passing then we can also assume the data bus going back to the CPU is fine.

So either character ram to graphics or graphics to the multiplexer (assuming there is one) to get the layer priorities right - and given the problem is across object, playfield and text i'd say its going to be buried somewhere in the former.
 
Top