Re: [Freedos-user] Application crash
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-00138FFF 164 1 02 used 2 00B2 00139000-00158FFF 128 1 02 used 3 00BC 00159000-002D8FFF 1536 1 02 used 4 00C6 002D9000-00558FFF 2560 0 02 used 5 00D0 00559000-00958FFF 4096 1 02 used 6 00DA 00959000-009933FF 233 0 02 used 7 00E4 00993400-00995BFF 10 0 02 used 8 00EE 00995C00-00A95BFF 1024 0 02 used 9 00F8 00A95C00-00E5A3FF 3858 0 02 used 10 0102 00E5A400-00EF 663 0 01 free so the extended memory managed by Jemm is from 10h-EF only (14 MB). This might be due to a memory hole of size 1 MB at F0-FF. JemmEx, FD Himem and HimemX have a restriction: they can handle ONE extended memory block only. There are 3 options now: 1. try to disable the hole. Some BIOSes allow to enable/disable the memory hole in the setup. 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. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Application crash
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.EXE A20 ALTBOOT I=TEST X=TEST S=C800-EFFF XMSHANDLES=32 SB EMX VERBOSE No. This isn't a problem of wrong command line options. If your BIOS doesn't allow you to disable the hole, try option 2. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Application crash
Sat, 4 Oct 2008 23:05:07 +0200 (MEST) Eric Auer пишет: Will be 100% crash when 'NAUTILUS_CONFIG_FILE' variable are set or '-s arg' (port lock speed) and sometimes '-e arg' (cipher) arguments are present in command line. What do the -s ARG and -e ARG options port lock speed and cipher do exactly? Are they documented to be harder for DOS or hardware? -e Encryption can be specified using the -e option and following it with the name of the specified cipher or NONE to turn encryption off. Note that if the -e option is not specified, Nautilus will use the Blowfish cipher by default. To get a list of available ciphers, use the -l ciphers option. -s If you wish to change the default DTE speed from 19,200 to a higher value, use the -s option followed by the speed you wish to use. '-s' are most problem option. When '-s ...' missing in command line, nautilus will use default DTE speed - 19200. He will start-up and work, however, on exit I got: Invalid Opcode at 5a38 978b 0202 59ba 4689 89e2 e456 c02b 4689 89f2 f046 4639 7dfe. run-time error M6111: MATH - floating-point error: stack underflow Invalid Opcode at 0108 0017 00D0 037C 058E 00D0 1B04 08E4 DB1D 00D0 6698 00D0 Hmmm floating point stack underflow or stack underflow? You can try a few of the following: STACKS=9,256 (or at most 16,384) instead of the 0,0 default OK, I set STACKShigh=9,256 Run CALC387 to check if your floating point behaves okay in FreeDOS in general - maybe also useful to use it at all before you run Nautilus Digital Voice Communicator...? Might be that DR DOS does some init which FreeDOS does not but CALC387 does? I have no 'CALC387' at this time, but I will see on freedos.org for that. 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 something: 1) Free XMS now = 633 Kb, SRDXMS disk = 6Mb. Should be about 45Mb free XMS with 262Mb SRDXMS disk. 2) My favorite games complain about 'not enough memory'. Should I reboot and switch FreeDOS boot configuration from time to time when I need Nautilus or games?.. ;-( -- D.A. id 0xC4D22CDD fp 8F52 8619 6918 DAE3 5E61 3146 C89F BDB8 C4D2 2CDD - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
Re: [Freedos-user] Application crash
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 arg' (port lock speed) and sometimes '-e arg' (cipher) arguments are present in command line. What do the -s ARG and -e ARG options port lock speed and cipher do exactly? Are they documented to be harder for DOS or hardware? run-time error M6111: MATH - floating-point error: stack underflow Invalid Opcode at 0108 0017 00D0 037C 058E 00D0 1B04 08E4 DB1D 00D0 6698 00D0 Hmmm floating point stack underflow or stack underflow? You can try a few of the following: STACKS=9,256 (or at most 16,384) instead of the 0,0 default Run CALC387 to check if your floating point behaves okay in FreeDOS in general - maybe also useful to use it at all before you run Nautilus Digital Voice Communicator...? Might be that DR DOS does some init which FreeDOS does not but CALC387 does? Try to use no or another emm386: FreeDOS EMM386, JEMM386, JEMMEX? Also read the docs for the compatible safe settings :-) Eric - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/ ___ Freedos-user mailing list Freedos-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-user
