Printing Problems

[unit512]

Ah yes...what a sweet mixture:<br>
Novell 4.11, Windows 9X work stations and DOS printing.<br>
<br>
Had a situation where PC A was running Nprinter so A and PC B could share the printer...under DOS. All was fine.<br>
<br>
Took PC A away and replaced it with a PIII PC. DOS still worked..but DOS jobs would not come out of the printer until a new DOS job was started or the DOS program was exited. I played around with Capture (FF NFF etc) and the Windows Properties/Details/Spool Settings. NO LUCK.<br>
<br>
Turned off NPRINTER and set up Windows Printer Sharing. This meant -- on PC A the printer now went to LPT1: instead of a queue. After unchecking the boxes under Printer/Properties/Details/Port Settings ... this printer start to send out ALL DOS jobs properly.<br>
<br>
However PC B...now printing to a Windows 9X queue can still not get the job out until the software is exited or another job is sent behind it.<br>
<br>
Anyone have any ideas?<br>
<br>
I can go back to NPRINTER if necessary (Tried WinNprinter, but it would not load properly)

 

[Westonbirt]

I am running 4.11 with 75 Win95 clients, and no problems.<br>
<br>
I had printer problems, it would be interesting to know what printers you are using and the driver used.<br>
<br>
My problems were got over with a HP Jet Direct card and software driver changes. 2.600 pages printed from 1 HP C2000N in the last 14 days.<br>
<br>
send me details as above and I may be able to help<br>
<br>
Regards<br>
<br>
John

 

[Technician]

Computers are weird and wonderful both at the same time.<br>
<br>
The joys of solving complicated problems have intrigued me to no end.<br>
<br>
Things to try:<br>
<br>
1. Turn off Parallel Port mode ECP. ECP uses DMA 3 and I have had nothing but problems using ECP. Try EPP, SPP or compatible (whichever your BIOS calls it). Windows should detect new parallel port upon boot.<br>
<br>
2. Try parallel I/O port 3BC and 378 with IRQ7.<br>
<br>
3. Try configuring your printer in pconsole/nwadmin to not use polled interupts.<br>
<br>
4. Have you also tried setting timeout in your capture? TI=0 disabled TI=10 (10 seconds).<br>
<br>
My guess would be 1 or 3 should fix your problem.<br>
<br>
Gordon Yuen<br>
<br>
<A HREF="mailto:gyuen@vanhosp.bc.ca">gyuen@vanhosp.bc.ca</A><br>

 

[unit512]

I have tried some of the above, but not all.<br>
<br>
The printer in question is an Okidata 321.<br>
<br>
Okidata did say to try the IBM Proprinter XL driver as an option,<br>
which I will also try.<br>
<br>
Thanks.

 

[dgrewe]

I am printing in the exact same enviroment you are.<br>
<br>
If you go back to Nprinter.<br>
In the capture statement for the workstations add the /A parameter and the /TI=10 statement.<br>
/A = Autoendcap so the job will start printing without exiting the program <br>
/TI=10 = Timeout after 10 seconds. (if a graphics program is involved you may want to up this to 30 seconds). <br>
<br>
If the novell does not get any data after 10 seconds it ends that print job and starts another. The /a then forces the job to print.<br>

 

[unit512]

That sounds like it might really work.<br>
Will try it as soon as the client pays<br>
up their overdue bills.<br>
<br>
Thanks

 

[rasindia]

Get the latest patch for Nrintser and play around with the different printer modes available in the system setup.I hope it will solve the problem

 

[rasindia]

Get the latest patch for Nprintser and play around with the different printer modes available in the system setup.I hope it will solve the problem