Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!linac!att!cbnewse!cbnewsd!cage
From: cage@cbnewsd.att.com (charles.gerlach)
Newsgroups: comp.protocols.tcp-ip
Subject: Re: WIN-TCP Problem on 3B2/500
Message-ID: <1991Feb26.172603.22618@cbnewsd.att.com>
Date: 26 Feb 91 17:26:03 GMT
References: <1991Feb25.214152.27244@prism.poly.edu> <1916@public.BTR.COM>
Organization: AT&T Bell Laboratories
Lines: 26

Folks:

Here we go again.  Trashing products based upon rumors, innuendos, and 
mis-information.  

I empathize with your 3B1 dilemma, but to compare that to the current
AT&T WIN/3B product is wrong.  The 3B2 product was produced by TWG 
approximately 4 years ago as a totally separate product from the 3B2 and 
386 lines.  Since then there have been 3 major releases of the 
other lines (R2.1, R3.0.1/R3.0, and R3.2).  I just checked with AT&T's 
support organization and Release 1.4 is the current 3B1 WIN product.
Its my understanding this product is not under active development,
so R1.4 is all there every will be on the 3B1.

Now to get back to the original question.  Around Christmas, Release 3.2
of WIN/3B and WIN/386 became generally available.  This release consolidates
the available R3.0.1/R3.0 patches and other changes to improve the 
functionality of the products.  Release 1.2 of NFS is also available.

To upgrade from a previous release, please contact your AT&T support
organization or your salesperson.  If they have any problems, tell them to
contact the product manager, Tim Trautman, for information on the upgrade
procedure.

				Chuck Gerlach
				cag@iwlcs.att.com


Brought to you by Super Global Mega Corp .com