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 when FDAPM was loaded. This was regardless of which power saving options were used. Should we cut back on when it is loaded? There have been comments in the past similar to (paraphrased) “my 486 sounds like a vacuum cleaner when just sitting here idle”. So, I don’t think we should just REM it out under all situations. However, I don’t think there is much benefit to loading FDAPM when running inside a Virtual Machine. 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? Jerome _______________________________________________ Freedos-devel mailing list Freedos-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/freedos-devel
