Victory over a cantankerous Pentium-75

Yes, the cantankerous Pentium-75 finally realized that resistance is futile, because I have more stamina than most computers. The problems when we started: sound was flaky, CD audio didn’t work, the modem didn’t work, and the system didn’t always boot properly. Once I got my mitts on it, things quickly got worse and the system wouldn’t boot at all except in safe mode, and of course nothing works in safe mode.
After borrowing some hardware from Gatermann (I don’t know where all my AT stuff went but I sure can’t find it) and spending some serious time with it (writing about NFS and flipping back and forth between my writing station and the P75), it works. Very nicely, in fact. It blows away most Pentium-233s I’ve seen. Seriously. It boots in 30 seconds. Word loads in 10-12. That’s hardly a cause for celebration when a system with a K6-2/500 and a modern hard drive boots Windows in 20 seconds and Word 97 in 4, but consider this: This is a 75 MHz Pentium with 256K L2 cache, a SiS 5500 chipset, a mere 32 megs of RAM, a #9 Vision 330 video card (with an S3 764 chipset), an ISA ESS688-based sound card, and a very old 850 MB Maxtor hard disk. Vintage 1995 all around. Cast in that light, this machine kicks some serious butt.

I suspect some of the problems were hardware-related. After reinstalling Windows, I went and grabbed an audio CD (the always-cheerful Still, by Joy Division), dropped it in, and it indicated it was playing. But I didn’t hear anything. So I stopped the CD and checked the hardware. The CD-ROM drive was set up alone on the secondary channel (good), as a slave device (not good). The audio cable looked like it was seated properly but I wasn’t sure. I took the drive out, gave it a once-over, triple-checked all cable connections, and let it go. I powered up, grabbed another CD (Tori Amos’ Little Earthquakes this time), and by the time I got the speakers plugged into the right jack, Tori Amos was asking why we always crucify ourselves. I didn’t have an answer to that question, but I had sound. Good. Either this computer doesn’t like Joy Division, or what I did fixed it.

I did a few more tweaks (OK, a lot more tweaks, because I’m a bloody perfectionist) and soon I had an overachieving P75 sitting atop the now-infamous Tower of Power. I think I’m going to keep an eye on it for one more day, then deliver it.

There are a large number of P233s at work that won’t launch Word in 10 seconds, and they certainly won’t boot Windows in 30.

So, the owner should be happy with it. I’m pretty happy with it. And I’m very glad to have some tangible numbers about what’s possible with the tricks in my book.

If this Pentium-75 is putting your system to shame, you can put an end to that.

Finishing touches: I let RAM Stress Test, by Ultra-X (trust me, you want to go to www.ultra-x.com, not any of the similar addresses–BIG mistake) run for about 20 hours straight. After 100 cycles without a failure, I restarted, booted into Windows, installed Juno (yuck), cleaned up the network settings, then installed Netscape and defragged the drive. The system is still pretty darn fast for what it is.

And, having run RAM Stress Test on the memory (it has commodity memory in it), I have reasonable confidence in the memory, and thanks to SpinRite, I have the utmost confidence in the drive (a Maxtor).

Attempting to optimize Windows with explicit paths

An interesting idea, this. But I’m not sure it’s worth the required time investment to see if it makes a difference for you.

From: ChiefZeke
Subject: Items to consider
To: dfarq@swbell.net

Dave,

A few more items to consider:

The various *.ini files usually point to files to load as oemfonts.fon=vgaoem.fon. Would it not be better to edit all files so that the full path is used instead; as above:
oemfonts.fon=c:\windows\fonts\vgaoem.fon ?

Also, when Folder Options – File Types – Registered File Types is reviewed many items are listed similar to rundll setup.dll ***. Again, would it not be better for the user to edit the complete listing so that the complete path is used; as above:
c:\windows\rundll.exe c:\windows\system\setup.dll *** ?

While I’m well aware of the tedium involved in doing the necessary editing I would think the end result would be worth it.

Jerry

