Message-ID:	<005c01c05665$9f906560$0400000a@alain-nb>
From:	"Alain" <alainm AT pobox DOT com>
To:	<opendos AT delorie DOT com>
Subject:	Re: Re: Optimizing CONFIG.SYS...
Date:	Fri, 24 Nov 2000 20:13:12 -0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3110.5
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To:	opendos AT delorie DOT com

Hi Mathias,

according to all your (very interesting) description, the FILES=
could be placed anywhere in the Config.sys file, but faced by
the fact that it is sometimes not working at the first line in MS-DOS
7.1 could you imagine some explanation for it? 

Where do you suggest placing it? (1) after HIMEM and EMM386
if they exist, (2) after the last line, (3) ???

Alain

De: Matthias Paul <PAUL-MA AT reze-1 DOT rz DOT rwth-aachen DOT de>
Para: opendos AT delorie DOT com <opendos AT delorie DOT com>

>For those who don't know, there's a fundamental difference between 
>how MS-DOS and DR-DOS execute CONFIG.SYS. Both have there Pro's 
>and Con's. Personally I prefer the DR-DOS style, but if all you 
>want is to create simple boot menus, they are easier to implement
>in the MS-DOS style.
>
>MS-DOS compiles the CONFIG.SYS in at least two passes and creates 
>in an internal memory buffer a tagged list of commands to be 
>executed. The list is then sorted in various groups and later 
>interpreted step by step.
>
[...]
>
>MS-DOS records the DEVICE[HIGH]= and INSTALL[HIGH]= statements 
>in the order of their appearance in CONFIG.SYS. When it has
>finished its basic setup, it will then first execute all the 
>DEVICE[HIGH]= statements in the list followed by all the 
>INSTALL[HIGH]= statements, optionally followed by SHELL= etc.
>This is why under MS-DOS device drivers and TSRs are loaded
>in different chunks (see MEM /DEBUG).
>Although you can load TSRs before device drivers under DR-DOS
>(a feature I often miss under MS-DOS!), it still tries to mimic 
>the MS-DOS memory layout to some extend by loading the drivers 
>in different memory regions (if there are more than one).
>
> Matthias

- Raw text -