Message-ID: <010c01c268bb$cee0b080$c03dfea9@atlantis>
From: "Matthias Paul" <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
To: <opendos AT delorie DOT com>
References: <20020928 DOT 194125 DOT 6G7 DOT rnr DOT w165w AT krypton DOT rain DOT com>
Subject: Re: Loadfix
Date: Mon, 30 Sep 2002 21:37:37 +0200
Organization: Aachen University of Technology (RWTH), Germany
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4522.1200
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id g8UJxGZ28300
Reply-To: opendos AT delorie DOT com

On 2002-09-29, Leonard Erickson wrote:

> I've run into a snag on a friend's BBS system (yes, there are still
> BBSes struggling along). It's running DR-DOS 7.03. We are using 4dos
> 5.5 as the command processor. And QEMM and desqview.
> [...]
> The DR-DOS LOADFIX.bat doesn't solve the problem. Running the
> critical lines by hand to invoke MEMMAX gets an error about "must
> be loaded from the Master command shell"

Most probably, this message is generated because you are not using
COMMAND.COM as a primary shell, but 4DOS. 4DOS will create a very
different conventional memory layout compared to COMMAND.COM.
Just to be sure, please try, if using COMMAND.COM instead of 4DOS
solves the problem. Also, please double-check (MEM /A instead of
MEMMAX -L), that the MEMMAX -L is actually executed from the
primary command processor. Which version of LOADFIX.BAT are you
using, anyway?

I see several possible solutions:

- Unpack the driver to not use the buggy EXEPACK decompressor
  any longer, or fix the decompressor stub with one of the
  tools available on the net.

- Have you tried this under plain DOS, or under DV or TASKMGR?
  In case you did under DESQview, execute MEMMAX -L before
  starting DESQview.
  
- Try some of 4DOS' configuration options, in particular
  loadhigh options.

- Try the current issue of 4DOS (7.01A), available from http://www.jpsoft.com

I am using 4DOS 7.01A as primary shell and have not run into the
problems observed by you, but this could well be a result of my
different memory layout.

Hope it helps,

 Matthias

-- 
<mailto:Matthias DOT Paul AT post DOT rwth-aachen DOT de>; <mailto:mpaul AT drdos DOT org>
http://www.uni-bonn.de/~uzs180/mpdokeng.html; http://mpaul.drdos.org

"Programs are poems for computers."