The Devil's Doorknob BBS Capture (1996-2003)/devilsdoorknobbbscapture1996-2003.iso/Dloads/OTHERUTI/LAPLINK.ZIP/README.TXT

Text File | 1993-02-15 | 26KB | 574 lines

                   The Latest About LapLink V
                          Version 5.0

Welcome to LapLink V. If you're a new LapLink owner, be sure to
mail in your registration card to ensure that you will be
notified of future releases.

   **************************************************************
   *********                                            *********
   *********  IMPORTANT! If you are using LapLink V     *********
   *********  over a network or modem be sure to read   *********
   *********  the first two sections of this document.  *********
   *********  By default, connections are limited until *********
   *********  you make the changes they describe.       *********
   *********                                            *********
   **************************************************************

                          -CONTENTS-

   I. You MUST change Security to Allow Incoming Connections
  II. Important Notes for Network Users
      A. To use Network Connections You MUST Enable Them First
      B. Checking for Windows 3.1 or Windows for Workgroups
         Compatibility
      C. The Xircom Pocket Ethernet Adapter
 III. Quitting LapLink if It "Freezes"
  IV. Remote Install and TSRs
   V. More Windows 3.1 Notes
      A. Multiple LapLink V Windows
      B. Non-standard Port IRQs
      C. RangeLAN
  VI. More Information About Security
      A. Using SUBST to Secure Lower-Level Directories
      B. When Security Creates Read-Only Files
      C. Sharing Address Book (or Security) Files
 VII. Starting LapLink V with Command Line Switches
VIII. Using LapLink V with OS/2 2.0
      A. DOS Session Settings
      B. Making Peer-to-Peer NetWare Connections
      C. Changing CONFIG.SYS for Serial Cable Connections
  IX. Computer Names, Passwords, and User Names
   X. The Xircom Parallel Port Multiplexor
  XI. Using LapLink V with Other Traveling Software Products
 XII. Getting Technical Support
XIII. Making Suggestions to Improve LapLink V

-----------------------------------------------------------------
I. You MUST change Security to Allow Incoming Connections

With the capabilities of this release, ANY modem or network user
may connect to your PC. For that reason, the LapLink security
system is now enhanced.

By default, the security system is set to allow cable connections
only. You can make OUTGOING connections to modem or network
users, but you must change the default before other modem or
network users can make INCOMING connections to your PC.

To change the default, use the Security Setup command on the
Connections menu:

-If you don't want to use security at all, choose the Anyone
 option and then the OK button. CAUTION: If you have enabled the
 network or modem port, any user will then have FULL ACCESS to
 any file on your PC, without supplying a password at all.

-If you want a one-password/unlimited access solution, as was
 present in LapLink Pro, choose the User List Only option. On the
 next dialog, leave the User Name field set to Default User, and
 type a password in the Password field. Then, highlight all your
 disks and choose the Entire Drive button. CAUTION: With this
 setup, any user that provides the password will have FULL ACCESS
 to any file on your PC.

-If you want to take full advantage of the new security features,
 follow the instructions on pages 106-113 of the LapLink V User's
 guide. The suggested procedure calls for you to provide very
 limited access to the default user and grant less restrictive
 access to specifically named users. With this setup, users that
 connect and are not in your list will only have access to the
 files defined for the default user. Users that are in your list
 may have greater rights.

-----------------------------------------------------------------
II. Important Notes for Network Users

A. To use Network Connections You MUST Enable Them First

When you first install LapLink V, you can make neither OUTGOING
nor INCOMING network connections. (This default provides an extra
measure of security for your files and also lets network
administrators control the amount of data transferred over the
network, if they desire.)

-To allow network connections, choose the Port/Modem Setup
 command from the Options menu. Choose the Network button to
 change the state to Enabled. Then choose Done.

This allows you to make OUTGOING connections immediately. To
allow INCOMING connections, be sure to change Security Setup as
described in the previous section.

NOTE: Enabling network connections has a very minor impact on
network traffic. When files are transferred, no disk space is
used on the server, only the disks on the connected workstations
are affected.

B. Checking for Windows 3.1 or Windows for Workgroups
   Compatibility

Outside of Windows (directly from DOS) any attached network
workstation can make peer-to-peer network connections if the
network is running Novell NetWare versions 2.2 or 3.11.

If LapLink "locks up" after you start it in Windows 3.1 or
Windows for Workgroups, however, you'll need to check the Windows
network configuration. You can use a tool provided with LapLink V
to check:

First, start the network from DOS and log on to the network.
Then, from your LapLink directory type the following command:

     NETINFO [windows path]

For example, if Windows is installed in C:\WINDOWS, type:

     NETINFO C:\WINDOWS

