HP3000-L Archives

February 1997, Week 4

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:
Gilles Schipper <[log in to unmask]>
Reply To:
Gilles Schipper <[log in to unmask]>
Date:
Tue, 25 Feb 1997 14:51:06 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (33 lines)
At 01:24 PM 97/02/25 -0500, you 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.
>
>Michael Miller
>
Reflection1 should work fine with the win95 tcp/ip stack.

You will need WRQ's VT-MGR (aka NSOPEN) to connect to the HP3000 via VTMGR
protocol.

However, if you are on MPE/iX 5.5, you could connect via Telnet instead of
VTMGR - meaning you could do without WRQ's TCP/IP stack and NSOPEN software.

However, AFAIK, the Telnet connection would consume more HP3000 CPU
overhead than would a VTMGR connection (assuming Telnet software - rather
than Telnet card in DTC).


---------------------------------------------------------------------------
Gilles Schipper
GSA Inc.
HP3000 & HP9000 System Administration Specialists
300 John Street, Box 87651   Thornhill, ON Canada L3T 7R4
Voice: 905.889.3000     Fax: 905.889.3001
Internet:  [log in to unmask]  Compuserve: 71203,474
---------------------------------------------------------------------------

ATOM RSS1 RSS2