| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 5334.1 | HDToolbox | ULTRA::KINDEL | Bill Kindel @ LTN1 | Wed Jan 08 1992 15:43 | 42 |
| Re .0:
> I have a question about what 2.04 does with the MountList specification
> for the hard drives. I have looked at my mountlist and can not
> find any reference to the hard drives in the system.
Autobooting controllers that support Commodore's Rigid Disk Block
format don't need mountlist entries for the drives/partitions thus
automounted. If you describe a partition as NOT automounted, you'll
need to have a descriptive entry in a file (e.g. devs:mountlist) that
can be used by the mount command.
> I have a A2000 with a 2091/52meg drive and a 2090 / ST225 20meg.
> I'm not sure what to do if I would like to change drives or add
> a second drive to the 2090. I have the 2090 install disk, but this
> talks about adding info to the mountlist. I also was going to change
> the file system on the st225/2090 by removing the L:fastfile ??
> statement but can't find where the statement is located now.
Since the Fast(er) File System is implemented in the KS 2.04 ROM, you
no longer need L:FastFileSystem when you're booted with AmigaDOS 2.04.
One of the items in the Rigid Disk Block information equates the file
system number (a hex number that decodes to 'DOS1' for FFS partitions)
with the supporting file. Prior to 2.04, this named L:FastFileSystem.
As of AmigaDOS V2.04, you can make it null, which means AmigaDOS will
use the built-in support in the KS 2.04 ROM.
> In 2.04 system, I have a program call HD????? that will set up and
> check my 2091. In the program it said to use XT mode for the A500
> harddisk. Is this the program to use for the 2090/st225 ?
2.04 comes with the HDToolbox, which is an updated version of the same
tool that is shipped with A2091 and A590 disk controllers. There's
been some discussion in this conference about how to use HDToolbox with
other controllers (and I think there was even an assertion that it works
with the A2090).
As for the XT vs SCSI selection, the stock 20MB drive in an A590 is an
XT drive, which is why the documentation reads as it does. If you have
an XT drive to describe, you should do likewise. I went the other way
when I replaced the 20MB drive with a Quantum 105S, so I described my
new drive as SCSI.
|
| 5334.2 | Answer time | FROCKY::BALZER | Christian Balzer DTN:785-1029 | Thu Jan 09 1992 03:46 | 13 |
| Re: .0
With A2090 you use Mountlist entries like with 1.3, but get rid of the
FastfileSystem entry (if you use FFS for that partition) and the GlobVec
entry.
HDToolBox is useless for the A2090, since it requires the RigidDiskBLock
standard, which this controller doesn't support.
Also don't confuse XT drives (which are IDE drives) with ST506 drives.
Cheers,
<CB>
|
| 5334.3 | Please Expand on your answer | NQOAIC::NILSEN | Bob @ 264-7017 | Thu Jan 09 1992 10:07 | 13 |
| If you just could expand your answer a little.
Do I add the harddisk info (2090 controller & st506 disks) to the
MountList or put it in a file called MountList.HD . Will the
system use MountList.HD or do I need to refer to it in some other
startup file. How do I get the system to recognize there are other
drives. ( I named them DH0: & DH1: , I have changed my Boot drive
[2091/52meg] name to HD1:) . I think in the 1.3 ver we mounted RES0:
and RES1: or something like that.
Thanks Bob
P.S. Does any one have any specs about a RODIME #R03055 Drive 3.5"
|
| 5334.4 | It's Running | NQOAIC::NILSEN | Bob @ 264-7017 | Fri Jan 10 1992 08:40 | 20 |
| Well, I got the drives up and running. Thanks for the Help.
To explain a little for others that may try this. You will need a
mount list for the extra drives. The list should contain :
RES0 ; Drive name and partitions (DH0) ; RES1: ; Drive name and par
(DH1) , just like you would need in 1.3 mountlist. In my
startup-sequence file I have the command,
mount DH0: from devs:mountlist.hd
mount DH1: from devs:mountlist.hd
The extra hard disks mountlist file is call mountlist.hd.
The system will boot from my a2991/52meg and the 2090/20meg & 42meg are
just extra devices.
As I said before, THANKS for the help, I starting the understand the
Amiga system a little better every time I do something that's not
normal.
Bob
|
| 5334.5 | Step by step... | FROCKY::BALZER | Christian Balzer DTN:785-1029 | Fri Jan 10 1992 09:10 | 74 |
| Re: .3
> If you just could expand your answer a little.
> Do I add the harddisk info (2090 controller & st506 disks) to the
> MountList or put it in a file called MountList.HD . Will the
> system use MountList.HD or do I need to refer to it in some other
> startup file. How do I get the system to recognize there are other
> drives. ( I named them DH0: & DH1: , I have changed my Boot drive
> [2091/52meg] name to HD1:) . I think in the 1.3 ver we mounted RES0:
> and RES1: or something like that.
OK, it seems that you have two ST506's hanging of your A2090. To make them
usable you need Mountlist entries for RES0: and RES1:. You mount those and
use PREP from the 2090 disk to enter some parameters. You want to make the
first partitions (DH0: and DH1: are _hardcoded_ to those and "automounting")
as small as possible, since they can only be OFS. Then use mountlist entries
like below to mount FFS partitions.
Here're my Mountlist entries for one of my RD53's:
---
/* My beloved Micropolis 1325 aka RD53 for 2.04 */
RES0: Device = hddisk.device
Unit = 1
Flags = 0
Surfaces = 8
BlocksPerTrack = 17
Reserved = 0
Interleave = 0
LowCyl = 0 ; HighCyl = 1
Buffers = 1
BufMemType = 0
#
/* FFS */
P01: Device = hddisk.device
Unit = 1
Flags = 0
Surfaces = 8
BlocksPerTrack = 17
Reserved = 2
Interleave = 0
LowCyl = 20 ; HighCyl = 521
Buffers = 10
BufMemType = 1
Mount = 1
Mask = 0x007FFFFE
DosType = 0x444F5301
StackSize = 4000
#
/* FFS */
P02: Device = hddisk.device
Unit = 1
Flags = 0
Surfaces = 8
BlocksPerTrack = 17
Reserved = 2
Interleave = 0
LowCyl = 522 ; HighCyl = 1021
Buffers = 100
BufMemType = 1
Mount = 1
Mask = 0x007FFFFE
DosType = 0x444F5301
StackSize = 4000
#
---
> P.S. Does any one have any specs about a RODIME #R03055 Drive 3.5"
Not me, sorry.
Cheers,
<CB>
|
| 5334.6 | A2090A AutoBoots the New FFS!!! | CSSE32::SMITH | Recreational Pcyclepath... | Mon Jan 20 1992 19:33 | 59 |
| re .2
>HDToolBox is useless for the A2090, since it requires the RigidDiskBLock
>standard, which this controller doesn't support.
Now I understand the A2090 doesn't support the RigidDiskBlock and
according to the "AmigaDOS V1.3 Enhancer Manual", page A1, quote...
"Since Commodore's Hard Disk/SCSI Controller (A2090A) auto-mounts the
default file system on the first partition of the hard disk, it is not
possible to use the FastFileSystem there."
But...
Whilst upgrading to 2.04 I decided to try booting the new FFS on the
A2090A's default partition and it works! Could this be because the
new FFS is now the default file system, since it's in ROM?
Here's what I did to try it.
I have a 2000 (revison 4.x) with an A2090A with 2 SCSI disks, 512K
Agnus, 4MB SupraRAM and the newly installed V2.04 ROM. After
installing 2.04 I tested without changing my disks around. Since I
had enough room on my 2nd SCSI disk I copied everything to it. This
left me with the first SCSI disk free to format. Originally it was
set up like so:
DH2: Automounted partition, cyl 2-3, not used (OFS)
HD0: MountList mounted V1.3 FFS (FFS)
Since my old ROM was V1.2 I was booting DF0 and switching to HD0. I
never used DH2: After installing the V2.0 ROM I re-formatted HD0:
using the new FFS and copyed enough stuff to DH2: to autoboot under
the OFS. This setup booted fine.
Being adventurous, I re-formatted DH2's cyl 2-3 with the new FFS and
tried the setup again and IT BOOTED FINE TOO! Being even more
adventurous I re-prep'd my disk into 2 equal partitions and formatted
both of them using the new FFS and installed AmigaDOS V2.04 on the
automounted DH2: partition and IT BOOTS FINE TOO! I'm using right now.
(appropiate L:FastFileSystem entries removed, of course). Here is how
it looks:
DH2: Auto-mounted/booted cyl 2-388 (NFFS)
HD0: MountList mounted cyl 388-774 (NFFS)
So what gives???
It appears to me that the new FFS in ROM supports automounting/booting
of the new FFS partitions from the old A2090A even with no
RigidDiskBlock support. Anyone else tried this? I searched the new
docs and they seen to expect everybody must have an A2091 or an A590.
They conviently forgot about us A2090A owners.
Cheers,
...Ed_who_is_very_happy_2.04_autoboots_his_A2090A_NFFS_partition ;')
|
| 5334.7 | So be it... | FROCKY::BALZER | Christian Balzer DTN:785-1029 | Tue Jan 21 1992 10:55 | 13 |
| Re .6
> So what gives???
Note that I only own an A2090 and not an A2090A.
And yes, I also forgot the the FFS is now ROM based and thus available at
boot time. Hell, I even use that feature at home, with the RRamdrive (on Fish
47?). I boot a plain WB and my reset-residendt FFS RAM disk is still there
and works. Now if only could get that thing to boot... ;-)
Cheers,
<CB>
|