-If Windows is set up correctly, you will see a message like:

    Netware Shell Version-> 3.26         OK
    IPX/SPX Version      -> 1.20         OK

    NETWARE.DRV          -> Found
    *VNETBIOS            -> Found
    VNETWARE.386         -> Found
    VIPX.386             -> Found

    Your Network drivers are current.
    Your SYSTEM.INI file specifies the necessary drivers to
    support LapLink peer-to-peer connections.

-If the message reports that your network drivers are not
 current, or that SYSTEM.INI does not specify the necessary
 drivers, you should re-run the Windows or Windows for Workgroups
 Setup program. If you specify Novell for the type of
 network, the correct drivers and changes should be made
 automatically. (You may need your Windows or Windows for
 Workgroups installation disks when you run Windows setup.)

 NETINFO checks the following information:

 1. The following network drivers must be in memory:

    NETX.COM version 3.26
    IPX.COM version 3.10
    (IPX.COM may be replaced with LSL.COM version 1.20 and
     IPXODI.COM version 1.20).

 2. SYSTEM.INI must contain the following lines:

    ----WINDOWS 3.1----
     Under the [boot] section header:
        network.drv=netware.drv
     Under the [386Enh] section header:
        network=*vnetbios,vnetware.386,vipx.386

   ----WINDOWS FOR WORKGROUPS----
     Under the [boot] section header:
        network.drv=wfwnet.drv
        secondnet.drv=netware.drv
     Under the [boot.description] section header:
        network.drv=Microsoft Windows for Workgroups
        (version 3.1)
     Under the [386Enh] section header:
        network=vnetbios.386,vnetsup.386,vredir.386,vserver.386,
        vbrowse.386,vwc.386
        secondnet=*vnetbios,vnetware.386,vipx.386

C. The Xircom Pocket Ethernet Adapter

In order to make a network connection under Windows with this
device, you must have the latest Xircom NetWare drivers.

For PE2ODI.COM the version should be 1.44, dated 10/30/92 (NOT
version 1.27, dated 6/4/92). For the PE2IPX.COM the version
should be 1.44, dated 10/30/92 (NOT version 1.27, dated 6/7/92).
Contact Xircom for the latest drivers.

NOTE: To make a network connection over a parallel port with the
Xircom adapter, you should DISABLE the parallel port to which the
adapter is connected. For example, if the adapter is attached to
LPT1, use the Port/Modem Setup command to disable LPT1. Disabling
prevents LapLink from trying to use the port for cable
connections.

-----------------------------------------------------------------
III. Quitting LapLink if It "Freezes"

If LapLink V will not respond to your keystrokes, it may be in a
"timed-out" state. If LapLink appears frozen, press [Ctrl+Break].
LapLink will exit. If you changed any options however, the
changes will be lost.

-----------------------------------------------------------------
IV. Remote Install and TSRs

If you experience problems with remote install, check the remote
PC for installed TSRs (memory-resident programs). Some PCs will
not accept a remote install if certain TSRs are in memory.

TSRs that are known to cause problems include DOSKEY (available
with DOS 5.0 and above) and SHARE. NDOS which replaces DOS's
COMMAND.COM is also known to prevent remote installs when
installed on the remote PC.

To uninstall a TSR, you'll usually need to reboot the PC. First
check the AUTOEXEC.BAT file. If there is a line that starts the
TSR, edit AUTOEXEC.BAT and place a "REM" at the beginning of the
line. For example, if there is a DOSKEY line in your AUTOEXEC.BAT
file, change it to:

     REM DOSKEY

Then, reboot the PC. Try running remote install again. You can
add the TSR back later by removing the REM.

To start the remote PC without NDOS, use a DOS boot disk to boot
the PC. After the remote install is complete you can reboot the
PC normally.

-----------------------------------------------------------------
V. More Windows 3.1 Notes

A. Multiple LapLink V Windows

We do not recommend opening more than one instance of LapLink V
during a given Windows session. This can cause particular
problems if LapLink is enabled for network peer-to-peer
transfers.

B. Non-standard Port IRQs

If some of your serial ports use non-standard IRQs (this is
common if you are using a PS/2 with COM3 and COM4) you may have
to edit your SYSTEM.INI file to allow the use of the port with
the non-standard IRQ.

If you have problems communicating over a serial port using IRQ
2, check your SYSTEM.INI file for a line in the [386Enh] section
that reads:

   COMxIRQ=2

   and change the IRQ to 9. For example:

   COMxIRQ=9

C. RangeLAN and Windows 3.1

LapLink V will not function if you are using a RangeLAN network
connector and Windows 3.1. With RangeLAN LapLink V may only be
run directly from DOS.

-----------------------------------------------------------------
VI. More Information About Security

A. Using SUBST to Secure Lower-Level Directories

