i know i need to edit the mountlist for RAD in devs/devices.
i am using wb3.0
thanks
--
DeCreator
Founder of the D&B WebRing
http://www.callieu.demon.co.uk
If you go to Aminet look for this:
statram31.lha disk/misc 9K 232 V3.1 of the recoverable ramdrive
Jesper
A1200 with Blizz 1230@50Mhz, 16 mb fast, 12xCD-SCSI, 540 mb HD.
<922703093.4415.0...@news.demon.co.uk>...
Use the BufMemType field in the mountlist, I can't remember what the value for
fast ram is though.. it might be 1.
Jon
richard
Jonathan Potter wrote in message <7dot7v$1a...@enews1.newsguy.com>...
DeCre> How do i mount a rad disk so that it uses fast ram instead of
DeCre> chip. I have 8mb of fast and want to mount a couple of rad
DeCre> disks.
I remember reading somewhere a long time ago that fast ram had to be
of a certain type for rad disks to use it. I can't remember the
"type." It may have had something to do with vectors or autoconfig,
or something like that?? Anyone know exactly what I'm trying to
say???
I had a GVP 030 @ 40MHz Turbo card for my 1200 with fast ram, and I
could never get RAD to use fast ram.
Now I have a 4000T with 060/PPC, and RAD uses fast ram with no
problem automatically.
--
------------------------------------------------------------------------
http://home.earthlink.net/~amigalander/
Amigas and Highlander - What else is there?
------------------------------------------------------------------------
WfW
Gordon.
--
EMail: mailto:Gordon...@gmx.net
Rechner: A1200T/3.0/030/882/32MB/3GB/8xCD/BJC250/...
Demnächst: RW Erfurt - FSV Zwickau 31.03. 18:15 Steigerwaldstadion(EF)
>Another RAD type device available from Aminet is Statram.
>
>It is safe and it's size (volume in kbs) can be varied in the ToolType.
>Also you can have up to 9 Statram devices mounted (depending on
>available RAM)
>
>I have one on my Blizzard 040 sys Workbench of 4 Meg size.
>
>After warm re-sets (and crashes, very few) it retains it's info.
You've missed out one of StatRam's greatest advantages: it only
uses as much memory as it needs. The size you set up is just
a maximum size. Contrast this with RAD:, which grabs and holds
its full allocation whether it needs it or not. If you're running
short of memory and have a large file in SD0: that you don't need,
just delete the file and the memory is freed.
StatRam is amazingly robust; I've had it survive violent crashes
that have sprayed garbage all over memory.
I have never used RAD: and see no reason why I ever should.
--
cgi...@sky.bus.com (Charlie Gibbs)
Remove the first period after the "at" sign to reply.
>Jonathan Potter wrote in message <7dot7v$1a...@enews1.newsguy.com>...
>>In article <922703093.4415.0...@news.demon.co.uk>,
>"DeCreator" <decr...@hotmail.com> wrote:
>>>How do i mount a rad disk so that it uses fast ram instead of chip. I have
>>>8mb of fast and want to mount a couple of rad disks.
>>>i know i need to edit the mountlist for RAD in devs/devices.
>>Use the BufMemType field in the mountlist, I can't remember what the value
>for
>>fast ram is though.. it might be 1.
>I know it is bufmemtype but i tried 1 to 10 and they always mounted in chip
Try
Kickmem.lha util/cli 1K 84+Replacement for Patchmem
--
/// /_\ _ _| |_ ___ _ _ _ _ http://www.bigfoot.com/~TheAntony
__ /// / _ \| ' \ _/ _ \ ' \ || | Amiga Translators' Organization
\\\/// /_/ \_\_||_\__\___/_||_\_, | (*Serbian department*)
\XX/ TheAntony bigfoot com |__/ Team *AMIGA*
while(!asleep) sheep++;
>I have never used RAD: and see no reason why I ever should.
Does "statram" support this:
1> diskcopy df0: rad:
With RAD: you have a copy of the disk in RAD: on less than a minute. (This
is by far the quickest way to copy disks to/from a HD, i.e. going via RAD:.)
/Hannu _ // 1985+
\X/Amiga user
Personal rc5-stats: 18,149 2^28-key blks, i.e. 4,871,835+ Mkeys, M68K Amiga.
450Mhz PII/MMX adding 1.1M RC5 & 4.6M DES keys/s to this since end of Dec'98
--
CHASTITY: The most unnatural of sexual perversions.
And more importantly, DMS writing files to rads. By making a small change to the rad
filename (rad1, rad2, etc) and changing the device file in the name you can mount many
of them and do install dms files without mucking about with floppies!
> I know it is bufmemtype but i tried 1 to 10 and they always mounted in chip
I remember there was some tool for this at Aminet. The other way to do it
is to use FastExec. I remember later versions of FE failed to make it happen,
so I kept some old version, v1.1. If you'll get problems w/ the new one, mail
me, so I'll send you this old one.
Blizzard users probably use BlizKick w/ LOCALFAST option.
--
EM@: dpu...@zesoi.fer.hr, rat...@usa.net AKA: Dalibor Puljiz
URL: http://islands.zesoi.fer.hr/~dpuljiz ICQ: 2463483
ORG: *WARP - Croatian Amiga Magazine* CTY: Croatia, Europe
I asked Jesus, "How much do you love me?"...
"This much," He answered, then He stretched out his arms, and died.
>Rad will not use Fast Ram if you are using certain accellerators
>eg: Blizzard because of memory addresses.
so use blizkick, which is excellent for other reasons as well
--
Adam Atkinson (gh...@mistral.co.uk)
ZOOGE
>And more importantly, DMS writing files to rads.
Ack! Get FMS from Aminet - it's a way better solution that RAD: (and even
lets you directly read/write to ADF files).
--
Kirk Strauser Member // http://members.dialnet.net/teknique/
Team AMIGA \X/ http://csc.smsu.edu/~strauser/RA.html
New page! See http://csc.smsu.edu/~strauser/honeypot.html for system info
KS> john lewis wrote:
KS>
KS> >And more importantly, DMS writing files to rads.
KS>
KS> Ack! Get FMS from Aminet - it's a way better solution that RAD:
KS> (and even lets you directly read/write to ADF files).
KS> --
I couldn't live without FMS and HFM. I've used them for years and
they are very handy indeed. Also, VDO also on Aminet is much, much
better than RAD. I t has may more options especially size of the
disk.
--
------------------------------------------------------------------------
Amiga user and damn proud of it!
------------------------------------------------------------------------
A clarification; This has NOTHING to do with RAM *addresses*, but a lot to do
with how the RAM-segments has their attributes set.
Blizzard accelerators has their local RAM attributed in such a way
that RAD: avoids it.
"FastRAD" and some other tools like it allows for removing the "offending"
attribute.
(The attribute says that "this RAM segment isn't available during a
reset", which makes RAD: believe that it can't survive resets when beeing
inside that segment)
/Hannu _ // 1985+
\X/Amiga user
Personal rc5-stats: 18,233 2^28-key blks, i.e. 4,894,383+ Mkeys, M68K Amiga.
450Mhz PII/MMX adding 1.1M RC5 & 4.6M DES keys/s to this since end of Dec'98
--
Magicians pull rabbits out of hats, psychologists pull habits out of rats.
>>>Rad will not use Fast Ram if you are using certain accellerators
>>>eg: Blizzard because of memory addresses.
>>so use blizkick, which is excellent for other reasons as well
> A clarification; This has NOTHING to do with RAM *addresses*, but a lot to
> do
>with how the RAM-segments has their attributes set.
I am aware of this. blizkick solves this.
> Blizzard accelerators has their local RAM attributed in such a way
>that RAD: avoids it.
indeed
> "FastRAD" and some other tools like it allows for removing the "offending"
>attribute.
> (The attribute says that "this RAM segment isn't available during a
>reset", which makes RAD: believe that it can't survive resets when beeing
>inside that segment)
I'm not sure if rad: really CAN survive reboots on my blizzard. I
haven't used the "boot from rad:" trick since my 1.3 floppy-only days.
I also almost never use RAD: anyway. but when I do, I like it to be in
fast ram :-)
--
Adam Atkinson (gh...@mistral.co.uk)
You mean, you'll put down your rock, I'll put down my sword, and
we'll try to kill each other like civilized people?