Flash forward to the day after and I got it to stay up all night long getting my stuff off of it onto another hard drive (about 20GB so it did take a while). This may or may not have something to do with pulling the bios battery (I had had similar seemingly random problems caused by dying batteries in the past). However the next day it started the whole crash thing again (though this time it was limited to the OS) so I just set it down for a few weeks since I didn't have the time to actually trouble shoot it.
The otherday I turned it on and left it shut. I set up a ping -t and then remote desktoped onto it when I went to sleep. I wake up in the morning and awesomely it's still going. I tried to use it and BAM crash. To clarify when I say crash I don't mean BSOD. It just sort of locks up and nothing moves on the screen. The pings stop getting returned and the RD gets lost. This was after about 14 hours of continuous uptime. I had even been web browsing and some other stuff via RD so it wasn't because I started using it.
Is there some inherent problem with me opening the thing up and using the track point that crashes it? I have used it both on and off battery power and it seems to of made no difference. The only thing thus far that has actually improved it seems to of been pulling the bios battery. Currently there is no bios battery still since I'd like to make sure it works before I get a new one.
Just for some spec stuff:
D-link external 802.11g card (tried removing it first)
Windows XP (dual booted with...)
Fedora core 4 (havent tried to see if it crashes in that yet)
Stock cd drive
no internal wireless
1024x768 screen
40GB stock HD
2x256mb pc133 (or whatever it uses I can't remember)
1.2 ghz PIII mobile
Oh and I changed the nub out for a cup on the track point
So what can you folks make of the situation?





