1. Using XShm in X-dosemu --- something fishy here?
I know it's not good style to post about work-in-progress on an
app to c.o.l.d.s, but I think this might actually be kernel related....
I grabbed the latest development version of dosemu a couple of days
ago, and WOW was I impressed with the feature list. It took me quite
some time to make it like my 1.3.61 kernel, though, but when I finally
got it compiled, lo and behold, not only did it run Duke Nukem 3D
(even dosemu 0.60.2 could do that), but it did so in an X window,
at a very decent frame rate.
Now I immediately looked through the code and noticed that dosemu
doesn't use the Shared Memory extension of X, resulting in about
50% system time when run with the fastest screen update --- in effect,
it pushes a very big ximage through a network socket many many times
I then took a look at what mpeg_play and xanim do to use that extension
and tried to put it into dosemu. The basic work took about an hour,
incuding the time to "learn" how to do it. Recompiled, started,
BOOOOOM. It went down in flames, saying it had received a processor
exception outside vm86 mode --- which I think is just a fancy way of
saying "Segmentation violation". I then spent the next 7 hours
looking for the where and why --- and I have located the where (it
happens when the program asks the server for the extension, which
is the first ever call having anything to do with shared memory),
but am still completely baffled as to the why.
I first suspected my libs were all messed up, so I cleaned out every-
thing X related and reinstalled from the XFree 3.1.1 binary distribution.
No change. I then went through all the hacks to get emumodule to be
accepted by the kernel, changed the one that looked suspicious,
recompiled the kernel, restarted --- no change. I then became a bit
desparate and compiled xanim from the sources, to see whether something
elemental was broken on my system --- worked like a charm, and used the
exact same libraries.
So what I am asking is --- is there anything about dosemu that makes
the use of the XShm extension impossible? Something about the vm86
mode, perhaps, or some strange memory remapping? And maybe could some
of the people for whom dosemu in a window works put in just the test
for the extension to see whether it bombs out for them, too?
I'd really love to see dosemu's X support go shared memory, because that
way we could have real great performance even when running on the
2. mkfile in RH advanced server 2.1?
3. Problem : Wordperfect +mouse in xdos
4. need some advice regarding application design
5. FAQ for WordPerfect? Problems with WordPerfect!
6. Possible to copy only dirctory structures
7. Wordperfect 6.0 under DOSEMU
8. Sending and reading reset codes from keyboard?
9. Running the Dos version of WordPerfect Office under DOSEMU
10. Dosemu and wordperfect
11. mouse problem in DOSEMU enviornment
12. Dosemu Mouse Problem
13. DOSEmu and Logitech mouse problem