#ffs hd proceedure???
2 messages in this thread
Jer,
If you want the hd auto-mounted by the BindDrivers command, (so you
don't have to do give an explicit mount command for it) it must be mounted and
preped as RES2: For example, I have NO mountlist entry for dh0:, I only have
an entry for the 2nd partition on that drive.
The way I'm set up, DH0: is only 1 cylinder long. That's 34K and I
keep just a couple of files there…like the FFS driver file and a short script
file. The other 600 some odd cylinders are the second partition on the drive
and are formatted as an FFS filesystem.
That gets me off the floppy very quick. I do a binddrivers, I move to
dh0: and do the mount of the 2nd partition by using the files on that small
partition and then move to the 2nd partition for the rest of the startup.
Your method works, but you have to do an explicit mount for your drive
after the binddrivers…thus incuring additional access of your floppy files to
mount the drive. They bonus you get is 3 additional cylinders for your use
(the 2 cylinders that PREP takes and the 1 cylinder automounted partition).
Don,
I found out that it automatically mounts dh2: without RES2:. So there's
got to be some reason for RES2: !
I just have Dh2: in my mountlist and ffs the whole thing!!!! I haven't
run into any problems yet but I want to know if I will.
Someone said that RES0: is there to help a Non-SSCI drive with errors or
something and that the RES2: isn't really needed because a SSCI takes care of
itself….
As I don't really know what anyone is talking about, I can sound REALLY
intellegent…..;+)!
Jer