subject:"\\\\\\\[Freedos\\\\\\\-user\\\\\\\] Bug\\\\\\\? Confusing boot options in FreeDOS 1.2"

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

2017-05-06 Thread Ulrich Hansen

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
Content-Type: text/plain;
charset=utf-8

In FreeDOS 1.1 there was a boot option 4 rCRLoad FreeDOS without driversrCL.
[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 rCRLoad FreeDOS without drivers
(Emergency Mode) [3]
If you choose it, you load FreeDOS with drivers: HIMEMX, FDAPM, CTMOUSE, UDVD2,
SHSUCDXrCa [4]

WouldnrCOt it be better not to load drivers? If people choose not to? ItrCOs
called rCREmergency moderCL after all...

There is also a boot option 4 rCRLoad FreeDOS low with some drivers (Safe
Mode)rCL [5]
But it is not loaded LOW, as promised. In FDCONFIG.SYS you find:
124?DOS=HIGH
rCa
124?DOSDATA=UMB
Isn't this the opposite of low? [6]

Probably thererCOs a quick way to fix the whole thing: Exchange only the titles
of menu options  3 and 4 and delete every 4? in FDCONFIG.SYS except the line
that loads SHELL=C:\FDOS\BIN\COMMAND.COM.  [7]

WouldnrCOt this make more sense? Please correct me if IrCOm wrong.

[1] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png

[2] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png

[3] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png

[4] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png

[5] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png

[6] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png


[7] New FDCONFIG.SYS:

SET DOSDIR=C:\FDOS

!COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
!LASTDRIVE=Z
!BUFFERS=20
!FILES=40
!MENUCOLOR=7,0

MENUDEFAULT=2,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS low with some drivers (Safe Mode)
MENU 4 - Load FreeDOS without drivers (Emergency Mode)

12?DOS=HIGH
12?DOS=UMB
12?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
23?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT



--Apple-Mail=_E891E33A-2D32-4678-A835-C43199D3E41C
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

In FreeDOS 1.1 there
was a boot option 4 rCRLoad FreeDOS without driversrCL. [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 rCRLoad FreeDOS without drivers (Emergency Mode) [3]If you choose it, you load FreeDOS with drivers: HIMEMX, FDAPM,
CTMOUSE, UDVD2, SHSUCDXrCa [4]WouldnrCOt it be better not to load drivers? If people choose not to?
ItrCOs called rCREmergency moderCL after all...There is also a boot option 4 rCRLoad FreeDOS low
with some drivers (Safe Mode)rCL [5]But it is not loaded
LOW, as promised. In FDCONFIG.SYS you find:124?DOS=HIGHrCa124?DOSDATA=UMBIsn't this the opposite of low?
[6]Probably
thererCOs a quick way to fix the whole thing: Exchange only the titles of menu
options 3 and 4 and delete every 4? in FDCONFIG.SYS except the line that
loads SHELL=C:\FDOS\BIN\http://command.com; class="">COMMAND.COM.
[7]WouldnrCOt
this make more sense? Please correct me if IrCOm wrong.[1]https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png;
class="">https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png[2]https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png; 
class="">https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png[3]https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png[4]https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png[5]https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png[6]https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png; 
class="">https://www.lazybrowndog.net/freedos/files/1.2-with-s
ome-drivers2.png[7] 
New FDCONFIG.SYS:SET

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

2017-05-06 Thread Ulrich Hansen

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
Content-Type: text/plain;
charset=utf-8


> Am 08.02.2017 um 22:46 schrieb Jerome Shidel >:
>
> Bug? Not really.
> Is it correct? Not even close.

Then lets correct it. :-) ItrCOs pretty easy, as I showed in my last mail.

> Also, #2 should not say EMM386 when it uses JEMM386.

ThatrCOs even easier. :-)

> The current 1.2 config files are based on a clean install of 1.1 into VMware
Fusion. Then a some things were added, moved, changed and removed.

Yes, the following line (which skipped all the drivers)

if "%config%rCL=="4" GOTO END

was left in AUTOEXEC.BAT although the "no driversrCL option was changed to
config 3 in FDCONFIG.SYS. That may have been the root of all evilrCa

At the moment both options are doing the opposite of what they say they do.
Instead of loading DOS low with some drivers, option 4 loads DOS high with no
drivers. Nobody complained about that, so here is another suggestion:

How about DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful?
People can always hit F8 for singlestepping...

I suggest to keep the NO DRIVERS option though, which should be exactly that:
No drivers, no memory managers, DOS not loaded high.

Dropping option 4 and keeping a clean option3 would mean deleting everything
with a 4 in FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing
the line in AUTOEXEC.BAT to

if "%config%rCL=="3" GOTO END

If this is too radical, see the suggestion in my last mail...

Ulrich
--Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=utf-8

Am 08.02.2017 um 22:46 schrieb Jerome
Shidel mailto:jer...@shidel.net;
class="">jer...@shidel.net:Bug? Not
really.Is it correct? Not even close.Then lets correct it. :-) ItrCOs pretty easy, as I showed in my last
mail.Also, #2
should not say EMM386 when it uses JEMM386.ThatrCOs even easier. :-)The current 1.2 config files are based on a clean install
of 1.1 into VMware Fusion. Then a some things were added, moved, changed and
removed.Yes, the following line (which
skipped all the drivers)if "%config%rCL=="4" GOTO
ENDwas left in AUTOEXEC.BAT although the "no
driversrCL option was changed to config 3 in FDCONFIG.SYS. That may have been
the root of all evilrCaAt the moment both options are
doing the opposite of what they say they do. Instead of loading DOS low with
some drivers, option 4 loads DOS high with no drivers. Nobody complained about
that, so here is another suggestion:How about
DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful? People can
always hit F8 for singlestepping...I suggest to keep
the NO DRIVERS option though, which should be exactly that: No drivers, no
memory managers, DOS not loaded high.Dropping option
4 and keeping a clean option3 would mean deleting everything with a 4 in
FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing the line in
AUTOEXEC.BAT toif "%config%rCL=="3" GOTO
ENDIf this is too radical,
see the suggestion in my last mail...Ulrich
--Apple-Mail=_F6D80F5B-4C1C-4E48-8341-93D55F699976--


