1.0.2.1 and latest kernel?

1.0.2.1 and latest kernel?

[Ryan Underwood]

Hi,

I just installed a new kernel, 2.4.23-pre4, and DOSEMU stable version
1.0.2.1 stopped working.  I have tried to boot freedos and msdos, and
both of them crash DOSEMU early in the boot process with strange errors.

Can anyone else duplicate this problem?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?

[Stas Sergeev]

Hello.

Ryan Underwood wrote:
> 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).
So, as you seem to have some spare time left
(otherwise why would you start fiddling with
1.0.2?:), it would be very nice if you try
how good is DosBox's DPMI support compared to
the one of dosemu (but not 1.0.2) and let us
know.
</offtopic>

Re: 1.0.2.1 and latest kernel?

[Ryan Underwood]

Hi,

On Tue, Sep 16, 2003 at 07:29:03AM +0400, Stas Sergeev wrote:
> Hello.
> 
> Ryan Underwood wrote:
> >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 was a request that I post the details of how to work DOSEMU
through an inetd connection.  I couldn't get my old method to work with the
latest version, so I was trying the stable version, which I was sure had
worked at soem point.  However, it doesn't seem to work anymore on the
new kernel :(

> 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).

Ok, I will take a look at it.  In the meantime, I really would like to
know if anyone gets 1.0.2.1 to work with the latest kernel, and the
precise kernel version which broke it would be helpful.


-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

Hmm,

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?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Bart Oldeman]

On Tue, 16 Sep 2003, Ryan Underwood wrote:

>
> 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?

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

Bart

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

Hi Bart,

On Tue, Sep 16, 2003 at 10:12:47AM +0100, Bart Oldeman wrote:
> On Tue, 16 Sep 2003, Ryan Underwood wrote:
> 
> >
> > 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?
> 
> you forgot to update lredir.com and friends. Don't worry, the new versions
> are backwards compatible.

Yep, I just discovered that too. thanks.

Back to hacking...

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

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.

Thanks,

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?

[Stas Sergeev]

Hello.

Ryan Underwood wrote:
> There was a request that I post the details of how to work DOSEMU 
> through an inetd connection.  I couldn't get my old method to work
>  with the latest version, so I was trying the stable version, which
>  I was sure had worked at soem point.
OK, I see.
You can't get that working on the recent
dosemu because that was explicitly prohibited
in the parser.
But please have a look into a parser.y:1314
of dosemu 1.0.2. strcpy(sptr->dev, ttyname(0))
is there and should segfault when the FD 0
is referring not to a tty and the virtual modem
is attempted to be used on it.

> In the meantime, I really would like to know if anyone gets 1.0.2.1
> to work with the latest kernel, and the precise kernel version
> which broke it would be helpful.
I've heard about a major changes done in 2.4
kernels recently, mostly VM-related. It would
be good to figure out what was broken, but
perhaps the things are just not settled down
yet after that changes.

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

Hi,

On Tue, Sep 16, 2003 at 04:33:50AM -0500, Ryan Underwood wrote:
> 
> 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.

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.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Bart Oldeman]

On Thu, 18 Sep 2003, Ryan Underwood wrote:

> On Tue, Sep 16, 2003 at 04:33:50AM -0500, Ryan Underwood wrote:
> >
> > 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.

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

Bart

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

Hi,

On Thu, Sep 18, 2003 at 12:52:41PM +0100, Bart Oldeman wrote:
> On Thu, 18 Sep 2003, Ryan Underwood wrote:
> 
> > On Tue, Sep 16, 2003 at 04:33:50AM -0500, Ryan Underwood wrote:
> > >
> > > 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.
> 
> have a look at a small prepatch that does exactly that, eg. patch-1.1.5.5
> added a $_lfn_support option.

Thanks for the pointer.  I still don't see what I missed now, but that
will help track it down.

Ryans Todo List:
- slowdown kludges
- document telnetting to dosemu application on inetd
- update Win3.11-DOSEMU HOWTO
- libsynthchip for OPL emulation at least
- dos emulator compatibility/regression database
- ALSA driver for sound/midi

By the way I also patched the Synchronet BBS software for DOSEMU
integration -- the result can be found at:
http://forge.icequake.net/syncmods

What are some other stuff that needs to be worked on that a DOS guy but
not DOS guru can do?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

Hi,

On Thu, Sep 18, 2003 at 12:52:41PM +0100, Bart Oldeman wrote:
> On Thu, 18 Sep 2003, Ryan Underwood wrote:
> 
> > On Tue, Sep 16, 2003 at 04:33:50AM -0500, Ryan Underwood wrote:
> > >
> > > 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.
> 
> have a look at a small prepatch that does exactly that, eg. patch-1.1.5.5
> added a $_lfn_support option.

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?

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Ryan Underwood]

On Thu, Sep 18, 2003 at 11:26:54PM -0500, Ryan Underwood wrote:
> 
> 5. in global.conf, under checkuservar, I add $_delay_interval.
> In the parser_version_3 scope, I add:
> delay_interval $_delay_intervala
                            -----^
Obviously, a typo.

-- 
Ryan Underwood, <nemesis at icequake.net>, icq=10317253

Re: 1.0.2.1 and latest kernel?a [1.1.5.7 now]

[Bart Oldeman]

On Thu, 18 Sep 2003, Ryan Underwood wrote:

> 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?

sounds about right; maybe there's something obscure. Try a "warn" in
global.conf, and the options
-h2 -D+cw -O
(not -D+C but small c) for some more clues. Also _delay_interval should
show up in "unix set" and "system set" typed from the DOS prompt.

The difference between () and "" is in global.conf. Numbers from ()
you can add, multiply, compare and so on; on strings you can use strlen
and so on. See also README-tech.txt.

Bart