Those promised keyboard tricks. To get a Windows key, download the Kernel Toys. The keyboard applet, which works under 95 and 98, allows you to remap the caps lock, control, or alt keys to a Windows key. You can also remap the caps lock key to control or alt if you want. 

To assign My Computer to a hotkey, create a new shortcut with the following command line:
explorer.exe /n,/e,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

Next, click on the shortcut key and hit a key (I suggest "m" or "c") and that'll give you instant two-pane access to My Computer any time you hit ctrl-alt and that key.

If you want single-pane access (I don't think it's as useful, but hey), use this command line instead:
explorer.exe /n,::{20D04FE0-3AEA-1069-A2D8-08002B30309D}

I finally fixed my firewall. I souped up the firewall a while back, then it never worked again. (I guess that's the ultimate in security, eh? No one can hack in if you're offline.) I forgot which ethernet card was outgoing and which was pointing inward, to my LAN. Finally, I tried stopping and restarting PMFirewall, which printed my network configuration. When both NICs were assigned to the address 192.168.0.1, I knew I was in trouble. With that tip-off, fixing it took just a matter of minutes.

Speaking of Linux, a speed tip. If you're running Red Hat Linux as a NAT/IP masquerade gateway to share an Internet connection, do yourself a favor and install the BIND and caching-nameserver RPMs, then set your first DNS entry on your other PCs to your gateway's IP address. This will make your proxy server look up DNS addresses for you and store them, reducing network traffic slightly but noticeably. The overhead is minimal; I've got Steve DeLassus running IP masquerade and caching nameserver on a 486SX/20 and it's more than up to the task. For a small home network, a 386SX/16 has enough horsepower as long as it meets your distribution's minimum memory requirements. I'd be more comfortable with a 50 MHz or faster 486 for a small office, but that's as much due to expected age and reliability as it is to CPU requirements.

If you're running a close derivative of Red Hat (Mandrake is certainly close enough, and I believe even Caldera and TurboLinux are as well), go ahead and download Red Hat's caching nameserver RPM. It's just a couple of short text files, but it's easier to download and install an RPM than it is to key them in.

Sorry, keyboard secrets will have to wait. No time. But here's something else.

Case of the disappearing cursor. Maybe you're lucky and you've never seen this, but sometimes the cursor will disappear inside text boxes in Windows NT (and presumably 9x). The solution is to reinstall your video driver -- preferably a newer version.

I'll be back in a bit. I've got some cool hotkey tricks. You don't have to buy a new Microsoft keyboard to have keyboard access to things like the My Computer icon. For that matter you don't have to buy a new keyboard to get a Windows key either, if you're an old-timer like me still using an old 101-key PS/2 keyboard (the keyboards of today just aren't nearly as good as the ones IBM and Lexmark made 12 or 13 years ago--of course, they also cost 10% of what those keyboards cost new).

I'll spill the beans later this morning.

Optimizing Windows NT for Games, Graphics and Multimedia or Whatever... I occasionally get a question whether there'll ever be such a beast. O'Reilly and I discussed it in the past, with little interest. (In fact when we were negotiating Optimizing Windows, I wanted it to be an NT book, and they asked if I knew Win9x well enough to write about that instead.)

There's the possibility that another publisher who's strong in Windows NT/Windows 2000, such as Sybex, might be interested. I haven't talked to anyone there about it yet. But believe me, I've thought about the possibility of such a book.

I tried to write Optimizing Windows in such a way that someone who knew Windows 9x and another OS would then be able to apply the principles to both OSes, even though the specifics would only apply to 9x.

In the meantime, the best suggestion I can come up with is to take yesterday's post , print it, then paste it to an otherwise underutilized page (such as the last page of the preface, which is totally blank). While it doesn't go into great detail, that message could well form the basis of a chapter in an NT/2000 follow-on. I'd say at least half of chapter 2 in Optimizing Windows (particularly the user interface stuff) applies to NT and 2000 as well.

Laptop troubleshooting. I had a laptop the other day that seemed to launch programs and move the mouse pointer around at will. I'd never seen anything like it before. We were perplexed about it for a couple of hours (it was a deployed user in California, so it wasn't like I could just tool over to his desk and start trying stuff). On a hunch, he unplugged everything and powered up the bare laptop. It worked fine. He started adding components one at a time, and when he got to the mouse, the problem reappeared.

