Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Print jobs mixing up

42 views
Skip to first unread message

Faisal Usmani

unread,
Nov 4, 1994, 12:59:39 PM11/4/94
to

We've been having intermittent problems with more than one person printing on a
network printer. The jobs sometimes get mixed up and end up printing on the
same page. Or, a single job gets split onto two pages

The OS is Netware 3.11, and the printer is an HP Laserjet 4 Plus, connected
to a machine running the latest RPRINTER. PSERVER is also the latest available

I DID notice that if PSERVER is unloaded, I get a message saying that some
resources were not freed.

If anyone has encountered similar problems, and found a fix for this
problem, I would appreciate a reply.

Thanks
Faisal

a...@acpub.duke.edu

unread,
Nov 4, 1994, 12:19:07 PM11/4/94
to
In article <39dsqc$c...@masala.cc.uh.edu> ac...@menudo.uh.edu (Faisal Usmani) writes:
>From: ac...@menudo.uh.edu (Faisal Usmani)
>Subject: Print jobs mixing up
>Date: 4 Nov 1994 17:59:39 GMT


>We've been having intermittent problems with more than one person printing on a
>network printer. The jobs sometimes get mixed up and end up printing on the
>same page. Or, a single job gets split onto two pages

[...]

> If anyone has encountered similar problems, and found a fix for this
>problem, I would appreciate a reply.

>Thanks
>Faisal

Using DOS PRINT to a captured LPT port rather than NPRINT to a quename can do
this. e.g. if I Capture LPT1 to queue LASER, then PRINT SOMEFILE.TXT, if you
look at the job in queue via PCONSOLE you will see that it is there in
"chunks" with numbers as identifiers. The bigger the file, the more discreet
chunks. If OTOH you NPRINT SOMEFILE.TXT Q=LASER, PCONSOLE will show a single
job in the queue named SOMEFILE.TXT which can't get interlaced w/someone
else's job.

Within apps it's the same deal, for example WordPerfect 5.1 -- if you select a
printer and assign it to LPT1 (which was earlier CAPTUREd to queue LASER), you
should instead select "8 - Other" from the menu when assigning the printer's
port, then enter the name of the queue as the port. (See WP51
documentation re: Network Administration and/or printing on networks for
details).

HTH,

Anne

David B. Ferguson

unread,
Nov 10, 1994, 9:00:10 PM11/10/94
to a...@acpub.duke.edu
Hello Faisal,

>We've been having intermittent problems with more than one person printing on a
>network printer. The jobs sometimes get mixed up and end up printing on the
>same page. Or, a single job gets split onto two pages
>

> If anyone has encountered similar problems, and found a fix for this
>problem, I would appreciate a reply.


You didn't mention how you were set up to print, but I've seen this
printing problem several times before, if the printer is attached
to a workstation thats using RPRINTER, check to see that this node
is also using the CAPTURE command to redirect print jobs to the
print queue and not printing directly to is local LPT port.

Do to the tsr nature of RPRINTER, it time slices local processor
time to service network print requests as well as local activities,
if another node was to send a print job at the same time as the node
running RPRINTER does ( but not CAPTURE), you'll get this mixed print
job effect.

If your using only the one printer on the network you should
include the CAPTURE command in all the users login scripts.

I was recently onsite doing some report programming requirments analysis
for a large law firm and I noticed the girls all asking (yelling), if the
printer was avalible. After two days of this yelling I just had to inquire
as to why. I was thinking maybe paper type as they do internatinal trial
cases and forms could be different?

One secretary told me they had to do this because of a printing bug
in Novell Netware 3.11.

'Hmmmm, bug ah, did Novell tell you about this?'

'No, Kevin are consultant did.'

'I think Kevin may be wrong, can I look?'

5 mins. later the print problem was repaired.
Belive it or not they were (yell printing) for two years. <g>

Office productivity went up 10%, and I have a new Novell client. :-)

Hope his helps :-)
O
o
||||| o
- -
@(0)-(0)@
---------------------oOOO-----U-----OOOo-------------------------------------
David B. Ferguson Internet....: micr...@fox.nstn.ca
Consultant Voice.......: (902)464-9976
MicroTask Pager.......: (902)459-2697
Computer Services Address.....: 8 Faulkner St.
Dartmouth, N.S.
Canada, B3A 3A3
-----------------------------------------------------------------------------
Programmer - a organism that turns coffee into software
-----------------------------------------------------------------------------

Rafey Kazi

unread,
Nov 11, 1994, 1:24:09 PM11/11/94
to
This is in followup to the printing problem I had posted about earlier. The
problem is that just _one_ user is having his print jobs split up onto two
pages. We're running 3.11, with Pserver (VER 3.76) and Rprinter (VER 3.75)
and the user is printing from Word 6.0 for DOS. The problem is intermittent,
and the same document prints fine at times and gets corrupted at other times.
I have tried increasing timeouts (to 75 secs), printing on other queues,
changing cables on the printer, changing the PC that Rprinter is running on,
and finally giving the user a new userid. I've also switched the machine,
and the network card, but the problem still persists. The user boots
quite clean, with DOS share, IPX, and NETX. There is about 530K available
in convetional memory before starting Word. I called HP (the printer is a
LaserJet 4 Plus), and Microsoft but they could not come up with a solution.

Also, the user on the machine with Rprinter running does NOT use and ENDCAP
statement, or print directly to the DOS port, which might sometimes cause
this problem to occur as I am told.

Are there any other settings in Novell, eg. PRINTCON, PRINTDEF that I could
change? Any suggestions or comments would be much appreciated.
Thanks

Faisal Usmani

BrJacques

unread,
Nov 24, 1994, 9:18:23 PM11/24/94
to
same problem - only 1 user would have print split up. reboot the pserver,
check the default printer on that uer users software. user may be using
another software package prior to pirinting which is send some commands.
check the sequence in which the user is acessing various packages.
0 new messages