Problems with Clipper/Blinker 3.30 driven app

Problems with Clipper/Blinker 3.30 driven app

[Jan Kandziora]

Hi all,

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

This is a DOS extended program which requires a minimum of a
286 processor and at least 512Kb of available DPMI, VCPI or XMS
memory to run. Please ensure that your system is configured
with a memory manager which provides these resources.


All memory settings are left default. Do you have any pointers what to do to 
get this app running with dosemu?

Kind regards

	Jan
-- 
I'm not in favor of senseless Micro$oft bashing.
I'm in favor of bashing Micro$oft senseless.

Re: Problems with Clipper/Blinker 3.30 driven app

[Claudia Neumann]

Hi Jan!

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.

CU

Claudia

Re: Problems with Clipper/Blinker 3.30 driven app

[Jan Kandziora]

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.

Re: Problems with Clipper/Blinker 3.30 driven app

[Jan Kandziora]

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.

Re: Problems with Clipper/Blinker 3.30 driven app

[Jan Kandziora]

Hallo Alain M., am Dienstag, 3. April 2007 15:53 schriebst du:
>
> 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*.
>
Tamedos 3.3.4a from

http://www.tamedos.com/downloads/

works (with freedos). There is a special setting for clipper

tame /i clipper

which brings down the CPU usage to 50% where it was 100% before. The program 
is shareware, but it may be worth (

$20 is ~16EUR, plus CC fees, ~20EUR <=> 118 kWh (17ct/kWh). So if the CPU has 
50W max. consumption, this is 25W less power meaning after 4720h (7 month), 
it payed off

) the $20 the author wants for it.

Kind regards

	Jan
-- 
Dazu paflt auch der Trend weg von der Kommandozeile: Dem Computer
*Kommandos* erteilen - nein, das geht nun wirklich nicht. Nein, *wir*
haben gef‰lligst *seine* Fragen zu beantworten und *seine* Meldungen
zu best‰tigen... (Christopher Eltschka in ger.ct)
-
To unsubscribe from this list: send the line "unsubscribe linux-msdos" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html