Yep, Norton Did It

Some time ago, the question of the oldest executable compression tool came up. EXEPACK was identified as a widespread and unexpectedly troublemaking specimen, but Realia SpaceMaker was reportedly older.

Only initially no one could come up with surviving executables compressed with SpaceMaker that were demonstrably older than EXEPACK (leave alone find old versions of SpaceMaker itself), although there were several unconfirmed hints that early versions of Norton Utilities used SpaceMaker.

Eventually an old executable compressed with SpaceMaker turned up: DVED.COM from September 1983, pre-dating the 1984 EXEPACK. But did Norton Utilities really use SpaceMaker?

Jeff Parsons of pcjs.org has now unearthed excellent circumstantial evidence: On floppies distributed with the Summer 1983 copies of the PC Disk Magazine, there were utilities authored by Peter Norton (though not specifically anything from the Norton Utilities). And those executables by Peter Norton were compressed with SpaceMaker.

In the meantime, the OS/2 Museum came into the possession of an image of an actual Norton Utilities 2.01 floppy. The files on the floppy are dated July 4, 1983, and yes, most of them are compressed with SpaceMaker. They contain the ‘MEMORY$’ signature near the beginning, and a decompression stub at the end. The rumors about Norton Utilities and SpaceMaker were true.

At this point, it is then known that yes, Peter Norton really used SpaceMaker for early Norton Utilities, and yes, SpaceMaker is really quite a bit older than EXEPACK; SpaceMaker may be considered the oldest known executable compression utility.

Posted in Compression, PC history | 6 Comments

My Second AMD

A few weeks ago I became a happy owner of a ThinkPad A485, the first ThinkPad (together with the E485 and related variants) to use an AMD CPU. History buffs will know that it’s far from the first ThinkPad with a non-Intel CPU; the very first ThinkPad-branded laptops (ThinkPad 700/720 in 1992) used IBM’s own 486 SLC and SLC2 processors, the 1995 ThinkPad 365 used Cyrix Cx486DX4 processors, and the 1996 ThinkPad 365E sported the IBM-built Cyrix 5×86. But for over 20 years, ThinkPad meant Intel, until the Summer of 2018.

What I just realized is that the A485 is only the second AMD-based machine I ever bought. The first one was a Lenovo IdeaPad Z75 in 2014, a laptop with an AMD A10 APU based on the infamous Bulldozer microarchitecture. Ironically I never had any real complaints about the Z75’s CPU, but the low-res display was absolutely horrible and made the laptop too painful to use very often. Continue reading

Posted in AMD, PC history, ThinkPad | 38 Comments

A Piece of History

A few months ago I received a well-used but not abused copy of Rakesh K. Agarwal’s book 80×86 Architecture and Programming (Volume II): Architecture Reference, published by Prentice Hall in 1991. This is an unusually well-informed book, no doubt because Agarwal was a member of the team that implemented the 80386 at Intel, and wrote some of the 80386’s microcode himself. The book is notable for being the second and only volume of a series (Volume I was apparently never published). Agarwal is also a co-author of an informative article titled The Intel 80386—Architecture and Implementation, published in the IEEE Micro magazine in December 1985.

80×86 Architecture & Programming Vol II

My copy  80×86 Architecture and Programming (Volume II): Architecture Reference came with handwritten notes sprinkled over various bits of the C-like pseudo-code that the book uses to explain the workings of the 386 microcode, as well as several explanatory notes in the instruction reference section. Continue reading

Posted in 386, Books, Cyrix, Intel, PC architecture, PC history | 6 Comments

DiskOnChip

This is a guest post by Nils aka stecdose

What Is DOC?

I would like to present a „storage card“ for the XT bus (8-bit ISA bus) that I built from scrap parts. It is based on a small device called DiskOnChip, or DOC.

8-bit DOC Card

DOC-based storage card

I have been using the card for about 3 years now and it has proven to be quite a handy tool. The storage card shows up as drive C: in a system and it is even bootable! Continue reading

Posted in Hardware Hacks, PC hardware | 11 Comments

FasterModeSwitch: Is It Really?

Short answer: Yes.

