Windows NT July 1992 Preview

So I got my hands on another early Windows NT preview. This one is so rough around the edges, it’s more of an alpha then a beta. It’s even reflected in the bootup screen.

Bootup Bluescreen

Well, what has changed from the 1991 releases? Plenty, the registry is coming along quite a bit, but there is no integrated setup program at this point. I almost wonder if this build was meant to be internal only, as it does drop stuff about your Microsoft badge ID. No, really!

Freaky, isn’t it?

Winver showing Build 297

In this build 297, and it includes the OS/2 & MS-DOS/WOW subsystems. The POSIX subsystem is absent, further cementing the idea that it was included much later to target Windows NT at government contracts with a POSIX check-box. I’ve only done some simple testing with the MS-DOS compatibility and it was ‘ok’ but nothing too solid. I didn’t have any luck with the OS/2 stuff, maybe I’m just doing it wrong. One thing is for sure, if it’s this rickety in 1992, they were nowhere near ready in 1991!

I guess if you paid for it, you can put your name all over it!

Another fun touch is who it’s registered to. I guess since Bill is footing the bill for NT, it’s all his anyways.

Broken boot.

With that being said, the installation which involves a batch script dos2nt.bat is very touchy, it does require few files to manually edit. I’ve found it works best with a d drive to swap to, but for the most part NT cann’t find itself properly and you wind up with a blank desktop, stemming from the “An error has occurred in the registry. The Program Manager’s settings and groups can not be accessed.” error. Since NT at this point is far more closer to Windows 3.1, then 1991’s builds being closer to Windows 3.0, the famed game reversi is missing…

However the administrative tools is in NT now, the logon/logoff and locking works. NT at this point is transitioning from an OS running a 32bit version of Windows 3.0 into a fleshed out operating system.

Shutting down.

Windows NT December 1991 Preview

So I re-read that great book, showstopper! which recounts the race to bring Windows NT to market.

showstopper cover

So after a lot of digging around I managed to find an old CD, the second public showing of Windows NT, the December 1991 pre-release.

Windows NT December 1991 scan

This is the first version that contained both MIPS and i386 binaries. At the time there were lots of issues with the MIPS processors, and the MIPS port of NT was slipping behind the i386 in major ways. So between the first public display of Windows NT at the 1991 COMDEX in October, there was a major push to bring the MIPS release up to some level of parity.

On the way to making Windows NT the team started by cross compiling from OS/2 1.3 machines. And in this release they left the cross compilers in there, which is kind of cool. So I just compiled a simple console application, like this:

OS2 cross compile for NT dec 1991

And then running it under the pre-release..

Windows NT dec 1991 running cross compiled exe

Which is pretty neat when you consider it.. And of course in the book there is the coming break with IBM as they pushed not only for the dominant Win32 personality, but also to make NT self hosting. According to the book, NT was self hosting some time in March of 1991, with NT being text only. The first graphics started to show up around May, and Networking as late as August.

Installing the beta is a little interesting as there is no ‘setup’ program at this point. The easiest way to install it is from within MS-DOS. There is a batch file that will xcopy in the needed parts, and then uses debug to write in a new bootsector. After a lot of trial and error I found that the disk works best when it’s under 500MB.

NT 3.1 dec 1991 bootsector fun

And away we go!

windows nt 3.1 december 1991 logon

What is interesting about these 1991 releases is that they didn’t include any of the subsystems other then the Win32 subsystem. And the user login screen here actually doesn’t even take the password it’s just a dummy screen. Windows NT is configured from a plain text file nt.cfg . The registry has only begun it’s work at this stage, but it’s just not there.

reversi!

reversi!

From a user standpoint it looks and feels more like Windows 3.0 or an early Windows 3.1 beta. Which should be expected from the timeline. Even the games, it’s solitare, winmine, and reversi! All in 32bit glory! Even the help about screen for program manger lists that it’s running in “NT MODE”, as opposed to REAL, STANDARD or 386 Enhanced modes, which were available at the time for Windows 3.0 .

