[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
| Title: | AMIGA NOTES |
| Notice: | Join us in the *NEW* conference - HYDRA::AMIGA_V2 |
| Moderator: | HYDRA::MOORE |
|
| Created: | Sat Apr 26 1986 |
| Last Modified: | Wed Feb 05 1992 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5378 |
| Total number of notes: | 38326 |
5175.0. "3 More 2090A ???'s" by ALLVAX::TERELLA (!Mike Terella DTN 287-3083 CTC2-1/C14) Tue Nov 05 1991 12:07
I am planning to migrate from the 42Mb ST506 drive which came with my
A2000HD (A2090A controller) to a larger SCSI device. Before committing
megabucks to a new drive, I wanted to test things out on a borrowed
SCSI to see how easy/difficult the process would be.(This decision was
made after reading ALL the notes in this conference I could find
concerning HD's, and still being a bit confused!)
First I disconnected the ST506 and booted using the ReInstall floppy
which came with the system. The "Intro to the 2000HD" manual says
to mount the first SCSI device from a mountlist specifying RES2:,Unit 3,
and the first partition will be known as DH2. As this information
comes out of the section on "Adding a second HD", I wasn't sure if it
applied verbatim to "replacing the existing HD". I made up a
mountlist which called out RES0:, Unit 3. Mounted it (i.e. mount RES0:
from mountlist...), rebooted, and the device showed up as DH2. I then
manually ran Prep, which I assume was successful as I was able to
mount and format a first (fastfile) partition, and read/write files
to it.
My intent for using RES0: instead of RES2: in the mountlist was to
try to get the system to recognize the first partition on the SCSI
as DH0, instead of DH2. The ST506 drive came partitioned with DH0,
FH0, FH1. Since I'd like to boot from the SCSI (I haven't tried it yet)
calling it DH0 would make it easier to swap things over as just about
everything directed to the boot partition references it as DH0.
(I know, a boot partition can't be fastfile under 1.3, but this was
just a quick test.)
My 3 questions are;
1) What is the significance in using RES2: (as opposed to RES0:which
seemed to work) in the mountlist prior to Prep?
2) Is there a way to get the system to recognize the first partition
of the SCSI as DH0 instead of DH2? (Specify Unit 1 instead of
Unit 3?)
3) While running the system with the SCSI, the 2090A "Hard Drive" LED
stayed on continuously (though the LED on the SCSI seemed to work
fine). I didn't change the LED connection to the 2090A. Is there a
way to get the "Hard Drive" LED to work properly with the SCSI?
Looking at the controller I can see another pair of pins directly
behind the the 2 pins that the LED connector is plugged into.
There is no labeling on the 2090A to indicate what these are for,
and I didn't get any additional documentation on the controller.
Could this be an alternate connection for the LED, or are they
jumper pins for something else?
Thanks in advance - Mike
| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5175.1 | Some answers... | FROCKY::BALZER | Christian Balzer DTN:785-1029 | Wed Nov 06 1991 04:05 | 28 |
| Re: .0
> 1) What is the significance in using RES2: (as opposed to RES0:which
> seemed to work) in the mountlist prior to Prep?
>
To keep you from getting confused. I have two ST-506 drives and a SCSI drive on
my A2090. BTW, there's no need to get rid of your ST-506 drive...
> 2) Is there a way to get the system to recognize the first partition
> of the SCSI as DH0 instead of DH2? (Specify Unit 1 instead of
> Unit 3?)
>
NO WAY!
This is hardcoded in the driver. The Unit directly relates to respective drive
so the only way to get to your SCSI drive is to use Unit 3.
But booting from DH2: should be just fine (and will teach to use things like
"SYS:" instead of "DH0:" in the future... ;-).
> 3) While running the system with the SCSI, the 2090A "Hard Drive" LED
> stayed on continuously (though the LED on the SCSI seemed to work
> fine). I didn't change the LED connection to the 2090A.
>
This is wierd. No good idea here...
Cheers,
<CB>
|
| 5175.2 | some thanks... | ALLVAX::TERELLA | !Mike Terella DTN 287-3083 CTC2-1/C14 | Wed Nov 06 1991 08:50 | 21 |
|
re .1
>>BTW, there's no need to get rid of your ST-506 drive...
Thanks for the reply <CB>. I realize I can keep the ST506, I'm just
not sure I want to! I have the 42Mb Rodine, and it's almost as noisy
as the fan on my 2000...(so maybe, if I use just the SCSI, and sell
the ST506, I'll be able to afford the 2.04 upgrade?)
>>This is hardcoded in the driver. The Unit directly relates to respective drive
>>so the only way to get to your SCSI drive is to use Unit 3.
>>But booting from DH2: should be just fine (and will teach to use things like
>>"SYS:" instead of "DH0:" in the future... ;-).
I've got nothing against logicals. I was just looking for a way to
prevent the need for going through all my command files/key assignments/
menu assignments etc. and changing DH0: to DH2: (or BOOT:)
|
| 5175.3 | An itzybitzy more tips | FRAMBO::BALZER | Christian Balzer DTN:785-1029 | Wed Nov 06 1991 11:38 | 24 |
| Re .2
> Thanks for the reply <CB>. I realize I can keep the ST506, I'm just
> not sure I want to! I have the 42Mb Rodine, and it's almost as noisy
> as the fan on my 2000...(so maybe, if I use just the SCSI, and sell
> the ST506, I'll be able to afford the 2.04 upgrade?)
>
Could you speak up a little? Them drives here are a tad noisy! ;-) ;-)
>>This is hardcoded in the driver. The Unit directly relates to respective drive
>>so the only way to get to your SCSI drive is to use Unit 3.
>>But booting from DH2: should be just fine (and will teach to use things like
>>"SYS:" instead of "DH0:" in the future... ;-).
> I've got nothing against logicals. I was just looking for a way to
> prevent the need for going through all my command files/key assignments/
> menu assignments etc. and changing DH0: to DH2: (or BOOT:)
Well, if you got nuttin against them, why don't you use them? :-) ;-)
A simple trick would be an "assign DH0: DH2:", though...
Cheers,
<CB>
|