No Work, No Pay!

In addition to writing about Windows NT, I install it for people, including computer artist David Em. David is one of the pioneers of computer art--he started during the late seventies, using custom programs chiefly written by Jim Blinn at the Jet Propulsion Laboratory (JPL) in Pasadena, California, where NASA controls and creates unmanned space probes, such as Voyager.

That in itself is a good measure of how far computers have come. Then, Blinn wrote programs in FORTRAN to picture Voyager's encounter with Jupiter. Later, he rewrote the code to produce the graphics in The Mechanical Universe and Mathematics. Today, you can buy a home computer powerful enough to produce work that good--but you need a strong operating system, like NT, to run the applications well.

David's work appears on some Herbie Hancock albums, on posters, and in a book collection. Not surprisingly, he intended to use his computer for programs, such as Fractal Design's Painter, Adobe Photoshop, Altamira Composer, and, in the future, Adobe Premiere and Autodesk's 3D Studio. He needed a fast and capable computer with room for expansion.

After some months of research--while both David and I tried to stay abreast of the state-of-the-art in a modern-day Red Queen's race--we finally decided on equipment. We built quite a nice computer for him composed of an Intel Triton II AZP (alias "Zappa") Peripheral Component Interconnect (PCI)-slot motherboard (256KB of secondary cache), an Intel Pentium/120-MHz processor (32MB of RAM), an Adaptec PCI 2940W fast and wide SCSI controller, a Conner Peripherals CFP-4207W 4GB Wide SCSI drive, an Orchid video-capture card, a Diamond Stealth 64 PCI SuperVGA card with 4MB of RAM and the multimedia MPEG decoder card, a Plextor SCSI quad-speed CD-ROM drive, a Logitech SoundMan sound card with Altec speakers, a Cirque touchpad mouse replacement, and a Wacom wireless 4" by 6" pen pad.

Topping the system off was a Nanao T2-20 monitor, a truly fine display that should serve David through the next two computers that he buys. Until flat-screen displays improve two more orders of magnitude, demanding tasks such as art, layout, and CAD are going to be done on monitors. At least, that's what you can tell your spouse when he or she asks why you need to spend $3000 on an over glorified TV.

David planned to edit video. He'd picked the Conner hard drive because reviews claimed it had the highest sustained throughput in its class. We tested the system at 5MB per second throughput, which is extremely good, under Windows 3.11.

We installed Windows 3.11, intending to install Windows 95 or NT afterward. The installation went well enough: Applications loaded fine. David got some actual work done after two weeks of dinking and twiddling with hardware--the kind of time-suck that computers are supposed to prevent. Along came August 24, and David eyed Windows 95 with a certain interest. He decided to be adventurous and install it: This became important during NT installation a few weeks later.

NT in the Cross Hairs
I didn't expect any problems installing NT: The hardware was pretty stable under Windows 3.1 and Windows 95, the motherboard was the most popular available for the Pentium, and everything else was on the Hardware Compatibility List, or HCL in Microsoft parlance. (I guess those initials mean equipment goes on the list only after passing the "acid" test!)

We cracked open a new copy of NT Version 3.51 and loaded the first two install floppies. At the hardware-recognition step, where NT determines what equipment it has available, we got the dreaded blue screen. That screen is equivalent to UNIX's panic messages or an Amiga guru meditation number and is similarly oriented toward the expert.

Unlike my previous NT installation woes, which were immediately traceable to hardware, this problem seemed to be one of those mysterious puzzles that persists for weeks without resolution. "Kmode exception not handled?" "Irql not less or equal?" Not encouraging. "Page Fault?" That I remember from college. Oh, and during at least one of these tries, NT refused to recognize the SCSI controller and hard disk, too.

After some more futzing around, removing boards we didn't need for the basic install, David and I made the call to technical support. Like a jailed man, NT comes with one free--actually toll--call for help, but it's to Digital, not Microsoft. I guess this is due to the alliance between them. "Dave" (no last name), the technician who answered the phone at Digital, tried to be helpful. At his instruction, we tried different installation options: copying the files from the CD-ROM to the hard drive, custom installation, etc. We got a variety of blue-screen messages again, all of which were unhelpful--the cybernetic equivalent of "I've fallen, and I can't reach my RAM!"

The Intel motherboard wasn't on the HCL, Digital's Dave said. I mentioned that this was the most popular board around and that many of its older relatives were on the list. Sorry, no, Dave explained. Support for one board doesn't mean support for another, even for Intel products. Perhaps you should make sure you have the latest BIOS for the board. Gosh, I countered, the board's only a month old: Wouldn't it have the latest one? Interestingly enough, possibly not, Dave told us. The date on the BIOS is 1992, which obviously is incorrect because the Pentium chip wasn't built then. After an hour on the phone to Digital with no results, we hung up.

One of the major joys of being a nosy columnist is calling companies out on problems like this. Through Microsoft's public relations agency, I hooked up with Jonathan Perera in the NT group. David and I walked through what we'd done and were given some more things to try. Nothing worked. We got the "Page Fault in Nonpaged Area" error message. "Cool," said Jonathan. I was thinking of a stronger epithet.

Then, Jonathan had another idea: Have you tried turning off the RAM cache during the hardware-recognition step? Uh, no, we hadn't. (It's in boot options in CMOS setup, of all places, on this motherboard.) We ran NT's install again and--success! Off it went, copying files, albeit very slowly because we had the RAM cache turned off.

I felt pretty stupid. I knew that was a common solution to install problems but hadn't thought of it. But neither had the Digital guy! And the problem was only in the installer because we re-enabled cache after the first phase of installation was finished and NT worked fine.