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=/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=/4140___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user