Updated: 3/28/2005; 11:31:18 AM.
Mondegreen
Erik Neu's weblog. Focus on current news and political topics, and general-interest Information Technology topics. Some specific topics of interest: Words & Language, everyday economics, requirements engineering, extreme programming, Minnesota, bicycling, refactoring, traffic planning & analysis, Miles Davis, software useability, weblogs, nature vs. nurture, antibiotics, Social Security, tax policy, school choice, student tracking by ability, twins, short-track speed skating, table tennis, great sports stories, PBS, NPR, web search strategies, mortgage industry, mortgage-backed securities, MBTI, Myers-Briggs, Rensselaer Polytechnic Institute, RPI, Phi Sigma Kappa, digital video, nurtured heart.
        

Saturday, January 15, 2005
trackback []

Just got my new Western Digital 200 Gb hard drive working--finally. It came with its own installation program, to partition and format the drive after it is installed. The program turned out not to be very helpful. The quick-install book said "If your drive is > 137 Gb, you will need to boot to DOS to take advantage of the additional space". I considered this a downer, since I never boot to DOS, so I was already in unfamiliar territory.

After a mis-start or two, I successfully booted to DOS from their CD (which included the Caldera DOS clone). But at the end of the boot sequence, there were 4 lines that all said "Invalid filename or blah". And nothing else happened. I tried looking for an EXE to type in, but that didn't yield any progress, either.

So then I tried making a boot diskette--first time I've touched a diskette in years--but that led to exactly the same result. So then I went to their website, which was not helpful at all, including using special non-standard search syntax. I got nowhere with that.

After fumbling around some more, including multiple, tedious reboots and looking at Device Manager, I somehow stumbled on the idea of maybe seeing if the Windows version of the install utility might work, despite the disclaimer. Lo and behold, it appeared to. Except that it hung up on partitioning--no progress, no error, just indefinite hang (I left it overnight, just to be sure).

I hung it up for the night. The next day, I decided to search for "can't boot to DOS". That yielded a lucky break--more chance than the fruit of well-targeted searching--that made me think of something that, if I were even a third-rate sysadmin, would have been obvious: Drive Manager.

I fired up XP's built-in Drive Manager, and from then on, it was smooth sailing. Drive Manager did find existing partitions from the WD utility. I deleted those, then created one big partition, then formatted it, and voila!

My analysis is that WD was trying to shield less technical (most) users from the need to access Drive Manager, and further assuming that anyone who did need to access it would know about it, and perhaps folded in there was an outdated assumption that anyone buying a > 137 Gb drive most likely fell into the latter category.


5:38:23 PM    comment []

© Copyright 2005 Erik Neu.
 
January 2005
Sun Mon Tue Wed Thu Fri Sat
            1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31          
Dec   Feb


Click here to visit the Radio UserLand website.

Subscribe to "Mondegreen" in Radio UserLand.

Click to see the XML version of this web page.

Click here to send an email to the editor of this weblog.


Search My Blog