macintosh@felix.UUCP (03/13/87)
[DeskCheck.Txt]
Attached is DeskCheck.Txt, which presents additional explanations of the
alerts given by DeskCheck.
---
This draft written February 4, 1987.
E.Vishniac / P.O. Box 1357 / East Arlington, MA 02174
Following are the alerts from DeskCheck, listed by ALRT number with a short
explanation of each one's significance. ^0, ^1, ^2, and ^3 indicate text which
is supplied at run-time.
128: "Welcome to DeskCheck!"
This alert is normal.
129: "All done."
This alert is normal.
130: "SetVol Failed! Error code = ^0."
DeskCheck was unable to move to some directory in the course of its search.
This should never happen.
131: "OpenResFile failed! Error code = ^0."
DeskCheck attempts to check every file that has a resource fork. Some files
have bogus resource forks, which cause errors when an attempt is made to open
them as resource files. In extreme cases, the Mac may bomb in OpenResFile.
132: "This file has one or more BNDLs, but the bundle bit is not set.
Number of BNDL resources = ^0."
In the case of the Desktop file, this is normal. For any other file, it
warns that the Finder won't take any notice of the file's bundle because
the bundle bit is off.
133: "BNDL ^0 has ^1 resource types instead of the expected 2."
BNDL resources normally have two lists of resources: one for ICN# resources
and one for FREF resources. A different number of lists is unusual, but not
necessarily an error.
134: "The signature resource listed in BNDL ^0, ^1 ^2, is missing."
An application's "signature" is the unique identifier which connects it with
the documents it creates or uses. The signature resource is a resource whose
resource type is the same as the creator of files associated with the
application. The signature is listed in the application's bundle.
135: "BNDL ^0 refers to resource type '^1'. The usual types are 'FREF' and
'ICN#'."
Types other than ICN# and FREF in the bundle are unusual, but not necessarily
an error.
136: "BNDL ^0 is too short!"
DeskCheck parses each bundle to be sure that the actual resource length is
long enough to contain the bundle's required fields and lists. A bundle
resource that's too short is a severe error.
137: "BNDL ^0 is longer than expected."
DeskCheck parses each bundle to be sure that the actual resource length is
no longer than required to contain the bundle's required fields and lists.
A bundle that's too long is unusual, but not necessarily a problem.
138: "ICN# ^2 is ^3 bytes instead of the usual 256."
ICN# resources have a fixed format, with a length of exactly 256 bytes.
A different length is a minor error.
139: "FREF ^2 is only ^3 bytes, which is less than the minimum FREF size of six."
An FREF consists of a required signature (four bytes) and ICN# local ID (two
bytes), optionally followed by a string (zero to 256 bytes). So, an FREF
could reasonably be any size from six to 256 bytes. An FREF of less than
six bytes is a severe error.
140: "FREF ^2 is ^3 bytes long, which exceeds the maximum FREF size of 262."
An FREF which runs past the maximum length of 262 bytes is unusual, but not
necessarily a problem.
141: "BNDL ^0 refers to resource ^1 ^2, which is missing."
DeskCheck verifies that all resources listed in the bundle are actually present
in the same file. A missing resource is a severe error.
142: "Check contents of volume "^0"?"
This inquiry is normal.
143: "BNDL ^0 does not contain the usual list of ICN# resources."
This is not necessarily a problem, but means the bundle isn't much good.
144: "BNDL ^0 does not contain the usual list of FREF resources."
This is not necessarily a problem, but means the bundle isn't much good.
145: "BNDL ^0 refers to FREF ^1, whose icon local ID is ^2.
This local ID is unresolved. That is, it is not the local ID of any
member of the ICN# resource list in the same bundle."
Each FREF associates a file type with an ICN# resource. The ICN# is identified
by a local ID, which is mapped to the ICN#'s real ID through the ICN# list in
the bundle itself. An unresolved local ID is a severe error.
146: "This file's bundle doesn't assign an icon to this file.
There's no FREF with a file type that matches this file's type, which
is '^0'."
In the case of the Desktop file, this alert is normal. For any other file, it
suggests that the bundle isn't complete. This is not necessarily a problem, but
means that the file will appear with a default icon on the desktop.
147: "This file's bundle doesn't appear to be for this file.
The OwnerName in the bundle doesn't match the file's creator, which is
'^0'."
In the case of the Desktop file, this alert is normal. For any other file, it
warns that the file's bundle doesn't match information about the file itself.
---