Would an inverted Sanyo monitor cause this?

disjaukifa

New member
Joined
Nov 9, 2011
Messages
2,837
Reaction score
31
Location
Ridgeway, Virginia
Hey Guys,

I got a Blasteroids that came with a Sanyo monitor that I was told had the colors inverted on the chassis itself. Here is what I'm seeing:

Parts of the game images do not display in certain portions of the screen, sometimes you see your ship, sometimes you just see your thruster, but depending on where on the screen you go depends on what you see.

Would this be caused by an incorrectly inverted monitor?

Thanks
Disjaukifa
 
pics pics pics

you know better than to post in the monitor section without posting pics.:rolleyes:


Peace
Buffett
 
pics pics pics

you know better than to post in the monitor section without posting pics.:rolleyes:


Peace
Buffett

Its not the Sanyo and I should have known that. I just took out the PCB and I took a look at the available MAME version of Blasteroids, my board is missing 4 EPROMs and it looks like I have EEPROMs on the board but I can't figure out who made them OR what model EEPROM they are so I'm like 99.999999% positive that is the issue, not the monitor!

Though I am wondering where do I adjust the horizontal position/center on a Sanyo?
 
the H-Hold is on the chassis inner right hand side.

verify the roms with the Mame set and see if they match.

Peace
Buffett
 
the H-Hold is on the chassis inner right hand side.

verify the roms with the Mame set and see if they match.

Peace
Buffett

The ones that are still on the board do but it appears I'm missing 4 actually . . . and yet the game will still turn on, its very weird.
 
The ones that are still on the board do but it appears I'm missing 4 actually . . . and yet the game will still turn on, its very weird.
Not weird if they're graphics or sound roms... As long as the code is there (and the startup test doesn't prevent the game from running because of the missing sound/gfx data) then that's all it needs to run.
 
Not weird if they're graphics or sound roms... As long as the code is there (and the startup test doesn't prevent the game from running because of the missing sound/gfx data) then that's all it needs to run.

Ok it turns out I'm not missing anything, and I can get the game to pass all the error checks so it might be the monitor . . . if the connector wasn't so different from the ones I'm use to seeing I would just do a quick monitor swap . . . arg I'll just do it tomorrow.
 
Peace
Buffett

I'll have pictures here in like 5 minutes or less! Couldn't find my camera cable! I think its the monitor now for two reasons.

1st - The game bases all the self tests AND I checked all the EPROMs on the PCB, they match perfectly with MAME.

2nd. I'm noticing stuff that should be in the foreground being in the background.

-Disjaukifa
 
Well a monitor issue certainly isn't going to cause that. You've got a logic issue with the board.

F*** . . . . wonderful . . . Its not an EPROM issue I know that. Great :(! Guess I'll be getting out the oscilloscope and actually learning how to use it now :cool:
 
Back
Top Bottom