[log in to unmask] (Eero Laurila) wrote:
 
>Duane Percox ([log in to unmask]) wrote:
>
>: I know people who use x.25 for vplus and it seems to
>work ok.
>: Except for the non-standard hp pad issues (but that's
>another
>: story for another time).
>
>
>Let's open up the other story as well - I'm quite
>curious about what do you mean with "non-standard hp
>pad issues".  To my understanding  HP2334/5 PAD's
>implement X.3, X.25, X.28 and X.29 standards exactly as
>the standard says plus provide some additional features
>that the standard does not address.  The biggest
>problem from application's  point of view that I see is
>the shortcoming of X.3, X.28 and X.29  standards that
>do not define read termination on bytecount...
>
>Thanks for elaborating,
>:-) Eero Laurila - HP CSY Networking lab, NS services.
 
I was afraid someone would ask that question!  I have a
customer who has HP and Fujistu pads in an ISDN x.25 setup. Now
I am not claiming to be much of an expert on these matters, but
this is what has been determined (I think <g>) by HP and the
customer: The hp pad behaves differently than other pads (the
Fujitsu in this case) when a running vplus application calls
vcloseterm to do some character mode operations. Some flow
control issues are left "undone". The app is printing a report
on the slave printer using <esc>&pW<data> syntax (sic). The 'S'
response for each line printed and the large report creating
much confusion and subsequent missed lines of print. The
Fujitsu pad works just fine. HP found some reference in the
knowledge base to this and the escape sequence to reset things
to a good state. This has solved the printing problem.
 
Mike Hawkins of HP was the person I worked with.
 
-- Duane Percox (Quintessential School Systems)
   [log in to unmask]