From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kandziora Subject: Re: Problems with Clipper/Blinker 3.30 driven app Date: Tue, 3 Apr 2007 15:11:37 +0200 Message-ID: <200704031511.38109.jjj@gmx.de> References: <200704021544.25539.jjj@gmx.de> <200704021952.48454.dr.claudia.neumann@gmx.de> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <200704021952.48454.dr.claudia.neumann@gmx.de> Content-Disposition: inline Sender: linux-msdos-owner@vger.kernel.org List-Id: Content-Type: text/plain; charset="us-ascii" To: linux-msdos Am Montag, 2. April 2007 19:52 schrieb Claudia Neumann: > > Am Montag, 2. April 2007 15:44 schrieb Jan Kandziora: > > I already came with this problem long ago; now I investigated a little > > deeper than last time. Using dosemu 1.2.2 with Freedos included in the > > package. > > > > I have problems starting a Clipper app. It always says > > > > BLX286 : 1304 : cannot use XMS host with current memory manager > > configuration > > 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! 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. Kind regards Jan -- I will never trust someone called GATES that sells WINDOWS.