dosemu 1.1.3.9 for testing

dosemu 1.1.3.9 for testing

[Bart Oldeman]

Hi,

it's at http://www.dosemu.org/testing. This should be the last testing
version before 1.1.4, the new development version.

Important things that changed from the user's perspective:
* 'make install' works again. It installs dosemu to locations
  specified in compiletime-settings; a FreeDOS tarball is optional
  (see compiletime-settings.help)
* setup-dosemu is broken (sorry, it needs adjustments to deal with the
  paths and I'm not able to fix it quickly). For now, just edit
  compiletime-settings* directly.
* for per-user installations:
  use ~/.dosemurc instead of ~/dosemu/conf/dosemu.conf and
  ~/dosemu/conf/dosemurc.
  boot.log is now in ~/.dosemu instead of ~/dosemu
* you can specify absolute paths for $_hdimage in dosemu.conf and
  ~/.dosemurc
* the default configuration files have everything commented out;
  DOSEMU uses default values if the options are not set (corresponding
  to the commented-out values).

Please let me know if anything is broken in the new 'make install'.

Bart

dosemu 1.1.3.9 user report

[Jan Willem Stumpel]

According to "top", 1.1.3.9 takes up 99 % CPU even when just
displaying the C:> prompt.

1.1.3.7 does this also; but 1.1.3.0 and 1.0.2.1 do not. They
hardly use any CPU when just displaying the prompt (or waiting for
a keystroke in a text-mode program).

Wolfenstein 3D:
1.0.2.1, 1.1.3.7, 1.1.3.9 play with $_sound = (off) .
1.1.3.0 hangs (with or without sound) after displaying the
start-up (setup) screen. Control-Alt-PgDn is the only way out.
1.1.3.7, 1.1.3.9 hang with $_sound = (on) .

Duke Nukem3D:
1.0.2.1 plays fine without sound.
1.1.3.0 plays without sound, but after a short while suddenly
disappears (no more dosemu window).
1.1.3.7, 1.1.3.9 play, with $_sound = (on) and soundblaster
selected in Duke Nukem Setup. I can see *and hear* the demo
(sounds, no music). When I want to start a game, I can select the
game type ("L.A. Meltdown" or whatever); however, when I try to
select the difficulty level the program hangs.

All this with kernel 2.2.18pre21, $_dpmi = (8192) , $_hogthreshold
= (800).

Regards, Jan

Re: dosemu 1.1.3.9 user report

[Peter Jay Salzman]

hi jan,

IIRC, there was talk about important dosemu related patches that are
present in the most recent kernels.   i think it was said that the
patches have been in the ac kernels for awhile, but have just recently
made it into the vanilla 2.4 kernels.

i have no idea what the patches do, but you can try using 2.4.20 and see
what happens.


btw, it sounds like you're playing in an xdos box.  have you been able
to play at all in console?

have you been able to have xdosemu grab the mouse?  i've been having
trouble playing redneck rampage because if the mouse "moves over" too
far left or right, the mouse leaves the xdos window.

pete



begin Jan Willem Stumpel <jstumpel@planet.nl> 
> According to "top", 1.1.3.9 takes up 99 % CPU even when just
> displaying the C:> prompt.
> 
> 1.1.3.7 does this also; but 1.1.3.0 and 1.0.2.1 do not. They
> hardly use any CPU when just displaying the prompt (or waiting for
> a keystroke in a text-mode program).
> 
> Wolfenstein 3D:
> 1.0.2.1, 1.1.3.7, 1.1.3.9 play with $_sound = (off) .
> 1.1.3.0 hangs (with or without sound) after displaying the
> start-up (setup) screen. Control-Alt-PgDn is the only way out.
> 1.1.3.7, 1.1.3.9 hang with $_sound = (on) .
> 
> Duke Nukem3D:
> 1.0.2.1 plays fine without sound.
> 1.1.3.0 plays without sound, but after a short while suddenly
> disappears (no more dosemu window).
> 1.1.3.7, 1.1.3.9 play, with $_sound = (on) and soundblaster
> selected in Duke Nukem Setup. I can see *and hear* the demo
> (sounds, no music). When I want to start a game, I can select the
> game type ("L.A. Meltdown" or whatever); however, when I try to
> select the difficulty level the program hangs.
> 
> All this with kernel 2.2.18pre21, $_dpmi = (8192) , $_hogthreshold
> = (800).
> 
> Regards, Jan
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 
First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D

Re: dosemu 1.1.3.9 user report

[Bart Oldeman]

On Mon, 16 Dec 2002, Peter Jay Salzman wrote:

> have you been able to have xdosemu grab the mouse?  i've been having
> trouble playing redneck rampage because if the mouse "moves over" too
> far left or right, the mouse leaves the xdos window.

try ctrl-alt-home. I noticed in your dosemu.conf that you uncommented the
mgrab_key setting, but it should work by default.

Bart

mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Peter Jay Salzman]

