Quick setup of a RAD: WB

[Piru]

What is the quickest way to Create a RAD:, copy the 3.1 WB files to it a make the appropriate assigns ?

Open Storage disk or drawer. Open DOSDrivers drawer. Drag RAD to your boot disk Devs/DOSDrivers -drawer. Choose the RAD icon, select Icon/Information. Change highcyl tooltype to 79. The actions above are needed only once.

Mount RAD (by doubleclicking the icon, or by mount RAD: from shell).

DiskCopy DF0: RAD: NOVERIFY

Remove disk from floppy drive, reboot.

Obviously you can also use normal Copy command to fill up the RAD disk if you don't want to copy from a floppy. In this case you can also make the RAD disk larger than 880k, just set the HighCyl higher. HighCyl is (size_in_kb) / 11 - 1.

Once set up and mounted:
Copy CLONE ALL Work:radwb RAD:

[Piru]

someone mentioned that RAD can be created in Fastram, rather than the default Chipram.

RAD doesn't use chipram.

ramdrive.device (that handle RAD) use MEMF_KICK memory for the drive. That is memory that is available at the early stage of the system startup. Some sucky accelerators don't add the memory early enough to system, and thus the memory doesn't have MEMF_KICK set. Thus, the only MEMF_KICK-memory available is the chipmem.

There are several solutions to this, one being the use of BlizKick and its' LocalFast module.
There are some other hacks too that "fix" this, but I'll let the others fill these in...

[Piru]

As far as I know, you can't make more than 1.

Wrong. Just change the unit number.

But, you may need to use the
Install rad: boot
command, before it will boot off of the rad:

Wrong. RAD is always bootable.

[Piru]

A really good tip is to add this entry to the tooltype ( edit the icon)

Buffmemtype=5

That way you`ll use fast memory to hold the rad: device. ( or ram: device).

BTW If you do need to use both fast and chip mem then:
Buffmemtype=3

And If you need to use just chip mem
Buffmemtype=1

Wrong. You can't use these with ramdrive.device, it always use MEMF_KICK memory.

Clarification: BufMemType only affect on which type memory is used for the *filesystem* buffers, eg fastfilesystem buffers. This has nothing to do with the actual device (ramdrive.device) memory buffers. So you cannot move the RAD to chip or fast mem with BufMemType.
[edit: clarification added]

[Piru]

That doc is wrong. BufMemType 1 means public memory, not chip mem.

And yet again, this is ONLY the filesystem buffer memory type, not the type of the actual device memory, which will always be MEMF_KICK.