From: Jan Kandziora <jjj@gmx.de>
To: "Alain M." <alainm@pobox.com>
Cc: linux-msdos <linux-msdos@vger.kernel.org>
Subject: Re: Problems with Clipper/Blinker 3.30 driven app
Date: Tue, 3 Apr 2007 17:47:33 +0200 [thread overview]
Message-ID: <200704031747.33863.jjj@gmx.de> (raw)
In-Reply-To: <46125C4F.2010207@pobox.com>
Am Dienstag, 3. April 2007 15:53 schrieb Alain M.:
> >> Update on at least 1.3.3, better 1.3.4. I use Clipper apps and can
> >> compile on apps with Clipper/Blinker without Problems.
> >
> > It works with dosemu 1.3.4. Great!
>
> News about Locks+Dosemu+FreeDOS+Clipper?
>
I think not. It's a hotel reception database and the hotels I administer are
small enough to have only one instance of the application running.
Are there any precautions if I want to run various instances of dosemu+this
application on the same (locally stored) files?
> > Now I come up with an related question. The application does a busy-loop
> > so the processor load is always 1. I know I can nice dosemu, but that has
> > effects only to the responsiveness of my system.
> >
> > I'd like to assign only a part of the processor to dosemu so I can make
> > use of power saving features. Is it possible to slow down the looping of
> > moronic DOS apps?
> >
> > $_hogthreshold = (1) doesn't seem to have any effect at all.
>
> What happens is that *idle* time is eaten up 100% by dosemu. It (usualy)
> dosen't affect the machine performance. If you want to check it: you
> just run any other cpu consuming app and see that dosemu gracefully
> reduces it's cpu use.
>
Yes. I know that.
> But it will keep energy saving form working. There is a program DOSIDLE
> that halts the cpu when needed and there is a new one SLEEPVM that I
> never tested. Google for "site:vmware.com dosidle"
>
Ah. Thanks.
> You will have an extra problem: this doesn't apply to clipper. There are
> some other tricks for that, if you make it work, *please let us know*.
>
I'll try it out.
> And there is an added benefit exclusive on dosemu: you can configure it
> so that it *stops* when it looses focus. It's a good alternative.
>
Ah, found the option. Thanks!
Kind regards
Jan
--
I will never trust someone called GATES that sells WINDOWS.
next prev parent reply other threads:[~2007-04-03 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-02 13:44 Problems with Clipper/Blinker 3.30 driven app Jan Kandziora
2007-04-02 17:52 ` Claudia Neumann
2007-04-03 13:11 ` Jan Kandziora
[not found] ` <46125C4F.2010207@pobox.com>
2007-04-03 15:47 ` Jan Kandziora [this message]
2007-04-03 23:03 ` Jan Kandziora
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=200704031747.33863.jjj@gmx.de \
--to=jjj@gmx.de \
--cc=alainm@pobox.com \
--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