Re: [Freedos-user] INTERLINK

[Tom Ehlert]

> 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


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> 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 /AUTO /NOPRINTER /LOW

it’s working. The machine is still on FreeDOS 1.0 and loads HIMEM.EXE and 
EMM386.
So with this „/LOW" everything seems to work fine too.

> 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, virtual box, or another kernel issue with interlnk.  (It 
> crashes later in booting, but only if I load interlnk, though it's fine if I 
> add low to interlnk which seems odd as functionally should behave same with 
> applied patch.)
> 
The patched version of ITERLNK leads to problems if I still have a line
version=3.31
before it in FDCONFIG.SYS. The computer boots but other drivers don’t seem to 
get loaded, keyboard, mouse, the whole AUTOEXEC.BAT stuff.

It’s not really comparable to your configuration of course, as you use a 
different kernel.--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Tom Ehlert]

> 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, virtual box, or another kernel issue
> with interlnk.  (It crashes later in booting, but only if I load
> interlnk, though it's fine if I add low to interlnk which seems odd
> as functionally should behave same with applied patch.)

I had only tested this with

  softice
  himem
  interlnk

what is your crashing configuration?




Mit freundlichen Grüßen/Kind regards
Tom Ehlert
+49-241-79886


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[perditionc]

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, virtual box, or another kernel issue with interlnk.
(It crashes later in booting, but only if I load interlnk, though it's fine
if I add low to interlnk which seems odd as functionally should behave same
with applied patch.)

Jeremy
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

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 fixed, it is possible to patch INTERLNK.EXE to make it 
work with FreeDOS. Here is how:

Get INTERLINK from the Microsoft FTP server ftp.microsoft.com.

Login with a FTP client like FileZilla, username is „anonymous“, password is 
your email.

Change to the directory Softlib/MSLFILES.

Get the file OLDDOS.EXE. It includes the two programs for INTERLINK: 
INTERSVR.EXE which is used by the server and INTERLNK.EXE for the client.

Please check the license file. You have the right to use the software "in 
conjunction with licensed copies of  Microsoft Windows 95“. Please make sure 
you have such a license.

The server program INTERSVR.EXE runs fine in FreeDOS. To share the C: 
harddrive, just command:

C:\UTIL\INTERSVR.EXE C:

On the client you need to run INTERLNK.EXE. It has to be loaded as device 
driver in FDCONFIG.SYS with a line like this:
DEVICE=C:\UTIL\INTERLNK.EXE /AUTO /NOPRINTER

At the moment, such a line in FDCONFIG.SYS will crash FreeDOS.

To get INTERLNK.EXE working, you could patch the file:

Open the file INTERLNK.EXE in a hex editor. Find the following pattern:

00 05 72 56 8b 1e 55 04

and replace it with:

00 05 eb 56 8b 1e 55 04

This replaces the „JB“ instruction in assembly language (conditioned jump) with 
an unconditioned „JMP“. The condition was about the DOS version detected. 

As you can see in the following pictures, such a patched version of 
INTERLNK.EXE boots just fine.
https://www.lazybrowndog.net/freedos/interlnk/interlnk-boot.png

And it connects with INTERSRV.EXE on the remote computer.
https://www.lazybrowndog.net/freedos/interlnk/interlnk-connection.jpg

Hope this helps someone someday.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> 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. 

On the server command:
DDLINK /S L=1
On the client command:
DDLINK L=1

while L=1 means LPT1.

Seemed to work without problem on the two machines with FreeDOS 1.
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[my . green]

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 FDCONFIG.SYS, but it also worked with
the old EMM386 and HIMEM (it’s still a FreeDOS 1.0 machine).

https://www.lazybrowndog.net/freedos/interlnk/interlnk1.jpg

Unfortunately the characters are garbled though.

https://www.lazybrowndog.net/freedos/interlnk/interlnk2.jpg

I tried it with and without any country/codepage settings, so I am pretty sure
that’s not the problem. File dates and times also don’t make a lot of sense, if
you take a look. :-> 

The program on the second picture is Necromancers DOS Navigator. But also
without GUI, when I change to D: (the remote drive) on the command line of the
client and do „dir“, it types a long list of weird filenames and characters.

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

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 FDCONFIG.SYS, but it also worked with 
the old EMM386 and HIMEM (it’s still a FreeDOS 1.0 machine).

https://www.lazybrowndog.net/freedos/interlnk/interlnk1.jpg 


Unfortunately the characters are garbled though.

https://www.lazybrowndog.net/freedos/interlnk/interlnk2.jpg 


I tried it with and without any country/codepage settings, so I am pretty sure 
that’s not the problem. File dates and times also don’t make a lot of sense, if 
you take a look. :-> 

