TITLE: Access Server V1.2 Rules of Thumb DOCUMENT #: TD.S.R2 DATE: April 25, 1991 PRODUCT: Access Server PRODUCT VERSION: 1.2 SUPERSEDES: NA but there are also Rules of Thumb for V1 NetWare Access Server is a powerful, practical, and cost effective way for multiple remote users to access NetWare LANs. To aid you in configuring Access Server for optimal reliability, performance, and ease of use, we asked our engineers what components they would use if they were installing the product, and to provide technical tips for users setting up an Access Server system. This document lists what they said. NetWare Access Server software is designed to run on a dedicated computer using an 80386 or 80486 microprocessor. Once the memory and communications interfaces are in place, an Access Server can simultaneously support up to 16 remote DOS sessions running in real mode (not protected mode). The Access Server must be equipped with a high-capacity (1.2MB 5.25 inch or 1.44MB 3.5 inch) disk drive and an optional hard disk. We recommend that you choose one of computers listed below. PERSONAL COMPUTER BIOS DATE Novell 386A AMI 1/13/88 Novell 386A DATATECH 2/15/89 AST Premium 386/33 Cupid-32 rev. 1.0 AT&T 6386/SX WGS Phoenix 2.0 AT&T 6386/25 WGS AST 386/20 Compaq 386/s Compaq 386/16 Compaq 386/20e Compaq 386/25e Compaq 386/33 Compaq 486/33 Compaq DeskPro 386/16 ROM BIOS F, Video BIOS C Compaq DeskPro 386/33* Compaq SystemPro Everex 386 Step 25 AMI,Ref.0000,Rev G1-32 7/16/90-K9 Hewlett-Packard Vectra 486/33 IBM PS/2 Model 70 IBM 8580 (PS/2 Model 80) IBM 3/30/87 NEC Powermate 386/25 Phoenix 1.10.68 Standard Brand 386 Modular vC3.03 Award Software, Inc. ZenithDataSystems 486/25-E3** Zenith ver. 1.05 * Must use 8-bit video mode ** Select non-slushed memory. NOTE: With all of the above computers you must disable RAM shadowing, BIOS shadowing, disk slow down, and memory caching. MEMORY Access Server requires 1 MB of RAM plus an additional amount of memory for each concurrent DOS session you expect to support. The recommended minimum configuration is 2.6 MB of memory (enough to support a single user session and an operator session without expanded memory). To determine the amount of memory your specific Access Server configuration requires, use the following formula: 1000 + (N x 800) + (S x E) - N is the number of virtual DOS sessions to be supported - S is the number of sessions needing expanded memory - E is 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.) Access Server can use up to 16 MB of memory (this must be extended memory). In addition, adequate address space must be available in the high memory range, from 640 KB to 1024 KB, to support all necessary adapters (a LAN adapter, a video adapter, and usually a remote communications adapter). Consult your LAN adapter, video adapter, and remote communications adapter documentation for memory requirements. See Appendix C of the "NetWare Access Administration Guide" for information on avoiding conflicts in the high memory range. LAN ADAPTERS Access Server connects to the local network through a LAN adapter. For optimal memory use and best performance, we recommend a 16bit or 32bit nonmemory mapped certified LAN adapter. CERTIFIED LAN ADAPTERS DESCRIPTION Novell NE1000 Ethernet Novell NE2000* Ethernet Novell NE/32* Microchannel Ethernet Novell RX-Net Arcnet (8-bit) 3COM 3C503** Ethernet 3COM 3C505** Ethernet IBM 16/4 Token Ring IBM PC Adapter/A Microchannel Token Ring SMC Arcnet Thomas Conrad Arcnet (8-bit and 16-bit) Western Digital EtherCard Plus 16 Ethernet Western Digital EtherCard Elite 16 Ethernet * These are 16 or 32 bit adapter cards recommended for optimal Access Server performance ** Must disable the on board memory TOKEN RING DRIVER AND PREVIOUS NETWARE VERSIONS If your version of NetWare is 2.2 or 3.11, no special measures are required to install the Access Server on a token ring LAN. Simply prepare your installation disk and run the Access installation program as described in Chapters 6 and 7 of the NetWare Access Administration Guide. However, if you are running any other version of NetWare, replace your original STOKEN.OBJ and IPX.OBJ files with special versions of these files (from the NetWare Access Utility diskette) as follows: 1. If you have not already done so, make copies of your NetWare SHGEN disk(s) and label the copies NetWare Access SHGEN-1 and, if applicable, NetWare Access SHGEN-2. 2. Make a copy of your NetWare LAN_DRV_001 diskette and label the copy NetWare Access LAN_DRV_001. 3. Delete the STOKEN.OBJ file currently on your NetWare Access LAN_DRV_001 disk. 4. Copy the TRN.OBJ file from your NetWare Access Utility diskette to your NetWare Access LAN_DRV_001 disk. 5. Rename TRN.OBJ on the NetWare Access LAN_DRV_001 diskette to STOKEN.OBJ. 6. If you have not already done so, locate the original IPX.OBJ file currently on your NetWare Access SHGEN-1 or NetWare Access SHGEN-2 disk. 7. If you have not already done so, replace the original IPX.OBJ file with the special IPX.OBJ file from your NetWare Access Utility disk (see Chapter 6 of the NetWare Access Administration Guide). 8. Run the SHGEN program on the NetWare Access SHGEN diskette to generate an Access Server-compatible IPX.COM file. 9. When running SHGEN, use the NetWare Access LAN_DRV_001 diskette in place of the original LAN_DRV_001 diskette. When the "Available LAN Drivers" menu appears, select IBM Token Ring v2.50. 10. Complete the SHGEN program and continue your software installation preparation (see Chapters 6 and 7 of the "NetWare Access Administration Guide"). 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 from default CA00h to CE00h when you run NASGEN (see Chapter 7 of the NetWare Access Administration Guide). 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. TOKEN RING SOURCE ROUTING To support token ring source routing for your Access Server sessions, edit your NASAUTO.BAT file (in the ACCESS directory) to load ROUTER.COM after loading IPX.COM. VIDEO ADAPTERS Access Server requires a video adapter. MDA, CGA, EGA, VGA, HGC, and HIC video standards are supported. The video adapter determines the range of graphics applications that run on the Access Server. We recommend installing a CGA card for optimal performance since the CGA standard is widely supported and uses minimal session memory for operation. The following table lists the available memory per session we obtained when we installed various types of video adapters in combination with an NE2000 (nonmemory-mapped) LAN adapter and WNIM+ remote communications adapter in a standard 80386 computer with 16 MB of memory. ACCESS SERVER ADAPTERS RAM AVAILABLE FOR EACH REMOTE SESSION CGA Approximately 600 KB MDA Approximately 567 KB HGC Approximately 533 KB EGA, VGA Approximately 470 KB * * You can configure the Access Server to convert EGA and VGA to CGA compatibility. In the above configuration, this conversion option increased available memory by 76 KB, to 546 KB per session. This increase varies with the specific adapter you install. SUPPORTING GRAPHICS Video adapters with graphics capabilities must be present in both the Access Server and each remote workstation using graphics applications. Graphics applications should be configured for the graphics mode installed in the Access Server. If the Access Server and the workstation have different types of video adapters, configured for different graphics modes, NetWare Access will carry out video mode translation and the workstation will display the application using the lower grade graphics mode. The MAXIMUM display quality supported for workstations through NetWare Access is 640 x 480 resolution in 8-bit video mode. GRAPHICS ON THE MACINTOSH A Macintosh workstation running OnLAN/Mac supports MDA, CGA, EGA, and VGA graphics. VGA and MONOCHROME Monitors If a VGA adapter is installed in an Access 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. MDA Video Mode Workstations with non-graphic MDA type video adapters installed cannot display applications that require CGA, MCGA, EGA, VGA, HGC, or HIC graphics capabilities. REMOTE COMMUNICATIONS ADAPTERS If a workstation does not connect to the Access Server through a LAN, it connects through a port on a remote communications adapter installed in the Access Server. Remote communications adapters support connections via direct cable, modem, multiplexer, NACS, and X.25 public data networks. We recommend using a certified adapter. CERTIFIED REMOTE COMMUNICATIONS ADAPTERS INTERFACE Novell WNIM+ 4 port 8-bit Adapter RS-232 IBM ARTIC Realtime Interface Coprocessor Adapters: Multiport Adapter (16 bit) RS-232 Multiport/2 Adapter (Microchannel) RS-232 Newport Systems Solutions Adapters: ACI, Asynch Comm. Interface, 8 ports RS-232 XCI X.25 Comm. Interface, 2 ports RS-232,RS-422 Specialix SI Family Adapters*: V.35,X21 SI/4, SI/8, SI/8-422, and SI/16 16-bit RS-232, RS-422 SI/PS4, SI/PS8, SI/PS8-422, and SI/PS16 Microchannel RS-232, RS-422 SI/E4, SI/E8, SI/E8-422, & SI/E16 32-bit RS-232, RS-422 * RS-422 Adapters require a special interface at the workstation NETWARE VERSION Access Server v1.20 works with NetWare v2.10 through v2.2 and NetWare v3.10 through v3.11 (NetWare 3.0 users can upgrade to 3.10 or 3.11. NetWare 3.10 users must install a patch which is available with instructions in file SCBFIX.ZIP in NetWire NOVA LIBRARY 7). When workstations use an AppleTalk LAN to connect to a Access Server, a NetWare v3.11 file server is required and it must be running NetWare for Macintosh as described in the NetWare Access Administration Guide. Access Server does not support Named Pipes. DOS Version NetWare Access is designed to operate on an 80386 or 80486 PC running IBM PC-DOS 3.x or 4.x. ACCESS SERVER CONNECTIONS Remote users can be connected to an Access Server version 1.2 via: -Modem -MUX -Null Modem Cable -X.25 PDN Connection -NetWare LAN Cabling MODEM CONNECTIONS Each user must have a modem that is compatible with the modem at the Access Server host. For example, the modems at each end of a connection must use the same speed and data communications processes. Access Server supports asynchronous transmission speeds up to 38.4 Kbps using dial-up modems (such as the Hayes Smartmodem) with features such as error correction, data compression, and V.32 compatibility. We recommend using error correcting modems. The following is a complete list of modems certified for use with Access Server. MODEM ROM SET Acer Modem 2424 1: V1.2, U18 2: V1.2, U16 Anchor Signalman Lightning 24 ATI 2400 ETC. (internal) Ver 1.00, 1988 AT&T 2224 CEO Type Ser. 7 1: ABTCC, 88 2: ABSLJ, 87 AT&T 4024 86 AT&T, ABLUV Bullet 2400M V. 2.2, M Bullet 2400MH (internal) V1.00 MH Bullet E9696M 1: ET 880603 2: E 96M V3.02 3: ET 890101 4: ET 890102 5: ET 890103 Calpak MX2400 (internal) Calpak MXE-2400 Codex 2234 1: R.1., 56809G01, 4/89 2: R.1., 56809G02, 4/89 Codex V.32 (internal) 1: 325226H1, 1990 UDS 2: 742000460000, Date Code 8845, Motorola Concord Data Systems Dial Access 296 1: Rev 1.003 1989, 1032459.004 2: Rev 1.003 1989, 1032459.003 3: 3.00 CCGD, U74 GEN II DSI 9624LE 1: CS 1722, 811 U16 2: CS BE95, U7 B01 3: CS 0552, U5 B01 4: CS 4AD5, U3 B01 Everex Evercom 24E+ EV947E - 15 - A Fastcomm 9600 Galaxy Networks Apollo V.32 Turbo 1: AVS 3.0 2: AV 3.7 GVC 9600 V.42 BIS 172 GVC Supermodem 2400 (internal) 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 V-Series Smartmodem 2400 V.42 1: 1.3, 04-00006, 1985 2: 1.1, 04-00142, 1987 Hayes V-Series Smartmodem 9600 1: 1.5, 04-00015, 1987 2: 1.2, 04-00017, 1987 3: 1.2, 04-00016, 1987 Hayes V-Series Smartmodem 9600 V.42 1: 1.1, 04-00141, 1987 2: 1.2, 04-00017, 1987 3: 1.2, 04-00016, 1987 Hayes V-Series Ultra Smartmodem 9600 1: 1.1, 04-00195, 1987 2: 1.1, 04-00187, 1987 Intel 2400EX Intel 2400EX MNP5 1: Rev5.3,100-0111-808,MNP5, High 2: Rev 5.3, 100-0111-807, MNP5, Low Intel 9600EX 303318-003 Micc 4824 2400 V.42 MNP5 2.1, 4824 BIS, 9124 Micc 9610 V.32/42 1: V1.2B, 9610 Odd, 8C74 2: V1.2B, 9610 Even, 8C3C Microcom QX/4232HS, MND Class 10 Rev. 1.2, QX4232HS Microcom AX9624C MNP Class 6 Rev. 1.6, 0095001 Migent Pocket Modem Multitech Multimodem 224 VS 1.14, MT224 AH/EH, 10/16/85 Multitech MT224EH7 vs. 0.00, 4/18/90, MT224EH7B Multitech MT932EAB vs. 3.00B2, 8/16/90 Multitech MT932ERB vs. 4.00, 10/23/90 Multitech MT932EA/25 vs. 2.05, 11/27/89 NEC N9631 1: v1.04, 27C256 2: v1.04, 27C512 Okidata Okitel 9600 1: YR1037-2747G1-1 2: YR1037-2748G1-1 Penril Alliance V.32 1: 1.07 1274,V.32 PUMP,159A03-01011 2: 1.07 BA1F,V.32 PUMP,159A03-01010 3: 1.07 B0BC,V.32 PUMP,159A03-01032 4: 1.07 67BF,V.32 PUMP,159A03-01031 5: V1.23 173F, U21 6: V1.23 85A2, U33 Penril Alliance V.32/14.4 1: 3.07 9A46, V.32 410 2: 3.07 6CE3, V.32 U5 3: 2.19 B7C4, V.32 454 4: 2.19 7DB1, V.32 446 5: 3.07 1AA7, V.32 432 6: 3.07 DEC7, V.32 442 Penril Datalink 2400 Rev.12,125A02-01,1984 Penril Datacomm Practical Peripherals 2400 (internal) Rev. 1.04, PPI 1988, 2400HG Practical Peripherals 9600SA Rev. 1.26, PPI 1991 Racal Milgo RMD 3222, Model P-2533-51 1:3.09 G6FA,14.4 PumpRM,167A02-01U5 2:3.09 9875,14.4 PumpRM, 167A02-01U10 3:3.09 C60B,14.4 PumpRM, 167A02-01U32 4:2.22 2BD4, 14.4 Main RM, 167A01-02U46 5:3.09 9BFF, 14.4 Pump RM, 167A02-01U42 6:2.22 FEDB, 14.4 Main RM, 167A01-02U54 Rockwell RG2400 SatisFAXtion Sharp 9624E V01.06 M1B1 Telebit T2500, Model T25A Telebit T1000 1:FA2.01 Odd,Locate U35, 8FB1 900301 2: FA 2.01 Even, Locate U34, 8647 900301 Telebit T1600, Model T165SA 1: LA 1.00 Odd, Locate U5, 6184 901201 2: LA 1.00 Even, Locate U12, 33FB 901201 Telebit Trailblazer Plus, Model T185A 1: BA4.00 Odd,S/U39 RM/UB,F51E 880106 2: BA4.00 Even, S/U38 RM/UI, B3E0 880106 Touchbase 2400 Universal Data Systems, Motorola V.3225 1: 327409G1, 1990 UDS 2: 327439F1, 1990 UDS US Robotics Courier 2400 SP244/CR, 2/10/87 US Robotics Courier 2400E SV CR24E, 4283, 110189, 27C256 US Robotics Courier HST Dual Standard 1: (socketed CPU) 1989 1016276,I/O-A14.4 EC68, 121988 87C451 2: (40 pin package) 1989, DP-C14.4 BC2C, 091889 57C257 3: (28 pin package) 1989 1016307, SV-DS 3EFC, 092989 27C512 US Robotics Courier HST Dual Standard 1990 1016390, DP-Ever 3B81, 111590, 27C4512 1990 1016389, DS-Ever AA18, 111590 27C512 1990 1016395, DS-Triad 1CA6, 113090 27C51216-375, 101190, 87C451, 2392 US Robotics Courier V.32 BIS 1: (28 pin package) 1990 1016390, DP-Ever 3B81, 111590, 27C4512 2: (28 pin package) 1990 1016389, DS-Ever AA18, 111590 27C512 3: (28 pin package) 1990 1016394, V.32, 120190 27C512 4: (socketed CPU) 16-375, 101190, 87C451, 2392 Ven-Tel 9600 Plus II 1: 4.11 USA, V-14D SAP 2 2: 4.11 USA, V-12E SAP 2 Zoom V.42 BIS V42 V32, EBC8 MUX CONNECTIONS Access Server supports multiplexers that provide RTS/CTS hardware flow control. Access Server does not support multiplexers that use XOn/XOff flow control (unless it can be turned off) or insert special characters in the data stream. Access Server operates with the Develcon Multiplexer using an X.25 PAD. DIRECT CONNECTIONS Workstations and ASCII terminals can be connected directly to the Access Server through a properly wired RS-232 null modem cable (there are several types of null modem cables available). The "NetWare Access Administration Guide" shows the proper wiring for a direct connection cable. 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 to complete the connection types. NETWARE ACCESS SERVER CONNECTIONS Workstations IBM PC# MACINTOSH TERMINAL OTHER PC MODEM P* M* N T MUX P* M* N T DIRECT P* M* N T NetWare LAN P AppleTalk LAN M NACS P+ T X.25 P* T N T P=ONLAn/PC1.20 M=ONLAN/MAC 1.20 N=None, no software required T=Terminal emulator program * May also use a terminal emulator program, but the listed software is preferred. + Must run NASI v2.09 also. # IBM PC or a compatible computer. 1 Any computer that can emulate a terminal. IBM PC Using OnLAN/PC An IBM PC, XT, AT, PS/2 or compatible computer can use OnLAN/PC v1.20 to complete many types of Access Server connections. OnLAN/PC is provided with NetWare Access and can be copied as many times as necessary for use with the Access Server. The PC must have a disk drive that uses floppy disks holding 720 KB or more; and it must have at least 350 KB of available RAM. Remote PCs must also have a serial communications port. While running OnLAN/PC, workstation users do not have direct access to the workstation's disk drives. Users can transfer files between the LAN and their disk drives, and they can exit to DOS. Users of OnLAN/PC v1.0x can use the ONFILE file transfer utility to download the v1.20 software. To avoid overwriting the active OnLAN/PC program, users should download the new files to a directory that does not contain the v1.0x OnLAN/PC files. MACINTOSH COMPUTER USING ONLAN/MAC An Apple Macintosh computer can use OnLAN/Mac software to complete many types of Access Server connections. The Macintosh must have at least 512 KB of RAM and run System 6.0 or higher. While running OnLAN/Mac, workstation users do not have direct access to the workstation disk drives. Users can transfer files between the LAN and their disk drives, and they can use MultiFinder to switch to the Finder or other applications. Users of OnLAN/Mac v1.0x can use the ONFILEM file transfer utility to download the v1.20 software. To avoid overwriting the active OnLAN/Mac program, users should download the new files to a folder that does not contain the v1.0x OnLAN/Mac files. ASCII Terminal Access Server is preconfigured to connect to 30 different types of ASCII terminals. Supported terminals include the VT-100 and the IBM 3101. Some terminal keys (such as the cursor and function keys) may not operate after installation. The operation of these keys can be changed using the the procedures in Chapter 12 of the "NetWare Access Administration Guide". TERMINALS Ampex 230 ADDS Regent ADDS Viewpoint ANSI Standard* Beehive ATL-004, ATL-078, DMSB, DMSC, DMSD Dasher D410, D460 DEC VT-52 Digital Microsystems DMS-3/F, DMS/-15, DMS-501, DMS-5080, DMS-5086 Esprit III Falco FAME III Hazeltine 1500 Hewlett-Packard HP 262X, HP 264X, HP 2382A, HP 150 IBM 3101 Kaypro 2'84, 4'84, 10, Robie Kimtron KT-7 PC Link PCTERM LSI ADM 3A OnLAN/PC or /Mac 1.2x, 1.0x Prime PST100 Qume QVT-102, QVT-108 Soroc Challenger Series Tektronix 4105, 4107, 4109 Teleray Model 7, Model 16 TeleVideo 910, 910+, 914, 924,925, 950 Visual Technology V330 (in DG D200 mode) VT-100/200? Wyse Technology WY-50, WY-100, WY-300 Zenith Z-19-HW Zenith Z-29 * The VT-100 is X3.64-compatible; the ANSI selection is set to assume non-X3.64 compatibility. If you experience attribute problems with your terminal, try switching between the ANSI and the VT-100 selection. TERMINAL EMULATION ON A PERSONAL COMPUTER Any computer should be able to use terminal emulation software to connect to the Access Server. To transfer files between NetWare and the personal computer, use a terminal emulator (such as Procomm+) that allows file transfers, and set the protocol to XModem. WORKSTATION SESSIONS This section describes session features that operate independently of the workstation hardware. MOUSE SUPPORT Access Server does not support mice or other pointing or digitizing devices. OnLAN/Mac users, however, can perform limited cursor movement functions with the mouse (all Macintosh functions, such as pull-down menus, continue to operate). EXECUTION SPEED Access Server is designed for optimal performance. Only keyboard input and screen output travel over the remote communication lines, allowing all processing to take place on the Access Server host itself. Access Server performance differs based on the following variables: Access Server host processor speed, line speed, network traffic, and graphics applications. A benchmark test was performed on a COMPAQ 386/33 with a 16-bit Ethernet adapter running the Access Server software. One to 16 remote users connected to this Access Server and ran typical business software applications in text mode. The time required to complete the test was recorded and compared to a single standalone 8MH IBM AT and a 4.77MH IBM PC. When 1 or 2 users were connected processing speeds were MUCH better than for the stand alone AT however, as more users were added performance slowed proportinately until there a total of 10 users connected to the Access Server and processing speeds became equivalent the AT. In all cases, each session on the Access Server processed at speeds more than twice as fast as an IBM PC. Since Access Server display data travels over the connection lines, some applications 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. For modem connections, transmission speed can be improved by using high-speed modems (9600 bps and above). WORKSTATION PRINT OPTIONS Workstations can connect to an Access Server and print to their remote printer (attached to the workstation) or to printers on either LAN. To select a printer while using the Access Server, workstation users must use the NetWare CAPTURE and ENDCAP commands in the correct sequence. The following paragraphs summarize the steps a Access Server user can take to select a printer. NOTE: Printing can not be done on a printer attached to the Access Server itself. To select a remote printer from a remote workstation (Workstation 2 in the example), connect to the Access Server and enter the ENDCAP command. To select a remote printer from a LAN workstation (Workstation 1 in the example), enter the ENDCAP command, start the OnLAN program (OnLAN/PC or OnLAN/Mac), and connect to the Access Server; then enter the ENDCAP command again. To select a LAN printer from a workstation on the same LAN (Workstation 1 to Fileserver 1), enter the CAPTURE command (with the appropriate options), connect to the Access Server, and then enter the ENDCAP command. To select a printer on the Access Server LAN from a remote workstation (Workstation 2 to Fileserver 2), connect to the Access Server and then enter the CAPTURE command (with the appropriate options). To select a LAN printer from a workstation on a different LAN (Workstation 1 to Fileserver 2 or Workstation 2 to Fileserver 1), connect to the Access Server and then enter the CAPTURE command (with the appropriate options). DISK DRIVE MAPPING When a workstation logs into a Access Server and then logs into a NetWare file server, the workstation drive mapping is determined by the Access Server configuration (not the workstation disk drive configuration). If the Access Server 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 Access Server disk drives, the letter for the first network drive is determined by the physical drives installed. If the Access Server has three drives or less, the first network drive letter is F. When four disk drives are installed, the first network drive letter is G. ACCESSING IBM SNA MAINFRAMES Remote users can access IBM mainframe information through a NetWare SNA Gateway installed on the Access Server LAN or internetwork. With NetWare 3270 LAN Workstation software v1.3 installed on the LAN, up to 16 Access Server users can access SNA gateways simultaneously. Access Server 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 Access Server administrator can prohibit user access to the Special Keyboard Handler in NASGEN.) We recommend that you maintain only one 3270 display session per user, for optimal performance. Using the NetWare NETBIOS Emulator The Access Server is compatible with the NetWare NETBIOS emulator v3.02, which is available on NetWire. The NETBIOS emulator must be loaded from NASAUTO.BAT. SEE: Access Server V1.2 Rules of Thumb (Part 2) for supported and unsupported software. SUPPORTED APPLICATIONS Access Server is designed to provide high-performance access to virtually all LAN applications for remote users. Applications should be run in real mode, not protected mode. PRODUCT PUBLISHER Agenda v2.0 Lotus Development Corp. Applause II v1.0 *1 Ashton-Tate ASCOM IV/Network v1.42 DMA AskSam v4.2b AskSam Systems, Inc. AutoCAD 386 Rel 11 *1 Autodesk, Inc. Btrieve v5.10A Novell cc:Mail v3.15 cc:Mail, Inc. CED The Cove Software Group Clipper v5.0 Nantucket Corp. The Coordinator v1.20 *2 Action Technologies Crosstalk Mark IV Digital Communications Associates Current v1.1 *3 IBM Corp. Dataflex v2.3b DataAccess Corp. dBASE IV v1.1 Ashton-Tate DisplayWrite 5 v2.1 IBM Corp. eMail v1.70d Da Vinci Systems Corp. Enable OA v3.0 The Software Group FoxBASE+ v2.10 Fox Software Framework III LAN v1.0 *4 Ashton-Tate Freelance Plus v3.10(1) *1 *5 Lotus Development Corp. Grandview v2.0 Symantec Corp. Harvard Graphics v2.31 Software Publishing Corp. Harvard Project Manager v3.02*6*7 Software Publishing Corp. InfoXL (1987) Valor Software, Inc. Lotus 1-2-3 v2.01, v2.2 Lotus Development Corp. Lotus 1-2-3 v3.11, *8 Lotus Development Corp. Microsoft C 6.02 *7 Microsoft Corp. Microsoft Excel v2.1d *3 Microsoft Corp. Microsoft Project v4.0 Microsoft Corp. Microsoft Project for Windows v1.0 *3 Microsoft Corp. Microsoft Windows v3.02,*1*9 Microsoft Corp. Microsoft Word 3.10 Microsoft Corp. Microsoft Word 5.5 *10 Microsoft Corp. MultiMate 4.0 Ashton-Tate Multiplan v3.0 Microsoft NASI v2.09 Novell NetWare 3270 Workstation v1.3 Novell NetWare LAN Workplace forDOSv4.0 *11 Novell NetWare NETBIOS Emulator v3.02 *12 Novell Norton Utilities Adv. Ed. v5.0 Symantec Corp. PageMaker 3.01 *1 *3 Aldus Corp. Paradox v3.5 Borland Intl. pcANYWHERE IV/LAN v4.03c DMA PC Paintbrush IV Plus v1.0 *1 *13 Z-Soft Corp. PrimeTime Personal 1.23 Primetime Software, Inc. Procomm+ 1.1 DataStorm Technologies Project Workbench 3.01 Applied Business Tech. Corp. Q & A v3.0 Symantec Corp. Quattro Professional v2.0 Borland Intl. R:BASE for DOS v3.1 Microrim, Inc. SABRE v 2.0 Sabre Systems Smartware II v1.02 Informix Software, Inc. Supercalc 5 + LAN Pack v5.0 *14 Computer Associates, Inc. SuperProject Expert v1.1 Computer Associates, Inc. Symphony v2.28, *7 *15 Lotus Development Corp. Timeline v4.08 Symantec Corp. TURBO Debugger 2.0 Borland Intl. Turbo Pascal v5.5 Borland Intl. Ventura Publisher GEM Ed.v3.02, *1 *16 Ventura Software, Inc. WordPerfect 5.0 *17 WordPerfect Corp. WordPerfect 5.1 *17 WordPerfect Corp. WordPerfect Office v3.0 *17 *18 WordPerfect Corp. XtreeNet v2.011 Xtree Company NOTE: Check NetWire for the latest application notes. *1 Difficult to use without a mouse. *2 Do not use with Alert utility. *3 Tested using retail version of Microsoft Windows 3.011. Does not run under bundled version. *4 Framework III uses the key to switch between "cabinets" and "documents." This key is disabled in an OnLAN session. Alternate methods to the key require four additional key strokes. *5 The OnLAN/PC Remote Session Manager cannot be "popped up" while Freelance is active. *6 Larger files may produce out of memory errors. *7 Maximize TPA memory when using this application. Refer to the Access Server Administration Guide for tips on maximizing available session memory. *8 When starting the program, use the -C option on the command line. *9 Windows 3.0 and some programs that run under Windows must be loaded in real mode (not protected mode). This reduces Windows capability *10 Do not use in 43- or 50-line mode. *11 Requires an additional network adapter. *12 Support available for all sessions. *13 Avoid using 256-color VGA drivers; best results produced with 640x480 16-color drivers. *14 To keep row and column numbers from blinking in an OnLAN session, set the Blink Attribute to Off. *15 Communications module not tested. *16 Allocate plenty of EMS memory. *17 Indicates products with special file and/or record-sharing capability when using NetWare v2.1x. *18 Do not use with Notify utility. UNSUPPORTED PC APPLICATIONS Although Access Server supports most commercially available software, it does not support: > Applications that duplicate the multitasking technologies contained in Access Server. > Some applications that take over hardware interrupts (for example, some Terminate-and-Stay-Resident (TSR) programs or debuggers). > Applications that take over control of the Access Server keyboard. > Applications that require use of the COM1, COM2, and LPT ports on the Access Server. CThe following applications have been tested and are NOT currently certified for operation with Access Server. CATEGORY/APPLICATION DESCRIPTION EXAMPLE APPLICATIONS Other Serial Remote Access Applications Carbon Copy Close-Up Some LAN-based Workstation Control Close-Up LAN Programs (programs that reside on the LAN LAN Assist+ and allow remote users to take over a workstation on the LAN) Applications that take over hardware Flight Simulator interrupts directly IBM 3270 Workstation CP NetWare 5250 Periscope Probe Turbo Lightning LAN-based applications that use a transport Some TCP-IP Applications protocol other than IPX and/or are not designed (NetWare LAN Workplace to run in a multiuser environment for DOS is compatible) IBM APPC Other Applications Advanced Revelation v2.0 CADD Level 3 Microsoft Codeview v2.2 Microsoft Quick Basic MFT v1.01 (Quarterdeck) Network Courier v2.1a Norton SI v4.50 Picture-Power 3.1 rel 2 Ready! SideKick v2.0 Who-What-When v2.0