Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!harvard!seismo!mcvax!ukc!rde
From: rde@ukc.ac.uk (R.D.Eager)
Newsgroups: net.micro.pc
Subject: Re: Ramdisks in high memory
Message-ID: <1194@eagle.ukc.ac.uk>
Date: Sun, 11-May-86 08:20:46 EDT
Article-I.D.: eagle.1194
Posted: Sun May 11 08:20:46 1986
Date-Received: Thu, 15-May-86 06:41:12 EDT
References: <1893@ihlpg.UUCP> <1897@ihlpg.UUCP> <2104@cbosgd.UUCP>
Reply-To: rde@ukc.ukc.ac.uk (R.D.Eager)
Organization: U of Kent at Canterbury, Canterbury, UK
Lines: 21


I  have  a  related  problem,  so  I  post this as a followup. I have an
obscure British PC compatible which uses an 8086 (that's  the  important
point).   As  such,  because  it  has a 16 bit system bus and because (I
presume) of wait states in memory on an expansion  board,  programs  run
*much*  more  quickly  if loaded in the bottom 256K. This would be fine,
but I run a RAMdisk which grabs this space during device  initialisation
thus forcing user programs into slower memory.

Anyone  know  a  safe, well behaved way of getting it to use high memory
(stuff from 640K downwards) for the RAMdisk? The  DOS  manual  says  you
can't  allocate  memory  (or do most anything) from device drivers, so I
can't do clever grab/free tricks to get the right piece.
-- 
           Bob Eager

           rde@ukc.UUCP
           rde@ukc
           ...!mcvax!ukc!rde

           Phone: +44 227 66822 ext 7589