> 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.
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
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
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
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
>
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
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
Reviving this thread to post an update:
I am trying to stay in FreeDOS on one of my PC's. I installed GRUB4DOS and
am pleased with configuration options, I can boot CDROM's of various
emulationn, I can boot PLOP Boot Manager to Boot USB flash drives (no more
searching for PLOP floppies around the
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
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
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
>> 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,
> 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
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
14 matches
Mail list logo