#2.1FileSys
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