The program on the second picture is Necromancers DOS Navigator. But also 
without GUI, when I change to D: (the remote drive) on the command line of the 
client and do „dir“, it types a long list of weird filenames and characters.



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Louis Santillan]

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 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 weekend if time permits after I commit
> changes from git to svn.
>
> On Feb 5, 2016 11:04 AM, "Tom Ehlert"  wrote:
>>
>> 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 when there were no network cards a
>> commodity. (the times they are a changing ...)
>>
>> > I believe Eric is correct when he says INTERxxx is sector-based
>> > rather than file-based as Tom states.  I do know that the client
>> > (INTERLNK) must be capable of "understanding" the file system of the
>> > server (INTERSVR).  For example, if the client is MS-DOS 6.2 (which
>> > doesn't understand FAT32) and the server is MS-DOS 7.x (which does
>> > understand FAT32) and you're trying to access a FAT32 disk on the
>> > server, it doesn't work.  I know this for sure because I've tried
>> > it.  If INTERxxx was file-based, it wouldn't matter which version of
>> > FAT was on either computer (and could even work on non-FAT drives
>> > the server had mounted, like CD's and network drives).
>>
>> you are right, my memory was plain wrong on this.
>>
>> and - while debugging the crashing problem - I also saw that it
>> installs itself as handler for INT 25/26 'DOS DISK READ/WRITE'
>>
>> Tom
>>
>>
>>
>> --
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Don Flowers]

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 either but did work with FreeDOS kernel as well
> as it did with PCDOS.
>
> * I'm releasing updated version this weekend if time permits after I
> commit changes from git to svn.
> On Feb 5, 2016 11:04 AM, "Tom Ehlert"  wrote:
>
>> 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 when there were no network cards a
>> commodity. (the times they are a changing ...)
>>
>> > I believe Eric is correct when he says INTERxxx is sector-based
>> > rather than file-based as Tom states.  I do know that the client
>> > (INTERLNK) must be capable of "understanding" the file system of the
>> > server (INTERSVR).  For example, if the client is MS-DOS 6.2 (which
>> > doesn't understand FAT32) and the server is MS-DOS 7.x (which does
>> > understand FAT32) and you're trying to access a FAT32 disk on the
>> > server, it doesn't work.  I know this for sure because I've tried
>> > it.  If INTERxxx was file-based, it wouldn't matter which version of
>> > FAT was on either computer (and could even work on non-FAT drives
>> > the server had mounted, like CD's and network drives).
>>
>> you are right, my memory was plain wrong on this.
>>
>> and - while debugging the crashing problem - I also saw that it
>> installs itself as handler for INT 25/26 'DOS DISK READ/WRITE'
>>
>> Tom
>>
>>
>>
>> --
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> ___
>> Freedos-user mailing list
>> Freedos-user@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/freedos-user
>>
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Jose R Gimenez]

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 Windows 7
installed.

Since I could not get INTERLINK running on FreeDOS, I Installed "MS Virtual
PC 2004" on my XP. The INTERLINK is running and I am about to test
communication between computers.

Thank you, I'll come back

Jose
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[perditionc]

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 weekend if time permits after I commit
changes from git to svn.
On Feb 5, 2016 11:04 AM, "Tom Ehlert"  wrote:

> 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 when there were no network cards a
> commodity. (the times they are a changing ...)
>
> > I believe Eric is correct when he says INTERxxx is sector-based
> > rather than file-based as Tom states.  I do know that the client
> > (INTERLNK) must be capable of "understanding" the file system of the
> > server (INTERSVR).  For example, if the client is MS-DOS 6.2 (which
> > doesn't understand FAT32) and the server is MS-DOS 7.x (which does
> > understand FAT32) and you're trying to access a FAT32 disk on the
> > server, it doesn't work.  I know this for sure because I've tried
> > it.  If INTERxxx was file-based, it wouldn't matter which version of
> > FAT was on either computer (and could even work on non-FAT drives
> > the server had mounted, like CD's and network drives).
>
> you are right, my memory was plain wrong on this.
>
> and - while debugging the crashing problem - I also saw that it
> installs itself as handler for INT 25/26 'DOS DISK READ/WRITE'
>
> Tom
>
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Tom Ehlert]

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 when there were no network cards a
commodity. (the times they are a changing ...)

