Re: dosemu-1.1.3.5 for testing.
Compile problem: I've upgraded to RedHat 8.0 since the last time I compiled Dosemu. The error message is: make[3]: Entering directory `/home/lrs/dosemu-1.1.3/src/base/init' bison -y -v -do parser.c parser.y gcc -c -D_GNU_SOURCE -O2 -fomit-frame-pointer -MD -mcpu=i686 -fno-strict-aliasing -DGCC_VERSION_CODE=3002 -DASM_PEDANTIC -DGLIBC_VERSION_CODE=2003 -D_XOPEN_SOURCE -pipe -DUSING_NET -Wall -I/home/lrs/dosemu-1.1.3/src/plugin/kbd_unicode/include -I/home/lrs/dosemu-1.1.3/src/plugin/translate/include -I/home/lrs/dosemu-1.1.3/src/include -I/home/lrs/dosemu-1.1.3/src/dosext/dpmi -I/home/lrs/dosemu-1.1.3/src/include/slang -DYYPURE -o parser.o parser.c parser.y: In function `yyparse': parser.y:554: parse error before '}' token make[3]: *** [parser.o] Error 1 make[3]: Leaving directory `/home/lrs/dosemu-1.1.3/src/base/init' make[2]: *** [base/init] Error 2 make[2]: Leaving directory `/home/lrs/dosemu-1.1.3/src' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/lrs/dosemu-1.1.3' make: *** [default] Error 2 What is wrong here? Lars -- Lars Bjørndal [EMAIL PROTECTED] Storetveitåsen 15, 5067 Bergen. Tlf.: 55 28 87 55 Mobil: 958 37 537 Telefaks: 55 28 40 67 - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: dosemu-1.1.3.5 for testing.
Am Sonntag, 27. Oktober 2002 14:54 schrieb Lars Bjørndal: Compile problem: I've upgraded to RedHat 8.0 since the last time I compiled Dosemu. The error message is: make[3]: Entering directory `/home/lrs/dosemu-1.1.3/src/base/init' bison -y -v -do parser.c parser.y gcc -c -D_GNU_SOURCE -O2 -fomit-frame-pointer -MD -mcpu=i686 -fno-strict-aliasing -DGCC_VERSION_CODE=3002 -DASM_PEDANTIC -DGLIBC_VERSION_CODE=2003 -D_XOPEN_SOURCE -pipe -DUSING_NET -Wall -I/home/lrs/dosemu-1.1.3/src/plugin/kbd_unicode/include -I/home/lrs/dosemu-1.1.3/src/plugin/translate/include -I/home/lrs/dosemu-1.1.3/src/include -I/home/lrs/dosemu-1.1.3/src/dosext/dpmi -I/home/lrs/dosemu-1.1.3/src/include/slang -DYYPURE -o parser.o parser.c parser.y: In function `yyparse': parser.y:554: parse error before '}' token make[3]: *** [parser.o] Error 1 make[3]: Leaving directory `/home/lrs/dosemu-1.1.3/src/base/init' make[2]: *** [base/init] Error 2 make[2]: Leaving directory `/home/lrs/dosemu-1.1.3/src' make[1]: *** [default] Error 2 make[1]: Leaving directory `/home/lrs/dosemu-1.1.3' make: *** [default] Error 2 What is wrong here? Your yacc or bison is too new. There is an ; missing after config.pc = $2. If you edit parser.y in line 554 and put the ; in it, you can build your dosemu. Reinhard PS: Michael Karcher told me about the solution - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
How do I unpack the wp.exe-file? I've tried loadfix c:\wp51\wp.exe. Doing this command two times, results in the same error. Hartmut Figge [EMAIL PROTECTED] writes: [Stas Sergeev]: Btw, wp.exe is exepack'ed. To my memory exepack was a constant source of troubles (Packed file corrupt and the like things). That reminds me of old days, when some programms refused to work. Looking in the folder, in which ancient batch files resides, shows e.g. push.bat, which contains the line 'loadfix push'. That cured the problem with the 'corrupte file' and was the only way, to use that game. Full name was pushover, IIRC. Perhaps 'wp' could be tested with 'loadfix'. cu -- hafi - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html -- Lars Bjørndal [EMAIL PROTECTED] Storetveitåsen 15, 5067 Bergen. Tlf.: 55 28 87 55 Mobil: 958 37 537 Telefaks: 55 28 40 67 - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
Hello. Lars BjÛrndal wrote: I've noticed that if I use dosemu-1.0.1, the mem-command gives, in the line largest executable program size 617K, 1.1.3.5, the same command and config gives 611K. Why, do you think? I can recall only one change in a memory allocation algo of that times, which is this: http://marc.theaimsgroup.com/?l=linux-msdosm=99142972626428w=2 Even though it is very unlikely, still try to revert that patch and see if it helps. - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
Hello. Hartmut Figge wrote: Looking in the folder, in which ancient batch files resides, shows e.g. push.bat, which contains the line 'loadfix push'. That cured the problem with the 'corrupte file' and was the only way, to use that game. I don't agree. loadfix works around the exepack bugs by preventing the load to some specific memory regions, AFAIK. It doesn't *cure* the problem, because the real problem is an exepack's bugs and not the default DOS loader. The only real fix is to get rid of exepack entirely, which is to unpack an executable. Actually I am unpacking all of the executables I have here to avoid such a problems, but so far the only problematic packers were exepack and an old UPX. - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Bug in the latest version
[Stas Sergeev]: Hartmut Figge wrote: Looking in the folder, in which ancient batch files resides, shows e.g. push.bat, which contains the line 'loadfix push'. That cured the problem with the 'corrupte file' and was the only way, to use that game. I don't agree. loadfix works around the exepack bugs by preventing the load to some specific memory regions, AFAIK. It doesn't *cure* the problem, because the real problem is an exepack's bugs and not the default DOS loader. To clarify: it cured the problem with pushover. Or should i say, it circumvented the problem caused by exepack? Nevertheless, that has nothing to do with dosemu. It was a problem with some versions of MSDOS. IIRC, in any case, i got the 'corrupted file' message, i could run 'loadfix programm' and the problem went away. Of course, i had only tested a few of such programms, and there may be other programms without hope. Can we agree, that there are cases, in which loadfix will work? cu -- hafi - To unsubscribe from this list: send the line unsubscribe linux-msdos in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
