On Mon, 12 Jan 2004 13:22:00 -0800, you wrote:
>well, it's broke then. Something - perhaps a data buffer, etc is just not
>happy....lots of help, eh?
That was my thought as well. :)
Al -- if you have access to a schematic (or you're really good at
following PCB traces!), work your way back from the video RAMs to the CPU,
and forward from the RAMs to the end of the video chain. _Something_ --
very likely a buffer chip, as John suggests -- either has a stuck output
that's not changing state in response to the inputs, a "floating" input
that's causing the output to trigger randomly, or it has two or more
inputs/outputs shorted together.
This is the point at which a dual-trace scope and a logic probe come in
_really_ handy. :)
-----------------------------------------------------------------------------
A: Because it reverses the natural flow of conversation.
Q: Why is top-posting bad?
-----------------------------------------------------------------------------
solarfox@DON'TMESSWITHtexas.net (Gary Akins jr.)
http://lonestar.texas.net/~solarfox
-----------------------------------------------------------------------------
---------------------------------------------------------------------------
** Unsubscribe, subscribe, or view the archives at http://www.vectorlist.org
** Please direct other questions, comments, or problems to chris@westnet.com
Received on Mon Jan 12 19:58:19 2004
This archive was generated by hypermail 2.1.8 : Thu Jan 15 2004 - 11:50:01 EST