Another thing, is that the ‘administrative’ tools didn’t exist yet. I do know the net command had the start/stop so services are there, if only hidden. NT really didn’t start to feel more like NT until late 1992 when it was getting really close to being feature complete, as they shook the bugs out.

Now the install media has this ‘special’ boot floppy to do a GUI install, which Qemu won’t support because of the lack of the ancient scsi controllers of the time. But with a little pathing I managed to get it to run under NT. I’ll spare you the middle bits, but if you can you can get them here.

windows nt 3.1 december 1991 setup

magic happens…

windows nt 3.1 december 1991 setup 14

And there we go!

Another interesting thing I stumbled across from this time was this: InfoWorld article, which is an interview with Steve Balmer just after the October COMDEX show.

It’s really neat to see something as prolific like Windows NT, which has installed seats in the hundreds of millions what it was like when it was so young and vulnerable.. It certainly was ‘forward thinking’ in that it didn’t run all that well on 386’s with 8MB of ram, a ‘power house’ of a computer back then. But it scales up to machines like my laptop with 8 cores and 6GB of ram just fine. By forcing the portability NT like any other *NIX just ports over and keeps on going.

As a silly story when NT 4.0 was in it’s heyday (sp2!) I ran a Compaq Desqpro 386 with 16MB of ram with NT 3.1 Advanced Server as a MSMail hub. And It’s kind of funny in retrospect but I had all the SQL servers using it for alerts and whatnot, and when it came to uptime NT 3.1 had all the 4.0 stuff beat. Then again NT 3.1 was the ‘pure’ architecture version, before they started the crazed speed hacks of the video/printer stuff moving to kernel space… Oh well that’s my $0.02.

Qemu 0.14.0 rc2 released!

Qemu 0.14.0 rc2 and Windows NT December 1991

Qemu 0.14.0 rc2 and Windows NT December 1991

Well this one compiles clean under MinGW so that’s a nice touch. the ISAPC machine type is still broken. 😐

I’ve built the usual set with soundblaster & adlib enabled, and the NE2000 set to 0x300 irq 3 so old crusty things ought to have some hope of working. I’ve also included the PS/2 mode 3 keyboard patch for some really old stuff.

So here we go the x86 / x86_x64 builds that 99% of you want/need.

And here for the rest of the stuff for the 1% that need/want sparc/arm/powerpc/mips etc…

Serweb 0.3

So a while back when I installed a copy of Windows NT 3.1, and put it on the internet, I looked high and low for a web server. Somehow I found this small web server, Serweb by Gus Estrella, which seemed to fit the bill. However one thing that I did notice after a while is that it had a tendency to crash, and it’d require manual intervention to hit an ‘ok’ dialog box. The other stumbling block, was that it was a Win16 application, and Windows NT 3.1 only supports a single WOW instance…. So running Serweb and Netscape always led to issues…

Then the other day, I actually found the source code to serweb! So the first thing I did was to remove the message box function that was preventing me from letting this thing ‘just run’. Well that was cool, but I wondered if this thing was from 1993, meaning it’s MFC dependencies shouldn’t be that involved it may even port to a Win32 application.

So with a few tweaks, mostly in the resource scripts, I was able to rebuild serweb as a win32 application! For the 2-3 people who care about this kind of thing, you can download it here.

I would suspect it’d run on the Dec Alpha or the MIPS, but I haven’t even tried to build it there, as I run NT 4.0 on both of those platforms, and I end up using the IIS that is available.

Serweb 0.3 on WindowsNT 3.1

Serweb 0.3 on WindowsNT 3.1

I do have to admit, I’m kinda surprised that Visual C++ 1.0 for Win32 could handle this… I’ve had pretty mixed results with it, but oddly enough converting a MFC Win16 to a Win32 MFC app seemed somewhat straight forward. It’s probably more so to Gus Estrella’s work then anything I did…!

