Xref: utzoo comp.protocols.nfs:1683 comp.windows.ms:8464
Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!caen!uflorida!travis!hardy!dana
From: dana@hardy.hdw.csd.harris.com (Dan Aksel)
Newsgroups: comp.protocols.nfs,comp.windows.ms
Subject: Re: PCNFS printer and MS Windows 3.0
Message-ID: <2064@travis.csd.harris.com>
Date: 16 Jan 91 13:40:13 GMT
References: <9762@cica.cica.indiana.edu>
Sender: news@travis.csd.harris.com
Reply-To: dana@hardy.hdw.csd.harris.com (Dan Aksel)
Followup-To: comp.protocols.nfs
Organization: Harris Computer Systems, Fort Lauderdale, FL
Lines: 14

In article <9762@cica.cica.indiana.edu> wcwang@cica.indiana.edu (Bill Wang) writes:
>I couldn't quite get the remote printing working on PCNFS within
>Windows 3.0.  It did work outside the WIN3.0 environment.
>Basically, I put 'net use lpt2: \\server_name\printer_name'
>in network.bat.  Window 3.0 applications couldn't print off
>lpt2 at all. Any help would be appreciated.

In WINDOWS 3.0, Printer Congigurations, change port from LPT2, to LPT2.OS2
This tells the print manager or spooler to hand the output data over to DOS and
allow the operating system to control the printer handler for you.

We do it here, works like a champ.
--------
Dan Aksel