Shrinking Windows 9x

There seems to be a competition to see how small one can make Windows 9x and have it still boot into a GUI. The latest salvo in this war reduces Win98SE to under 5 megs.
People brag about how fast Windows runs when you do this. Well, yeah! Look at the file listing and the most crowded directory is 28 entries. I’ve seen 1,000+ files in C:\Windows at times. Since FAT is very efficient when dealing with small numbers of files (MS themselves said in the DOS 5 manual to never put more than 100 files in a directory) but inefficient when not, it’s no wonder to me that Windows, cut down this much, can boot in seconds. A computer’s disk is its biggest bottleneck, and the FAT filesystem doesn’t help.

The only problem is, as far as I can tell, Windows cut this small has no networking capabilities or anything else interesting besides a GUI. Which raises the question: Whatcha gonna do with it now? These days, an OS without Internet connectivity and some means to print isn’t very useful to anyone. I know that eliminates two of the three reasons I wanted a computer in the first place.

A few words from Dave the Bloody Pulp after learning about NT software RAID

I’ve worked 26 hours so far this week. I’d say I hope there’s an end in sight, but then again I hoped to leave work at 3:30 this afternoon and that didn’t happen. I’m gonna go read a book and try not to think about work or much of anything else.
I learned something today. I learned that it’s possible for NT4 software RAID (mirroring) to cause a bluescreen and immediate reboot loop on bootup. Funny how the thing that’s supposed to make the server reliable can make it unbootable. One of my colleagues and I figured it out after about three hours of messing around with a downed server. An NT repair install failed; after loading a device driver for the SCSI card, it would refuse to see the drives. At one point we booted the thing up with only one of the drives present (accidentally, I think) and it started. And then we accidentally booted it up with the other one. And that was how we learned that the system was mirrored. The system was set up by some other consulting shop, in case you’re wondering why we didn’t know our own server.

And I’m sure that even a tyro (ahem) knows this about NT4 software RAID, but seeing as I’ve only ever done hardware mirroring, personally, with NT4 (and it’s been six years since I did software striping with it), it’s new to me.

Nothing in the event logs gave any indication what corrupted the mirror, but we broke and recreated the mirror and the server’s been fine.

And maybe this isn’t a tyro problem, because the configuration was unusual. There were two drives and two SCSI host adapters in the mirror. It should make it even more reliable that way, theoretically. But it didn’t turn out that way.

I’m gonna go read a biography of F. Scott Fitzgerald. That ought to take my mind of things.

Why my ramdisk techniques don’t work with XP

I got a question today in a roundabout way asking about ramdisks in Windows, specifically, where to find my instructions for loading Win98 into a ramdisk, and how to do the same in XP.
I haven’t thought about any of this kind of stuff for more than two years. It seems like two lifetimes.

The original instructions appeared in my book, Optimizing Windows (now in the half-price bin at Amazon.com), and instructions to use DriveSpace to compress the disk appear here. You can get the freeware xmsdisk utility this trick requires from simtel.

These techniques absolutely do not work with Windows NT4, 2000, or XP. Despite the similar name, Windows NT/2000/XP are very different operating systems than Windows 9x. Believe it or not, they’re much more closely related to IBM’s OS/2 than they are to Windows 98. Since there is no DOS laying underneath it all, there’s no easy way to do the trickery that the bootable ramdisk tricks use. What these two tricks do is literally intercept the boot process, copy Windows into the ramdisk, then continue booting.

There’s a $99 piece of software called SuperSpeed that gives the NT-based operating systems this capability. I haven’t used it. I imagine it works using the same principle, hooking into the boot process and moving stuff around before booting continues.

The downside, no matter what OS you use, is the boot time. XP boots in seconds, and my book talks about the trickery necessary to get 95 and 98 to boot in 30 seconds or less. But any time you’re moving a few hundred megs or–yikes–a gig or two of data off a disk into a ramdisk, the boot process is going to end up taking minutes instead.

