> The patched version of ITERLNK leads to problems if I still have a line
> version=3.31
version=3.31 is lying about location and size of a couple DOS
datastructures. don't do this, or expect trouble.
use /low or a new kernel to run interlnk.
tom
--
> Am 11.02.2016 um 14:55 schrieb :
>
> Something else that should work if you don't want to modify it, add /low
> option which will also bypass the problematic code.
>
Oh, that’s interesting. If I load the original, unpatched INTERLNK.EXE in
FDCONFIG.SYS with
DEVICE=C:\UTIL\INTERLNK.EXE /AU
> Something else that should work if you don't want to modify it, add
> /low option which will also bypass the problematic code.
> Tom's workaround will be in svn kernel soon, but I need to do some
> more testing as I'm still getting crashes, but haven't determined if
> its because of memory mana
Something else that should work if you don't want to modify it, add /low
option which will also bypass the problematic code.
Tom's workaround will be in svn kernel soon, but I need to do some more
testing as I'm still getting crashes, but haven't determined if its because
of memory managers, virtu
With a lot of help by Tom (thanks!!), here is more information about INTERLINK
and FreeDOS.
Microsofts INTERLNK program doesn’t work with FreeDOS at the moment. There is a
bug in the FreeDOS kernel that makes some programs crash the system, one of
those is INTERLNK.EXE.
As long as this isn’t
> I've used David Dunfield's DDLINK[0] successfully in VirtualBox over
> the virtual switch & NICs.
>
> [0] http://www.classiccmp.org/dunfield/dos/index.htm
Yesterday evening I tried winlink, filemaven and DDLINK. DDLINK was by far the
easiest to configure and use.
Put it on both machines.
O
Tom suggested to put a line
version=3.31
in FDCONFIG.SYS, right before
DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER
This solved the problem of the crash/freeze. (Thanks!)
As you can see in the first picture, interlnk is now able to make a connection.
I tried it with an empty AUTOEXEC.BAT and FDC
Tom suggested to put a line
version=3.31
in FDCONFIG.SYS, right before
DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER
This solved the problem of the crash/freeze. (Thanks!)
As you can see in the first picture, interlnk is now able to make a connection.
I tried it with an empty AUTOEXEC.BAT and FD
I've used David Dunfield's DDLINK[0] successfully in VirtualBox over
the virtual switch & NICs.
[0] http://www.classiccmp.org/dunfield/dos/index.htm
On Fri, Feb 5, 2016 at 9:05 AM, wrote:
> Have tried with latest* kernel, there is a fixed bug in int 25/26 that may
> effect it.
>
> You may want
I had to install NON-ECC RAM to eliminate the MCB error
On Fri, Feb 5, 2016 at 12:05 PM, wrote:
> Have tried with latest* kernel, there is a fixed bug in int 25/26 that may
> effect it.
>
> You may want to try RIFS as well, it has source, but I don't recall if it
> used serial, parallel, or eith
Hi all,
I haven't read all the mails.
The problem I am facing is that one client of mine has an old industrial PC
that lost some data files due to low battery. The PC has INTERLINK
installed and no other means to copy files to it.
On the other hand, my work computer has FreeDOS, Windows XP and W
Have tried with latest* kernel, there is a fixed bug in int 25/26 that may
effect it.
You may want to try RIFS as well, it has source, but I don't recall if it
used serial, parallel, or either but did work with FreeDOS kernel as well
as it did with PCDOS.
* I'm releasing updated version this week
Bret,
> Eric/Tom:
> I used to use INTERxxx a lot many years ago using the special
> parallel cables designed for that purpose (I think I still have a
> couple of those cables in my "spare cable box"). Parallel is MUCH
> faster than serial (null modem) cables.
I also used it *A LOT*. in times whe
Ulrich:
If you really have an "MCB chain corrupted" error, you have a serious problem
and need to figure out what's causing it. It's more than likely a device
driver or TSR that isn't compatible with FreeDOS for some reason (could be
INTERxxx or could be something else).
Eric/Tom:
I used to
FileMaven is ok for small file transfers, I happen to have LapLink V and
it works the best for me, but still speed is limited on serial ports. I
have been trying to configure a LAN crosslink transfer but no luck so far.
Until then USB is my goto for file tranfers.
On Fri, Feb 5, 2016 at 6:45 AM,
> Am 05.02.2016 um 03:35 schrieb Jose R Gimenez :
>
> Just want to know if FreeDOS can run interlink.exe and intersrv.exe
In theory. Out of curiosity I booted two Compaq Contura Aeros, installed
intersvr and interlnk and tried it. It didn’t work for me so far. The intersvr
machine runs great.
>> Just want to know if FreeDOS can run interlink.exe and intersrv.exe
>> If FreeDOS is compatible with interlink, then what steps should follow?
interlink/intersrv are part of msdos. this should work in theorie,
but you are probably the first to test this on FreeDOS.
> As far as I remember, tho
Hi!
> Just want to know if FreeDOS can run interlink.exe and intersrv.exe
> If FreeDOS is compatible with interlink, then what steps should follow?
As far as I remember, those provide sector based connection of FAT
partitions through a serial or printer port cable: As long as your
sector size is
Hi,
Just want to know if FreeDOS can run interlink.exe and intersrv.exe
If FreeDOS is compatible with interlink, then what steps should follow?
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM
19 matches
Mail list logo
