However, every network requires a hardware adapter through which you communicate with the server and other users. For the purposes of this discussion there are two types of network adapters: 1. The hardware adapter is accessed through a software controlled I/O port and does not use any physical addresses in the system. 2. The hardware adapter is accessed through a RAM buffer, or includes some option ROM, or both, which occupies some physical addresses between 640K and 1024K. In the first case, the ALLEMM4 driver statement in your CONFIG.SYS file need only include the RAM option as follows: DEVICE=ALLEMM4.SYS RAM If your network adapter is of the second type, then you must use the X option (in addition to the RAM option) to exclude the range of addresses that the adapter occupies. DEVICE=ALLEMM4.SYS RAM X=sp00-spFF * sp00 and spFF specify the start and end addresses of the range(s) to be excluded for the network adapter; the "s" represents the Segment and "p" is the Page of the address in hexadecimal. In some cases, the network adapter RAM and/or ROM locations can be relocated to different addresses. The Harware section (in ALLMENU) provides somes details on how to relocate various network adapters. Once you have installed the ALLEMM4 driver with the RAM option you will be able to see the high memory areas in your system. Run EXAMEM under the ALLEMM4 selection in ALLMENU. The "T"s represent the high memory in your system; each "T" equals 4K of memory. The more "T"s there are the more high memory you have. If you have used the EXCLUDE option with ALLEMM4, then the excluded ranges will be marked "X". The excluded ranges may fragment your high memory. Your objective is to have as many contiguous "T"s as possible, so you may need to go back and relocate the RAM/ROM addresses of the network adapter. If the your network adapterd has any ROM, RAM or both which occupies addresses in reserved memory space (between 640K and 1024K) then: If possible try to set your network RAM/ROM at the beginning or end of a block of "T"s (minimizing the fragmentation) or set the RAM/ROM addresses to the smallest block of "T"s (in cases where there is more than one high memory block). INSTALLING YOUR NETWORK ----------------------- Now that you have found the best possible position to place your network adapter RAM/ROM, and enabled high memory (RAM with ALLEMM4 in CONFIG.SYS) you should rerun EXAMEM to have a look at the free memory above 640K. You can now use the DEVICE and ALLOAD programs to load the various network files (plus other TSRs) above 640K into the free high memory. *** Before you install these commands in your AUTOEXEC.BAT file, run them from the command line, test your network, and view your configuration under EXAMEM to make sure every is working properly. Note: You can gain an additional 64K of high memory by eliminating the EMS Pageframe. If the applications you plan to run do not require expanded memory you can add the FRAME=NONE option to ALLEMM4.SYS in your CONFIG.SYS file. DEVICE=ALLEMM4.SYS RAM FR=NONE <+ X'ed areas) At this point your system should be operational. If you have VGA Mono change the above setting to read: CHOICE " "C0000-C3FFF" " POS[2] = 1100000Xb MEM 0B0000h-0B3FFFh Below is an example of what you will see in the .ADF file for RAM settings: @E000.ADF: CHOICE " "DC000-DFFFF" " POS[0] = 1101110Xb MEM 0DC000h-0DFFFFh If you have VGA color change the above setting to read: CHOICE " "B4000-B7FFF" " POS[0] = 1011010Xb MEM 0B4000h-0B7FFFh If you have VGA Mono change the above setting to read: CHOICE " "C4000-C7FFF" " POS[2] = 1100010Xb MEM 0C4000h-0C7FFFh @E001.ADF: CHOICE " "16KB/DC000-DFFFF" " POS[0] = 1101110Xb POS[1] = XXXX01XXb MEM 0DC000h-0DFFFFh In a system with VGA color change the above setting to read: CHOICE " "16KB/B4000-B7FFF" " POS[0] = 1011010Xb POS[1] = XXXX01XXb MEM 0B4000h-0B7FFFh If the system has VGA Mono then the lines should read: CHOICE " "16KB/C4000-C7FFF" " POS[0] = 1100010Xb POS[1] = XXXX01XXb MEM 0C4000h-0C7FFFh Once you have saved the appropriate changes to the .ADF file which applies to your Token-Ring adapter, you must reboot your computer and rerun the SETUP with the Reference Disk. Run "Set Configuration" and select the new addresses for the Token-Ring adapter. The ALLEMM4 statement line in your CONFIG.SYS file should reflect the new addresses: DEVICE=ALLEMM4.SYS RAM X=B000-B7FF DEVICE=ALLEMM4.SYS RAM X=C000-C7FF Now that you have set your Token-Ring Adapter you can proceed with loading the device driver into high memory. LOADING THE TOKEN-RING DRIVERS ------------------------------ If you are using Token-Ring device drivers then all of them can be loaded into high memory if the PAL on your Token-Ring has had its serial number burnt in to it. If you have to supply the serial number, then only the DXMT0MOD.SYS driver can be loaded into high memory. Your Token-Ring drivers should always be loaded in the following order: DXMA0MOD.SYS should be loaded first DXMC0MOD.SYS should be loaded second, and DXMT0MOD.SYS (optional) should be loaded third. IMPORTANT: If you are using the IBM 3270 Connection Adapter for 3270 emulation, then it is critical where it and the IBM Token-Ring Adapter sit in the BUS. The 3270 Connection Adapter should be in Slot 1 (nearest the outside casing) and the IBM Token- Ring Adapter should be in Slot 2 next to it. At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. If your network adapter has any ROM, RAM or both which occupies addresses in reserved memory space (between 640K and 1024K) then: VINES 3.X --------- The BAN.COM program normally loads the entire network at once, it consists of three (3) parts: a) BAN.COM (Interrrupt Dispatcher) b) The network board driver (listed below) c) EPCBFS.COM (DOS Redirector) Each of the various network parts listed above may be loaded individually by running the BAN.COM program with the /NC (ie. No Controller) option. BAN /NC The /NC option will load only BAN.COM (approx.1K). You can then proceed to use the ALLOAD program to load the other parts of VINES above 640K. ALLOAD ie. for Etherlink: ALLOAD ETHERBAN and finally ALLOAD EPCBFS MEMORY REQUIREMENTS FOR VINES 3.01 ---------------------------------- Description File Name Size Addr. --------------------------------------------------- *****Base Software***** Interrupt Dispatcher BAN COM 1600 DOS Redirector EPCBFS COM 57744 *****Options***** NetBIOS emulator PCNETB COM 38682 Asynch Term. Emulation RASYNCH COM 46128 3270/SNA R3270 COM 66800 or T3270 COM 42448 Semaphore Emulation PCSEM COM 19584 Remote Print PCPRINT COM 7424 Description File Name Size Addr. --------------------------------------------------- *****LAN DRIVERS***** Asynch Dial-in ASYNCBAN COM 56889 3COM Etherlink ETHERBAN COM 50581 3COM Etherlink II 3C503BAN COM 51691 C800 3COM Etherlink/MC 3C523BAN COM 52835 C000 ProNET-10 Token Ring PROBAN COM 48891 ProNET-4/PC(P1340) TokenRing PRO4BAN COM 52511 E000 ProNET-4/AT(P1344) TokenRing PRO4BAN COM 52511 Micom NI5010 Ethernet INTERBAN COM 50617 Micom NI5210 Ethernet INTR2BAN COM 51748 C000 Micom NI5210S Starlan INTR2BAN COM 51748 C000 Omninet OMNIBAN COM 53443 ARCNET ARCBAN COM 50043 E000 PC Network PCNETBAN COM 52293 Ungerman-Bass NIC Ethernet UNGERBAN COM 50409 8000 Ungerman-Bass NIU Ethernet UBNIUBAN COM 50247 Ungerman-Bass NIU TokenRing UBTKBAN COM D000 VistaLAN/PC VLANBAN COM 51591 D000 IBM Token Ring TOKNBAN COM 51819 D800 IBM Token Ring TOKUIBAN COM 51754 D800 + IBM LAN Sup.Prog. DXMA0MOD SYS 8208 + DXMC0MOD SYS David Systems IPA IPABAN COM 55467 NT LanStar LSTARBAN COM 50419 AT&T Starlan ATTSTBAN COM 51811 C000 WD 8003S Starlan WDBAN COM 52253 C400 WD 8003E Ethernet WDBAN COM 52253 C400 The RAM requirements for the LAN Drivers are based upon: a) Default of 6 Open Files Volumes b) Default of 18 Communication Buffers The size of the LAN driver will vary depending upon the Files and Communication Buffers specified in PCCONFIG.DB: For each additional File Volume - add 220 Bytes For each additional Comm. Buffer - add 1024 Bytes VINES 4.0 --------- With VINES 4.0, the DOS redirector "EPCBFS", is replaced by "REDIR3" or "REDIR4" depending on the DOS version used. If there is enough contiguous high memory (between 55K and 63K) use: ALLOAD REDIRn If not, REDIRn contains 37K of CODE and 18K - 26K of DATA, and has the capability of loading itself in two different addresses in the high memory area; the code segment will load into a 37K block and the data segment will require between 18K and 26K. The syntax is as follows: REDIRn /C:yyyy /D:zzzz, loads both segments high REDIRn /C:yyyy, loads high code segment only or REDIRn /D:zzzz, loads high data segment only where: n specifies the DOS version. /C:yyyy specifies load address for code segment /D:zzzz specifies load address for data segment NOTE: Before using these switches, the actual size of REDIRn has to be determined. This can be done by loading it into conventional memory. Since the CODE segment takes 37K, the size of the DATA segment can be determined by substracting 37K (37888 bytes) from the total size of REDIRn. Once the sizes are determined and you know how much high memory is available (use DOS MEMORY BLOCKs under ALLMENU) you will know if you can load the complete REDIRn, the CODE segment only, the DATA segment only or both CODE and DATA, in separate high memory locations. Since REDIRn itself takes charge of loading its CODE and DATA segments, and does not inform ALLEMM4 which addresses it uses in high memory, it is necessary to create and load "dummy" programs to protect the memory areas. IMPORTANT: If there is enough contiguous high memory available for REDIRn to load, then you do not need to create the DUMMY files for the CODE and DATA segments. You can simply ALLOAD REDIRn. In such a case your AUTOEXEC.BAT file will appear as follows: BAN /NC /NL ALLOAD TOKUIBAN (or other adapter) ALLOAD REDIRn CREATING DUMMY PROGRAMS FOR REDIRn ---------------------------------- Let's suppose that there is no space to load REDIRn in one high memory block, but the CODE and DATA segments can be loaded separatly to two different locations in high memory. The following will show you how to create and load two DUMMY files that will allocate the memory areas that REDIRn uses to load its segments into high memory: Using a text editor, create a file named CODE_SEG.SCR that will reserve a space of 37888 bytes (9400h) in high memory: N CODE_SEG.COM A MOV DX,9400 INT 27 RCX 5 W Q NOTE: Make sure that you have left an extra blank line after the "INT 27" and "Q" lines. Save the file as "CODE_SEG.SCR". Use the DOS DEBUG program to process the file: DEBUG < CODE_SEG.SCR This will create an executable file called CODE_SEG.COM that can be loaded into high memory using ALLOAD. It will allocate the memory required by the CODE segment of REDIRn. Create DATA_SEG.SCR in a similar way. In line three the ???? must be changed to a hexadecimal value which denotes the size of the DATA segment. For example, if the DATA segment requires 20512 bytes (21K) then the hexadecimal value used to replace ???? would be 5020. N DATA_SEG.COM A MOV DX,???? INT 27 RCX 5 W Q NOTE: Make sure that you have left an extra blank line after the "INT 27" and "Q" lines. Save the file as "DATA_SEG.SCR". Use the DOS DEBUG program to process the file: DEBUG < DATA_SEG.SCR This will create an executable file called DATA_SEG.COM that can be loaded into high memory using ALLOAD. It will allocate the memory required by the DATA segment of REDIRn. Once you have created the CODE and DATA DUMMY files for REDIRn you should re-boot your computer with the following changes in your AUTOEXEC.BAT file: BAN /NC /NL ALLOAD TOKUIBAN (or other adapter) ALLOAD CODE_SEG.COM ALLOAD DATA_SEG.COM Once completed, run ALLOAD (with no options) and note the addresses where CODE_SEG.COM and DATA_SEG.COM have loaded in high memory. The addresses for the CODE and DATA segments can then be included with the REDIRn command. AUTOEXEC.BAT: BAN /NC /NL ALLOAD TOKUIBAN ALLOAD CODE_SEG.COM ALLOAD DATA.SEG.COM REDIR3 /C:yyyy /D:zzzz At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. CBIS recommends that you run NWSTART /ARGS first as this should provide you with the information and parameters for the network. The following network files can be loaded high: NC .EXE 8K NX .EXE 19K to 28K SHARE .EXE 8K NR .EXE 42K NS .EXE 66K UBRIDGE .EXE 9K BRIDGE .EXE 19K to 32K Note that every configuration is different and that the examples given are intended only as a guide. Your configuration may be different from the examples shown. EXAMPLE ------- CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM X=sp00-spFF * sp00 and spFF specify the start and end addresses of the range(s) to be excluded for the network adapter; the "s" represents the Segment and "p" is the Page of the address in hexadecimal. AUTOEXEC.BAT: FILES=20 BUFFERS=30 DEVICE= REM If there is a Network Card driver REM it should go here. ALLOAD NC ALLOAD NX ALLOAD SHARE ALLOAD NR ALLOAD NS ALLOAD UBRIDGE ALLOAD BRIDGE At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. EXAMPLE 1: 3+ Open Workstation with LAN Manager 1.0 --------------------------------------------------- Experience has shown that SPP.SYS needs to be loaded first in the first available block of memory above 640K. The order of the other device drivers does not matter, but the examples below were designed to obtain the best fit. CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM X=C000-C3FF AUTOEXEC.BAT: rem 3+Open DOS LAN Manager 1.0 rem PS/2 Model 30-286, 50, 50Z, or 60 w/ 1MB rem & DOS 3.3 cd \all\util FILES=20 BUFFERS=20 LASTDRIV=Z rem SPP.SYS must be loaded first into the first rem segment DEVICE /AF =\3open\doswksta\lanman\drivers\SPP.SYS DEVICE /LM =\3open\doswksta\lanman\drivers\PRO.SYS ...12 20 2 DEVICE=\3open\doswksta\lanman\drivers\BUF.SYS DEVICE /LM =\3open\doswksta\lanman\drivers ...\ETH523.SYS DEVICE=\3open\doswksta\lanman\drivers\IDP.SYS DEVICE /LM =\3open\doswksta\lanman\drivers\LGL.SYS cd \ rem 3+Open DOS LAN Manager 1.0 break on prompt = $p$g set home_server=dark_overlord set home_server_security=user set screen=color.ini rem initialize network path=\3open\doswksta\lanman\drivers runminds mindspro mindsbuf mindseth mindsidp mindsspp mindslgl rem load NETBIOS and MINSES into high memory rem with ALLOAD cd \3open\doswksta\lanman\drivers if errorlevel 1 goto Error_Netbios \all\util\alload netbios if errorlevel 1 goto Error_Netbios \all\util\alload /LM minses12 if errorlevel 1 goto Error_Netbios cd \ path=\3open\doswksta\lanman net start workstation ...etc. EXAMPLE 2: 3+ Open Workstation with LAN Manager 1.1 --------------------------------------------------- CONFIG.SYS: device=c:\all\ALLEMM4.SYS RAM shell=c:\command.com /e:256 /p device=c:\3open\doswksta\lanman\drivers\PROTMAN.DOS .../I:c:\3open\doswksta\lanman\drivers device=c:\3open\doswksta\lanman\drivers\XNSTP.DOS NOTE: PROTMAN.DOS and XNSTP.DOS can not be loaded into high memory and must remain in your CONFIG.SYS file. AUTOEXEC.BAT: echo off rem ********************************************** rem ** ** rem ** 3+Open DOS LAN Manager 1.1 AUTOEXEC.BAT ** rem ** Enhanced Netstation ** rem ** ** rem ********************************************** path=c:\;c:\dos;c:\ALL;c:\3open DEVICE=c:\3open\doswksta\lanman\drivers\ELNKII.DOS FILES=20 BUFFERS=30 LASTDRIVE=Z break on prompt=$p$g set home_server=server set home_server_security=user set screen=mono.ini rem Initialize Network path=c:\3open\doswksta\lanman\drivers;c:\all ALLOAD /TF NBP ALLOAD /TF NETBIND ALLOAD MINSES if errorlevel 1 goto Error_NetBIOS path=c:\3open\doswksta\lanman\netprog ALLOAD /TF NETWKSTA /COMPUTERNAME:xx .../LOGONSERVER: /LANROOT:C:\3OPEN \DOSWKSTA\LANMAN if errorlevel 1 goto Error_Workstation rem loading the re-director high may involve trying rem changing the parameters. :Do_Logon LOGON ... etc. The above configuration will result in 660K of conventional (DOS) memory available for your applications while on the network if using Hercules or compatible video. If using VGA video, the free available DOS memory is about 587K. APPLICATION NOTES ----------------- MINSES pre 1/27/86 and NB (NetBios) pre 8/12/87 will not work. If you have these you must update them. On 3Com's 3+ network operating system, if the full NetBIOS must be loaded into high memory, you must use NetBIOS 1.2.1H (available to 3+ customers from 3Com and is included with 3Com 3+Open systems). Use the IBM PS/2 Reference Diskette to relocate the RAM Packet Buffer of the EtherLink /MC card to address C000-C5FF. Although the documentation specifies that the ETH523 card RAM Packet Buffer is 24K, it really only uses 16K. Thus, you need only exclude 16K rather than 24K with ALLEMM4. FOR 3+OPEN only: In the LANMAN.INI file, you will find the line containing the "redir" command. Append the beginning of the line to include the full path of ALLOAD. \\ALLOAD REDIR At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. CONFIGURING DEPCA BOARD MEMORY MODES (W7 & W8) ---------------------------------------------- The function of JUMPERs W7 and W8 is dependant on the revision level of the DEPCA board and the version of DECnet PC software that you are using. DEPCA revision E (or later) is compatible with all versions of DECnet PC software. However, in order to use the 32K memory mode on revision E (or later) DEPCA, you must be running DECnet PC software that supports this feature. See your DECnet PC Software Product Description to verify 32K mode. If you have a DEPCA board with revision letter D, call your local DEC supplier for the W7 and W8 settings. For Revision E cards, follow the settings below: W7 W8 MODE START ADDRESS -- -- ---- ------------- IN IN 64K D000 OUT IN 64K E000 IN OUT 32K D800 OUT OUT 32K C800 NOTE: JUMPERs W7 and W8 are found above the bus contact teeth in the middle of the board. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. EXAMPLE 1 --------- A system with EGA and 3Com 501 ETHERLINK Card. CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM=C800-E7FF FR=NONE AUTOEXEC.BAT: FILES=25 BUFFERS=10 LASTDRIVE=Q DEVICE=LADDRV.SYS ALLOAD SCHPC ALLOAD DLL /IRQ:5 ALLOAD DNPETHPC SESSION /REM:1 ALLOAD REDIR ALLOAD LAST /NAME:(user name) ALLOAD LAD /R:1 NETTIME %1 %2 ETC. netuse ...etc. EXAMPLE 2 --------- A system with EGA and DEPCA Card (Rev. E 32K mode) CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM X=C800-CFFF FR=NONE AUTOEXEC.BAT: FILES=20 BUFFERS=20 LASTDRIVE=Q: DEVICE=LADDRV.SYS DEVICE= ALLOAD SCHPC ALLOAD DLL /IRQ:5 etc. EXAMPLE 3 --------- CONFIG.SYS: DEVICE=C:\ALL\ALLEMM4.SYS RAM X=C800-CFFF shell=c:\command.com /e:386 /p AUTOEXEC.BAT: path=c:\all;c:\decnet prompt=$p$g FILES=20 BUFFERS=30 LASTDRIVE=R DEVICE=C:\LADDRV.SYS /d:4 DEVICE=C:\KBDLK250.SYS ALLOAD SCHPC /S DLL /IRQ:5 /T:2 ALLOAD LAST /N:TRES02 /M:E /C:D /G:-1 ALLOAD LAD /R:-1 /W:-1 /A:-1 net start lad /n:TRES02 /r:-1 /w:-1 use E: \\tresry\issysd33 /v path=\decnet;c\all;E:\system;E:\decnet net define executor TRES02 1.302 dnpethpc rem load high with ALLOAD, if using Ethernet rem leave low if using DEPCA ALLOAD SESSION /REM:1 ALLOAD REDIR net start rdr net start lat subst L: E:\ set _VA1=G set _VA2=F set _VA3= set _VA4= set _VP=F set _P1= set _P2=L:\pcapp;L:\win\PS230;L:\win\util; ...L:\system;L:\decnet set _WD=PS230 set _SYS=IBM33 keybrd c:\all\alload deckeyb 1:\counrty\stduk.key set comspec=E:\command.com path %_P2% test byte At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. NOVELL VER. 2.1X EXAMPLE 1 --------- CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM X=sp00-spFF * sp00 and spFF specify the start and end addresses of the range(s) to be excluded for the network adapter; the "s" represents the Segment and "p" is the Page of the address in hexadecimal. AUTOEXEC.BAT: prompt $p$g path ... FILES=40 BUFFERS=40 ALLOAD IPX ALLOAD NETx (x=3 or 4 or XMS or EMS) ALLOAD NETBIOS (if required) F:LOGIN NOTE: Declaring LASTDRIVE=Z causes a problem. Netware requires F: as the default LOGIN. If you declare LASTDRIVE=Z all the available drive designations will go to a local DOS, and will not let Netware have a LOGIN drive. It is recommended that you do not use the LASTDRIVE statement. NOTE: If you are using a Token-Ring adapter then the drivers must be loaded as follows: DXMA0MOD.SYS DXMC0MOD.SYS , DXMT0MOD.SYS EXAMPLE 2 --------- A system used as workstation running Netware 2.0a with IBM Token-Ring Adapter Boards. Switch Block 1 is configured to address CA00 (FNNFNF) using Interrupt 3 (NF). Note: N denotes ON, F denotes OFF. CONFIG.SYS: DEVICE=C:\ALL\ALLEMM4.SYS X=C000-CDFF RAM AUTOEXEC.BAT: path ... prompt ... FILES=40 BUFFERS=20 rem other device drivers go here if needed DEVICE=DXMA0MOD.SYS DEVICE=DXMC0MOD.SYS ,C800 ALLOAD NETBIOS ALLOAD ANET3 rem The following commands load the EICON rem 3270 Emulator software ALLOAD NABIOS RDR password RDIR /2 SDLC USE SNAGATE ACCESS F: LOGIN At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. EXAMPLE 1 --------- IBM PS/2 with Network Adapter II CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM stacks=32,64 shell=command.com /e:512 /p AUTOEXEC.BAT: path ... prompt=$p$g DEVICE=IBMPCNET.SYS BUFFERS=20 FILES=30 LASTDRIVE=Z net start RDR net use R: net use S: net use T: net use U: net use LPT2 net use LPT3 EXAMPLE 2 --------- IBM PS/2 with IBM PC Network Adapter IIA Broadband and 3270 Emulation. CONFIG.SYS: device=dasddrv.sys (must remain in CONFIG.SYS) DEVICE=ALLEMM4.SYS RAM stacks=32,64 shell=command.com /e:512 /p AUTOEXEC.BAT: path ... prompt=$p$g BUFFERS=20 FILES=30 LASTDRIVE=Z DEVICE=IBMPCNET.SYS DEVICE=HOSTMYTE.SYS /Q (IBM 3270 emulator) net start RDR net use R: net use S: net use T: net use U: net use LPT2 net use LPT3 EXAMPLE 3 --------- IBM PC LAN version 1.2 CONFIG.SYS: shell=c:\command.com /e:256 /p device=c:\exdskbio.drv DEVICE=ALLEMM4.SYS RAM stacks=64,128 AUTOEXEC.BAT: verify on set intercom.bur=n:\icc path ... prompt $p$g BUFFERS /AF =20 FILES /AF =30 LASTDRIVE /AF =Z DEVICE /AF =DRIVER.SYS /D:2 /T:80 /S:9 /H:2 /C DEVICE /AF =ICC.DEV rem NETWORK START pause net start rdr rick /nbs:2048 /pb2:1024 net use lpt2 \\prntserv\laser if errorlevel 1 goto netmsg goto continue :netmsg cls type netlaser.msg pause :continue net use M: \\server\courier net use N: \\server\fileserv net use S: \\server\sym net use P: \\server\pdox pause m:newmail name -c if errorlevel 1 goto next m:mail -c name -prac :next ALLOAD /SG:CE00 MONITOR -C -K NAME -PRAC ... -x10 SWAPSK /N emcee menu0.fil 0 EXAMPLE 4 --------- IBM LAN Support Program 1.1, IBM PC LAN Program 1.31 and IBM 3270 Emulation Entry 1.21 with Token-Ring adapter. In order to maximize high memory it is necessary to pack together any adapter ROM/RAM in a contiguous address space. The 3270 Connection card type "A" has an 8K ROM with only one address choice: CE00- CFFF. Therefore, the Token-Ring ROM/RAM is set to accommodate this. The Token-Ring ROM is set at CC00 while the RAM address is set at C800 (see the Token- Ring data file for more information. CONFIG.SYS: DEVICE=DASDDRVR.SYS DEVICE=DXMA0MOD.SYS DEVICE=DXMC0MOD.SYS ,C800 DEVICE=ALLEMM4.SYS RAM X=C800-CFFF FR=NONE AUTOEXEC.BAT: prompt=$p$g path=c:\;c:\lan;c:\3270;c:\dos;c:\ALL rem Loading BUFFERS, FILES, and NetBIOS high BUFFERS=20 FILES=20 DEVICE=DXMT0MOD.SYS rem Loading PC LAN Program 1.31 net start rdr name net use lpt1: \\server1\printer1 net use D: \\server2\disk1 echo LPT1: is now the LAN 3812 echo Disk drive D: is from the file server cd\3270 rem Loading 3270 Emulation Entry 1.21 high ALLOAD PC3270 n ALLOAD EEHLLAPI RUNNING PC SUPPORT WITH AS/400 SYSTEM -------------------------------------- AS/400 PC Support uses the "EIMPCS.SYS" device driver as a memory manager to take advantage of EMS expanded memory available in the system . If expanded memory is detected by this device driver it will cause the shared folder support to load into the expanded memory instead of conventional memory. ALLEMM4.SYS provides expanded memory for EIMPCS.SYS. EXAMPLE ------- CONFIG.SYS: DEVICE=ALLEMM4.SYS RAM X=CC00-CFFF DEVICE=EIMPCS.SYS DEVICE=ECYDDX.SYS DEVICE=FSDD.SYS AUTOEXEC.BAT: prompt $p$g path ... FILES=50 BUFFERS=30 LASTDRIVE=Z If the READYNET overhead is very large, you may wish to use the FR=NONE option with ALLEMM4 to gain a further 64K of high memory: DEVICE=ALLEMM4.SYS RAM FR=NONE In order for UMMGR to load READYNET above 640K you must specify the address range of each high memory block you would like READYNET to use. The address must be included when UMMGR is executed, in the form: UMMGR sp00-spFF or UMMGR sp00 sp00-spff * sp00 and spFF specify the start and end addresses of the high memory range(s) to be used by READYNET; the "s" represents the Segment and "p" is the Page of the address in hexadecimal. If you run ALLOAD with no parameters you can get the address(es) of the high memory blocks for UMMGR. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. EXAMPLE ------- CONFIG.SYS: files=20 buffers=30 shell=c:\command.com /e:320 /p DEVICE=ALLEMM4.SYS RAM device=c:\readynet\ready.bin AUTOEXEC.BAT: path ... prompt=$p$g cd\readynet UMMGR C000-DFFF readyfs ... NOTE: Once a high memory block is allocated by UMMGR cannot be used to load any other TSR or DOS resource. You will not be able to use the Files, Buffers, Lastdrive, Device or ALLOAD loaders to move other overhead into high memory. At the DOS prompt (or AUTOEXEC.BAT) use the Files, Buffers, Lastdrive and Device programs supplied to load these DOS resources into high memory. Please remember that every system configuration is different and the examples given are intended as a guide. Your configuration may differ. EXAMPLE 1 --------- CONFIG.SYS: shell=c:\command.com /e:320 /p device=c:\lansmart\D-HMS.SYS DEVICE=ALLEMM4.SYS RAM X=C000-C3FF AUTOEXEC.BAT: path ... prompt=$p$g FILES=20 BUFFERS=30 LASTDRIVE=Z cd\lansmart LOGON ??? WKS /MEM=C000 ALLOAD /TF NET /R ALLOAD /TF CHAT /R EXAMPLE 2 --------- CONFIG.SYS: shell=c:\command.com /e:320 /p device=c:\lansmart\D-HMS.SYS DEVICE=ALLEMM4.SYS RAM X=C000-C3FF AUTOEXEC.BAT: path ... prompt=$p$g FILES=20 BUFFERS=30 LASTDRIVE=Z cd\lansmart LOGON ??? SVR /MEM:C000 ALLOAD /TF NET /R ALLOAD /TF CHAT /R NOTE: The D-HMS.SYS driver is only require if you are running on a 286 based system. If you are running on a 386 system then omit the D-HMS.SYS driver from your configuration as it is not required. <