1.0.2.1 and latest kernel?

I just installed a new kernel, 2.4.23-pre4, and DOSEMU stable version 1.0.2.1 stopped working.

Hello.

Quoted 2 lines · Ryan Underwood

I just installed a new kernel, 2.4.23-pre4, and DOSEMU stable version 1.0.2.1 stopped working.

<offtopic>
May I just suggest you a better way of spending your free time? :)

There is another dos emulator there, called DosBox (was already popped up on that list recently). It seems to have a rather complete DPMI support, including the undocumented "MS-DOS" extension, which means it is intended to run the programs like bcc and winos2, which was a "secret weapon" of dosemu for years. Their DPMI source code looks very clean and promising:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/*checkout*/dosbox/dosbox/src/ints/dpmi.cpp?rev=HEAD&content-type=text/plain
but I am wondering if it really exceeds dosemu as it claims to be (which is deserved anyway).

Seems 1.1.5.7 no longer works with -pre4 either.

When running any dosemu command (such as lredir, exitemu, etc):
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool

Anyone know what is going on?

Quoted 3 lines · Ryan Underwood

Seems 1.1.5.7 no longer works with -pre4 either.

Quoted 5 lines

When running any dosemu command (such as lredir, exitemu, etc):
ERROR: lowmem_alloc failed for 10240
ERROR: Unable to allocate memory pool

Anyone know what is going on?

you forgot to update lredir.com and friends. Don't worry, the new versions are backwards compatible.

Hi,

While on the topic, is there a document that explains how to add a new configuration option? I have modified, parser.y, config.c, global.conf, and lexer.l and having a little trouble getting the new variable to be "seen". I grepped through the docs for "lexer" and "parser" but didn't see much useful right away.

Quoted 6 lines · Ryan Underwood

While on the topic, is there a document that explains how to add a new configuration option? I have modified, parser.y, config.c, global.conf, and lexer.l and having a little trouble getting the new variable to be "seen". I grepped through the docs for "lexer" and "parser" but didn't see much useful right away.

I take it from lack of response that nobody knows? :)

Just kidding, but I really have some problems implementing a new configuration option, so any hints would be helpful.

Quoted 8 lines · Ryan Underwood

Quoted 6 lines · Ryan Underwood

While on the topic, is there a document that explains how to add a new configuration option? I have modified, parser.y, config.c, global.conf, and lexer.l and having a little trouble getting the new variable to be "seen". I grepped through the docs for "lexer" and "parser" but didn't see much useful right away.

Quoted 4 lines

I take it from lack of response that nobody knows? :)

Just kidding, but I really have some problems implementing a new configuration option, so any hints would be helpful.

have a look at a small prepatch that does exactly that, eg. patch-1.1.5.5 added a $_lfn_support option.

Quoted 8 lines · Ryan Underwood

Quoted 6 lines · Ryan Underwood

While on the topic, is there a document that explains how to add a new configuration option? I have modified, parser.y, config.c, global.conf, and lexer.l and having a little trouble getting the new variable to be "seen". I grepped through the docs for "lexer" and "parser" but didn't see much useful right away.

Quoted 4 lines

I take it from lack of response that nobody knows? :)

Just kidding, but I really have some problems implementing a new configuration option, so any hints would be helpful.

have a look at a small prepatch that does exactly that, eg. patch-1.1.5.5 added a $_lfn_support option.

5. in global.conf, under checkuservar, I add $_delay_interval. In the parser_version_3 scope, I add:
delay_interval $_delay_intervala

Here is the procedure I undertook, to hopefully shed some more light:

1. First I added a new variable to the config struct in src/include/emu.h called delay_interval

2. in src/base/init/lexer.l.in:
delay_interval RETURN(DELAY_INTERVAL);

3. in src/base/init/parser.y.in:
%token DELAY_INTERVAL

4. in src/base/init/parser.y.in also:

	| DELAY_INTERVAL expression
		{
		c_printf("Hello, this is delay_interval speaking\n");
		}

5. in global.conf, under checkuservar, I add $_delay_interval. In the parser_version_3 scope, I add:
delay_interval $_delay_intervala

6. in dosemu.conf on my system, I add $_delay_interval = (1234)

7. I run the new dosemu.bin -D+C, and my c_printf is never displayed.

Any ideas?