Since Windows only looks in \Windows\Fonts for fonts, I don’t see how specifying a pathname there would help matters, and it might hurt. And I believe the ini files look for device drivers and the like in \Windows\System and possibly \Windows\System32 exclusively.

The registered filetypes is an interesting idea. Since Windows traverses the path (normally C:\Windows;C:\Windows\System;C:\Windows\Command) looking for that stuff, theoretically, putting a pathname in front of stuff that’s in C:\Windows\Command or C:\Windows\System would make it find the file slightly faster. How much faster depends on how full those directories are, of course.

I wouldn’t start editing without first making a full backup of the \Windows tree (or at the very least, a backup copy of the registry). I fear it might be an awful lot of work for very little gain. I’m always interested in even small speedups, and I’m sure I’ll end up trying it at some point (when I’m not banging my head against the wall learning NFS, NIS and NDS so I can write about them).

Proceed with caution, but if you try it I’m of course very interested in the results.

From: ChiefZeke
Subject: Re: Items to consider
To: Dave Farquhar

Dave,
It wasn’t only the .FON files I was talking about. I was also thinking of the .DRV, .ACM. etc files. In fact, I’ve already edited SYSTEM.INI and WIN.INI to add the path in all those places that I’ve determined warrant it.

Also, while it took about three hours. I’ve also edited the entries for registered filetypes and that went smoothly. I feel there is no need to back-up anything, at this time, to accomplish that task. When you’re doing the editing the path and filename are monitored and any errors get a ‘beep’. Further, long-file names are also ‘beeped’ if they are not enclosed in ” “.

Since all operations are subjective as to how fast our computers really are I will confess I noticed no differential in speed during Windows start or program loading.

Jerry

vestigating that. It’s hard to know what tricks are going to make a difference and which ones won’t. I suspect specifying a path would help really slow systems with extremely crammed system directories more than modern systems with optimized directories.

Ultra-useful Windows and DOS utilities (plus Linux stuff)

4/3/00
There are loads of links in this mail. Explore them; you won’t be disappointed.

Hello. I maintain the Interesting DOS programs website and I was pleasantly surprised when I got an email telling me my site was mentioned in your book as a download reference site for XMSDSK.

While I only provided a link to the XMSDSK file on Simtel, it was still great to see my site which I never thought will ever get mentioned in any book, especially a Windows one 🙂

I got your book and I like it (a lot). However, there were some tools I thought should have gotten mentioned (most are mentioned on my site)

———————————————————————–

On Page 65, you mentioned FIPS as a tool to resize partitions. While I haven’t tried FIPS, there is another freeware utility which I’ve used several times :

Partition Resizer v1.33 It resizes/moves your FAT16/FAT32 partitions safely without losing the data on it. It doesn’t eliminate the need for FDISK. You use Partition Resizer to resize and rearrange the FAT16/FAT32 partitions to create free space on your drive and then run FDISK to create the partition.

———————————————————————–

The Infozip link at http://www.cdrom.com/pub/infozip is orphaned and is no longer updated. An updated link is at ftp://ftp.info-zip.org/pub/infozip/Info-ZIP.html

———————————————————————–

On Page 209, you mentioned that internal Zip drives lack DOS drivers, this is not true as I have an internal ZIP drive and I access them from DOS. Perhaps you were trying the older drivers that came with the first Iomega parallel port drive?

———————————————————————–

FastVid v1.10 Improves video performance on Pentium Pro and Pentium II PCI/AGP systems. I haven’t tested this myself but you may want to check it out.

———————————————————————–

LFN Tools v1.48 These are DOS commands (as stand alone EXE’s) that can handle long filenames in plain DOS. Supports FAT32

For example there is LCOPY which works like XCOPY under a DOS window (copying the long filenames) but in plain DOS. This is useful for diaster recovery situations when you can’t get into Windows and you need to get files off your Windows drive. Other commands include

LMD – create a long directory name LRD – remove a directory with a long directory name (e.g lrd “Program Files”) LDIR – like the DIR command showing long filenames.

The Tools are released under the GPL so source code is available and it is free.

————————————————————————

