X-Apparently-From: <pmoran22 AT yahoo DOT com>
Message-ID: <000d01c05799$bdf5cfb0$a1881004@dbcooper>
From: "Patrick Moran" <pmoran22 AT yahoo DOT com>
To: <opendos AT delorie DOT com>
References: <819A5186A6F AT reze-1 DOT rz DOT rwth-aachen DOT de> <001301c05594$ab2df350$a28a1004 AT dbcooper> <2 DOT 07b7 DOT YMVX DOT G4IZ6W AT belous DOT munic DOT msk DOT su> <006101c05614$1f71a4d0$a28a1004 AT dbcooper> <2 DOT 07b7 DOT 3EXL DOT G4K1NY AT belous DOT munic DOT msk DOT su> <001501c056e6$11012b50$ce881004 AT dbcooper> <20001125162011 DOT B6511 AT sk2 DOT org>
Subject: Re: Optimizing CONFIG.SYS...
Date: Sun, 26 Nov 2000 04:08:34 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.3018.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300
Reply-To: opendos AT delorie DOT com

True, however, if I load NWCDEX in the CONFIG, it does not load everything
high, there is still the 112 bytes env and 7248 bytes of it left in low
memory. If I load UNIVESA in the CONFIG, it still used 112 bytes of env in
upper menory in the B000 range, then loads into the next higher available
high memry range. It must need a lot of space to load. I have tried
everything I can think of to make it load into the B000 range and see if it
still leaves an env. But 112 bytes is not that much to worry about. The
reason I load it and NWXDEX last before the environment settings is it puts
their envs at the last area of B000 that is used, thus that range does not
get fragmented.

BTW QEMM thinks that NWCDEX needs 128k to load. I tell QEMM to only use
65,000 (just under 64k) bytes to load it. It actually loads in two parts.
That way QEMM could load drivers and TSRs more efficiently. QEMM is not very
good on my current computer because of some wierd things that happen during
the boot process. QEMM cannot find the 1A handler because somthing moves it
during boot. I suspect it's the SCSI portion of the MB BIOS that is doing
this. It is probably the reason I cannot use the F700-F7FF range of upper
memory. Whe I use debug and check that area, it is part of the CMOS setup.
Then the area just following that is all 0000, and that area cannot be used
either. But if I install EMS, I can use both those ranges.

I'll check that prompt string again and see if it does change the env that
NWCDEX and UNIVESA uses if I put that before the TSRs are loaded. But I am
pretty sure it did not affect it.

Pat




----- Original Message -----
From: "Stephen Kitt" <steve AT tardis DOT ed DOT ac DOT uk>
To: <opendos AT delorie DOT com>
Sent: Saturday, November 25, 2000 9:20 AM
Subject: Re: Optimizing CONFIG.SYS...


> On Sat, Nov 25, 2000 at 06:44:17AM -0700, Patrick Moran wrote:
> > > >> PM> PROMPT [DRDOS] $P$G
> > > >> PM> ^
> > > >> PM> These can be loaded anytime. I did not notice any difference if
I
> > loaded
> > > >> PM> them first.
> > > >>      PROMPT is not a program, this is substitute for SET PROMPT
> > statement,
> > > >> also as PATH is a substitute for SET PATH statement.
> > > PM> Yes, I know. they do not use any memory, that is why they can be
used
> > at
> > > PM> anytime.
> > >
> > >      This statement _uses_ memory for consequent environment variable.
> >
> > Yes, but that is included in the env size you use in the CONFIG file, it
is
> > not extra memory that can interfere or fragment loading and memory.
>
> Except that each program you run gets its own copy of the environment,
> shrunk to the closest multiple of some value (sixteen bytes would make
sense
> since that is the size of a paragraph, but thirty-two rings a bell). So
> putting stuff in the environment can make a difference when loading TSRs.
> That's why the common recommendation is to load all TSRs before setting
any
> environment variables. If a TSR requires a variable, it should be set just
> before that TSR is loaded and unset afterwards... Things vary from TSR to
> TSR too since some release their environment while others don't.
>
> (In the example which was being discussed, that wasn't an issue since all
> the TSRs were loaded beforehand.)
>
> I'd imagine (but I can't check just now) that the Interrupt List would
have
> all the gory details, possibly under the DOS EXEC function (interrupt 21h,
> function 4Bh if I remember correctly) or the description of the PSP.
>
> Stephen


_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com