> ...
> By no means is VINFO perfect. In fact, there is a known issue in
> detecting some 486 based machines that I have not got around to
> fixing. Also, there some other things that could be done better.
> But, they are mostly minor issues that I have not found the time or
> motivation to remedy.
Hi Bret,
> On Mar 17, 2023, at 9:41 PM, Bret Johnson wrote:
>
>> Tom's suggestion of using IDLEHALT is most likely the best solution.
>>
>> As you suggest, Using IDLEHALT for VM's and FDAPM for real
>> hardware on installed systems will be easy to do.
>>
>> Since such decisions cannot be made
> Tom's suggestion of using IDLEHALT is most likely the best solution.
>
> As you suggest, Using IDLEHALT for VM's and FDAPM for real
> hardware on installed systems will be easy to do.
>
> Since such decisions cannot be made automatically during boot in the
> CONFIG at present, probably just swit
> Am 17.03.2023 um 19:25 schrieb tom ehlert :
>
> in that case: WHAT REGRESSIONS?
To name one: The text editor segfaulted right after start. Can happen if you
are using a development snapshot. It is fixed by now because the current
maintainer is very committed to solving the bugs and tracks th
> IDLEHALT=1 works for my machines and reduces the CPU load under
> VirtualBox to nearly zero at the command prompt.
:-)))
FDAPM whatever
should be REMified.
OTOH this seems to be a problem between FDAPM,
VirtualBOX and Watcom Installer. Whoever wants to develop ON FreeDOS
...
>> Am 17.0
IDLEHALT=1 works for my machines and reduces the CPU load under VirtualBox to
nearly zero at the command prompt.
> Am 17.03.2023 um 15:25 schrieb jer...@shidel.net:
>
> On a side note… Why run the watcom installer at all? Installing the FreeDOS
> WATCOMC 1.9 package through FDIMPLES, even with
I ran a test with idlehalt=0 / -1 / 1 and put fdapm to rem in virtualbox
Fast speed with 0 and 1!
idlehalt=-1 gave slow speed.
After this I removed idlehalt and activated fdapm again - and then ran
fdapm off : fast speed.
Willi
Am 2023-03-17 15:34, schrieb jer...@shidel.net:
> On Mar 17
> On Mar 17, 2023, at 10:07 AM, Rugxulo wrote:
>
> Hi,
>
> On Fri, Mar 17, 2023 at 5:32 AM wrote:
>>
>> At present, the FreeDOS installed system and installer boot media load FDAPM
>> on many hardware configurations and virtual machines.
>>
>> As most are aware, there has recently discusse
Hi,
> On Mar 17, 2023, at 7:58 AM, tom ehlert wrote:
>
> Hallo Herr Bernd Boeckmann via Freedos-devel,
>
> am Freitag, 17. März 2023 um 12:52 schrieben Sie:
>
>
>>> Any thoughts?
>
>> I have some additional data:
>
>> 1) Pentium MMX 166, T2303 default installation:
>
>> Installation time
Hi,
On Fri, Mar 17, 2023 at 5:32 AM wrote:
>
> At present, the FreeDOS installed system and installer boot media load FDAPM
> on many hardware configurations and virtual machines.
>
> As most are aware, there has recently discussed issue that the watcom
> installer was taking an excessively lon
Hallo Herr Bernd Boeckmann via Freedos-devel,
am Freitag, 17. März 2023 um 12:52 schrieben Sie:
>> Any thoughts?
> I have some additional data:
> 1) Pentium MMX 166, T2303 default installation:
> Installation time Open Watcom 1.9, FDAPM activated: 7:09 minutes.
> After FDAPM OFF: 4:30 Minut
> Any thoughts?
I have some additional data:
1) Pentium MMX 166, T2303 default installation:
Installation time Open Watcom 1.9, FDAPM activated: 7:09 minutes.
After FDAPM OFF: 4:30 Minuten.
2) VirtualBox, activated APM: aborted after 2 minutes @ 10%
3) VirtualBox with LH FDAPM ADV:REG same
Hi All,
At present, the FreeDOS installed system and installer boot media load FDAPM on
many hardware configurations and virtual machines.
As most are aware, there has recently discussed issue that the watcom installer
was taking an excessively long time to install. The problem only occurred
13 matches
Mail list logo
