Hi, Jerry,
I've been following the thread on your Interlnk and Intersvr prob with a
little bit of puzzlement. I always use it with parallel cables, but looking
at the help file in PC-DOS 7.00 you get by typing:
help intersvr
or
help interlnk
to use a serial transfer, you need to tell both programs some things about
the parameters of the serial connection, which com port, what baud rate,
what IRQ, etc. I've never tried to load interlnk from startup under
Windows, but I'd be inclined to run Interlnk.exe as a device in config.sys
on the 486 machine, assuming it'd be the DOS machine, and then run
intersvr.exe from a DOS box under Windows on the Pentium box and use the 486
machine to initiate the transfers between the two machines, since the
Pentium's drivers would be mapped by intersvr.exe to the 486 machine.
Parallel cable transfers would be at least eight times faster than serial
port ones, and you don't have to tell anybody anything about which ports to
use, how fast to run, or what drives to map where. It's definitely the way
to go. In fact, all my DOS-based machines always boot up with a line in
that config.sys file that says
DeviceHigh=C:\DOS\InterLnk.Exe
and I run intersvr.exe on the machine that I want to be the "server" who's
drives will be mapped onto the controlling machine. Of course, you'll need
a lastdrive= statement in the config.sys file of the interlnk machine with a
letter high enough to map all the other guy's drives.
I used to use all kinds of parallel and serial port file transfer utilities,
even older version of LapLink, but I find Interlnk and Intersvr to be such a
KISS-principle pair of programs, that I use them almost exclussively now.
I've never had a problem using the one program from a given DOS version X.Xx
with the other program from somebody else's DOS version Y.YY, and it doesn't
matter if one machine is a fast 80486 and the other an old 80286 tortoise.
It all works as advertised.
Reply to: [EMAIL PROTECTED]
Brent Reynolds, Atlanta, GA USA
Net-Tamer V 1.12 Beta - Registered
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.
