Skip to contentSkip to conversation

dosemu-1.3.3

announce Alain 2 participants 3 messages Dec 30, 2005 – Dec 31, 2005

lore
Share & tools
lore

Alain

author
#0 lore raw

Hi Bart,

I erroneously sent this to your return address an it appears that it got lost, so I am repeating it here...

I am having a very bad keyboard behaviour since I moved to Mandriva 2006. I tested dosemu 1.3.2 but it doesn't compile any more :( and CVS november 28 version is the same.

I have made some real improuvements changing the check_key_available() function in int16.c and the delay calls.

Please tell me where to find the INT 2fh function 1680h, there might be something to be done there too.

Most affected programs are NDN, Setedit and BC31 (only compile time, editor is ok)

Up to now I using basicaly my DOS knowledge, I will probably need more specific dosemu later,

thanks,
Alain

#1 lore raw
Quoted 2 lines · Alain

I have made some real improuvements changing the check_key_available() function in int16.c and the delay calls.

The delay calls have also changed in CVS after 1.3.3 so you might want to update that again (src/emu-i386/cputime.c). The delays were a bit too long and were not interrupted by signals. But if you still have problems even with "speed 0" that won't help.

http://sourceforge.net/tracker/index.php?func=detail&aid=1387967&group_id=49784&atid=457447

shows that issue.

Quoted 2 lines

Please tell me where to find the INT 2fh function 1680h, there might be something to be done there too.

"grep" is your friend. src/base/async/int.c

Bart

author
#2 lore raw

Hi Bart,

Quoted 4 lines
Quoted 2 lines

I have made some real improuvements changing the check_key_available() function in int16.c and the delay calls.

The delay calls have also changed in CVS after 1.3.3 so you might want to update that again (src/emu-i386/cputime.c).

I will check, is it suposed to change again?

Quoted 1 line

But if you still have problems even with "speed 0" that won't help.

speed 0 is ok, even something like speed form 2 to sometimes 4. BUT, in both cases I get 98% cpu usage.

Quoted 1 line

"grep" is your friend.

Only if you are lost in the forrest XOR you have a lamp, but not both ;-)

Thaks and Happy new year,
Alain