{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "LITE", "dir": true, "date": "1994-03-25", "time": "11:41" } ] }, { "path": "/LITE", "files": [ { "name": "DRIVER", "dir": true, "date": "1994-03-25", "time": "11:41" }, { "name": "PROGRAM1", "dir": true, "date": "1994-03-25", "time": "11:42" }, { "name": "PROGRAM2", "dir": true, "date": "1994-03-25", "time": "11:42" } ] }, { "path": "/LITE/DRIVER", "files": [ { "name": "DRIVER LST", "size": 1221, "date": "1991-09-11", "time": "19:11" }, { "name": "WDPLUS COM", "size": 17076, "date": "1991-06-21", "time": "14:11" }, { "name": "3C503 COM", "size": 14821, "date": "1991-06-14", "time": "9:14" }, { "name": "3C523 COM", "size": 12238, "date": "1991-07-29", "time": "9:35" }, { "name": "IPXODI COM", "size": 20885, "date": "1991-06-25", "time": "13:52" }, { "name": "LSL COM", "size": 7557, "date": "1991-06-25", "time": "13:42" }, { "name": "NE1000 COM", "size": 12717, "date": "1991-07-29", "time": "9:37" }, { "name": "NE2 COM", "size": 13028, "date": "1991-07-29", "time": "9:33" }, { "name": "NE2000 COM", "size": 13018, "date": "1991-06-03", "time": "13:25" }, { "name": "NET OVL", "size": 87092, "date": "1991-09-11", "time": "19:11" }, { "name": "PCN2L COM", "size": 14117, "date": "1991-07-17", "time": "15:40" }, { "name": "TOKEN COM", "size": 15663, "date": "1991-06-14", "time": "16:10" }, { "name": "TRXNET COM", "size": 12128, "date": "1991-08-06", "time": "10:48" }, { "name": "DEDICATE COM", "size": 170, "date": "1991-09-11", "time": "19:11" }, { "name": "DEMO EXE", "size": 11766, "date": "1991-09-11", "time": "19:11" }, { "name": "NETBIOS EXE", "size": 21506, "date": "1990-11-15", "time": "15:48" }, { "name": "NLSNIPES EXE", "size": 18042, "date": "1991-09-11", "time": "19:11" }, { "name": "NE2000 INS", "size": 96, "date": "1991-09-11", "time": "19:11" }, { "name": "3C503 INS", "size": 170, "date": "1991-09-11", "time": "19:11" }, { "name": "WDPLUS INS", "size": 219, "date": "1991-09-11", "time": "19:11" }, { "name": "NE1000 INS", "size": 97, "date": "1991-09-11", "time": "19:11" }, { "name": "TRXNET INS", "size": 203, "date": "1991-09-11", "time": "19:11" } ] }, { "path": "/LITE/PROGRAM1", "files": [ { "name": "CLIENT EXE", "size": 16102, "date": "1991-09-11", "time": "19:11" }, { "name": "INSTALL EXE", "size": 44032, "date": "1991-09-11", "time": "19:11" }, { "name": "NET EXE", "size": 29416, "date": "1991-09-11", "time": "19:11" }, { "name": "SERVER EXE", "size": 34310, "date": "1991-09-12", "time": "19:11" } ] }, { "path": "/LITE/PROGRAM2", "files": [ { "name": "CLIENT EXE", "size": 16102, "date": "1991-09-11", "time": "19:11" }, { "name": "INSTALL EXE", "size": 44032, "date": "1991-09-11", "time": "19:11" }, { "name": "NET EXE", "size": 29416, "date": "1991-09-11", "time": "19:11" }, { "name": "SERVER EXE", "size": 34310, "date": "1991-09-12", "time": "19:11" }, { "name": "NET HLP", "size": 95574, "date": "1991-09-11", "time": "19:11" }, { "name": "LITE$RUN OVL", "size": 2400, "date": "1991-09-11", "time": "19:11" }, { "name": "README TXT", "size": 32648, "date": "1991-09-12", "time": "19:11" } ] } ], "volume": "5E03190B250" } }, "desc_file": "README.TXT", "desc_text": "\r\n NetWare Lite 1.0 -- README file (09/12/91)\r\n --------------------------------------------\r\n ***************************************************************************\r\n ************ Print this file and save it for future reference. ************\r\n ***************************************************************************\r\n This file contains hints and suggested conventions for how NetWare\r\n Lite might be setup on a network and how it might be used. \r\n\r\n\r\n\r\n Table of Contents\r\n -----------------\r\n 1. Shared Resources\r\n 2. Printing\r\n 3. Network Applications\r\n 4. Compatibility with the NetWare Shell\r\n 5. SERVER optimization and functions\r\n 6. Using CD-ROMs\r\n 7. IPXODI\r\n 8. Auxiliary NetWare Lite files\r\n 9. Logging in after INSTALL\r\n 10. Windows compatibility\r\n 11. Documentation Errors (Errata)\r\n \r\n\r\n\r\n 1. Shared Resources (Network Directories and Printers)\r\n ------------------------------------------------------\r\n\r\n Shared resources are those resources (Network Directories or Network\r\n Printers) that are shared with CLIENTs on a network. We suggest that\r\n Network Directories and Printers be given descriptive names. Good\r\n names for Network Directories might be: TURBOC, WORDPERFECT, GAMES,\r\n IBM_DOS_310 or PUBLIC. Good names for Network Printers might be:\r\n LASERJET_II, EPSON_DOT. Names that might not be good are CDRIVE,\r\n PRINTER1, PRINTER2. These names provide no indication of what\r\n applications or what kind of printers are being made available. You\r\n will notice that during NetWare Lite installation we create a CDRIVE\r\n Network Directory for you. When you become familiar with the product\r\n this resource ought to be removed and one or more descriptive Network\r\n Directories created in its place.\r\n\r\n Assisting Floppy-based CLIENTs\r\n If there are workstations on the network that don't have hard disks\r\n then we suggest that NetWork Directories be set up to help those\r\n workstations. A DOS shared Network Directory should be created so that\r\n workstations with no hard disks can load DOS commands from the network. \r\n A Network Directory sharing IBM DOS version 3.10 (named IBM_DOS_310\r\n perhaps) would be useful for those CLIENTs with only floppy drives to\r\n get to their version of DOS. In conjunction with this the DOS\r\n environment variable \"comspec\" should be set so as to allow the loading\r\n of DOS COMMAND.COM from across the network; for better performance. \r\n For example, these lines could be included in an AUTOEXEC.BAT or\r\n STARTNET.BAT file:\r\n\r\n NET MAP F: IBM_DOS_310\r\n SET COMSPEC=F:\\COMMAND.COM\r\n\r\n In addition, workstations that only have floppies can be assisted by\r\n creating a Network Directory where the NetWare Lite utility (NET.EXE,\r\n NET.OVL, NET.HLP and LITE$RUN.OVL) can be loaded from; instead of\r\n always loading them from the floppy. We suggest that a Network\r\n Directory called NWLITE be created. This directory should be a\r\n SERVER's C:\\NWLITE directory. We also suggest that this Network\r\n Directory be given default rights of READ and not the default of ALL. \r\n All floppy-only CLIENTs should map a drive to this resource and add the\r\n drive to their DOS path. This will allow the loading of the NET\r\n utility from across the network; a much better solution than loading\r\n from floppy. For example, these lines could be included in an\r\n AUTOEXEC.BAT or STARTNET.BAT file:\r\n\r\n NET MAP M: NWLITE\r\n PATH=M:.;%PATH%\r\n\r\n If you want to run the CLIENT from a floppy drive and have that\r\n diskette be the boot diskette, the following configuration is\r\n suggested. Where ever NE2000.COM appears, replace it with the\r\n appropriate driver name you are using. Also, L: and M: are simply used\r\n as examples; you may use any other valid driver letters. We map drive\r\n M: to the Network Directory NWLITE as described above. Similarly, L:\r\n is mapped to the Network Directory IBM_DOS_310 as described above.\r\n\r\n 1) Create a bootable diskette using the FORMAT A: /S command.\r\n\r\n 2) Copy the following NetWare Lite files to the diskette.\r\n LSL.COM\r\n NE2000.COM\r\n IPXODI.COM\r\n CLIENT.EXE\r\n NET.EXE\r\n\r\n 3) Create an AUTOEXEC.BAT with the following lines added to it.\r\n LSL\r\n NE2000\r\n IPXODI A\r\n NET LOGIN\r\n NET MAP L: IBM_DOS_310\r\n NET MAP M: NWLITE\r\n PATH=L:\\;M:\\;%PATH%\r\n SET COMSPEC=L:\\COMMAND.COM\r\n\r\n 4) Create an CONFIG.SYS with the following line added to it.\r\n LASTDRIVE=M\r\n\r\n For those Network Directories that contain applications (executables)\r\n the drives used to map to these applications should be included in the\r\n DOS environment variable PATH. For example, these lines could also be\r\n included in an AUTOEXEC.BAT or STARTNET.BAT file:\r\n\r\n NET MAP G: TURBOC\r\n NET MAP H: WORDPERFECT\r\n NET MAP I: GAMES\r\n SET PATH=G:\\BIN;H:.;I:\\TETRIS;%PATH%\r\n\r\n Make Shared Executables Read-Only\r\n Executable files that will be run by more than one user at a time need\r\n to be marked as read-only. If they are not, then you may notice at\r\n times that you are temporarily denied access to a file you wish to run. \r\n For example, you may get a message that access was denied or that the\r\n EXE file could not be run. If this happens, mark the executable files\r\n read-only using the DOS ATTRIB command. Type ATTRIB +R *.EXE in the\r\n directory where the executable files reside. This example marks the\r\n *.EXE files read-only. All shared .COMs, .BATs, and .OVLs should be\r\n marked as well. The read-only attribute can be cleared using the same\r\n command replacing the +R with -R. (See DOS documentation for\r\n information on the ATTRIB command).\r\n\r\n Location Independence\r\n You will notice that our resources are location independent. Suppose\r\n you create a Network Directory named ALL_APPS on a server named\r\n DEPT_SERVER. Server DEPT_SERVER is a 8 MHz 286 machine with a 40 MB\r\n hard disk. All CLIENTs map drives to ALL_APPS and use it every day. \r\n Now suppose you buy a 50 MHz 486 machine with a 1 GB disk drive on it. \r\n You want to move the Network Directory ALL_APPS to this new machine. \r\n You install this new machine and call it HOT_SERVER. You can then\r\n create a new Network Directory on this new server and call it ALL_APPS\r\n (same name as before). You then copy the files from DEPT_SERVER to\r\n HOT_SERVER. ALL_APPS can now be removed from DEPT_SERVER. All your\r\n CLIENTs will now use ALL_APPS from HOT_SERVER and nothing need be\r\n changed from the CLIENT's perspective. The CLIENTs don't need to know\r\n that the location of the Network Directory ALL_APPS has moved. This\r\n same principle applies to Network Printers.\r\n\r\n\r\n\r\n 2. Printing -- Conventions and Suggestions\r\n -----------\r\n\r\n Chances are that you bought this product to share one or more printers. \r\n For this reason, give special attention to the following remarks.\r\n\r\n Local Network Printers\r\n Once a printer is assigned as a Network Printer, you should only access\r\n that printer through the network. You may have a printer attached to\r\n your workstation that has been defined as a Network Printer. In this\r\n case, you should capture a port when you wish to print to it. If you\r\n print to it directly (not using capture), you may cause print job\r\n corruption.\r\n\r\n Characters Per Second and Print Buffers\r\n Network Printers are created in the NET menu utility in the \"Supervise\r\n the Network\" category. When a printer is created, you can configure\r\n the performance of the printer relative to the DOS running on the same\r\n machine where the printer is attached. This is done by modifying the\r\n \"Chars per second\" parameter in conjunction with the \"Print buffer\r\n size\" parameter of the server configuration. The print buffer is an\r\n area in memory where characters are stored before being printed. The\r\n larger the print buffer size, the less often the SERVER will need to go\r\n to disk to read more characters to print. If the \"Chars per second\"\r\n value is high (relatively speaking) and the \"Print buffer size\" is\r\n large (relatively speaking) then the printer will be driven faster and\r\n the DOS running on that machine will be interrupted more often to send\r\n characters to the printer. The converse is also true if the value of\r\n \"Chars per second\" is low and \"Print buffer size\" is small. These\r\n values should also be tuned to the speed, or desired speed, of the\r\n printer. If the printer is physically a \"slow\" printer then setting\r\n the \"Chars per second\" parameter to a high number will have no effect. \r\n Additionally, if the \"Chars per second\" is set higher than the \"Print\r\n buffer size\" parameter then this will have little effect, as well.\r\n\r\n Setup Strings\r\n One of the options available on Network Printers is setup strings. You\r\n can define up to ten setup strings for each Network Printer. In short,\r\n a setup string is a series of characters that put the printer into a\r\n particular mode (i.e. landscape mode, large characters mode). By\r\n default, the DEFAULT setup string is set to nothing. The DEFAULT setup\r\n string should be set to a sequence of values which reset the printer. \r\n Many printers use the string \"1E 45\" (E) to reset the printer\r\n (check the documentation for your printer to find out what sequence\r\n resets the printer). The manual that came with the printer should\r\n describe the values that place the printer into different modes. Setup\r\n strings are always entered using hexadecimal codes.\r\n\r\n By defining more than one setup string for a Network Printer it is\r\n possible to submit jobs that will print in different printer modes. \r\n Setup strings can be used as part of the \"NET CAPTURE\" command or in\r\n the \"Print\" category of the NET menu utility. An example of its use\r\n with \"NET CAPTURE\" is provided below.\r\n\r\n Capture Settings\r\n CLIENTs can access Network Printers with the \"NET CAPTURE\" command. \r\n There are several options available with this utility. Special\r\n attention should be given to the options available with the \"NET\r\n CAPTURE\" command. They are discussed in the manual, as well as in the\r\n on-line help in the NET menu utility and on the command-line when \"NET\r\n CAPTURE HELP\" is typed. A sample command-line might look like this:\r\n\r\n NET CAPTURE LPT1 LASERJET B=N D=Y S=LANDSCAPE\r\n\r\n This means that all jobs sent to LPT1 of the local machine will be\r\n redirected to the Network Printer LASERJET. It also means that for all\r\n print jobs sent to LPT1 (LASERJET), there should be NO banner printed\r\n and each job should start printing before the job has been completely\r\n submitted (direct printing). Finally this job is printed using the\r\n LANDSCAPE setup string (created previously on printer LASERJET). The\r\n LANDSCAPE setup string values are sent to the printer just previous to\r\n the data of each print job sent to LPT1. The DEFAULT setup string\r\n values are sent to the printer after each print job is printed (thus\r\n resetting the printer for the next job sent to this printer). \r\n\r\n From the NET menu utility it is also possible to submit a print job and\r\n have the job immediately go on hold. When a print job is on hold it is\r\n placed on the queue but not printed. It can be taken off hold (and\r\n thus printed) by selecting the job from the print job list and changing\r\n the flags of the job.\r\n\r\n Postscript printing\r\n Because of the nature of postscript printers, special care must be\r\n taken when sending print jobs. You should make sure your capture has\r\n the following set:\r\n BANNER=No\r\n TABS=0\r\n FORMFEED=No\r\n You may also want to set the WAIT parameter to a value higher than 10\r\n seconds. If your print job gets split to multiple jobs when printing\r\n to a postscript printer, you will want to increase the WAIT value. \r\n Increase it until your print job comes out all in one job.\r\n\r\n Using WAIT=0\r\n The WAIT=0 should only be used if the application you are using will\r\n close the print job. If the application does not close the print job,\r\n using WAIT=0 will keep the print job open until it is closed\r\n explicitly. A print job on LPT1 can be closed manually from the DOS\r\n command-line by sending a formfeed or -L, displayed ^L (press and\r\n hold the Ctrl key while pressing the L key, then release the L key and\r\n Ctrl key). Type \"ECHO ^L > LPT1\". This sends a form feed character to\r\n LPT1 and closes the job. Generally using a WAIT value of 10 or so is\r\n adequate. CAUTION: If you use WAIT=0 and DIRECT=Y you will hold the\r\n printer until the print job is explicitly closed.\r\n\r\n Capturing Ports\r\n The documentation incorrectly states that as a CLIENT, you can capture\r\n COM1 or COM2. The COM1 and COM2 ports can only be used by a SERVER. A\r\n Network Printer can be assigned to the COM1 or COM2 port. CLIENTs can\r\n then capture LPT1, LPT2, or LPT3 to a Network Printer that has been\r\n created and assigned to COM1 or COM2.\r\n\r\n\r\n\r\n 3. Network Applications\r\n -----------------------\r\n\r\n Installation\r\n Installing applications on NetWare Lite may be different than\r\n installing applications on NetWare. NetWare is, as you know, a very\r\n popular LAN. Many applications have NetWare specific installation\r\n options. These installation options DO NOT apply to NetWare Lite\r\n networks. NetWare Lite is a DOS peer-to-peer network. If the\r\n application being installed has network specific installations then\r\n \"Other networks..\" or \"DOS Peer to peer network\" or the like, should be\r\n selected. DO NOT select NetWare or Novell installation options. See\r\n Appendix B in the documentation for more details.\r\n\r\n In general, some consideration should be given when installing\r\n applications. If the application requires configuration information at\r\n the time it is installed, then consideration should be given to which\r\n CLIENTs (machines) will use the application. For example, say\r\n application TESTAPP.EXE is being installed and it asks what kind of\r\n monitor will be used with this application. Suppose that the machine\r\n you are sitting on has a VGA screen but no other machines on the\r\n network have VGA screens. If you were to select VGA then when this\r\n application is run from across the network from an CGA screen, say, it\r\n may not function properly. We have no specific guidelines on this\r\n subject, as a general solution may not be possible. This is a general\r\n problem with configuration of applications on a network.\r\n\r\n\r\n\r\n 4. Compatibility with the NetWare Shell\r\n ---------------------------------------\r\n\r\n If your site is currently using Novell NetWare and you are installing\r\n NetWare Lite on the same LAN, then there are some guidelines that\r\n should be followed in order for both to function properly.\r\n\r\n NetWare Lite functions on a single LAN segment. In other words,\r\n NetWare Lite packets DO NOT cross Novell bridges (NetWare Lite packets\r\n do cross MAC layer bridges or repeaters, however.) In a site that has\r\n existing NetWare, each NetWare Lite network will be constrained to a\r\n single LAN segment.\r\n\r\n If there are workstations that will load both the NetWare shell and\r\n NetWare Lite software we suggest the following load order:\r\n\r\n IPX (either the IPX you had or IPXODI that came with\r\n NetWare Lite; either one but NOT both)\r\n\r\n DOS Share (SHARE.EXE, if becoming a SERVER)\r\n\r\n NetWare Lite Server (SERVER.EXE, if desired)\r\n\r\n NetWare Lite Client (CLIENT.EXE, if desired)\r\n\r\n NetWare Shell (NETx.COM)\r\n\r\n Once you have installed the CLIENT to a workstation that will also be\r\n running the NetWare Shell, you will need to modify your AUTOEXEC.BAT or\r\n appropriate batch file to load the files in the correct order. Note:\r\n with LASTDRIVE set, the NetWare Shell will map the first drive past\r\n LASTDRIVE to the SYS:LOGIN directory of the NetWare server for you to\r\n login. If LASTDRIVE is not set, DOS defaults it to E:, thus F: would\r\n be mapped to SYS:LOGIN. Also, if you use the MAP *1:= command in your\r\n login script, *1 means the first drive past LASTDRIVE. If you are\r\n dependant on certain drives being mapped with certain letters, the\r\n changing of LASTDRIVE may change which drive letters are mapped. Be\r\n aware that all drive letters, A: - Z:, can be mapped to NetWare servers\r\n (NetWare Lite can only map A: - LASTDRIVE).\r\n\r\n See Network Applications in this README file for installing network\r\n applications.\r\n\r\n\r\n\r\n 5. SERVER Optimization and Functions\r\n ------------------------------------\r\n\r\n Disk Caches\r\n NetWare Lite does not ship with a disk cache. We have tested with\r\n several (read many) commercially available disk cache products and\r\n found them to be quite inexpensive while adding significant performance\r\n to the NetWare Lite SERVER software. We suggest for higher performance\r\n of the NetWare Lite SERVER that a disk cache be acquired and installed\r\n on the SERVER machines. Some cache tuning may be necessary for best\r\n results.\r\n\r\n Server Configuration\r\n For best performance we suggest that receive buffer and read buffer\r\n sizes be increased to what is supported by the network topology (i.e.\r\n ethernet, token ring) up to a maximum of 4096 bytes using a multiple of\r\n 512 bytes. In fact, if 4096 is selected then the SERVER will truncate\r\n the value to the maximum value supported by the topology. This tuning\r\n allows CLIENTs to request more data from (or send more data to) the\r\n SERVER with each read (write) operation. When more data is sent, fewer\r\n requests are necessary and better performance is obtained. This\r\n enhancement does increase the size of the SERVER when it is resident in\r\n DOS.\r\n\r\n Depending on the \"load\" being placed on the server, it may be\r\n beneficial to increase the number of receive buffers and read buffers. \r\n In general, we have found that 8-12 receive buffers is enough for even\r\n the most heavily loaded server. Similarly, 5-10 read buffers is\r\n sufficient. These values need not be more than one or two above the\r\n number of simultaneous connections (up to our suggested maximums of 8-\r\n 12 receive buffers and 5-10 read buffers).\r\n\r\n Mapping vs. SUBSTing\r\n If your machine is a SERVER and you map to yourself, it is recommended\r\n that you SUBST to yourself instead of mapping to yourself. SUBST is a\r\n DOS command that lets you assign a drive letter to a directory on\r\n another drive. For example, if you usually map to yourself with G: to\r\n the Network Directory APPS, and if APPS is actually the C:\\APPS\r\n directory, the NET MAP G: APPS could be replaced by SUBST G: C:\\APPS. \r\n To remove this substitution, you would type SUBST G: /D. Using this\r\n substitution, rather than a mapping, will result in better performance\r\n for operations done on drive G:.\r\n\r\n Mapping Local Drive\r\n You can map drives that are local, for example A: or B:, and use them\r\n temporarily as network drives. However as a general practice, it is\r\n not recommended. If you run out of drive letters to map, increase\r\n LASTDRIVE in your CONFIG.SYS.\r\n\r\n Use of ASSIGN\r\n Do not use ASSIGN with NetWare Lite. The DOS reference manual (3.3)\r\n recommends that you use SUBST instead of ASSIGN and explains how to do\r\n so.\r\n\r\n Remove a SERVER from your hard drive\r\n If you installed the SERVER on your hard drive and no longer want it\r\n there, you can remove it by doing the following:\r\n\r\n 1) Boot your machine without loading the SERVER.\r\n\r\n 2) Run the original INSTALL.EXE that came on a floppy.\r\n\r\n 3) Select \"Make this machine a SERVER\". When asked to select the\r\n network interface card, press ESC and exit the INSTALL utility. \r\n The SERVER is now removed from your hard disk drive.\r\n\r\n Improving SERVER performance\r\n It has been found that fragmented file on the hard disk drive of a\r\n SERVER can adversely affect performance. It is suggested that you\r\n periodically unfragment the files on the hard disk drive of each\r\n SERVER. This can be done using any of a number of disk optimizing or\r\n disk compression tools available in the market place. MAKE SURE THE\r\n SERVER IS NOT RUNNING WHEN THIS TYPE OF OPERATION IS DONE!!!\r\n\r\n NEVER run any low-level disk repair utilities on the hard disk drive of\r\n the SERVER while the SERVER is loaded. This can cause corruption of\r\n data stored on the hard disk drive. This includes CHKDSK /F, disk\r\n doctor utilities, and disk optimizing utilities. Low-level utilities\r\n can only be run directly on the SERVER machine. You cannot run them\r\n from CLIENTs that have a drive mapped to the SERVER.\r\n\r\n Renaming SERVERs and Reconnection\r\n Whenever a SERVER is renamed, you should reboot that SERVER as soon as\r\n possible and have the CLIENTs that were connected to that SERVER, re-\r\n login. CLIENTs cannot reconnect to a SERVER that was renamed.\r\n\r\n Disabling the SERVER\r\n There is no way to remove the SERVER or CLIENT from memory once either\r\n is loaded. The SERVER can be disabled once loaded. Press CTRL-ALT-\r\n DEL, as if you were rebooting. When the Reboot window comes up, press\r\n 1 to disable the SERVER. This simply turns the functionality of the\r\n SERVER off, it is not removed from memory.\r\n\r\n SHARE.EXE -- Status Report 5\r\n When loading the SERVER, you may get \"Status Report 5\", which talks\r\n about SHARE.EXE not being loaded when the SERVER.EXE was run. \r\n SHARE.EXE is a program that comes with DOS 3.1 or above. If you get\r\n Status Report 5, you do not have SHARE.EXE in your PATH. Either add\r\n the appropriate directory to your PATH (where SHARE.EXE is located) or\r\n copy SHARE.EXE to the directory where NetWare Lite is installed. SHARE\r\n should be loaded before the SERVER. SHARE is the mechanism that allows\r\n files to be accessed simultaneously from multiple CLIENTs. It is not\r\n required to be loaded for the SERVER to run, though strongly suggested.\r\n SHARE.EXE should be tuned for proper behavior. You may need to\r\n increase the values for locks (/L) and files (/F) for SHARE if you run\r\n database applications, or if you have more than 4 users. Configuration\r\n of SHARE.EXE is documented with your DOS manual. The CLIENT does not\r\n need SHARE.EXE to be loaded.\r\n\r\n Workstation Time\r\n To keep time of CLIENT machines on the network synchronized we suggest\r\n that \"NET TIME \" be placed in everyone's AUTOEXEC.BAT or\r\n STARTNET.BAT file. should be a machine that keeps\r\n \"pretty good\" time. This becomes especially important if NetWare Lite\r\n is being used in a software development environment where MAKE.EXE is\r\n being used. MAKE.EXE requires strict time synchronization. If \"NET\r\n TIME\" is used then MAKE.EXE will function smoothly. Further more, the\r\n time on all SERVERs can be synchronized by using the \"Time\r\n Synchronization\" option in the \"Supervise the Network\" menu.\r\n\r\n\r\n\r\n 6. CD-ROM Support\r\n -----------------\r\n\r\n NetWare Lite does support CD-ROM drives. You can use CD-ROM drives\r\n with the SERVER and/or CLIENT. If you will be running the CLIENT on\r\n the same machine as the CD-ROM drive, you MUST load the CLIENT before\r\n loading the CD-ROM redirector (e.g. MSCDEX). You may attach a CD-ROM\r\n to a SERVER workstation and create a Network Directory that point to\r\n the CD-ROM drive. This way remote CLIENTs can access the CD-ROM.\r\n\r\n\r\n\r\n 7. Loading IPXODI\r\n -----------------\r\n\r\n In the STARTNET.BAT file that is created for you, the line \"IPXODI A\"\r\n appears. The parameter \"A\" tells IPXODI to only load IPX, this makes\r\n it so IPXODI takes up less memory. If you have an application that\r\n needs SPX to run, remove the \"A\" from this line when loading IPXODI\r\n then SPX will also be loaded. You can type \"IPXODI ?\" to see a list of\r\n all available options for IPXODI.\r\n\r\n\r\n\r\n 8. Auxiliary NetWare Lite Files\r\n -------------------------------\r\n\r\n Included with NetWare Lite are four extra programs that are not\r\n documented. These files are not needed for NetWare Lite to run, but\r\n add fun and functionality. They are: DEDICATE.COM, DEMO.EXE,\r\n NETBIOS.EXE, and NLSNIPES.EXE.\r\n\r\n DEDICATE.COM -- DEDICATE is a little program that can be run on a\r\n SERVER to improve performance. It is a useful program to be run on\r\n NetWare Lite machines that are acting as dedicated servers; or if a\r\n machine is a CLIENT/SERVER and the CLIENT is not going to be active for\r\n a while. To run DEDICATE, type DEDICATE when in the C:\\NWLITE\r\n subdirectory on the machine running SERVER.EXE.\r\n\r\n DEMO.EXE -- DEMO is a networking demonstration program that shows how\r\n workstations can communicate using shared file access. When run, a\r\n \"worm\" is shown moving around on the screens of the workstations\r\n running DEMO.EXE. As the \"worm\" covers each screen, eventually the\r\n word \"LITE\" is shown. To run DEMO, change to the same directory on the\r\n same SERVER on each machine that will be running DEMO. With DEMO.EXE\r\n in your PATH, type DEMO and press ENTER on each workstation. DEMO\r\n works best if run in a Left-to-Right fashion. That is, starting on the\r\n left-most workstation, run DEMO.EXE and move right running DEMO on each\r\n machine. The screens are \"connected\" starting left and moving right in\r\n the order which DEMO was started. Once running, you can drive your\r\n \"worm\" using the arrow key. DEMO will only support 9 workstations\r\n running simultaneously.\r\n\r\n NETBIOS.EXE -- This is the NETBIOS that is included with regular\r\n NetWare. It can be loaded any time after IPXODI is loaded. Some\r\n applications require the presence of NETBIOS. For this reason NETBIOS\r\n is provided with NetWare Lite. For more documentation on NETBIOS.EXE,\r\n contact the nearest Novell Authorized Reseller.\r\n\r\n NLSNIPES.EXE -- NLSNIPES is a game. One to five users can play at a\r\n time. Everyone that wants to play NLSNIPES must map a drive to the\r\n same Network directory on the same SERVER. To run, type NLSNIPES. You\r\n will then be asked for two initials, this uniquely identifies your\r\n \"man\" as you play. The first person to run NLSNIPES is the \"starter\". \r\n As people run NLSNIPES and enter their initials, they will see the\r\n initials of the other players that are entering the game. Once the\r\n desired group is ready, the \"starter\" will press ENTER to begin. Move\r\n your \"man\" through the maze killing snipes, generators, and other\r\n \"men\". For instructions on how to move and shoot, type \"NLSNIPES /H\"\r\n at the command-line.\r\n\r\n\r\n\r\n 9. Logging in after INSTALL\r\n ---------------------------\r\n\r\n The first time you login to a newly installed network there will be\r\n only one user defined on the network, SUPERVISOR. To login, type NET\r\n LOGIN SUPERVISOR or type NET and enter SUPERVISOR when prompted for a\r\n username.\r\n\r\n If you are installing on a network where other SERVERs are already\r\n running, the user accounts defined on the network will also be defined\r\n on SERVERs you install. You will need to consult with the\r\n administrator of the network to find out what user accounts are defined\r\n and how you may login.\r\n\r\n Note: The SUPERVISOR account on a newly installed network has no\r\n password. For security reasons it is recommended that you set a\r\n password on the SUPERVISOR account soon after installation. DO NOT\r\n FORGET THIS PASSWORD!\r\n\r\n\r\n\r\n 10. Windows 3.0 Compatibility\r\n -----------------------------\r\n\r\n This section contains information about using NetWare Lite with Windows\r\n 3.0. Follow the suggestions outlined below to operate your Windows 3.0\r\n environment.\r\n\r\n Network vs. Local installation of Windows\r\n Install Windows locally, do not attempt to install it from a Network\r\n Directory. Follow the regular installation procedures using Windows\r\n diskettes. Windows INSTALL may indicate the presence of a \"Microsoft\r\n Network (or 100% compatible)\" network, change this selection to \"No\r\n Network Installed\".\r\n\r\n Before Entering Windows\r\n It is suggested that you set up your NetWare Lite environment before\r\n running Windows. Such operations include: logging into the network,\r\n mapping drives, and capturing ports.\r\n \r\n Mapping Drives\r\n If a SERVER to which you have mapped a drive goes down, Windows will\r\n display a message indicating that the drive does not contain any files. \r\n Any attempt to access that drive will fail. Under regular DOS, this\r\n error is trapped and the CLIENT saves enough information to\r\n automatically restore the connection to that Network Directory when the\r\n downed SERVER returns to the network. Windows prevents regular DOS\r\n from trapping this error.\r\n\r\n To restore connections to your mapped drive, exit Windows and re-issue\r\n the NET MAP command when the SERVER is back on the network.\r\n\r\n Printing\r\n Use the NET CAPTURE command described in your NetWare Lite User Guide\r\n to re-direct printing from your LPT1 or LPT2 ports to a network printer\r\n before you enter Windows. Configure your printer in Windows to either\r\n the LPT1.OS2 or LPT2.OS2 ports depending on which port you captured\r\n before entering Windows.\r\n\r\n Workstations that are configured as both SERVER and CLIENT should use\r\n LPT1.OS2 or LPT2.OS2 to print from Windows. (See the note on Local\r\n Network Printers above)\r\n\r\n NetWare Lite SEND messages\r\n NetWare Lite SEND messages will only appear when you open a DOS prompt\r\n or exit Windows.\r\n\r\n\r\n\r\n 11. Documentation Errors (Errata)\r\n ---------------------------------\r\n\r\n Your manual may contain one or more of the following errors.\r\n\r\n Page 7 -- In the \"Log in to NetWare Lite\" section step 3, \"NET LOGIN\"\r\n should read \"NET LOGIN SUPERVISOR\". See section 9 above.\r\n\r\n Pages 36 and 60 -- Incorrectly state that the supervisor privileges are not\r\n required. That is not correct. Supervisor privileges are required\r\n unless you are running on your own machine.\r\n\r\n Page 106 -- Incorrectly states that COM1 and COM2 can be captured using the\r\n NET CAPTURE command. This is not true, only LPT1, LPT2, and LPT3 can\r\n be captured by a CLIENT. NOTE: Serial printers are supported at the\r\n SERVER as Network Printers.\r\n\r\n Page 107 -- Is missing the \"notify\" capture setting. You can specify the\r\n notify option using \"N=Y\" or \"NOTIFY=Y\". If set, the SERVER will send\r\n you a message when the print job is done.\r\n\r\n Page 149 -- The discussion of network configuration files is not needed. \r\n The NetWare Lite INSTALL utility generates the correct NET.CFG file\r\n from the options you select during installation. After installation,\r\n you can edit the NET.CFG file using any standard ASCII text editor.\r\n\r\n\r\n\r\n WE HOPE YOU LIKE THIS PRODUCT!\r\n\u001a" }