Skip to contentSkip to conversation

High Temperature with DOSEMU

DISCUSSION Hayen Iggena 5 participants 10 messages Nov 22, 2007 – Nov 23, 2007

lore
Share & tools
lore
#0 lore raw

Hallo!

I´m using a very old DOS Programm in my office which I´ve written in Nantucket-Clipper 20 years ago . In former times it run well in a Dos Window on OS/2. But now I get a new computer with Suse Linux 10.3. The programm runs good in DOSEMU but "top" tells me it consume nearly 99.9% CPU. And afte a short time the temperature alarm of my computer is ringing. I tried to change HogThreshold but even with "1" I´ve a system load of more than 98%. Same if i use "Speed" in Dosemu.

How can I fix this?

Hayen
-
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

#1 lore raw

Hi,

there is no easy fix. The problem basicaly is that Clipper does not call dos to wait for user input, it keeps running in a loop. The result is that even if HogThreshold is 1, all unused cpu goes back to dosemu.

There is (somewhere, I don't know) a small lib for clipper that changes that behaviour. As you said that you wrote the program, you can re-link it with that.

In the mean time, all you can do is buy a better cooler, that excess heating may happen for other reasons too ;-)

Win98 had a workaround for that, but even XP doesn't. Neither does doesmu...

Alain

Hayen Iggena escreveu:

Quoted 10 lines

Hallo!

I´m using a very old DOS Programm in my office which I´ve written in Nantucket-Clipper 20 years ago . In former times it run well in a Dos Window on OS/2. But now I get a new computer with Suse Linux 10.3. The programm runs good in DOSEMU but "top" tells me it consume nearly 99.9% CPU. And afte a short time the temperature alarm of my computer is ringing. I tried to change HogThreshold but even with "1" I´ve a system load of more than 98%. Same if i use "Speed" in Dosemu.

Quoted 9 lines

How can I fix this?

Hayen
-
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

-
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

#2 lore raw
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

"Alain" == Alain M <[email protected]> writes:

Alain> Hi, there is no easy fix. The problem basicaly is that Alain> Clipper does not call dos to wait for user input, it Alain> keeps running in a loop. The result is that even if Alain> HogThreshold is 1, all unused cpu goes back to dosemu.

Alain> There is (somewhere, I don't know) a small lib for Alain> clipper that changes that behaviour. As you said that Alain> you wrote the program, you can re-link it with that.

Alain> In the mean time, all you can do is buy a better Alain> cooler, that excess heating may happen for other Alain> reasons too ;-)

There's also a little DOS TSR tame www.tamedos.com which monitors a DOS program in different ways and notifies the underlying OS in different ways.

#3 lore raw
Quoted 12 lines · Jonathan Goldblatt
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

"Alain" == Alain M <[email protected]> writes:

Alain> Hi, there is no easy fix. The problem basicaly is that Alain> Clipper does not call dos to wait for user input, it Alain> keeps running in a loop. The result is that even if Alain> HogThreshold is 1, all unused cpu goes back to dosemu.

Alain> There is (somewhere, I don't know) a small lib for Alain> clipper that changes that behaviour. As you said that Alain> you wrote the program, you can re-link it with that.

Quoted 9 lines

Alain> In the mean time, all you can do is buy a better Alain> cooler, that excess heating may happen for other Alain> reasons too ;-)

There's also a little DOS TSR tame www.tamedos.com which monitors a DOS program in different ways and notifies the underlying OS in different ways.

I can get tame only for Windows. I'm using Linux.

Does anyone know where I can get the special Clipper lib?

begin:vcard
fn:Hayen Iggena
n:Iggena;Hayen
adr:;;Westerstr. 8;Esens;;26427;Deutschland
email;internet:[email protected]
version:2.1
end:vcard

#5 lore raw
In reply to Hayen Iggena

Hi Hayen,

please follow this link:

http://www.engwall.com/clipper/nfpat1a.htm

Here you find a little function to include into your clipper program and the problem is gone. I use it with great success since many years.

HTH
Klemens

----- Original Message -----
From: "Hayen Iggena" <[email protected]>
To: <[email protected]>
Sent: Thursday, November 22, 2007 10:36 PM
Subject: High Temperature with DOSEMU

Quoted 7 lines

Hallo!

I´m using a very old DOS Programm in my office which I´ve written in Nantucket-Clipper 20 years ago . In former times it run well in a Dos Window on OS/2. But now I get a new computer with Suse Linux 10.3. The programm runs good in DOSEMU but "top" tells me it consume nearly 99.9% CPU. And afte a short time the temperature alarm of my computer is

ringing.

Quoted 11 lines

I tried to change HogThreshold but even with "1" I´ve a system load of more than 98%. Same if i use "Speed" in Dosemu.

How can I fix this?

Hayen
-
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

-
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

#6 lore raw
Quoted 9 lines · Klemens Lichter (via GMX)

Hi Hayen,

