Hey, Jude,
If you are using a parallel connection for your data transfer using
Interlnk and Intersvr, whether they are in any version of MS- or PC-DOS or
any other DOS that has those programs, you do not need to specify any
parameters at all for either program. You need to run interlnk.exe as a
device= statement loaded from config.sys on one machine, and you invoke
intersvr.exe from the command line on the other machine. I always use
commands that will load either program high. Usually, I have interlnk.exe
set up as a device statement in config.sys on both machines, allowing
either to be the controlling machine without rebooting.
The statement reads:
device=c:\dos\interlnk.exe
When I run the intersvr program on the other machine, I just type the
program name and press the <enter> key twice. If a synthesizer is
connected to that machine, it reads part of the message that says, "This
computer
Other Computer"
and shows the transfer speed status. Other than the message that appears
onscreen when the interlnk .exe device loads from config.sys, there is no
indication that the program is doing anything.
I always use a parallel connection because, all other things being equal,
the transfer rate should be at least eight times faster than a serial
connnection. This, of course works best if your parallel ports are both
using the EPP or the ECP, Extended Parallel Port or Expanded Capability
Parallel protocols so transfer can happen easily in both directions.
For the connection, you hneed what is generically referred to as a
"LapLink cable", although you don't need to buy a copy of the LapLink
software to get Travelling Software's expensive name-branded cable. You
can get a "laplink" cable at any computer "show" or any good computer
store. It has the male parallel connection on both ends and most of them
are better shielded than your average cheap printer cable.
For the serial connection, you need a "null modem" cable and you must
specify com ports and communications parameters on the interlnk device
statement line and in some versions, on the intersvr line. I find that
the interlnk/intersvr pair from any DOS version that has it works well on
any other DOS version, even on earlier DOS versions that did not have
those programs included. The only exception to that may be version 7.00
or later of Corel/Lineo's OpenDOS/DR-DOS which has a nasty habbit of
locking their external utility programs to their DOS version. I have seen
a few of those utilities not work even using a version number entry for
the program in a DOS SetVer table.
Come to think of it, I have never had a problem getting a successful
connection using the interlnk from PC-DOS 7.00 on one machine and Intersvr
from MS-DOS 6.22 on the other machine.
The machine you use to control the connected pair is always the interlnk
machine. Once Intersvr is invoked and running on the server machine, the
only keystroke that does anything is the <alt-F4> combination and the
<enter> key to confirm that, yes, you really do want to exit and return to
DOS.
Brent Reynolds
Random Access Internet Shell account
Standard disclaimers apply.
Email: [EMAIL PROTECTED]
To unsubscribe from SURVPC send a message to [EMAIL PROTECTED] with
unsubscribe SURVPC in the body of the message.
Also, trim this footer from any quoted replies.
More info can be found at;
http://www.softcon.com/archives/SURVPC.html
