HP3000-L Archives

April 1995, Week 1

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:
From:
Netnews Server <[log in to unmask]>
Reply To:
Date:
Mon, 3 Apr 1995 21:11:46 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (58 lines)
To all:
 
I, like Gavin, think the EX box is actually oem'd by HP
from YoYoDyne. It has historicaly been the source of
interesting problems not seen in the internal cards.
 
The C30D group are now aware of the problem and are
investigating. I will publish the results here. They
do agree that there is some misunderstanding between
them and the Boise people about supported printers
and will to resolve it.
 
Note that setting the idle timer to zero (disabling it)
has worked around the problem successfully.
 
As for Marty's comments:
 
The details of the centronics/bitronics issue were not
given to me by the Boise engineer. His explanation did
not make sense from several angles but he was not interested
in exploring this, only in stating that the Jetdirect EX
C30D pair are not supported. Note that at this time, it
appears that this problem may be a special case and the
Boise engineer was too busy talking (!) to listen and
simply classed this problem as non-supported device.
 
As for the engine-truck analogy,  I called the Peripherals
Support Group because that is who you call for JetDirect
interface problems. The C30D and the JetDirect EX are two
separate products, purchased independently, made by two
different maufacturers and you combine them yourself (or
combine the JetDirect EX with a non-HP device). Furthermore,
since the idle timer is a feature of the EX unit, calling
Boise was quite correct.
 
Developers of TCP/IP software to communicate with the
JetDirect interfaces typically belong to the HP Peripherals
Developer Program (Boise) and receive support writing host
drivers for these interfaces from this group...
 
I think most people would agree that the engine-truck
analogy makes no sense here...
 
Finally, since the running/not running of the idle timer
is a JetDirect issue, the behavior of HPUX is immaterial...
 
BTW, One of the Boise people did take the initiative to call
Cupertino and get the balling rolling on resolving the problem
with the JetDirect EX/C30D and the internal HP issues that seem
to be involved here.
 
rc
---------------------------------------------------------------
Richard Corn                       e-mail: [log in to unmask]
RAC Consulting                      Voice: (360) 357-9572
Olympia, WA. USA                      fax: (360) 352-8453
---------------------------------------------------------------

ATOM RSS1 RSS2