begin Bart Oldeman <oldeman@math.ohio-state.edu> 
> On Mon, 16 Dec 2002, Peter Jay Salzman wrote:
> 
> > have you been able to have xdosemu grab the mouse?  i've been having
> > trouble playing redneck rampage because if the mouse "moves over" too
> > far left or right, the mouse leaves the xdos window.
> 
> try ctrl-alt-home. I noticed in your dosemu.conf that you uncommented the
> mgrab_key setting, but it should work by default.
> 
> Bart
 

i guess enlightenment traps cntl-alt-home, because the key combo won't
let dosemu grab the mouse.

however, it DOES work with twm.

these are the only 2 wm's i use.   :)

also, running DOSEMU as your "window manager" by running "exec xdosemu"
from .xinitrc also works.  :)


pete

-- 
First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D

Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Stas Sergeev]

Hello.

Peter Jay Salzman wrote:
> i guess enlightenment traps cntl-alt-home, because the key combo won't
> let dosemu grab the mouse.
> however, it DOES work with twm.
Can you figure out a more reliable
combination then?
Set $_X_mgrab_key to, say, "Scroll_Lock"
or "Pause" and if there is something
that works everywhere, then I think the
default "Home" should be changed.

Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Bart Oldeman]

On Tue, 17 Dec 2002, Stas Sergeev wrote:

> Peter Jay Salzman wrote:
> > i guess enlightenment traps cntl-alt-home, because the key combo won't
> > let dosemu grab the mouse.
> > however, it DOES work with twm.
> Can you figure out a more reliable
> combination then?
> Set $_X_mgrab_key to, say, "Scroll_Lock"
> or "Pause" and if there is something
> that works everywhere, then I think the
> default "Home" should be changed.

Pause is already taken as being a force pause (freeze).
One problem is that you can define just about any keycombo in some of
these window managers, so there is nothing that works everywhere; however
some combinations are used more often than others.

ctrl+alt+scroll_lock might be something that makes sense though, since
you're locking the mouse. something to think about post-1.1.4 :)

For KDE I have ctrl+alt+esc (kill), ctrl+alt+del (logout).

Bart

Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Peter Jay Salzman]

omg.  getting dosemu has been bad for me.  i just spent the last 3 hours
playing non-stop redneck rampage.  :)

so far, it has been nearly flawless.  it runs better under dosemu on a
celeron 550 than it does under microsoft on a celeron 450 (my girlfriend
has a dual boot that i used to compare).

dosemu hung once in 3 hours of playing, but it didn't take out my
system.  i flipped to virtual console and killall'ed it.

holy moley.  thank you guys.  i really appreciate all the work you've
done!

begin Bart Oldeman <oldeman@math.ohio-state.edu> 
> On Tue, 17 Dec 2002, Stas Sergeev wrote:
> 
> > Peter Jay Salzman wrote:
> > > i guess enlightenment traps cntl-alt-home, because the key combo won't
> > > let dosemu grab the mouse.
> > > however, it DOES work with twm.
> > Can you figure out a more reliable
> > combination then?
> > Set $_X_mgrab_key to, say, "Scroll_Lock"
> > or "Pause" and if there is something
> > that works everywhere, then I think the
> > default "Home" should be changed.
> 
> Pause is already taken as being a force pause (freeze).
> One problem is that you can define just about any keycombo in some of
> these window managers, so there is nothing that works everywhere; however
> some combinations are used more often than others.

i'd have to agree.  i'm not hip onto all the window managers;
enlightenment and twm are the only ones i use.

btw, for gaming purposes (and i guess this is general, but is more
appropriate for gamers), placing the line:

exec xdosemu

in .xinitrc, restarting X, and using ctl-alt-+ to cycle through video
modes till xdosemu fills the entire screen gives the illusion of
fullscreen.

it's not *true* fullscreen in the sense of SDL's "fullscreen" bit when
you initialize SDL video, but honestly, you can't really tell the
difference.

> ctrl+alt+scroll_lock might be something that makes sense though, since
> you're locking the mouse. something to think about post-1.1.4 :)

i'm not sure if there's any safe keycombos to use, but frankly,
ctl-alt-home is pretty exotic.  i'd recommend keeping it or perhaps
using ctl-alt-scroll_lock, which is definitely more intuitive.
 
i know a lot of people who'd love to play these old games again, but
weren't able to get dosemu to run the games.  the doom in linux howto is
very good, but there's no reason why the advice applies just to doom.
most of it applies to all games.

i used that howto as a guide, but did other things like use a more
recent freedos and used 1.1.3.9 (which came out after the howto was last
updated).  i'm detailing everything i did in a general DOS gaming under
linux HOWTO.  i'll having something useful by this evening after i come
back from our local LUG meeting[1].

