Hi,
On Jun 8, 2012 12:06 PM, "JPT" <j.p...@gmx.net> wrote:
>
> Am 06.06.2012 13:15, schrieb Eric Auer:
> >
> >> Two apps do not run using the first boot option JEMMEX:
> >>
> >> - Borland Pascal 7
> >> - Xtree Pro
>
> > Do both run if you do not load any EMM driver at all?
>
> when using XMGR or no EMS/XMS at all they run both.
>
> Xtree complains after a minute:
> device: AUX, Cannot write data.
> what about the AUX device in Freedos?
> Mode doesn't know about it?
Dunno, would only make a horrible suggestion to use a different file
manager, e.g. DJGPP-built Ytree. (Without further knowledge, it's very
difficult, esp. since I don't have Xtree. But I honestly hate the idea of
giving up or "don't use it" as worthwhile advice.)
> BP IDE starts fine, did not try further yet.
>
> current JEMMEX config is
> DEVICE=C:\DOS\BIN\JEMMEX.EXE NOEMS X=TEST NOVME NOINVLPG
Wait, are you running inside a VM? There's almost no other explanation for
using "NOVME".
BTW, "X=TEST I=TEST" [sic] is, I thought, the safest choice, though at this
point I'd be surprised if that was your problem.
It's a mess. I'm not pessimistic, but indeed with so many things mixed and
matched, it can get confusing.
> Xtpro does not crash any more. Maybe because I understood I have to wait
> forever for the AUX stuff. ;)
Dunno. Maybe a bug in FreeDOS, compared to MS-DOS, but I can only blindly
guess here. Unlikely but still possible.
> excluding anything doesn't help BP.
> but I realized there is a little bit of randomness.
> after boot-up, on the third try the BP IDE comes up.
That doesn't sound very promising. :-)
> mh... everytime BP crashes, it reserves a LOT of XMS memory.
> ~ 100 MB on first try, ~28 MB and all 8 MB of EMS on second try,
> on the third try it does not crash any more. I guess it does not reserve
> any EMS or XMS now.
Dunno, no reason it should be using so much or even both XMS plus EMS at
the same time. Might be some configuration setting (env. var.?) for that
somewhere. Or it could just be the extender's bug. Try HDPMI16 or DPMIONE
instead.
> why does MEM report EMS when JEMMEX option says NOEMS?
MEM isn't always reliable, just ignore it here. But I've personally seen
some incompatibilities ("bugs"?) with EMM386 lately, esp. NOEMS, which
confuses some extenders, so I can only suggest trying various setups, e.g.
XMS only.
> That's all I can do for now.
> over to the experts ;)
It's hard for some extenders to work in all circumstances, esp. modern
machines. Clearly they weren't fully tested, and they make some weird
assumptions, probably because it mostly worked fine in common cases (e.g.
legacy Win9x). 16-bit DPMI was always quirky, says CWS, because it was
always relying on non-standard, undocumented int 21h extensions.
> btw. I still have some problems with XKEYB and other programs while
> JEMMEX is loaded
XKEYB is deprecated. Try Aitor's latest KEYB 2.01 bugfix instead, if
possible, it is preferred. Or even mKEYB if your needs are minimal.
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user
