M__ hollered at me Christmas day; her computer was broken. With the power problems we had that morning, I really wasn't surprised: surge protectors aren't foolproof.
So I run over and take a look. Sure enough; it was just as she described it to me: press the power button, the light would come on, but nothing happened. Great. Best case, the power supply's borked; worst case, the whole box is fried. I brace her for the worst, and told her I'd take a look at it Saturday morning. To tide her over; I hooked her up with a replacement rig: my new laptop won't win any speed awards, but hook her monitor and mouse up and it's a serviceable email kiosk. No, this isn't something I'd normally do, but M__ is a good customer.
I get this thing to my makeshift workshop and hook it up to a spare mouse and monitor (and power cord, just in case) of mine. No surprise, still didn't work. Was worth a shot, though; a power cord is a lot less expensive than a new computer.
I shut'er down, crack open the case, and get to troubleshooting. All the connections are good, and nothing looks scorched off hand. Power supply is cheaper than a new box, so I hit the test button. Nothing. Now, this power supply is supposed to spin the case fans when you hit the test; but all I get is a twitch and a green LED.
I don't have any spare power supplies on hand, but I had just replaced the power supply in my own desktop. Normally, no problem; hop on New Egg, pick up the part, wait a couple days. I give M__ a call, see what she wants to do. And for some reason, I offered to just leave in my power supply at replacement cost. Normally, I wouldn't have even thought about putting parts from my own PC in a customer's computer, but like I said, M__ is a good customer: she's already shopping for a new computer with me. And since I have the laptop, there's nothing on the desktop I actually need for a while. So, she's up and running, I've got my laptop back. And I've got a customer who knows I'll go the extra mile.
Monday, December 28, 2009
Tuesday, December 22, 2009
New Comp
Picked up a free laptop this weekend. It cost me bout $125.
Yeah, i know. Sounds like a contradiction, right? But when something is "free", there's always a catch. The laptop itself was crap. And I don't say that lightly. The guy who sold it to me told me it was crap.
So, the rundown... Lappy's an Acer TravelMate 2420, with an Intel Celeron D 1.5GHz, 512 MB RAM, 20 GB Hard Drive, 14.1" screen, DVD-ROM/CD-RW, WiFi, Bluetooth, USBx3, Modem, LAN, PCCard (Type II), VGA out.
Anyway, this thing has never been a "top-of-the-line", and frankly, never will be. That Celeron is just powerful enough to run XP (what it originally came with); 7 isn't in the realm of possibility.
If it was, I wouldn't have gotten it so cheap. Of course, I wouldn't have gotten it so cheap if it weren't DOA anyway.
I can already here you asking, "Wait, if you knew that the laptop wouldn't work, why in the world would you spend money on it?" And I would reply, I never said the laptop wouldn't work, it didn't work. And while I wouldn't go so far as to compare myself to mechanic rebuilding an engine, the basic idea is the same. I take the shell of a computer, salvage what I can, replace what I can't, and wind up with something I can use, give away, or sell. Usually the first.
Before that mechanic begins his rebuild, he figures out the problems, decides if it would be worth the work, then makes a plan, including contingencies in case something new crops up. And like our imaginary mechanic, I did the same thing.
What Was Wrong
The damn thing wouldn't start.
I've ran into the same trouble with my car enough times, I think I'm drawn to things that don't want to get going in the mornings (something, something, wife, something... love you, honey). Of course, just like a car, there are dozens of reasons why a computer won't start. The diagnostic screen wasn't much help at first: some esoteric (read: I didn't recognize them at first) error codes and the dreaded "Operating System Not Found" message. That isn't good. It's the equivalent of getting into the car, putting your key in the switch and the car looking back at you and saying "Where's my power train? I can't find my power train!"
Yeah, that's not a Good Thing™.
So, first things first; I googled the error codes, and found out they were network boot errors. "Network boot" is way of starting the computer where the operating system is hosted on the network instead of on the computer itself. So, into the BIOS we go.
This is where I found part of the problem. The BIOS (Basic Input/Output System) was able to notice the hard drive, but wasn't able to identify it. Modern BIOSes are able to read the serial number from drives, and they display it. In a desktop computer, this can be a useful tool when you have multiple hard drives. This laptop was able to grab the basic manufacturer information from the drive, but not the serial number. Just to be on the safe side, I double-checked the boot order: Optical drive, Hard Drive, Network, Floppy. Pretty standard; and pretty much what I expected -- the previous owner was your typical computer user: he isn't one to poke and prod too much; and I knew the other guy he took it to would more than likely return things to base if he couldn't find the cause.
That concerned me a bit... since we were polling the Hard Drive before searching for a Network, the fact that we got the network connection errors were a problem, but not totally unexpected: the previous owner had reported having some corruption issues. I popped open the case, made sure that the memory and hard drive were properly seated -- always a concern when looking at a laptop. I reseated both, and no change. Again, it wasn't a surprise; but double- and triple-checking the simple stuff can save time, money, hassle, and face-palming on a job.
Since I knew the hard drive wasn't accessible at the moment, I went to the next option:
booting from CD.
Luckily, quite a few Linux Distributions have what's called a "Live-CD". Live-CDs are complete operating systems contained on a CD (or in some cases, a DVD). A Live-CD is used to demonstrate the OS or just test hardware for compatibility before actually installing. Booting a live environment is also useful for providing a way to get into an otherwise unaccessible computer (assuming there's no encryption).
Because LiveCDs run completely in RAM, I went ahead and grabbed a memory upgrade; luckily, previous owner had already bought an upgrade. I bought the two 1GB sticks off of him, along with a soft-side carrying case for $50. Sans laptop, he wasn't going to need it, but I gave him fair market for the upgrade anyway.
I fire up a CD called MacPuppy Opera. This particular distro is a variant of Puppy Linux; and one of the major selling points of Puppy is that it has a complete graphic environment, loads completely into RAM, and has the underlying tools to work with a broken computer.
So, I fire up gparted (GNOME Partition Editor) and ask it about the hard drive. It does find it, but like the BIOS, it couldn't actually access it. Seems it needs a disklabel. Unfortunately, I can't seem to create one. Block 0 is unwritable. Crap.
I went ahead and picked up a new hard drive (newegg.com, since nobody seems to have a spare 2.5" ATA HDD lying around.
When it comes in (probably Monday after Christmas), I'll update again.
Yeah, i know. Sounds like a contradiction, right? But when something is "free", there's always a catch. The laptop itself was crap. And I don't say that lightly. The guy who sold it to me told me it was crap.
So, the rundown... Lappy's an Acer TravelMate 2420, with an Intel Celeron D 1.5GHz, 512 MB RAM, 20 GB Hard Drive, 14.1" screen, DVD-ROM/CD-RW, WiFi, Bluetooth, USBx3, Modem, LAN, PCCard (Type II), VGA out.
Anyway, this thing has never been a "top-of-the-line", and frankly, never will be. That Celeron is just powerful enough to run XP (what it originally came with); 7 isn't in the realm of possibility.
If it was, I wouldn't have gotten it so cheap. Of course, I wouldn't have gotten it so cheap if it weren't DOA anyway.
I can already here you asking, "Wait, if you knew that the laptop wouldn't work, why in the world would you spend money on it?" And I would reply, I never said the laptop wouldn't work, it didn't work. And while I wouldn't go so far as to compare myself to mechanic rebuilding an engine, the basic idea is the same. I take the shell of a computer, salvage what I can, replace what I can't, and wind up with something I can use, give away, or sell. Usually the first.
Before that mechanic begins his rebuild, he figures out the problems, decides if it would be worth the work, then makes a plan, including contingencies in case something new crops up. And like our imaginary mechanic, I did the same thing.
What Was Wrong
The damn thing wouldn't start.
I've ran into the same trouble with my car enough times, I think I'm drawn to things that don't want to get going in the mornings (something, something, wife, something... love you, honey). Of course, just like a car, there are dozens of reasons why a computer won't start. The diagnostic screen wasn't much help at first: some esoteric (read: I didn't recognize them at first) error codes and the dreaded "Operating System Not Found" message. That isn't good. It's the equivalent of getting into the car, putting your key in the switch and the car looking back at you and saying "Where's my power train? I can't find my power train!"
Yeah, that's not a Good Thing™.
So, first things first; I googled the error codes, and found out they were network boot errors. "Network boot" is way of starting the computer where the operating system is hosted on the network instead of on the computer itself. So, into the BIOS we go.
This is where I found part of the problem. The BIOS (Basic Input/Output System) was able to notice the hard drive, but wasn't able to identify it. Modern BIOSes are able to read the serial number from drives, and they display it. In a desktop computer, this can be a useful tool when you have multiple hard drives. This laptop was able to grab the basic manufacturer information from the drive, but not the serial number. Just to be on the safe side, I double-checked the boot order: Optical drive, Hard Drive, Network, Floppy. Pretty standard; and pretty much what I expected -- the previous owner was your typical computer user: he isn't one to poke and prod too much; and I knew the other guy he took it to would more than likely return things to base if he couldn't find the cause.
That concerned me a bit... since we were polling the Hard Drive before searching for a Network, the fact that we got the network connection errors were a problem, but not totally unexpected: the previous owner had reported having some corruption issues. I popped open the case, made sure that the memory and hard drive were properly seated -- always a concern when looking at a laptop. I reseated both, and no change. Again, it wasn't a surprise; but double- and triple-checking the simple stuff can save time, money, hassle, and face-palming on a job.
Since I knew the hard drive wasn't accessible at the moment, I went to the next option:
booting from CD.
Luckily, quite a few Linux Distributions have what's called a "Live-CD". Live-CDs are complete operating systems contained on a CD (or in some cases, a DVD). A Live-CD is used to demonstrate the OS or just test hardware for compatibility before actually installing. Booting a live environment is also useful for providing a way to get into an otherwise unaccessible computer (assuming there's no encryption).
Because LiveCDs run completely in RAM, I went ahead and grabbed a memory upgrade; luckily, previous owner had already bought an upgrade. I bought the two 1GB sticks off of him, along with a soft-side carrying case for $50. Sans laptop, he wasn't going to need it, but I gave him fair market for the upgrade anyway.
I fire up a CD called MacPuppy Opera. This particular distro is a variant of Puppy Linux; and one of the major selling points of Puppy is that it has a complete graphic environment, loads completely into RAM, and has the underlying tools to work with a broken computer.
So, I fire up gparted (GNOME Partition Editor) and ask it about the hard drive. It does find it, but like the BIOS, it couldn't actually access it. Seems it needs a disklabel. Unfortunately, I can't seem to create one. Block 0 is unwritable. Crap.
I went ahead and picked up a new hard drive (newegg.com, since nobody seems to have a spare 2.5" ATA HDD lying around.
When it comes in (probably Monday after Christmas), I'll update again.
Saturday, December 19, 2009
Misread headlines
Had to double-take this headline; I wondered what was so bad about getting someone a cooktop for Christmas. Then I realized, griddle != girdle
Tuesday, December 15, 2009
Seriously, can I smack Luke Wilson now?
You have a product. You want to sell your product. You'd like to sell your product to me.
So you advertise. You try to convince me that your product is better than the other guy's similar product. And you make compelling arguments. But there's a catch. See, if I use your product where I would need to use your product, you'll stop me from using your product. So why, pray tell, are you advertising to me?
You see, AT&T, we're at a bit of an impasse. According to your map, I'm in the middle of a great big "Partner" area. And, according to the footnotes linked, "excessive use of Partner coverage may subject [my] service to early termination... Data services may not be available." To get out of the Partner coverage area, I have to go at least 75 miles from home. Besides, we can't very well count your non-affiliated partner's coverage in with yours, now can we? And as for that 3G coverage you keep bragging on, we're talking 130 miles before you say I can even get the signal.
So why, AT&T -- nee Cingular nee SBC nee Southwestern Bell -- do you keep advertising to me?
Hell, I can't even browse your calling plans... because you don't have any for my area. Or Dodge City. Or Larned. Or Greensburg. Or Jetmore. Or Great Bend. Or Pratt. Or Hays. Or Liberal. Or Garden City. Or any other damn city within an hour's drive. I should know; I entered their zip codes to your finder, too.
So please, stop getting Luke Wilson's smug all over my living room. Because when all the comparisons to other cell phone companies you throw up can be shot down by a single answer -- that being, "Maybe so, but if it doesn't work where I need it to, it's useless to me" -- all your ad accomplishes is to piss me off... enough that I switched away from your landline service.
So you advertise. You try to convince me that your product is better than the other guy's similar product. And you make compelling arguments. But there's a catch. See, if I use your product where I would need to use your product, you'll stop me from using your product. So why, pray tell, are you advertising to me?
You see, AT&T, we're at a bit of an impasse. According to your map, I'm in the middle of a great big "Partner" area. And, according to the footnotes linked, "excessive use of Partner coverage may subject [my] service to early termination... Data services may not be available." To get out of the Partner coverage area, I have to go at least 75 miles from home. Besides, we can't very well count your non-affiliated partner's coverage in with yours, now can we? And as for that 3G coverage you keep bragging on, we're talking 130 miles before you say I can even get the signal.
So why, AT&T -- nee Cingular nee SBC nee Southwestern Bell -- do you keep advertising to me?
Hell, I can't even browse your calling plans... because you don't have any for my area. Or Dodge City. Or Larned. Or Greensburg. Or Jetmore. Or Great Bend. Or Pratt. Or Hays. Or Liberal. Or Garden City. Or any other damn city within an hour's drive. I should know; I entered their zip codes to your finder, too.
So please, stop getting Luke Wilson's smug all over my living room. Because when all the comparisons to other cell phone companies you throw up can be shot down by a single answer -- that being, "Maybe so, but if it doesn't work where I need it to, it's useless to me" -- all your ad accomplishes is to piss me off... enough that I switched away from your landline service.
Subscribe to:
Posts (Atom)