Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga
Subject: Re: Continuous memory...
Message-ID: <2135@lpami.wimsey.bc.ca>
Date: 15 Oct 90 11:11:01 GMT
Lines: 29
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <40860@eerie.acsu.Buffalo.EDU>, v092mgp5@ubvmsd.cc.buffalo.edu (Scott K Wood) writes:
>   Since I am not one of the fortunate owners of a 3000 (yet!), I am not
>currently able to enjoy to pleasures of 2.0, por so I thought.  A developer
>friend of mine loaned me his developer's version of 2.0.  It has Kickstart
>in a 512K file on a disk.  Apparently a program included, called KickIt,
>reads this file, puts it in RAM and boots the system with it.  Here is the
>problem.  When running KickIt, the program says I need 524,000+ (512K) bytes
>of continuous memory.  It seems to believe cries that I don't have this. I
>am running a 500 with 1 MEG of memory.  I find it hard to believe that after
>a warm boot, I don't have that much continous memory.  Does anyone know
>what could be going on here and how to fix it?  Is it due to the CHIP/FAST
>RAM differentiation made my the OS?  Help...I wanna see 2.0!!!

CHIP/FAST differentiation is made by both the OS and the hardware, and are not
contiguous with one another.

 The best way to fix it is to become a developer, learn about the machine, and
run a legal version of 2.0 on a machine that can handle it.

-larry

--
It is not possible to both understand and appreciate Intel CPUs.
    -D.Wolfskill
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+