Download SanityCheck - e-Node

Reported Items
208 Resource bundle '<1>' is too big for SanityCheck to manage.
Detailed Description: SanityCheck has an internal limit of 1024 entries in the
bundle resources. Most likely, this reflects damage in the bundle resource.
Actions: Try re-installing the plug-in / external. If this item still occurs, contact the
external vendor to determine if this is a problem with their external or if SanityCheck needs to be revved to handle larger bundle sizes. Contact Committed
Software if the latter is true.
209 Resource '<1>' has duplicate ID.
Detailed Description: There are two resources with the same resource ID.
Actions: Use Mac resource editing tool to fix this problem.
210 4DX Folder ('<1>') contains a Folder ('<2>').
Detailed Description: This item is only reported on the Macintosh, and is merely
intended to help you clean up your Mac4DX Folder.
Actions: Nothing, this is for your information only.
211 4DX File '<1>' is of wrong type ('<2>').
Detailed Description: Mac Version Only: The 4DX file is verified to be of the
proper external type. On the PC, this is impossible to do.
Actions: Try re-installing the external. If you still get this item, ask the plugin vendor if this is normal behaviour. If it is, perhaps turn off this item.
212 '§' reference used on line <1>.
Detailed Description: This token is not encouraged by ACI for variable dereferencing.
Actions: Rewrite the line to remove this token.
213 <1> object has an off-screen window.
Detailed Description: The given object's window is off screen.
Actions: You may fix this from the Browser - open the object and change the rectangle to be on-screen.
214 The general info area (PR4D) has a bad tag header (it isn't 'PR4D').
Detailed Description: The header for the general information area is incorrect.
Actions: This may indicate serious damage in your structure file. You may most
likely need to recover from backup.
215 User name is too long (user: <1>, len: <2>, maxlen: <3>)
Detailed Description: The user name claims to be larger than is possible. This
most likely indicates damage in the password area of your structure file, and
should be addressed immediately.
Actions: Try re-entering the user name in the password editor. If this fails,
recover from backup.
216 Method/Proc name is too long (user: <1>, len: <2>, maxlen: <3>)
Detailed Description: The method/proc name that is to be used as a startup procedure is too long, and indicates damage in your password area.
Actions: Try re-entering the method/procedure name. If this fails, recover from
88