[Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

From: Ulrich Hansen --===7417113793669517128== Content-Type: multipart/alternative; boundary="Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C" --Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C Content-Transfer-Encoding: quoted-printable

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

From: Ulrich Hansen --===7381254713677974754== Content-Type: multipart/alternative; boundary="Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976" --Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976 Content-Transfer-Encoding: quoted-printable

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

From: Jerome Shidel Bug? Not really. Is it correct? Not even close. You are correct that there are at least a couple issues with the FDCONFIG.SYS and AUTOEXEC.BAT file. Also, #2 should not say EMM386 when it uses JEMM386. The current 1.2 config files are based on a clean

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

> Am 08.02.2017 um 22:46 schrieb Jerome Shidel >: > > Bug? Not really. > Is it correct? Not even close. Then lets correct it. :-) It’s pretty easy, as I showed in my last mail. > Also, #2 should not say EMM386 when it uses JEMM386. That’s even

Re: [Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

Bug? Not really. Is it correct? Not even close. You are correct that there are at least a couple issues with the FDCONFIG.SYS and AUTOEXEC.BAT file. Also, #2 should not say EMM386 when it uses JEMM386. The current 1.2 config files are based on a clean install of 1.1 into VMware Fusion. Then

[Freedos-user] Bug? Confusing boot options in FreeDOS 1.2

In FreeDOS 1.1 there was a boot option 4 „Load FreeDOS without drivers“. [see picture 1] It booted a clean system, with SYSTEM and COMMAND and nothing else. [2] In FreeDOS 1.2 there is a boot option 3 „Load FreeDOS without drivers (Emergency Mode) [3] If you choose it, you load FreeDOS with