A Few Decades Late Book Reviews
Linkers & Loaders, by John R. Levine
Morgan Kaufmann Publishers, October 1999; 256 pages, ISBN 1-55860-496-0; $60.95
Published in 1999, Linkers & Loaders is one of the more recent books reviewed in this series. Interestingly, after more than a decade, the work is both relevant and showing its age. Continue reading
On the Internets, one may find a package labeled as SCO XENIX 386 version 2.2.3 or similar, sometimes mislabeled as version 2.2.2. This is one of the very oldest operating systems designed for 386-based PC compatibles, released around June 1988 (years before 32-bit OS/2 and Windows NT, or Linux and 386BSD for that matter; note that the first release of XENIX 386 probably happened sometime around mid-1987). Based on AT&T’s System V Release 3.2, it’s also one of the hardest operating systems to get running, for several reasons.
The core operating system (the ‘N’ floppies) is version 2.2.3c, though the rest, i.e. the basic and extended utilities (the ‘B’ and ‘X’ floppies) is version 2.2.2c. That may explain the occasional mislabeling. Continue reading
The MS OS/2 videos exhibit has now been completed with the addition of two PDF documents. These are scans of two fat three-ring binders that were handed out to attendees of the Microsoft OS/2 Developer’s Conference in New York City on July 7-9, 1987.
These are 700 pages containing hardcopies of conference slides. More or less all the slides are shown in the videos, but obviously print has a bit better resolution than VHS tape. This should make it easier to follow the videotaped presentations.
Note that the binder covers included the phrase “Master Builders”, which does not appear to be repeated anywhere else in the text.
In December 1994, IBM shipped the first beta version of OS/2 for the PowerPC to selected developers. This beta included the PowerPC operating system as well as Intel-based cross-development tools that ran on OS/2 2.11 or Warp.
The operating system naturally required a PowerPC system to run on. In late 1994, there was only a single machine that OS/2 for PowerPC supported: IBM Personal Computer Power Series 440, also known as Model 6015 or Sandalfoot. This system was very similar to the RS/6000 Model 7020 (40P). The difference was that the Power Series used PReP firmware, rather than OpenFirmware.
Do you remember the famous Windows NT Blue Screen Of Death? For years it was a source of jokes and bad reputation of Windows reliability. There even was a Blue Screen Saver!
Today we fortunately see much less of it, but it still is there, reminding us that Windows Kernel was developed in a text mode environment. The 1989 NT Design Workbook tells us that in the early days of development there was an ANSI terminal emulator and bunch of command line utilities running in the text mode. Sadly all were removed in the retail version. The only true text mode application left around was autochk. Since the day Aclock was conceived I always wanted to run it on the NT text mode boot screen. In it’s twisted logic it actually makes a perfect sense. Continue reading
The site has been finally expanded to include videos of presentations given at Microsoft OS/2 developer conferences held in 1987, a quarter of a century ago. These videos are of historical interest as they show Microsoft’s product plans as they existed at a time (e.g. Steve Ballmer touting the advantages of OS/2). There is naturally a wealth of technical information as well, although that is less historically significant.
Windows buffs may also find some of the presentation interesting, as they show Windows 2.0 several months before the product became available. The reason why a conference targeted at OS/2 developers showed Windows at all was simple: In mid-1987, the upcoming Windows 2.0 was a prototype of the OS/2 GUI, called the Windows Presentation Manager at the time. While Windows 2.0 was more or less complete, OS/2 Presentation Manager was still more than half a year from the first beta.
In fact the Microsoft OS/2 SDK included copies of Windows 1.x and 2.0 so that developers could start wrapping their heads around the new concepts of GUI programming, and do so more than a year before the OS/2 Presentation Manager shipped. Continue reading
On November 3, 1987 IBM announced a few new products and provided more information on several previously announced packages. One of those was OS/2 1.0 Standard Edition. First announced on April 2, 1987, OS/2 1.0 SE ($325) had been completed and IBM would start shipping it to customers in December 1987, slightly ahead of the original schedule.
The announcements from November 3, 1987 covered OS/2 1.0 and 1.1 SE (letter 287-498), OS/2 1.0 and 1.1 EE (letter 287-499), a slew of development tools such as C/2, Macro Assembler/2, or FORTRAN/2 (letter 287-500), and IBM LAN Sever 1.0 (letter 287-501).
In 1984, IBM briefly flirted with XENIX, Microsoft’s variant of UNIX licensed from AT&T. Around 1983-1984, Microsoft and Intel worked on porting XENIX to the 286 processor; Intel shipped XENIX with a number of its development systems in the mid-1980s.
A good description of IBM’s flavor of XENIX may be found in the IBM Personal Computer Seminar Proceedings, Volume 2, Number 9, published in November 1984. The OS/2 Museum recently obtained a copy of this booklet, which is now being made available in PDF format.
A few weeks ago I came across an interview with an academic software researcher, now working for Microsoft. (Unfortunately the interview was in a non-English print publication, so I can’t link to it.) The interview was quite interesting, far better than I’d expect from a magazine targeted at a wider audience; it certainly wasn’t a trade publication.
Near the end of the interview, I had to stop reading and went “What?? That’s the stupidest thing I ever heard!” This was where the interviewee said that one distinguishing mark of good code is the lack of (inline) comments. Properly written code, the theory goes, is so clear and simple that it needs no comments.
This was a bit of a shocker for me. I have some software development experience, and in the fields I’ve worked in, lack of comments in code is a clear mark of poorly written, sloppy code. Even suggesting that code should not be commented would be an obvious sign of utter ignorance, perhaps too strange to even take seriously. Continue reading
Attempting to install the October 1992 pre-release on any CPU less than about 20 years old is likely to result in the following error message:
This is similar to the behavior of the official Windows NT 3.1 and 3.5 releases, but harder to work around, and likely to happen even on Pentiums and some 486s. The reason for that is that Microsoft knew too much, but not enough. Continue reading
