HP3000-L Archives

August 1997, 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:
Gavin Scott <[log in to unmask]>
Reply To:
Gavin Scott <[log in to unmask]>
Date:
Thu, 7 Aug 1997 10:38:13 -0700
Content-Type:
text/plain
Parts/Attachments:
[HP3000-L] (19 lines)
Rose asks,
> Also,  we will be using Reflections to connect to the HP3000.  We
> understand that Reflections has an option to use the Microsoft TCP/IP
> stack or a Reflections TCP/IP stack.  Is there any advantage of using one
> over the other?

These days I know of no reason to use anything other than the built-in
TCP/IP transport (assuming we're talking about Windows 95 or later and
not something older).  TCP/IP is a fundamental operating service, and
one which should be provided as part of the operating system.  Replacing
such a built-in service is just asking for trouble because it makes
your system different from what most software vendors test against.  I
have several software packages that I use on a day to day basis that
state that they do not support any other TCP/IP stack than Microsoft's,
and at least one of these checks and refuses to even load if you are
not running the Microsoft TCP/IP.

G.

ATOM RSS1 RSS2