Xref: utzoo comp.protocols.nfs:29 comp.sys.ibm.pc:20904
Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!pasteur!ucbvax!amdcad!diablo.amd.com!phil
From: phil@diablo.amd.com
Newsgroups: comp.protocols.nfs,comp.sys.ibm.pc
Subject: PC-NFS net print bug?
Message-ID: <23464@amdcad.AMD.COM>
Date: 5 Nov 88 03:06:08 GMT
Sender: news@amdcad.AMD.COM
Reply-To: phil@diablo.amd.com ()
Organization: Advanced Micro Devices, Inc. Sunnyvale CA
Lines: 26


I have an Easy Data AT clone running at 12.5 MHz with a WD 8003
Ethernet interface connected to a thick wire network and a Logitech
Mouse. The clone is running PC-DOS 3.3, PC-NFS 3.0, and Microsoft Word
3.0. When I use "net print", it goes to a Sun-4 which hands it off to
a microvax running 4.3 BSD which drives an Apple LaserWriter over a
serial port.  Both of the Unix hosts have Sun's transcript installed
and running. 

This combination works well most of the time.  Word files have to be
printed in PC-NFS's "postscript" mode, as Word doesn't stick on the
complete header needed. PC-NFS's "net print" is claimed to have the
capability to do this for you, and it usually works. However, when I
try to print a Microsoft Word file that is only one page long, it
usually doesn't work. Net print will either just hang forever (
sometimes CTRL-ALT-DEL doesn't even work), or say "null pointer
assignment", or "divide by 0". 

I can usually get around the problem by sticking some extra junk and
empty lines in to make it two pages.  However, this seems undesirable.

Any comments or cures?

--

Phil Ngai, phil@diablo.amd.com
{uunet,decwrl,ucbvax}!amdcad!phil