The LapLink V security system lets you permit or deny access to
any directory located immediately in the root of your drives. If
you need finer-grained security, you can make use of the DOS
SUBST (substitute) command.

SUBST lets you assign a drive letter to a given path. For
example, suppose your hard disk has this partial structure:

    C:\-
        |
        --DATA\-
                |
                --SALES\
                |
                --GOALS\


If you use this SUBST command:


     SUBST G: C:\DATA

Then DOS will treat C:\DATA like it is a drive named G:. You can
then deny access to C:\DATA but allow access to the G:\SALES or
G:\GOALS directories individually because they are immediately at
the root of G:

If you want to use SUBST for security, you should include the
SUBST command in your AUTOEXEC.BAT file so that the "substituted"
drive is available anytime you start LapLink V. For more
information about the SUBST command, see your DOS manual.

B. When Security Creates Read-Only Files

If you assign read-only access to a drive or directory, then a
remote user will see the files in the drive or directory as
read-only. If the user then copies the files, they will arrive at
his or her PC marked as read-only.

IN ORDER TO EDIT THE FILE THE USER WILL HAVE TO CHANGE THE
READ-ONLY ATTRIBUTE OF THE FILE. To change the attribute, use the
DOS ATTRIB command.

For example, if a directory contains a number of read-only files,
they can all be edited (given read/write access) if the following
command is issued:

   ATTRIB -R *.*

For more information about ATTRIB, see your DOS manual.

C. Sharing Address Book (or Security) Files

We do not recommend exchanging your Address Book (TSI.PBK) or
Security List (TSI.PWD) files with other users. If another user
must use your Address Book, however, you should use the Local
Password command and remove the extra security provided by the
command.

Choose Local Password and un-check the file you want to exchange.
The other user should also remove this protection. Then, copy
TSI.PBK to the remote user. Once the user has successfully viewed
the Address Book, he or she can reinstate Local Password
protection.

If you copy your Address Book to another user with the Local
Password enabled, the user will have to provide the Local
Password you designated on your PC before he or she can use the
Address Book.

-----------------------------------------------------------------
VII. Starting LapLink V with Command Line Switches

You can start LapLink V with the following command line switches:

LL5 /p[path]        Tells LapLink where to look for its support
                    files. Most useful if LapLink V is on a
                    read-only disk.

LL5 /43 or          Tells LapLink to use more lines on your
LL5 /50             display. If your monitor is EGA, 43 lines are
                    displayed; VGA monitors display 50.

LL5 /s              Starts LapLink in the short menu mode. During
                    the session, long menus cannot be turned back
                    on.

LL5 /g              If you can start LapLink V but the screen
                    appears blank, /g may allow you to see
                    the LapLink screen. This will force LapLink
                    to the non-graphic (no icon) mode.

LL5 recording       Starts LapLink and causes LapLink to run the
                    named recording. The recording file must be
                    located in the LapLink directory.

-----------------------------------------------------------------
VIII. Using LapLink V with OS/2 2.0

To install LapLink V for OS/2, run the LapLink Install program
directly from DOS (not in an OS/2 DOS window). Start LapLink
directly from DOS and use the Port/Modem Setup command to make
sure the ports you want to use are enabled.

With the default OS/2 configuration you will then be able to use
parallel and modem connections in the foreground. If you make
the changes described in section A (below), modem connections
will be improved and you'll also be able to transfer files in
the background.

NOTE: Under OS/2 modem speeds are limited to 9600.

To make peer-to-peer network connections, read section B. If
you want to make serial cable connections read section C.

A. DOS Session Settings

In order for LapLink V to function correctly in a DOS session or
window, you must change the DOS session settings:

1. Open the OS/2 System folder. Then open the Command Prompts
   folder.

2. Right-click either the DOS Window or DOS Full Screen icon.

3. Open the Settings notebook, select the Session tab, and choose
   the DOS Settings button.

4. Change or ensure the following settings:

   COM_HOLD   on
   DOS_BACKGROUND_EXECUTION   on
   DOS_BREAK   on
   DOS_HIGH   on
   HW_TIMER   on
   IDLE_SENSITIVITY   100
   VIPX_ENABLED   on    (This is for network connections only and
                         will only be available if you make the
                         changes in section B., below.)

You should then be able to open a DOS Window or Full Screen
session and make serial, parallel, and modem connections. For
network connections, read the instructions below.

B. Making Peer-to-Peer NetWare Connections

In order to make a NetWare connection, the OS/2 NetWare Requestor
must be installed for OS/2. In addition you must open a DOS box
and start the DOS NetWare drivers. You must also change the OS/2
CONFIG.SYS file.

-Editing the OS/2 CONFIG.SYS file

Open CONFIG.SYS and check for a line that reads:

    DEVICE=VIPX.SYS        or      REM DEVICE=VIPX.SYS