please follow this link:

http://www.engwall.com/clipper/nfpat1a.htm

Here you find a little function to include into your clipper program and the problem is gone. I use it with great success since many years.

Thanks for the link.
I've tried to compile my programm. But if I start the executable Dosemu crash. I got these messages in the console:
/ERROR: SMALLOC: bad pointer passed to smfree()
ERROR: SMALLOC: Out Of Memory on alloc, requested=102400
ERROR: general protection at 0x7d9: 67/

What ist wrong?

Hayen

begin:vcard
fn:Hayen Iggena
n:Iggena;Hayen
adr:;;Westerstr. 8;Esens;;26427;Deutschland
email;internet:[email protected]
version:2.1
end:vcard

#7 lore raw

Hayen,
what linker do you use? I use Exospace fpr Clipper 5.3 and RTLink for 5.0

You should have the follogin lines inside your .LNK file:

FILE ..\iamidle.obj
LIB ...\nanfor
LIB ...\cpmi

I think all these is needed for. It is so long time since I included this to my projects and than never again thought about.

Another tip: this "iamidle" does not like the clipper debugger. So I have the very first lines of my first starting procedure in every project:

#ifndef DEBUG
ft_onidle({|| ft_iamidle(30,.T.)})
#endif

While debugging there is high cpu using, but not while the program is in its normal run.

Klemens

----- Original Message -----
From: "Hayen Iggena" <[email protected]>
To: "Klemens Lichter (via GMX)" <[email protected]>; <[email protected]>
Sent: Friday, November 23, 2007 11:05 AM
Subject: Re: High Temperature with DOSEMU

Quoted 8 lines
Quoted 7 lines · Klemens Lichter (via GMX)

Hi Hayen,

please follow this link:

http://www.engwall.com/clipper/nfpat1a.htm

Here you find a little function to include into your clipper program and

the

Quoted 13 lines
Quoted 2 lines

problem is gone. I use it with great success since many years.

Thanks for the link.
I've tried to compile my programm. But if I start the executable Dosemu crash. I got these messages in the console:
/ERROR: SMALLOC: bad pointer passed to smfree()
ERROR: SMALLOC: Out Of Memory on alloc, requested=102400
ERROR: general protection at 0x7d9: 67/

What ist wrong?

Hayen

#8 lore raw

Hi!

It works! Thank you!
The problem is that I compiled the programm on my laptop. If I start it Dosemu crashes or the programm stop at the line with the new function. But on the computer in my office the programm works well in Dosemu and system load is near 0%.

Hayen

Quoted 25 lines · Klemens Lichter (via GMX)

Hayen,
what linker do you use? I use Exospace fpr Clipper 5.3 and RTLink for 5.0

You should have the follogin lines inside your .LNK file:

FILE ..\iamidle.obj
LIB ...\nanfor
LIB ...\cpmi

I think all these is needed for. It is so long time since I included this to my projects and than never again thought about.

Another tip: this "iamidle" does not like the clipper debugger. So I have the very first lines of my first starting procedure in every project:

#ifndef DEBUG
   ft_onidle({|| ft_iamidle(30,.T.)})

#endif

While debugging there is high cpu using, but not while the program is in its normal run.

Klemens

Signature · 6 lines
Hayen Iggena
Zahnarzt
Westerstr. 8
26427 Esens
Tel.:04971-2444
Fax:04971-7426

begin:vcard
fn:Hayen Iggena
n:Iggena;Hayen
adr:;;Westerstr. 8;Esens;;26427;Deutschland
email;internet:[email protected]
version:2.1
end:vcard

#9 lore raw

That is the way that "should" work. I am glad to know that it does. External (to clipper) program don't work for clipper because the problem is inside clipper, there are other programs that do this too including some but not all Borland IDEs.

As to not working in some places, please keep us informed and if possible, I beg you to post a final and complete solution when you find it.

BTW, there are other similar programs, maybe you have luck and find another one...

Alain

Hayen Iggena escreveu:

Quoted 38 lines

Hi!

It works! Thank you!
The problem is that I compiled the programm on my laptop. If I start it Dosemu crashes or the programm stop at the line with the new function. But on the computer in my office the programm works well in Dosemu and system load is near 0%.

Hayen

Quoted 25 lines · Klemens Lichter (via GMX)

Hayen,
what linker do you use? I use Exospace fpr Clipper 5.3 and RTLink for 5.0

You should have the follogin lines inside your .LNK file:

FILE ..\iamidle.obj
LIB ...\nanfor
LIB ...\cpmi

I think all these is needed for. It is so long time since I included this to my projects and than never again thought about.

Another tip: this "iamidle" does not like the clipper debugger. So I have the very first lines of my first starting procedure in every project:

#ifndef DEBUG
   ft_onidle({|| ft_iamidle(30,.T.)})

#endif

While debugging there is high cpu using, but not while the program is in its normal run.

Klemens