Mail Archives: opendos/1997/05/26/11:35:34
On Mon, 26 May 1997, "Arkanoid" wrote:
> Interlink server does not work over OpenDOS. At least my configuration
> does not work.
Yes, this is a known problem of MS DOS Interlink, which is a *very*
dirty hack, patching around in DOS. You *can* use the client on a
COD/NWDOS machine, but not the server. Beware of running the *server*
on COD/NWDOS machines, it may seriously corrupt your file-system.
Some users even reported they had to re-partition their harddisk!
I would recommend to completely forget about this utility.
While FILELINK normally does not perform at the same speed (though it
is better configurable by directly editing it's .INI file), you can
use it on both, COD/NWDOS and MS-DOS/PC-DOS systems.
Some better alternatives are the NC 5 (COM/LPT) or the DN II 1.50
(COM/LPT/IPX) link functions, or specialized utilities like
LAPLINK (COM/LPT/IPX) or FASTLYNX (COM/LPT/IPX).
For automatic and almost troublefree configuration and setting up
connections, I can recommend FASTLYNX (FX), e.g. which is very
easy to use when connecting a new (and unknown) machine to your
main PC. It will detect the correct ports etc. 'automagically',
you just need to plug in the cable, and that's all...
When speaking of the IPX protocol, or course, one should not forget
about using PNW, which also comes with COD... However, there are
some scenarios, where an IPX stack (provided e.g. by the ODI-drivers
without loading VLM) has advantages over the 'IPX/NETX' alias ODI/VLM,
(which is required for PNW), and vice versa. Some discussion on this
can be found in MPDOSTIP.ZIP...
Matthias
--------------------------------------------------------------------
Snail mail: Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
New eMail : <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
Web : URL: http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
--------------------------------------------------------------------
- Raw text -