Conference hydra::amiga_v1

Well, I don't know about the A2000, but as far as the hard drive goes
use the mounting holes on the FRAME (sounds like the 4 you found).
The frame as opposed to the HDA (where the actual disk platters and heads are)
provides shock/vibration isolation.

John

    Paul,
    	I just recently installed a 65MB Seagate in my 2000. The Seagate
    has small mounting brackets attached in four places which provides
    screw holes both underneath and on the side of the drive. The Amiga
    uses the holes in the side. The screws required are 6/32 by .25".
    If my memory serves me right, these brackets were held on by screws,
    perhaps in the holes you have in your drive.
    
    The NEC 3.5" floppies use 4-40 screws for mounting. I replaced the
    ones which come with the drive for slightly longer ones so I could
    install washers under the heads. There is no danger of shorting
    out anything with the longer screws since there is no electronics
    under the mounting holes in the drive.

    On the subject of hard drive cabling ...
    Does the 2090 board comes with the cables needed to connect a hard
    drive? Or, must one rely on whatever is supplied with the hard drive?
    I don't have any cables with my hard drive, so I am hoping that
    the 2090 supplies them.

	No. No cables are supplied with the A2090, because they
	didn't know whether a user would be installing an
	ST506 or a SCSI drive.  Sorry.

    So, I will need two cables? One for the power and one for the drive?
    I believe I saw a cable inside for the hard disk light.

    Is the cabling pretty standard? In other words, will whatever comes with
    the drive fit the connections on the 2090? Haven't seen the 2090
    yet, so I haven't the foggiest. What's the difference between DMA
    and SCSI cabling.? I have an RD-31 and an RD-52 sitting in my office.
    Are they both DMA?
    
    Paul

    
    You will need two cables if you are going to be connecting an ST506
    drive or you will need one cable for SCSI.  Hint: The ST506 cables
    are the same cables used in uVAXes to connect to HDs (RD53, RD54).
    
    The two cables have edge connectors on one end and pin connectors
    (female) on the other end.  I forget the number of pins on each
    cable, but one is smaller than the other.
    
    Be very careful when plugging the cables into the A2090.  The male
    pins on the 2090 are just sitting there exposed and there are no
    cable guide mechanisms other than lining up the pins with the
    connector.  Make sure that you have the cables plugged in right
    side up on the A2090.  I spent 30 minutes figuring out that I had
    mine plugged in upside down.  The installation manual mentions this,
    but it is sorta easy to overlook when reading through it.
    
    brad

>    I forget the number of pins on each

