>> 2. use Jemm386 instead of JemmEx and continue to use your previous
>> XMS host.
>>
>> 3. JemmEx's source can be extended to be able to manage more than
>> one block. This means some work, because the current implementation
>> isn't very flexible.
>
> Nothing wrong in my fdconfig.sys?
> JEMMEX.E
> Sorry for long responce. I was update Jemm, because previous version
> have no xmsstat. The xmsstat output attached as memstat.zip.
the report for Jemm did display
no handle regionsize(kB) locks flags
1 00A8 0011-0
>> Try to use no or another emm386: FreeDOS EMM386, JEMM386, JEMMEX?
>> Also read the docs for the "compatible safe" settings :-)
>
> Hmm. With an 'jemmex' i've got some gifts: more free conventional
> memory (about +3 kb.) and Nautilus works VERY WELL in this
> configuration. However, I lost some
Sat, 4 Oct 2008 23:05:07 +0200 (MEST) Eric Auer пишет:
> > Will be 100% crash when 'NAUTILUS_CONFIG_FILE' variable are set or
> > '-s ' (port lock speed) and sometimes '-e ' (cipher)
> > arguments are present in command line.
>
> What do the -s ARG and -e ARG options "port lock speed" and "ciphe
Hi!
> I have many silent and verbose crashes with Nautilus Digital Voice
> Communicator -- Version 1.5a. However, in the same time Nautilus works
> very well in DR-DOS.
Hmm okay.
> Will be 100% crash when 'NAUTILUS_CONFIG_FILE' variable are set or '-s
> ' (port lock speed) and sometimes '-e ' (
Hello.
I have many silent and verbose crashes with Nautilus Digital Voice
Communicator -- Version 1.5a. However, in the same time Nautilus works
very well in DR-DOS.
Will be 100% crash when 'NAUTILUS_CONFIG_FILE' variable are set or '-s
' (port lock speed) and sometimes '-e ' (cipher) argument
