hadgraft@civeng.monash.edu.au (Roger Hadgraft) (08/04/90)
Novell Netware 2.10 + Win3 in enhanced mode - junk going out to network printers. I have a 386 running MS-DOS 4.00, Windows 3 in enhanced mode, and Novell Netware 2.10 with version 3.01 of NET4 and IPX. When I direct output from Windows apps to one of the network printers (I've tried both a Postscript laer printer and an HP LJ Series II), various junk gets appended and prepended to the actual output. A 1K file which properly translates to a 10K postscript file is appearing as anything from 63K to 94K! I've just switched over to Standard mode for Win3, and there appears to be no such problem. Likewise, I have had no problem with my 286 (in standard mode). Last week I upgraded the machine to DOS 4.00. I don't think I had any problems with DOS 3.30, but I can't be sure. Has anyone else experienced this problem? Is DOS 4.01 a solution? -- Roger Hadgraft | hadgraft@civeng.monash.edu.au Lecturer in Civil Engineering | Monash University | phone: +61 3 565 4983 Clayton, Vic. 3168. Australia. | fax: +61 3 565 4944 or 3409
laughner@news.nd.edu (Tom laughner) (08/08/90)
From article <38342.26bafa3f@vaxc.cc.monash.edu.au>, by hadgraft@civeng.monash.edu.au (Roger Hadgraft): > Novell Netware 2.10 + Win3 in enhanced mode - junk going out to network > printers. > > I have a 386 running MS-DOS 4.00, Windows 3 in enhanced mode, and Novell Netware > 2.10 with version 3.01 of NET4 and IPX. When I direct output from Windows apps > to one of the network printers (I've tried both a Postscript laer printer and an > HP LJ Series II), various junk gets appended and prepended to the actual output. We've been running Windows in enhanced on Novell testing with DOS 4.0, DOS 4.01, and DOS 3.3. The only difference is we're using Netware 2.15. We've had no problems printing under Windows applications or non-Windows applications. We're using an HP Laserjet II. Tom Laughner DOS Consultant/Analyst University of Notre Dame (219) 239-8270 TLAUGHNE@IRISHVMS
altman@sbpmt.cs.sunysb.edu (Jeff Altman) (08/08/90)
This message is empty.