DOS Clipper in Windows and Memory 1

[samirlias]

Migrating our LAN DOS Clipper application to Windows works except it is taking up all the CPU usage, making it hard to run any other processes. In the LNK file we are using the "BLINKER EXECUTABLE EXTENDED 2048". Is there a simple way to force it to take just enough memory ?
If not is there another way since once running on the server, every other activity will take for ever.
Thanks in advance

 

[HotEye]

Just a thought...

This may not ba a memory problem, but to do with with processor hogging. If it is Windows 98, use System Monitor to see if the processor is fully utilized. Try without your program running first to make sure some processor is free. Then start your program and see if the utilization goes up to 100%. Windows NT/2000 use Task Manager, although I have not tried this.

If it does, then your program will need to be changed to release the processor in wait states.

Use ft_iamidle() from the Nantucket Forum Library in your custom Inkey() routine, and add
lib nanfor, cpmi
into your link script. You will need to add this call all over the place so use System Monitor to track them down.

The library can be found at various sites including

http://www.the-oasis.net/

Hope it helps.

 

[samirlias]

Actually I was mistaken. The root cause was that the DOS Clipper 5.2 application running in Windows 2000 server is taking up all the CPU, which causes problems when trying to run another program. Is this a de-facto thing or anyone found a solution ?

 

[samirlias]

Great... I followed your suggestion and looked on the Web for more info and tried a similar OSLIB library and it reduced the CPU usage from 100% to 29% for my application by simply including 4 lines of code at the initialization time. That's a big improvement. But, does this mean that's all I have to do ? or there are other tricks to reduce CPU even more, since the suggestion that came with OSLIB suggested a function call at each idle point.
Thanks for this great help.

 

[lgraybiel]

We have used the ft_iamidle routine for years. Currently run a Clipper app under Windows Terminal Services. With eight sessions running on a PII 700mhz, it averages about 20% CPU utilization.

 

[samirlias]

Coming back to this issue. Mr. Igraybiel you mentioned Terminal Services, which we use to remotely connect to the server. We have batch DOS and Clipper processes running. Every few days or hours, one of these batches is hung with the CPU at close to 100%. Did you have similar batch ? and how do you or any other gentleman handle the CPU in the batch case. Because right now we cannot even connect to the server to check, because our profile for terminal services is corrupted and we have to reboot the server.