From: reece@eco.twg.com (Reece R. Pollack)
Subject: Re: message for wollongong - re pathways transition
Reply-To: reece@eco.twg.com (Reece R. Pollack)
Organization: The Wollongong Group (East Coast Operations)
Date: Fri, 4 Sep 92 01:02:15 GMT


In article <1992Sep2.124436.3509@macc.wisc.edu>, dorl@vms.macc.wisc.edu (Michael (NMI) Dorl) writes:
|>Wollongong:
|>
|>I received a letter from Wollongong saying they would be offering
|>to transition my win tcp licenses to something called PathWays Access
|>for VMS.
|>
|>I have some questions about this...
|>
|>  Is WIN/TCP still going to be available and supported?

WIN/TCP is evolving into PathWay for VMS. The sum of the three products,
PathWay Runtime, PathWay Access, and PathWay API form a superset of the
original WIN/TCP product.

The WIN/TCP V5.2.1.1 bugfix release is (hopefully) the last release to
carry the WIN/TCP name. All further releases should carry the PathWay
name.

|>  What is PathWays and why would I want to pay to 'transition'
|>  to it?

There are two basic ideas behind the PathWay-ization of the WIN/TCP product.
The first is economic: we have some customers who don't need or want the
entire WIN/TCP product set, and don't want to pay for those portions they
don't need. With PathWay for VMS you can select the options which meet
your need.

The second reason is to bring the VMS product in line with our other product
lines. This should make our product line consistant, and that gives our
marketing people warm and fuzzies.

|>  What parts of PathWays do I need to get the basic TCP/IP
|>  facilities I have now with WIN/TCP?

The PathWay product line is broken down as follows:

PathWay Runtime -- This is the basic TCP/IP kernel and the utilities needed
to configure and maintain it.  If you're running a product which requires
a TCP/IP transport but have no need for any of the other utilities, this
is all you need.

PathWay Access -- This is the collection of user applications which most
people associate with TCP/IP. That is, TELNET, FTP, TALK, and the like.
This package is layered on top of PathWay Runtime, which makes Runtime
a prerequisite.

PathWay API -- This is the Applications Programming Interface kit, which
contains all the files needed to develop new applications. If you do
application development on one system but use these applications on a
number of machines, all would require Runtime, but only the development
machine will require API.

If you truely want all the functionality provided by the current WIN/TCP
product, you need all three. Keep in mind that what you'll get will actually
be a superset of the existing product.

|>  The price schedule lists conversion fees but says nothing
|>  about educational discounts.  Are there discounts for
|>  conversion for educational sites?  If so what are the
|>  discounted prices?

Ok, you're one up on me here. I'se just a lowly engineer, and I haven't seen
any pricing information at all. I'll see if I can drag one of the salescritters
into the newsgroup tomorrow.

|>On another issue...
|>
|>  I need educational prices for WIN/TCP on the following
|>  systems.
|>
|>    vaxstation 4000/90 workstation
|>
|>    uvax 3100/90
|>
|>    vax 4000/100
|>
|>  Please supply discouted education license costs and annual
|>  support costs.  Add PathWays prices in addition.

I'll forward this request to our sales group, and you should get a personal
response in a couple of days. If you don't, let me know and I'll beat the
mail system into submission.

Anyone else wishing to discuss pricing and availability should send email
to our sales group at 'Sales@Twg.Com'.

--
Reece R. Pollack
Senior Software Engineer
The Wollongong Group, Inc.
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Subject: (no subject given)