SHOWSTOPPER!

show-stopper-coverI was browsing around at a book store, and I came across the book “SHOWSTOPPER” the breakneck race to create Windows NT and the next generation at Microsoft.

If you have ever lived through the Windows NT 3.x days you’ll find this a very interesting read. It goes into the big personalities, and of course covers the working habits of Dave Cutler… Although it does paint him in some really odd colors, mostly as an antisocial kind of dictator pushing people to produce the largest program Microsoft had ever produced at the time.

But there is no doubt, Cutler could not have written Windows NT at Digital, as DEC was too fond of hardware lockins (look at VMS & Ultrix/True64). And it does cover the major animosity of Cutler towards DEC with the cancellation of the Prisim/Mica projects, and then the later “I told you so” moment when DEC licensed Windows NT from Microsoft (although other reports claim that DEC threatened MS with a lawsuit, and MS gave them access to NT, along with some money…). Apparently the mantra was “Dec could have had NT for free”..

There is also coverage of the culture clash of what happened when Microsoft had absorbed the Prisim & Mica engineering teams from DEC, and how they did not get along with Microsoft staff, and even did their best to poke holes in the current offerings of MS-DOS & OS/2 as either a toy, or a joke.

One thing I found interesting, is that the book mentions the WLO project, as the foundation for what would be the ‘Win32’ system. WLO if you remember was a port of the Windows Libraries to OS/2. It was very interesting in that Windows, OS/2 and even MS-DOS & Win16 via WOW were all not part of the main Windows NT group, but rather ‘tacked on’.

However it is quite interesting that the design decisions made for a very portable and modular operating system, that survived it’s original CPU & platform being changed 1/4th the way through development, and then the removal of the primary API.

Another thing that was interesting was some of the ‘fixes’ for the too slow, too big that would plague the early versions of NT, was the idea of demand paging portions of the kernel.. I for one would go insane with the blue screens about paging non page-able areas or some other VM error… But the truth was NT was written by people who came from a minicomputer world, and as the book made evident from time to time, they did NOT use PC’s.

Needless to say, the book was somewhat spot on, in that it’d take 10+ years for computers to catch up to what Windows NT was written for. I for one can remember trying to run this on a 386sx-16 and it was horrible… But if you install it on a Pentium II the 3.x series simply FLIES… And in emulation on modern machines it has incredible performance.

While Windows NT 3.1 was no doubt a 1.0 release, 3.5 was a 2.0. The x86 optimizations really payed off, and kicking out the Spider TCP/IP stack, and bringing in the new MS stack helped a LOT. There is no doubt back in 1994 as SLIP & PPP accounts were becoming more common place, Windows NT 3.5’s networking was the easiest to configure and use. Linux back then really was in it’s infancy, and the dialup scripts for pap/chap/pppd were… a nightmare.

“Dogfooding” was another interesting, and necessary thing as once NT was able to start running programs it was important to make people start using it as quickly as possible to shake out bugs in the system. Its also interesting to note the reluctance of the kernel team to deal with the graphical part of NT, and how the first versions were text only. Another weird part was how the security in Windows NT was an after effect, of the internal networking group cooking up what eventually became the domain & trust model. Not to mention how NTFS almost didn’t make it because the filesystem people (all two of them!) were so busy making sure HPFS worked correctly.

There is no doubt that such a ‘ground up’ OS of this magnitude hasn’t been attempted since 1988. It took Microsoft 5 years to get Windows NT out the door, but there is no doubt looking around in the year 2010, Windows NT has a long life ahead of it.

For those interested, you can find it on amazon.

Quake 1 fun

Well I started playing some more with the Quake source, looking to get a dedicated server at least running on Windows NT 3.1 . The problem is that every time someone connected I got this error:

SV_ReadClientMessage: NET_GetMessage failed

