Path: utzoo!utgpu!water!watmath!clyde!rutgers!mit-eddie!uw-beaver!tektronix!reed!tessi!aardvark!steve
From: steve@aardvark.UUCP (Steve Willoughby)
Newsgroups: comp.dcom.lans
Subject: Re: LAN print problems with Lotus 1-2-3
Message-ID: <121@aardvark.UUCP>
Date: 14 Dec 87 08:19:38 GMT
References: <1857@cup.portal.com> <301@westmark.UUCP>
Reply-To: steve@aardvark.UUCP (Steve Willoughby)
Organization: None to speak of
Lines: 37

-In article <301@westmark.UUCP> dave@westmark.UUCP (Dave Levenson) writes:
->In article <1857@cup.portal.com>, David_J_Buerger@cup.portal.com writes:
->...
->> I've had a devil of a time getting Lotus 1-2-3 to print on
->> a Novell LAN.
->
->...we find that if an application writes to stdprn, it is writing to a
->spool file on the network print server's disk....
->If the application program finishes writing to
->stdprn but doesn't specifically close the output file, and doesn't
->return control to MS-DOS, then the spool file remains open, and no
->printing occurs until the application actually exits.
->
->If this is what's happening, try a Shift-Control-PrtSc.  I'm not
->familiar with Novell, but on AT&T Starlan, that causes the stdprn
->output to be flushed and printed without waiting for the process to
->terminate.

For Novell, you might make sure you are starting off with 
the SPOOL command (which routes stdprn (LPT1) requests 
to a network printer spooler.

Make sure that when your application finishes, you issue the
ENDSPOOL command at the DOS prompt.  Hopefully this
will start the output printing on the network printer.

Hope this helps

--steve

------------------------------------------------------------------------------

-- 
Steve Willoughby       |  "You will, I am sure, agree with me that if page
...ihnp4!tektronix!    |  534 finds us only in the second chapter, the length
tessi!aardvark!steve   |  of the first one must have been really intolerable."
                                -- Sherlock Holmes, in The Valley of Fear