Fix Mac eof
a link
End of File Errors happen in pretty well every OS I’ve used (Wintel, UNIX,
Mac, Atari and Commodore AMiga)… from time to time. What happens is that
the file mapping file gets screwed (by a few bad bits, or an interrupted
save or whatever) and this then sets attributes for that file which can be
way outta whack. For example if could tell the OS that the file is 2000
terabytes long, and contained in sectors that don’t exist on the volume in
question.
When the time comes to access the file … the OS takes this screwed up
info and compares it to the volume characteristics it has on file and, in
the MacOS and Wintel case (no version fo UNIX I’ve used treats this as a
fatal error) … crashes big-time because the conflict can’t be resolved.
Solution … do regular file integrity checks using Nortons, TechTool,
Apple’s Disk First Aid etc … and watch what they tell you. If they tell
you a file is corrupted by a bad EOF don’t boot it. Try to repair it, and
if that’s not successful trash the puppy. Everyone does back-ups of
crucial data files, so it should simply be a matter of copying it back
onto the machine from your backup.
Often on the Mac these file related errors happen in Preference or app
associated files that are loaded when the app loads … which can be a
bummer. But regular file integrity checks tend to nail the suckers as they
appear.
If the file being corrupted is always the same, or if the files concerned
are being corrupted under the same sets of circumstances then you may have
either an extension conflict or a ‘bad’ appplication. Also, check that
you’ve installed all the OS and app bug-fixes from Apple and the
application suppliers)
無迴響
Comments RSS
TrackBack Identifier URI
No comments. Be the first.
Leave a comment
