Conference hydra::axp-developer

    Unfortunately this information doesn't seem to be anywhere on the web
    to point him to...
    
    I called and left a lengthy voicemail detailing the changes listed in
    the V3.2G "Read This First" and "Release Notes Addendum".  I also
    suggested he either send mail or call referencing this note if he
    wanted more details, or for us to fax him the information.
         
    Donna

From:	HYDRA::AXPDEVELOPER "alpha-developer@digital.com" 31-JAN-1997 06:40:21.78
To:	VANORDEN
CC:	AXPDEVELOPER
Subj:	note 3116

From:	SMTP%"dgs@bgs.com" 30-JAN-1997 17:33:21.72
To:	alpha-developer@digital.com
CC:	
Subj:	Note 3116

Return-Path: dgs@bgs.com
Received: by asimov.mro.dec.com (UCX V4.1-12, OpenVMS V6.2 VAX);
	Thu, 30 Jan 1997 17:33:19 -0500
Received: from pobox1.pa.dec.com by fluid.mro.dec.com; (5.65v3.2/1.1.8.2/19Nov96-0448PM)
	id AA09445; Thu, 30 Jan 1997 17:33:31 -0500
Received: by pobox1.pa.dec.com; id AA17995; Thu, 30 Jan 97 14:33:33 -0800
Received: from gatekeeper.bgs.com by mail2.digital.com (5.65 EXP 4/12/95 for V3.2/1.0/WV)
	id AA30799; Thu, 30 Jan 1997 14:27:49 -0800
Received: from bgs-dbms.bgs.com  by gatekeeper.bgs.com (8.7.Beta.10) with ESMTP
	id RAA21010; Thu, 30 Jan 1997 17:27:47 -0500 (EST)
Received: from BGS_DBMS/SpoolDir by bgs-dbms.bgs.com (Mercury 1.20);
    30 Jan 97 17:27:48 EST5EDT
Received: from SpoolDir by BGS_DBMS (Mercury 1.20); 30 Jan 97 17:27:30 EST5EDT
From: "David Stimson" <dgs@bgs.com>
To: alpha-developer@digital.com
Date: Thu, 30 Jan 1997 17:27:23 EST5EDT
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
Subject: Note 3116
Priority: normal
X-Mailer: Pegasus Mail for Windows (v2.33)
Message-Id: <1E0EFC934A6@bgs-dbms.bgs.com>

Hi Donna (or virtual Donna),
Thanks for your voice mail of this afternoon. 
Just to clarify what I'm looking for: 

We don't have the 3.2g OS release in-house, nor do we have the
October maintenance kit. 

We have a customer who encountered problems installing one of our
product components on a 3.2g machine until he installed this
particular maintenance kit.  I'm just trying to see if there's
something I can identify about this kit which would explain the
change.  Our installation depends upon common UNIX executables (such 
as tar) for its operation.  As we are not really supporting 3.2g, 
this is not a big issue, but I wanted to be able to put some useful 
details into my resolution of this customer's problem.

If you see any information about this maint patch that seems to 
answer this question, feel free to email or fax as directed in my 
signature below.
Many Thanks,
David


*******************************************************
*  David Stimson                dgs@bgs.com           *
*   UNIX R&D Organization       BGS Systems, Inc.     *
*   Talk: 617-663-4593          Fax: 617-663-1515     *
*******************************************************

From:	HYDRA::AXPDEVELOPER "alpha-developer@digital.com"  4-FEB-1997 11:13:45.23
To:	US3RMC::"dgs@bgs.com"
CC:	AXPDEVELOPER
Subj:	RE:Note 3116

David,

Can you tell me a little more about the customer?  What versions of the
O/S was running when the problems were encountered (what version of the
O/S was running before the upgrade?)  Perhaps the fix wasn't in 3.2g,
but in one of the releases between the O/S version and 3.2g.

Is their system one of our newer models?  There is a lot of new system supprt
provided in 3.2g (along with the releases which exist prior to 3.2g).

Donna
Alpha Developer Suppor

    Closed due to lack of response from the customer.
    
    (I think this question was mostly to satisfy his curiosity.  Since I
    had already supplied a detailed response over the phone, I suspect he
    decided not to pursue this any further.)
    
    Donna VO