That's an option, yes, but not one I normally use. I find that in many cases with legacy apps the user needs to print to a server queue *only* for the legacy app. When done there they want to go back to printing from Windows apps to a local printer on that same LPTx: port.

Legacy app startup batch files can be something like

NET USE LPTx: \\ServerName\QueueName
MyFPDOSApp.EXE
NET USE LPTx: /DEL

Also, setting up appropriate port mappings in the logon script is usually a good idea. Simply doing it once then relying on the /Persistent switch ends up causing support calls when Windows loses its memory.

>Also add on: /Persistent:Yes
>to the net use command.
>
>:o)
>Tracy
>
>>>Is it possible to print to a network printer in 2.6? The code currently allows the user to select which lpt to print to:
>>>set print to &pt (pt = 'lpt1' or 'lpt2')
>>>
>>>How would I use the code above to print to a network printer?
>>
>>If it's FPDOS you need to "map" a network printer (or queue) to a local port. On Microsoft networks you can issue the following from a DOS box:

NET USE LPTx: \\ServerName\QueueName

This command can be included in a logon script or as part of a batch file that starts up a FPDOS app.