Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!homxb!whuts!mtune!westmark!dave From: dave@westmark.UUCP (Dave Levenson) Newsgroups: comp.dcom.lans Subject: Re: LAN print problems with Lotus 1-2-3 Message-ID: <301@westmark.UUCP> Date: 10 Dec 87 02:23:27 GMT References: <1857@cup.portal.com> Organization: Westmark, Inc., Warren, NJ, USA Lines: 25 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. ... What (the devil) happens when you try to print? What is the failure? In our limited experience with MS-DOS networked printers, we find that if an application writes to stdprn, it is writing to a spool file on the network print server's disk. When the application program terminates, MS-DOS catches the termination signal, and sends a signal to the print server telling it to close the spool file and queue the print job. 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. -- Dave Levenson Westmark, Inc. A node for news. Warren, NJ USA {rutgers | clyde | mtune | ihnp4}!westmark!dave