Dosemu takes 99% of cpu

Dosemu takes 99% of cpu

[Fajar Priyanto]

Hi all,
Another problem that I encounter is that dosemu takes 99% of cpu for each of 
it's instances. This becomes a performance problem in my LTSP configuration, 
where as all the work is on the server. The dos program becomes very slow.

Is it normal that dosemu takes 99% of cpu?
Thanks
Fajar.

Re: Dosemu takes 99% of cpu

[Stas Sergeev]

Hello.

Fajar Priyanto wrote:
> Is it normal that dosemu takes 99% of cpu?
That depends on the program that it runs,
and on dosemu version, which you, AFAICS,
haven't specified. 1.3.2 is known to be not
very good on that - try the CVS code.

Re: SOLVED: Dosemu takes 99% of cpu

[Fajar Priyanto]

On Friday 26 August 2005 15:47, Stas Sergeev wrote:
> Hello.
>
> Fajar Priyanto wrote:
> > Is it normal that dosemu takes 99% of cpu?
>
> That depends on the program that it runs,
> and on dosemu version, which you, AFAICS,
> haven't specified. 1.3.2 is known to be not
> very good on that - try the CVS code.

I use dosemu 1.2.2.0.
Btw, it turns out that the performance problem is because of duplicated files 
of the program.

You see, at first I have all the filenames in capital letters, because it 
comes from DOS environment.

Then a guy from accounting department supplied me some current dbf files. And 
what I don't realize is that all the files name are in small letter (not 
capital letter). So, in the program folder there are some identical files, 
one in capital letter, and the other in small letter. Looks like he copied 
the files from WinXP environment using explorer.

Then when dosemu runs, somehow it manage to "merge" those files to show only 
in capital letter (of course it is what DOS does). Apparently this confuse 
the program itself on which files to read when generating some on screen 
report.

When I got it fix by eliminating the duplicated files, the program can display 
the report quickly again, although dosemu still takes 99% of cpu. But, it is 
only when it is calculating. When the report is done, the cpu comes normal 
again.

I guess this is the culprit.
Another lesson I got :)
Thanks for all the help.

Fajar