HP3000-L Archives

January 1998, Week 5

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Network Printing and troubleshooting/tracing
From:
Lars Appel <[log in to unmask]>
Reply To:
Lars Appel <[log in to unmask]>
Date:
Thu, 29 Jan 1998 14:48:18 +0100
Content-Type:
text/plain
Parts/Attachments:
text/plain (15 lines) 
>This seems on the surface to be a carriage control issue. Knowing
>what is in the packets being sent by the HP3000 to printer would
>help. Knowing what is in packets can be a trick too. If you have
>a packet analyzer, see what the HP3000 is converting the page eject
>cctl code (%61) into.

It might even be possible without a packet analyzer. I vaguely recall
some options in NPCONFIG regarding network tracing (socket level and
something else) for a printer LDEV. The output was either written to
NMLG or separate log/tracefiles and would be examined with NMDUMP.

Sorry for the vague memory. Hope this is still helpful.

Lars.

ATOM RSS1 RSS2