=============================================================================== AST RESEARCH, INC. SOFTWARE BULLETIN # 0120A 12-12-94 =============================================================================== MADGE TOKEN RING 16/4 SMART RINGNODE DRIVERS Production Release: 1.05 Available: June 1994 This is a new revision of the Madge Token Ring 16/4 AT Plus SMART Ringnode which includes the following software: Installation, Diagnostics, and BIOS Image. Part Number: 910764-010 3.5" diskette 1 of 1 Diagnostics 1.05 910764-011 3.5" diskette 1 of 1 Installation 1.05 910764-012 3.5" diskette 1 of 1 LAN Manager/OS/2/WFW/NT 1.05 910764013 3.5" diskette 1 of 1 ODI 1.05 Release 1.05 of the Madge Token Ring 16/4 AT Plus SMART Ringnode BIOS Image supersedes all previous releases and provides the following problem resolutions and enhancements: PROBLEMS RESOLVED: Server Drivers - OS/2 - COPYALLDATA = NO causes LAN Server 3.0 to fail Component: SMARTND.OS2 v1.30 Configuration : IBM PS/2 95 SMART 16/4 MC32 Ringnode IBM OS/2 v2.01 IBM LAN Server v3.0 Server configured as domain server with COPYALLDATA = NO set in PROTOCOL.INI Descriptions : A domain server running the above configuration will fail with an internal processing error when another server attempts to validate its user database with it. This is an issue as it is sometimes recommended to set the COPYALLDATA = NO parameter in PROTOCOL.I NI in order to obtain optimum server performance. Solution: The workaround is to remove the parameter COPYALLDAT = NO from PROTOCOL.INI Work station Drivers - DOS (Netware) - Problem: 1 Gigatape Master SAFE - SPX receive errors Component : SMARTIPX.EXE v2.23. Fixed Component: IPX.SMT v3.23. Configuration : DOS Work station using Master SAFE v1.50. Description: MasterSAFE V1.5 shows 'SPX receive errors' when used with SMARTIPX. - Problem: 2 Lost text when using ATTACHMATE EXTRA! for windows V3.3. Component: SMARTIPX.EXE v2.11. Fixed component: SMART.EXE v3.32 with IPX.SMT v3.23. Configuration: Attachmate Extra v3.3 multiple 3270 sessions. Description: The second or third session showed lost lines and corrupted text. - Problem: 3 Attachmate EXTRA! for Windows V3.32 fails. Component: SMARTIPX.EXE v2.28. Fixed component: SMART.EXE v3.32 with IPX.SMT v3.23. Configuration: IBM PC3270 v3.1. Description: Windows was intermittently hanging before clearing the logo screen. - Problem: 4 Symptom: Fails Novell IPXLOAD certification test. Component: IPX.SMT v3.05. Fixed Component: IPX.SMT v3.23. Configuration: Novell IPXLOAD certification tests. Description: The work station under test would fail by hanging. - Problem: 5 PC sometime hands if nocable attached. Component: ODI.SMT v3.04. Fixed component:ODI.SMT v3.22. Configuration: No cable attached to the ringnode. Description: The software would hang about one in four times if no cable attached to the Ringnode. - Problem: 6 SMART ODI and Netware 4.0 (VLM.EXE) Fragmentlist too short. Companion: ODI.SMT v3.08. Fixed component: ODI.SMT v3.22. Configuration: Netware DOS Requester with VLMs. Description: When running VLM, the screen would fill with random character and PC would lock up. - Problem : 7 SMART IPX and VLM hangup due to fragment list too short. Component: IPX.SMT v3.05. Fixed Component: IPX.SMT v3.23. Configuration: NetWare DOS Requester with VLMs. Description: When loading the SMART software VLM would report "PB BUFFERS not supported, set to 0" and lock the machine. Setting PB BUFFERS to 0 did not help the problem. - Problem : 8 IPX.SMT does not support VLM.EXE operating in burst mode. Component: IPX.SMT v3.08. Fixed Component: IPX.SMT v3.23. Configuration: Netware DOS Requester with VLMs. Description: The SMART software did not support burst mode with VLMs. - Problem : 9 Netware for SAA s/w update causes DOS hotkey problems. Component: IPX.SMT v3.08. Fixed Component: IPX.SMT v3.23. Configuration: Netware for SAA v1.3.31 IBM PC support v2r2 Standard version. Description: Applying Novell patch PTF354 breaks the fix mentioned in PRF685. This results in an inability to hotkey between DOS and 5250 sessions. - Problem : 10 UNIXWARE Socket change problem. Component: IPX.SMT v3.14. Fixed Component: IPX.SMT v3.23. Configuration: Univel UNIXWARE DOS work station running SMART IPX. Description : UNIXWARE changes its socket number when starting the connection. SMART IPX fails to recognize this change and keeps sending retries to the old socket number. - Problem : 11 Incorrect IPX/SPX statistics reported SPX diagnostic tools. Component: IPX.SMT v3.08. Fixed Component: IPX.SMT v3.23. Configuration: Novell Netware Care v1.0 DOS IPX work station. Description: The work station fails to report the correct values for sockets SPX connections. - Problem : 12 Novell VLM work station unable to find servers running MADGEODI.LAN. Component: ODI.SMT v3.16. Fixed Component: ODI.SMT v3.22. Configuration: Netware v3.12 or v4.0x server work station using VLMs. Description: The work station is sending out all IPX frames with an incorrect LLC header with the Control Field = 00 instead of the value 03. - Problem : 13 Attachmate 3270 terminal fails to connect with COMM598 error. Component: ODI.SMT v3.16. Fixed component: ODI.SMT v3.22. Configuration: Attachmate Extra! v3.4 (using IPX). Description: The Attachamate client's 3270 terminal fails to connect to the gateway with a comm598 error message being displayed at the bottom of the screen. - Problem: 14 CSCON returns API Error - Errorcode = 0XFFF7 after 5 mins. Component: IPX.SMT v3.05. Fixed Component: IPX.SMT v3.23. Configuration: Netware for SAA v1.3 on server DOS work station running CSCON. Description: When running the utility CSCON, the work station freezes when loading the profile and after approximately 5 min. returns with an error message API Error. Error code = 0XFFF7. - Problem : 15 SMART ODI LLC / VLM / LOGIN hangs PC. Component: SMART.EXE v3.16. Fixed component: SMART.EXE v3.32. Configuration: Netware 4.0x server Netware 4 DOS requester. Description: The work station could not login to the server. - Problem 16 SMART ODI LLC with Netware IP causes work station hang. Component: ODI.SMT. Fixed Component: ODI.SMT v3.22. Configuration: Netware/IP v1.1. Description: The work station hung when loading the VLM software. - Problem 17 Novell Windows VLM support - DOS box file copy hangs windows. Component IPX.SMT v3.18. Fixed component: IPX.SMT v3.23. Configuration: Netware DOS Requester using VLMS Windows updated using WINUP9. Description: Windows hung when attempting to copy a file from a network drive in a DOS box. NWUTILS failed to show any Netware serve volume in the resources box. Pressing and then returned a 'File allocation error' message. - Problem 18 Netsoft Elite - Unable to maintain 5250 section connection. Component: IPX.SMT v3.08. Fixed Component: IPX.SMT v3.23. Configuration: DOS Netware work station with Netsoft Elite NWSAA Gateway to AS400. Description: SMART IPX cannot maintain with SAA Gateway/AS400. They are using a Eline/400 IWS. This product uses a Windows virtual driver instead of a DOS TSR. The problem was SPX related. - Problem 19 Work station lock up when exiting Windows. Component: IPX.SMT v3.15. Fixed component: IPX.SMT v3.23. Configuration: Windows using VIPX.386 from WINUP9. Description: The problem is to do with the way that VIPX is virtualizing interrupts. - Problem 20 Frequent connection loss to distant Netware servers. Component: IPX.SMT v3.18. Fixed component: IPX.SMT v3.23. Configuration: Netware DOS requester connecting to distant Netware server. Description: Transport time is the time taken for the RIP request/response round trip and is in timer ticks (each tick is 1/18th of a second). This is returned to an application (example NETX or VLM) when it makes the IPX GET_LOCAL_TARGET call. NETX/VLM uses this transport time to work out how long it should wait before expecting a reply from a server. Novell IPX reports a transport time of 1 or 2 based on the network number of the RIP response. If the counter network number is the same as the work station network number then the transport time of 1, otherwise it is 2. IPX.SMT always return a transport time of 1, hence, IPX applications expect replies to be returned sooner than they will return which leads to frequent connection loss to distant targets. Work station drivers - DOS (Other environments) - Problem: 1 IBM PC3270 for Windows hang when closing session. Component: SMARTLSP.EXE v2.00. Fixed component: SMART.EXE v3.32. Configuration: IBM PC 3270 work station. Description: When shutting down Windows, an error message is displayed starting "CMTQD04 Stack overflow in TQ_Scavanger" which hung the PC. - Problem 2 Remote adapter status request - Node address not reversed. Component: SMARTLSP.EXE v2.28. Fixed component: NETB.SMT v3.16. Configuration: SMART netb with the anr parameter. Description: Remote Token Ring adapter's node address appears byte reversed when it is not meant to or appears not byte reversed when it is meant to be byte reversed. - Problem 3 IBM 3270 EP fails to load when no LAA is specified. Component: SMARTIPX.EXE v2.11. Fixed component: SMART.EXE v3.32 with IPX.SMT v3.23. Configuration: The IBM 3270 Emulation Program used to work without specifying an LAA on the SMARTIPX LLC command line. Now you have to specify the LAA on SMARTIPX's command line since it must be connect at open-on-load time. This is because SMARTIPX now opens the adapter on load, which prevents registration of LAAs by other LLC applications. Description A new parameter to IPX.SMT has been added to prevent the adapter from opening on load (IPX0 = N). - Problem 4 SMARTLSP ES = 6 - Adapter resource exceeded error. Component: SMART.EXE v3.32 with LLC.SMT v3.18. Configuration: Loading SMARTLSP.EXE es = 6. Description: This configuration failed to load. - Problem 5 DCA IRMA work station for Windows V2.00.00 fails. Component: SMARTIPX.EXE v2.22. Fixed component: SMART.EXE v3.32 with LLC.SMT v3.18 and IPX.SMT v3.23. Configuration: DCA IRMA work station connecting to a gateway. Description: This work station would lock when attaching to the gateway. - Problem 6 Attachmate EXTRA! - DLC interface problem. Component: SMART.EXE v3.32 with LLC.SMT v3.18. Configuration: Attachmate extra for Windows v3.4 (using DLC). Description: Attachmate EXTRA!, setup up to use the DLC interface failed to attach to the gateway. There was a bug in Attachmate DLCINTFC found that causes FRMR and lost 3270 sessions for I-frame >800 bytes. - Problem 7 Novell LAN Workplace V4.01-PING fails if LAA used. Component: SMARTLSP.EXE v2.28. Fixed component: SMART.EXE v3.32 with LLC.smt v3.18. Configuration: Novell LAN Workplace for DOS v4.01. LANSUP.COM. Description: PING sometimes fails to show the presence of active TCP nodes if run immediately after the LAN Workplace drivers have loaded. - Problem 8 IBM PC/3270 hangs after re-configuring host session. Component: SMARTLSP.EXE v2.28. Fixed component: SMART.EXE v3.32 with NETB.SMT v3.16. Configuration: IBM PC/3270 v3.0 for Windows (using Netbios). Description: If the configurations configuration is changed the PC may hang. - Problem 9 IBM PC3270 for Windows - GP if session closed after 20 seconds. Component: LLC.SMT v3.13. Fixed component: LLC.SMT v3.18. Configuration: IBM PC3270 v3.1 for Windows (using LLC). Description: When trying to close a 3270 session a GP fault is reported. - Problem 10 IBM PC3270 for Windows - GP if PIU size incorrect. Component: LLC.SMT v3.13. Fixed component: LLC.SMT v3.18. Configuration: IBM PC3270 v3.1 for Windows (using LLC). Description: If a PIU size is set to a value smaller than that of the host, the session will GP. - Problem 11 Lotus CC:mail - Windows insufficient memory error. Component: NETB.SMT v3.05.01. Fixed Component: NETB.SMT v3.16. Configuration: Server : LAN Server V3.0. Client: AST 386/33 with 8MB RAM. IBM DOS LAN Requester (WRU6000). Windows V3.1. Lotus CC:Mail V1.11. Description: Windows returns an 'Application Execution Error. Insufficient memory' when CC:Mail tries to start. 4.5 NDIS 3.0 driver - (Windows NT) - Problem 1 Invalid length LAA is accepted as correct. Component: SMARTNT.SYS v1.07. Configuration: Configure driver to use an LAA with more than 12 digit. Description: If the LAA is incorrectly entered with more than 12 digits, it is wrongly accepted as valid. This address is ignored on startup and the BIA is used. New Features Release 4.2 is the first release of the SMART LAN support software that supports the SMART 16/4 Plus Ringnote. Release 4.2 provides utilities which you can use to configure the SMART 16/4 AT Plus Ringnode. Release 4.2 provides utilities for the AT Plus Ringnode (ATPLUS.ROM). This includes a configuration utility, a remote Reset boot image, and an RPL boot image. Release 4.2 includes the first release of a new protocol suite with the SMART II software. This is the suite of TCP/IP modules: IP.SMT TCP.SMT UDP.SMT RARPD.SMT In addition, with these modules is a host interface to enable applications to access the SMART TCP/IP protocol suite. The host interface provided is compatible with Novell's LAN WorkPlace for DOS. The interface is provided by the SMART module NOVAPI.SMT. Release 4.2 contains a new bootable install diskette (disk 1) which you can use to configure your SMART 16/4 AT Plus Ringnode, run diagnostic software, and to program your SMARTROM. Release 4.2 includes the first release of the FastMac plus based NDIS2 driver for OS/2 2.x platforms. This gives significant performance improvements over the previous generation of FastMac-based drivers. Included on the distribution disks for release 4.2 are NDIS3 drivers for Window NT. Release 4.2 contains the first release of NDIS 3 driver for Windows for Workgroups version 3.11. Release 4.2 contains the first release of Netware 4.0x ODI drivers based on Madge's FastMac Plus technology. This gives significant performance improvements over the previous generation of FastMAC-based drivers. This driver can be found in the following directory on disk 3: \NETWARE.40x - Netware 4.0x server driver Release 4.2 includes support for Ringnode Mirroring with the FastMAC Plus-based versions of both the Netware 3.1x, and Netware 4.0x server driver. Ringnode Mirroring allows two SMART 16/4 Ringnodes in a server to be connected to the same ring, one designated as the Primary connection, the other as a back-up or Hot-Standby. The Primary Ringnode is monitored by the server. If the Primary Ringnode fails due to a cable fault or an adapter check, the server shuts it down safely and maintains full service to network users by automatically initializing the Hot Standby. Included on the release disks is a program called IFADAP.EXE. This program supersedes the IFIBM.EXE program which was includes in the previous releases of the SMART LAN Support Software. It gives you more flexibility than IFIBM.EXE if you want to use a single boot disk to boot work stations that have different kinds of network adapters installed. The following drivers are no longer shipped with the release: MDGDLC.OS2 MDGSH.* MDGDIRSH.* Production Release 1.01 Part Number: 910546-004 5.25 inch, 1.2MB diskette, LAN Drivers 910546-034 3.50 inch, 1.44MB diskette,LAN Drivers 910546-005 5.25 inch, 1.2MB diskette, Novell 910546-035 3.50 inch, 1.44MB diskette,Novell 910546-006 5.25 inch, 1.2MB diskette, OS/2 Config 910546-036 3.50 inch, 1.44MB diskette,OS/2 Config PROBLEMS RESOLVED: MADGE Configuration FILE: - New EISA Config File (!MDG0002.CFG) added on Disk #3 OS/2 Config. NOVELL: - The NetWare 386 server driver has been updated to provide support for 802.2-aware protocol stacks. - SMARTIPX and the IPX shell drivers have been updated and fully tested with all the latest NetWare work station shells (NETx) and most popular SPX and IPX applications. - The NetWare OS/2 ODI driver (SMARTOS2.NET) has been updated for use with OS/2 v2.0 and has been tested with NetWare OS/2 Requester v2.0. OS/2: - The OS/2 NDIS (SMARTND.OS2) driver has been updated for use with OS/2 v2.0 and has been tested with IBM OS/2 v2.0, IBM Extended Services v1.0 and IBM LAN Server v2.0 and Microsoft LAN Manager v2.1. TCP/IP: - Wollongong Pathway Access using ASI, NDIS and ODI Interfaces. - IBM TCP/IP for DOS using ASI and NDIS interfaces. - Novell NetWare LAN Workplace for DOS using the ODI interface. Files 764010.EXE, 764011.EXE, and 764012.EXE, and 764013.EXE can be found on AST's BBS, in the Systems file area. AST's BBS can be reached by dialing the following telephone number: (817) 230-6850. AST's BBS supports modem speeds up to 28.8k bps.