Before launching into the long answer, let’s recap what it even is. FasterModeSwitch is a SYSTEM.INI setting in Windows 3.1 which applies only to Standard (286) mode and can therefore be found in the [standard] section of the INI file. KB article Q83387 describes the setting accurately and explains everything… except what it actually does.

Here’s what Microsoft had to say on the subject: Enabling this setting causes Windows running in standard mode to use a faster method of switching from protected to real mode on many 80286-based computers. When this setting is enabled, Windows responds quicker to hardware interrupts, allowing better throughput for interrupt-intensive applications, such as communications applications. In addition, you should enable this setting if you are using a Zenith Z-248 system and are losing characters while typing, or if you are using an Olivetti M-250-E and lose control of the mouse.

Note: This setting has no affect [sic] on 80386-based computers. Some early IBM-AT and compatible computers do not have the BIOS support necessary to use this setting. Enabling this setting on these computers may cause them to hang when starting Windows.

The upshot then is that enabling FasterModeSwitch either speeds up Windows 3.1 or hangs it, depending on the machine’s BIOS implementation. Now, what does the setting really do, and why is the behavior system specific? Here’s the long answer… Continue reading

Posted in 286, BIOS, Microsoft, Windows | 10 Comments

Didn’t Expect That to Work

Once the ThinkPad T43p with a bad fan was in working shape again, I restored the preloaded software on it. Which meant Windows XP (this is a system from 2005).

It didn’t take long for me to establish that XP is really hard to use these days. Even Firefox doesn’t support it. Getting any kind of halfway modern software running on XP is simply a no go. After reading about fairly good experience with installing Windows 7 on T43/T43p, I decided to go the same route.

I happened to have a burned DVD with Windows 7 Ultimate lying around, so I tried that. After installation, there was no WiFi, but there was wired Ethernet—good enough. Windows Update successfully installed drivers for WiFi, graphics, and a number of other devices. The rest (power management, fingerprint software, hotkey OSD) I grabbed from Lenovo.

Once I was done, I had a reasonably functioning laptop (surprisingly well functioning for a 13-year old machine) with just one small problem—no Windows 7 license. The T43p obviously came with an XP Pro license. And I would probably be able to scrounge a Windows 7 Pro license, but I installed Windows 7 Ultimate without thinking much about the problem. Is it even possible to buy a Windows 7 license these days? Continue reading

Posted in ThinkPad, Windows | 22 Comments

Crazy World

After I successfully upgraded two Windows 10 VMs to the 1809 release at the beginning of October, I tried to do the same with more VMs and an actual laptop this week. But I couldn’t, no update was offered. While trying to find out how to install the 1809 update, I found out why I couldn’t—Microsoft withdrew it after the update, among other things, deleted users’ data.

Reading about the details left me stunned (though only momentarily, and now I can write about it). The complaints included this now-famous gem: “I have just updated my windows using the October update (10, version 1809) it deleted all my files of 23 years in amount of 220gb. This is unbelievable, I have been using Microsoft products since 1995 and nothing like that ever happened to me. […] I am extremely upset. Not sure what to do….please let me know.”

One would like to answer “easy—just restore the files from your latest backup” but that could perhaps be construed as insensitive.

The fact that someone has been using PCs for 20+ years and still hasn’t figured out that yes, your data can and will go poof is just mind-boggling. External hard disk? NAS? USB stick or two? A cloud backup if there’s nothing else? There are so many options. And are there really people so lucky that in over twenty years, they never had a bad sector on a hard disk, never a bricked SSD, never an accidental file delete caused by a slip of the finger? That’s amazing luck.

But then there is the other side of the story. Files got deleted because of confusion caused by “Known Folder Redirection” aka KFR, which manages to make symlinks look good. The key takeaways are that a) the complexity of Windows is out of control (not news, I know), and b) someone at Microsoft thinks that upon encountering a set of unknown user files, deleting them without asking is an appropriate response. That’s just… wow.

It also turned out that the file deletion bug was reported months ago but ignored, presumably (speculation on my part) because it was a) lost in the deluge of low-quality bug reports, and b) only affected a tiny fraction of users with who were convinced that there was nothing special about their configuration and anyone not seeing the bug was either not looking hard enough or lying. That at least is not surprising.

