Conference hydra::amiga_v1

    The assign command will do what you want.  Try Assign libs: FF0:libs
    where FF0: is any mounted drive name with enough room for all you
    lib files.
    
    Alan
    

    I guess my real question is, what is the minimum amount of stuff
    to boot from the 1st partition and then can i put Workbench in a
    large partition and not worry about it.
    
     mark

    The first partition can be the entire hard disk if you want.  But
    depending on your controller, you may not be able to use the Fast
    File System.  Therefore, most people make the first partition small
    and then use the Fast File System on the rest of the disk.

    Yes, that is why i have the problem. We made the 1st partition 900k
    to hold WorkBench in the old file system (required by 2090A to
    autoboot). The rest of the disk is FFS. I still want to boot off
    the 1st partition, but i really don't want to keep a copy of WorkBench
    there and i don't want to make it any bigger (well i really don't
    want to reformat it to make it bigger or smaller, but i will if
    i have to). Can someone post a startup-sequence that doesn't require
    WorkBench to be in the bootable partition or point me to some
    documentation?
    
     mark

    I did what you want to do.
    
    I have  a  2  cyl.  partition (DH0:) that I autoboot from.  In the
    1.3 docs near the back they give you some information on how to do
    this and (I think)  a  list  of  the  files  you have to have as a
    minimum to get started.
    
    What I do in dh0:s/startup-sequence is something like this:
    
        cd c:
        fastmemfirst
        defdisk fs1:  !fs1:  is my first 10 Meg fastfile partition and
                        defdisk  is a pd program (should  be  on  Tape
                        etc.) that will do all the assigns required.
        execute s:startup-sequence !  this will execute the startup in 
                                      fs1:s/   for  the  rest  of  the
                                      stuff that needs to be done.
    
    I'll try and remember to  dial  in  tonight and give you a list of
    files I have in DH0:.   One  thing  to remember is that the driver
    requires memory for each partition used.  The more partitions, the
    more memory used.
    
                Clint          

    OK, using the 1.3 enhancer book i finally got a minimal bootable
    partition. Now, how do control the placement of all these damn icons?
    I just read somewhere how to make them free floating or fix them
    where you want them, but i can't remember where i read it (i've
    got a stack of Amiga reading about 2' high).
    Also, i'm not having any success using the Lattice procedure
    'install_hd', inside is <hdisk>, is this a parameter? or a logical?
    or what. How does it get the value i want it to have (ie FSHD0:)?
    I need help (more disk space too)!
    
     mark

    Move the icon to the location you want it. Click it once (not twice!).
    Then pull down the Special menu from the workbench and click Snapshot.
    That will write the icon to the current location in the window.
    Now, if you resize the window or move it, you'll want to perf�m
    a similar function. If you are in the root directory of the disk,
    click the disk icon once and select Snapshot again from the Special
    menu. If you are in a subdirectory, click the drawer for that
    directory once, and then do the snapshot.

    I would HIGHLY recommend reading chapter 4 of the Amiga 2000 Intro.
    It is entitled, Using the Workbench. There is probably an equivalent
    chapter in the 500 and 1000 manuals.
    
    Paul
    

    Remember that the snapshot only updates the positions and window sizes
    for currently selected icons.  But holding down the shift key will let
    you select multiple icons.  So after you get everything positioned
    and sized the way you want it.  Hold the shift key and and select
    all moved icons and the drawer icon for any moved or resized windows,
    before you do the snapshot.

    True, but do be careful when selecting multiple icons with the shift
    keys. One slight twitch can cause all those selcted icons to be
    instantly transported into the last draw selected (that is if you
    are selcting directories). I've had this happen a couple times on
    Wb 1.3. Not sure if its a bug or a feature!

    Following is what I do to transfer control from the boot partition to
    the FFS partition, and what each directory contains.
    
    
    This is the main directory:


     c (dir)
     System (dir)
     l (dir)
     devs (dir)
     s (dir)
     t (dir)
     libs (dir)
     Expansion (dir)
  .info                            Disk.info
  DiskMaster                       DiskMaster.info
  shell                            Shell.info