If the line has the "REM" at the beginning, delete it so it looks
like:

    DEVICE=VIPX.SYS

You'll then need to restart your PC.

-Starting the NetWare Drivers

First, log on to the network using your usual OS/2 procedures.

Next, you'll need to obtain the DOS NetWare drivers from your
system administrator.  Then open a DOS box and start the drivers
in order.

For example:

    LSL.COM     <--- NetWare Link Support Layer
    XXXXXX.COM  <--- A specific driver for your network card
    NETX.COM    <--- NetWare Workstation Shell

NOTE: You do not need to start IPXODI.COM. Under OS/2 that
functionality is provided by VIPX.SYS.

After you start the drivers, you should then be able to start
LapLink V and make network connections. You might wish to create
a DOS batch file that starts the drivers and then LapLink V.

C. Changing CONFIG.SYS for Serial Cable Connections

To make serial cable connections under OS/2, edit the OS/2
CONFIG.SYS file. However, making this change may prevent
stable modem connections.

If you want to use serial cables, find the line that reads:

    DEVICE=[path]\VCOM.SYS

and disable it by adding "REM" before the line so that it reads:

    REM DEVICE=[path]\VCOM.SYS

You will need to restart OS/2.

NOTE: For the most consistent serial cable performance, use the
LapLink V Port/Modem Setup command and set the serial port to
"Polled."

-----------------------------------------------------------------
IX. Computer Names, Passwords, and User Names

We do not recommend using high-order ASCII characters in computer
names, passwords, or user names. When stored by LapLink,
characters are converted to upper-case which may not correspond
to the lower-case letters. This is especially a problem with
passwords which are not displayed on your screen.

-----------------------------------------------------------------
X. The Xircom Parallel Port Multiplexor

LapLink V has been designed to work with parallel ports that have
a Xircom Parallel Port Multiplexor. However, the system must
first be set up properly.

First, do NOT use the port-switching software that comes with the
multiplexor. (LapLink V contains code that causes the multiplexor
to automatically switch ports, so the port-switching software is
unnecessary. Not using the switching software has the additional
benefit of freeing more memory for your applications.)

Second, the LapLink parallel cable must be attached to the "A"
port of the multiplexor. The printer cable should be attached to
"B."

Third, you must make a change using the "Port/Modem Setup"
command (Options menu):

Choose the command, and in the Port/Modem Setup dialog, select
the parallel port with the multiplexor. In the next dialog place
an x in the Force Standard (4-bit) mode check box and choose
<OK>. If you do not make this change, the Multiplexor may try to
switch between the printer and the cable during the middle of a
copy.

NOTE: There is one case where a connection involving a Xircom
parallel port multiplexor does not work: The PC with the
multiplexor is running LapLink V from DOS. It is connecting via
parallel cable to a PC running LapLink V from Windows, and the PC
with Windows has installed the LapLink V enhanced port drivers.
To allow these two PCs to connect, either start Windows on the PC
with the multiplexor and then start LapLink. Or quit Windows on
the PC without the multiplexor and then start LapLink.

-----------------------------------------------------------------
XI. USING LAPLINK V WITH OTHER TRAVELING SOFTWARE PRODUCTS

LapLink V is not compatible with LapLink Pro and you cannot
connect to another PC running LapLink Pro.

Because WinConnect, DeskLink, and the LapLink III Device Driver
compete with LapLink V for port usage, using them with LapLink V
may require experimentation. In most cases, you need to delete
the LapLink V configuration file (TSI.INI), start the other
program, and then start LapLink V. This causes LapLink V to
re-check all available ports and it then only uses the ports that
are not currently in use by the other program. (Note: When you
delete TSI.INI many options are returned to their default
values.) If you need help with this procedure, call Traveling
Software Technical Support.

Battery Watch Pro is compatible with LapLink V, but as with other
TSRs, you should avoid popping up the Battery Watch screen during
a file transfer.

-----------------------------------------------------------------
XII. GETTING TECHNICAL SUPPORT IN THE U.S.

If you have a question or need Technical Support, check the
numbers in your user manual.

If you want to contact the TSI Technical Support bulletin board,
set your modem to dial [phone]. Use the following settings
for your communications program:

Baud rate      2400 or 9600
Parity         None
Data bits      8
Stop bits      1
-----------------------------------------------------------------
XIII.  MAKING SUGGESTIONS TO IMPROVE LAPLINK V

Traveling Software is constantly looking for ways to improve its
products. Over the years, our customers have been the ones who
have provided some of the best product improvement suggestions.

We encourage you to send us your comments, criticisms, and ideas.
We will try to implement your requests in future versions.

You may address your comments to:

   Traveling Software, Inc.
   LapLink V Suggestions
   18702 North Creek Parkway
   Bothell, WA 98011


Compiled February 15, 1993