Path: utzoo!attcan!uunet!oddjob!ncar!ames!elroy!cit-vax!ucla-cs!sdcrdcf!ism780c!tim
From: tim@ism780c.isc.com (T.W."Tim" Smith, Knowledgian)
Newsgroups: comp.sys.mac
Subject: Re: System 6.0 clash with Micah AT100 hard disk?
Message-ID: <11535@ism780c.isc.com>
Date: 2 Jul 88 22:44:38 GMT
References: <6218@coherent.com>
Reply-To: tim@ism780c.UUCP (T.W."Tim" Smith, Knowledgian)
Distribution: comp
Organization: Suction and Pressure Lab, California Institute of Lawsonomy
Lines: 26

In article <6218@coherent.com> dplatt@coherent.com (Dave Platt) writes:
< HYPOTHESIS: Based on these symptoms, and on the symptoms that some users
< of CMS drives have been reporting, I'm beginning to suspect that the Mac
< is now looking at some fields in the driver information, or in the disk
< partition tables, that it had not previously been examining... and that
< some vendors' drivers or formatters haven't been filling these fields in
< correctly.  Just a guess...

I doubt it.  I have a formatter that only supports the old format partition
table.  There *aren't* any fields in the old format partition table to be
filled in incorrectly.

Also, there is no need for the file system to know anything about the
partition table anyway.  That is just for the driver to use.  Initializing
a file system is a file system operation.  Everything that the file
system needs to know to initialize a disk should be obtainable from
the drive queue entry.

In other words, if a driver works well enough to boot, and be usable
when a file system is already on the drive, then the Finder should be
able to initialize the disk.  I suspect Apple has some sort of bug in
DIZero() for system 6.
-- 
Tim Smith				tim@ism780c.isc.com
"I don't practice what I preach because I'm not the
                       kind of person I'm preaching to" -- J.R. "Bob" Dobbs