And they were disconnected. Some digging thru the source code revelaed that they were being dropped because they had ‘timed out’. But they did not timeout, the real cause is that the null_sys driver is TOO FAST!!! So this gave me a good excuse to re-use my failed SDL build for NT 3.1 (it has no video) but the timer works great! So with a little fun with the linker & Visual C++ 1.0 I managed to get it running!

I’ve put the source and build script for building the dedicated quake server here

The SDL.lib will probably link with every version of Visual C++, but I’m no promising. Also it wont work video wise on NT 3.1 so don’t get all excited.

Anyways no I havent put one on the internet… I dont know if there are enough people even slightly excited about quake… but it’s FYI….

Qemu test…

*Edit, this is completely out of date, and replaced by the much more improved Apache 1.3 for Windows NT 3.1.  Not that it’s visible to a visitor, but it’s live @ http://winnt31.superglobalmegacorp.com/

Well I figured I’d try Qemu on the PowerPC 64 platform… (AKA Playstation 3), and I loaded up NT 3.1 & Serweb… Not exactly a ‘high performance’ solution but I wanted to see it work..

And you can too!

http://216.75.197.51

I just put some minor things on NT 3.1 on there, although I’ll have to get something… better on there.

In the meantime, enjoy some old cat stuff.

Tip on memory for Windows NT 3.1 users

I just found out that if you replace the ntldr & ntdetect.com from Windows NT 3.51 service pack 5, you can access as much memory as the 32bit platform will let you!!! This is of course, 2GB per process, 1GB for Windows NT, the other 1GB is reserved for PCI hardware (remember the upper 384k in MS-DOS??). I have to say it’s GREAT to shatter the 64MB barrier of the earlier PC’s.

Anyways it’s quite simple to do, just download and extract service pack 5, then just copy the ntldr & ntdetect.com in the c:\ directory.

And here is a screen shot for the heck of it, of my Windows NT 3.1 with NT 3.51’s loader running with 3GB of ram! This makes compiling bigger things way easier, and I don’t have to page like crazy with Netscape…

Windows NT 3.1 with 3GB of RAM!

Windows NT 3.1 with 3GB of RAM!

For what it’s worth, I wouldn’t go beyond 3GB, as you’ll never get to use any more then that much, just as it is with Windows 2000,XP,2003,Vista on the i386 32bit platform. That is just the way it is, and yes XP & Vista that tell you about your 4GB of ram are simply reporting installed ram, not available memory.

Networking with Windows NT 3.1 under emulation

 

Windows NT 3.1 does NOT support the PCI bus, making most emulation difficult to impossible.

However some vendors wrote their own PCI routines allowing their PCI devices to work under Windows NT 3.1!

And as luck would have it, the two that I found should work for both VMWare & Virtual PC users!

First the Virtual PC users, you’ll want this file GF10011.EXE , and just extract it, and put it on a floppy.  x64 users will either need to do this under dosbox / MS-DOS in a VM… Also another note about Virtual PC & NT 3.1 is that it has massive pauses, to where it seems to be unusable.  I’ve found that altering the Virtual PC process, and binding it to only a single CPU, and boosting it’s priority helps a great deal, although it’s nothing compared to the speed of Qemu…

VMWare users can download an AMD Pcnet driver here that will happily bind on PCI.  Once you install the driver, you can have it scan the appropriate busses and it should pull up and work.

Another fun thing I found for Virtual PC users, is that the HP Pavilion 5000 desktop shipped ready for Windows NT 3.1, and it was equiped with a S3 video card! And it’s video driver will work with Virtual PC! You can download it from HP’s site here.

This brings Windows NT 3.1 into a far more usable state. Another fun thing I found is that Netscape 2 & 3 for Windows 3.1 WILL RUN! One of these days I’ll have to sort out the exchange client situation…

And if anyone wants to see it in action, be sure to check out Apache running on Windows NT 3.1!

Or you can hit it directly:

http://winnt31.superglobalmegacorp.com/