Skip to contentSkip to conversation

Dosemu and clipper applications eating all CPU

DISCUSSION Stas Sergeev 2 participants 3 messages Mar 10, 2004 – Mar 11, 2004

lore
Share & tools
lore
#0 lore raw

Hello.

Quoted 4 lines · Maximiliano Curia
Quoted 3 lines

Problem of clipper I presume? If it
just runs in a busy loop while idle,
dosemu can't really help.

Yes, that dosemu doesn't detect the clipper idle calls.

But *what kind* of idle calls? This is the vital info. If you can't find the answer, then the problem can't be fixed:)
int 0x28 is the real idle call, but since dosemu catches that, I suspect clipper does something else.

Quoted 2 lines

It still eats the cpu, with nice -n 19, but now the 60% is marked as nice.

Yes, and the system must not be crawled now at least. At least in a theory:)

Quoted 1 line

I'm trying to understand the freedos idle.

That might be not the case either. FreeDOS can just call int16 to do a blocking wait for a keypress, and that will do the trick.
You have to find out what exactly the clipper does however.

#1 lore raw

Stas,

clipper calls time-of-day interrupt when idle, don't have right number of interrupt call here at home, but I did write some years ago a little TSR to release cpu under OS/2 and I'm using a home-made dosemu 1.0.x at work with a changed handling of this interrupt call inside dosemu code, tomorrow I'll tell you the right call.

regards.

Quoted 40 lines · Stas Sergeev

Hello.

Quoted 5 lines · Maximiliano Curia
Quoted 3 lines

Problem of clipper I presume? If it
just runs in a busy loop while idle,
dosemu can't really help.

Yes, that dosemu doesn't detect the clipper idle calls.

But *what kind* of idle calls?
This is the vital info. If you
can't find the answer, then the
problem can't be fixed:)
int 0x28 is the real idle call,
but since dosemu catches that,
I suspect clipper does something
else.

Quoted 2 lines

It still eats the cpu, with nice -n 19, but now the 60% is marked as nice.

Yes, and the system must not be
crawled now at least. At least in
a theory:)

Quoted 1 line

I'm trying to understand the freedos idle.

That might be not the case either.
FreeDOS can just call int16 to do
a blocking wait for a keypress, and
that will do the trick.
You have to find out what exactly
the clipper does however.
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

Signature · 3 lines
__________
|  |  | |__|  Maurilio Longo
|_|_|_|____| 
#2 lore raw

Hi,

clipper runtimes calls int 0x21 sub-function 0x2C, I intercept this one and issue a usleep().

I had to change INT2F_IDLE_SEC to INT28_IDLE_SEC and call usleep() only every 50 times this function gets called or else I had a sluggish dos application. (I set hog_threshold to 0)

regards.

Maurilio Longo ha scritto:

Quoted 55 lines

Stas,

clipper calls time-of-day interrupt when idle, don't have right number of interrupt call here at home, but I did write some years ago a little TSR to release cpu under OS/2 and I'm using a home-made dosemu 1.0.x at work with a changed handling of this interrupt call inside dosemu code, tomorrow I'll tell you the right call.

regards.

Quoted 29 lines · Stas Sergeev

Hello.

Quoted 5 lines · Maximiliano Curia
Quoted 3 lines

Problem of clipper I presume? If it
just runs in a busy loop while idle,
dosemu can't really help.

Yes, that dosemu doesn't detect the clipper idle calls.

But *what kind* of idle calls?
This is the vital info. If you
can't find the answer, then the
problem can't be fixed:)
int 0x28 is the real idle call,
but since dosemu catches that,
I suspect clipper does something
else.

Quoted 2 lines

It still eats the cpu, with nice -n 19, but now the 60% is marked as nice.

Yes, and the system must not be
crawled now at least. At least in
a theory:)

Quoted 1 line

I'm trying to understand the freedos idle.

Quoted 11 lines

That might be not the case either.
FreeDOS can just call int16 to do
a blocking wait for a keypress, and
that will do the trick.
You have to find out what exactly
the clipper does however.
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
__________

Quoted 7 lines
|  |  | |__|  Maurilio Longo
|_|_|_|____|

-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html

--
__________

|  |  | |__| [email protected]
|_|_|_|____| Team OS/2 Italia