--===7381254713677974754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
--===7381254713677974754==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--===7381254713677974754==--

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

2017-05-06 Thread Jerome Shidel

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 install of 1.1 into VMware
Fusion. Then a some things were added, moved, changed and removed. There was
very little feedback on them during the testing phase. So, it is good that they
start to get some attention. They can use a lot of improvement.




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

--- Internet Rex 2.29
 * Origin: capcity2.synchro.net - 502/875-8938 (276:10/901)
--- Synchronet 3.15a-Linux ListGate 1.3
 *  Capitol City Online - Frankfort, KY - telnet://capitolcityonline.net


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

2017-02-08 Thread Ulrich Hansen


> 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 easier. :-)

> The current 1.2 config files are based on a clean install of 1.1 into VMware 
> Fusion. Then a some things were added, moved, changed and removed.

Yes, the following line (which skipped all the drivers)

if "%config%“=="4" GOTO END

was left in AUTOEXEC.BAT although the "no drivers“ option was changed to config 
3 in FDCONFIG.SYS. That may have been the root of all evil…

At the moment both options are doing the opposite of what they say they do. 
Instead of loading DOS low with some drivers, option 4 loads DOS high with no 
drivers. Nobody complained about that, so here is another suggestion: 

How about DROPPING option 4 (SOME DRIVERS) completely? Was it ever useful? 
People can always hit F8 for singlestepping...

I suggest to keep the NO DRIVERS option though, which should be exactly that: 
No drivers, no memory managers, DOS not loaded high.

Dropping option 4 and keeping a clean option3 would mean deleting everything 
with a 4 in FDCONFIG.SYS and removing the 3 from the HIMEMX line. And changing 
the line in AUTOEXEC.BAT to 

if "%config%“=="3" GOTO END

If this is too radical, see the suggestion in my last mail...

Ulrich--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

2017-02-08 Thread 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 install of 1.1 into VMware 
Fusion. Then a some things were added, moved, changed and removed. There was 
very little feedback on them during the testing phase. So, it is good that they 
start to get some attention. They can use a lot of improvement.




--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

2017-02-08 Thread Ulrich Hansen

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 drivers: HIMEMX, FDAPM, CTMOUSE, UDVD2, 
SHSUCDX… [4]

Wouldn’t it be better not to load drivers? If people choose not to? It’s called 
„Emergency mode“ after all...

There is also a boot option 4 „Load FreeDOS low with some drivers (Safe Mode)“ 
[5]
But it is not loaded LOW, as promised. In FDCONFIG.SYS you find:
124?DOS=HIGH
…
124?DOSDATA=UMB
Isn't this the opposite of low? [6] 

Probably there’s a quick way to fix the whole thing: Exchange only the titles 
of menu options  3 and 4 and delete every 4? in FDCONFIG.SYS except the line 
that loads SHELL=C:\FDOS\BIN\COMMAND.COM.  [7] 

Wouldn’t this make more sense? Please correct me if I’m wrong.

[1] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers.png 

[2] https://www.lazybrowndog.net/freedos/files/1.1-without-drivers2.png 

[3] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers.png 

[4] https://www.lazybrowndog.net/freedos/files/1.2-without-drivers2.png 

[5] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers.png 

[6] https://www.lazybrowndog.net/freedos/files/1.2-with-some-drivers2.png 


[7] New FDCONFIG.SYS:

SET DOSDIR=C:\FDOS

!COUNTRY=001,858,C:\FDOS\BIN\COUNTRY.SYS
!LASTDRIVE=Z
!BUFFERS=20
!FILES=40
!MENUCOLOR=7,0

MENUDEFAULT=2,5
MENU 1 - Load FreeDOS with JEMMEX, no EMS (most UMBs), max RAM free
MENU 2 - Load FreeDOS with EMM386 (Expanded Memory) and SHARE loaded
MENU 3 - Load FreeDOS low with some drivers (Safe Mode)
MENU 4 - Load FreeDOS without drivers (Emergency Mode)

12?DOS=HIGH
12?DOS=UMB
12?DOSDATA=UMB
1?DEVICE=C:\FDOS\BIN\JEMMEX.EXE NOEMS X=TEST I=TEST NOVME NOINVLPG
23?DEVICE=C:\FDOS\BIN\HIMEMX.EXE
2?DEVICE=C:\FDOS\BIN\JEMM386.EXE X=TEST I=TEST I=B000-B7FF NOVME NOINVLPG
34?SHELL=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT
12?SHELLHIGH=C:\FDOS\BIN\COMMAND.COM C:\FDOS\BIN /E:1024 /P=C:\AUTOEXEC.BAT


--
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot___
Freedos-user mailing list
Freedos-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freedos-user

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

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

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

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

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

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

6 matches

Site Navigation

Mail list logo

Footer information