Conference hydra::amiga_v1

    well... the 500 doesn't have a LA (left Amiga)
    it has a LC (left Commodore) as in Commodore-Amiga
    
    For a quick database of disks i do the following:
    1. COPY C:DIR RAM:
    2. PATH RAM: ADD
    3. put formatted disk in DF0:
    4. MAKEDIR mydisks
    5. CD mydisks
    6. DIR >diskname.dir DF1: OPT A    for each disk
    7. then can use "SEARCH #? string" to hunt for which disk a file
       is on.
    
    For any "*.*" fans, there is no such thing as file extensions.
    And no such thing as specifying the current directory as "*.*".
    The AmigaDOS equivalent of "COPY *.*" is "COPY #?"
                               "COPY f.*" is "COPY f.#?"
                               "COPY *.TXT" is "COPY #?(.TXT)"
    
    When deleting or copying files, use a | between filenames.
    "COPY A.TXT|B.C|D.BAT" will try to copy all three files instead
    of aborting the first time it encounters an error.
    
    -dave
    

    I agree on the range of knowledge..I am just learning how to spell
    Amiga..Us F/S guys are slow sometimes..I didn't know I could do
    multicopies...Here I have been coping single commands..This Amiga
    is a neat machine, but the information seems to be really dispersed
    in many manuals..It sure didn't come with owner's manual..
    By the way, where can I find some info on Music and graphics...like
    both areas are real gray to me..
    

    See the recent note on Abel Supply prices.  There is a pretty complete
    list of available Amiga publications.
    
    Microsoft has published a pretty nice book called 'Graphics and
    Sound on the Amiga'.  I've seen it in most WaldenBook stores.

    things seem to be pretty quiet here recently.. :-)
    
    found this one in an example on usenet,
    
    connect to your favorite directory, then to copy from another directory
    to it just:
    
    COPY another_directory/some_file ""
    
    It actually put it in my connected directory!  I've been hunting
    for how to do that in the AmigaDOS manuals for months.
    
    -Dave

I'd like to create a copy of WB 1.2 that I can use to run VT200. What I want to
do is delete whatever is "expendable" from the WB disk to make room for VT200 so
as to leave the second drive free for whatever. Right now, WB is about 99% full.
I suppose that there should be a copy of VirusX on the disk as well. Any
suggestions of what to delete/keep? 

Another possibility is to copy from WB to RAM: whatever is necessary so I don't
have to constantly replace the WB disk. If I do this, will I be able to do a
disk-to-disk copy (duplicate) without having to keep swapping disks? How do I go
about doing this? 

Dave.

    re: .5
    
    just delete anything you don't use out of the c,fonts,and printer
    driver and top level directories.  Anything you decide later you really
    did need can be copied from your original WB.
    
    I usually delete Preferences, Notepad, Clock, icons, fonts, all
    the printer drivers except Generic and Epson.
    
    re: doing diskcopy running from RAM:  are you asking how to do it
    from the workbench or the CLI?
    
    -Dave

    
    You should always delete unused printer drivers from WB.  These
    are in DEVS/PRINTERS.
    
    You can lose many commands in the C directory, such as EDIT, JOIN,
    SEARCH, DISKDOCTOR etc.  Vital C commands are...
    
    ASSIGN
    DIR
    LIST
    COPY
    MAKEDIR
    LOADWB
    NEWCLI
    ENDCLI
    PATH
    
    and so on..
    
    You could make a usable system in RAM: with a startup-sequence like..
    
    MAKEDIR RAM:C
    MAKEDIR RAM:SYSTEM
    COPY DF0:C/DIR   (and any other C commands) to RAM:C
    COPY DF0:SYSTEM/DISKCOPY TO RAM:SYSTEM QUIET
    COPY DF0:SYSTEM/FORMAT TO RAM:SYSTEM QUIET
    
    Then, you must tell AmigaDOS where to find the C and SYSTEM directories
    via the ASSIGN command, ie;
    
    ASSIGN SYSTEM: RAM:SYSTEM
    ASSIGN C: RAM:C
    
    and so on.  The PD DEFDISK command will make all logical assignments
    to any device, ie;
    
    DEFDISK RAM: will make all the necessary assignments.  There is
    a catch; DEFDISK will fail unless the destination has C, SYSTEM,
    L, LIBS, DEVS, and FONTS directories already created.
    
    Hope this helps.
    
    Ed.

    I forgot to add that once SYSTEM/DISKCOPY and SYSTEM/FORMAT are
    copied and ASSIGNed to RAM, you will be able to format and copy
    disks without being asked for the WB disk.  This also assumes that
    SYSTEM has been added to the searchlist via the PATH command (see
    your default WB startup-sequence to see how this is done).
    
    Ed.

     Dave
     
     I went through this recently, (but still qualify as a beginner
     so take my advise for what it is worth) and can get you started.
     
     I deleted all the extra printer drivers located in the directory
     devs/printers. This alone may be enough to leave room for VT200. 
     
     I think my next step was to delete the demos, since after you see
     them once or twice you don't HAVE to have them on the WB.
     
     Other options include the EDIT "editor" from the C directory.
     If you try it once you'll see why I blasted that.
     
     I forget the exact directory path, but you can delete any extra key
     maps for foreign languages. Generally you will use USA0 or USA1
     depending on Amiga model. I _think_ USA0 is Amiga 1000 - USA1 is
     500/2000. 
                              
     I suggest checking out some Amiga magazines too.  It seems that
     many of them have articles detailing how you can do exactly what
     you request (except using VT200, of course). The info is probably
     in this conference too; I've found a lot here! 
          
     Since I got my 500 a few months ago I have been reading the rags
     like crazy. Overload prevents me from saying which issues offer
     the info.
         
     Dave R
     

     Geez you guys are fast!  Like I said in .9
    >> The info is probably
    >> in this conference too; I've found a lot here!
     
     Sometimes it just sneaks in before you hit CTRL/Z.  8-)
     
     Dave R. 

    re: .5  diskcopy from ram:
    
    I usually do diskcopy and format from the CLI, it always bothered
    me that CBM hides those commands in the system directory instead
    of c.
    
    so I normally "copy system/diskcopy|format vd0:", then 
    "cd vd0:" before diskcopying.
    
    For formatting lots of disks on a 2 drive system, I do the following
    
    1. copy system/format vd0:
    2. copy c/info|run vd0:
    3. copy c/execute vd0:e
    4. copy f vd0:f
       where f is a file containing the following:
         run format drive df0: name empty noicons
         run format drive df1: name empty noicons
    5. cd vd0:
    6. insert two disks needing to be formatted
    7. e f
    8. ignore the "format failed" error message, format is just
       complaining because it was "run".  Use info to check if
       the disks formatted correctly.
    
    the above method is good for sanity checking if a box of single
    sided disks can be formatted double sided.  Better to find out
    that way than halfway thru a diskcopy.

Re: Diskcopy from RAM:

I am sort of unusual in that I use the Workbench, not the CLI, most of
the time on my Amiga.  CLI users aren't the only ones who can make use
of Diskcopy from RAM:.

Do the following in your Startup-Sequence or whatever:

Makedir RAM:System
copy sys:system/diskcopy#? RAM:system
copy sys:system/format#? RAM:system
assign sys: ram:

After doing this, the Workbench will load the Diskcopy and Format programs
from RAM:system rather from floppy.