Is it worth it? For some people, yes. It’s nice to have applications load instantly. A lot of things aren’t CPU intensive. You spend more time waiting for your productivity apps to load than you do waiting for them to do anything. Web browsing and e-mail are generally more bandwidth- and disk-intensive than they are CPU-intensive (although CSS seems determined to change that).

But a lot of games aren’t especially disk-intensive, with the possible exception of when they’re loading a new level. So loading the flavor-of-the-week FPS game into a ramdisk isn’t going to speed it up very much.

Of course, XP is far, far more stable than 98. Windows 9x’s lack of stability absolutely drives me up the wall, and for that matter, I don’t think 2000 or XP are as stable as they should be. Given the choice between XP or 98 in a ramdisk, I’d go for XP, with or without speedup utilities.

I’ve made my choice. As I write, I’m sitting in front of a laptop running 2000 (it’s VPNed into work so I can keep an eye on tape backup jobs) and a desktop PC running Linux. I have a 400 MHz Celeron with Windows 98 on it, but it’s the last Win9x box I have (I think I had 4 at one point when I was writing the aforementioned book). Sometimes I use it to play Baseball Mogul and Railroad Tycoon. Right now it doesn’t even have a keyboard or monitor connected to it.

I guess in a way it feels like hypocrisy, but I wrote the first couple of chapters of that book with a word processor running in Red Hat Linux 5.2 (much to my editor’s chagrin), so I started down that path a long, long time ago.

Good news for Optimizing Windows fans

O’Reilly wants to release my 1999 book, Optimizing Windows for Games, Graphics, and Multimedia , under an open content-style license. I’d love to see the thing released so it can gain widespread distribution, which it never really had.
The forms for me to sign are in the mail. My understanding of the license is that it permits changes, so long as the original author and publisher are cited. This will give me the freedom to make a few changes I’ve wanted to make since the book’s initial release, which I intend to take advantage of. I won’t spend months rewriting the manuscript, but I would like to incorporate some corrections I accumulated over the past three and a half years. Not to mention the tools that have changed version numbers since then.

I’m excited at the possibility. I’ll be sure to post an update once I know something. More and more obsolete technical books are getting released in some form or another, and this is a very good thing.

This guy was anti-Microsoft years before anti-Microsoft was cool

Here’s an interesting article, written in 1997 in France, that goes all over the anti-Microsoft map, talking about technical problems, legal problems, bundling, and other issues. The interesting thing about this is that in 1997, there weren’t a lot of people willing to listen.
It’s called Cybersnare. Of course I enjoyed reading it.

What to do when Windows breaks

Every once in a while I get a question like this one, which showed up Thursday night on this page:
I did a stupid thing last night. A friend thought I might need to upgrade my Windows 98SE to Windows ME, but didnt get me an upgrade version, but the full version. Through the installation process, I did not copy the unistall files to my hard drive as I didnt think I would need to uninstall, plus I wanted to get rid of all elements of any old system files, as they were the ones causing me problems (errors in cd-rom line 2, 3 4 etc)…
Now, my computer stays in dos mode, and says that windows cannot run on ms dos version 8.00!?
Please help!? I need to wipe my hard drive and start again. How do I do that?

Please help

This question opens up a huge can of worms, like whether Windows ME really was an upgrade over 98SE, but in this case it sounds like it’s too late for that argument. How do you install Windows cleanly?

Here’s what I do. At a DOS prompt, I enter this command:

REN WINDOWS WINBAK

This gets your old Windows directory out of the way, but without deleting it. This is important because you might want to harvest stuff out of there: IE bookmarks and fonts are the two most likely things.

Next, because these files under any 32-bit Windows cause nothing but problems:

DEL C:\CONFIG.SYS
DEL C:\AUTOEXEC.BAT

If you’re really paranoid, rename them instead:

REN C:\CONFIG.SYS C:\CONFIG.BAK
REN C:\AUTOEXEC.BAT C:\AUTOEXEC.BAK

Next, start Windows setup. Run it off a CD–grab a boot floppy from bootdisk.com if you don’t have one–or the CAB files might, if you’re lucky, be on your hard drive. The standard place OEMs put it is C:\Windows\Options\Cabs. We just renamed Windows, so you can try these commands:

