#2.1FileSys
17 messages in this thread
The rigid disk block (RDB) is a standard that CBM came up with for partitioning
the disk and storing the file system on. Befire RDB you couldn't boot a
partition unless it used a file system that was in kickstart. The all happened
at the time of OS1.3. With OS1.3 the only file system you could boot from was
DOS\0 or OFS. CBM also came up with FFS (DOS\1), the problem was this wasn't in
ROM so they had to get something sorted out. They came up with RDB and everyone
was happy. Therefore if you had your hard drive set up with FFS when you were
running KS1.3 then the odds are that you have RDB. However (there is always a
however) some hard drive controller manufacturers didn't follow RDB standard to
the letter and some came up with there own thing before CBM. I use an ICD
Trifecta controller on my a500. That was formatted under KS1.3 using the 1.3
fast file system. The reason for doing it this way is if you format your hard
drive under 2.04 using the FFS in ROM then it won't put the file system
in the RDB area and therefore you wouldn't be able to boot under KS1.3. So why
you would need to put the 2.04 file system on there is beyond me. Especially as
the file system is only used if there isn't a copy of it in ROM. Someone will
say this is incorrect. But I have never upgraded the file system on my hard
drive and have use 1.3,2.04,2.05,3.0 & 3.1 successfully and without problems.
If you want to check what version of the file system you have in memory (this
is what counts I believe) then type version dh0: Or whatever your device name
is of course. For KS2.04 you should get something like filesystem V37.1 (I
can't give you the precise response as I am on a portable at work after the
power went down and my amiga is at home). After all this rambling, if you
wanted to put a different file system on your hard drive then you need
something like hdprep. This software and others like it allows you to partion,
format and normally install a file system. The software I used came from ICD
but I ran that last about 2 years ago, so can't remember too much about it. If
you want to install a different type of file system FFS instead of OFS then you
will of course have to back up your drive and format it. You should run with
FFS really, there was a supposedly better file system called PFS but that only
supported 31mb partitions (not very useful). If you are running with OFS then
move over to FFS quickly (run don't walk). Typing "info" should tell you what
file system the disk has on it. Hope some of that helps. Not in to good shape
mentally at the moment as I need more sleep. Minds going see you.
Phill.
Phil;
RDPrep (that is C= RDPrep anyway) was a 1.3 program but should not be used with
later versions of the OS (not really sure it would even work anyway).
I do not believe that RDPrep actually created what is called an RDB though it
did write a file system to the disk. The boot actually occurred to an OFS
partition and then transfered to an FFS partition.
You are quite correct that many manufactures did not comply with the RDB spec.
Of course in several cases that was just due to the fact that such manufactures
produced a hard disk/controller combination prior to the existance of a spec.
Others definately 'switched' over once C= defined what was wanted. Microbotics
and GVP are two good examples. In their cases, their disk preparation software
will even work on C= supplied controllers (sometimes requiring a tooltype
entry).
You are correct in stating that the version <device> gives you the actual
driver code version being used. What happens with the filesystem in the RDB is
that IF it is not custom then the latest version found is used. Thus, if the
ROM version is newer than what is in the RDB then the ROM version is used.
Conversely, if the RDB version is newer, then it is read from the RDB and used
in place of the ROM version. If the filesystem is custom then it is used
unconditionally from the RDB.
BTW, it really helps to read your messages if you will break up the text with
an occassional blank line.
-bill
Bill –
I believe that the Microbotics' (copyrighted but freeware) RDPrep is still
current. As far as I know, latest RDPrep is v3.91 and latest RDPrepX (the low
level executable for RDPrep) is at v2.96 (just released).
However, IMHO, Joanne Dow (jdow@bix.com – perhaps CIS too) would be the
best source of authoritative (and reliable) info on this.
——
Correct, I have known Joanne for a long time.
-bill
Bob,
Sorry to bud in, i'm new here. How can I get in touch with microbotics? I
called the tel that is on the directions, but that's not a working number
anymore. i would appreciate any help.
thanks george
George –
> I called the tel that is on the directions, . . .
Do you mean the one in the circa 1992/93 Read.First file?
> MicroBotics, Inc.
> 1251 American Parkway
> Richardson, Texas 75081
> United States of America
>
> VOICE : (214) 437-5330
Sorry, but that's the only one I have. But, if you have questions about
RDPrep/RDPrepx, hard disks, rigid disk blocks, etc. there is (IMHO) no one more
knowledgeable than Joanne Dow (who is maintaining RDPrepx). You might try
contacting her by EMail:
> INTERNET:jdow@bix.com
BTW does '[NJ]' mean New Jersey? Just wondered because I spent some
interesting years of my life (1961-1982) on the 'Joisey Showah' — well
Monmouth County (mostly) East of the GS Pkwy that is 🙂 — before returning to
the plains.
——
Bob, Thanks for the info. Yes, the number for microbotics that i was reffering
to is 214 437-5330 which is no longer in service. Sounds like i do need to get
in touch with Joanne Dow, but i am not on internet. Could you please therefore
find out for me how i can get in contact with her either voice or fax. I do
need some help desperatly, my amiga is very ill.<G> I would appreciate it. Or
she could call or fax me:
Delfin Underwater Productions Inc. Tel: 201 487-4328 Fax: 201 487-6327 thanks
BTW, yep it is New Jersey, I live north of 'Joisey Showah' <G> george
George –
You can send internet messages on CIS just go mail and check the help. The
address I gave is (I'm pretty sure) the one you would use at the 'To:' prompt
(i.e. you precede the internet address 'jdow@bix.com' with 'INTERNET:'). Of
course there is a cost to send and receive internet messages — but what
doesn't on CI$ including these forums? 🙂
Red Bank was my 'adopted' home town but I actually lived more years in
Eatontown (and worked at Fort Monmouth).
——
Bob, Thanks, yes I did find out about sending internet e-mail a bit later. Did
send it and got a message back.
george
> Did send it and got a message back.
Great, hope you will be able to get your HW probs resolved.
Bob
——
>>Great, hope you will be able to get yoyr HW probs resolved <<
Well, not really. As i'm finding out, i'm stuck with the 8 meg on the gvp
accelerator and two on the megamem. I'm witing now for updated software from
dataflier to format my drives so that gigamem can read the mask, or something
like that. Let's see if that helps me.
george
George,
The latest number I have for the company that took over support for microBotics
is (214) 644-0003. This worked for me right after I bought the MBX 1200z. They
sent out a replacement software disk with their memory test program on it.
Hope this helps,
Rob Hays
Microbotics was also heavily involved in coming up with the RDB spec, btw.
andy
Helps explain their excellent compliance (plus JDOW of course).
-bill
I am sorry about the lack of formatting.
But I was really tired and using a portable in the dark (we had a power cut).
So I couldn't even edit anything because I was using the online editor.
I am using the online editor now.
But I am making a special effort to space the text out more :-).
The prep software that came with my ICD trifecta was for 1.3 & 2.04 and would
put the fast file system on the RDB if you needed to boot up in 1.3. I assumed
that all other RDB utilities would work the same way. I may be wrong sometimes
:-(.
Phill
Phillip;
>tired in the dark
Yea, we ALL have experience with those sorts of times.
>put the fastfilesystem on the drive if you needed to boot up in 1.3.
That could well be a disaster. You really should never attempt to access an HD
with a filesystem of an older version than was used to 'create' the disk (or
even write to the disk). To some extent, you will probably 'get away with it'
but if you try using the 1.3 stuff to access a version 38 or later drive the
sparks will fly.
The reason that the filesystem SHOULD be in the RDB is that the boot code
checks the RDB filesystem version and the ROM filesystem version and then uses
whichever is newer.
If you don't put a filesystem in the RDB, you may of course still be fine —
until you do something like move the drive to an older machine.
-bill
> If you don't put a filesystem in the RDB, you may of course still be > file
— until you do something like move the drive to an older machine.
I think that is what I was trying to say (maybe).
phill