LANtastic by ARTISOFT Artisoft Technical Bulletin TITLE: LANtastic v6.0 Interoperability FILENAME: 60IOP.TXT UPDATED: 04.30.95 CLASSIFICATION: Connectivity AUTHOR: RRR/DCD/POH NetWare Client Support through LANtastic's NCP Interface LANtastic's new NCP option allows seamless interconnection with NetWare servers while maintaining an essentially LANtastic look-and- feel through the user interface. This product overcomes previous network limitations involving concurrently-loaded dual protocol stacks and incompatibilities between Artisoft's AILANBIO and Novell's NetBIOS. Also, many software applications are network-specific, such as Microsoft Windows, and do not consistently interpret how multiple concurrent networks present a computer's resources to it. LANtastic 6.0 removes these obstacles by handling the NetWare function calls internally. This allows the system to present LANtastic as the only network installed and alleviates such issues. It is intended as client software that allows sharing of printers and files across a NetWare network while still running in an Artisoft context. It is not intended as a NetWare administration client as the NetWare administration utilities require a NetWare-specific client such as NETX or VLM. Also, it will not load any NetWare login scripts upon the act of attaching to a NetWare server. Installing the NCP services can be broken down into three steps. 1) Install Novell's ODI low-level drivers. This provides the basic driver services to the network adapter and allows the system to understand the NetWare IPX protocol. These files would be used in place of the native LANtastic driver programs. 2) Bind the NDIS protocol to the ODI driver. LANtastic traditionally uses its own native drivers to communicate with the network adapter. If a native driver did not exist, connection to a LANtastic server could be achieved through a manufacturer-supplied NDIS driver and Artisoft's AI-NDIS program. ODI drivers do not use NDIS, but Novell's ODINSUP (ODI NDIS Support) program allows NDIS protocols to be processed through the ODI driver. By extension, this allows LANtastic network traffic to be handled by ODI. 3) Start NCP services through LANtastic's redirector program. This configures REDIR to recognize NCP traffic and allows logins and redirections to a NetWare server. Several configuration and driver files are required to setup the system -- STARTNET.BAT, NET.CFG, and PROTOCOL.INI. STARTNET.BAT is the batch file that invokes the various drivers and customizes the network session. Many examples of these configuration files are shown later in this document. NET.CFG is a configuration file that defines the system resources that the card will use such as interrupt, IO port address, shared memory address, and frametype. PROTOCOL.INI in a true NDIS configuration would perform this same function. As this system uses ODINSUP -- which routes NDIS traffic to the ODI driver, the PROTOCOL.INI is only referenced for a "buffered" statement and does not configure the network card at all. All configuration information is loaded through NET.CFG by the ODI driver. Here are some sample configurable files that LANtastic could use to login to a NetWare server and use its resources: CONFIG.SYS DEVICE = C:\DOS\HIMEM.SYS DEVICE = C:\DOS\EMM386.EXE NOEMS DOS = HIGH,UMB DEVICE = C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI SHELL = C:\COMMAND.COM /E:2048 /P FILES = 50 BUFFERS = 30 LASTDRIVE = Z STACKS = 9,256 The only network-specific line in this file is the device driver for PROTMAN.DOS. This driver is necessary to load the NDIS protocol stack. As LANtastic is a DOS-based network, it uses the LASTDRIVE=Z statement to make all the letters of the alphabet available as network drives. AUTOEXEC.BAT @ECHO OFF VERIFY ON PROMPT $P$G PATH C:\DOS;C:\UTILITY;C:\BATCH;C:\ CALL C:\LANTASTI\STARTNET.BAT This rudimentary AUTOEXEC.BAT file sets an initial path and invokes a call to load the network. STARTNET.BAT @ECHO OFF PATH C:\LANTASTI;G:\;%PATH% SET LAN_CFG=C:\LANTASTI LSL NRODI ODINSUP AI-NDIS BIND_TO=NRODI RECEIVE_BUFFERS=5 IPXODI A AILANBIO BUFFERS=2 REDIR WORKSTA1 BUFFERS=2 NCP LOGINS=20 NET LOGIN \\NOVELL1 ?"USERNAME: " ^"PASSWORD: " NET USE F: \\NOVELL1\SYS NET USE G: \\NOVELL1\SYS\PUBLIC NET USE LPT1 \\NOVELL1\PRINTQ1 NET USE LPT2 \\NOVELL1\PRINTQ2 If the card in use in this system is an AE-2 or AE-3 instead of a NodeRunner, use the NE2000 driver instead of NRODI above. This example logs into a NetWare server called NOVELL1 and attaches logical drive F: to the SYS volume, and drive G: to the PUBLIC directory off of the SYS volume. It also redirects printer ports to NetWare queues called PRINTQ1 and PRINTQ2. LSL is Novell's low-level Link Support Layer driver that allows a single driver to support multiple protocols and for a protocol to use multiple drivers. NRODI and NE2000 are MLIDs--A Multi-Link Interface Driver controls communication between the LAN board and the Link Support Layer. ODINSUP allows an NDIS driver such as AI-NDIS to bind to an ODI driver and route NDIS traffic through it. Note the RECEIVE_BUFFERS switch on the AI-NDIS command line. In order for NDIS to properly handle the data stream to the ODI driver, at least five receive buffers need to be allocated. The "A" parameter on the IPXODI command is used to save memory. By default, IPXODI takes about 16K to run. This switch pares the size down to approximately 7K by eliminating the diagnostic responder and SPX support from the program. AILANBIO is Artisoft's implementation of NetBIOS. When using the NCP (NCP_SUPPORT) switch, passwords will be automatically encrypted. The NOENCRYPT_NCP_PSWDS switch can be used on the REDIR command line to disable automatic passwords encryption. Passwords will then be sent across the network exactly as they are typed in. This is to retain compatibility with 2.x versions of NetWare that did not support password encryption. NET.CFG PROTOCOL ODINSUP BUFFERED PROTOCOL IPXODI BIND #4 LINK DRIVER NRODI FRAME ETHERNET_802.2 FRAME ETHERNET_II FRAME ETHERNET_SNAP FRAME ETHERNET_802.3 ODINSUP requires all four frametypes loaded and the "Buffered" statement under its protocol header. A particularly important section to note is the BIND reference under the PROTOCOL IPXODI section. This entry defines the frametype to which the IPX protocol will be bound. In this case, IPX is bound to the fourth frametype listed...ETHERNET_802.3. NetWare v 2.x and 3.1x used IEEE 802.3 ethernet packet types. Version 4.x and 3.2 use IEEE 802.2 stacks. By default LANtastic uses IEEE 802.2 packets with NCP support. If you are running a NetWare v 3.x or 4.x server and redir reports that it cannot find a netware server try using the 802.3 packet type. Do this by changing the command, BIND #1 to BIND #4 in the Protocol IPXODI section of the NET.CFG file, I.E., PROTOCOL IPXODI BIND #4 PROTOCOL.INI [PROTOCOL MANAGER] DRIVERNAME = PROTMAN$ DYNAMIC = YES This file is only read by the PROTMAN.DOS driver in CONFIG.SYS as the system boots. Any subsections that may be in this file (possibly from other NDIS drivers that were used for different networks) that refer to card settings are disregarded as these are defined in NET.CFG. If the system is also being configured for SMB support, other entries will be placed in this file to enable NetBEUI protocols. Issues with NETX and VLM Many native NetWare utilities make direct calls that can only be routed through a NetWare shell. These NetWare programs are known to not function using the LANtastic client services. These programs are usually not needed on a regular user basis for general file and printer access, or have LANtastic equivalents that will perform similar functions. When it is necessary to administer the system through the NetWare shells, it will be necessary to unload the LANtastic NCP support before loading NETX. If REDIR.EXE is the last TSR loaded, this can be accomplished by running REDIR/REM followed by NETX or VLM. If using NETX, The LASTDRIVE statement in CONFIG.SYS must be less than Z whereas VLM prefers LASTDRIVE=Z. NETX can then be unloaded by running NETX /U. REDIR with NCP support can then be reloaded afterwards either from the command line, or through a batch file that would restore connections and print services. NetWare 3.1X utilities known to require NETX or VLM: ALLOW.EXE ATOTAL.EXE ATTACH.EXE BCONSOLE.EXE BINDFIX.EXE BINDREST.EXE BROADCAST CAPTURE.EXE CASTOFF.EXE CASTON.EXE CHKDIR.EXE CHKVOL.EXE DSPACE.EXE ENDCAP.EXE FCONSOLE.EXE FILER.EXE FLAG.EXE FLAGDIR.EXE GRANT.EXE LISTDIR.EXE LOGIN.EXE LOGOUT.EXE MAKEUSER.EXE MAP.EXE MENU.EXE MENUEXE.EXE NBACKUP.EXE NCOPY.EXE NDIR.EXE NMENU.EXE NPRINT.EXE NVER.EXE PAUDIT.EXE PCONSOLE.EXE PRINTCON.EXE PRINTDEF.EXE PSC.EXE PSERVER.EXE PSTAT.EXE PURGE.EXE REMOVE.EXE RENDIR.EXE REVOKE.EXE RIGHTS.EXE RPRINTER.EXE SALVAGE.EXE SECURITY.EXE SEND.EXE SESSION.EXE SETPASS.EXE SETTTS.EXE SLIST.EXE SMODE.EXE SYSCON.EXE SYSTIME.EXE TLIST.EXE USERDEF.EXE USERLIST.EXE VERSION.EXE VOLINFO.EXE WHOAMI.EXE When using LANtastic v6.0's NCP support with Novell NetWare (v 3.x and 4.x) you must KNOW the NetWare servers NAME and the names of the server's resources. This information will NOT appear in the NET Menus as LANtastic Server names and resources do. You use the LANtastic NET Login commands to log into a NetWare server and use the LANtastic Net USE command to connect to the servers' resources rather than the NOVEL MAP command. When using a LANtastic client on a NetWare v 4.01 network, the NetWare server(s) MUST have bindery services installed. LANtastic's Auto-reconnect feature is NOT supported with NON LANtastic client services. AI-NDIS MUST have RECEIVE_BUFFERS=5 or greater when using NCP support and Windows. LANTASTIC SMB CLIENT SUPPORT Windows for Workgroups, using Artisoft's AILANBIO Both LANtastic and Windows for Workgroups are DOS and Netbios (NetBEUI) based Networks. Either will run on Artisoft's Adapter Independent NetBIOS (AILANBIO.EXE) or on NetBEUI /NDIS. Since Artisoft's NetBIOS is smaller and faster if you are setting up a mixed network with both LANtastic and Windows for Workgroups Servers you should configure the computers to use Artisoft Netbios. (This is done by loading the low level driver and AILANBIO.EXE in the computers autoexec.bat file.) The following steps illustrate how to configure a Windows for Workgroups server to use Artisoft's AILANBIO: 1. Install Windows for Workgroups on the computer following Microsoft's instructions; when asked to select the card, specify Novell Anthem NE2000. 2. Run Windows for Workgroups 3. Open the Network group 4. Double click on Network Setup 5. Press the DRIVERS button on the Network Setup screen 6. Make sure that the NE2000 driver is highlighted and press the REMOVE button 7. Press YES when queried: "Are you sure you want to remove the selected drivers?" 8. Press the CLOSE button on the Network drivers screen 9. Press the OK button on the Network Setup Screen 10. When queried: "The _____ Compatible network adapter has been detected in your computer. Do you want to install the driver for this adapter now?" Press NO 11. Press the CANCEL button on the Add Network Adapter screen. 12. When queried "You do not have a network adapter installed and will not be able to use the networking features of Microsoft Windows Network until you install an adapter. Do you want to continue?" Press the YES button. 13. When you are informed "Network Setup has modified your SYSTEM.INI and PROTOCOL.INI files. The old versions have been saved as SYSTEM.xxx and PROTOCOL.xxx." Press OK. Restart your computer. 14. Load the LANtastic NetBIOS, i.e. NR AILANBIO Start Windows for Workgroups network by entering the command NET START Start Windows for Workgroups with the command WIN The LANtastic computers will only need to add the /SMB switch the the REDIR command line in order to communicate with the Windwos for Workgroups Servers. Here is a typical STARTNET.BAT file with the SMB support enabled : CD C:\LANTASTI PATH C:\LANTASTI;C:\LANTASTI\NW;%PATH% SET LAN_CFG=C:\LANTASTI SET LAN_DIR=C:\LANTASTI.NET SET NWDBPATH=C:\LANTASTI\NW NR AILANBIO REDIR WINDOWS_USERNAME LOGINS=## /SMB Note that the REDIR name must be the same as a valid username on the Windows for Workgroups server. This is the case when connecting to any SMB server. Windows for Workgroups, LAN MANager, LAN Server, or Windows NT using NetBEUI and AILANBIO When there are mostly SMB servers on the network, you may wish to use NetBEUI to allow the LANtastic computers to communicate with the SMB servers, rather than converting the SMB servers to use AILANBIO. This involves using the Microsoft NDIS Protocol Manager to load AILANBIO and NetBEUI on the LANtastic computers simultaneously. The files involved with using NDIS are CONFIG.SYS, STARTNET.BAT, and PROTOCOL.INI. The NET.CFG file is not needed, as it is only used when connecting to NCP networks. Following are examples of the files with SMB support enabled with NetBEUI and AILANBIO : CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS BUFFERS=32 FILES=50 DOS=UMB LASTDRIVE=Z FCBS=4,0 DOS=HIGH DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI DEVICE=C:\LANTASTI\AEXNDIS.DOS Note that the Protocol Manager and the low level driver for an Artisoft Noderunner or AEx series adapter are started on the last two lines of the file. STARTNET.BAT CD C:\LANTASTI PATH C:\LANTASTI;C:\LANTASTI\NW;%PATH% SET LAN_CFG=C:\LANTASTI SET LAN_DIR=C:\LANTASTI.NET SET NWDBPATH=C:\LANTASTI\NW NETBEUI NETBIND AI-NDIS BIND_TO=AEXNDIS_NIF AILANBIO REDIR WINDOWS_USERNAME LOGINS=# /SMB Note that no low level driver for the adapter is loaded in STARTNET.BAT PROTOCOL.INI [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES PRIORITY = NETBEUI [NETBEUI_XIF] DRIVERNAME = NETBEUI$ SESSIONS = 6 NCBS = 12 BINDINGS = AEXNDIS_NIF LANABASE = 1 [AEXNDIS_NIF] DRIVERNAME = AEXNDS$ In this configuration, all communication is routed through the Protocol Manager, using AEXNID$ to communicate to the network interface card. There are reportedly some versions of NetBEUI that will allow the LANtastic machines to communicate without using AILANBIO. The exact version numbers of NetBEUI which have this capability have not been verified by Artisoft. NETWARE 3.x or 4.x servers AND Windows for Workgroups Servers running on ODI, AILANBIOS, and NetBEUI To allow LANtastic computers to connect to Netware AND Windows for workgroups, the NCP support must be enabled, using ODI (as described earlier in this document), and NetBEUI, as described above. Following are the files needed to establish the multiple connections : CONFIG.SYS DEVICE=C:\DOS\HIMEM.SYS DEVICE=C:\DOS\EMM386.EXE NOEMS BUFFERS=32 FILES=50 DOS=UMB LASTDRIVE=Z FCBS=4,0 DOS=HIGH DEVICE=C:\LANTASTI\PROTMAN.DOS /I:C:\LANTASTI Note that there is no low level adapter driver in the CONFIG.SYS. STARTNET.BAT CD C:\LANTASTI PATH C:\LANTASTI;C:\LANTASTI\NW;%PATH% SET LAN_CFG=C:\LANTASTI SET LAN_DIR=C:\LANTASTI.NET SET NWDBPATH=C:\LANTASTI\NW LSL NRODI ODINSUP IPXODI NETBEUI NETBIND AI-NDIS RECEIVE_BUFFERS=5 IRQ=14 BIND_TO=NRODI AILANBIOS REDIR WINDOWS_USERNAME LOGINS=10 NCP SMB In this configuration, all communication is routed through the Protocol Manager, using NRODI to communicate to the network interface card. PROTOCOL.INI [PROTMAN] DRIVERNAME = PROTMAN$ DYNAMIC = YES [NETBEUI_XIF] DRIVERNAME = NETBEUI$ SESSIONS = 6 NCBS = 12 BINDINGS = NRODI LANABASE = 1 [AEXNDIS_NIF] DRIVERNAME = AEXNDS$ Note here that even though AEXNDIS_NIF exists in the file, it is not used. All bindings are to NRODI, which is loaded in STARTNET.BAT. NET.CFG PROTOCOL ODINSUP BUFFERED PROTOCOL IPXODI BIND #4 LINK DRIVER NRODI FRAME ETHERNET_802.2 FRAME ETHERNET_II FRAME ETHERNET_SNAP FRAME ETHERNET_802.3 LANtastic v6.0 NetWare Client BUZZWORDS: IPX Internetwork Packet Exchange is the native transport protocol for NetWare. It is similar to LANtastic's NetBIOS. It provides a connectionless service between two computers via a network. On the OSI model IPX provides the Network layer interface. IPX does not guarantee either packet delivery or packet delivery sequence. This interface may also be referred to as the Datagram Interface. IPXODI A version of IPX designed to work with NetWare's ODI. LSL Link Support Layer - This program enables the workstation to communicate using several protocols. LSL serves as sort of a central switchboard through which all of the other modules communicate. IT determines which protocol stack should receive the packet. (Compare this to the NDIS protocol manger discussed earlier.) MLID Mufti Link Interface Drivers - The low level Network Adapter driver used with ODI. Artisoft provides the driver NRODI.COM with our Noderunner Adapter cards. Artisoft currently does NOT provide a MLID for the Aex series of adapters. The MLID controls communication between the LAN board and the LSL. When the MLID receives a packet of data is removes the MAC header and passes the packet to the LSL. NCP Network Control Protocol is the language that a NetWare workstation uses to communicate with a NetWare server. This provides a mechanism for client/server interaction between the workstation and the server. NET.CFG Net.cfg is an ASCII text file that changes the NIC's interrupt and memory address. The ethernet frame type is also set in this file. NETx The Workstation shell, similar to LANtastic's redirector, this program provides NetWare's basic Network Services. It communicates to the server using NCP via IPX. ODI Open Data-Link Interface is the datalink spec developed jointly by Apple and Novell. ODI is designed to support multiple protocols on a single network and on a single network card. Unlike Microsoft's competing NDIS specification Novel ACTIVELY tests and APPROVES all ODI drivers. ODI drivers and protocols are normal tsr's that can be dynamically loaded and unloaded as the computer runs rather than being device drivers that have to be loaded in the config.sys upon system bootup. NetWare v 3.10 and v 2.2 and above all ship with ODI support. ODINSUP This is a NDIS/ODI shim. It allows NDIS protocol stacks to run unmodified over the ODI LSL. SPX Sequenced Packet Exchange provides the Transport Layer on the OSI model. This is connection oriented communication between computers. SPX provides guaranteed delivery of packets, in sequence, and without errors or duplications. LANtastic v6.00 Interoperability Memory Usage and configurations LANtastic v6.0 SMB Client BUZZWORDS: AILANBIOS Adapter Independent LANtastic NetBIOS - Artisoft's version of IBM's NetBIOS. When coupled with a compatible low-level driver this netbios will work with any network adapter. AEXNDIS An Ailanbios/NDIS shim. MAC Media Access Control - a protocol governing access to transmission media (network adapter cards). NDIS drivers are often called MAC Layer drivers. NDIS Network Driver Interface Specification - Specification for a generic device driver for Network interface cards. Jointly developed by Microsoft and 3Com. Microsoft provides a certification kit that allows driver developers to test and certify their own drivers. NetBIOS Network Basic Input Output System - An application programming interface (API) for data exchange and network data transport.. Developed by Sytex for IBM in 1984. NetBEUI Network Basic Extended User Interface - Developed by IBM in 1985 for use with Token Ring network adapter cards. NetBEUI consists of a program NETBEUI.COM that provides the API and a low Level Driver specific to the network adapter card. Typically used with NDIS and by Microsoft and IBM with their SMB based family of Networks. PROTMAN Microsoft's Protocol Manager - Protman þwires the protocols together with the device drivers (BINDS). When a packet is received it is offered in turn to each protocol based on the order loaded. SHIM A program that converts software protocols - a translation engine. SMB Server Message Block - IBM's and Microsoft's server control language a subset of SNA. Used by Microsoft's and IBM's family of Networks. Windows for Workgroups, Windows NT, LAN Manager, LAN Server, and their compatibles. SNA Systems Network Architecture - IBM's protocol governing mainframe communication. SNP Server Network Protocol - Artisoft's server control language. Used by LANtastic workstations to communicate with servers over the transport protocol. WORKSTATION MEMORY USAGE CHART Actual memory usage may vary depending on the versions of the software used and the command line switches. ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄ¿ ³SERVER AND TRANSPORT³ MEMORY ³ MEMORY ³MEMORY ³ ³PROTOCOLS ³ ³ IPX /D ³IPX /A ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic - ³ ³ ³ ³ ³SNB using AILANBIOS ³ 43,702-43k ³ N/A ³N/A ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP & ³ ³ ³ ³ ³SMB using AILANBIOS ³ 49,376-48k ³ N/A ³N/A ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP & ³ ³ ³ ³ ³SMB using NetBEUI ³ 70,420-69k ³ N/A ³N/A ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP ³ ³ ³ ³ ³w/AILANBIOS ³ ³ ³ ³ ³& SMB w/NetBEUI ³ 106,544-104k ³ N/A ³N/A ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP & ³ ³ ³ ³ ³NetWare w/ODI ³ 96,640-94k ³93,024-90k ³7,664-86k ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP & SMB ³ ³ ³ ³ ³w/AILANBIOS AND ³ ³ ³ ³ ³NetWare using ODI ³ 101,616-99k ³ 98,000-96k ³92,640-90k ³ ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄ´ ³LANtastic SNP & SMB ³ ³ ³ ³ ³w/NetBEUI AND ³ ³ ³ ³ ³NetWare w/ODI ³ 138,736-135k ³135,120-132k ³129,760-127k³ ÀÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÙ INDIVIDUAL PROGAM MEMORY USAGE AI_NDIS.EXE Artisoft AILANBIO/NDIS shim 13k AILANBIO.EXE Artisoft Adapter Independent NetBIOS 21k NETBEUI.EXE Microsoft NetBEUI 36k IPXODI.COM Novell IPX protocol 16k with /D switch 12k with /A switch 7k LSL.COM Novell Link Support Layer 5k PROTMAN.DOS Microsoft Protocol Manager 6k NRODI.COM Artisoft Low Level Noderunner ODI driver 5k REDIR.EXE LANtastic Redirector 18k with NCP support 28k with SMB support 23k with NCP and SMB support 33k NOTE-NETBEUI.EXE can be obtained from the file NTB600.EXE. ARTISOFT, Inc. makes no warranties as to the completeness or accuracy of this document. LANtastic is a trademark of ARTISOFT, Inc. Brand names, company names, and product names are trademarks or registered trademarks of their respective companies. We have several methods, you can use to receive support. Our normal technical support line is 520-670-7000 (7a-5p MT). You can post a message on CompuServe in the Artisoft Forum. CompuServe is answered in 1 business day (if left before 6am MT). You can post a message on the Arti-Facts BBS @ 520-884-8648 or 520-884-9675 (14.4k) [8,n,1]. For immediate access to a technician, you can contact our Express Service @ $2.50/minute with extended hours of 6a-9p MT and 6a-5p MT on Saturday. Express service can be obtained at 1-900-555-8324 (billed to phone) or 1-800-293-3936 with a valid AmEx, MC, or VISA card. Please Note During Daylight Savings our Times are 1 hour earlier.