Ref: 15990002
Title: Using Paradox 386 with Link Plus Optimizer
Date: 7/18/89

Copyright 3Com Corporation, 1991.  All rights reserved.

Programs that access the timer tick or that depend heavily on
timing tend to interfere with the operation of Link Plus
Optimizer (LPO) and network software running on the card.

Paradox 386 is an example of such a program.  It runs fine off of
a local drive, but causes the computer to crash when run from a
network drive while using LPO.  The computer requires a cold boot
(turning the computer off, then on again) to resume operation.

The problem is due to the pusher (PSH.SYS) conflicting with these
type of programs.

The solution is to run the process manager (PRO.SYS) in main
memory to isolate LPO from the offending program as well as
running PRO.SYS on the card.  A sample (partial) CONFIG.SYS file
shows PSH.SYS defined before PSH.SYS:

                device=pro.sys 12 2 2
                device=psh.sys
                device=pth.sys


A sample (partial) AUTOEXEC.BAT file shows the addition of
RUNMINDS MINDSPRO:

                runminds mindspro
                ldr
                minses12
                msredir /z:4096
                setname $$3com$$


Allocating more buffers will also make the system more stable.
If you have enough memory on the 3C505 card, add the following
line to the LDR.CFG file:

                device=eth505e.sys -b32 -h6

(Default values are -b24 and -h4.)

If you have LPO version 1.2 or higher, you can find out how much
memory is available on the 3C505 card by running LDR -i after
your AUTOEXEC finishes executing.