34 and 20

    Yep, the RD-51 cables seems to fit just fine. There are 3 of them
    ... two edge connector ribbon cables in the pin configs you described,
    and one 4-pin power connector. I assume there is an appropriate
    jack or plug on the A2000 power supply?
    
    Paul

    Yeah, my A2000 came with 2 4-pin power connectors coming from the
    power supply.
    
    Ed.
    

    
    You won't need the power supply cable, as you will be using the
    2000's power supply.  Or at least that is how i did it.  There 
    should be power cable sitting there in the drive bay unused.  There
    is one power cable for each of the drive bays, one should be used
    by your internal drive, and then two others unused (unless you have
    a second floppy drive free.  Good luck.
    
    brad
    

    
    re .11
    
       free = there.
    
    re .10
    
    	Sorry 'bout the duplication...welcome to simul-noting.
    
    b

    I finally installed the NEC 40 Mbyte hard drive. After spending
    much time puttering around with the differences between MOUNT vs.
    BINDDRIVERS and Expansion/HDDISK vs. Expansion/HDDISK.DEVICE and
    lousy NEC documentation, I managed to get the darn thing formatted.

    I have two problems though:
    
    o  When I boot, I hear a nasty 1 or 2 sec long BUZZ from either
       DF0: or DH0:. I haven't been able to isolate it. But it seem to
       occur when the BINDDRIVERS command is executed from within
       s/startup-sequence. Any thoughts?
    
    o  Some programs generate gurus when run off the hard disk. For
       example, CHESSMASTER 2000. Any thoughts on curing that problem?
       (Fortunately GOMF V1.0 gets me out of trouble there.)
    
    Paul

    I was never able to get CM2000 to run off of the HD.  I believe
    there are some invisible files needed to run the program.
    
    It's odd, since I de-protected it long ago with Marauder.
    
    Ed.

    How would one go about getting the startup-procedure transferred
    to the hard disk asap. Right now my entire s/startup-sequence is
    read from DF0:. Is there a way to just BINDDRIVERS in df0:s/ and
    then continue with the startup from dh0:s/ ??

  
    Can any of you Megabyte addicts rep with your Hard Disk
    startup-sequencelistings?
    
    Paul

You need to assign all the system logicals to point to DHx.
(i.e. SYS:. C:, L:, DEVS:, FONTS:, LIBS: etc)

There is a program called DEFDISK.C  but I haven't been successfull
in compiling it under Lattice 4.0 yet...

John

    I'll post mine later tonite...as for the buzz...I think its "normal"
    given the rash of postings on it on usenet, etc.  My disk also does
    it...I think its just the re-calibrate of the head after being "parked"
    or some such nonsense...any of you other disk guys care to comment...
    
    

Yup. Most hard drives have an audible recal.    

Joh    

re:16
        I think I did, or maybe I just used the compiled version...I think
    its in the archive here..........(multitasking at work).........nope,
    the code is, but no binary here...can upload...later...scott
    
    

    My hard drive makes a funny noise when I power up the Amiga, but
    it's not terribly loud.  It makes a similar noise when I power down
    the Amiga.  No noise on BindDrivers, though.
    
    My hard disk is mounted inside the system box, so that may contribute
    to its quietness.
        John Sauter

    OK, here's my DF0:s/Startup-Sequence 
    
    Mount DH0:
    Mount DH1:
    run execute DH0:s/HDBoot
    EndCLI >nil:

    My HDBoot file goes something like this...
    
    DEFDISK DH0:
    ..... <all the sordid custom garbage I perform>
    
    Maybe we should start a new note posting all our startups.
    
    Ed.

    About the noises...
    
    My Seagate 277n has an autopark feature.  They retract the heads
    to a safe radius before shutting down the spindle.  This produces
    a little chirping sound.

    My startup-seqeunce for my Supra
    +------
    SUPRAMOUNT
    dh0:c/execute dh0:s/startup-sequence
    ENDCLI > NIL:
    
    +------
    
    Initially I was confused because the busy light on DF0: would stay
    on for 5 or 6 seconds.  Then I realized that it was loading the
    device drivers for the supra.  
    
    -Paul

    Here's mine...Once you "Mount" and then change defaults, the rest
    comes from the hard drive...
    
    Note...I use shell almost exclusively, even for the startup!
    
    scott.
    
    ------startup-sequence----from df0:----------
    
mount DH0:                              ;mount hard disk...
defdisk DH0:sys                         ;make it the default system
mount DH1:                              ;mount the other partition
cd DH1:                                 ;and access it to make it show up on WB
run c:shell -c source s:shell-startup   ;now do the rest in the shell
endcli >nil:                            ;exit
    

    -------this is the shell file to "finish" startup-----------------

#
#    Shell-startup...Boot up the Amiga using Shell
#
set _path     "c:,sys:utilities,sys:system"
#
sys:utilities/setfont pearl 8
echo "Amiga Shell-Startup - Wedge version 1.0"
#
#           Mount the RRD...
#
mount vd0:
cd vd0:
#
#           Add some buffers for the Floppy's
#
addbuffers df0: 20
addbuffers df1: 20
#
#
#           Set the time
#
run c:execute s:timeset
#
#
#           Make any necessary assignments....
#
assign ARCTEMP: ram:
#
assign lc:      dh0:lc/c
assign lib:     dh0:lc/lib
assign include: dh0:lc/include
assign quad:    RAM:
#
assign extras:  dh0:
#
#
#           Add paths for AmigaDOS
#
path reset sys:system sys:utilities lc:
#
#
#           Do the final utilities to get things going....
#
stack 8192
runbackground -1 sys:utilities/rslclock
# increase stack for command shells...
stack 24576
runbackground -1 sys:utilities/popcli 600 newcli con:0/1/640/199/Shell FROM s:Shell-Login
#
#           Bind drivers, load WB, and quit
#
BindDrivers
sleep 2
LoadWb
sleep 2
runbackground -1 sys:utilities/browser
#
stack 8192
sys:utilities/wkeys s:wkeys.default
sys:utilities/wiconify
#
quit

I can't seem to get the STACK and CD from startup to follow to CLI's
created later.

I have a 

	CD place_I_want_to_be
        STACK 8192

at the end of startup (called from startup-sequence)
but new CLI's (popcli or cli icon style) always end up CD at SYS, and stack
4000??

I tried them before and after loadwb

John

    don't know about the default dir, since I use the a shell startup
    source file to set all my alias's, etc.  BUT, stack from popcli
    seems to be related to the stack you give popcli II (not 3) when
    you start it...so I up the stack during the startup, runbackground
    popcli with a command to spawn the newcli, and invoke a command
    file (one of the v1.2 goodies), and that takes care of it...
    
    scott
    

    
    
    here is line from my startup....
    
    runbackground -1 sys:utilities/popcli 600 newcli 
    				con:0/1/640/199/Shell FROM s:Shell-Login

    And since you are running a script, any commands like stack, cd,
    etc. can be issued...
    
    scott
    

Re: .25, .27

The various CLI attributes like current directory, prompt, stack size, etc
are inherited by new CLIs created by the NEWCLI and RUN commands.  The
newly created CLIs inherit the state of the CLI that created them as
was current at the time of creation.

The Workbench CLI program only allows the new CLI it creates to inherit
the path of the CLI that started Workbench at the time that CLI did the
LOADWB command.  The stack size, current directory, prompt, etc are lost.
As you point out, a CLI created via the Workbench is always connected to
SYS:.

However, POPCLI 2, in effect is a CLI and uses the RUN command to create
the new CLIs.  So, if you set up your CLI the way you want it before
RUNning or RUNBACKing POPCLI, all the CLIs created by that program will
be set up as you wish.

Setting up your initial CLI properly before running POPCLI is superior
to making use of the command file option on the NEWCLI command.  (Well,
at least it is much faster!)

Note that POPCLI 3 has the drawback that it doesn't allow the CLIs it
creates to inherit the CLI attributes.  Because of this drawback, I
recommend using POPCLI 2 instead.

>  the new CLIs.  So, if you set up your CLI the way you want it before
>  RUNning or RUNBACKing POPCLI, all the CLIs created by that program will
>  be set up as you wish.

That sounds good. Thanks!

> Setting up your initial CLI properly before running POPCLI is superior
> to making use of the command file option on the NEWCLI command.  (Well,
> at least it is much faster!)

This is the FROM part, right?  Hmm, just like a LOGIN.COM :-)

> Note that POPCLI 3 has the drawback that it doesn't allow the CLIs it
> creates to inherit the CLI attributes.  Because of this drawback, I
> recommend using POPCLI 2 instead.

What else is in POPCLI III that you give up?

John (who_can_finally_stop_CD_PATH_and_STACKing_his_NEWCLI's!)

    MACH20 also uses the PopCLI2 strategy. I've dumped PopCLI in favor
    of MACH20 (PAULY"AMIGA"::MACH20.ARC). A superb program. Author deserves
    a reward of some sort. Also, it no longer interferes with some programs
    like ProWrite (as MACH16 did).
    
    Paul