Posts: 384
Threads: 18
Joined: Sep 2010
Quote:
Someone asked aboout s/n. It is: 2840A87206 with USA printed to left of s/n.
That's the package reduced vintage with the former
memory-use only r2d2 integrated in the cpu. I don't
have one here but I'd speculate the external ISA bus
still carries all activity. You could scope it to
see if the cpu is executing bus cycles coming out of
sleep. It should fall back into sleep (after a few
seconds IIRC) where bus activity is quiesced, notably
the bus clocks are idled.
The R2D2 has AFAICT a separate RC oscillator which clocks
the display drive scan. So if you are seeing random junk
on the display it could be the cpu hasn't set the display
registers to a known state coming out of sleep/power-up and
it is just rendering random power up data.
I'd still take a look at the LC oscillator and verify
that is stable. Other issues I've noticed is a stuck
key on the same row as the on key can cause startup
problems (f/g/sto/rcl). Although in that case the
firmware bails on power-up and shouldn't cause the
failure you've described.
Don't discount physical damage in terms of an open
lqfp package to pcb trace. I've seen some marginal
reflow solder jobs on voyagers that I'd never expect
to be associated with the name HP. So it could be
an intermittent (or a contamination short).
Quote:
How about using a previous cure all before power up/down became so popular--several blows with a hammer?
Resist the temptation. If all attempts at resurrection
fail someone will still buy it from you on EEEbay for
a price which will leave you with an incredible story to
tell.