Path: utzoo!news-server.csri.toronto.edu!rutgers!cbmvax!bagate!dsinc!unix.cis.pitt.edu!zaphod.mps.ohio-state.edu!caen!kuhub.cc.ukans.edu!zeus.unomaha.edu!bacon
From: bacon@zeus.unomaha.edu (Infomaniac)
Newsgroups: comp.sys.amiga.hardware
Subject: Re: Q: AMAZ. COMP. A1000 RAM EXPANSION HACK
Message-ID: <10677.27de9c8f@zeus.unomaha.edu>
Date: 14 Mar 91 03:41:34 GMT
References: <7229.27ca4872@cc.curtin.edu.au> <307@documail.UUCP>
Lines: 55

In article <307@documail.UUCP>, rich@documail.UUCP (Rich McCallister) writes:

> In article <7229.27ca4872@cc.curtin.edu.au>, tlynchmj@cc.cutin.edu.au says:
>> I'm considering adding ram to my 1000 the DIY way using the method outlined
>> in Amazing Computing (1987). The article tells of problems with Kick-Start
>> 1.2 trying to configure the RAM in a way that it shouldn't be used. 
>> 
>> What I want to know is does this problem still exist with KS 1.3???
>    Yes.

I had the memory hack also done, but the guy who did it didn't want to bother 
with the WB1.2 hack part of it.  Instead he addressed the memory from 00100000 
to 0017ffff.  

Now, I have heard about another program, which I think he is referring to 
below, which was supposed to merge the pseudo fast/chip ram so that it 
basically functioned as autoconfig ram.  The program was on a Fish Disk and it 
was called KickMem, by Edward Lapin, I believe.  My problem, as you see, is 
that my mem is not configured to the same addresses as the hack is supposed to 
be, so the KickMem program wouldn't work.  Worse, it rendered the kickstart 
disk useless.  On that disk I also had the Boot1 wedge inserted as well.  I 
cannot relocate the original program and it doesn't appear to have been on any 
of the Fish disks (Boot1 was a program that allows you to boot from df1, much 
better than the horrendously noisy A1000 internal drive!)

So, to put it in short, my questions are:

* Can a quick rewrite of the Kickmem program be made to config my memory 
  addresses?

* Does anyone still have a copy of the Boot1 program or is it on a FTP site?

* Oh, one other problem.  Does anyone know why this setup isn't acceptable to 
  VD0 or the RRamDisk progs?  I've never been able to get them to work 
  correctly.

> By the way, I had some trouble using the program, included in the AC
> article, that removes the extra 512K from the "CHIP" ram pool, and adds it
> to that of the "FAST" ram. (You only need this if you don't add the hardware
> circuitry to hide the 512K while booting, and you don't use a modified 
> Kickstart disk.) I think the program assumed that the memory would be all
> in one chunk, or would be the last chunk in the list, or something like that.
> I modified it to catch all such chunks (er, entries in the MemList), but
> felt it was a risky way to go anyway. If the 512K is fragmented before I even
> run my startup-sequence, how do I know the memory isn't being used as

Russ Bacon
comments/suggestions/additions/deletions/obfuscations/indigestions WELCOMED!!!
******************************************************************************
Gee. . . Toto . . . this sure doesn't look like Kansas!    
                                                               //  Have you
             Russ Bacon   University of NE at Omaha           //    tried
                 Bitnet - Bacon@UNOMA1                    \\ //       an
               Internet - Bacon@zeus.unomaha.edu           \\/      AMIGA??
*****************************************************************************