Rules of Thumb, NetWare Access Services v1.3 December 28, 1992 NetWare Access Services is a powerful, practical, and cost effective way for multiple remote users to access NetWare LANs. We asked our engineers what components they would use if they were configuring NetWare Access Services for optimal reliability, performance, and ease of use, and to provide technical tips for users. This document reports what they said. NetWare Access Services = The Novell software which provides simultaneous support for up to 16 remote DOS sessions on a NetWare LAN. Application Server = The dedicated 486 or 386 PC or PS/2, Access Services runs on. For the very latest technical information please refer to Compuserve/NetWire; NOVLIB Library 9 and NOVA Section 2 (Communications) . VERSION 1.3 NEW FEATURES Microsoft Windows Support ONLAN/PC Supports Windows 3.0 and 3.1 applications running in real or standard mode (only). Mouse Support OnLAN/PC V1.3 users have complete mouse support for Windows applications. In addition they can use a mouse with most DOS applications. With some DOS applications, the mouse may work differently than usual. Zmodem The Zmodem file transfer protocol may now be used with terminal emulation packages which provide it. NASI Ports The option of having users call in through the ports on your NACS instead of the adapter ports on the Application Server. Improved Memory Management Support - Up to 64MB of RAM can now be accessed. - QEMM Stealth is included and supported Easier International Keyboard Support The ability to chose among DOS's national language character sets during NASGEN. Pregenerated IPX.COM Files Includes a disk with drivers for 10 common LAN adapters (see list below). During NASGEN hardware installation, you select the driver that matches your adapter. Scripting Instructions Over 100 pages of scripting instruction for OnLAN/PC. APPLICATION SERVER Almost any 486 and 386DX based PC or PS/2 can be used as an Application Server (machine on which Access Services is installed). We expect that all machines that were certified for Access Server V1.0 and 1.2 will work with V1.3. 386SX machines are not recommended as they use a 16 bit bus, which results in multiple session speeds too slow to satisfy users. In general, a machine with the most powerful available CPU should be chosen. Machine features such as: - Disk slow down - Memory caching - Shadowing, including RAM shadowing and BIOS shadowing Can not be used, and it is important that the machine you select include clear instructions for disabling such features. In addition, you may want the ability to disable built in VGA in order to increase memory in the virtual sessions. Refer to the NetWork Support Encyclopedia or the Novell IMSP files in NetWire, NOVLIB for a complete list of 486 and 386 machines certified for use with NetWare Access Services. The machine must be equipped with a high capacity (1.44MB 3.5" or 1.2MB 5.25") disk drive. A 1.2MB drive may be inadequate for some configurations as the required files may be slightly to large to fit, or leave too little space for an audit log. For example, a 1.2MB disk will probably be too small if you configure for an "international" keyboard. A hard drive is optional, but recommended, particularly if the audit log feature will be used. We recomend that users not be given the ability to use the Access Server's drives. They should use network drives instead. The serial and parallel ports on the machine will not be used. Memory NetWare Access Services can use up to 64MB of memory. All memory over 1MB MUST be extended memory, but Access Services will configure it to expanded memory within the sessions. The minimum configuration is 2.6MB of RAM (enough to support a single user session and an operator session without expanded memory). The Application Server requires 1MB of RAM plus an additional amount of memory for each concurrent Access Services virtual session you expect to support. To determine the minimum amount of memory required, use the following formula: 1MB + (N x 800K) + (S x E) N = the # of virtual sessions to be supported. S = the # of virtual sessions (including Windows sessions) needing expanded memory. E = the expanded memory required for each of those sessions. The value for E must be the same for all sessions requiring expanded memory. You cannot vary the expanded memory limit from session to session. If you are using Windows in one or more Access Services session E must = AT LEAST 2MB of expanded memory. In addition, adequate address space must be available in the high memory range, from 640KB to 1024KB, to support all necessary adapters (a LAN adapter, a video adapter, and usually a remote communications adapter). Consult the adapter manufacturer's documentation for memory requirements. See Appendix C of the NetWare Access Services v1.3 Administration Guide for background on avoiding conflicts in the high memory range. LAN Adapters The Application Server must connect to the LAN through a NIC adapter (Network Interface Card). We recommend a 16 bit or 32 bit nonmemory mapped NIC for best performance and optimal memory. NIC Drivers included with Access Services v1.3 NIC Description Bus Type --- ----------- -------- NetWare NE1000 Ethernet 8 bit NetWare NE2000 Ethernet 16 bit NetWare NE/2 Ethernet microchannel NetWare Ethernet NE2100 Ethernet 16 bit NetWare Turbo RX Net Arcnet 8 bit 3COM 3C503 Etherlink II* Ethernet 8 bit 3COM 3C505 Etherlink Plus* Ethernet 16 bit 3COM 3C523 Etherlink/MC Ethernet microchannel IBM Token Ring Token ring 8 bit IBM PCN II & Baseband Broadband/Baseband 6 bit or microchannel * On board memory must be disabled We recommend that you upgrade your LAN drivers. NASGEN's upgrade option does not automatically do that. To update LAN drivers from NASGEN's Main Menu, select the Modify option in the NASGEN Main Menu and update your LAN driver. Video Adapters The Application Server must have a CGA, MDA, EGA, VGA, HGC, or HIC video adapter. A CGA card is recommended since the use of a CGA card ("CGA only", not multi graphics): - Provides by far the most session memory. - Limits the chances of installation memory conflicts. - Is supported by almost all business software. If the Application Server and the workstation have different types of video adapters the workstation will display the lower grade graphics mode. Characters in character based applications will display according to the standard set by video adapter and monitor in the workstation. The maximum display quality supported for workstations through Access Services is 640 x 480 resolution in 8 bit video mode. For text characters the resolution is 80 x 25. The following table lists the memory available per session when various types of video adapters are installed in an Application Server: - with WNIM board(s) - with a nonmemory mapped NIC. - without the use of Stealth. The exact value is determined by the software and hardware configuration in the Application Server. Other configurations will provide either more or less less memory. To avoid memory problems, use 8 bit video mode. Video Adapter RAM Available for Each Remote Session ------------- -------------------------------------- CGA 550KB to 580KB VGA & EGA (converted to CGA)* 476KB to 526KB HGC 470KB to 520KB VGA & EGA 400KB to 450KB * Windows will hang the Application server if VGA/EGA is converted to CGA. In order to use graphics, video adapters with graphics capabilities must be present in both the Application Server and the remote workstation. Graphics applications should be configured for the graphics mode installed in the Application Server. Graphics on the Macintosh OnLAN/Mac supports MDA, CGA, EGA, and VGA graphics. VGA and Monochrome Monitors If a VGA adapter is installed in an Application Server equipped with a monochrome monitor, be sure to specify MVGA-Monochrome Video Graphics Array for the Display adapter type field in the Hardware Configuration screen when you run NASGEN. REMOTE COMMUNICATIONS ADAPTERS The serial ports (COM ports) built into the Application Server can not be used for either incoming or outgoing communication. A workstation must connect to Access Services through a: - LAN, or - Port on a remote communications adapter installed in the Application Server, or - Port in a NACS server. Remote communications adapters support connections via direct cable, modem, multiplexer, and X.25 Public Data Networks. In order to increase the amount of memory for virtual sessions use remote communications adapters that use a minimum amount of shared memory. Refer to each adapter's manual for information on its effect on available RAM. We recommend using the following certified adapters. Remote Communications Adapter Interface Company/Phone Number ----------------------------- --------- -------------------- WNIM+ (4 port, 8 bit adapter) RS-232 Microdyne Corporation 800-255-3967 DigiCHANNEL PC/8e RS-232 Digiboard 612-943-9020 ACI (8 Ports) RS-232 Newport Systems Solutions 714-752-1511 XCI (X.25 Comm. Interface) RS-232 RS-422 Newport Systems Solutions V.35, X.21 More than one kind of board can be used in a single Application Server. WNIM+ Drivers A WNIM+ driver is provided on installation disk #2. During Access Services installation, the WNIM+ driver will copy into the NASGEN directory. (the driver will also work with a WNIM Z-80) Digiboard and Newport Drivers Secure the drivers for DigiCHANNEL and Newport boards from their respective manufacturers. These drivers should be copied to the NASGEN directory on the PC where you will run NASGEN (some manufacturers provide driver installation programs that copy the driver files into the NASGEN directory). IBM ARTIC Board Drivers An IBM ARTIC board driver is provided for customers who have already have the following models ONLY: Realtime Interface Coprocessor Multiport Adapter Model 6240 (00F5525) Model 6241 (00F5527) Realtime Interface Coprocessor Multiport/2 Adapter Model 6263 (09F1897) Model 6247 (16F1820) The driver does not support current versions of the ARTIC board or other versions not listed above. To use one of the ARTIC boards listed above: 1. Copy all of the files in the NCDARTIC directory on disk #3 into the NASGEN directory. 2. When NASGEN's Hardware Configuration screen appears, highlight the Remote Communication Adapter Type(s) field, and press , the driver appears in the Known Driver(s) window under the title IBM Multiport (ARTIC) Board(s). NASGEN Hardware Configuration screen Any drivers that have been installed in the NASGEN directory will display in the Known Driver Window. Installation is completed by highlighting the Remote Communications Adapter Type(s) field and pressing . TOKEN RING Token Ring Driver and WNIM+ Adapters If you have a token ring driver and the WNIM+ remote communications adapter installed, change the WNIM+ adapter's software memory address default from CA00h to CE00h when you run NASGEN. NASGEN automatically reconfigures the token ring driver's memory address range to start at C800h, which would overlap and conflict with the WNIM+ adapter's default software memory address. In NASGEN set the: - 8KB token ring ROM address to CC00 - token ring RAM address to C800 for 16KB Set the switch settings on the token ring adapter accordingly. Many sites with token ring LANs have placed a second (non-memory mapped, Ethernet NIC) in their file server and connected only the Access Services machine to that NIC. This: - Maximizes virtual session memory. - Improves the speed of communication between Access Services and the file server as there is no competing traffic on the cable. - Simplifies installation. Source Routing To support token ring source routing for Access Services sessions, edit NASAUTO.BAT (in the ACCESS directory) to load ROUTE.COM after loading IPX.COM. NETWARE Access Services v1.3 works with: - NetWare v3.10* through v3.11 and, - NetWare v2.10 through v2.2 * NetWare 3.10 users must install a patch which is available with instructions in the file SCBFIX.ZIP in NetWire NOVLIB LIBRARY 4. Only NetWare 3.11 supports a LAN connection to Access Services via AppleTalk. NetWare Access Services does not support Named Pipes. Although a second NIC with an ODI driver can be installed the primary connection to the LAN can not be ODI. DOS Versions Supported - PCDOS or MSDOS 3.3 or higher - DR DOS 6.0 or higher. The DOS used has an effect on the amount of RAM available in each virtual session as the larger the COMMAND.COM the less RAM available. - DOS 4 will provide less memory than DOS 3.3. - DOS 5 will provide less memory than DOS 4. CONNECTION TYPES Multiplexer (MUX) Connections Access Services supports multiplexers that provide RTS/CTS hardware flow control. Multiplexers that require XON/XOFF flow control or insert special characters in the data stream are not supported. Direct Connections Workstations and ASCII terminals can be connected directly to the Application Server through a RS232 null modem cable. There are several kinds of null modem cable. Make certain that you use a null modem cable which is properly wired for the ports of the communications adapter board you are using. If you are using OnLAN/PC to connect; - set the "Connection Started By" and "Connection Ended By" fields to DCD. - set the DTR state to "On While Connected". However, if your null modem cable does not support DCD, set DCR to "Always Connected" . NACS/NASI Connections You can configure Access Services v1.3 to use ports on communicators adapters in its Application Server OR in a NACS, but not both at the same time. Three kinds of NACS/NASI connections are available: A. Inbound, with a workstation dialing into Access Services via a port on the NACS. B. Outbound, with a workstation on a remote LAN using a NACS port to dial out to Access Services. C. Outbound, with a remote caller using an Access Services session to call out through a NACS port on the central LAN. If, during NASGEN you acquire and configure NACS ports, once Access Services Server is brought up, it will own the NACS port(s) until Access Services is brought down. Configuring to Use the NASI Connection NASI v2.x and v3.x cannot run at the same time. Therefore, if you are using: - NASI v2 to get NACS ports for calls coming into Access Services. - Do not have NASI v3 in a path were it can be reached by Access Services users. - NASI v3 to get NACS ports for calls coming into Access Services. - Do not have NASI v2 in a path were it can be reached by Access Services users. To use NASI3 in Access Services Sessions: - Use V3.02F or higher (NASI3.EXE V3.02f is provided with the NetWare Access Services software and will be copied to the NASGEN directory during installation.) - Make a copy of NASI3.EXE, changing its name to NASI.EXE. For example, enter COPY NASI3.EXE NASI.EXE. - Place the renamed file where it can be reached by Access Services users ONLY. If you use NASI v2.x: - NASI 2.x in an Access Services session must be started with the /D parameter. (type: NASI /D) - It must be v2.09 or higher. Previous versions are not compatible with Access Services. - If you have a version earlier than 2.09 you can upgrade to NASI V2.14 and NACS V2.15 by downloading NACS2.ZIP from NetWire NOVLIB Library 9. - NASI 2.x uses 41KB of memory. Modem Connections Each user must have a modem that is compatible with the modem on the Application Server. NetWare Access Services supports asynchronous transmission speeds up to 38.4 Kbps using dial up modems (such as the Hayes Smartmodem) with features such as data compression. We recommend using V.32 error correcting modems. The certified modems can be chosen from the Accesss Services and OnLAN menus. It is usually very difficult to get modems not on the menus to work. The list of supported modems is at the end of this document. REMOTE WORKSTATION REQUIREMENTS The types of workstations that can connect to the Access Server are shown below together with the software required by each workstation. NETWARE ACCESS SERVICES CONNECTIONS IBM PC# MACINTOSH TERMINAL OS/2 ------- --------- -------- ---- MODEM P* M* N T MUX P* M* N T DIRECT P* M* N T NetWare LAN P M X X NASI P X X T X.25 PDN P* T N T LAN via AppleTalk X M X X # IBM PC or a compatible computer running DOS (including Windows) P = ONLAn/PC1.2 M = ONLAN/MAC 1.2 (Windows support is currently not available with a MacIntosh) N = No software required T = Terminal emulation program X = Not Available * May also use a terminal emulator program, but OnLAN is preferred. OnLAN/PC An IBM PS/2, PC or compatible computer can use OnLAN/PC v1.30. OnLAN/PC is provided with NetWare Access Services and can be copied on all PCs that may use it to connect with NetWare Access Services. PCs must have: - A disk drive that uses floppy disks holding 720KB or more - At least 350KB of available RAM. - A serial communications port. OnLAN requires: - 8N1 (8 bits, no parity, 1 stop bit)) - XON/XOFF disabled While running OnLAN/PC, workstation users do not have direct access to their workstation's disk drives. However users can: - Transfer files between the LAN and their disk drives using the ONFILE utility. - Temporarily exit the Access Services session by selecting "Exit to DOS" in the Session Options menu and use their workstation drives (but not to use data on those drives for the Access Services session). Users of OnLAN/PC v1.0x or v1.2x can use the ONFILE file transfer utility to download OnLAN v1.3. To avoid overwriting the active OnLAN/PC program, users should download the new files to a directory that does not contain the OnLAN/PC files. MACINTOSH OnLAN/MAC is provided with NetWare Access Services and can be copied on all MacIntoshes that may use it to connect with NetWare Access Services. Access Services currently provides no Windows support or mouse support for Macintosh users. An attempt to run Microsoft Windows in an OnLAN/Mac session will hang the Application Server. A Macintosh with at least 512KB of RAM and System 6.0 or higher can use OnLAN/MAC to utilize Access Services DOS sessions. OnLAN/Mac v1.2 is provided with NetWare Access Services v1.3. A NetWare v3.11 file server running NetWare for Macintosh v3.x or greater is required if any MacIntosh's will use AppleTalk to connect to NetWare Access Services. ONFILEM is obsolete. OnLAN/MAC users should use ONFILE instead. OnLAN/Mac v1.0x users should use ONFILE to download OnLAN/MAC v1.20. To avoid overwriting the active OnLAN/Mac download the new files to a folder that does not contain the OnLAN/Mac files. PC Terminal Emulation other than OnLAN A PC should be able to use any terminal emulation software (such as Procomm Plus) to connect to NetWare Access Services. Only the top or bottom 24 lines will display in 25 line terminal emulation. Users can switch between the bottom and top with ESCAPE B or ESCAPE T. You have only two file transfer choices with communications programs other than OnLAN: - Zmodem, if the emulation package supports it (if, not Xmodem MAY work). OR, - ONFILE. (Because the ONFILE has limited features when used outside of OnLAN be careful to specify the correct path of the source and destination directories. Multiple connections to Access Services can be established with the communications software that is shipped with: - OS/2 v2.0 (PM Terminal: Softerm). For an IPX connection the NetWare Workstation Kit for OS/2 v2.0 is required. - Microsoft Windows (Terminal). ASCII TERMINAL TYPES SUPPORTED BY NETWARE ACCESS SERVICES Terminal Type Terminal Type 1. OnLAN v1.2x and above 17. Link PCTERM 2. Ampex 230 18. LSI ADM 3A 3. ADDS Regent 19. Prime PST100 4. ADDS Viewpoint 20. Qume (102/108) 5. ANSI Standard 21. Soroc 6. Beehive 4/78/DMS 22. Tektronix 7. Dasher D410/D460 23. Teleray 8. DEC VT-52 24. TeleVideo 9. Digital Microsystems 25. Visual V330 (DG) 10. Esprit III 26. VT-100/200 1 11. Falco FAME III 27. VT-100/200 IBM font 12. Hazeltine 1500 28. Wyse 50/100/300 13. Hewlett-Packard 29. Zenith Z-19 14. IBM 3101 30. Zenith Z-29 15. Kaypro 31. OnLAN v1.0x 16. Kimtron KT-7 PC 32. OnLAN v1.3x with parity * The VT-100 is X3.64 compatible; the ANSI selection is set for non X.34 compatibility. If you experience attribute problems with your terminal, try switching between the ANSI and VT-100 selection. ** This selection results in VT-220 emulation without Windows and mouse support instead of the full OnLAN/PC support and features. Some terminal keys (such as the cursor and function keys) may not operate after installation. The operation of these keys can be changed using "MODTERM" as described in Appendix I of the Access Services v1.3 Administration Guide. WORKSTATION SESSIONS Execution Speed Only keystrokes and screen updates travel over the remote communication lines keeping traffic on the line to a minimum. All processing takes place on the Application Server. Access Services performance differs based on: - Application Server processor speed - How intensely the application uses the processor - Graphics - Line speed - Network traffic A benchmark test was performed on a COMPAQ 386/33 with a 16 bit Ethernet adapter running the Access Services software. One to 16 remote users connected to this Access Server and ran typical business software in text mode. The time required to complete the test was compared to a single standalone 8MH IBM AT and a 4.77MH PC. - When 1 or 2 users were connected processing speeds were MUCH better than for the stand alone AT. - As more users were added performance slowed proportionately until there were a total of 10 users connected to the Access Server and processing speeds became equivalent to an AT. - Even with 16 users, each session on the Access Server processed at speeds more than twice as fast as on 4.77MHZ PC. Display Speed Since the display data travels over the connection lines, applications with detailed graphics require more time to display at the remote workstation. - Most character oriented applications show little performance degradation due to the communications link. - Applications that depend heavily on graphics suffer degradation in screen display time. Printing Access Services users can print on a printer attached to: - their remote workstation - the remote LAN - the LAN Access Services resides on However, you may not connect a printer to the Application Server. Access Services users must use the NetWare CAPTURE and ENDCAP commands in the correct sequence. Disk Drive Mapping When a workstation logs into Access Services and then logs into a file server, the workstation drive mapping is determined by the Access Services configuration (not the workstation disk drive configuration). If the Access Services installation specified that users could not access the physical disk drives, the user's network drives will begin at drive A. If users can access the application server disk drives, the letter for the first network drive is determined by the physical drives installed. If the application server has one hard drive, the first network drive letter is F. When two hard drives are installed, the first network drive letter is G. To make sure that the user gets the usual network drive mappings starting at F:, (when the application server has one network drive) enter the following in the system or user login script: MAP F: = A: DRIVE F: Accessing IBM SNA Mainframes Up to 16 simultaneous remote users can access IBM mainframe(s) if NetWare for SAA and NetWare 3270 LAN Workstation for DOS are installed on the LAN. To use 3270 LAN Workstation for DOS, you must select an OnLAN terminal (terminal type 1 or 31 in the list of terminals above. 3270 LAN Workstation for DOS does NOT support: - ASCII terminals - OnLAN with parity (terminal type 32) Access Services supports Send-Receive file transfers and 3270 Model 2 emulation (using basic data stream only). OnLAN users should set the OnLAN Special Keyboard Handler to level 1 or higher. (Note that the administrator can prohibit user access to the Special Keyboard Handler in NASGEN.) For optimal performance, we recommend that you maintain only one DOS based 3270 display session per user. If you are disconnected after running KEYDEF.EXE: 1. Run NASGEN to reconfigure the Application Server. 2. Go to the NASGEN General Configuration screen. 3. Set the Convert EGA/VGA to CGA option to Yes. WARNING: If you will run Windows in application server sessions, DO NOT set Convert EGA/VGA to CGA to Yes, because it will cause the application server to fail. 4. Reboot the application server and try WSLAN again. NetWare 3270 LAN Workstation for Windows is not supported because it runs in Windows enhanced mode. Accessing an AS/400 Remote users can connect to NetWare Access Services and access an AS/400 via NetWare 3270 LAN Workstation for DOS but not via PC Support (incompatibility with DESQview) or 5250 emulation. TCP-IP Hosts Including UNIX Access Services users can use NetWare LAN Workplace for DOS to access UNIX and other TCP/IP hosts. To do this a second NIC must be installed in the Application Server. This NIC must have an ODI driver and be compatible with LAN Workplace for DOS. ASTATUS Enables users to obtain: - their port and session number. - available RAM per session. - IPX packet size being used by Access Services. For example: Available Session memory: 534112 bytes IPX Packet Size: 512 Netware Access Server Terminal Number: 01 NetWare Access Server Port Number: 01 NetWare Access Server Session Number: 01 The terminal number indicates the OnLAN/PC terminal type used by the user (type 1 through 32). If the user is logged in through a LAN connection, the port number is L. See Access Services' READ.ME for information regarding the installation and use of ASTATUS. NetWare NETBIOS Emulator You can run multiple NetBIOS sessions with NETBIOS emulator v3.02C or later. A compatible version of NetBios can be found in NASNET.ZIP in NOVLIB Library 9. NETBIOS must be loaded from NASAUTO.BAT after loading IPX and MEMMGR. SEND COMMAND WHEN RUNNING IN QEMM STEALTH MODE If you are running the Application Server in QEMM Stealth mode (by setting Enable Stealth Memory Management to YES on the NASGEN General Configuration screen or have edited the QEMM.SYS device line in CONFIG.SYS to run QEMM in Stealth mode), instruct users to issue a CASTOFF ALL after they start a session. The receipt of a SEND while Access Services is running in Stealth mode will cause the Application Server to hang. MICROSOFT WINDOWS SUPPORT 1. Windows based applications are only supported in REAL and STANDARD mode. If a user tries to run Windows in ENHANCED mode, Windows will fail to load and the user will be returned to the DOS prompt (and the Application Server may crash). 2. Access Services v1.3 is able to run most Windows applications. However, each Access Services virtual session supports only a single Window's session. All Access Services multitasking must be provided by the Access Services Session Manager rather than Windows. 3. For Windows support both the Application Server and the remote PC need a VGA or EGA video adapter and monitor. 4. "Maximum Expanded Memory per Session" in NASGEN must be set to a minimum of 2MB (4MB would be better). 5. The "Convert EGA/VGA" option in NASGEN must be set to NO. 6. We do not recommend running more than 6 simultaneous Windows sessions through the Application Server. If you must run more than 6 simultaneous Windows sessions through an Application Server, download ACEWIN.ZIP from NetWire NOVLIB Library 9. (ACEWIN.ZIP does not yet exist as of December 29, 1992) 7. Do not run Windows in an operator session initiated from Access Service's "Information Menu". 8. Do not install personal Windows directories on the Application Server's hard drive. You should install personal Windows directories on a file server that Access Services users will have access to. 9. Do not use the View Session option on Access Service's "Information Menu" to view a Windows session running in STANDARD mode. 10. The View Session option provides a limited ability to view a Windows session running in STANDARD mode. You will see only a "snapshot" of the single window without updates. 11. Do not use the Windows DOS prompt icon to toggle to a DOS session. Instead, press to bring up the Session Options menu, then select Remote Session Manager and initiate a new DOS session. 12. If the Application Server is running under DR DOS 6 and users are running Windows 3.0A or 3.1, choosing the "Go to DOS" option from the OnLAN/PC Session Options menu will cause the OnLAN session to hang. Supported Applications Most commercially available software can be used with NetWare Access services. Two lists are provided below. 1. A list of applications known to be compatible. 2. A list of the types of software which are not compatible with examples. Check with the Sysop in NetWire NOVA Section 9 (Communications) for later information. If you wish to use software which is not listed we suggest that you try to run it in real mode as only applications which are DPMI or VCPI compliant and relinquish control of the processor are supported in protected mode. Product Publisher -------- ---------- Advanced Revelation v2.1 Revelation Technologies Agenda v2.0 Lotus Development Applause II v1.5 Borland ASCOM IV/Network v1.42 Symantec AskSam v5.1 AskSam Systems Borland C++ v3.1 Borland International Btrieve v5.10A Novell cc:Mail v3.15 Lotus CED The Cove Software Group Clipper v5.0 Nantucket CorelDRAW! v3.0 *(1) Corel Corp. The Coordinator II v2.01 *(2) Action Technologies Coordinator for Windows v1.2 Action Technologies Crosstalk Mark IV Digital Communications Associates Crosstalk for Windows v1.2 Digital Communications Associates Crosstalk Mark IV LAN v2.01 Digital Communications Associates Current v1.14 IBM DAC Easy Network Accounting DataFlex v3.0 DataAccess Corp. dBASE IV v1.5 Borland Direct Access v5.1 *(3) Fifth Generation Systems DisplayWrite 5 v2.1 IBM eMail v1.70e Da Vinci Systems FoxPro v2.0 *(4) Microsoft FoxBASE+ v2.10 Microsoft Framework IV v1.0 *(5) Borland Freelance Plus v4.0 *(6) Lotus Grandview v2.0 Symantec Harvard Project Manager v3.02 Software Publishing Corp. InfoXL (1987) Valor Software Lotus 1-2-3 v2.4 *(7)(8)(11) Lotus Lotus 1-2-3 v3.1 *(7)(8)(11) Lotus Lotus 1-2-3 for Windows v1.1 Lotus Micrografx Designer v3.1 Micrografx Microsoft C v6.02 *(9) Microsoft Microsoft Excel Windows Ed. v4.0 Microsoft Microsoft Mail v2.1 Microsoft Microsoft Project DOS Ed.v4.0 *(10) Microsoft Microsoft Project Windows v3.0 Microsoft Microsoft PowerPoint v3.0 *(11)(12) Microsoft Microsoft Word for Windows v2.0 Microsoft Microsoft Word v5.5b *(13) Microsoft MultiMate v4.0c Borland Multiplan v3.0 Microsoft NACS/NASI v2.09 (or later) Novell NACS/NASI3 V3.2F (or later) Novell NetWare 3270 LAN Workstation for DOS v2.0 &> Novell LAN Workplace for DOS v4.01 *(14) Novell NETBIOS Emulator v3.02C & > Novell Norton pcanywhere /LAN v4.5 Symantec Norton Utilities v6.01 *(13) Symantec Norton SI v5.0 Symantec ObjectVision v2.0 *(15) Borland Omnis Seven BLYTH Software Oracle *(16) Oracle PageMaker 4.0 Aldus Paradox v3.5 Borland International PC Paintbrush 5+ v1.0 *(17) Z-Soft Picture-Power PictureFile Corp. PerForm Pro v2.0 Delrina Technology Platinum Accounting (G/L) *(18) American Business Microsystems Primetime Personal 1.23 Primetime Software Procomm Plus NCSI/NASI (network v1.0) DataStorm Technologies Procomm Plus v1.0 DataStorm Technologies Project WorkBench v3.1 Applied Business Tech Q & A v4.0 Symantec Quattro Pro v4.0 Borland International Quicken 1.01 Windows Edition Intuit Quicken 5.0 Intuit R:BASE for DOS v4.0 Microrim Sabre Menu Sabre Systems Sidekick v2.0, *(19) Borland Smartware II v1.51 Informix Software Supercalc 5 v5.2 Computer Associates Supercalc 5 + LAN Pack v5.0 Computer Associates SuperProject v2.0 DOS edition Computer Associates SuperBase IV Software Publishing Symphony v2.2 *(9)(20) Lotus Development Timeline v5.0 *(9) Symantec Timeline v1.0 Windows edition Symantec TURBO Debugger 2.0 Borland International Turbo Pascal v6.0 *(21) Borland International Ventura Publisher GEM ed. v3.0 Ventura Software Ventura Publisher Windows ed. v4.0.1 Ventura Software Who-What-When Enterprises Chronos Software WordPerfect v5.1 WordPerfect WordPerfect for Windows v5.1 WordPerfect WordPerfect Office v3.0 *(2) WordPerfect XtreeNet v2.07 *(13) Xtree *(1) Does not support file locking when multiple sessions are editing the same paint file on the LAN. *(2) Do not use with Alert or Notify *(3) Do not use the File Maintenance option when configuring the application. *(4) Foxswap does not work *(5) Set up the program to swap to the network drive and not to the C: drive. With VGA, we recommend using 80 X 25 mode. *(6) You may experience mouse problems if you are using a VGA driver. *(7) Eliminate user access to WYSIWYG files *(8) Do not use a VGA driver. *(9) Maximize TPA memory when using this application. Refer to the Administration Guide for tips on maximizing available session memory. *(10) Use a text editor to change the line in CONFIG.SYS that says stacks=0,0. Increase the value of the first number after the equals sign to a value between 8 and 64. Increase the value of the second number to a value between 32 and 512. If the program still does not work correctly, increase the value further. Reboot the Application Server. *(11) Mouse support may not be available *(12) Users must type in the name of the file to open. Do not click on the selected file. Clicking on the selected file will start the preview option, which terminates the application. *(13) Do not use 43 or 50 line in text mode *(14) Requires an additional adapter. *(15) Make sure that users have access to PARADOX.NET on the file server. *(16) In order to access an Oracle server: a) Set the Convert EGA/VGA to CGA option on the NASGEN General Configuration screen to YES (NOTE: you will then not be able to have Windows sessions). b) Reboot the Application Server. c) Start an Access Services session. d) Run SQLSPX.EXE. e) Run SQLDBA.EXE. *(17) Use in CGA mode only *(18) Map the C: drive to the file server and not to the hard disk *(19) Do not use TSR mode *(20) Communications module was not tested *(21) If you experience problems disable the mouse before you start the program. UNSUPPORTED PC APPLICATIONS The following applications have been tested and are NOT currently certified for operation with NetWare Access Services. Applications that take over control of the Application Server keyboard Applications that require use of the COM or LPT ports on the Application Server Other Serial Remote Access Applications: Carbon Copy Close-Up Close-Up LAN Some LAN based Workstation Control Programs (programs that reside on the LAN and allow remote users to take over a NetWare 3270 LAN Workstation for Windows workstation on the LAN): LAN Assist+ RPRINTER Applications that take over hardware interrupts directly: Flight Simulator IBM 3270 Workstation CP Periscope Probe Turbo Lightning Many TSRs and debuggers LAN based applications that use a transport protocol other than IPX and/or are not designed to run in a multi-use environment: Some TCP/IP Applications (NetWare LAN Workplace for DOS v4.01 is compatible) IBM APPC Applications which require protected mode and - Do not comply with the DPMI/VCPI (DOS Protected Mode Interface/Virtual Control Programming Interface) specifications. - Or fail to relinquish control of the processor. Paradox V4.0 Other Applications AutoCAD 386 r12 CADD Level 3 Enable/OA v4.5 Harvard Graphics v3.0 Microsoft CodeView v2.2 Microsoft Quick Basic Microsoft Windows applications requiring enhanced mode MFT v1.12 (Quarterdeck) Network Courier v2.1a PC Support Ready! MODEMS CERTIFIED FOR USE WITH NETWARE ACCESS SERVICES Modem ROM Set ------- ------------ Acer Modem 2424 V1.2, U18; V1.2, U16 Anchor Signalman Lightning 24 LGHT<164> 10/86; LGHTTAR<70> 8/86 TXO 3/86 Apollo V.32 turbo AVS 3.0 copy 1989, 90; AVS copy 1989, 90 AT&T 2224 CEO AT&T 88 ABTCC; AT&T 87 ABSLJ AT&T 4000 WE882A-3 29084 AT & T 4024 86 AT&T, ABLUV ATI 2400 etc Ver 1.00, 1988 ATI 9600etc/e 1120108113 U18 C Calpak MX2400/MXE-2400 9033SC11006CN Codex 2234 R.1., 56809G01, 4/89; R.1., 56809G02, 4/89 Codex 3220 325226H1 1990 UDS 74200046000 Codex 3260/3265 PC 21000 CompuCom Speedmodem Combo 9101 SC11006CN Digicom 9624 CS 1722 811 U16 ETech Bullet E2400 v2.2, M ETech Bullet PC2400MH v1.00 MH ETech Bullet E9696M ET 880603; E 96M V3.02; ET 890101; ET 890102; ET 890103 Everex Evercom 24E EV947E-15-A Everex Evercom 24E+ EV947E-15-A Fastcomm FDX Series 9696-90329 Forval 14400 SA041891 HI; SA041891 LO Forval 9600 V.32 CS9319 U31402; CS464D U41402; CSF443 U61402; CS5966 V51TU3 Galaxy UFO V.32 Turbo/V.42bis AVS 3.0; AV 3.7 GVC 9600 172 GVC 9600 V.42 bis 172 GVC 14400 V.42 bis 194 ver 2.8 GVC Supermodem 2400 168 Hayes Smartmodem 300 2.2, 04-00082, 1987 Hayes Smartmodem 1200 40-27322, 1982 Hayes Smartmodem 2400 2.2, 04-00082, 1987 Hayes Smartmodem 9600 - V.32 CTL Ver 2.0, 7/31/89, CKSM 67F0AE Hayes Smartmodem OPTIMA 96 1.6, 04-00195, 1987; 1.6, 04-00187, 1987; CTL Ver 2.0, 7/31/89, CKSM 67F0AE Hayes V-Series 2400 1.3, 04-00006,1985.1, 04-00142, 1987 Hayes V-Series 9600 1.5, 04-00015,1987; 1.2, 04-00017, 1987 1.2, 04-00016, 1987; 1.1, ;04-00018, 1987 1.1, 04-00019, 187 Hayes V Series Ultra 96 1.1, 04-00195, 1987; 1.1, 04-00187, 1987 Hayes V Series Ultra 144 04-00455-10 167; 04-00471-300 6 167 04-00472-300 6 008 Intel 2400EX No ROM ID Intel 2400EX MNP Rev 5.3, 100-0111-808, MNP5, High; Rev 5.3, 100-0111-807, MNP5, Low Intel 9600EX 303318-003 Intel 14.4 EX 305216-002 Intel SatisFAXtion No ROM ID Lightning LightCom 96 671-1538 MIDCOM 9135 Maxmodem 2400EI No ROM ID Megahertz 96/24 FAX/Modem 0.4B MICC 4824 2.1, 4824 BIS, 9124 MICC 9600/9610/9620 v1.2B, 9610 Odd, 8C74; V1.2B, 9610 Even, 8C3C Microcom AX/1200-2400 series 1.6 Microcom AX/9612-9624C series Rev. 1.6, 0095001 Microcom QX/4232bis 961-010 Microcom QX/4232hs Rev. 1.2, QX4232HS Migent Pocket Modem 1987 107184F MultiTech 224 v1.14, MT224 AH/EH, 10/16/85 MultiTech 224E v5.04, MT224EH5, 10/3/89 MultiTech 224EH5/EH7 v0.00, MT224E7B, 4/18/90 MultiTech 696 1.14 MultiTech MultiModem II MT1432 0302 MultiTech MultiModem V32 1.04 NEC N9631 v1.04, 27C256; v1.04,27C512 Netcomm SmartModem M4/M5 Okidata Okitel 9600 YR1037-2747G1-1; YR1037-2748G1-1 OmniTel Netcomm Q1200 2122CP 8619 OmniTel Netcomm Q2400 Q2400 110-2 Penril Alliance V.32 1.07 1274, V.32 PUMP, 159A03-01011; 1.07 BA1F, V.32 PUMP, 159A03-01010; 1.07 B0BC, V.32 PUMP, 159A03-01032; 1.07 67BF, V.32 PUMP, 159A03-01031; v1.23 173F, U21; v1.23 85A2, U33 Penril Datalink 2400 Rev. 12, 125A02-01, 1984 Penril Datacomm Practical Peripherals 1200 A10009100 Rev. B Practical Peripherals 2400SA 04-00027-16 1.072 LR Practical Peripherals 2400SA V.42bis 242 ver 1.12C Practical Peripherals 9600SA Rev. 1.26, PPI 1991 Practical Peripherals 14400FXSA 1.12C Racal Milgo RMD 3222, Model P-2533-51 3.09 G6FA, 14.4 Pump RM, 167A02-01U5; 3.09 9875, 14.4 Pump RM, 167A02-01U10 3.09 C60B, 14.4 Pump RM, 167A02-01U32 6:2.22FEDB,14.4 Main RM, 167A01-02U54 2.22 2BD4, 14.4 Main RM, 167A01-02U46 5:3.09 9BFF,14.4 Pump RM,167A02-01U42 Racal Vadic 9632VP 16045-0691312C Rockwell RG2400 PC Modem No ROM ID Sharp 9624E V01.06 M1B1 Telebit QBlazer No ROM ID Telebit T1000 FA 2.01 Odd, Locate U35, 8FB1 900301; FA 2.01 Even, Locate U34, 8647 900301 Telebit T1600 LA 1.00 Odd, Locate U5, 6184 901201; LA 1.00 Even, Locate U12, 33FB 901201 Telebit T2500 WR260332-20; WR270331.20 12007-01; 12006-01 GF 7.00 ODD 9039; GF 7.00 EVEN 9039 Telebit T3000 4.00 Telebit Trailblazer+, Model T185A BA4.00 Odd, S/U39 RM/UB, F51E 880106; BA4.00 Even, S/U38 RM/UI, B3E0 880106 Touchbase Worldport 1200 No ROM ID Touchbase Worldport 2400 No ROM ID Touchbase Worldport 9600 No ROM ID UDS FasTalk V.32/42b 357401A 37 UDS V.32 25 327409G1 1990 US Robotics Courier 2400 SP244/CR, 2/10/87 US Robotics Courier 2400E SV CR24E, 4283, 110189, 27C25614 US Robotics Courier HST 1989 1016276 I/O A14.4 EC68 121988 87C451 US Robotics HST Dual Standard 1989 1016276, DP-C14.4 BC2C 091889, 57C257 US Robotics Sportster 2400 PC MNP 11018927c256 US Robotics Sportster 2400 v42bis 11.12.91 US Robotics Sportster 9600 v42bis F590C693 US Robotics Courier V.32/V.32bis (28 pin package) 1990 1016390, DP-Ever 3B81, 111590, 27C4512; 8 pin package) 1990 1016389, DS-Ever AA18, 111590 27C512 28 pin package) 1990 1016394, V.32, 120190 27C512 (socketed CPU) 16-375, 101190, 87C451, 2392 Ven-Tel 9600 Plus/Plus II 4.11 USA, V-14D SAP 2; 4.11 USA, V-12E SAP 2 Viva 9642e V.42bis 1.100 Western Datacom 432 LineBkr V.32 No ROM ID Zoom 2400 3.02C Zoom 2400 V.42bis V42 V32 EBC8 Zoom 9600 V.32 Turbo 010 v1.20Z Zoom FaxModem FX 9624V No ROM ID Zoom FaxModem VFX V.32/V.42bis 1.20