{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "INSTALL DRV", "size": 269, "date": "1992-06-05", "time": "12:38" }, { "name": "INSTALL HLP", "size": 34997, "date": "1992-01-31", "time": "15:36" }, { "name": "INSTALL EXE", "size": 63008, "date": "1992-05-21", "time": "16:29" }, { "name": "README TXT", "size": 22032, "date": "1992-06-04", "time": "16:25" }, { "name": "INSTALL DLL", "size": 33280, "date": "1992-05-21", "time": "14:36" }, { "name": "NWUNPACK EXE", "size": 32826, "date": "1992-03-23", "time": "16:16" }, { "name": "LOGIN", "dir": true, "date": "1992-06-05", "time": "16:32" }, { "name": "WINDOWS", "dir": true, "date": "1992-06-05", "time": "16:32" }, { "name": "DOS NP", "dir": true, "date": "1992-06-05", "time": "16:32" }, { "name": "WINDOWS NP", "dir": true, "date": "1992-06-05", "time": "16:33" }, { "name": "REQUESTR", "dir": true, "date": "1992-06-05", "time": "16:33" }, { "name": "SQL", "dir": true, "date": "1992-06-05", "time": "16:37" } ] }, { "path": "/LOGIN", "files": [ { "name": "ATTACH EX@", "size": 13862, "date": "1991-07-18", "time": "8:56" }, { "name": "LOGIN EX@", "size": 41878, "date": "1991-06-04", "time": "16:35" }, { "name": "MAP EX@", "size": 14799, "date": "1991-07-18", "time": "11:08" }, { "name": "SLIST EX@", "size": 12266, "date": "1991-07-18", "time": "13:11" } ] }, { "path": "/WINDOWS", "files": [ { "name": "NETWARE DR@", "size": 50104, "date": "1992-02-21", "time": "15:26" }, { "name": "NETWARE HL@", "size": 16115, "date": "1992-02-12", "time": "15:12" }, { "name": "NWPOPUP EX@", "size": 1522, "date": "1992-02-24", "time": "8:27" }, { "name": "NWIPXSPX DL@", "size": 13745, "date": "1992-01-29", "time": "10:36" } ] }, { "path": "/DOS.NP", "files": [ { "name": "DOSNP EXE", "size": 9971, "date": "1992-05-26", "time": "11:00" } ] }, { "path": "/WINDOWS.NP", "files": [ { "name": "NETAPI DLL", "size": 7168, "date": "1991-06-24", "time": "11:05" } ] }, { "path": "/REQUESTR", "files": [ { "name": "LANSUP SY@", "size": 12596, "date": "1992-03-25", "time": "11:19" }, { "name": "SPXCALLS DL@", "size": 1100, "date": "1992-05-11", "time": "11:06" }, { "name": "SPX SY@", "size": 10083, "date": "1992-05-26", "time": "11:33" }, { "name": "SPDAEMON EX@", "size": 8170, "date": "1992-05-11", "time": "11:06" }, { "name": "VSHELL SY@", "size": 11942, "date": "1992-06-05", "time": "15:06" }, { "name": "DOSVSHLL SY@", "size": 2125, "date": "1992-05-22", "time": "17:21" }, { "name": "NWAFP DL@", "size": 3353, "date": "1991-08-30", "time": "11:07" }, { "name": "NWWORKER DL@", "size": 32350, "date": "1992-05-05", "time": "8:53" }, { "name": "LSL SY@", "size": 5798, "date": "1992-05-06", "time": "11:12" }, { "name": "DDAEMON EX@", "size": 6775, "date": "1992-05-06", "time": "11:11" }, { "name": "NWREQ SY@", "size": 12491, "date": "1992-05-19", "time": "13:08" }, { "name": "NWIFS IF@", "size": 23515, "date": "1992-05-18", "time": "10:56" }, { "name": "NWDAEMON EX@", "size": 15927, "date": "1992-05-18", "time": "10:57" }, { "name": "EXOS205 SY@", "size": 10656, "date": "1991-11-27", "time": "15:21" }, { "name": "EXOS215 SY@", "size": 10841, "date": "1991-11-27", "time": "15:21" }, { "name": "NE1000 SY@", "size": 8627, "date": "1991-06-24", "time": "13:41" }, { "name": "NE1500T SY@", "size": 10431, "date": "1992-04-16", "time": "12:08" }, { "name": "NE2-32 SY@", "size": 10338, "date": "1992-03-31", "time": "14:41" }, { "name": "NE2 SY@", "size": 8985, "date": "1991-06-24", "time": "13:40" }, { "name": "NE2000 SY@", "size": 9732, "date": "1991-11-27", "time": "11:10" }, { "name": "NE2100 SY@", "size": 10432, "date": "1992-04-16", "time": "12:08" }, { "name": "NE3200 SY@", "size": 12226, "date": "1992-04-02", "time": "15:25" }, { "name": "ODINSUP SY@", "size": 6261, "date": "1992-02-27", "time": "8:46" }, { "name": "PCN2L SY@", "size": 10017, "date": "1992-05-06", "time": "10:15" }, { "name": "ROUTE SY@", "size": 2850, "date": "1991-06-25", "time": "9:53" }, { "name": "TOKEN SY@", "size": 12813, "date": "1992-04-17", "time": "9:30" }, { "name": "TRXNET SY@", "size": 9365, "date": "1992-02-19", "time": "16:36" }, { "name": "TRXNET2 SY@", "size": 9372, "date": "1992-02-19", "time": "16:36" }, { "name": "TLI DL@", "size": 10038, "date": "1991-07-15", "time": "16:03" }, { "name": "TLI_SPX DL@", "size": 14386, "date": "1991-08-13", "time": "12:22" }, { "name": "TLI_TCP DL@", "size": 6320, "date": "1991-03-19", "time": "9:02" }, { "name": "RPRINTER EX@", "size": 51351, "date": "1992-03-10", "time": "15:53" }, { "name": "NWCONFIG DL@", "size": 2411, "date": "1992-05-27", "time": "14:43" }, { "name": "NWCALLS DL@", "size": 53131, "date": "1992-05-21", "time": "15:07" }, { "name": "IPX SY@", "size": 7544, "date": "1992-05-21", "time": "16:27" }, { "name": "IPXCALLS DL@", "size": 1035, "date": "1992-05-21", "time": "16:27" }, { "name": "3C501 SY@", "size": 7895, "date": "1991-06-24", "time": "13:44" }, { "name": "3C503 SY@", "size": 9416, "date": "1991-06-24", "time": "13:30" }, { "name": "3C505 SY@", "size": 10064, "date": "1991-08-15", "time": "9:14" }, { "name": "3C523 SY@", "size": 8150, "date": "1991-07-09", "time": "11:18" }, { "name": "NETBIOS EX@", "size": 12653, "date": "1992-05-18", "time": "15:26" }, { "name": "NWTOOLS EX@", "size": 47691, "date": "1992-05-28", "time": "9:13" }, { "name": "NWTOOLS HL@", "size": 12234, "date": "1992-05-14", "time": "13:55" }, { "name": "NWTOOLS DL@", "size": 16436, "date": "1992-05-28", "time": "9:13" }, { "name": "NETX CO@", "size": 34070, "date": "1992-05-27", "time": "14:55" }, { "name": "VIPX SY@", "size": 12122, "date": "1992-06-05", "time": "15:13" }, { "name": "DOSVIPX SY@", "size": 4598, "date": "1992-06-05", "time": "15:14" }, { "name": "NPCALLS DL@", "size": 1021, "date": "1992-05-11", "time": "13:04" }, { "name": "NPSERVER SY@", "size": 6527, "date": "1992-05-27", "time": "14:36" }, { "name": "NMPIPE SY@", "size": 5366, "date": "1992-05-19", "time": "11:50" }, { "name": "NPDAEMON EX@", "size": 15222, "date": "1992-05-27", "time": "14:37" }, { "name": "TBMI CO@", "size": 4615, "date": "1991-07-10", "time": "12:27" }, { "name": "NETAPI DL@", "size": 1025, "date": "1992-05-28", "time": "16:33" }, { "name": "NETSUB DL@", "size": 1025, "date": "1992-05-28", "time": "16:33" }, { "name": "NBDAEMON EX@", "size": 2397, "date": "1992-05-28", "time": "16:27" }, { "name": "NETBIOS SY@", "size": 13939, "date": "1992-05-28", "time": "16:33" } ] }, { "path": "/SQL", "files": [ { "name": "NETOEM DLL", "size": 2047, "date": "1991-02-13", "time": "21:22" }, { "name": "NETAPI DLL", "size": 2291, "date": "1991-02-13", "time": "21:20" } ] } ], "volume": "REQUESTER" } }, "desc_file": "README.TXT", "desc_text": " Readme file for the \r\n NetWare Requester for OS/2 v2.0\r\n included in the \r\n NetWare Workstation Kit for OS/2 v2.0\r\n June 1992\r\n\r\n\r\nThis Readme file explains known software problems and issues, as \r\nwell as corrections to the documentation. \r\n\r\n\r\nGeneral\r\n-------\r\n#1 This release does not support the remote-boot (RIPL) feature. \r\nRemote-boot support will be included in an NSD at a later date. \r\n\r\n#2 If you want to establish file server connections and map drives \r\nbefore executing the OS/2 startup folder or the STARTUP.CMD file, \r\nadd the following line to your AUTOEXEC.BAT file:\r\n\r\nCALL=C:\\NETWARE\\LOGIN.EXE SERVER\\USER\r\n\r\nIf you installed the Requester files in a location other than the \r\ndefault, replace \"C:\\NETWARE\" with the location of the Requester \r\nfiles. This capability is useful for automatically starting \r\nprograms from network drives. \r\n\r\n#3 The NetWare Requester manual incorrectly states that \r\nDBNMPIPE.EXE is found on the NetWare Requester for OS/2 v2.0 \r\ndiskette. DBNMPIPE.EXE is part of the SQL Server software from \r\nMicrosoft.\r\n\r\n\r\nVirtual DOS and Windows Sessions\r\n--------------------------------\r\n#4 Network support in virtual sessions can be private, global, or \r\nIPX/SPX-only. When you install the NetWare Requester with support \r\nfor virtual sessions, the default support is for IPX/SPX-only. IPX/SPX-only\r\nbecomes private support when you run NETX.COM in a session. \r\n\r\nNote: By default, the NetWare Resources Property will be set to\r\nPrivate. However, until you run NETX.COM, the support is\r\nactually IPX/SPX-only. \r\n\r\nIPX/SPX-ONLY. All DOS and Windows sessions set up for IPX/SPX-only \r\nsupport do not have a NetWare connection, but they do provide \r\nsupport for DOS IPX and SPX applications and access to OS/2-redirected\r\nNetWare resources such as drives and printers. IPX/SPX-only support \r\nuses the DOSVIPX.SYS (for VM Boot sessions) and VIPX.SYS \r\nprograms included on the NetWare Requester diskette. \r\n\r\nPRIVATE. All DOS and Windows sessions set up for private login \r\nsupport have their own connection to the NetWare network. Private \r\nlogin support uses the DOSVIPX.SYS, VIPX.SYS, and NETX.COM programs \r\nincluded on the NetWare Requester for OS/2 diskette. \r\n\r\nGLOBAL. All DOS, and Windows sessions set up for global login \r\nsupport share a single connection to a NetWare network with OS/2 \r\nsessions. Global login support uses the DOSVIPX.SYS, VIPX.SYS, \r\nVSHELL.SYS, and DOSVSHLL.SYS programs included on the NetWare \r\nRequester diskette.\r\n\r\n#5 Many of your non-NetWare-aware programs will function in an IPX/\r\nSPX-only environment, and since this environment requires the least \r\nsetup, you should try your programs in this environment first. If \r\nthe programs do not run properly in an IPX/SPX-only environment, \r\nrun them in a private or global environment. The private login \r\nenvironment provides support for all NetWare features and utilities. \r\nThe global environment does not currently support the FILER utility and\r\nprograms that use temporary drive connections. Support for these \r\nfeatures will be provided at a later time. \r\n\r\n#6 For all virtual sessions you start, the COMSPEC variable must \r\npoint to the correct version of DOS. If you are running the version \r\nof DOS included with OS/2, the COMSPEC variable should be set as \r\nfollows:\r\n\r\nSET COMSPEC=drive:\\OS2\\MDOS\\COMMAND.COM\r\n\r\nReplace \"drive\" with the letter of your boot drive. If you are \r\nrunning another version of DOS, the COMSPEC variable should point \r\nto the location of the COMMAND.COM file for that version. Be sure \r\nto check the COMSPEC variable definition AFTER logging in. \r\n\r\n#7 If you are running a Windows program that uses the IPX or SPX \r\nprotocol but does not access a NetWare server, you must load the \r\nTBMI.COM program BEFORE running the program. Load TBMI \r\nautomatically before each session by including the following line \r\nin your AUTOEXEC.BAT file:\r\n\r\ndrive:\\path\\TBMI.COM\r\n\r\nReplace \"drive:\\path\" with the location of the TBMI.COM file. By \r\ndefault, TBMI.COM is copied to the \\NETWARE directory with the \r\nother Requester files. For more information about TBMI, see the \r\nNetWare documentation for Windows workstations. \r\n\r\n#8 When you log out from an OS/2 session, the drive for your login \r\ndirectory is drive L:. When you log out from a virtual DOS session, \r\nthe drive for your login directory is the last physical drive plus \r\none. For example, if your last physical drive is C:, the drive for \r\nyour login directory will be D:. This means that the drive you see \r\nafter logging out depends on whether you log out from a DOS or an \r\nOS/2 session. \r\n\r\n\r\nPrivate Virtual Sessions\r\n------------------------\r\n#9 To set up private login support, do the following steps. \r\n\r\nA) Make sure network support for virtual sessions was installed \r\nwhen you installed the Requester. If it wasn't installed, use the \r\nRequester installation procedure to edit the CONFIG.SYS and install \r\nvirtual session support. \r\n\r\nB) Open the DOS Settings Notebook for a DOS or Windows icon on your \r\ndesktop. Modify the Settings notebook for each DOS and Windows \r\nicon you want to have private support. \r\n\r\nC) Select the DOS_LASTDRIVE property and type a drive letter other \r\nthan Z. The letter should name the last drive you want to appear \r\nas local in this session. In this session, NetWare can use all \r\ndrives occurring after the letter you specify.\r\n\r\nD) Select the DOS_FILES property and type 255.\r\n\r\nE) To enable the NetWare CAPTURE command, select the DOS_DEVICE \r\nproperty and type the following line:\r\n\r\ndrive:\\OS2\\MDOS\\LPTDD.SYS\r\n\r\nReplace \"drive\" with the drive letter of your boot drive. \r\n\r\nF) Exit the DOS Settings Notebook.\r\n\r\nG) Load the NETX.COM program in each session. To load NETX.COM \r\nautomatically in ALL DOS and Windows sessions, put the following \r\ncommand in an AUTOEXEC.BAT file in the root of your boot drive:\r\n\r\ndrive:\\path\\NETX.COM\r\n\r\nReplace \"drive:\\path\" with the location of NETX.COM. By default, \r\nNETX.COM is installed in \\NETWARE with the other Requester files. \r\n\r\nTo load NETX.COM automatically for every session you start from a \r\nparticular icon, use the Optional Parameters feature on the \r\nSettings Notebook for that icon. In the Optional Parameters text \r\nentry box, type /K followed by a space, the directory path, and the \r\nNETX.COM filename. The file will then be executed at the start of \r\nevery session opened from that icon. For example, to load NETX.COM \r\nfrom the default location, type the following:\r\n\r\n/K C:\\NETWARE\\NETX.COM\r\n\r\nFor more information about Optional Parameters, see your OS/2 \r\ndocumentation. \r\n\r\n#10 To access the network from a private session booted with a \r\nversion of DOS other than the one included in OS/2, type the \r\nfollowing lines in the CONFIG.SYS file on the DOS diskette or \r\npartition you will boot from:\r\n\r\nDEVICE=drive:\\OS2\\MDOS\\FSFILTER.SYS\r\nDEVICE=drive:\\path\\DOSVIPX.SYS\r\nFILES=255\r\n\r\nReplace \"drive:\\path\" with the drive and directory where the \r\nNetWare Requester files are located. \r\n\r\n\r\nGlobal Virtual Sessions\r\n-----------------------\r\n#11 To set up global login support, do the following steps. \r\n\r\nA) Make sure network support for virtual sessions was installed \r\nwhen you installed the Requester. If it wasn't installed, use the \r\nRequester installation procedure to edit the CONFIG.SYS and install \r\nvirtual session support. \r\n\r\nB) Open the DOS Settings Notebook for a DOS or Windows icon on your \r\ndesktop. Modify the Settings notebook for each DOS and Windows icon \r\nyou want to have global support.\r\n\r\nC) Select the NETWARE_RESOURCES property and choose the GLOBAL \r\nbutton. \r\n\r\nD) Exit the DOS Settings Notebook.\r\n\r\n#12 To access the network from a global session booted with a \r\nversion of DOS other than the one included in OS/2, type the \r\nfollowing lines in the CONFIG.SYS file on the DOS diskette or \r\npartition you will boot from:\r\n\r\nDEVICE=drive:\\OS2\\MDOS\\FSFILTER.SYS\r\nDEVICE=drive:\\path\\DOSVSHLL.SYS\r\nDEVICE=drive:\\path\\DOSVIPX.SYS\r\n\r\nReplace \"drive:\\path\" with the drive and directory where the \r\nNetWare Requester files are located. \r\n\r\n#13 The global login support provided with VSHELL does not support \r\nprograms, such as NETWARE.DRV, that use temporary drive \r\nconnections. Therefore, run Windows programs that are NetWare-\r\naware--and other programs that encounter problems--in a private \r\nrather than a global environment. \r\n\r\n#14 Drive mappings in DOS differ slightly from drive mappings in \r\nOS/2. In OS/2, all mapped drives function like root drives, so \r\ndrives mapped in OS/2 sessions will show up as root drives in global \r\nDOS sessions. Root drives mapped in global DOS sessions will show \r\nup as normal drives in OS/2 sessions. \r\n\r\nSearch drive mappings are not used in OS/2. Therefore, search \r\ndrives mapped in global DOS sessions are ignored in OS/2 sessions. \r\nAlso, search drives mapped in one DOS session do not apply to other \r\nDOS sessions. To eliminate confusion, avoid using search drives \r\ncompletely in a global environment. Instead, obtain the same \r\nfunctionality by setting up your environment as follows: \r\n\r\nA) If you want to use both global and private login support from \r\nthe same machine, create two \"DOS Full Screen\" icons on your \r\ndesktop. Name one icon for global and one for private. \r\n\r\nB) Follow the instructions in the NetWare Requester manual to set \r\nup the DOS Settings for both the global and private icons. \r\n\r\nC) Decide which drives you want mapped in your global environment. \r\nDecide which of those drives need to be included in a search path. \r\n\r\nD) Edit your OS/2 login script and include map statements for all \r\nNetWare drives. \r\n\r\nE) Edit your DOS login script and include map root statements for \r\nall NetWare drives. Use MAP ROOT rather than MAP for consistency \r\nbetween DOS and OS/2. For easiest maintenance, both login scripts \r\nshould contain identical map statements. \r\n\r\nF) Create an OS/2 .CMD file which includes a path statement and \r\nthe drive letters you want included in the path. The path is where \r\nOS/2 searches for .EXE, .CMD, and .COM files. For example, to \r\ninclude drive P: in the search path, type the following line in \r\nyour .CMD file: \r\n\r\nSET PATH=%PATH%;p:\\;\r\n\r\nNote: The \"%PATH%;\" appends whatever you type to the directories \r\nthat already exist in the PATH statement. \r\n\r\nIf needed, you can also include a drive letter in the data path \r\n(DPATH). The DPATH is where OS/2 searches for non-executable, \r\nnon-.DLL types of files. To include drive P: in the DATH, you would \r\ntype the following line in your .CMD file:\r\n\r\nSET DPATH=%DPATH%;p:\\;\r\n\r\nG) Create a DOS .BAT file which includes the same PATH statements \r\nyou included in the OS/2 .CMD file. You cannot include DPATH \r\nstatements in the DOS .BAT file. DOS PATH statements are limited \r\nto 123 characters, so try to map drives to the exact directories \r\nyou need and minimize the number of subdirectories you specify.\r\n\r\nH) Run the .CMD file each time you open an OS/2 session. Run the \r\n.BAT file each time you open a DOS global session. One way to do \r\nthis is to use the Optional Parameters feature on the Settings \r\nNotebook. In the Optional Parameters text entry box, type /K \r\nfollowed by a space and the name of the .CMD or .BAT file. The \r\nfile will then be executed at the start of every session opened \r\nfrom that icon. \r\n\r\nFor more information about PATH, DPATH, Settings, or Optional \r\nParameters, see your OS/2 documentation. \r\n\r\n#15 DOS applications using VSHELL may not be able to open files \r\non a NetWare v3.11 server if you do not have file scan rights in \r\nthe directory where the files are located. If your application \r\ncannot open a file, check your file scan rights. This does not \r\napply to applications using NETX.\r\n\r\n#16 The VSHELL program is compatible with 3.x DOS programs. It is \r\nnot compatible with earlier versions of DOS programs that use \r\nNetWare FCB function calls. \r\n\r\n\r\nNamed Pipes and SPX\r\n-------------------\r\n#17 The maximum number of Named Pipes servers supported on a single \r\nnetwork is 100. \r\n\r\n#18 The \"abort timeout,\" \"listen timeout,\" \"send timeout,\" and \r\n\"verify timeout\" settings for the Protocol Stack SPX option have \r\nan upper limit of 65,535 milliseconds.\r\n\r\n\r\nNetBIOS\r\n---------\r\n#19 Some defaults for the NetWare NetBIOS option in the NET.CFG \r\nfile are incorrectly documented in the NetWare Requester manual. \r\nThe correct defaults are:\r\n\r\nCOMMANDS Default=128 commands\r\nNAMES Default=32 names\r\nSESSIONS Default =64 sessions, maximum allowed=64 sessions\r\n\r\n#20 Chapter 7 of the NetWare Requester manual shows two incorrect \r\nexamples of modifying the PROTOCOL.INI file. In both cases, you \r\ndo not need to type \"LM10,\" although \"LM10\" is shown in the example. \r\nThe lines added to PROTOCOL.INI should read:\r\n\r\n[NETBIOS]\r\n DriverName = NETBIOS$\r\n ADAPTER0 = IPXNB$,0,16,16,8\r\n\r\n#21 To run NetBIOS applications from a virtual session when \r\nExtended Services/LAN Services are NOT loaded, do not install \r\nNovell's NETBIOS.SYS as instructed in the NetWare Requester manual. \r\nJust run the NETBIOS.EXE program in the virtual session. You can only\r\nhave one NetBIOS connection per OS/2 machine. It can be either one\r\nDOS/Windows connection or one OS/2 connection.\r\n\r\n#22 NetBIOS requests from a virtual Windows session do not go \r\nthrough Novell's Windows NETAPI.DLL as documented in the NetWare \r\nRequester manual. The requests go directly to NETBIOS.EXE. \r\n\r\n\r\nUsing ODINSUP (Interoperability)\r\n--------------------------------\r\n#23 Each time you install IBM communications and networking \r\nsoftware, install or reinstall the NetWare Requester afterward. \r\nThe order that components load in the CONFIG.SYS file is important \r\nwhen running ODINSUP, NetBIOS, or LANSUP. The NetWare Requester \r\ninstallation program automatically orders the statements \r\ncorrectly. \r\n\r\n#24 The CONFIG.SYS interoperability example in the NetWare \r\nRequester manual is incorrect. When running the NetWare Requester \r\nwith Extended Services or LAN Services, IBM's NETWKSTA.200 file \r\nshould load after the NWIFS.IFS in the CONFIG.SYS file. Following \r\nis a new CONFIG.SYS example:\r\n\r\nLIBPATH=.;C:\\OS2\\DLL;C:\\OS2\\MDOS;C:\\;C:\\OS2\\APPS\\DLL;C:\\NETWARE;\r\nSET PATH=C:\\OS2;C:\\OS2\\SYSTEM;C:\\OS2\\MDOS\\WINOS2;C:\\OS2\\INSTALL; \r\nC:\\;C:\\OS2\\MDOS;C:\\OS2\\APPS;C:\\NETWARE;L:\\OS2;P:\\OS2;\r\nSET DPATH=C:\\OS2;C:\\OS2\\SYSTEM;C:\\OS2\\MDOS\\WINOS2;C:\\OS2\\INSTALL; \r\nC:\\;C:\\OS2\\BITMAP;C:\\OS2\\MDOS;C:\\OS2\\APPS;C:\\NETWARE; \r\n\r\nDEVICE=C:\\IBMCOM\\LANMSGDD.OS2 /I:C:\\IBMCOM \r\nDEVICE=C:\\IBMCOM\\PROTMAN.OS2 /I:C:\\IBMCOM \r\nDEVICE=C:\\IBMCOM\\PROTOCOL\\LANDD.OS2 \r\nDEVICE=C:IBMCOM\\PROTOCOL\\NETBEUI.OS2\r\nrem DEVICE=C:\\IBMCOM\\MACS\\IBMTOK.OS2 \r\nRUN=C:\\IBMCOM\\PROTOCOL\\LANDLL.EXE \r\nRUN=C:\\IBMCOM\\PROTOCOL\\NETBIND.EXE \r\nRUN=C:\\IBMCOM\\LANMSGEX.EXE \r\nDEVICE=C:\\IBMLAN\\NETPROG\\RDHELP.200\r\n\r\nrem --- NetWare Requester statements BEGIN --- \r\nDEVICE=C:\\NETWARE\\LSL.SYS \r\nRUN=C:\\NETWARE\\DDAEMON.EXE \r\nDEVICE=C:\\NETWARE\\TOKEN.SYS \r\nDEVICE=C:\\NETWARE\\ODINSUP.SYS\r\nDEVICE=C:\\NETWARE\\IPX.SYS \r\nDEVICE=C:\\NETWARE\\SPX.SYS \r\nRUN=C:\\NETWARE\\SPDAEMON.EXE \r\nrem DEVICE=C:\\NETWARE\\NMPIPE.SYS \r\nrem DEVICE=C:\\NETWARE\\NPSERVER.SYS \r\nrem RUN=C:\\NETWARE\\NPDAEMON.EXE NP_COMPUTERNAME \r\nDEVICE=C:\\NETWARE\\NWREQ.SYS \r\nIFS=C:\\NETWARE\\NWIFS.IFS \r\nRUN=C:\\NETWARE\\NWDAEMON.EXE \r\nrem DEVICE=C:\\NETWARE\\NETBIOS.SYS \r\nrem RUN=C:\\NETWARE\\NBDAEMON.EXE \r\nDEVICE=C:\\NETWARE\\VIPX.SYS \r\nRUN=C:\\NETWARE\\NWSPOOL.EXE\r\nrem --- NetWare Requester statements END ---\r\n\r\nIFS=C:\\IBMLAN\\NETPROG\\NETWKSTA.200 /I:C:\\IBMLAN \r\nDEVICE=C:\\IBMCOM\\PROTOCOL\\NETBIOS.OS2 \r\n\r\n#25 If you are using Token-Ring network boards that support frame \r\nsizes up to 4 KB, type the following lines in your NET.CFG file:\r\n\r\nLink Support\r\n buffers 14 4210\r\n\r\nThe manual incorrectly says to use \"15\" instead of \"14\".\r\n\r\n#26 If you are using ODINSUP, you do not need to make sure that \r\nthe Communications Manager transmit buffers are 6 bytes larger than \r\nyour NetWare Requester Link Support buffers. The NetWare Requester \r\nmanual is incorrect. \r\n\r\n#27 The directions in chapter 6 of the manual for increasing the \r\npacket size are incorrect for network boards that support frame \r\nsizes up to 2 KB. Follow these instructions. If the network boards \r\nyou're using support only frame sizes up to 2 KB, the default size \r\n(buffers 20 1514) is adequate for Ethernet boards. If Token-Ring \r\nboards require 2 KB, the size must be increased to\r\n\r\nLink Support\r\n buffers n 2154\r\n\r\nReplace \"n\" with a number less than or equal to 28, so that the \r\nmaximum memory size of 64 KB is not exceeded. \r\n\r\n\r\nUsing LANSUP (Interoperability)\r\n-------------------------------\r\n#28 Novell's LAN Support (LANSUP) device driver replaces the \r\nCMGRLAN and TOKENEE modules used in the NetWare Requester v1.3. \r\nCMGRLAN and TOKENEE are not supported in the NetWare Requester \r\nv2.0. LANSUP meets the needs of IBM LAN users who would like to \r\naccess NetWare but do not have an ODI-compliant network board \r\ndriver for the board in the workstation. \r\n\r\nLANSUP supports PC Network II in addition to Ethernet and Token-\r\nRing compatible drivers. ODINSUP and LANSUP provide essentially the \r\nsame functionality, but each targets a different communications \r\ninteroperability environment (LANSUP for primary IBM LAN users or \r\nODINSUP for primary NetWare users). \r\n\r\nTo use LANSUP, do the following:\r\n\r\nA) Install all IBM communication and database products that will \r\nbe used. \r\n\r\nB) Install the NetWare Requester for OS/2 v2.0\r\n\r\nC) Modify the CONFIG.SYS file by doing the following:\r\n\r\n- Make sure that LANSUP.SYS is loaded after PROTMAN.OS2 and \r\n LSL.SYS. If the CONFIG.SYS contains a statement to load an \r\n ODI driver, replace the ODI driver name with LANSUP.SYS. If \r\n the CONFIG.SYS does not contain an ODI driver, add the \r\n statement to load LANSUP.SYS. \r\n\r\n- Make sure that the NetWare NWIFS.IFS loads before the OS/2 \r\n NETWKSTA.200 file.\r\n\r\nFollowing is a sample CONFIG.SYS file for using LANSUP:\r\n\r\nLIBPATH=.;C:\\OS2\\DLL;C:\\OS2\\MDOS;C:\\;C:\\OS2\\APPS\\DLL;C:\\NETWARE;\r\nSET PATH=C:\\OS2;C:\\OS2\\SYSTEM;C:\\OS2\\MDOS\\WINOS2;C:\\OS2\\INSTALL; \r\nC:\\;C:\\OS2\\MDOS;C:\\OS2\\APPS;C:\\NETWARE;L:\\OS2;P:\\OS2;\r\nSET DPATH=C:\\OS2;C:\\OS2\\SYSTEM;C:\\OS2\\MDOS\\WINOS2;C:\\OS2\\INSTALL; \r\nC:\\;C:\\OS2\\BITMAP;C:\\OS2\\MDOS;C:\\OS2\\APPS;C:\\NETWARE; \r\n\r\nDEVICE=C:\\IBMCOM\\LANMSGDD.OS2 /I:C:\\IBMCOM \r\nDEVICE=C:\\IBMCOM\\PROTMAN.OS2 /I:C:\\IBMCOM \r\nDEVICE=C:\\IBMCOM\\PROTOCOL\\LANDD.OS2 \r\nDEVICE=C:IBMCOM\\PROTOCOL\\NETBEUI.OS2\r\nDEVICE=C:\\IBMCOM\\MACS\\IBMTOK.OS2 \r\nRUN=C:\\IBMCOM\\PROTOCOL\\LANDLL.EXE \r\nRUN=C:\\IBMCOM\\PROTOCOL\\NETBIND.EXE \r\nRUN=C:\\IBMCOM\\LANMSGEX.EXE \r\nDEVICE=C:\\IBMLAN\\NETPROG\\RDHELP.200\r\n\r\nrem --- NetWare Requester statements BEGIN --- \r\nDEVICE=C:\\NETWARE\\LSL.SYS \r\nRUN=C:\\NETWARE\\DDAEMON.EXE \r\nrem Replace TOKEN.SYS with LANSUP.SYS\r\nDEVICE=C:\\NETWARE\\LANSUP.SYS \r\nDEVICE=C:\\NETWARE\\IPX.SYS \r\nDEVICE=C:\\NETWARE\\SPX.SYS \r\nRUN=C:\\NETWARE\\SPDAEMON.EXE \r\nrem DEVICE=C:\\NETWARE\\NMPIPE.SYS \r\nrem DEVICE=C:\\NETWARE\\NPSERVER.SYS \r\nrem RUN=C:\\NETWARE\\NPDAEMON.EXE NP_COMPUTERNAME \r\nDEVICE=C:\\NETWARE\\NWREQ.SYS \r\nIFS=C:\\NETWARE\\NWIFS.IFS \r\nRUN=C:\\NETWARE\\NWDAEMON.EXE \r\nrem DEVICE=C:\\NETWARE\\NETBIOS.SYS \r\nrem RUN=C:\\NETWARE\\NBDAEMON.EXE \r\nDEVICE=C:\\NETWARE\\VIPX.SYS \r\nrem --- NetWare Requester statements END ---\r\n\r\nIFS=C:\\IBMLAN\\NETPROG\\NETWKSTA.200 /I:C:\\IBMLAN \r\nDEVICE=C:\\IBMCOM\\PROTOCOL\\NETBIOS.OS2 \r\n\r\nD) Modify the NET.CFG file by doing the following:\r\n\r\n- Use the Link Driver option to enable the frame types supported\r\n by Token-Ring, Ethernet, or PC Network II. You must enable at \r\n least one frame type. Supported frame types are: \r\n\r\n token-ring, token-ring_snap for Token-Ring \r\n ethernet_802.2 and ethernet_snap for Ethernet \r\n ibm_pcn2_802.2 and ibm_pcn2_snap for PC Network II\r\n\r\n For example, to enable both allowable frame types for Token-Ring, \r\n type the following:\r\n\r\n Link Driver LANSUP\r\n frame token_ring\r\n frame token_ring_snap\r\n\r\n - Use the Link Driver statement to specify the node address \r\n used by the network board. The node address is normally \r\n printed on the board. For example, to enable one PC Network II \r\n frame type and set the node address, type the following:\r\n\r\n Link Driver LANSUP\r\n node address 080000A564CBL\r\n frame ibm_pcn2_802.2\r\n\r\n The node address must be a 6-byte hexadecimal number (12 \r\n characters) followed by the letter L or M (standing for LSB \r\n or MSB). Note: If you do not know the node address, you can type \r\n a \"dummy\" address and reboot the machine. At machine start-up, \r\n the correct address will be displayed. \r\n\r\n- Use the Link Support statement to increase the size of the packet \r\n to be transmitted. For Ethernet network boards that only support \r\n frame sizes up to 2 KB, the default size (buffers 20 1514) is \r\n adequate. If Token-Ring boards require 2 KB, the size must be \r\n increased to \r\n\r\n Link Support\r\n buffers n 2154\r\n\r\n Replace \"n\" with a number less than or equal to 28, so that the \r\n maximum memory size of 64 KB is not exceeded. For Token-Ring \r\n boards that support frame sizes up to 4 KB, type the following \r\n statement:\r\n\r\n Link Support\r\n buffers 14 4210\r\n\r\n- (Optional) Change the default for whether addresses are \r\n transmitted in canonical (least significant bit first) or \r\n non-canonical (most significant bit first) form. By default, \r\n Token-Ring and PC Network II frames are in non-canonical (or \r\n MSB) format and Ethernet frames are canonical (LSB). \r\n\r\n To change the default, add an LSB or MSB keyword after the \r\n frame statement. For example, to enable both Token-Ring frame \r\n types, and override the non-canonical form for one of the \r\n frame types, add the following statement:\r\n\r\n Link Driver LANSUP\r\n frame token_ring\r\n frame token_ring_snap lsb\r\n\r\n Note: MSB and LSB can only be used if the network board \r\n driver supports Octet Bit Reversal (OBR)." }