Subj : dosemu2 configuration instructions
To   : all
From : ner
Date : Thu Oct 19 2023 21:45:20

All,

I'm running the latest version of 2.0 pre9 for dosemu2.  I followed the wiki,
and things didn't go too well. Here's what I had to ensure if it helps anyone
else. I also wanted to know if anyone experienced this.
I had to make sure that the cmd keys were all on one line. If that's not done,
then it won't run the command
With the dosemu.ini changes that are quoted in the wiki, when I ran a door, I
got all of the boot trash you get when you run dosemu by itself. This is great
for debug, and for seeing versions and such, but isn't great when you just want
the user to see the game start.
The command key conatains a "QUIET=1" value. Whether or not it is 0 or 1,
output remains the same. However, after checking the /usr/bin/dosemu wrapper
script, I fonud that the -quiet switch (-q in dosemu) runs the following
command and must be added to both keys
-tde -ks -exec 2>/dev/null
Nasty but true, and it's how the script runs it.
Running this way sets terminal to dumb and then pipes some content to
/dev/null.  Also note, it takes about 1.5 to two seconds to run a door this
way.
Is there an easier way to get quiet output, or am I doing the right thing? I
can say that this setup is working for the games I'm using--I'm slowly adding
more, and if I find some that don't work, I'll let you know. I do believe I've
decrypted the new command line options (undocumented I might add for some of
them.

Thanks all.

NER
NER BBS
--- SBBSecho 3.20-Linux
 * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

.