[Tfug] t60 motherboard..

[Bexley Hall]

Hi Jeremy,

> > To be clear:  you spilled something on/in it?
> > Have you let it dry out *thoroughly*?
> > are you sure your problem is MB and not just the
> > *keyboard*, etc?  (i.e. try an external keyboard)
> 
> Ya, I actually consider myself something of an expert in
> this now. I

Um, I don't think that's something you want ot be PROUD of!  :>

> poured a solid 12 oz of coffee through the keyboard about a
> year ago. I immediately pulled the cord and battery, took 
> all the insides out and dried/cleaned them, waited a day,
> fired it up and had not a single problem.
> 
> However, this time was different. I was traveling and had
> it on the floor of the room I was staying in. It was on, but
> suspended to ram when I went to sleep, and strangely off 
> when I woke up.  When I picked it up, water oozed out from
> various points.

WTF?  Was the "water" YELLOW, by any chance??  ;-)
(I am at a lss to figure out how this could have
happened, otherwise!  A leaky roof during a rainstorm?)

> I still had high hopes and have been drying for a week. I even
> when so far as to *warm* up the oven, let it cool to about
> 120/130 degrees and put the frame and MB in
> as it slowly cooled to room temp over night, but it still
> twitches when I turn it on. No POST, no bios of any kind.
> It cycles the fan and various leds once and then sits there 
> making a sort of faint high pitched wine.

Well, *something* is running enough to turn the lamps on and
then off!

> I have removed ram, disk, and pretty much everything
> else, so it's either the MB or the actual CPU, but I doubt
> that.

Have you tried throwing another (good) disk into it (and
ram, etc.) just to see if the disk spins up?  Does it have
a floppy drive?  Or, can you add anything USB external as a boot
device (CDROM) just to see if it is *trying* to do anything?
Also try an external keyboard.  Point here is to see if
you can get *any* signs of life from it so you can decide what
other lifesigns might be hiding...

> I'm annoyed, because I think I could have saved it if I had
> known it happened right away.

Shit Happens.
 
> I guess I can add it to the list of things that went wrong
> on the trip:  shuttle to the wrong rental car company,
> simultaneous dying of batteries on the phone and laptop during 
> the last mile of navigation to the destination, and hit-and-run
> smashed rental car the morning I was returning to the airport.

Yikes!  Note to self:  *never* go THERE!  ;-)

> And now a dead laptop.  But aside from
> that, it was a fantastic trip. :-)

Ah, well... just a bit more expensive than you had planned!