From: Fajar Priyanto <fajarpri@cbn.net.id>
To: linux-msdos@vger.kernel.org
Subject: Re: SOLVED: Dosemu takes 99% of cpu
Date: Sat, 27 Aug 2005 08:01:54 +0700 [thread overview]
Message-ID: <200508270801.54603.fajarpri@cbn.net.id> (raw)
In-Reply-To: <430ED70F.103@aknet.ru>
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
prev parent reply other threads:[~2005-08-27 1:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-26 8:47 Dosemu takes 99% of cpu Stas Sergeev
2005-08-27 1:01 ` Fajar Priyanto [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200508270801.54603.fajarpri@cbn.net.id \
--to=fajarpri@cbn.net.id \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox