> On Mar 17, 2023, at 10:07 AM, Rugxulo <rugx...@gmail.com> wrote: > > Hi, > > On Fri, Mar 17, 2023 at 5:32 AM <jer...@shidel.net> 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 long time to install. The problem only >> occurred when FDAPM was loaded. This was regardless of which power saving >> options were used. Should we cut back on when it is loaded? > > I almost forgot that the Borland IDE tools were also slowed down when > FDAPM was loaded. That is a known issue. > >> What I’m thinking is we more or less keep things as they are. But, add an >> exception to the various AUTOEXEC files that skips loading it as a driver >> when the OS is running under a known VM like VirtualBox, VMware, etc. >> >> Any thoughts? > > Yeah, just turn it off if under a VM (and document why with a REM > comment). Oh, and turn on IDLEHALT like Tom suggests.
Sorry, I forgot about it effecting other things as well. So, just making a WATCOM2 package would not solve any other slowdown issues. Assuming, there is no large slowdown in the watcom installer with IDLEHALT. 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 switch to using IDLEHALT on the LiveCD as well. :-) Jerome > > > _______________________________________________ > Freedos-devel mailing list > Freedosemail@example.com > https://lists.sourceforge.net/lists/listinfo/freedos-devel _______________________________________________ Freedos-devel mailing list Freedosfirstname.lastname@example.org https://lists.sourceforge.net/lists/listinfo/freedos-devel