CD \WINBAK\OPTIONS\CABS
SETUP

That’ll start up Windows Setup for whatever version came with your computer.

If the directory’s not there, or Setup.exe isn’t there, you’re stuck using the CD. Boot off the CD, or use the bootdisk if the CD isn’t bootable.

Run Windows setup, and setup will say it found an installation in C:\WINBAK and ask if you want to upgrade it. SAY NO!!!!! (I feel so strongly about this that I’m tempted to use the dreaded blink tag, but I’ll spare you.) It’ll ask where you want to install. Say good ol’ C:\WINDOWS, and you’re on your way to a fresh, clean build.

Update Expert is something for your NT power toolbelt

Now that most of the fun of SQL Slammer has died down, let me present you a tool that might have prevented it: Update Expert.
Basically what it does is query all the NT/2K/XP machines on your network, then query its own database, and tell you what Microsoft patches are available to you. Then it’ll help you download them and push them out. It even figures out the order to install the patches (important) and knows which ones can be installed together to minimize the number of reboots. It’s a lot better than running Windows Update on every PC on your LAN.

I have no connection with St. Bernard Software. My former boss used it and swore by it; when I changed jobs, I introduced it to my new boss. I recommend it because I use it myself.

Open a blg file in Windows

Open a blg file in Windows

In some versions of Windows, the usual method of viewing a file–double clicking on it–doesn’t work for BLG files. If you can’t view a BLG file just by double clicking on it, here’s the other way to open a BLG file in Windows.

This works in current versions of Windows and all the way back to Windows 2000.

Read more

Houston is Microsoft’s problem: Alternatives to Microsoft Office

Houston had a problem. Now it’s Microsoft’s problem.
You see, Microsoft threatened Houston with the same threat they’ve been rattling around a lot of other places. Sign a multi-million-dollar, automatic-upgrade deal for Office and other Microsoft software, or face an audit. When you’re the only game in town and you suspect people have played fast and loose with your licensing agreement, you can afford to do that.

Except the Texans stared the bully down. When Microsoft said Houston needed to cough up some bucks for office software, Houston said fine, they’d buy it from someone else.

And now that Houston is using SimDesk instead of Microsoft Office, it’s making headlines.

The city of Largo, Florida, which runs itself on a thin-client environment based on Linux and KDE, is a PR coup for Linux. But Houston is the fourth-largest city in the United States. And this is turning into a PR nightmare for Microsoft–now Chicago, the third-most populous city, is also looking at SimDesk.

For less than half the money, the cities get ease of use, cross-platform compatibility, centralized offsite file storage, and longer hardware life. SimDesk stands to save Houston far more than the $7 million on paper.

But SimDesk isn’t the only other game in town. WordPerfect is still hanging on, one of the few survivors of the era when there were a dozen or more word processors, spreadsheets, and databases available for the PC. It’s still solid and capable today, and it’s a good choice if you’re looking to go a fairly traditional route. StarOffice is cheaper but still capable. The 602Suite (a.k.a. 602office) is either free or inexpensive, depending on the feature set you want.

Unfortunately, the highly regarded Gobe Productive is off the market, and efforts to raise the money to purchase the source code for the purpose of releasing it as GPL appear to have quietly failed. The good news is that the declination seem to indicate Gobe expects to have some kind of future.

If you want free, go with OpenOffice, which is StarOffice’s free, open-source twin brother. And if you’re willing to dith Office and Windows, you can run KDE and KOffice, or a variety of Gnome productivity apps, such as Evolution, AbiWord, and Gnumeric.

Most of the alternatives don’t offer all the functionality that Office includes, but few people use more than about 20% of Office’s functionality anyway. The alternatives have all of the essentials down.

The main thing tying most companies and organizations to Microsoft Office file format compatibility. An obscure piece of software called ConversionsPlus takes care of that problem. I’ve used ConversionsPlus to convert literally hundreds of files at a time to and from Microsoft Office format, and the process only takes a few minutes.

Windows potpourri

