The CPU detection utility used by the installer has compatibility issues with 
some processors.
For example, there are some 486 systems that are detected as a 186. This has 
been a known issue
for a while. Unfortunately, I just have not had the time to resolve that.

As a stop gap, if the installer is told the system is less than a 386, it 
assumes it is incorrect and
installs the 386 package set. So, there should be no need to override the 
detected CPU on 386+ systems.

That will just break the complete install on pre-386 systems. If you
insist on not trusting your tools, at least ASK the user whether they
want to override the detection.

Or better: If the tool detects a pre-386, make sure that you install
an 8086 compatible kernel. You can still let the config/autoexec keep
a boot menu item a la "if you are sure that your CPU can actually do
it, select this item to try to load EMM386 and HIMEM at your own risk."

For systems with less than a 386, you will want to override it to ensure the 
8086 compatible kernel
is installed.

This should be the other way round. If you know what you are doing,
you MAY override the detection result that you have no 386. If you
do NOT know for sure, then the installer should NOT give you an
install which would require 386.

Of course if the INSTALLER is sure that the CPU is 386 or newer,
the whole problem does not occur. So my proposal only annoys a
small number of people with exotic 386+ CPU, but rescues all the
users with actual 286 or older CPU or emulators from getting an
un-usable install due to overly optimistic automated overrides.

Regards, Eric

Freedos-user mailing list

Reply via email to