And each one broken down:


C:
  Assign                           Binddrivers
  CD                               Execute
  FF                               Mount
  Resident                         SetPatch

SYSTEM:

  FastMemFirst                     SetMap

L:

  Aux-Handler                      Disk-Validator
  FastFileSystem                   Newcon-Handler
  Ram-Handler                      Shell-Seg

DEVS:

     keymaps (dir)		(put what you need in this one)
     printers (dir)		( "    "   "    "   "   "   " )
     clipboards (dir)		(empty)
  ljsystem-configuration *          MountList
  ramdrive.device                   system-configuration *
                              
*    (when I borrow an LJ250 I rename ljsys.. to system-configuration
      and that way I don't have to go trough preference each time)
    
S:

  CLI-Startup                      DPAT
  PCD                              Shell-Startup
  SPAT                             start-hd
  startup-sequence                 

T:

  Command-00-T01                   

LIBS:

  diskfont.library                 icon.library
  info.library                     mathieeedoubbas.library
  mathieeedoubtrans.library        mathtrans.library
  translator.library               

EXPANSION:

  .info                            hddisk


And this is my startup sequence:

DH0:c/setpatch
DH0:System/FastMemFirst
DH0:c/BindDrivers
assign t: DH0:t
DH0:c/execute DH0:s/start-hd
wait >NIL 60 sec


This is "start-hd"

DH0:c/cd c:
FF >NIL: -0   ; start FastFonts
resident c:assign pure
assign Devs: DH0:devs
DH0:c/mount DI0:
assign Devs: DI0:devs
assign c: DI0:c
assign Fonts: DI0:Fonts
assign l: DI0:L
assign Libs: DI0:Libs
assign T: DI0:T
assign hd: DI0:
assign S: DI0:s
assign system: DI0:system
assign Sys: DI0:
assign ENV: DI0:Env
assign dpaint: DI0:
assign wp: DI0:wp
assign chessmaster: DI0:echecs
DI0:c/stack 20000
DI0:c/copy DH0:DIsk.info ram:
DI0:c/path sys:system ram: sys: s: add
Sys:System/SetMap usa1
DI0:ced -r
DI0:c/loadwb
DI0:c/SetClock >NIL: load   ; Quelle heure est-il?
DI0:c/resident CLI L:Shell-Seg SYSTEM pure   ; activate Shell
DI0:c/resident c:Execute pure   ; pre-load the Execute command
DI0:c/mount newcon: ; mount the improved console handler
DI0:c/execute DI0:s/start-DI0
break 1 c

This is "start-DI0"

cd di0:
newcli "CON:0/0/300/100/depart" from login.script
endcli >NIL:

And this is "login.script"

runback c/machII	(mouse accelerator and screen blanker)
runback c/faccii	(floppy accelerator)
run c/virusx 0 10	(no comments)
endcli >NIL:



Some of these might be not quite right, all I know i know is that it works.
My Dho now takes about 330Kb.  I seems that it is all that is required to
transfer control to the FFS partition.


Jean

    I am planning to add a hard drive to my 2000 system soon, within a week
    I hope.  It will probably be a 105 meg Quantum drive on the HardFrame
    (or possibly GVP) hardcard controller.
    
    Would some of you "experts" like to recommend a partition configuration
    for this setup?  I'm leaning toward equal sized partitions as possible
    backup/DiskSalv options until I need the extra space, maybe 4 parts
    (all FFS).  Does this sound like a good strategy?

    Re: .11
    
    If you can afford it, get the HardFrame (or wait for the 2091...).
    Your idea about equal sized partitions for possible salvaging purposes
    is completly "right". That's the the way I do it, too.
    
    Regards,
    
    <CB>