windows xp - DOS legacy application with USB printer -

The unfortunate task of doing (minimum) maintenance work on two heritage applications developed in DBII + + / K8PER.

I have full access to the source and if there is a minimum toolchain for compiling the application, if needed Due to various (most psychological) reasons from the main user, I do not have permission to complete it again from scratch.

Anyway, while applications work fine under XP, hardware support is a home work user failure printer (an old effect HP with parallel interface) and 486 (!) Desktop Changes where applications are hosted.

The main problem is now to find a printer that can be used under XP, probably the USB (ASUEEEE box will be perfect, and it does not play parallel port) and it is called "visible" Makes it

So far I have found a workaround:

Plus some utilities:

Utilities Looks better because they offer some sort of filters for the old escape sequences (epson or HP's bid for EPS / P), making the printer transparent. Either they say, at least

then the question is: Is there any experience to distinguish between old dos programs with old printers under XP? Any warning? Have you used one of the utilities listed (or some other I have not searched for yet) and if so, what would you recommend?

We usually refer to one of your links. That is, under Windows, the printer wants to install itself on any port (ie: USB etc.).

Next, share the printer (we say that the workstation is called Computer 1 and your share is HPPR).

Create a batch file to launch the next app, it should look like this:

  Pure use lpt1 / d net use lpt1 \\ COMPUTER1 \ HPPRINTER & lt ; Yourapp.exe & gt;  

The output is set to LPT1 in your app.

Other, there are more complex solutions, but this is the easiest. We still have a DOS app that was made years ago, we still actively market and sell. In this way we handle print. it works very well. Now you can get additional benefits of using Windows for the print print queue, so that you can prevent printer queues and more. The printer may also be closed or out of paper and still jobs in the Windows Spooler can be queued.

Warning: It assumes that the output will be supported by new printers. If this is the 'old' HP laserjet then it is probably PCL 5, find a device that supports PCL 5 and you are away.

In the case of filtering, it is not sure why you need it, as long as the output PPL or PostScript or any other standard, you can find a printer that supports identifying the printer should be able. If you are worried then add a comment about the current device and I can provide ideas as compatibility as we deal with this daily.