So it's not the RAM...
Apr. 21st, 2003 07:24 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
annuinThe RAM arrived this afternoon, two days ealier than I'd expected. Because I had little desire to wait all day until ![[livejournal.com profile]](https://www.dreamwidth.org/img/external/lj-userinfo.gif)
prez came home, and because he had taken his laptop with him and left me computerless, I called him and got him to walk me through installing the RAM myself.
That part was successful. Bringing the computer back to life wasn't. So, it's not the RAM (though my old RAM didn't work inprez's computer either). By putting one of prez's CPU's into my system we've determined it's not the CPU and I probably have a fried motherboard. Whoop-de-fucking-doo.
prez came home, and because he had taken his laptop with him and left me computerless, I called him and got him to walk me through installing the RAM myself.That part was successful. Bringing the computer back to life wasn't. So, it's not the RAM (though my old RAM didn't work in
prez's computer either). By putting one of prez's CPU's into my system we've determined it's not the CPU and I probably have a fried motherboard. Whoop-de-fucking-doo.