> I believe Eric is correct when he says INTERxxx is sector-based
> rather than file-based as Tom states.  I do know that the client
> (INTERLNK) must be capable of "understanding" the file system of the
> server (INTERSVR).  For example, if the client is MS-DOS 6.2 (which
> doesn't understand FAT32) and the server is MS-DOS 7.x (which does
> understand FAT32) and you're trying to access a FAT32 disk on the
> server, it doesn't work.  I know this for sure because I've tried
> it.  If INTERxxx was file-based, it wouldn't matter which version of
> FAT was on either computer (and could even work on non-FAT drives
> the server had mounted, like CD's and network drives).

you are right, my memory was plain wrong on this.

and - while debugging the crashing problem - I also saw that it
installs itself as handler for INT 25/26 'DOS DISK READ/WRITE'

Tom


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Bret Johnson]

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 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 believe Eric is correct when he says INTERxxx is sector-based rather than 
file-based as Tom states.  I do know that the client (INTERLNK) must be capable 
of "understanding" the file system of the server (INTERSVR).  For example, if 
the client is MS-DOS 6.2 (which doesn't understand FAT32) and the server is 
MS-DOS 7.x (which does understand FAT32) and you're trying to access a FAT32 
disk on the server, it doesn't work.  I know this for sure because I've tried 
it.  If INTERxxx was file-based, it wouldn't matter which version of FAT was on 
either computer (and could even work on non-FAT drives the server had mounted, 
like CD's and network drives).

As a logical extension to the above, I don't think Eric is correct when he says 
it will only work with 512-byte sectors, though I've never actually tried it.  
I don't think it matters what the sector size is, as long as both computers can 
"understand" the sector size.  For example, MS-DOS is compatible with large 
sector sizes (larger than 512 bytes) with a little finagling, but FreeDOS is 
not.  I suspect that INTERxxx would work with any sector size (whether bigger 
or smaller than 512), as long as both OS's "understand" it.

Find your perfect car
Search 4.1 million listings
http://thirdpartyoffers.juno.com/TGL3141/56b4c14aacfe2414a3382st01vuc

--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Don Flowers]

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, Ulrich Hansen  wrote:

>
> > 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. But on the one with interlnk I get an error
> after loading the driver in FDCONFIG.SYS with
>
> DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER
>
> dos mem corrupt
> panic: mcb chain corrupted
> system halted
>
> The error was only visible when both computers were NOT connected. If I
> connect both computers over LPT and boot again the interlnk machine just
> freezes.
>
> I tried with memory managers on and off and even with a nearly empty
> AUTOEXEC.BAT and FDCONFIG.SYS (well the SHELL command was the only other
> line in it).
>
> I confess, both machines are still running FreeDOS 1.0, so maybe it’d work
> with FreeDOS 1.1. And both Aeros have the 16 MB RAM extension module
> installed, which unfortunately has a bug by design. So it may work with
> different hardware and if you try hard enough.
>
> Filemaven, which Eric suggested, worked for me out of the box and without
> changing FDCONFIG.SYS. So try it, if you don’t need the intersvr program
> running as TSR in the background and providing you with a drive letter for
> the remote machine.
>
> regards
>
> PS: Wow, I still had the centronics cable and the LPT adapter in a box!
>
>
>
>
>
>
> --
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> ___
> Freedos-user mailing list
> Freedos-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/freedos-user
>
--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Ulrich Hansen]

> 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. But on the one with interlnk I get an error after loading 
the driver in FDCONFIG.SYS with 

DEVICE=C:\INTERLNK.EXE /AUTO /NOPRINTER

dos mem corrupt
panic: mcb chain corrupted
system halted

The error was only visible when both computers were NOT connected. If I connect 
both computers over LPT and boot again the interlnk machine just freezes.

I tried with memory managers on and off and even with a nearly empty 
AUTOEXEC.BAT and FDCONFIG.SYS (well the SHELL command was the only other line 
in it).

I confess, both machines are still running FreeDOS 1.0, so maybe it’d work with 
FreeDOS 1.1. And both Aeros have the 16 MB RAM extension module installed, 
which unfortunately has a bug by design. So it may work with different hardware 
and if you try hard enough.

Filemaven, which Eric suggested, worked for me out of the box and without 
changing FDCONFIG.SYS. So try it, if you don’t need the intersvr program 
running as TSR in the background and providing you with a drive letter for the 
remote machine. 

regards

PS: Wow, I still had the centronics cable and the LPT adapter in a box!
 




--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Tom Ehlert]

>> 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, those provide sector based connection
wrong. it provides a file based service, and makes remote drives available
as drive letters.

> of FAT
> partitions through a serial or printer port cable: As long as your
> sector size is 512 bytes, that should probably work. Note that you
> only have those tools if you already own MS DOS anyway and that the
> tools only support FAT16 and maybe FAT12, but not FAT32.
interlink/intersrv doesn't care about fat12/16/32


Tom


--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

Re: [Freedos-user] INTERLINK

[Eric Auer]

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 512 bytes, that should probably work. Note that you
only have those tools if you already own MS DOS anyway and that the
tools only support FAT16 and maybe FAT12, but not FAT32. You could
also use the drive-over-cable feature in the free FileMaven (FM3)
file manager instead of using interlnk and intersvr. The latter two
require at least MS DOS 3.0 and 2.11, respectively, according to MS
KB item 502282 on the support.microsoft.com website - should be ok.

For more modern connectivity, you could also use FTP, SCP (see SSH)
and SMB (using the DOS port of smbclient) or of course solutions on
the basis of (HTTP or not-too-new-HTTPS) websites. However, all of
those have in common that you use a client tool rather than making
one drive on one computer visible as an actual drive on the other.

For making drives directly visible, the modern solution would be to
run DOS in a virtual environment: There is a DOS driver for client
drives in VMware http://www.freedos.org/software/?prog=vmsmount and
if you use the DOSEMU or DOSBOX environments, making host directories
visible as drives visible from DOS is even a built-in feature which
does not require any additional drivers on the DOS side :-)

FileMaven 3.5a is closed source freeware with laplink style transfer
and support for ZIP and others: http://www.briggsoft.com/fmdos.htm

Cheers, Eric



--
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

[Freedos-user] INTERLINK

[Jose R Gimenez]

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 + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user