I can answer your first question; set raw_keyboard=(1) or something like
that in your dosemu.conf file.
On Sat, 7 Aug 1999, Gereon Ruetten wrote:
> Hi,
>
> first of all I want to say you all did a great job, dosemu is really
> great...
>
> I try to run a big Dos Application under Dosemu and there are two
> problems
> i can't solve.
>
> 1.) The dos-Application uses <ALT-Fx> and <STRG-Fx> keys... how can i
> configure
> my linux that i can use them (most run with dos not xdos) ? I played
> a
> little bit with loadkeys and was able to make linux not to switch
> the
> Consoles while pressing <ALT-Fx>, but the keystroke isnt realized by
> the
> dos-application
>
> 2.) This DOS-Application should run about 30 times per linuxbox. This
> Application is written in C/C++ and compiled with watcom compiler
> in protected mode, most time the application has to wait on
> keystrokes
> so the programmer tried to give the idle-cpu time back, but the the
> clock runs only at about the halfspeed... Time is extremly important
> in
> thios application so i cant ignore that.
> The Programmer uses following function :
>
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
> > INT 2F - MS Windows, DPMI, various - RELEASE CURRENT VIRTUAL MACHINE
> > TIME-SLICE
> > AX = 1680h
> > Return: AL = status
> > 00h if the call is supported
> > 80h (unchanged) if the call is not supported
> > Notes: programs can use this function in idle loops to enhance performance
> > under multitaskers; this call is supported by MS Windows 3+, DOS 5+,
> > DPMI 1.0+, and in OS/2 2.0+ for multitasking DOS applications
> > does not block the program; it just gives up the remainder of the time
> > slice
> > should not be used by Windows-specific programs
> > when called very often without intermediate screen output under
> > MS Windows 3.x, the VM will go into an idle-state and will not
> > receive the next slice before 8 seconds have elapsed. This time can
> > be changed in SYSTEM.INI through "IdleVMWakeUpTime=<seconds>".
> > Setting it to zero results in a long wait.
> > this function has no effect under OS/2 2.10-4.0 if the DOS box has an
> > "Idle Sensitivity" setting of 100
> > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
>
> this problem didnt exist while running under real Win9x or NT.
>
> If you want i can post you a test-program
>
> the really strange thing is :
>
> - start dosemu
> - look at the time (dos-command time)
> - start the testprogram
> - clock works slower
> - after a while i stop the testprogram, the time is e.g. 5 min.
> after theright time
> - start once again dos-command "time" and get the correct (!) time
>
>
> when i set
>
> $_hogthreshold = (0)
>
> the clock works fine, but the process uses all of my cpu-time :-(
>
>
> I tried the last stable version of dosemu and also the last developer
> release...
>
>
> Gereon
>
