I just wanted to do a quick follow up on the post by
 Michael L Gueterman regarding the Telnet Server. Micheal Wrote:

: The "basic" TELNET server shipped with 5.5 wasn't usable (at least
: I couldn't get it to work) by the TELNET client in Windows 95.  The
: "full" TELNET server shipped on the Powerpatch 1 tape (which has
: been superceeded by a newer patch available on SupportLine) is
: usable.  I believe you can apply the patch without having to do
: the Powerpatch.  Unless there is a newer version (I haven't checked
: this morning), the patch id is "PTDEDF6A" for the newest TELNET
: server for 5.5.

 The initial server release was extremely literal regarding telnet
 negotiation options. If the client refuses an option the server sent,
 the server would terminate the connection. I forget which option the
 Win95/WinNT Telnet Client rejected, but we discovered it after the
 submittal to the base MIT. We did correct for Power Patch 1.

 Please be aware however that the Microsoft provided clients display the
 3000's D1 read trigger character as a splat. Under CI applications this
 is visually annoying, but not likely to cause a problem. Running block
 mode applications however, is not likely to work. We do require HP
 terminal emulation for 3000 Block Mode applications. I believe we
 documented the requirement of HP terminal emulation for supported
 connections in the release documentation and data sheet.
 The Telnet Server is written based on the
 assumption that there is a HP terminal receiving the data stream and
 displaying/reacting properly to it.

 Micheal is correct, you may apply patch PTDEDF6A without having Power
 Patch 1 installed. Telnet doesn't care. As far as I know,  PTDEDF6A
 will be included with Power Patch 2.

 For those who find our assumption of HP terminals too restrictive, there
 are 2 SR's you might be interested in.

 1)4701345256 : Using FDC30/32 to set read trigger to null does not
 disable read trigger.
   We have a possible solution for this in beta test. It will be helpful for
   those applications that need to suppress the HP read trigger.

 2) 4701345314 : add term=18 functionality to telnet server.
   This is an enhancement request to allow the user to login using the
   term=18 option to specify that the 3000 should treat the terminal as a
   generic non-hp terminal (AKA Termtype 18).

   We have one customer requesting this behavior because they have an
   application that does non-hp terminal screen maniipulation that they
   wish to run over telnet.

   We're building the business case for this change now. If this is of
   interest to your company, it would be useful for us to hear from you.
   The most effective way for you to communicate your need is to submit
   an SR via the RCs. Less effective, is for you to e-mail me with your
   information and I can add you to the list in the current SR.


 I hope this is useflu information to y'all.

 Sincerely
 cas
--
=======================================================================
[log in to unmask] (Cas Caswell)   By the way: I said it, not my company.
 =======================================================================