Item Subject: cc:Mail Text
Curt Brimacomb wrote:
>I have a question that you may have to search your memory.
>We have a client that is still running a series 37. They had a
>rugged
>writer printer that died and we gave them a 2934a. As far as I can
>tell
>(the manual for the 2934a is missing), the printer driver configured
>for a
>2934a is the same as a rugged writer, but it will not print.
>They are on g.b3.02 MPE. The ldev port is configured as:
>22 8 1 0 32 14 ?? 960 66 0 S HIOASLP0 RUGGED
>The printer is configured as 9600 baud, 7 bits, odd, parity on,
>xon/xof on,
>enq/ack on.
>TIA
>*********************************************************************
There are two pieces of information that would be helpful here.
First, the termtype of "??" means that a termtype filename was given
instead of a termtype number(which also actually references a termtype
filename of TT##.PUB.SYS). If we know what termtype filename was used
or, more importantly, the characteristics of the termtype filename,
then we may know a little more about how MPE expects the printer to
act(e.g., will the printer respond to MPE status requests? What
parity, etc. does MPE think the printer is set at.)
Second, you say it will not print but we need to know if there is an
error being reported before it does not print, or does it just not do
anything. If the termtype file was created to do status requests,
then you should be getting some sort of SPOOLEE I/O ERROR. If the
termtype file was based on TT18, then you may see nothing at all.
Another possibility is since the 2934's top speed is 200 cps, then it
may very well be set at 2400 baud. Many of my customers did this to
cut down on the chance of getting buffer overruns on the printer.
Assuming the data connection is intact, I would guess parity or baud
rate conflicts.
Jon Broz
HP Cleveland
------------------------------------------------------------------
|
