bacon@zeus.unomaha.edu (Infomaniac) (03/27/91)
Date: 26 Mar 91 16:39:00 CST
Rich, I tried to send this directly to you twice but it didn't go. I'm posting
it in comp.sys.amiga.hardware. Sorry about the bandwidth, guys.
--------------------------------ORIGINAL MESSAGE-------------------------------
From: ZEUS::BACON "RUSS BACON ECLECTICIST, LINGUIST, CULTUROPHILE"
25-MAR-1991 15:50:01.05
To: WINS%"rich@documail.uucp"
CC: BACON
Subj: Your reply on the Amaz Comp A1000 expansion hack
Date sent: 25-MAR-1991 15:28:44
Rich, this is in response to your posting to usenet on my question about the
Amazing 512K ram hack.
> The 1.3 Kickstart disk can be modified to both
> 1) Work with the Chris Erving / Amazing Computing memory hack, and
> 2) Boot off DF1:
>
> For a while, I was booting my 1000 with the Chris Erving memory (at
>80000 to fffff hex) off DF1:. I simply applied the patches for the DF1: boot
>to my Kickstart disk that was already modified to boot safely with the Chris
>Erving memory. I was lucky, in that the two patches happened to not patch
>the same location twice!
> The same kickstart patch I use should work for you. That's because it
>basically tells the system that CHIP RAM is on the range 0 to 7ffff only,
>rather than the normal 0 to 1fffff. Thus, it places both my memory (at
>80000 to fffff) and yours (at 100000 to 17ffff, if I recall) outside of
>CHIP RAM, which is what we want.
> When you boot with such a patched Kickstart disk, the system thinks it
>has 512K of CHIP RAM, and doesn't know at all about your Chris Erving memory.
>Thus, you need to use addmem to add it to the system list of free memory.
>I THINK you can use the normal addmem for this; I believe it just adds the
>memory to the FAST RAM free list. (I'm not positive at the moment about this.
>I've always used a custom addmem that did not do any memory diagnostics,
>because I used to use a recoverable RAM disk. Regular addmem would write into
>some or all of the memory, wiping out my recoverable RAM disk. Out of inertia,
>I think I still use the modified version.)
That's exactly the same thing that I heard about RAD: and the regular addmem
program that one uses on the WB disk.
> If you need them, I have
> 1) the instructions for patching Kickstart to ignore CHIP RAM above 512K
> 2) the name of the Kickstart DF1: patch I am using
Yes for both #1, 2. I don't know beans about compiling so the source wouldn't
help me on #3. There was a program out called AMF= Add Memory Forever. But it
didn't seem to work with my configuration.
I don't remember if on my post I mentioned the problem I had with the date
command and the patches. Somehow the patch interfered with the system clock
settings (I don't have a battery backed clock) so that when it read the WB disk
it wasn't able to establish a system time. Instead it came back with a date
of: <unset><unset><unset>. I just read something on comp.sys.amiga about that
but I can't remember it now. No, I think it was in AW, now that I think about
it.
BTW - with all the patches to KS that are around, isn't it feasibly possible to
modify the disk TOO much? Also, I'm considering the KSEliminator board to add
another 128K to memory. By using the 1.3ROM do I keep myself from being able
to use these patches?
> 3) the source for the modified addmem (which I think you don't need)
>and I'll be happy to dig these out of my mounds of rubbish at home.
> By the way, I fell funny about using "Chris Erving" as an adjective. It is
>a bit of an honor, tho, just as "Ward Christiansen" protocol is.
Russ
P.S. I'm not too proficient at uudecode yet. Can we arrange a disk swap?
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??
*****************************************************************************monty@sagpd1 (03/28/91)
In article <11424.27ef79b4@zeus.unomaha.edu> bacon@zeus.unomaha.edu (Infomaniac) writes: >From: ZEUS::BACON "RUSS BACON ECLECTICIST, LINGUIST, CULTUROPHILE" > 25-MAR-1991 15:50:01.05 >To: WINS%"rich@documail.uucp" >CC: BACON >Subj: Your reply on the Amaz Comp A1000 expansion hack In my opinion a much better route is to add Dave Haynies mod to allow the extra ram to auto configure. Why mess with patching kickstart when the OS already handles the task for you. If you need more information I will still send out a package of both the 512K piggy back hack and Dave's mod to allow it to auto configure. Simply send me a Stamped self addressed envelope (with postage for about 10 sheets of 8 1/2 x 11 paper) (9 x 12 envelope works best) to: Monty L. saine 4551 Piute Pl. San Diego, CA. 92117 Include a blank formatted disk and I'll give IFF and text copies of the ones I have "electronified" to date. The only thing in over two years that I have had problems with was AMAX. It simply didn't like the ram... so far. Monty Ssaine