Posted in Bugs, Microsoft, Random Thoughts, Windows | 9 Comments

ThinkPad Fan

I suppose I am one, but recently I had trouble with the other kind of a ThinkPad fan. An elderly ThinkPad 43p with a 2.13 GHz CPU (Dothan Pentium M with 2MB L2 cache) and a rather nice 1600×1200 IPS screen (hello, 2005!) was effectively unusable due to a near-dead fan. At startup, the laptop almost always complained about a fan error and turned itself off. Pressing Esc made it possible to get past the error, but as one would expect, the laptop got very uncomfortably hot.

Upon closer examination, it turned out the fan was beyond repair. It was so worn out that as soon as it started spinning at higher revs, it began vibrating so badly that it stopped again. Not really fixable. But finding a new (that is, old but unused) fan assembly wasn’t hard, so I thought I’d just swap it out.

This is in theory not overly difficult, as only the ThinkPad keyboard and top bezel need to be popped off the laptop, which involves removing about 15 screws from the bottom of the unit. The screws are well labeled and the process is well documented in the HMM (Hardware Maintenance Manual).

Copper fan/heatsink assembly in a T43p

Trouble hit when I tried to remove the old fan assembly, held in place by three screws. The screws weren’t difficult to remove, but the fan was stuck fast. It was apparent that the heatsink effectively glued itself to the GPU (ATI Mobility FireGL V3200 aka Mobility Radeon X600, a PCI Express chip with 128MB video memory). For whatever reason, IBM used thermal paste for the CPU but a thermal pad for the GPU, possibly because the GPU comes with a heat spreader and the CPU doesn’t. The thermal pad turned into surprisingly good glue. Continue reading

Posted in Hardware Hacks, IBM, ThinkPad | 4 Comments

The History of a Security Hole

Warning: If you do not care for the finer points of x86 architecture, please stop reading right now—in the interest of your own sanity.

A while ago I was made aware of a strange problem causing a normal user process running on 32-bit i386 OpenBSD 6.3 to crash the OS (i386 only, not amd64). The problem turned out to be a security hole with history that goes back more than three decades.

The crashing code looked like it didn’t really have any business crashing, but the CPU was in a very odd state with inaccessible kernel stack and GDT (that’s extremely unhealthy because exceptions and interrupts cause triple faults and CPU shutdown).

After much head scratching, I noticed that the (virtual) CPU’s A20 gate was off. That’s a big no-no because when the CPU is in protected mode, turning the A20 gate off has very nasty, unpredictable, and system-specific consequences. It’s one of those Just Don’t Even Try That things. But could a user process really turn off the A20 gate? That makes no sense.

As it turns out, a user process really could do that on i386 OpenBSD 6.3 (again, i386 only, not amd64). A security hole allowed regular user processes to read and write many I/O ports, which is obviously very unhealthy. The chain of events that led to this is long, and probably the biggest player in it is Intel, with important contributions from NetBSD and OpenBSD developers. Thanks to the nature of open source, we can trace back exactly how it came to be, and perhaps even learn a thing or two from the mistakes. Continue reading

Posted in 386, BSD, Bugs, Documentation, PC history | 44 Comments

A Sound Card Before Its Time

A mysterious full-length sound card recently arrived at the OS/2 Museum. It was clearly manufactured by IBM in 1985, and sports a 20 MHz Texas Instrument TMS32010 DSP (the DSP is the large black DIP chip near the lower left corner, not the ceramic gold cap chip).

A curious 1985 IBM sound card

The card has a FCC ID sticker, which is usually a good way to identify hardware:

A suspicious FCC ID sticker

The FCC ID is ANO95A6450611… which apparently does not exist. However, ANO9SA6450611 does. It is hard to say whether the typo is on the IBM card or in the FCC database. Either way, it’s an IBM FCC ID… from 1988. On a card made in 1985. If we discount time travel, there must be some other explanation. Continue reading

Posted in IBM, PC history, Sound | 20 Comments