Windows 7: How do I capture lpt1 and send to a network printer

How do I capture LPT1 from an old DOS program and send it to a network printer?

In XP I used the command: net use lpt1: \\servername\printername to capture the printer port. In the Win 7 XP Mode the I haven't figured out what to use for the servername and the printername.

The old DOS program, dBase, runs perfectly. Just need to get the printing working.

Welcome Lindenberg to the windows 7 forums.

When you say that you have a network printer? There is some information missing here. How do you print to it now? Are you an administrator?

Can I assume that you have done a search on microsoft.com using
"how to print to a network print under dos"

or Google... (google is your friend)

Rich

I have to ask...how long are you going to cling to the past?
At least ditch the ancient DOS based version...which has been dead for years.

I am currently using Windows XP and use the net use command to capture the output to lpt1: and this is sent to the network printer. Works great on XP and Windows 7 32bit. The 64bit of Window 7 using the virtual pc and xp mode is the challange.

Every path I followed on Microsoft's site sent me back to how printing works on XP. They don't talk about setting up capturing a printer port in XP Mode and sending the output to a network printer. The problem is on my network the network printer is \\server7\officeptr but in the XP Mode it doesn't understand \\server7\officeptr.

The reason I'm still using this old DOS software is because it runs all areas of my company and fits our manufacturing processes like a glove. There are hundreds of programs. My options are stay with xp, only use 32bit Windows 7, figure out how to get the network printing to work or spend thousands of dollars on new software.

Thanks for your assistance.

Hi there
It's been AGES since I used DOS but is it not possible to send the output to a .PRN type of file and then use normal Windows 7 or XP methods to print the .PRN file out as a standard file.

I think also this piece of FREE software will do it for you if the company is still around

PrintFil: DOS print USB printer | LPT1 to USB, PDF, GDI Windows printing

Hi there again

Made a slight error --it costs around 70 USD but I would think in your case it would be worth it -- saves spending 1000's of dollars(US) and your old software keeps working.


Cheers
jimbo

Looks like this person got at least part way there:
Can't print to network printer through "LPT1:" from MSDOS app in XP Mode

Edit: If you can't get it through XPMode you might want to try DosBox.

And... Sir/Madam, How long do you persist in regaling others who have spent 100's of hours programming in a system, not necessisarily of your liking, because you won't have to waste all of this precious time that you have *not devoted* to?

Hi there
Not sure comments like that are appropriate (logicearth) -- the OP said that his legacy application NEEDS this type of stuff and it's currently too expensive or not practicable to either install a new application (would need to train staff and possibly change the business process in the organisation).

It's very EASY for an individual to go out and say "Ditch the old app -- I'll go and install a new one) --but businesses aren't like that -- some have systems still running that are 40 years old or even older. I can name at least 7 instances where some old IBM Mainframe COBOL is still being used daily.

Most businesses don't have any interest in the computers --they just want the applications to run -- usually as cheaply as possible.

I'm quite sure if the business thought it was worthwhile to change the application plans would already be in hand to do it.

I'd go about it this way

1) forget Virtual PC and XP mode -- run a fully blown XP virtual machine on say vmware player or vbox -- both FREE . Install your Dbase software on the XP VM.

2) Now you CAN share printers between XP and Windows 7 (32 / 64 bit mix) -- I posted a thread on how to do this on these Forums.


Read my post (nr 3 ) in THIS thread

Networking from Printer attached to Win XP PC to Win 7


Problem solved !!!!



Cheers
jimbo

Right, because old stuff continues to work...One day the OP is going HAVE to upgrade, one day it is going to be forced. It would be in the best interest for the OP to start planning for the long term. Find alternatives and means of updating their stuff, because there will be a time when they will be forced and that will be more expensive then anything now.

For example, those old IBM Mainframes you mentioned when they start to break down (they WILL break down), RAM goes bad, Motherboards and chipsets etc. The cost of repairing those systems makes buying a whole new infrastructure the cheapest alternative. The same goes with software, technology changes quickly over time, serial and parallel ports for example have all but left the newest computers in place of a new connection. It will continue to happen, and operating systems will continue to drop support for the older technology as time passes. Either you keep running on 100 year technology and hope it doesn't break down or you start planning to upgrade things gradually.

Lindenberg: I just tried your net use command on my virtual XP machine and it worked just fine. (net use LPT1: \\print1\publishing) Question... Has your Virtual xp been joined to the domain?

logicearth: I'm sure you're trying to be helpful, but I've owned my own businesses before and once you have a system working just the way you want it, it's more like a last resort to change systems... Think of it like this: I have a 15 year old car that has 200k+ miles but I take good care of it and it's running fine. Then something breaks... Does that mean I should get a newer car because eventually I'll have to anyway? Not unless whatever broke is really expensive. Also, he didn't say his hardware was old, just that he wants to run an old DOS program. Unless the media gets corrupted or Windows no longer will run it, it shouldn't break. He may outgrow it eventually, but if he can get this working, he'll save a ton of money and a lot of headaches for now...