AVPLite Build 134 Free (yet powerful) command-line antivirus detection and removal program.

The engine is only is only 49K (the antivirus updates are about 1.7MB) but it can scan inside ZIP, TGZ, CAB, mail folders in Netscape and Outlook, DOC files). If there is a virus on a machine, you can have a bootable disk with XMSDSK to create a ramdisk, then have the AVPlite and the antivirus update on separate floppy disks unzipped to the ramdrive and then run AVPlite from the ramdrive.

————————————————————————-

Some Linux links :

SET’s editor v0.4.41

GREAT text editor with the fimiliar Borland IDE interface with syntax highlighting. This is literally the FIRST app to install after you boot Linux. Editing text files with Joe, Vi and Emacs were ummmmmm….. kinda difficult ;-). Released under GPL.

(SET edit is also available for DOS with a built-in MP3 player 😉 )

The one page linux manual A PDF containing a summary of useful Linux commands You mentioned on your Silicon Underground that you wished there was a command reference for Linux. This one is close

————————————————————————- Since you mentioned Win3.x program manager, thought I’ll mention this

Calmira II v3.02 Freeware Win95 shell/interface for Windows 3.x, including explorer, etc.

Mask for Windows – PRWin98 Gives Win3.x apps the look and feel of Win9x apps

————————————————————————-

Looking forward to your upcoming Linux book (I agree with your sentiments on Silicon Underground – documentation is the main holdback for Linux)

Dev Teelucksingh
devtee@trinidad.net
Interesting DOS programs at http://www.opus.co.tt/dave
Trinidad and Tobago Computer Society at http://www.ttcsweb.org

— This email sent with Arachne, the ultimate Internet client —
— http://home.arachne.cz/ —

Wow. Thanks for all the links. That’ll keep my readers busy for ages and ages to come. I did immediately go download SET edit. Very, very nice.

I’m very glad you like my book and look forward to the Linux book. It’s coming along, faster than the Windows book did, but not as quickly as I’d like. I’m not even willing to hazard a guess when it will be finished at this point.

A year from now, there will probably be twice as many Linux books available as there are now. Maybe more. The quality will vary widely. But we need them. The stuff coming out of the Linux Documentation Project is getting better (or maybe I’m just getting smarter) but the stuff available even six months ago very frequently had gaps that a newcomer wouldn’t be able to climb over: missing steps, poor or inaccurate description of output–all kinds of little things that suggest the author didn’t take the time to step through the process one last time. A plethora of available Linux books will help in more ways than one.

Back to DOS and Windows… Although many people deny it, DOS is still an integral part of Windows, and some things just can’t be accomplished without diving into DOS. Even under NT, I always keep a command line open. I can tell you the last day I didn’t use a command line. It was in June of last year. I know because I was in New Mexico, far away from work and from any of my computers.

So Iomega finally got around to releasing Zip drivers that work with the internal IDE and ATAPI models? About time. We bought a big batch of them at work about two years ago, and I needed to access them from DOS, and nothing. The drivers wouldn’t work. We contacted Iomega, and their line was, “These drives require Windows 95 or newer.” A year later, when I was writing that chapter, drivers still hadn’t appeared. But better late than never.

Thanks again.

Refurbishing a Pentium-75

Remember that Pentium-75 I worked on a couple weeks ago? It’s back. I love problem-child PCs. Not. But its owner couldn’t be nicer about it, so that makes it better to deal with. This time I’m doing what I should have done in the first place: clean reinstalling Win95 with a minimalist setup. It works so much better that way.
She’s really funny about it. I guess she’s been driving around with it in the trunk of her car since Friday, so it’s been a few places, like the park. Taking the computer to the park for some fresh air… I guess it couldn’t hurt, though I can’t say I’ve ever tried that. “Not the way I drive,” she said. I see…

I’d better see if I can get some stuff written, and maybe put the computer up on the bench and see what I can get it to tell me.

Later:

