OS/2 Shareware BBS: 30 fixes_v/30-fixes_v.zip/lr11g1.zip/README.TXT

Text File | 1995-07-20 | 14KB | 350 lines

LinkRight 1.1G

New for 1.1G

Not much is new.  The major fixes with this patch are new
LRCOM.SYS and LRPAR.SYS files.  These drivers will only work with
version 1.1F and 1.1G of the executables.

LR.EXE has a minor fix for Retry / Cancel.  Now Cancel actually
does something.

LRDOS.EXE has a minor fix.  For some users of ThinkPads and other
portables, LRDOS.EXE would not work properly.  A new parameter
has been added to optionally use an I/O Delay for parallel port
access.

Running the Patch Program

First, make a backup of your LinkRight directory in case you want
to go back to a previous version.  Next, unzip the file to your
LinkRight directory.  Then run LRPATCH.EXE.  It should find your
previous LR.EXE, determine it is valid, then patch LR.EXE, LRCLONER.EXE,
and LRDOS.EXE.  It will then update your config.sys by doing the
following steps:

  Copy config.sys to config.bak
  Replace the line for LRCOM.SYS and LRPAR.SYS with new lines or
  add them if they are not there.  These lines will be at the end
  of your config.sys.

Be sure to shutdown and reboot before running LinkRight.

Installing on new systems

After running the patch, you may want to install on other systems.
You can do this by copying the entire LinkRight directory to a floppy
and running INSTALL.EXE.  INSTALL.EXE is included with the zipped
patch file.

Tuning

After doing the patch, you may want to do some tuning.  I would
recommend deleting LINKRGHT.CFG so that LinkRight will start with
default options.

Make sure the Retry Warning Delay is set to a high value.  I'd
recommend 8 or 9.

After you've got it up and running, you can then tune the options
for speed, reliability, response.

First, try doing an 8 bit parallel port connection.  Uncheck the
4 bit par port transfers option and establish a connection.  If the
connection is not established, you'll have to drop back to 4 bit
mode.

For speed, try these settings:

No Verify - this will do CRC checks on all packets but will
not do a complete file verification.  So you'll only get one verify
test instead of two.

Use Compression

8 Bit Par Port Transfers - you've already tried this to see if it
will work on your particular systems.

Uncheck Idle Time Transfers Only

Max Packet Size - set this to the maximum at 1024.

For system responsiveness, try these settings:

Max Packet Size - set to 256 or 128.

Check Idle Time Transfers Only.

A couple of new options have been added as parameters for
the drivers.  The complete list of options for LRPAR.SYS are

DEVICE=LRPAR.SYS /Q:7 /P /A:3BC /M /C:3 /D

where:
 /Q:7 uses IRQ7 or /Q:5 uses IRQ5.  These are the only IRQs supported.
 Interupt driven mode can only be used if PRINT01.SYS or PRINT02.SYS
 also uses the same interupt.  If no /Q option is selected, polled is
 assumed.

 /P is for polled.  This is a useless option, since it is the default.

 /A:3BC or /A:378 or /A:278 select the address of the LPT port for
 LinkRight to use.  If this parameter is used, only one address can
 be specified.  Then, when you select Connect from the LinkRight
 menu, no matter which LPT port you select, either LPT1, LPT2 or
 LPT3, LinkRight will use the address specified.  If this parameter
 is not included, LinkRight reads the BIOS info at bootup time to
 get the LPT addresses.

 /M is to specify MicroChannel machines.  For some MicroChannel systems
 when booted from bootable floppies, LinkRight would not see that it
 was MicroChannel and would assume an ISA bus.  This caused the
 driver to fail.  So if you boot your MicroChannel system from floppies
 and the LinkRight driver displays a message at bootup time saying
 an ISA bus was found, use this parameter to fix the problem.

 /C:X is used to tell the driver what type of system is being used.
 If the driver does not load properly, use this parameter and the
 driver will skip it's own test for type of system used and will accept
 the entered parameter as the system type.

 /C:1 is for a 386 SX system.
 /C:2 is for a 386 DX system.
 /C:3 is for a 486 DX system.
 /C:4 is for a 486 DX2 system.
 /C:5 is for a 486 DX4 system.
 /C:6 is for a Pentium system.
 /C:7 is for a faster than Pentium system.

 /D is to add a driver delay for parallel port access.  Use this
 parameter if you are having problems transferring lots of files.
 The sympton of the problem is that you establish a connection,
 transfer a megabyte or 2 megabytes but then LinkRight just locks
 up.  It is most common with ThinkPads and other portable systems.
 This problem is different from the Retry Warning Delay and you
 should not include this parameter until you've tried bumping up
 the Retry Warning Delay to 8 or 9 and the problem persists.

 The preferred and suggested mode of use is no parameters on the
 LRPAR.SYS line in CONFIG.SYS.  You can add parameters if there are
 any problems.

