{ "disks": { "1": { "dirs": [ { "path": "/", "files": [ { "name": "INSTALL EXE", "size": 184694, "date": "1993-02-13", "time": "17:28" }, { "name": "LL5 EXE", "size": 268701, "date": "1993-02-12", "time": "21:03" }, { "name": "LL5 GRP", "size": 908, "date": "1993-01-28", "time": "16:55" }, { "name": "LL5 ICO", "size": 766, "date": "1993-01-28", "time": "16:55" }, { "name": "LL5 PIF", "size": 545, "date": "1993-01-28", "time": "16:55" }, { "name": "LL5 TSI", "size": 98715, "date": "1993-02-15", "time": "11:43" }, { "name": "LE EXE", "size": 35003, "date": "1993-01-28", "time": "16:55" }, { "name": "LE FON", "size": 10240, "date": "1993-01-28", "time": "16:55" }, { "name": "TSI INI", "size": 1510, "date": "1993-01-28", "time": "16:55" }, { "name": "TSI PBK", "size": 132, "date": "1993-02-13", "time": "12:59" }, { "name": "TSI PWD", "size": 106, "date": "1993-02-13", "time": "12:59" }, { "name": "TSIVID 386", "size": 9288, "date": "1993-02-07", "time": "13:19" }, { "name": "NETINFO EXE", "size": 11813, "date": "1993-02-11", "time": "16:10" }, { "name": "VCD 386", "size": 8204, "date": "1992-10-01", "time": "3:11" }, { "name": "VPD 386", "size": 9287, "date": "1992-10-01", "time": "3:11" }, { "name": "COMM DRV", "size": 9632, "date": "1992-10-01", "time": "3:11" }, { "name": "CHANGES TXT", "size": 181, "date": "1993-01-28", "time": "16:55" }, { "name": "README TXT", "size": 26299, "date": "1993-02-15", "time": "15:50" } ] } ], "volume": "LL5_1" } }, "desc_file": "README.TXT", "desc_text": " The Latest About LapLink V\r\n Version 5.0\r\n \r\nWelcome to LapLink V. If you're a new LapLink owner, be sure to\r\nmail in your registration card to ensure that you will be\r\nnotified of future releases.\r\n \r\n **************************************************************\r\n ********* *********\r\n ********* IMPORTANT! If you are using LapLink V *********\r\n ********* over a network or modem be sure to read *********\r\n ********* the first two sections of this document. *********\r\n ********* By default, connections are limited until *********\r\n ********* you make the changes they describe. *********\r\n ********* *********\r\n **************************************************************\r\n \r\n -CONTENTS-\r\n \r\n I. You MUST change Security to Allow Incoming Connections\r\n II. Important Notes for Network Users\r\n A. To use Network Connections You MUST Enable Them First\r\n B. Checking for Windows 3.1 or Windows for Workgroups\r\n Compatibility\r\n C. The Xircom Pocket Ethernet Adapter\r\n III. Quitting LapLink if It \"Freezes\"\r\n IV. Remote Install and TSRs\r\n V. More Windows 3.1 Notes\r\n A. Multiple LapLink V Windows\r\n B. Non-standard Port IRQs\r\n C. RangeLAN\r\n VI. More Information About Security\r\n A. Using SUBST to Secure Lower-Level Directories\r\n B. When Security Creates Read-Only Files\r\n C. Sharing Address Book (or Security) Files\r\n VII. Starting LapLink V with Command Line Switches\r\nVIII. Using LapLink V with OS/2 2.0\r\n A. DOS Session Settings\r\n B. Making Peer-to-Peer NetWare Connections\r\n C. Changing CONFIG.SYS for Serial Cable Connections\r\n IX. Computer Names, Passwords, and User Names\r\n X. The Xircom Parallel Port Multiplexor\r\n XI. Using LapLink V with Other Traveling Software Products\r\n XII. Getting Technical Support\r\nXIII. Making Suggestions to Improve LapLink V\r\n \r\n-----------------------------------------------------------------\r\nI. You MUST change Security to Allow Incoming Connections\r\n \r\nWith the capabilities of this release, ANY modem or network user\r\nmay connect to your PC. For that reason, the LapLink security\r\nsystem is now enhanced.\r\n \r\nBy default, the security system is set to allow cable connections\r\nonly. You can make OUTGOING connections to modem or network\r\nusers, but you must change the default before other modem or\r\nnetwork users can make INCOMING connections to your PC.\r\n \r\nTo change the default, use the Security Setup command on the\r\nConnections menu:\r\n \r\n-If you don't want to use security at all, choose the Anyone\r\n option and then the OK button. CAUTION: If you have enabled the\r\n network or modem port, any user will then have FULL ACCESS to\r\n any file on your PC, without supplying a password at all.\r\n \r\n-If you want a one-password/unlimited access solution, as was\r\n present in LapLink Pro, choose the User List Only option. On the\r\n next dialog, leave the User Name field set to Default User, and\r\n type a password in the Password field. Then, highlight all your\r\n disks and choose the Entire Drive button. CAUTION: With this\r\n setup, any user that provides the password will have FULL ACCESS\r\n to any file on your PC.\r\n \r\n-If you want to take full advantage of the new security features,\r\n follow the instructions on pages 106-113 of the LapLink V User's\r\n guide. The suggested procedure calls for you to provide very\r\n limited access to the default user and grant less restrictive\r\n access to specifically named users. With this setup, users that\r\n connect and are not in your list will only have access to the\r\n files defined for the default user. Users that are in your list\r\n may have greater rights.\r\n \r\n-----------------------------------------------------------------\r\nII. Important Notes for Network Users\r\n \r\nA. To use Network Connections You MUST Enable Them First\r\n \r\nWhen you first install LapLink V, you can make neither OUTGOING\r\nnor INCOMING network connections. (This default provides an extra\r\nmeasure of security for your files and also lets network\r\nadministrators control the amount of data transferred over the\r\nnetwork, if they desire.)\r\n \r\n-To allow network connections, choose the Port/Modem Setup\r\n command from the Options menu. Choose the Network button to\r\n change the state to Enabled. Then choose Done.\r\n \r\nThis allows you to make OUTGOING connections immediately. To\r\nallow INCOMING connections, be sure to change Security Setup as\r\ndescribed in the previous section.\r\n \r\nNOTE: Enabling network connections has a very minor impact on\r\nnetwork traffic. When files are transferred, no disk space is\r\nused on the server, only the disks on the connected workstations\r\nare affected.\r\n \r\nB. Checking for Windows 3.1 or Windows for Workgroups\r\n Compatibility\r\n \r\nOutside of Windows (directly from DOS) any attached network\r\nworkstation can make peer-to-peer network connections if the\r\nnetwork is running Novell NetWare versions 2.2 or 3.11.\r\n \r\nIf LapLink \"locks up\" after you start it in Windows 3.1 or\r\nWindows for Workgroups, however, you'll need to check the Windows\r\nnetwork configuration. You can use a tool provided with LapLink V\r\nto check:\r\n \r\nFirst, start the network from DOS and log on to the network.\r\nThen, from your LapLink directory type the following command:\r\n \r\n NETINFO [windows path]\r\n \r\nFor example, if Windows is installed in C:\\WINDOWS, type:\r\n \r\n NETINFO C:\\WINDOWS\r\n \r\n-If Windows is set up correctly, you will see a message like:\r\n \r\n Netware Shell Version-> 3.26 OK\r\n IPX/SPX Version -> 1.20 OK\r\n \r\n NETWARE.DRV -> Found\r\n *VNETBIOS -> Found\r\n VNETWARE.386 -> Found\r\n VIPX.386 -> Found\r\n \r\n Your Network drivers are current.\r\n Your SYSTEM.INI file specifies the necessary drivers to\r\n support LapLink peer-to-peer connections.\r\n \r\n-If the message reports that your network drivers are not\r\n current, or that SYSTEM.INI does not specify the necessary\r\n drivers, you should re-run the Windows or Windows for Workgroups\r\n Setup program. If you specify Novell for the type of\r\n network, the correct drivers and changes should be made\r\n automatically. (You may need your Windows or Windows for\r\n Workgroups installation disks when you run Windows setup.)\r\n \r\n NETINFO checks the following information: \r\n \r\n 1. The following network drivers must be in memory:\r\n \r\n NETX.COM version 3.26\r\n IPX.COM version 3.10 \r\n (IPX.COM may be replaced with LSL.COM version 1.20 and\r\n IPXODI.COM version 1.20). \r\n \r\n 2. SYSTEM.INI must contain the following lines:\r\n \r\n ----WINDOWS 3.1----\r\n Under the [boot] section header:\r\n network.drv=netware.drv\r\n Under the [386Enh] section header:\r\n network=*vnetbios,vnetware.386,vipx.386\r\n \r\n ----WINDOWS FOR WORKGROUPS----\r\n Under the [boot] section header:\r\n network.drv=wfwnet.drv\r\n secondnet.drv=netware.drv\r\n Under the [boot.description] section header:\r\n network.drv=Microsoft Windows for Workgroups \r\n (version 3.1)\r\n Under the [386Enh] section header:\r\n network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,\r\n vbrowse.386,vwc.386\r\n secondnet=*vnetbios,vnetware.386,vipx.386\r\n \r\nC. The Xircom Pocket Ethernet Adapter\r\n \r\nIn order to make a network connection under Windows with this\r\ndevice, you must have the latest Xircom NetWare drivers.\r\n \r\nFor PE2ODI.COM the version should be 1.44, dated 10/30/92 (NOT\r\nversion 1.27, dated 6/4/92). For the PE2IPX.COM the version\r\nshould be 1.44, dated 10/30/92 (NOT version 1.27, dated 6/7/92).\r\nContact Xircom for the latest drivers.\r\n \r\nNOTE: To make a network connection over a parallel port with the\r\nXircom adapter, you should DISABLE the parallel port to which the\r\nadapter is connected. For example, if the adapter is attached to\r\nLPT1, use the Port/Modem Setup command to disable LPT1. Disabling\r\nprevents LapLink from trying to use the port for cable\r\nconnections.\r\n \r\n-----------------------------------------------------------------\r\nIII. Quitting LapLink if It \"Freezes\"\r\n \r\nIf LapLink V will not respond to your keystrokes, it may be in a\r\n\"timed-out\" state. If LapLink appears frozen, press [Ctrl+Break].\r\nLapLink will exit. If you changed any options however, the\r\nchanges will be lost.\r\n \r\n-----------------------------------------------------------------\r\nIV. Remote Install and TSRs\r\n \r\nIf you experience problems with remote install, check the remote\r\nPC for installed TSRs (memory-resident programs). Some PCs will\r\nnot accept a remote install if certain TSRs are in memory.\r\n \r\nTSRs that are known to cause problems include DOSKEY (available\r\nwith DOS 5.0 and above) and SHARE. NDOS which replaces DOS's\r\nCOMMAND.COM is also known to prevent remote installs when\r\ninstalled on the remote PC.\r\n \r\nTo uninstall a TSR, you'll usually need to reboot the PC. First\r\ncheck the AUTOEXEC.BAT file. If there is a line that starts the\r\nTSR, edit AUTOEXEC.BAT and place a \"REM\" at the beginning of the\r\nline. For example, if there is a DOSKEY line in your AUTOEXEC.BAT\r\nfile, change it to:\r\n \r\n REM DOSKEY\r\n \r\nThen, reboot the PC. Try running remote install again. You can\r\nadd the TSR back later by removing the REM.\r\n \r\nTo start the remote PC without NDOS, use a DOS boot disk to boot\r\nthe PC. After the remote install is complete you can reboot the\r\nPC normally.\r\n \r\n-----------------------------------------------------------------\r\nV. More Windows 3.1 Notes\r\n \r\nA. Multiple LapLink V Windows\r\n \r\nWe do not recommend opening more than one instance of LapLink V\r\nduring a given Windows session. This can cause particular\r\nproblems if LapLink is enabled for network peer-to-peer\r\ntransfers. \r\n \r\nB. Non-standard Port IRQs\r\n \r\nIf some of your serial ports use non-standard IRQs (this is\r\ncommon if you are using a PS/2 with COM3 and COM4) you may have\r\nto edit your SYSTEM.INI file to allow the use of the port with\r\nthe non-standard IRQ.\r\n \r\nIf you have problems communicating over a serial port using IRQ\r\n2, check your SYSTEM.INI file for a line in the [386Enh] section\r\nthat reads:\r\n \r\n COMxIRQ=2 \r\n \r\n and change the IRQ to 9. For example:\r\n \r\n COMxIRQ=9\r\n \r\nC. RangeLAN and Windows 3.1\r\n \r\nLapLink V will not function if you are using a RangeLAN network\r\nconnector and Windows 3.1. With RangeLAN LapLink V may only be\r\nrun directly from DOS. \r\n \r\n-----------------------------------------------------------------\r\nVI. More Information About Security\r\n \r\nA. Using SUBST to Secure Lower-Level Directories\r\n \r\nThe LapLink V security system lets you permit or deny access to\r\nany directory located immediately in the root of your drives. If\r\nyou need finer-grained security, you can make use of the DOS\r\nSUBST (substitute) command.\r\n \r\nSUBST lets you assign a drive letter to a given path. For\r\nexample, suppose your hard disk has this partial structure:\r\n \r\n C:\\- \r\n |\r\n --DATA\\-\r\n |\r\n --SALES\\\r\n |\r\n --GOALS\\\r\n \r\n\r\nIf you use this SUBST command:\r\n \r\n\r\n SUBST G: C:\\DATA\r\n \r\nThen DOS will treat C:\\DATA like it is a drive named G:. You can\r\nthen deny access to C:\\DATA but allow access to the G:\\SALES or\r\nG:\\GOALS directories individually because they are immediately at\r\nthe root of G:\r\n \r\nIf you want to use SUBST for security, you should include the\r\nSUBST command in your AUTOEXEC.BAT file so that the \"substituted\"\r\ndrive is available anytime you start LapLink V. For more\r\ninformation about the SUBST command, see your DOS manual.\r\n \r\nB. When Security Creates Read-Only Files\r\n \r\nIf you assign read-only access to a drive or directory, then a\r\nremote user will see the files in the drive or directory as\r\nread-only. If the user then copies the files, they will arrive at\r\nhis or her PC marked as read-only. \r\n \r\nIN ORDER TO EDIT THE FILE THE USER WILL HAVE TO CHANGE THE\r\nREAD-ONLY ATTRIBUTE OF THE FILE. To change the attribute, use the\r\nDOS ATTRIB command.\r\n \r\nFor example, if a directory contains a number of read-only files,\r\nthey can all be edited (given read/write access) if the following\r\ncommand is issued:\r\n \r\n ATTRIB -R *.*\r\n \r\nFor more information about ATTRIB, see your DOS manual.\r\n \r\nC. Sharing Address Book (or Security) Files\r\n \r\nWe do not recommend exchanging your Address Book (TSI.PBK) or\r\nSecurity List (TSI.PWD) files with other users. If another user\r\nmust use your Address Book, however, you should use the Local\r\nPassword command and remove the extra security provided by the\r\ncommand.\r\n \r\nChoose Local Password and un-check the file you want to exchange.\r\nThe other user should also remove this protection. Then, copy\r\nTSI.PBK to the remote user. Once the user has successfully viewed\r\nthe Address Book, he or she can reinstate Local Password\r\nprotection.\r\n \r\nIf you copy your Address Book to another user with the Local\r\nPassword enabled, the user will have to provide the Local\r\nPassword you designated on your PC before he or she can use the\r\nAddress Book.\r\n \r\n-----------------------------------------------------------------\r\nVII. Starting LapLink V with Command Line Switches\r\n \r\nYou can start LapLink V with the following command line switches:\r\n \r\nLL5 /p[path] Tells LapLink where to look for its support\r\n files. Most useful if LapLink V is on a\r\n read-only disk.\r\n \r\nLL5 /43 or Tells LapLink to use more lines on your\r\nLL5 /50 display. If your monitor is EGA, 43 lines are\r\n displayed; VGA monitors display 50.\r\n \r\nLL5 /s Starts LapLink in the short menu mode. During\r\n the session, long menus cannot be turned back\r\n on.\r\n \r\nLL5 /g If you can start LapLink V but the screen\r\n appears blank, /g may allow you to see\r\n the LapLink screen. This will force LapLink\r\n to the non-graphic (no icon) mode.\r\n \r\nLL5 recording Starts LapLink and causes LapLink to run the\r\n named recording. The recording file must be\r\n located in the LapLink directory.\r\n \r\n-----------------------------------------------------------------\r\nVIII. Using LapLink V with OS/2 2.0\r\n \r\nTo install LapLink V for OS/2, run the LapLink Install program\r\ndirectly from DOS (not in an OS/2 DOS window). Start LapLink\r\ndirectly from DOS and use the Port/Modem Setup command to make\r\nsure the ports you want to use are enabled.\r\n \r\nWith the default OS/2 configuration you will then be able to use\r\nparallel and modem connections in the foreground. If you make\r\nthe changes described in section A (below), modem connections\r\nwill be improved and you'll also be able to transfer files in \r\nthe background.\r\n \r\nNOTE: Under OS/2 modem speeds are limited to 9600.\r\n \r\nTo make peer-to-peer network connections, read section B. If\r\nyou want to make serial cable connections read section C.\r\n \r\nA. DOS Session Settings\r\n \r\nIn order for LapLink V to function correctly in a DOS session or\r\nwindow, you must change the DOS session settings:\r\n \r\n1. Open the OS/2 System folder. Then open the Command Prompts\r\n folder.\r\n \r\n2. Right-click either the DOS Window or DOS Full Screen icon.\r\n \r\n3. Open the Settings notebook, select the Session tab, and choose\r\n the DOS Settings button.\r\n \r\n4. Change or ensure the following settings:\r\n \r\n COM_HOLD on\r\n DOS_BACKGROUND_EXECUTION on\r\n DOS_BREAK on\r\n DOS_HIGH on\r\n HW_TIMER on\r\n IDLE_SENSITIVITY 100\r\n VIPX_ENABLED on (This is for network connections only and\r\n will only be available if you make the\r\n changes in section B., below.)\r\n \r\nYou should then be able to open a DOS Window or Full Screen\r\nsession and make serial, parallel, and modem connections. For\r\nnetwork connections, read the instructions below.\r\n \r\nB. Making Peer-to-Peer NetWare Connections\r\n \r\nIn order to make a NetWare connection, the OS/2 NetWare Requestor\r\nmust be installed for OS/2. In addition you must open a DOS box\r\nand start the DOS NetWare drivers. You must also change the OS/2\r\nCONFIG.SYS file.\r\n \r\n-Editing the OS/2 CONFIG.SYS file\r\n \r\nOpen CONFIG.SYS and check for a line that reads:\r\n \r\n DEVICE=VIPX.SYS or REM DEVICE=VIPX.SYS\r\n \r\nIf the line has the \"REM\" at the beginning, delete it so it looks\r\nlike:\r\n \r\n DEVICE=VIPX.SYS\r\n \r\nYou'll then need to restart your PC.\r\n \r\n-Starting the NetWare Drivers\r\n \r\nFirst, log on to the network using your usual OS/2 procedures.\r\n \r\nNext, you'll need to obtain the DOS NetWare drivers from your\r\nsystem administrator. Then open a DOS box and start the drivers\r\nin order. \r\n \r\nFor example:\r\n \r\n LSL.COM <--- NetWare Link Support Layer\r\n XXXXXX.COM <--- A specific driver for your network card\r\n NETX.COM <--- NetWare Workstation Shell \r\n \r\nNOTE: You do not need to start IPXODI.COM. Under OS/2 that\r\nfunctionality is provided by VIPX.SYS.\r\n \r\nAfter you start the drivers, you should then be able to start\r\nLapLink V and make network connections. You might wish to create\r\na DOS batch file that starts the drivers and then LapLink V.\r\n \r\nC. Changing CONFIG.SYS for Serial Cable Connections\r\n \r\nTo make serial cable connections under OS/2, edit the OS/2\r\nCONFIG.SYS file. However, making this change may prevent \r\nstable modem connections.\r\n\r\nIf you want to use serial cables, find the line that reads:\r\n \r\n DEVICE=[path]\\VCOM.SYS\r\n \r\nand disable it by adding \"REM\" before the line so that it reads:\r\n \r\n REM DEVICE=[path]\\VCOM.SYS\r\n \r\nYou will need to restart OS/2.\r\n \r\nNOTE: For the most consistent serial cable performance, use the\r\nLapLink V Port/Modem Setup command and set the serial port to\r\n\"Polled.\"\r\n \r\n-----------------------------------------------------------------\r\nIX. Computer Names, Passwords, and User Names\r\n \r\nWe do not recommend using high-order ASCII characters in computer\r\nnames, passwords, or user names. When stored by LapLink,\r\ncharacters are converted to upper-case which may not correspond\r\nto the lower-case letters. This is especially a problem with\r\npasswords which are not displayed on your screen.\r\n \r\n-----------------------------------------------------------------\r\nX. The Xircom Parallel Port Multiplexor\r\n \r\nLapLink V has been designed to work with parallel ports that have\r\na Xircom Parallel Port Multiplexor. However, the system must\r\nfirst be set up properly.\r\n \r\nFirst, do NOT use the port-switching software that comes with the\r\nmultiplexor. (LapLink V contains code that causes the multiplexor\r\nto automatically switch ports, so the port-switching software is\r\nunnecessary. Not using the switching software has the additional\r\nbenefit of freeing more memory for your applications.)\r\n \r\nSecond, the LapLink parallel cable must be attached to the \"A\"\r\nport of the multiplexor. The printer cable should be attached to\r\n\"B.\"\r\n \r\nThird, you must make a change using the \"Port/Modem Setup\"\r\ncommand (Options menu):\r\n \r\nChoose the command, and in the Port/Modem Setup dialog, select\r\nthe parallel port with the multiplexor. In the next dialog place\r\nan x in the Force Standard (4-bit) mode check box and choose\r\n. If you do not make this change, the Multiplexor may try to\r\nswitch between the printer and the cable during the middle of a\r\ncopy.\r\n \r\nNOTE: There is one case where a connection involving a Xircom\r\nparallel port multiplexor does not work: The PC with the\r\nmultiplexor is running LapLink V from DOS. It is connecting via\r\nparallel cable to a PC running LapLink V from Windows, and the PC\r\nwith Windows has installed the LapLink V enhanced port drivers.\r\nTo allow these two PCs to connect, either start Windows on the PC\r\nwith the multiplexor and then start LapLink. Or quit Windows on\r\nthe PC without the multiplexor and then start LapLink.\r\n \r\n-----------------------------------------------------------------\r\nXI. USING LAPLINK V WITH OTHER TRAVELING SOFTWARE PRODUCTS\r\n \r\nLapLink V is not compatible with LapLink Pro and you cannot\r\nconnect to another PC running LapLink Pro.\r\n \r\nBecause WinConnect, DeskLink, and the LapLink III Device Driver\r\ncompete with LapLink V for port usage, using them with LapLink V\r\nmay require experimentation. In most cases, you need to delete\r\nthe LapLink V configuration file (TSI.INI), start the other\r\nprogram, and then start LapLink V. This causes LapLink V to\r\nre-check all available ports and it then only uses the ports that\r\nare not currently in use by the other program. (Note: When you\r\ndelete TSI.INI many options are returned to their default\r\nvalues.) If you need help with this procedure, call Traveling\r\nSoftware Technical Support.\r\n \r\nBattery Watch Pro is compatible with LapLink V, but as with other\r\nTSRs, you should avoid popping up the Battery Watch screen during\r\na file transfer.\r\n \r\n-----------------------------------------------------------------\r\nXII. GETTING TECHNICAL SUPPORT IN THE U.S.\r\n \r\nIf you have a question or need Technical Support, check the\r\nnumbers in your user manual. \r\n \r\nIf you want to contact the TSI Technical Support bulletin board,\r\nset your modem to dial (206) 485-1736. Use the following settings\r\nfor your communications program:\r\n \r\nBaud rate 2400 or 9600\r\nParity None\r\nData bits 8\r\nStop bits 1\r\n-----------------------------------------------------------------\r\nXIII. MAKING SUGGESTIONS TO IMPROVE LAPLINK V\r\n \r\nTraveling Software is constantly looking for ways to improve its\r\nproducts. Over the years, our customers have been the ones who\r\nhave provided some of the best product improvement suggestions.\r\n \r\nWe encourage you to send us your comments, criticisms, and ideas.\r\nWe will try to implement your requests in future versions.\r\n \r\nYou may address your comments to:\r\n \r\n Traveling Software, Inc.\r\n LapLink V Suggestions\r\n 18702 North Creek Parkway\r\n Bothell, WA 98011\r\n \r\n \r\nCompiled February 15, 1993" }