On 12/16/2019 10:00 AM, Lino Mastrodomenico wrote:
Despite some limitations the nice thing about setting high-res text
modes using only generic VGA registers (as opposed to card-specific
SuperVGA) is that the same code works ~everywhere and doesn't need a
VBE BIOS; the downside is that the VG
Sorry, edit error cutting off the end of my sentence:
> Also, please add the exotic modes to an updated svgatextmode port
> and not to mode! Mode is meant to stay within BIOS support limits
> and compatibility as far as possible, as far as I am concerned,
> while svgatextmode is known to be usea
Hi Lino,
In which ways does the old svgatextmode fail for you and
which VESA text modes do you have as opposed to which text
modes would you like to have? You cannot set ARBITRARY size
because the text mode has to follow a graphics mode as far
as resolution is concerned. Of course modern screens
On Mon, Dec 16, 2019 at 05:08:51PM +0100, Eric Auer wrote:
> As you say your PC fails to idle while just waiting at
> the command prompt: Your command.com is a version of
> FreeCOM, I guess? Which version?
OK, one more:
just did quick-test of newest available FreeCOM binaries:
https://github.c
On Mon, Dec 16, 2019 at 05:08:51PM +0100, Eric Auer wrote:
> As you say your PC fails to idle while just waiting at
> the command prompt: Your command.com is a version of
> FreeCOM, I guess? Which version? Any hypervisors or
> virtual computers or similar running "around" DOS?
OK, forgot one more
On Mon, Dec 16, 2019 at 05:08:51PM +0100, Eric Auer wrote:
> As you say your PC fails to idle while just waiting at
> the command prompt:
Update: just a minute ago I noticed that at last after I called fdapm again
it reported: "CPU was idle 5% of the time" - just "out of the blue".
It was repeat
On Mon, Dec 16, 2019 at 12:33:45PM -0500, dmccunney wrote:
> What hardware are you running, where you have four fans in
> the box and it's still not enough to prevent a system halt because the
> CPU overheated?
It's Athlon XP 3000+ on Asrock mobo, my fans are on CPU, power supply,
graphics card
On Mon, Dec 16, 2019 at 05:08:51PM +0100, Eric Auer wrote:
> > So how can I check idle statistics, if not using FDAPM?
>
> I mean try using FDAPM without using IDLEHALT.
I don't see any difference - and, actually, I didn't even expect any.
If with IDLEHALT my CPU doesn't take any "breaks" - why
Hi all,
TL;DR: is there a modern open source equivalent of SVGATextMode that works
on FreeDOS, supports recent graphics cards and PC emulators, and is not
limited to the few (if any) text modes provided by a typical VESA BIOS?
For context: x86 emulators (QEMU, DOSBox, Bochs...) happily allow high
On Mon, Dec 16, 2019 at 7:42 AM ZB wrote:
> Indeed PCISLEEP can make my VGA sleep, it seems (at least it declared it
> can) - but most important to me is to give CPU a break when it's not that
> busy (waiting for my typing etc.). The energy maybe not that important,
> just I'd like to avoid CPU's
Hi!
> So how can I check idle statistics, if not using FDAPM?
I mean try using FDAPM without using IDLEHALT.
As you say your PC fails to idle while just waiting at
the command prompt: Your command.com is a version of
FreeCOM, I guess? Which version? Any hypervisors or
virtual computers or simi
ZB, on Thursday, December 12, 2019 11:13 AM, wrote...
>
> On Thu, Dec 12, 2019 at 03:30:50PM +, Jose Isaias Cabrera wrote:
>
> > Old to MS DOS, but newbie to FreeDOS. Is there a webserver written and
> run purely on FreeDOS? I have done a few searches, but don't see anything
> in the various a
On Mon, Dec 16, 2019 at 02:21:24PM +0100, Eric Auer wrote:
> Hi! Idlehalt is just a small routine, it may
> not contribute to the idle statistics shown
> by FDAPM.
So how can I check idle statistics, if not using FDAPM?
> I guess it might even make those
> look lower if you use both in parallel.
Hi! Idlehalt is just a small routine, it may
not contribute to the idle statistics shown
by FDAPM. I guess it might even make those
look lower if you use both in parallel. You
could check which apps you use which fail to
let your CPU go idle with FDAPM. Maybe there
are possibilities to tune apps
On Mon, Dec 16, 2019 at 12:59:42PM +0100, Eric Auer wrote:
> You can always use HLT to save power, which both FDAPM
> and the kernel IDLEHALT support even on older-than-APM
> systems. The kernel config sys option can be either
>
> IDLEHALT=1 to use HLT when the kernel is waiting
> IDLEHALT=2 to a
Hi!
> acpi0: sleep states S0 S1 S4 S5
> acpi0: tables DSDT FACP APIC
> ...
> acpicpu0 at acpi0: C1(@1 halt!)
You can always use HLT to save power, which both FDAPM
and the kernel IDLEHALT support even on older-than-APM
systems. The kernel config sys option can be either
IDLEHALT=1 to use HLT w
I can recall a longer time ago I asked a question about this, and the tip
was to use "FDAPM ADV:REG".
Unfortunately it seems FDAPM most probably supports only APM, which isn't
present in BIOS-es of (most of) post-2000 motherboarda anymore. When I get
its status by simply typing "fdapm" it answers:
17 matches
Mail list logo
