Is it normal for my c++ software to get my processor working at full power?

I have the Borland C++, and because of the heat the processor goes over the hedge. When I start the IDE the processor climbs up to 60 Celsius and then the Windows give's me the blue screen. Is it normal for C++ to put this much presure on my cpu? I have a AMD Athlon 3500+/ 2 Gb Ram/ Asus Mb. So the system is not a weak one. The borland software has been used by my highscholl for about 15 years, from my teacher I got it to work at home. Could the problem be that the software is too old?

Is it normal for my c++ software to get my processor working at full power?
The IDE is sitting on a 'busy-wait', the application seems to be that old!





http://en.wikipedia.org/wiki/Busy-wait





Run it in Dos-Box, that will regulate the speed.





http://dosbox.sourceforge.net





Or you could use a newer IDE instead. Your C++ compiler should still work, but it's really old, and your programs will suffer the same fate as the IDE!





This is the best free IDE/GNU G++ based C++ tool chain I can find:





http://www.bloodshed.net/dev/





About the compiler:


http://en.wikipedia.org/wiki/G%2B%2B





(Dev-C++ uses the GNU compilers, it's used to compile most Open Source applications, including some Operating Systems! It will also use the features of your processor, where the old Borland compiler wont - a new Borland compiler will of course. To find out why the IDE failed, look into the following functions - sleep, and usleep! - have fun!)





Should you want to experiment with C++ outside of windows I recommend:





http://www.ubuntu.com
Reply:Borland C++ consuming too much CPU on a 2gig Box, amazing!


I guess the SW is corrupt. Why dont you re-install Borland C++ and try again?





Get the latest Borland C++ SW. If you are using the old one (from your school days), its designed for DOS and 80*88 processors. That should be the problem.





Alternately, you can run the C++ IDE (If it is DOS based) in command window launched by "cmd" command - not "command" command. Try this.
Reply:The only thing I can think of is that you're running a console application in DOS. To deal with that use DOSBox or something similar to underclock your machine. Seems odd though!

online florist