>A legacy FP2.6 DOS app is required to print across sundry networks. Virtually all my customers workstations are now running XP pro SP1. 50% have no problem whatsoever. The other 50% require almost completely arbitrary fixes before I can persuade them to print across their networks. Examples include having to install the Foxprox development environment and run the app through that. (Which made me think it was a FOXUSER issue but swapping FOXUSER files didn't help) Elsewhere, I have had to include an explicit "NET USE" command (on Novell nets). And so on.
>
>There is one workstation I just cannot fix. It is one of a pair on the smallest network (Windows) I manage. There was no problem up until this week when I re-installed both machines after a complete manicure and OS reinstallation to fix unrelated problems with system stability (anti virus software refusing to update and stuff like that). Now everything works in the windows environment (i.e. we can print across the windows network to the shared printer from windows apps) but I cannot print across the network from ANY DOS app. And none of the usual tricks are working.
>
>In the recent past, when you installed a network printer under windows, it asked you if you wanted to print from DOS. XP no longer asks that question and I can't figure out how to check if that functionality is enabled, irrelevant or what.
>
>Anybody got any suggestions?

You can run a command like the following from a command prompt (or login script, .CMD file, whatever) to redirect DOS LPT port(s) to network print queues:

NET USE LPT1 \\ServerName\QueueName /persistent:y