Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re[2]: (ASCEND) 5.0Ai10
I haven't seen a problem with an i release. Haven't tried it. But I
am having difficulty getting current status on the bug fixfor pcA
crashing the Maxes. And I need clarification on the release note
below which seems to contradict itself. Note the tik.m40 file is for
Max 400X while eik.m40 is for Max 400XE. Yet below that is says "Max
4000E software was NOT included. Max 4002/4 software was NOT
included." Isn't that contradictory?
And my other burning issues are when is a Max 200 version of code
which fixes the pcA going to be available? When will there be a code
fix compatible with the Max 1600 (our most widely deployed). ??
Any insight is greatly appreciated. Our world-wide RAS deployment
is stalled because of this.
-Michael
------------------------------------
Support called to say the fix for the bug that allowed the application
pcAnywhere to crash the Max was available. What's up the the 4000E,
4002/4004 not included? The statements seem to contradict Max 400X
and Max 400XE support?
---------------------------------------------------------
at
ftp://ftp.ascend.com/pub/Software-Releases/Max/Patch/Release-5.0Ap6/
The Max image file names are as follows:
tik.m20 Max 2000 T1/PRI w/ RIP/OSPF & K56 flex support
eik.m20 Max 2000E E1/PRI w/ RIP/OSPF & K56 flex support
tik.m40 Max 400X T1/PRI w/ RIP/OSPF & K56 flex support
eik.m40 Max 400XE E1/PRI w/ RIP/OSPF & K56 flex support
BRI support = support for the BRI slotcard
DM-8 support = support for the 8-modem slotcard DM-12 support =
support for the 12-modem slotcard
K56 flex support = support for the 56k modem slotcard
NOTE: DM-8s and DM-12s are NOT supported simultaneously
in the same Max
SPECIAL NOTES:
------- -----
Max 200 software was NOT included
Max (Max 1600) software was NOT included Max 1800 software was NOT
included
Max 4000E software was NOT included
Max 4002/4 software was NOT included
______________________________ Reply Separator _________________________________
Subject: Re: (ASCEND) 5.0Ai10
Author: Kevin Smith <kevin@ascend.com> at INTERNET
Date: 5/6/97 11:58 AM
At 08:37 AM 5/6/97 -0700, you wrote:
>
>Does this include the fix to the pcAnywhere incompatibility? Is the code
>available for the Max 200's and the 4004? Is there a 4.x version for the
Max
>1600s that addresses the similar issues?
Michael....as far as I can tell, the problem was never seen in 5.0Ai1, so no
fix was ever posted for the "i" releases. The "p" branch was fixed with
5.0Ap6,
but that release does not support "stacking", so we are wary to recommend
upgrading to that version.
**** Did you ever see the problem in an "i" release ? Because if you did I
will need to open an emergency fix-request to have the fix ported to the "i"
branch.
Kevin Smith Updated Service and Support
Ascend Communications Resources are now at:
http://www.ascend.com/service
Received: from Mailer.symantec.com (198.6.49.5) by smtp-ima.symantec.com with
SMTP
(IMA Internet Exchange 2.1 Enterprise) id 0000ABEB; Tue, 6 May 97 13:02:04
-0700
Received: from drawbridge.ascend.com (drawbridge.ascend.com [198.4.92.1]) by
Mailer.symantec.com (8.8.4/8.7.6) with SMTP id MAA18116 for
<MMedwid@symantec.com>; Tue, 6 May 1997 12:37:02 -0700 (PDT)
Received: from spud.ascend.com (fw-ext.ascend.com [198.4.92.5])
by drawbridge.ascend.com (8.6.12/8.6.12) with ESMTP
id MAA22203 for <MMedwid@symantec.com>; Tue, 6 May 1997 12:24:39 -0700
Received: from ascend.com by ascend.com with SMTP
id MAA22902 for <MMedwid@symantec.com>; Tue, 6 May 1997 12:24:32 -0700
Message-Id: <3.0.1.32.19970506115846.00a30b90@mktg_srv.ascend.com>
X-Sender: kevin@mktg_srv.ascend.com
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Tue, 06 May 1997 11:58:46 -0700
To: MMedwid@symantec.com (Michael Medwid)
From: Kevin Smith <kevin@ascend.com>
Subject: Re: (ASCEND) 5.0Ai10
In-Reply-To: <00009C13.3152@symantec.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"