MountList Help
7 messages in this thread
I have an A1000 with a MiniMeg addon (one meg RAM). I just added an
InsiderII with 1.5 meg RAM and now I can't create a recoveable ram drive.
The MiniMeg configs to $200000 and the Insider installs at $C00000. The
two memory pools conflict and GURU whenever I try to mount RAD:. I think I
can specify a single memory block with the 'MASK' entry in the MountList,
but the 1.3 Enhancer manual doesn't give any examples. Can anyone give me
the format for this entry? Thanks.'
I had a Starboard II and Spirit board on my 1000. With both installed
I never got the RAD: to work until I moved up to 2.0. None of the
Abacus books have the format for MASK either. Maybe ASDG's VD0 might
work better.
Abacus books >> nil:
Mask value for a Starboard II can be anything. For compatability reasons
I'd make it $7ffffffe.
{@_@}
I was looking up the format for mask for a person using a Minimegs and a
Insider II. His 1000 would guru when trying to mount RAD:. I no longer
have my Starboard, when I did I could not get the RAD: to survive a
reboot. Thanks anyway.
Richard -> via the Amiga 1000 AutoPilot
What version of the OS? What memory mapping for the Insider? It is
possible that there is an interaction of softwares here that corrupted a
critical piece of information RAD sticks away in interesting portions of
memory. (Under 1.3 "setpatch -r" command must be run. (Or something like
that. It is so long since I ran 1.3 that I am no longer sure. I do
remember it was caps sensitive and format sensitive on that command.))
{@_@}
BTW – MASK for RAD: on an A1000 ought to be 0xffffff.
He said he was using 1.3. It sounded like he solved the problem by
changing the jumpers on the Insider and running addmem to configure
it at the right address, then mounting RAD:. The Insider was at $C00000
before he changed the setup, $200000 after. Not having experience with
the Insider just the Spirit board, Starboard, RAD: and also notrunning
1.3 for a while, I wasn't alot of help.
Richard -> via the Amiga 1000 AutoPilot
David,
Is RAD: the only thing that crashes? If so then I believe your problem
is solvable. If I remember correctly, RAD will not span memory blocks.
This means you cannot set RAD's size larger than the largest available
chunk of FAST ram available. My guess is that you have it set for 1.5 meg
exactly. Reduce it to 1 meg and see if it does any better.
Dean
DKB Software