delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/2000/07/07/12:43:13

From: "Matthias Paul" <PAUL-MA AT reze-1 DOT rz DOT rwth-aachen DOT de>
Organization: Rechenzentrum RWTH Aachen
To: opendos AT delorie DOT com
Date: Fri, 7 Jul 2000 18:38:36 +0100
Subject: Re: DR-DOS upper memory problem
X-mailer: Pegasus Mail v3.22
Message-ID: <4DE3EE7E35@reze-1.rz.rwth-aachen.de>
Reply-To: opendos AT delorie DOT com

On Thu, 06 Jul 2000 Mike Sensney wrote:

> I think you identified the real problem in your first line:
> >I've been using an old Packard Bell 486
> 
> It is difficult to judge the reliability of any software running on flakey
> hardware.
Hm, DR DOS EMM386 should support any kind of machine, even if it's not
100% compatible. If there's an incompatibility somewhere it's good to 
know about it. 
I don't know if I can help, but I'd like to go into this a little, 
as it is quite well defined how to detect ROMs.
If you send a private email with your configuration files, MEM /A 
outputs, exact version numbers of DR DOS issue, memory manager, 
ROM-BIOS, and a memory dump from A000h..FFF0h (of course without 
any memory manager loaded ;-), and anything else that might help, 
I will have a look.

One thing to try: Load MS-DOS HIMEM before loading DR DOS EMM386.EXE.
(This will give a warning, because it's a sub-optimal configuration, 
but I'd like to know if this fixes your problem). The MS HIMEM.SYS
driver probably uses different detection methods for non-standard 
hardware then the DR DOS memory managers.

 Matthias

-------------------------------------------------------------------
Matthias Paul, Ubierstrasse 28, D-50321 Bruehl, Germany
eMail: <Matthias DOT Paul AT post DOT rwth-aachen DOT de>
Web  : http://www.rhrz.uni-bonn.de/~uzs180/mpdokeng.html
-------------------------------------------------------------------

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019