Constant travel and frequent plugging and unplugging certainly could be hard on the mouse cable, so I can see where this might be a common problem for road warriors (I'd say 90 percent of my support experience is desktop PCs). So, if you're getting unexplainable behavior from a PC, especially a laptop, try a different mouse -- and a different external keyboard too, while you're at it -- and see if that makes the problem go away.

A partial retraction. OK, Southwestern Bell isn't responsible for all my missing mail. I had a second POP3 client running that I forgot about, which was grabbing some of my mail. But my computer couldn't find a DHCP server all day, so even though one problem wasn't their fault, another one was. So I'm still gonna write Casey Kassum with a request and dedication: Todd Rundgren's "I Hate My Frickin' ISP," dedicated to my beloved Southwestern Bell.

Running, uh, no, executing Windows NT 4.0 on a Pentium-75 with 16 MB RAM. Disclaimer: Before you start thinking things that include my name and words like "crack" or "LSD," let me state emphatically that this was not my idea. I was only following orders. (I'm not on drugs. I'm not nuts--I'm certifiably sane. I'm not even depressed.) All that clear? Good.

That said, the stated minimum hardware requirements for NT 4 are a 486 CPU with 12 MB RAM. And I did once build a print server out of an old IBM PS/2 that had a 486SLC2/50 CPU and 16 megs of RAM. Hey, I was young and I needed the money, OK? Besides, it was a very experimental time and I didn't think anybody would get hurt...

OK, I'm done turning druggy double entendres.

Needless to say, NT on this machine is anything but pretty. (And I'll put a marginal machine into service as a server where no one ever interacts with it directly long before I stick one on an end-user's desk.) The video card in my flagship PC has more memory and processing power. But we're out of PCs, and this poor girl needs a computer on her desk (though she's never done anything to deserve this fate), so here's what I did to try to make life on this machine more tolerable. These tricks work much better on fast machines.

• Pull out all network protocols except TCP/IP. I also double-checked all TCP/IP settings and made sure the closest DNS server was first on the list.
  
• Use a static IP address. The DHCP service uses memory and CPU cycles, and on machines like this, every byte and cycle counts.
  
• Remove Office Startup, Find Fast, and LoadWC from Startup. The first two are in the All Users start menu. The last is in the registry. All eat memory and provide no useful functionality.
  
• Move the swap file to a second physical hard disk. This machine happened to have a second drive, so I put the swap file there for better performance.
  
• Turn off unnecessary services. The Scheduler service and Computer Browser service normally aren't needed. If the network never sent out notifications (ours does), I'd also turn off the Messenger service.
  
• Remove unnecessary fonts. I won't do this without her present, since I might inadvertently nuke her favorite font. But if she doesn't use it, it's gone.
  
• Keep free space above 100 megs. Windows slows to a crawl when forced to live on a drive that's as crowded as a mosh pit.
  
• Defragment! Making matters worse, this drive didn't seem to have a single file on it that wasn't fragmented. I ran Diskeeper and there was more red on the screen than at a Cardinals game when Mark McGwire's chasing home run records.
  
• When you have two drives, put the OS on the faster of the two. Unfortunately, the OS is on an ancient Seagate 420-meg drive, with a 2.1-gig drive in as the secondary drive. The roles really should be reversed. When in doubt, the bigger drive is usually faster. The newer drive almost always is. I may just Ghost the OS over to the 2.1-gig drive, then switch them.
  
• Switch to Program Manager. She's probably not comfortable with the old Windows 3.1 interface (I've only ever met one person who liked it) so I probably won't do this, but that'll save you a couple megs.

Short stuff today. There's mail on nostalgia and my infamous books today, so let's get right to them.

Another Internet utility. I found a link to Naviscope (www.naviscope.com) this week. Naviscope is a swiss army knife Internet tool, providing ad blocking, DNS caching, prefetch, logging and a few other features. As such, it can replace Proxomitron, FastNet, and Netsonic--three utilities I mention in Optimizing Windows.

Using bootlog.txt. I resurrected a dead Win95 box yesterday; it wouldn't boot. Bootlog.txt to the rescue. (You can also use bootlog.prv, the log of the previous boot). Search the file for the string "fail" and note the device driver that isn't working. Hot tip: frequently it's a network driver. Boot into safe mode, remove the offending driver(s) from Device Manager and potentially problematic software (Anti-Virus software and RealAudio both come to mind; you can always reinstall those later after you've got the system back up and running), then reboot. If you boot successfully, add the drivers back in, then reinstall the software you uninstalled, and you're back in business. Sure beats a reformat and reinstall.

Wednesday, 10/4/00

Take charge of your CPU usage under Win9x. I talked about CPU Controller from BinaryWork in Optimizing Windows, which allows you to set a task's priority (a la WinNT's Task Manager). There's a freeware app at http://www.blehq.org/pv2k.htm that has most of its functionality. Haven't tested it yet, but I definitely will.

Binary file editing. I've recovered many a student's term paper from munged disks over the years using Norton Disk Edit, from the Norton Utilities (making myself a hero many times). Usually I can only recover the plain text, but that's a lot better than nothing. Rebuilding an Excel spreadsheet or a QuarkXPress document is much harder--you have to know the file formats, which I don't.