Re: (ASCEND) How Ascend should fix thier software problem

[MMedwid@symantec.com]

           While I agree with the sentiment (it took eighteen months
           to get a stable code version for the 4004)...
           we have been relatively stable with 5.0Ap42 and 5.0Ap36.
           Some of these have been up constantly for
           several months.  And this includes a couple of sites with a
           high level of use.  We use V.34 modems.

           On the other hand the thought of upgrading to 7.x.x is
           scarey given the track record.



           From: Marc Newman <mknewman@blkbox.com> AT Internet on
                 03/04/99 07:59 AM


           To:   ascend-users@max.bungi.com AT
                 Internet@sym-corp@ccMTA-SYM-CORP
           cc:   kevin.smith@ascend.com AT
                 Internet@sym-corp@ccMTA-SYM-CORP (bcc: Michael
                 Medwid/Cupertino/Cal/SYMANTEC)
           Subject:  (ASCEND) How Ascend should fix thier software
                 problem


           There is only one answer possible:

           Ascend should open thier source tree to the public domain.

           They have been ineffective in implementing changes (almost
           everything is broken when they first release it) and it
           takes several releases to fix anything.  I still, after 4
           years, 3 revs of modem cards (28800, 33600 and 56kb) and
           untold versions of software don't have a stable release of
           software for my Max4004's.  I have been fighting with them
           on this since 4.3.

           I want a release that will not slow down under after a few
           days, will not reboot on it's own, and will support all the
           announced features.

           I do have a Pipeline 400T with 8 modems that has been up
           for 2 years.

           Marc
           ++ Ascend Users Mailing List ++
           To unsubscribe: send unsubscribe to
           ascend-users-request@bungi.com
           To get FAQ'd:   <http://www.nealis.net/ascend/faq>

           Received: from mailer.Symantec.Com ([198.6.49.176]) by
           smtp-ima.symantec.com
           with SMTP
             (IMA Internet Exchange 3.1) id 0053379E; Thu, 4 Mar 1999
             07:10:28 -0800
           Received: from max.bungi.com (max.bungi.com [207.126.97.7])
            by mailer.Symantec.Com (8.8.8/8.8.8) with ESMTP id
            HAA16893
            for <mmedwid@symantec.com>; Thu, 4 Mar 1999 07:10:17 -0800
             (PST)
           Received: (from majordom@localhost)
            by max.bungi.com (8.8.7/8.8.7) id FAA09301
            for ascend-users-outgoing; Thu, 4 Mar 1999 05:59:41 -0800
           (PST) X-Authentication-Warning: max.bungi.com: majordom set
           sender to
           owner-ascend-users using -f
           Received: from blkbox.com (mknewman@blkbox.com
           [206.109.97.2])
            by max.bungi.com (8.8.7/8.8.7) with ESMTP id FAA09296
            for <ascend-users@max.bungi.com>; Thu, 4 Mar 1999 05:59:36
             -0800 (PST)
           Received: (from mknewman@localhost)
            by blkbox.com (8.8.7/8.8.7) id HAA25080;
            Thu, 4 Mar 1999 07:59:33 -0600 (CST)
           From: Marc Newman <mknewman@blkbox.com>
           Message-Id: <199903041359.HAA25080@blkbox.com>
           Subject: (ASCEND) How Ascend should fix thier software
           problem
           To: ascend-users@max.bungi.com
           Date: Thu, 4 Mar 1999 07:59:33 -0600 (CST)
           Cc: kevin.smith@ascend.com
           X-Mailer: ELM [version 2.4 PL24 PGP3 *ALPHA*]
           Content-Type: text
           Sender: owner-ascend-users@max.bungi.com
           Precedence: bulk