MICHAEL C. MILLER wrote:
>
> Has anyone had any experience on using the Windows95 native TCP/IP stack
> and REFLECTION/1 to connect to an HP3000.  I know that WRQ says we must use
> their TCP/IP stack, but we are developing desktop standards and we need one
> single TCP/IP stack that works with all of our applications.  I know that
> Reflection uses VT-MGR to connect.  How can we get the native Windows95 IP
> to use this?  What are other considerations that you can think of?  Thanks
> for your help.

As of Reflection 4 or thereabouts Reflection supports WINSOCK.DLL on
the PC and MacTCP on Macintosh for telnet connections, *out of the box*.
If you have a DTC with telnet card, or MPE/iX 5.5 + powerpatch 1 to
give you telnet/ix server, you can connect perfectly well without any
of the WRQ TCP/IP stack.  Our typical faculty member accesses our 3000
via a server copy of Reflection 1 (ver 4.21) and Trumpet Winsock (for
Win3.1) or Win95 (out-of-the-box Microsoft TCP/IP).

If you simply must have NS/VT, you can get NS/Open from WRQ.  This
is a relatively small but very expensive DLL you place in the same
directory as WINSOCK.DLL to give you NS/VT access.

We had a large number of licenses for WRQ's RNS TCP/IP software, but
as machines are going to Win95, we're letting them telnet in and moving
their old RNS to somebody else's Win3.1, or someone who needs the added
servers (RNS does include some nice services you don't get otherwise).

Jeff Kell <[log in to unmask]>