Conference hydra::amiga_v1

    That's an easy one .. DISKCOPY and FORMAT are not located in your
    C directory to begin with. They are located in the SYSTEM directory
    (or the UTILITIES directory -- not sure which).
    
    Paul

    Paul:
    
    Right, but I copied the entire 'System' directory to ram:, then
    added 'Ram:' to the search list, that should work, no?
    

    You have to
    
    MAKEDIR RAM:C
    
    then 
    
    COPY C/#? RAM:C
    
    then
    
    ASSIGN SYS: RAM:C   (not sure of the syntax here, but you have
                         to assign the SYS:C directory to RAM:C)
    
    After that, just copy FORMAT and DISKCOPY to RAM:C from whereever
    they are on your Wb disk (probably SYSTEM or UTILITIES drawers.
    
    You can also set up PATHs using the PATH command in your
    V1.2 Startup-Sequence.
    
    By the way ...  256K 150 ns rams are $2.65 apiece ... 4 will give
    your new board 2 MB!
    
    Paul

ASSIGN SYS:C RAM:<dir>
ASSIGN SYS:SYSTEM RAM:<dir>

where <dir> has the commands and system utilities you copied to 
ram.  Workbench probably looks in SYS:SYSTEM, which if you haven't
reassigned, is still the workbench disk.  (You probably also
need ASSIGN SYS: RAM: as well, don't know about this one)
-Dave

    re: 3 & 4...
    
    Thanx guys, I'll check it out and give it a try...but I thought
    the 'PATH' command would handle it without having to 'ASSIGN', since
    it worked on C: commands...

Lest someone become confused, there is a program named DiskCopy in both
the c and System directories.  However, c/DiskCopy gets its arguments
from the CLI command that starts it while System/DiskCopy gets its
argument from an Intuition message from the Workbench.  These are two
distinct programs.

The Workbench runs the program SYS:System/DiskCopy to copy a disk.
(SYS: is the logical device name assigned automatically to boot
workbench disk.)  Thus, if you create a System directory in RAM:
and copy DiskCopy and Initialize into RAM:System, and you then do
"Assign SYS: RAM:", you are all set.

I don't have a copy of 1.2, but I am fairly sure that PATH only
affects were the CLI looks for commands.  In other words, it is
like multiple active assignments for the C: logical device.

Looking over the command procedure in note .0, I believe that
several other actions may cause a request to insert the bootup
workbench disk.  For example, if you go into the Notepad and
try and change the font selection.  The reason why is that
the system looks for font files using the FONTS: logical device.
By default, FONTS: is the Fonts directory in the bootup
workbench device. An "Assign FONTS: RAM:Fonts" will avoid
that disk request.

The full set of logical devices that you may want to assign are:

SYS:		Used by workbench to find SYS:system utilities.

C:		CLI commands directory (path is a better alternative
		if you are only going to put a subset of commands
		in RAM:)

L:		The l directory on the bootup disk.  Contains parts
		of Amiga DOS.

S:		The s directory on the bootup disk.  Contains the
		startup-sequence file.  The Execute command looks
		for the command file on S: if it cannot find the
		file in the current directory.  Some programs, like
		Wecker's VT100, look in S: for init files.

LIBS:		The libs directory on the bootup disk.  Contains the
		loadable libraries.

DEVS:		The devs directory on the bootup disk.  Contains the
		device drivers.

FONTS:		The fonts directory on the bootup disk.  Contains the
		font definition files.

Whether to move all of the above to RAM: depends on your personal
preferences.  If I was you, I moving FONTS: and S: to RAM: would be
a very low priority because I rarely cause these directories to be
accessed.  Moving SYS:system and most of C: to RAM: would be a high
priority.  Rather than copy LIBS: to RAM: (a somewhat medium priority
item), I would write a program that did an openlibrary on all the
libraries to fault them into memory for real.  That way there is
only one copy of them resident (the shareable, executable image)
as opposed to two copies (the copy in the ram disk and the shareable,
executable image.)  If you move the device drivers to RAM:, make sure
you only copy the device driver for your model of printer and not
all the random printer drivers that AmigaDOS provides.

    Randy, you hit it right on the head.  As I mentioned in .0, the
    Diskcopy and Format commands worked fine FROM THE CLI when copied
    and assigned to Ram:, but the Workbench versions insisted on using
    the SYS: boot disk.  I now understand completely.  Thank you.
    
    PS:  With a 2-meg board, I probably will copy most of the useful
    	 Boot disk into an archive, then load the archive into ram:
    	 and de-archive it....presto, 2 totally free drives!

    Get the Microbotics board yet? Have a source for 256K 150ns CMOS
    DRAMs yet?

    re .3: I think it will take 32 256K RAMs to get another megabyte.
    4 chips will only give 1 megabit. Still a good deal though.
    
      mitch

    I ordered the board on 12/2/86 from Arizona, shipped UPS gropund.
    
    I hope to have it today or tomorrow!
    
    Spoke with some more people who are using it and they absolutely
    love it.
    
    Ed