pete

[1]- funny story.  tonight the guest speaker is talking about C99.
while my friend was putting up flyers advertising the event, an asian
guy asked him what was going on.  they started talking, and it turns out
the guy is on the C99 standards committee.   :)   it's be cool if he
came to the meeting.  :)

-- 
First they ignore you, then they laugh at you, then they fight you,
then you win. -- Gandhi, being prophetic about Linux.

Fingerprint: B9F1 6CF3 47C4 7CD8 D33E 70A9 A3B9 1945 67EA 951D

Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Bart Oldeman]

On Mon, 16 Dec 2002, Peter Jay Salzman wrote:

> btw, for gaming purposes (and i guess this is general, but is more
> appropriate for gamers), placing the line:
>
> exec xdosemu
>
> in .xinitrc, restarting X, and using ctl-alt-+ to cycle through video
> modes till xdosemu fills the entire screen gives the illusion of
> fullscreen.

right, well you don't even have to edit .xinitrc to do this but you can do

xinit /usr/local/bin/xdosemu -- :1

or the following which can be faster if you usually use 24bpp in
the main X:

xinit /usr/local/bin/xdosemu -- :1 -depth 8

instead. For me this even works in an xterm. Maybe in some situations
you'll need to ctrl-alt-f1, log in, and then do this (if you normally
use X, that is). Using this command, xdosemu runs in VC 8.

"exitemu" even brings me back to my normal X -- nice :-)

Bart

Re: mouse grabbing gotcha (was: dosemu 1.1.3.9 user report)

[Stas Sergeev]

[-- Attachment #1: Type: text/plain, Size: 1005 bytes --]

Hello.

Bart Oldeman wrote:
>> default "Home" should be changed.
>  Pause is already taken as being a force pause (freeze).
But it doesn't actually work, it
just lock up dosemu in a non-TSC
mode unless the attached patch is
applied.

> One problem is that you can define just about any keycombo in some of
> these window managers, so there is nothing that works everywhere;
Well, there are either the combos
that are always reserved by some
WMs, and those can and should be
avoided.

> however some combinations are used more often than others.
User-defined combos is not something
we have to care about, that was not
what I mean.

> ctrl+alt+scroll_lock might be something that makes sense though, since
> you're locking the mouse.
The only disadvantage of it is that
it switches a scroll-lock led:)

> For KDE I have ctrl+alt+esc (kill), ctrl+alt+del (logout).
And you'll probably never know what
other combos it already reserved
without you even asking it about:)
I think dosemu can avoid using those.

[-- Attachment #2: cputime.diff --]
[-- Type: text/plain, Size: 1406 bytes --]

--- src/emu-i386/cputime.c	Mon Dec 16 00:45:12 2002
+++ src/emu-i386/cputime.c	Tue Dec 17 04:54:30 2002
@@ -181,7 +181,6 @@
      * but only flags processing (& other features) */
     RAWcpuTIME = rawP5time;		/* in usecs */
     GETcpuTIME = getP5time;		/* in usecs */
-    ZeroTimeBase.td = GETTSC();		/* in CPU cycles */
     g_printf("TIMER: using pentium timing\n");
   }
   else {
@@ -189,7 +188,6 @@
      * 'rdtsc off' into config file */
     RAWcpuTIME = rawC4time;		/* in usecs */
     GETcpuTIME = getC4time;		/* in usecs */
-    ZeroTimeBase.td = rawC4time();	/* in usecs */
     if (config.realcpu) {
       if (kernel_version_code < 0x2017e)
         g_printf("TIMER: using gettimeofday\n");
@@ -197,6 +195,7 @@
         g_printf("TIMER: using new gettimeofday with microsecond resolution\n");
     }
   }
+  ZeroTimeBase.td = RAWcpuTIME();
 }
 
 
@@ -208,7 +207,7 @@
   if (cpu_time_stop) return 1;
   if (!quiet) dbug_printf("STOP TIME\n");
   StopTimeBase = RAWcpuTIME();
-  LastTimeRead = StopTimeBase - TSCtoUS(ZeroTimeBase.td);
+  LastTimeRead = StopTimeBase - ZeroTimeBase.td;
   cpu_time_stop = 1;
   return 0;
 }
@@ -218,7 +217,7 @@
 {
   if (!cpu_time_stop) return 1;
   if (!quiet) dbug_printf("RESTART TIME\n");
-  ZeroTimeBase.td += ((RAWcpuTIME() - StopTimeBase) * config.CPUSpeedInMhz);
+  ZeroTimeBase.td += RAWcpuTIME() - StopTimeBase;
   cpu_time_stop = 0;
   return 0;
 }