>Hi,
>
>I am having a problem redirecting the printed output from our FPD 2.6 application when user changes from local printer to network printer and back in Windows. For example there might be a local Laser printer and a dot matrix printer with checks in the LAN.
>
>Our application prints all output to LPT1:. With Novell, we redirect by issuing a MAP command from a DOS session.
>

You are in real trouble. It doesn't work as you think in DOS, either. You use NetWare's CAPTURE to assign ports to print queues - MAP handles drive mappings.

If both printers are local, use SET PRINTER to port name within FPDOS. If you use Novell networking, CAPTURE still points a local port to a NetWare-managed remote print queue, and ENDCAP releases it; it can be fired from FPDOS's RUN as long as the server's SYS:PUBLIC directory or the equivalent in an NDS environment is in your DOS search path. If referring to an MS Client, NET USE port name \\ServerName\PrinterShareName assigns the printer port to the printer named PrinterShareName on machine ServerName, and NET USE port name /DELETE releases it. Ask your network people which client is handling the printer if you don't know.

You to learn about your network. You will not be able to guess. Win9x is not DOS, and NT is even less like DOS.

Your network support people should be able to assist in sorting out what type of system provides access to the printer. If you don't have network support people, hire some.

>I haven't figured out how to do this consistently in Windows. I have tried setting up two printers and capturing/uncapturing ports from Windows but it's been trial and error with no repeatabilty at other customers.
>
>This is embarrassing!
>
>Thank you.
>
>Alex