From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-0.8 required=5.0 tests=BAYES_00,INVALID_DATE
	autolearn=no autolearn_force=no version=3.4.4
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!cs.utexas.edu!rice!uw-beaver!uw-june!pattis
From: pattis@cs.washington.edu (Richard Pattis)
Newsgroups: comp.lang.ada
Subject: Another Alsys Problem (or maybe it's me)
Summary: Alsys on Ramdisk
Message-ID: <10490@june.cs.washington.edu>
Date: 25 Jan 90 00:13:12 GMT
Organization: U of Washington, Computer Science, Seattle
List-Id: <comp.lang.ada>


  I have a 16MB 386 machine. With that much space, I'd like to install
Alsys on a Ramdisk (copying its state to a harddisk before powering down)
and cut down on harddisk use.  So, I made a 10MB ramdisk and installed Alsys
Ada on it (with plenty of RAM left for the compiler work space).  The problem
is that I can't get anything to work for too long; sometime the installation
itself hangs. When I called Alsys, they told me that it might have to do with
a "too fast" disk, so I powered my machine from 20 to 7Mhz but had the same
problems.  I was using EDISK (Everex's ramdrive driver).  Then I switched
to ECACHE (running the compiler from my harddisk, where it works just fine)
with a 10Mb cache, and the same behavior resulted.

  Anyone out there actually get such a configuration to work?  I'd appreciate
hearing how.

Rich Pattis