pawan@cunixc.cc.columbia.edu (Pawan Misra) (12/20/89)
Has anyone seen PC-NFS 3.0.1's print redirector drop escape characters when
sending data to pcnfsd? Is this a known bug? Or is it "yet another
feature" (tm)? This only seems to happen with 3.0.1; PC-NFS 3.0's prt.exe
appears to work fine.
PC Hardware: 286 machine with a 3C503 board running PC-NFS 3.0.1. Also
happens on a 286 machine with a WD8003E board running PC-NFS
3.0.1 Does *NOT* happen on 286 and 386 machines with 3C503 and
3C501 boards running PC-NFS 3.0.
Unix Hardware: Sun Sparcstation I running SunOS 4.0.3c. Printer is an HP
LaserJet II off a serial port.
Repeat by: If running PC-NFS 3.0.1 print a file from inside Microsoft
Word (ver 4.0) on the PC. Take a look at the file pcnfsd
puts into /usr/spool/pcnfs/`pc-hostname`/... All escape
characters are missing from both the font download and the
actual text. Plus, ( and this makes no sense ), the font
download appears *after* the actual text itself--it's
almost like prt.exe is reversing the order.
(One) Fix: If you have have PC-NFS 3.0 somewhere, copy over the print
redirector "prt.exe" to your PC-NFS directory, and reboot
your PC. Print again. A look at the file(s) will show all
the right escape sequences are present ( in both the font
download and the actual text itself ). The file will print
normally.
pawan.
#include <std-disclaimer.h>
Internet: bond!pawan@bellcore.com, pawan@cunixc.cc.columbia.edu
Usenet: rutgers!bellcore.com!bond!pawan, {rutgers,topaz}!columbia!cunixc.cc.columbia.edu!pawan
Bitnet: pawan@cunixc.bitnetgeoff@hinode.East.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top) (12/20/89)
Quoth bond!pawan@bellcore.com (in <2520@cunixc.cc.columbia.edu>): # #Has anyone seen PC-NFS 3.0.1's print redirector drop escape characters when #sending data to pcnfsd? Is this a known bug? Or is it "yet another #feature" (tm)? This only seems to happen with 3.0.1; PC-NFS 3.0's prt.exe #appears to work fine. Check out the documentation and the NFSCONF help screen for the various printer modes. In 3.0.1 we added some filtering to the standard text mode because various applications were blowing TranScript away, then we added a "raw" mode for those apps and printers which want to pass every single byte. Geoff