Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: (ASCEND) 6.0.0 for the MAX family



Thanks for the answer.  Guess I get to find the Acrobat reader for Linux.
:)

Regards,
Joe Shaw - jshaw@insync.net
NetAdmin - Insync Internet Services

On Thu, 26 Feb 1998, Randy E. Reinhardt wrote:

> Joe,
> 
> I asked the same question earlier - then solved it myself.
> 
> You need to download both the rtik.m40 and ftik.m40 files.  Read carefully
> in the .ps or .pdf docs about loading extended loads.  (Pages 21 and 22 in
> the .pdf)
> 
> Follow those instructions to the letter, don't let the double restarts
> between each load panic you and all will be ok.  I just did it to a Max4004
> and it works.  Already tested the Windows 95 Multi-Link modem feature.  Had
> a 33.6 and a K56flex paired together for connect rates of 79,000+
> downloading compressed files at 7K+ per second. Dual K56flex units should
> get close to 100,000 BPS.
> 
> Randy E. Reinhardt - System Administrator
> Pyramid.Net   2701 Conestoga Drive, #123
> Carson City, NV. 89706
> Admin    - 702-884-3202  Fax-702-884-1827
> Tech Sup - 702-853-4227  Fax-702-851-6115
> Tech Support Hours M-F 9am-7pm  Sat/Sun closed
> http://www.pyramid.net/   randy@pyramid.net
> "Man is still the most amazing computer of all."
> John F. Kennedy
> 
> 
> -----Original Message-----
> From: Joe Shaw <jshaw@insync.net>
> To: Kevin A. Smith <kevin@ascend.com>
> Cc: Ascend User-Group <ascend-users@bungi.com>
> Date: Wednesday, February 25, 1998 11:30 PM
> Subject: Re: (ASCEND) 6.0.0 for the MAX family
> 
> 
> >I missed something.  What's with the fXXX.m40 naming convention?  It's not
> >listed in the README file like the others are, and I noticed there was no
> >tik.m40
> >
> >Regards,
> >Joe Shaw - jshaw@insync.net
> >NetAdmin - Insync Internet Services
> >
> >On Wed, 25 Feb 1998, Kevin A. Smith wrote:
> >
> >> 6.0.0 for the MAX family has been given to support and manufacturing.
> This
> >> release contains the following:
> >>
> >> New features:
> >>
> >> * BRI interface supports new analog encoding parameter
> >> * Support for 64K and 56K calls with R2 signaling
> >> * Israeli R2 signaling
> >> * Danish switch type added
> >> * MAX CH CNT upper limit specific to platform
> >> * B-Channel preference when MP+ or BACP adds bandwidth
> >> * BACP/BAP PPP protocol IDs match IETF
> >> * TACACS+ server retry attempts
> >> * Set Cause Code for ISDN DISCONNECT
> >> * ISDN Pre-T310 Timer
> >> * Enable data-service functionality for the MAX 4002 and MAX 4004
> >> with AIM cards installed
> >> * Raw TCP connection enabled
> >> * TCP modem connections can be disabled
> >> * User-definable TCP connection retry timeout
> >> * IDSL voice call support
> >> * Loopback support for IDSL card (BRI/LT)
> >> * MAX supports new CSLIP Auto Detect parameter
> >> * More information provided for SLIP connections
> >> * Multilink or MP+ call now can span multiple MAX units
> >> * Updated Microsoft Callback Control Protocol support
> >> * MAXDial/IP support for immediate modem call restriction
> >> * Support added for multiple host selection
> >> * Limiting terminal server access per user
> >> * User-configurable call blocking after failed connection attempt
> >> * Specifying Shared Profiles per Connection Profile
> >> * Terminal server users can be forced to use unique profiles
> >> * CR-LF characters act as a single CR in terminal server
> >> * DNIS support for TCP-CLEAR, X25/PAD, and X25/T3POS calls
> >> * RADVision extensions to V.25bis for DNIS
> >> * Enhanced support for T1/PRI conversion
> >> * Enhanced support for outbound modem connections
> >> * PRI number plan in outgoing AIM/BONDING and PPP calls
> >> * PRI number plan in outgoing calls
> >> * Enable NAT on MAX 1800 and 2000
> >> * DHCP services on the MAX 1800 and 2000
> >> * Show DHCP command added to terminal-server
> >> * Alphanumeric IP pool names
> >> * Removing routes to a host when the connection is down
> >> * Local DNS host address table option added
> >> * UDP Queue Control
> >> * Specifying the metric and preference for offline WAN connections
> >> * Specifying an OSPF ASE preference
> >> * Specifying the OSPF type of pool advertisement
> >> * Support for OSPF NSSAs (RFC 1587)
> >> * Advertise static routes as OSPF internal LSAs
> >> * Multicast default route
> >> * Configurable multicast group membership timeout
> >> * NetWare SAP Home Server Proxy
> >> * SPX spoofing added for IPX
> >> * New Answer profile option for dial-in NetWare clients
> >> * Support for IPX without defining an IPX server
> >> * ATMP attributes in RADIUS accounting
> >> * RADIUS refers to filter and firewall policies defined in local profile
> >> * NAS-Port-Type added to RADIUS Accounting records
> >> * RADIUS Accounting checkpoint feature
> >> * NACK option for Local Profiles First parameter
> >> * Format of RADIUS NAS-Port attribute modified for the MAX
> >> * Call-logging feature
> >> * AppleTalk configurable from RADIUS
> >> * RADIUS Accounting ATMP Notification
> >> * Specifying preferences for routes configured in RADIUS
> >> * SecurID authentication for ARA (AppleTalk Remote Access) clients using
> >> RADIUS/LOGOUT
> >> * MAX returns to primary RADIUS server after fixed time
> >> * New RADIUS attributes enable call routing to PPTP
> >> * RADIUS now recognizes packet types 33 and 34
> >> * RADIUS Accounting-Request packets show whether accounting is enabled or
> >> disabled
> >> * Configuring Data Over Voice Bearer Service (DOVBS) in RADIUS
> >> * New parameter for generating a second accounting Start record
> >> * New RADIUS and terminal server support for Point to Point Tunneling
> >> Protocol (PPTP)
> >> * RADIUS support for IPX call and data filters
> >> * Modem ID added to RADIUS Accounting Stop Records
> >> * RADIUS now follows NI-2 PRI spec for outgoing calls
> >> * SNMP can enable/disable/quiesce T1/PRI links
> >> * Enable and Disable individual modem using SNMP
> >> * SNMP write security disabled by default
> >> * SNMP can help find which device a call is logged into
> >> * SNMP "get" now retrieves MPP session statistics
> >> * SNMP can monitor WAN lines and channels
> >> * SNMP can obtain active call status
> >> * SNMP system reset
> >> * SNMP can detect concurrent sessions
> >> * ASCEND MIB now includes modem status objects
> >> * SNMP RFC 1398 Ethernet-like MIB (dot3) support added
> >> * Set system clock through SNMP
> >> * Terminating user sessions using SNMP
> >> * Ascend MIB change supports counters for total and current calls
> >> * Firewall Control Protocol managed by SNMP
> >> * SNMP request authentication added
> >> * Initiating RADIUS updates using SNMP
> >> * SNMP sysConfigTftpStatus object reports more states
> >> * SNMP now reports reasons for last reset
> >> * Layer 2 Tunnel Protocol (L2TP) support added
> >> * Maximum number of ATMP Tunnel sessions can be set
> >> * ATMP inactivity timer
> >> * Support for Finger remote user information protocol (RFC 1288)
> >> * Terminal server show users command added
> >> * Data rates reported to syslog
> >> * Receive and transmit rates now reported
> >> * Syslog enhancements
> >> * Syslog messages generated when Security profile activated
> >> * Configure port for Syslog messages
> >> * Defender authentication enhancements
> >> * RLOGIN enhanced -l option
> >> * TFTP checks for compatibility of downloaded files
> >> * Cexample now uses a session server key
> >> * T1-CSU Status window added to the MAX 2000
> >> * New 56K digital modem cards
> >> * Disable modem capability added for MAX 1800 and MAX 2000
> >> * 56k Modem Numbering
> >> * Ability to select between V.34 and K56Flex modulation
> >> * X.25 T3POS support
> >> * X.25 over the D channel
> >> * X.29 Reselection PAD message support
> >> * Answer Profile for X25/PAD terminal server users
> >> * Specifying X.3 parameters in an X.25 PAD Connection profile
> >> * X.25/IP inactivity timer supported
> >> * New X.25 user facilities parameters added
> >> * Personal Handy Phone Service (PHS) support (Japan only)
> >> * RADIUS bootup server supported for ZGR subaddresses and answer numbers
> >> * ZGR answer numbers obtained from RADIUS
> >> * ZGR subaddresses obtained from RADIUS
> >> * DTPT encapsulation for T-Online PPP sessions
> >> * PRI-PRI switching for T-Online
> >> * AppleTalk routing added
> >> * Defender authentication added for AppleTalk Remote Access Protocol
> (ARAP)
> >> * Dial-in PPP support for AppleTalk
> >> * SecurID authentication for AppleTalk Remote Access (ARA) users
> >> * Enable data-service calls for the Multiband MAX 1800, 2000, and 4000
> >> * Suppress the display of the second T1 line on the Multiband MAX 2000
> >> * Suppress the T1-CSU and Serial WAN menus for the Multiband MAX 1800,
> >> 4002, and 4004
> >> * Suppress the T1-CSU and Serial WAN menus for the Multiband MAX 2000
> >> * Multiband simulation restricts MAX functionality
> >> * Multiband only option added
> >> * Megahertz CC1336 and XJ1336 modems available with MAX 200Plus
> >> * USR Courier V.Everything modem available with MAX 200Plus
> >> * Support for Xircom 33.6 PC Card modems
> >> * Support for Hayes Optima 33.6 PC Card (PCMCIA) modems
> >> * New modems supported on the MAX 200Plus
> >> * Support for Practical Peripherals 33.6 V.34+Fax PC Card modems
> >> * Support for Practical Peripherals 33.6 PC Card modem with EZ-Port
> >> * Support for the Hayes Optima 33.6 PC Card modem with EZjack
> >> * Support for Hayes Optima 288 V.34+Fax PC Card modems (Australia)
> >> * Flashing CD lights indicate problems with modems
> >>
> >>
> >> Corrections:
> >>
> >> TR 918    Two MP connections to MAX caused second system to
> >>           reboot first.
> >> TR 1070   Australian SPCs were not working correctly on the MAX 4000 E1.
> >> TR 1168   Bad negotiation of MRRU hung Cisco or Yamaha routers
> >> TR 1246   Connection problems between MAX and NT4.0.
> >> TR 1269   Users showed connection to a MAX but were not
> >>           actually active.
> >> TR 1270   Reduced incidence of type 1 disconnect records.
> >> TR 1310   snmpset on radAcctCurrentServerFlag failure.
> >> TR 1330   RADIUS truncates the "SD_CLIENT: name" field
> >>           to 5 characters.
> >> TR 1374   SNMP variable callStatusIfIndex returned
> >>           wrong value
> >> TR 1407   MPP subsequent channels caused IP address leak.
> >> TR 1414   Static IPX routes defined in RADIUS not added
> >>           to routing table
> >> TR 1421   Shared profiles were ignored.
> >> TR 1422   PC dialing MAX received invalid IPX route.
> >> TR 1455   MAX 1800 wouldn't dial port-to-port using
> >>           AIM/6 slot cards.
> >> TR 1459   P130 - CSU wouldn't sync if signal was less
> >>           than -7.5db
> >> TR 1490   IfType for Serial WAN incorrectly recorded for
> >>           Frame Relay
> >> TR 1510   Closing Immediate Telnet session cleared
> >>           call before telnet disconnected.
> >> TR 1546   MAX 4004 occasionally reset with fatal error 29.
> >> TR 1561   RADIUS dial-out routes did not work.
> >> TR 1562   Aview 1.1 coredumped.
> >> TR 1579   MAX 4000 T1 reset when MP Stack was enabled.
> >> TR 1584   IPX SAP tables not properly propagated
> >> TR 1620   X.25/PAD and TCP-Clear connection couldn't be made.
> >> TR 1624   After upgrade, the third T1 on a MAX 4000 did not
> >>           recover from a Yellow Alarm
> >> TR 1631   Aview back panel was not operating as documented.
> >> TR 1632   Coldstart message was not reported in RADIUS Accounting.
> >> TR 1647   MAX BRI slot card B channel stays in the "r" state
> >>           with Switch Type=Japan.
> >> TR 1653   Fatal error on MAX when ISDN hardware showed active
> >>           but wasn't.
> >> TR 1664   When CLID failed, call was not answered.
> >> TR 1667   MAX 4000 received a Fatal Warning 104.
> >> TR 1684   Inactivity timer not started for CLID authentication call.
> >> TR 1691   MAX Call Duration could not be disabled once value was set.
> >> TR 1716   TNT didn't form OSPF adjacencies with the MAX 4000.
> >> TR 1732   Nailed/MPP connections didn't establish switched link
> >>           consistently.
> >> TR 1734   PBX-T1 was not functioning with Data Call option installed.
> >> TR 1737   Large SNMP PDU size.
> >> TR 1773   Ascend unit failed to connect BRI channels that
> >>           appeared to be stuck in ringing state.
> >> TR 1775   M1800 didn't disconnect first call before callback.
> >> TR 1783   RADIUS: CLID with dynamic IP and callback didn't work.
> >> TR 1818   Terminal server "show calls" command did not
> >>           display phone number.
> >> TR 1826   Local profiles didn't work when unit configured
> >>           with DEFENDER.
> >> TR 1859   MAXDial/IP was not working in 5.0A or 5.0Ap1 (E1).
> >> TR 1861   X.25/IP broken for more than two local profiles.
> >> TR 1878   With PAP-TOKEN-CHAP, second channel couldn't be
> >>           brought up.
> >> TR 1880   Third prompt setting was not echoing correctly.
> >> TR 1925   Routes sometimes incorrectly went to WANIDLE.
> >> TR 1930   MAX 4000 was supporting only 9 concurrent users.
> >> TR 2002   IP pool leak problem using MP and JapaneseTA.
> >> TR 2023   MAX started sending compressed data to an NT
> >>           workstation even though compression was not negotiated.
> >> TR 2028   MAX 4000: Under a heavy load, calls were not connecting
> >>           completely.
> >> TR 2046   Call Duration was not working on a MAX 4004.
> >> TR 2054   Occasionally, the MAX 200Plus could not bring up a
> >>           4-channel call to another MAX.
> >> TR 2055   Unconfigured MAX 200Plus invisible to Console.
> >> TR 2072   Data filter wasn't applied for RADIUS-authenticated
> >>           user if Answer Defaults=Yes.
> >> TR 2085   The MAX did not always support two incoming calls on
> >>           the same BRI line from a 5ESS switch.
> >> TR 2092   MAX 2000: Boot hung with V110 card installed.
> >> TR 2096   MAX 4000: Poisoning of dial-out routes didn't work
> >>           correctly.
> >> TR 2100   FR MTU/MRU calculation caused fragmentation problems.
> >> TR 2135   Disabling or enabling one BRI line affected the other
> >>           BRI lines in unit.
> >> TR 2145   MAX 1800 BRI lines did not come up after reset
> >> TR 2153   MAX 4000 units running the TCP Modem feature
> >>           would crash when a TCP modem user entered an incorrect
> >>           password.
> >> TR 2154   MAX 4000 running ARA, gave warnings (indexes 145 and 175)
> >>           and reset with a Fatal Error 2.
> >> TR 2158   On a MAX 4000, the Net/T1 menu would occasionally
> >>           appear as "Not Available".
> >> TR 2163   callActiveTable not valid unless a call was active
> >> TR 2198   SNMP reported MAX 2000 product ID incorrectly
> >> TR 2236   The MAX could not dial out from a PRI GTD 5 switch.
> >> TR 2242   MAX 1800 were resetting with Fatal Error 19
> >> TR 2245   The MAX did not recognize Telnet-Break on V.34 and
> >>           K56flex calls.
> >> TR 2256   MAX 4000 units running T1-PRI conversion, could not place
> >>           outbound calls. New parameters have been introduced to
> >>           fix this problem.
> >> TR 2287   On an incremental software version, 64K channels could
> >>           not be added to MP+ calls.
> >> TR 2292   SNMP reported incorrect number of modems
> >> TR 2293   Users could not disable modems on MAX 1800 or MAX 2000
> >> TR 2309   TCP statistics for TCP-Clear calls were not being generated
> >> TR 2328   MAX did not operate correctly with GTE GDT5 switch and
> >>           Siemens switch.
> >> TR 2345   Password authentication did not work with BONDING calls.
> >> TR 2357   MAX 4000 sent wrong value for trap 12
> >> TR 2398   The MAX units were resetting with an FE2.
> >> TR 2426   MAX units with the combined E1/R2 and K56 hash codes
> >>           enabled did not answer modem calls.
> >> TR 2429   MAX responded to FINGER only once.
> >> TR 2438   If a mobile node tried to FTP files over an ATMP
> >>           connection, the transfer would occasionally fail.
> >> TR 2439   MAX reset - FE 1 - when simultaneous clear TCP session
> >>           users dial in.
> >> TR 2446   MAX4000 with PHS did not reject voice incoming call
> >>           via PRI
> >> TR 2466   RADIUS Accounting Start packet missing IP address.
> >> TR 2470   MAX 200Plus: USR Sportster modem connection issues
> >> TR 2475   MAX sent menu prompt twice at Terminal Server Login.
> >> TR 2478   Cannot get second channel into bind in a MAX stack
> >>           using CHAP-TOKEN-PAP.
> >> TR 2533   MAX units running bridging in a MAX stack reset with a
> >>           FE 2 or 29 and warning 175.
> >> TR 2538   The MAX 2000 E1 model did not interpret NET 5 charging
> >>           information.
> >> TR 2540   MSN client username was not understood by the MAX
> >> TR 2584   MAX 4000 reset-FE1-5.0Ap18.
> >> TR 2589   RADIUS accounting and authentication used a single
> >>           sequence of packet IDs.
> >> TR 2599   Incorrect username for RADIUS accounting was
> >>           generated when Immed Svc was defined.
> >> TR 2605   MAX 4000 reset-FE8-5.0Ap18.
> >> TR 2648   RADIUS accounting problems with Auth-Authentic=local
> >> TR 2658   MAX did not add network route for static IP user defined
> >>           in RADIUS.
> >> TR 2659   "Use Answer As Default=Yes" caused PPP sessions to fail
> >>           for Tserv login users. (RADIUS accounting problems)
> >> TR 2690   Fatal Error 2 after running 10 days.
> >> TR 2692   MAX CBCP did not call back to synchronous user.
> >> TR 2693   Fatal Error 1 in 5.0Ai23
> >> TR 2738   Fatal Error 1 on digital modem slot card failure
> >> TR 2747   MAX 200Plus created broadcast storm when routing IPX enabled
> >> TR 2771   Could not write ssnStatusValidFlag and ssnActiveValidFlag
> >>           in the Session MIB using SNMP
> >> TR 2772   SNMP did not report all callStatusGroup
> >> TR 2781   First channel of an MP+ bundle dropped on when line
> >>           utilization falls
> >> TR 2785   MAX 2000 reboots with FE 1 on SNMP query
> >> TR 2794   SNMP needed three states: Failed, Succeeded,
> >>           Transferred.
> >> TR 2804   MAX reset with FE 2 and Warning 175 every few days.
> >> TR 2820   MAX was not sending CLID/DNIS accounting request to RADIUS
> >>           when caller hung up
> >> TR 2821   MAX accounting log did not record start of 2nd channel
> >>           of MP+ call when stacked
> >> TR 2830   MAX 1800 fatal error 2
> >> TR 2843   TCP-Clear options not working in Connection profile
> >> TR 2863   PRI number plan in outgoing call using RADIUS
> >> TR 2864   PRI number plan in outgoing call using local Connection
> >>           profile
> >> TR 2865   PRI number plan in outgoing call using local
> >>           Dial Plan profile
> >> TR 2874   MAX did not callback user if CBCP Mode=User Num  and
> >>           Use Trunk Grps=No
> >> TR 2889   MAX did not add addresses assigned to CBCP users to
> >>           its routing table
> >> TR 2902   Increase immediate Telnet and Rlogin performance and
> >>           maximum # of sessions
> >> TR 2931   In 5.0Ap36 MAX 1800 reset with fatal error 8
> >> TR 2939   Multicast routes in routing table caused HP Openview
> >>           to display incorrect MAX icon
> >> TR 2952   MAX rejected incoming calls
> >> TR 2954   MAX sent CBCP callback request to non-CBCP users
> >> TR 2956   MAX 1800 did not respond to incoming BRI call
> >> TR 2971   For Raw-TCP sessions, logout message not fully
> >>           displayed
> >> TR 2980   SNMP did not report OSPF state correctly
> >> TR 2993   RADIUS Framed IP route pointed to the Ethernet
> >>           interface instead of a WAN port interface
> >> TR 3000   Some MAX loads too large for flash memory
> >> TR 3012   Syslog not reporting end-of-call information
> >> TR 3013   Syslog syntax fixed
> >> TR 3015   MAX 1800 provided wrong number for second channel
> >>           of MPP call
> >> TR 3059   MAX 2000 would reset with Fatal Error 1 and
> >>           no fatal error log on large OSPF networks
> >> TR 250002 DHCP option needed for NAT.
> >> TR 250008 Using MAXDial, M4000 used SPEECH Bearer Service for
> >>           outgoing modem calls.
> >> TR 250017 MAX 1800 could not activate a 1TR6 NT from a Info 0 state
> >> TR 250026 ELSA Microlink x.75 TA session was disconnected and hung.
> >> TR 250038 MAX 4000 reset - Fatal Error 2.
> >> TR 250046 PPTP with RADIUS connected only one end-point.
> >> TR 250066 DHCP missing from MAX 2000 and 4000.
> >> TR 250074 The MAX would not disconnect a user after an X.25/PAD
> >>           autocall was finished.
> >> TR 250088 During an X.25 session, the MAX would not always
> >>           send the entire X.25 packet
> >> TR 250098 MAX and Pipeline units overwrote static IPX routes with
> >>           SAP updates
> >> TR 250103 Frame relay fragmentation did not work with ATMP
> >> TR 250110 MAX inserted additional bytes on backup frame relay PVC.
> >> TR 250127 MAX 4000 reset with FE 2.
> >> TR 250134 Pipeline took several seconds to connect to MAX
> >> TR 250153 MAX did not send Call User Data on first X.25/PAD call
> >> TR 250157 MAX, with stacking enabled, would reject calls with
> >>           names longer than 11 characters
> >> TR 250158 MAX answering TCP-Clear calls would require reset
> >>           after 3 or 4 days
> >> TR 250169 MAX 2000 did not correctly interpret V.120 Reject frame
> >> TR 250185 During PPTP session RADIUS accounting packets not
> >>           logged correctly
> >> TR 250199 MAX not answering modem calls after receiving ISDN call
> >> * Appletalk routing not supported over Frame Relay links.
> >> * MAX reports non-SNMP version 1 PDU as authentication trap.
> >> * Good V.34 modems occasionally fail POST.
> >> * DHCP request failed if host specified an IP address not in list.
> >> * SDSL fixes for startup reliability, temperature adaptation, serial
> swap.
> >>
> >> Known issues:
> >>
> >> * When you bring up a call using the IPXPING command, Answer
> >>   appears in the IPX Route Table as an entry under the Origin
> >>   column. When the call is disconnected, the table returns to normal.
> >>
> >> * The MAX does not send IPX RIP Response packets for a
> >>   PPP-encapsulated dialup connection
> >>
> >> * In countries which support A-law encoding, 56k Modem
> >>   handshake fails when a user dials out using either the
> >>   MAX terminal server or the DeskDial client.
> >>
> >> * When dialing a busy number, terminal server outdial modems
> >>   do not report BUSY. The MAX detects the busy signal and goes
> >>   on-hook before its modem receives the busy signal. The MAX
> >>   reports Cause Code 17 in the message log, and modems disconnect,
> >>   displaying NO CARRIER. This might be a problem for users or
> >>   scripts that require a modem to report BUSY.
> >>
> >> * When Stacking is enabled, PAP-TOKEN-CHAP is not supported.
> >>
> >> * Data filters are not supported when used in conjunction with
> >>   Microsoft's CallBack Control Protocol (CBCP)
> >>
> >> Rockwell code version:
> >>
> >> * Release 6.0.0 supports Rockwell K56flex code version 1.160t.
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Kevin
> >>
> >>
> >> ++ 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>


References: