Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: (ASCEND) 6.1 clarifications
Yes.
On Sat, 6 Jun 1998 iml@interconnect.net wrote:
> Thanks can you then do a trestore from a tsaved config?
>
> On Sat, 6 Jun 1998 00:43:08 -0400 (EDT), you wrote:
>
> >
> > You first need to get the restricted image and run that, after a nvram
> >you would need to load the full image then do another nvram then you
> >box will be up to 6.1
> >
> >Example,
> >
> >I run tik.m40 for 5.0ap46
> >
> >I downloaded the following to upgrade to 6.1 :
> >
> >
> >/pub/Software-Releases/Max/Current/rtik.m40 (Restricted Image)
> >
> > THEN
> >
> >/pub/Software-Releases/Max/Current/ftik.m40 (Full Image)
> >
> >Please remember you must load the rtik.m40 image then do a nvram
> >then load the ftik.m40
> >
> >Jason Nealis
> >Director Internet Operations / Network Access
> >Erols Internet (An RCN Company)
> >
> >
> >On Fri, 5 Jun 1998 iml@interconnect.net wrote:
> >
> >> What would be the correct binary filename to upgrade Max40xx units
> >> running 5.0Ap46 Load tk.m40 and can the current config be saved via
> >> tsave and trestore to load it back on the 6.1 unit if need be?
> >>
> >> On Fri, 05 Jun 1998 13:03:38 -0700, you wrote:
> >>
> >> >A couple of clarifying points to the 6.1 release notes...
> >> >
> >> >1. The V.90 modem code supplied in 6.1.0 supports both K-Flex and
> >> >V.90 clients. It should be completely compatible with existing
> >> >client modems. What the release note is trying to convey when it
> >> >says customers can't run both at the same time is simply that we only
> >> >supply one version of modem code in this release. Some customers may
> >> >be concerned that the new code is relatively unproven. We invite
> >> >those customers to continue with the older 6.0.x code branch, which
> >> >is still fully supported, and contains the older (K-Flex-only) code.
> >> >
> >> >2. It is believed the Windows 95 issue with Winsock affects a truly
> >> >small percentage of the world. This problem was documented by
> >> >customer service during the 6.0 beta test seven or eight months ago.
> >> >They came up with the workaround, which we documented in the 6.0
> >> >release note. We carried it through to the 6.1 release note,
> >> >because we have not yet implemented a change. We do have a fix
> >> >coming soon.
> >> >
> >> >Matt Holdrege http://www.ascend.com matt@ascend.com
> >> >++ Ascend Users Mailing List ++
> >> >To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> >> >To get FAQ'd: <http://www.nealis.net/ascend/faq>
> >>
> >> ++ Ascend Users Mailing List ++
> >> To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
> >> To get FAQ'd: <http://www.nealis.net/ascend/faq>
> >>
>
++ Ascend Users Mailing List ++
To unsubscribe: send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd: <http://www.nealis.net/ascend/faq>
Follow-Ups:
References: