Moving over to CNET
As of July 2007, I do my blogging at CNET.
The new blog is called Defensive Computing. It is a continuation of this blog, CNET gives all their bloggers free rein.
I am now part of the CNET Blog Network. :-)
Comments on computers from a long-time computer nerd. This blog is intended for non-techie computer users.
As of July 2007, I do my blogging at CNET.
The new blog is called Defensive Computing. It is a continuation of this blog, CNET gives all their bloggers free rein.
I am now part of the CNET Blog Network. :-)
Posted by Michael Horowitz 0 comments Links to this post
David Pogue is not a computer nerd. I mean this neither as a compliment nor an insult, just a statement of fact. I mention it because when reviewing computer "things" his mind set is different from that of a computer nerd.
Mr. Pogue plays with toys and writes about it. This is certainly useful, as far as it goes. I read his columns and have learned things from them. But without an IT background, Mr. Pogue is limited in what he can add to the discussion above and beyond what is in front of him. That is, he can't put things into perspective. It's one thing to say what a device or service or software is, but quite another to say when/where/how to use it. (I can describe a scalpel, but you don't want me operating on your appendix).
With this in mind, let me try to put his article in today's New York Times, The Cartridge, Updated, Catches Up to Data, in perspective.
The article reviewed three removable cartridge devices that are fast and hold lots of data. In general he liked the devices but felt the cartridges were too expensive.
What he failed to mention is that each of these removable cartridge drives is a single point of failure. That is, if the drive itself dies, you lose access to all your data.
Experience tells us that computer backup devices have a limited shelf life. It is all but guaranteed that in a year or two none of the devices he wrote about will still be on the market. And, it goes without saying, that hardware breaks. So anyone planning on depending on these things, needs to buy two - one for now and one for the future when they can't be replaced.
In addition, the drives should be stored in different physical locations.
And if you are really going to depend on them, a case can be made that you need to buy three drives. In other words, you need to treat the backup hardware itself just like the data. Backup. Backup. Backup.
Switching focus to the cartridges, two of them have no track record. Mr. Pogue mentions the "click of death" that haunted previous backup devices from Iomega and notes that their current product, the Rev, seems to have stood the test of time. An excellent point and one that should make anyone wary of the two newer products.
If one of the newer products sounds appealing, let me suggest making a couple phone calls. DriveSavers and OnTrack are the companies of last resort when it comes to extracting data off hard disks. Call them to see if they will extract data from a Rev, GoVault or RDX cartridge. If not . . .
Posting viewed: times
Posted by Michael Horowitz 3 comments Links to this post
Labels: David Pogue, New York Times, Reviews of articles
In the Wall Street Journal on May 17, 2007, Walter Mossberg answered a question about improving WiFi reception. I think his answer could be improved.
He starts with "A more powerful router might help..." I am reasonably familiar with WiFi wireless networks and the power ratings for routers are not a standard topic. Even finding the power rating for a router is probably going to be difficult. While a stronger signal should help reception, anyone reading this needs to be informed as to what constitutes a low, medium and high power ratings for routers.
He also says "You might look for a new router that features a technology called MIMO...".
While true, this is not really the point. The point is to get a pre-N or draft-N router. They all use MIMO, something a non-techie shouldn't need to know. There are many important facts about Pre and Draft N routers that he failed to point out such as: their effectiveness varies greatly, there have been at least five (by my count) generations of "early" N routers, to get the best performance you need to pair an early N router with a matching WiFi adapter and, unlike WiFi G, there is no interoperability between brands.
Then he says "There are also various boosters and repeaters that can be used, though some of these require more technical expertise to install than most folks have."
If it takes technical expertise then its not a suggestion for the audience Mossberg claims to serve. A much better suggestion, and one that does not take technical expertise, is to buy a better antenna and connect it to the existing router. There are omnidirectional antennas that transmit the signal in all directions and directional antentennas for use when you only need the better signal in a single direction. Also, this would serve a heads-up to anyone buying a new router - get one where the antennas can be removed and replaced by better antennas should the need arise.
Then there is what Mr. Mossberg did not say.
The first and easiest step is to change the channel. The G flavor of WiFi uses a single channel, numbered 1, 6 or 11 (I'm simplifying this a bit). If your neighbor has a strong signal on channel 6, for example, it will interfere with your network if you also use channel 6. Determine the channels used by the strongest signals near you, then configure your network to use a different channel. Windows XP does not display the channel used by WiFi G networks, but pretty much all other WiFi software does.
Finally, the router is not the only end of the network that can be improved, so too can the network adapter in the computer.
You might try a USB based WiFi adapter because it lets you move the adapter around to get the best signal without moving the computer. I forget the exact spec, but USB wires can be pretty long. Then too there are PCMCIA (a.k.a. PC Card) network adapters that have very large antennas.
Posting viewed times since May 31, 2007
Posted by Michael Horowitz 2 comments Links to this post
Labels: wall street journal, walter mossberg, wifi
A client, who had been dealing with Dell technical support, came to me with his Dell Inspiron 1150 laptop that no longer ran. The machine came with Windows XP SP1 and after installing Service Pack 2 it slowed down. Then while trying to download the post-SP2 patches it hung.
The first thing Dell had him do (in response to a different set of software problems) was restore the machine to its factory fresh state. There is a hidden copy of Windows on the hard disk for just this purpose and you invoke the recovery program with Control-F11 during system startup.
That worked, the machine was restored. But problems continued.
Next, Dell had him do a clean install of Windows from a Windows CD. This worked too, but the machine had no software on it other than Windows itself and only ran at 640x480 screen resolution.
He wanted the pre-installed software, so Dell tried to restore again to the factory fresh state. But the restore refused to run. Control-F11 no longer invoked the restore program. At this point he came to me.
The only real problem was the incompetence of Dell technical support.
Dell mistake number 1:
Restoring the machine to factory-fresh state requires a special Dell-specific Master Boot Record (the first thing run by the computer after the BIOS has done its job). It turns out that a clean installation of Windows XP updates the Master Boot Record and wipes out the fudges Dell put there. This breaks the Control-F11 feature. So Dell tech support told him to do something that made it impossible to later restore to factory-fresh state - and they didn't know this. When faced with the problem of not being able to restore the machine, Dell support said he must have wiped out the partition.
The story continues:
The main problem after the first recovery back to factory-fresh state was the machine running very slowly. Extremely slowly. This happened after installing Windows XP Service Pack 2 (again, the machine shipped with XP Service Pack 1).
After I restored the machine to factory-fresh state, I un-installed all the junky software that Dell pre-installs on their consumer machines. Then I installed Service Pack 2 and the machine slowed to a crawl. Using Process Explorer I could see the huge amount of cpu being used but there was no one culprit. I turned off all auto-started programs and all optional services to no effect. The "Explorer" process was using alot of cpu time.
Since no applications were running and cpu usage was still very high, it had to have been SP2 that caused the problem. I remembered that when SP2 came out some vendors created updates for their computers that had to be applied to make them SP2 compatible.
Long story short, installing the Dell updates for SP2 that applied to the Inspiron 1150 fixed the cpu usage problem. The machine ran ten times faster than it had been.
Dell mistake number 2:
Ignorance of the above. Dell created updates for SP2 for this machine and yet tech support never suggested installing them when faced with the problem of SP2 slowing down the machine.
Dell mistake number 3:
In searching for the relevant updates to this machine, I entered the service tag at Dell's support site and was presented with a long list of updated software and drivers. A very long list. Too long. It included driver updates for many hardware devices that this machine did not have. For example, there were updates for four or five different optical drives. It was up to me to research the actual hardware and find the appropriate updates.
Other computer vendors do a better job of this. They have software that handles the finding and installing of the correct driver updates. Even if writing software is too hard, how hard can it be to maintain a hardware inventory by service tag and only display the appropriate driver updates? Too hard for Dell it seems.
A huge thank-you goes to Dan Goodell for writing the DSRFIX program that zapped the MBR and made Control-F11 again invoke the recovery utility. It was a life saver. Dan has documented this in great detail. See his Inside the Dell PC Restore Partition. Thanks Dan.
You could consider Dell's lack of documentation about this and their not creating a similar program, their fourth mistake.
Posting viewed times since May 31, 2007
Posted by Michael Horowitz 24 comments Links to this post
Labels: Dell, Gripes, tech support