The complete list of options for LRCOM.SYS are

DEVICE=LRCOM.SYS (1, 03F8, 4) /C:3

 /C:X is used to tell the driver what type of system is being used.
 If the driver does not load properly, use this parameter and the
 driver will skip it's own test for type of system used and will accept
 the entered parameter as the system type.

 /C:1 is for a 386 SX system.
 /C:2 is for a 386 DX system.
 /C:3 is for a 486 DX system.
 /C:4 is for a 486 DX2 system.
 /C:5 is for a 486 DX4 system.
 /C:6 is for a Pentium system.
 /C:7 is for a faster than Pentium system.

 (COM, ADDR, IRQ) where COM is which COM Port to use, ADDR is the
 address of the COM port, and IRQ is the interupt to use.  The format
 is similar to what the standard COM.SYS driver of SIO.SYS driver
 uses.

 The preferred and suggested mode of use is no parameters on the
 LRCOM.SYS line in CONFIG.SYS.  You can add parameters if there are
 any problems.

Bootable Floppies

Warp bootable floppies should be built slightly differently.
From the OS/2 System folder, select System Setup.  From there, select
Create Utility Diskettes.  Build the 3 diskettes.  Boot the system from
those 3 diskettes, make sure it works OK, then start the modifications.

 REM out the config.sys line for memman=noswap.

 Add lines:
 MEMMAN=SWAP,PROTECT
 SWAPPATH=C:\TEMPSWAP

 Make sure you have about 8 Meg of disk space available for swapper.

 REM out protectonly=yes

 Add PROTECTONLY=NO

 Add LIBPATH=\;A:\;A:;

At the end of config.sys, add
 DEVICE=A:\LRPAR.SYS

Copy LRPAR.SYS to Utility diskette 2. Copy NLS.DLL to Utility diskette 2.
You may also need VIOCALLS.DLL  and DOSCALL1.DLL (I think, I'm
not sure about these).

Obviously, I skipped a couple of steps for partitioning, formatting, making
c:\tempswap, making c:\temp and putting LRCLONER.EXE in there.

You don't need CMD.EXE or EAUTIL.EXE in the C:\TEMP directory if you're using
version 1.1E or greater of LinkRight.  Ignore the statements in the manual
saying you do need to do this.

On Utility diskette 3 you'll find things like format.com fdisk.com, and the
important file sysinstx.com.  Other than that, diskette 3 is not used.


From the LinkRight 1.1F README.TXT

*********************
Late Breaking Bug Report

I've had some users tell me that when loading LRPAR.SYS or
LRCOM.SYS, OS/2 comes back and says it is an invalid device
driver.  I've seen this problem but have no definitive fix
for it yet.  A couple of workarounds are available which
will help.  The problem seems to be an interaction between
LRPAR.SYS and LRCOM.SYS when loading.  If you know you will
be using serial ports, don't load LRPAR.SYS and only load
LRCOM.SYS.  Conversely, if you're only using parallel ports,
don't load LRCOM.SYS.

If you need both parallel and serial ports, put one driver
as the first statement in your config.sys and the other
driver as the last statement in your config.sys.

Also, strangely enough, the error occurs more often when
the system is initially powered on.  In other words, when
the system is rebooted with CNTL-ALT-DEL, the error is
less likely to occur.

Finally, watch for an announcement for a bug fix for this
annoying problem.  A fix should happen soon. (This should
be taken care of with this 1.1G patch).
**********************

Bootable Floppies

For bootable floppies to use LRCLONER.EXE, a couple of
files need to be added for Warp usage.  DOSCALL1.DLL
and NLS.DLL need to be added to disk 1 from your Warp
system C:\OS2\DLL directory.

Differences between 1.1E and 1.1F

The biggest difference is improved serial port speed.  Now, you
can reliably do 115.2 kbps.  Note the new driver, LRCOM.SYS, is
required for 57.6 kbps or 115.2 kbps.  This driver does not
interfere with your normal com drivers (either com.sys or sio.sys).