I’ll give some random Windows tips tonight, since it’s getting late and I don’t really want to think. So here’s some stuff I’ve been putting off. So let’s talk utilities and troubleshooting.
Utilities first. Utilities are more fun. So let’s talk about a pair of reader submissions, from Bryan Welch.

Proxomitron. Bryan wondered if I’d ever heard of it because I’d never mentioned it. I’m sure I mentioned it on my page at editthispage.com because I ran Proxomitron for a couple of years. Proxomitron is a freeware proxy server that blocks ads, Javascript, cookies, and just about anything else undesirable. I’ve found that these days I get everything I need from Mozilla–it blocks popups just fine, and I can right-click and pick “Block images from this server” when I run across an objectionable ad, and of course I have GIF animation turned off and Flash not installed. That works for me, and it saves me memory and CPU time.

But if you want more than Mozilla gives you off the shelf, Proxomitron will give it to you. I used to recommend it wholeheartedly. I haven’t looked at a recent version of it but I’d be shocked if it’s changed much. If any of that interests you, I’m sure you’ve already run off to download it. It runs on any version of Windows from Win95 on.

98lite. Most of my readers run Windows 2000 or XP at this point, but about 20% of you are still running Win98 or WinMe. If you want to get a little extra speed, download and run 98lite to remove Internet Explorer and other not-quite-optional-but-mostly-useless cruft. It’s been pretty well established that Windows 9x runs 20-25% faster with IE gone. That’s more improvement than you’ll get from overclocking your CPU. Or from any single hardware upgrade, in most cases.

If you need IE, 98lite can still help you–it can break the desktop integration and speed things up for you, just not as much.

If you’re still running 98, I highly recommend it. How much so? When I was writing Optimizing Windows, Shane Brooks probably would have given me a copy of it, on the theory that its mention in a book would cause at least sales he wouldn’t get otherwise. I mentioned it (I think I dedicated half a chapter to it), but I didn’t ask him for one. I registered the thing. If I liked it enough to pay for it when I probably didn’t have to, that ought to say something.

Troubleshooting. Let’s talk about troubleshooting Windows 2000 and XP.

Weird BSODs in Premiere under Windows 2000. I haven’t completely figured out the pattern yet, but my video editing computer gets really unstable when the disk gets jammed. A power play at church forced me to “fork” my new video–my church gets its edited, censored, changed-for-the-sake-of-change version (pick one) while everyone else gets the slightly longer how-the-guy-with-the-journalism-degree-intended-it version. Re-saving a second project filled up nearly all available disk space and the machine started bluescreening left and right. After I’d done some cleanup last week and freed up over a gig on all my drives, and then defragmented, it had been rock solid.

So if you run Premiere and it seems less than stable, try freeing up some disk space and defragmenting. It seems to be a whole lot more picky than any other app I’ve ever seen. I suspect it’s Premiere that’s picky about disk space and one or more of the video codecs that’s picky about fragmentation. But if you’re like me, you don’t really care which of them is causing the BSODs, you just want it to stop.

Spontaneous, continuous Explorer crashes in Windows 2000. Yeah, the same machine was doing that too. I finally traced the problem to a corrupt file on my desktop. I don’t know which file. I found a mysterious file called settings.ini or something similar. I don’t know if deleting that was what got me going again or if it was some other file. But if Explorer keeps killing itself off on you and restarting and you can’t figure out why, try opening a command prompt, CD’ing to your desktop, and deleting everything you find. (I found I had the same problem if I opened the desktop directory window in Explorer while logged on as a different user, which was how I stumbled across the command line trick.)

I can’t say I’ve ever seen this kind of behavior before. First I thought I had a virus. Then I thought I had a corrupt system file somewhere. I’m glad the problem turned out to have a simple cure, but I wish I’d found that out before I did that reinstall and that lengthy virus scan…

Defragging jammed drives in Windows 2000 and XP. If you don’t have 15% free space available to Defrag (and how it defines “available” seems to be one of the great mysteries of the 21st century), it’ll complain and not do as good of a job as it should. In a pinch, run it anyway. Then run it again. Often, the available free space will climb slightly. You’ll probably never get the drive completely defragmented but you should be able to improve it at least slightly.