Conversation about WinInterlnk
Here is a transcript of an IM conversation between two of our
support technicians about WinInterlnk,
a software program used to connect from Windows to a DOS machine
running INTERSVR. WinInterlnk
as well as the original INTERLNK and INTERSVR were developed by Sewell
Development Corporation. WinInterlnk
are available for free download to owners of a licensed copy of
FastLynx. The following transcript has been edited for readability.
I have a customer on the phone trying to get WinInterlnk set up with
What is he trying to do?
He is trying to connect a Win 2000 and a 6400 RF unit…?
First, is he running INTERSVR on the 6400?
He has it connected and INTERSVR is running on the 6400
If he has it connected, then the 6400 should show up as its own drive
letter when he opens My Computer. Does it?
It’s not. Does he need INTERLNK running?
ok… maybe he is getting it figured it out.
No, he just needs to open WinInterlnk and connect via the COM port that
the serial cable is plugged into. He can close WinInterlnk when the
connection has been made. The WinInterlnk program 1) sets up a drive
letter by which you can access the remote machine and 2) tells you the
I think he has a drive letter now, but it says it is inaccessable
Is FastLynx saying it is inaccessible or Windows?
I think it was Windows, but now it looks like it is working
Did he just have to close the programs after the connection was made?
Since the serial connection is a lot slower than accessing his local
drive, he needs to remember to wait a few seconds for any interaction
to complete everytime he does something that communicates with the
6400, e.g. copy, delete, DIR, etc.
In other words, if tries to delete something, just because Windows
might report that the file is deleted, it doesn’t necessarily mean that
the file is actually finished being deleted on the remote machine.
That seems to have done it for him. Thanks!
Now he should be able to run FastLynx in Local Connection mode and
access the 6400 as a locally mapped drive.