

This causes a problem because they are open-drain/open-collector outputs, so something needs to pull them up when a high value is needed. First of all, their bidirectional control pins (strobe, auto/linefeed, initialize, and select printer) do not have pull-up resistors. The PLX-based cards throw a couple of curveballs into the picture, though. I’ve tested them on my desktop computer with Windows 7 64-bit (my DLL) and my laptop with Windows XP (Ben’s DLL).

The Syba cards both use Moschip (now ASIX) chipsets, while the Shentek and StarTech cards use Oxford (now PLX Technologies) chipsets.īoth of the ASIX-based cards seem to work fine with no messing around needed. My experience with these is the following.

My remapped io.dll (uses TVicPort for port access).

There are replacement versions of io.dll that trick the Willem software into talking to a different parallel port address: The good news, however, is that it does its port access through a DLL called io.dll. Unfortunately, the Willem software only lets you pick from a hardcoded list of addresses to work with. Add-on PCI/PCI Express/ExpressCard parallel ports don’t use those addresses. You can find add-on parallel port cards, but a good chunk of today’s software is written to work directly with the parallel port addresses that were found on motherboards of older computers (0x378, 0x278, and 0x3BC). Traditional Willem EPROM programmers require your computer to have a parallel port, and almost no computers today have them. My previous blog posting on this subject from a few years ago sparked quite a bit of interest, so I’d like to follow it up with the latest compatibility information I have.