Whooee! Talk about one sick puppy! I dredged up the motivation to pop that computer up on the bench (so to speak–I’ve got a real Tower of Power going here now, with three minitowers stacked on top of one another, cascading off a KVM switch–I do wish I had a digital camera right about now so you could see). Well, I fire up, and Windows takes a week to load (warning sign #1: this computer may be old, but it’s not a 486SX/25). When that annoying Windows screen finally goes away, I get a Windows protection error while initializing device VAUDRV. Obviously some kind of audio driver. Veree strenge, as Chief Inspector Clouseau would say. (I find myself wanting to type grep -r vaudrv * to hunt down that file, which just indicates I’ve been getting way too much Linux time lately.) I boot in safe mode, nuke the audio drivers, reboot, and…. same error. Let’s look around a bit more. The root directory is littered with stuff that doesn’t need to be there, but nothing causing problems. I see multiple installations of the sound drivers, which isn’t helping but shouldn’t hurt–they’re in separate directories. I see a directory with a weird name, but that turns out to be DOS-mode CD-ROM drivers. A quick scan of autoexec.bat/config.sys reveals they’re not active, so they’re out of mind, if not totally out of sight. Then I notice the disk space: 390 megs free. What’s she been doing? A quick dir /w /s reveals 406 MB used. No way. Scandisk. No problems. Huh? So I run FDISK and… learn that this computer thinks it has an 813 MB drive. What? I reboot, go into the BIOS, and autodetect the drive. No, it’s a 1.6 gig. OK. Reboot, go into DOS, and… 813 MB.

I’m starting to wonder how many problems that’s causing.

A dir /s *.doc turns up very little, so it doesn’t look like she has any data on the machine. I’m thinking visit Maxtor’s site, get a low-level format utility for the drive to wipe out whatever Windows decided to do to that poor drive’s partition table, and start over. But I’ll have to ask before I do that, just in case.

Hey, I wonder if SpinRite would have anything to say about all this? So I run SpinRite. The model number it retrieves from the drive suggests it’s an 850-meg drive. Hmm. Maybe I misread the BIOS? Might as well let SpinRite finish at this point. It thinks it’ll only take a couple of hours on a drive this size. I can go read, or switch over to one of my other PCs and write for a while.

I still think I want to low-level format and start over from scratch. We’ll see if I can get this P75 to outrun the P233s at work. I’m betting I can. (Part of it is that I’m good, yes, but a big part of it is the sorry state of those P233s.) I’m gonna whip this underachieving heap of silicon into shape.

Still later:

I was misreading the drive parameters last night. I’m not used to working with machines with the AMI BIOS. It was reporting the number of sectors where I expected to see the drive size, hence the 850 MB/1.6 GB confusion. So I haven’t found something totally out of the ordinary after all.

Underachieving Win9x Network performance

David Yerka asked what can cause really slow network performance in Windows 95/98. I mailed him, suggesting maybe someone had run MTUSpeed or some similar utility on the machine to optimize dialup performance. LAN performance tends to go into the toilet after doing that. (Voice of experience speaking… My Win95 box was a real dog until that light went off–long after my book was on store shelves, of course.) He responded with some useful information.

From: David M. Yerka
Subject: Re: Slow Win9x network performance
To: Dave Farquhar

Hi Dave:

Thanks for the reply you win the big bucks! That is exactly what is going on. Apparently Win9x only sets the MaxMTU in one place:

HKey_local machine\system\currentcontrolset\services\class\nettrans000

and while additional information makes this key appear to belong only to dialup networking apparently it is the place where Win9x picks up the settings for the network also. You were right also I remembered (actually, before I got your email) that someone had used MTUSpeed on this machine to optimize dialup before I convinced my clients to get a “webramp appliance” to do sharing. Unfortunately, it appears that even if you tell MTUSpeed to “remove all settings” it leaves the MaxMTU setting at say 576 (which is usually the best for dialup ISP’s). You must explicitly change the settings in MTUSpeed to 1500 and reboot BEFORE have MTUSpeed “remove all settings.”

Interestingly, I found that you could sort of hack the registry with a combination of stuff and seemingly get both optimizations: stick a string in the key below of MaxMTU=”1500″

HKey_local machine\system\currentcontrolset\services\class\nettrans\netservice000

Use MTUSpeed to set the MTU to 1500 reboot

edit the first key …\nettrans000 to MaxMTU=”576″ and reboot.

checking with MTUspeed (and don’t under any circumstance change anything) shows the MTU to be 576 while network performance approaches 950K for a 10T UTP network.

Isn’t Window just wonderful and weird.. or something!!

Thanks again David Yerka

If you can’t buy it, is it legal to copy?

3/29/00
Here’s a big, hairy question:

From: Francisco Garcia Maceda
Subject: Napster
To: Dave Farquhar

I have also been playing around with Napster for a couple of days and as you have seen there are a couple of rough edges still in the design and implementation. However, I think this is going to grow to something bigger and probably very different from the original implementation. There is already Wrapster, which allows you to “wrap” files, images, videos, programs, etc. in MP3 headers so you can exchange this “wraps” as if they were actual MP3’s. We’ll see.

The other day I was talking to a friend that made some research into copyright law both in the US and locally (Mexico). It appears that in both countries you can copy ANY copyrighted material that is out of print or distribution as long as you do not redistribute it or profit from it. This could be very important for people that don’t want to encourage piracy but at the same time is looking for some old tunes/books/etc. that are impossible to obtain today since they have been out of print for years/decades. Maybe you or one of your readers could shed some light in this topic regarding copyright law in the US and even in the EU?

Francisco Garcia Maceda

My understanding is that copyright law makes no provisions for material that’s in print or out of print, and until the copyright holder says it’s OK to freely copy something, freely copying it is illegal.

Tracking down the copyright holder can be a real pain. I wrote Optimizing Windows, but I don’t hold the copyright on it. If O’Reilly takes the book out of print, that doesn’t mean people can freely copy it. And in the case of my contract, O’Reilly retains the copyright, so you can’t get my permission to copy it–because I can’t give it. Sometimes the rights revert back to the author, but only the publisher and author can generally answer that question.

Those Young Snakes tunes I was referring to are a case point. Aimee Mann doesn’t own the copyrights on those, so she can’t give permission to freely copy them. She’s toyed with the idea of buying back the rights, but that’s never happened. So, technically, yes, by owning those MP3s, I’m breaking the law. Whether anyone cares is another question. Since no one’s making money off this 20-year-old EP that’s been out of print for probably 18 or 19 years, probably not. As Pournelle says, you have to let your conscience be your guide. [Ironic note: Some months later, Andy Breslau, the album’s producer, mailed me. We had a long, pleasant discussion over e-mail, and $10 later, I have a legal copy of the EP. So sometimes copyright holders will find you.]

Music is a bit hairy, because there’s the copyright on the lyrics and notes themselves, but then there’s the copyright on the recording. The label owns the copyright on the recording. The songwriter owns the copyright on the lyrics and notes. If an artist breaks from a label, the recordings don’t go with them, but they have the rights to re-record the song. Prince has long been threatening to do exactly this (and for all I know he’s made good on it).

That leads us into live concert recordings. A recording that a sound technician makes by splicing into the soundboard or that a fan makes by smuggling in a recording device isn’t covered by the label’s copyright, nor are they covered by the artist’s copyright, which is why the courts have upheld the rights of bootleggers. When you go into a record store and plunk down $40 for a Tori Amos live CD, Amos never sees a dime of it. The live recordings field is an underground industry, living on the very fringe of the law. As I said before, some artists worry about this stuff a lot, while other artists go so far as to encourage it. You have to be a fan to love these recordings, so I don’t see any problem with them. Record labels do, but the law isn’t on their side in this case. They may argue that this hinders their ability to sell live CDs, but I don’t buy that. I own every live Joy Division album their record label ever put out, plus every bootleg I’ve managed to find. The fanatics will buy anything that has their favorite band’s name on it, and those are the people who plunk down obnoxious amounts of money for these bootlegs. If those MP3s hurt anyone, it’s the bootleg record companies and the record stores that deal in them.

The other place where this question comes up a lot is old software. The author doesn’t make a dime if you go buy an Atari 2600 cartridge at a flea market for a buck, so it doesn’t make any difference to the author, I would assume, if you bought a copy of it or just downloaded the ROM image and played it with an emulator–though it makes a big difference to the law. With software this old, frequently the publisher is long gone, the author may or may not still be alive, but the copyrights are still valid for a few more years and someone, somewhere, owns them and could choose to enforce them.

Really, what it comes down to is two questions: 1. Am I hurting the owner of the copyright? And 2. If I’m not hurting the owner, morally I can do this, but legally I may not be able to, so am I willing to take that risk?

I hope that answers your question. I’m sure others will pipe in as well.

Dave

More thoughts on MP3. Record sales are down. The industry blames MP3. But as labels consolidate, they axe artists by the hundreds or thousands. The end result is fewer people recording music, and, probably, fewer sales. Plus, many artists don’t hit it big right away. It took U2 seven years and five albums. Today, they’re Ireland’s biggest industry. They wouldn’t have survived if they had come along in 1999 rather than 1979–Boy was a great album, a really great album, but probably wouldn’t have been a great commercial success in any era.

I don’t think MP3 hurts teenybopper bands like The Backstreet Boys and ‘NSync. Sure, those songs get pirated by the boatload, but they also sell by the boatload, and much of the money surrounding bands like that is in merchandising–lunch boxes, bedsheets, posters, videos… The records are an afterthought. (And it shows.) Those bands will disappear within a couple of years, just like the New Kids on the Block did in the late ’80s/early ’90s and the Bay City Rollers in the mid-1970s.

I think who the MP3s really hurt are the one-hit wonders. You know, bands like Deep Blue Something, who record an album with exactly one catchy song (“Breakfast at Tiffany’s,” in that band’s case) that goes on to become a mega-hit, but with no obvious followup the band drops off the face of the earth.

I don’t see how MP3s can hurt established bands any more than radio taping does. And record companies fall all over themselves to get their acts played on the radio.

FTP batch files

I found this question on the Sys Admin magazine forum:
Can I create a batch file (or something else) to allow me to execute my file transfer from a Tru64 UNIX to a NT without having to type each command? This is what I’m doing now to transfer a recompiled data base from UNIX to NT: At the NT machine:

C:> cd\sandgis
sandgis> erase *.*
are you sure? Y
sandgis> ftp 000.00.000.0
name: *******
passwd: ********
ftp> cd /data/sandgis
ftp> prompt off
ftp> bin
ftp> mget *.*
ftp> cd /apps/sandcauv
ftp> mget par*.*
ftp> quit
sandgis> cd info
sandgis\info> erase *.*
are you sure? Y
sandgis\info> ftp 000.00.000.0
name: ****
passwd: *****
ftp> cd /data/sandgis/info
ftp> bin
ftp> prompt off
ftp> mget *.*
ftp >quit
(this is half of it)

Well, you get the idea… I can get a batch file to work until it goes into FTP, then it stops. Since I’ve got to do this on five NT machines twice a week and the total files size is near half a gig., this is very time consuming.

And here’s the response I submitted:

Put your pre-FTP commands in a batch file, as it sounds like you already have, then add the -s:[textfile] parameter to your FTP statements containing FTP commands, e.g. ftp -s:ftp1.txt 000.00.000.0.

The contents of ftp1.txt, based on your example:
name
password
prompt off
bin
mget *.*
cd /apps/sandcauv
mget par*.*
quit

Anything you put in a file specified by the -s parameter gets fed to your FTP client.

So, you’ll need a batch file, plus a text file for each FTP session, which could turn into a real mess of files, but it’s a whole lot better than typing all that garbage twice a week.

So, who makes the best Mac utility?

When it comes to Macintoshes, I feel like a catcher playing shortstop. Yes, a good athelete can play both positions, but very few can play both exceptionally well. The mindset’s all different. The ideal physique for each is all different.
I fix Macs for the good of my team. Period. Right now my job is to nurse along a dozen Macs for four months until the new fiscal year starts, then they can replace them. I think those machines have four months left in ’em. The bigger question is, do I have four months’ tolerance left in me? Hard to say.

But thanks to my pile of Macs on their last legs (these are 120 MHz machines with no L2 cache and a pathetic 10 MB/sec SCSI-II bus, and they’ve never had regular maintenance) I’ve gotten a lot of first-hand experience with Mac utilities suites.

I said in my book that Norton Utilities for Windows is, in most regards, the second-best utilities suite out there. Problem is, the other two big ones split first place, and the third-placer is usually so bad in that regard that you’d prefer not to use it. So Norton Utilities compromises its way to the top like a politician. The Mac Norton Utilities is the same way. There are two reasons to buy Norton Utilities for the Mac: Speed Disk and Norton Disk Doctor. Period. The rest of the stuff on the CD is completely, totally worthless. Eats up memory, slows the system down, causes crashes. Copy SD and NDD to a CD-R, then run over the original with your car. They’re that bad. But of course your end-users will install them since all software is good, right? You should install everything just in case you need it someday. Famous last words, I say…

But you need Speed Disk and Norton Disk Doctor desperately. Macs are as bad as Microsoft OSs about fragmentation, and they’re far worse about trashing their directory structures. Use a Mac for a week normally, and use a PC for a week, turning it off improperly on a whim (with automatic ScanDisk runs disabled), then at the end of a week, run a disk utility on each. The Mac will have more disk errors. Apple’s Disk First Aid is nice and non-invasive, but it catches a small percentage of the problems. NDD scoops up all of the routine stuff that Disk First Aid misses.

As for Speed Disk, it works. It’s not the least bit configurable, but it has enough sense to put frequently used stuff at the front of the disk and stuff you never touch at the end.

But if you need to do what Norton Utilities says it does, you really need Tech Tool Pro. Its defragmenter is at least the equal of Speed Disk, and its disk repair tools will fix problems that cause NDD to crash. Plus it has hardware diagnostics, and it’ll cleanly and safely zap the Mac’s PRAM (its equivalent to CMOS) and cleanly rebuild the Mac’s desktop (something that should be done once a month).

But the best disk repair tool of them all is Disk Warrior. Unlike the other suites, Disk Warrior just assumes there are problems with your disk. That’s a pretty safe assumption. It goes in, scavenges the disk, rebuilds the directory structure, and asks very, very few questions. Then it rewrites the directory in optimal fashion, increasing your Mac’s disk access by about the same factor as normal defragmentation would.

Oh yes, Disk Warrior comes with a system extension that checks all data before it gets written to the drive, to reduce errors. I really don’t like that idea. Worse speed, plus there’s always something that every extension conflicts with. That idea just makes me really nervous. Then again, since I regard the Mac’s directory structure as a time bomb, maybe I should use it. But I’m torn.

Which would I buy? If I could only have one of the three, I’d take Tech Tool Pro, because it’s the most complete of the three. I’d rather have both Tech Tool and Disk Warrior at my disposal. When a Mac goes bad, you can automatically run Disk Warrior, then rebuild the desktop with Tech Tool Pro before doing anything else, and about half the time one or the other of those (or the combination of them) will fix the problem. Or they’ll fix little problems before they become big ones.

Disk Warrior is positively outstanding for what it does, but it’s a one-dimensional player. For now, it does ship with a disk optimizer, but it’s limited to optimizing one of the Mac’s two common disk formats. At $79 vs. $99 for Tech Tool Pro, if you’ve only got a hundred bucks to spend, you’re better off with Tech Tool Pro.

As for Norton Utilities, I’ve got it, and it’s nice to have a third-string disk utility just in case the other two can’t fix it. Sometimes a Mac disk problem gets so hairy that you have to run multiple disk utilities in round-robin fashion to fix it. So run Disk Warrior, then Tech Tool Pro, then Norton Disk Doctor, then Apple Disk First Aid. Lather, rinse, and repeat until all four agree there are no disk errors.