Printing from dos on windows xp

So, DosPrint doesn't even have to be uninstalled later on. For more info about how to uninstall them please refer to the documentation installed with those programs and their websites. DosPrint is free , both for private and commercial use. Please see the License. Since it doesn't need to be installed on your machine simply run the DosPrint. If instead you've questions or need support for configuring the preferred DOSBox variant you've installed, please note we didn't write them ourselves , they're third-party software available on the internet, so, please contact directly their manufacturers as indicated in the documentation installed with those programs and their websites.

If you need help with the Printfil program, you can contact the Printfil support at this link. We respect your privacy ; your data will be treated in accordance with the law. See our privacy policy. New DosPrint 1. Ask a question.

Quick access. Search related threads. Remove From My Forums. Asked by:. Archived Forums. Sign in to vote. I couldn't find a better location to post this question, so I figured this was as good as any, since I am running SP3 on the computer having the issue. We have an old DOS program that we run within our company.

The program prints to network printers by mapping the local lpt1 or lpt2 port to a shared printer on a print server. This has always worked fine. We have a couple of instances where we have users outside of the company run the application via Citrix. Hey, I have weird friends who do mind-boggling to me things! Anyway, if you've just been using the parallel port connection, perhaps you should try eliminating that and using the USB connection.

That's all I have experience with local printer-wise under Windows XP. I would be interested to see what happens if you share the printer and use the UNC method of designating the printer as the target for a copy command. The specificity of your problem with printing to this particular local printer from the command line in Windows XP makes me think that the problem may be particular to the printer driver, or at least to the combination of Token Ring networking and the printer driver.

It sounds like you may have already ruled out the latter, but you do need to rule out every possibility step-wise. Even if it appears that the networking is eliminated from consideration as a possible cause of the problem I would be very interested to see if this printer will accept a print job from the Windows XP command line when no networking is enabled at all.

It's a possibility that I would at least consider -- and definitely would rule out before spending much more time on the issue, if I were you. Hehe, yeah, it's only hooked to the parallel connection. However I'm unfamiliar with "UNC". Of course that system runs different printers and all too though.

I didn't want to get into that too much, as too avoid confusing the issue. Anyway, I'll try disabling networking all together and see what that does. BTW, I just tried it after changing the printer settings to force it directly to the printer and get access denied. Hey, sorry, but I had to ask. Didn't want to make any assumptions. Like I said, I've got friends that do the strangest things! I haven't seen the problem posted until I ran across your thread here.

But, to be honest, I hadn't tried it until I saw this thread, either. But it has worked just fine on every Windows XP system I've tried it on yesterday and today. None of them have had printers attached to their parallel ports. All printing has been to the UNC path specification to shared printers.

Not one has failed. One thing I can tell you, and I think I may have mentioned it earlier, is that I wouldn't expect this to work with PostScript printers. Your printers wouldn't all be PostScript printers, would they? I know it's weird for me to ask, but it's just one possibility that the tiny voice in the back of my head wants to rule out. Given this information I suspect that you are right.

But the fact that you have the problem at home on an ordinary P2P LAN topology as well as at work on a Token Ring network makes me think along other lines. This is exactly the sort of thing that might happen to me. I'm very consistent in the way I go about setting up systems. I'm beginning to wonder if there might be some commonality among all of the systems with which issuing print commands from a command line doesn't work.

All of mine work, so that tends to make me think that this a is something that you install on or do to your systems that my systems don't have in common, b is something to do with printers connected to parallel ports of which I have none , c is something to do with common differences between the printers themselves.

I don't believe that your Lexmark printer is a PostScript printer, though I didn't look it up to be certain. That seems to leave us with "a" and "b", unless I'm missing something? If someone sees another possibility here, I hope that person will speak up. In the meantime, I'll see if I can find anything on the use of parallel-connected printers from the command line of Windows XP and Windows , too, right?

I'm not sure what you mean by this. What did you do exactly? I keep on getting the feeling that we're missing something obvious, but I cannot for the sake of my life figure out just what that would be! But I will hang on doggedly as long as I think we've got a hope of figuring this thing out!

Hehe, I know you were just covering all basis and got a chuckle out of it. I went into the printer's properties and selected "Print directly to printer" vs "Spool print documents so program finishes printing faster". And yeah, I agree that it's most likely something simple that we're missing. Just wish i knew what it was. But consider this, the new Dell was just delivered last week. I had already been playing with the program, that I want to eventually get to printing under WinXP, at home and had ran into this problem along with a couple others.

I had also already been in contact with a member of the Lexmark support team and he had assured me that it would not be an issue with the Z It did not work then either. This was prior to making the connection to the LAN, now that I think about it. So I just don't know.

The reason I got the Z55 was because it is one of a very few printers that still has a parallel connector. It does however support "Queue" as well as parallel, so if i were able to get it working on the USB hookup then I should be able to map the printer to either a LPT port or use the Queue.

As to my systems at home. The Canon also has both parallel and USB connections. Do you want to retry or cancel? I haven't tried any others but will in a bit. This is on the laptop running Win2K. Also, my hands are tied for the most part on the laptop, from a testing standpoint, because I only have "Power User" status on it and don't have alot of room to work as a result. I'm at a loss as to what's going on here. BTW, The linux box also dual-boots Win I installed the HPC directly on it and prints fine from the command prompt inside Win98, go figure.

I also done a little digging around in the XP registry and found some settings named "DosPrint", they were all set to "no".

I changed them to yes but it didn't make any difference. And thanks for hanging in there trying to help me resolve the issue, it's very much appreicated.

I removed the parallel connected one and now it does the exact same thing when hooked up to the USB port as it did with the parallel. The hairs on the back of my neck are standing up because I expect someone to come along, read this thread, then issue the standard verbal dimwit smack to our foreheads and point out what we're missing.

And that would be welcome, BTW. I can't help but think this has more to do with permissions than with any underlying problem with Windows XP being told to print from the CMD prompt. Let me ask you this. How was the test. Could you be getting the Access Denied message because of a permissions issue with the test file?

After seeing your list of printers I am sure that none of them are PostScript printers unless you can get it as an extra cost option on those printer models , so that has nothing to do with our puzzle, I think. I still don't understand the "Local Downlevel Document" message. That's not a message I've seen in my own use of this OS.

It sounds like the OS is saying that the document is coming from a system running an older version of Windows.

Is the history of your test file perhaps significant insofar as this message is concerned?