When Microsoft started offering OS/2, the arrangement was roughly similar to how DOS 3.3 had been handled: Microsoft and IBM jointly developed the code, IBM maintained its own version, and Microsoft licensed an “adaptation kit” to OEMs. While the IBM and Microsoft versions were not identical, they were interchangeable from application perspective. There was no retail MS OS/2 package, and perhaps due to lower interest there also wasn’t a “packaged product” for OEMs (like there had been with MS-DOS since version 3.2).
Numerous OEMs licensed MS OS/2 1.0 in anticipation of it being the wave of the future, as Microsoft and IBM loudly proclaimed. OEM interest persisted through OS/2 1.1, but significantly waned by the time OS/2 1.2 was released. This coincided with Microsoft’s shift of focus towards Windows 3.0.
Pictured above are MS OS/2 1.0 (Epson OEM release) and MS OS/2 1.21 (Tandon OEM release). These were among the first and last OEM releases of OS/2. The Epson version was a relative latecomer, coming out in the second half of 1988. The Tandon version was released in summer 1990, when Windows 3.0 was already on the market. Continue reading
The recently unearthed copy of the near-mythical Multitasking (aka European) MS-DOS 4.0 clearly did not want to be alone. James Lariviere, a kind reader of this blog, provided a disk image of multitasking DOS 4 which was released in 1986 by the French company SMT Goupil.
Microsoft’s contract with Goupil was the main reason why multitasking DOS 4 was completed at all. Goupil was the most important and perhaps even only OEM shipping multitasking DOS 4 (British ICL was the primary customer of the updated multitasking DOS 4.1 in 1987).
The machine that multitasking DOS 4 ran on was the Goupil G4, and a brief look at the machine’s specs reveals why Goupil was interested in multitasking DOS 4: The G4 was equipped with an 8 MHz Intel 80186 processor. Continue reading
About twenty years ago I ended up with a spare ISA graphics card from an upgraded computer. It was a SVGA card based on the Cirrus Logic CL-GD5422 chip, equipped with 1 MB video memory.
This was a very cheap graphics card sold as part of a low-end PC in 1993 by ESCOM, a large European (originally German) PC retailer. It was a basic but hassle-free card, it was no speed demon but did its job well.
Now fast forward nearly twenty years. In the quest for the Ultimate Museum PC, I tried this old VGA card in a 440BX board (Abit BP6). It didn’t work. At all. There was no video signal whatsoever. I assumed that the card was most likely dead, because other (even older) ISA VGA cards did work in the same 440BX system. But I didn’t throw the card out… just in case. Continue reading
I have a problem:
Anyone familiar with 386 LIF (Low Insertion Force) sockets knows that the trouble isn’t installing the processors—that indeed doesn’t require much force and is easy to do. The real problem is getting the processor out without bending the pins and/or damaging the ceramic package.
This got me wondering… surely it would be possible to build a ZIF (Zero Insertion Force) socket for the 132-pin PGA used on 386s, just like the larger sockets used for 486 processors? Is anyone familiar with such a thing? Continue reading
In cooperation with the excellent Computer History Museum in Mountain View, Microsoft released the source code to MS-DOS 1.1, MS-DOS 2.0, and Microsoft Word for Windows 1.1a.
Here’s hoping that this is a sign of things to come and Microsoft will also release the source code to historic versions of Windows 1.x, 2.x and 3.x, further versions of MS-DOS—and maybe even OS/2 1.0!
The poor CHM server is currently suffering from a severe overload so actually looking at the goodies will have to wait… Continue reading
As previously mentioned, IBM’s OS/2 1.0 and 1.1 is extra unfriendly to modern hypervisors. To recap, there is a curious difference between IBM’s and Microsoft’s kernels in OS/2 1.0/1.1 with regard to mode switching.
For reasons that aren’t very clear, IBM’s kernels implement only 286 style mode switching: In order to get from protected back to real mode, the processor is reset and the BIOS told where to resume execution. On the other hand, Microsoft’s kernels have had (faster) 386-specific code ever since the first OS/2 SDK beta from April 1987.
To make matters more interesting, the OS/2 kernel is also famous for using the undocumented LOADALL instruction when running on a 286. Yet IBM’s OS/2 did run on 386 AT clones of the era. How is that possible? Continue reading
The following four processors are much more similar than one might think:
486 aficionados will recognize the processors made by IBM, ST Microelectronics, and Texas Instruments to be essentially one and the same model—Cyrix 486DX. Continue reading
(note this is a guest post by Tenox)
Quite a while ago I’ve came across Opera rendering proxy for mobile browsers. This got me thinking. If you could render a web page on a proxy server to a simplified HTML, say 3.x. This would make a lot of web browsers happy. For some unrelated purposes I have been using webkit2png which allows to create a whole web page snapshot in a single png image. Wait… what if such image had an image map of clickable regions pointing to the original links? Maybe… Continue reading
As the OS/2 museum pointed out, many kids these days don’t really know how to properly use floppies. Fortunately, not all is lost and at least some youngsters know exactly what to do with a 3½” diskette.
First, firmly hold the floppy…
Following is a list of notes describing several less-than-obvious features and characteristics of the Soyo SY-4SAW2 486 VIP motherboard. This is a latter-day 486 board based on the SiS 496/497 chipset, notable for PS/2 mouse support and the ability to use just about any CPU compatible with Socket 3.
Most of these characteristics and limitations are a direct consequence of the use of the SiS 85C496/497 chipset and the way said chipset is configured in the 4SAW2 board. Continue reading