Limitations

Faster serial speed comes at a price.  If you have a serial mouse,
you'll find that running LinkRight at 115 kbps or 57 kbps changes your
system to a single tasking system.  If you have a PS/2 mouse or
bus mouse using a high interupt, you can probably continue to use your
system while transferring files.

This limitation will be fixed in a future version.  1.1F was created
in a couple of weeks and is a quick and dirty version for faster
serial support.  Some niceties were sacrificed so it could be
released sooner.

Bug fixes

A couple of bugs have been fixed.  Some users reportedly could not
change directories to certain directories.  This bug was reported
many months ago, but I was never able to duplicate it.  During
final testing of 1.1F, I saw this bug occur on one of the four
systems I use for testing.  About 5 directories out of 200 failed.
After I duplicated the problem, it was fairly easy to fix, though
I still can't understand why it happened and why it happened on
only some systems and only on some directories.

Options

The patch file deletes your current options.  When you start the
new version of LinkRight, it will start with the default options,
so you'll have to set things up the way you want them.

If you copy the files to another system, be sure to delete the
LINKRGHT.CFG file, and have it start with no old configuration
file.

****IMPORTANT******
The MOST common user error for those using LRCLONER is starting
a clone operation and having the files transferred to C:\TEMP.
Some users try to fix this by starting LRCLONER from the root
directory of C:.  This only causes other problems.

The proper method of cloning is to start LRCLONER from the
C:\TEMP directory.  Once a connection is established, from the
Local system change directories on the Remote system by double
clicking on the line with ".." (you also have to change directories
on the Local system to get to the root).  Now you can start
transferring files and they will go to the proper location.
*******************

Turbomode (in the Options menu of LinkRight when in Local mode)
should be turned off initially.  Also, Turbomode is read and
set once when you establish a connection.  To change Turbomode,
change the option, disconnect if you are currently connected,
and do a re-connect.  If you have no trouble with Turbomode
off, you can try Turbomode on and get a speed boost.

The LinkRight parallel port driver can now be used in interupt
driven mode or polled mode.  The default is polled, which matches
the default of PRINT01.SYS in OS/2 Warp 3.0.

Interupt driven mode has some problems.  I've had some of my test
systems lock up completely when used in Turbomode with interupt mode.
The same system does not lock up when Turbomode is off.  None of my
test systems have any problems when using polled mode.  Many
gigabytes transferred successfully!!  Obviously, we suggest you
use polled mode.

For LRCLONER, you no longer need EAUTIL.EXE and CMD.EXE in the
C:\TEMP directory.  This should make cloning easier.  You still
need the temp directoy and LRCLONER.EXE should be started from
this directory.  Although I said this for 1.1D it turned out not
to be true.  I really mean it this time!!

 Serial mice and slow systems are a problem when using the parallel
 port.  Bump the packet size down to 128 bytes and turn Idle time
 transfers on and it may improve response with the mouse.  PS/2 style
 mice are not a problem.  If you find responsiveness is a problem and
 you are willing to work with me, I'll create a special driver for
 your particular systems to improve mouse responsiveness.  It may take
 a few tries to get it right, so patience would be required.  Obviously,
 when I get it working well on your systems, I'll incorporate it into
 the full LinkRight product.

 Bump up the Retry Warning Delay option to 9 and you will not get any
 of those annoying Retry Warnings.  LinkRight will try forever if this
 value is 9.  Of course, you won't know if there is a problem either.

 One user complained about updating the Remote system screen just to
 display a "dot".  I didn't see any problem on my systems, and it looked
 like a minor nit.  But during final testing of this version, I grabbed
 my slowest system, turned the hardware turbo switch off on it, and
 watched for about a second for it to refresh the screen.  Very annoying.
 There is a workaround available, though.  From an OS/2 command prompt,
 run LRCLONER T LPT1 on the Remote system.  You won't lose any
 functionality and won't be annoyed by the slow screen refresh.

 For cloning systems, run LRCLONER with no parameters to check the proper
 usage.  You should comment out any network stuff in your config.sys on
 the Source system so no files are locked at bootup. I've been told you
 have to do it this way if you're using COMM manager or Extended Services.
 After that, you can run the full PM version of LinkRight on the Source
 system and copy everything.  Running LRCLONER from the Source system to
 clone an entire system doesn't work (till I fix it), so use full PM
 version on the Source system.


 Good luck and happy computing!!

 Jeff Tremble
 President Rightware Inc.