

{"id":26,"date":"2005-07-21T10:20:45","date_gmt":"2005-07-21T09:20:45","guid":{"rendered":"http:\/\/www.fredkuo.idv.tw\/wordpress\/?p=26"},"modified":"2005-07-21T10:20:45","modified_gmt":"2005-07-21T09:20:45","slug":"fix-mac-eof","status":"publish","type":"post","link":"https:\/\/fredkuo.idv.tw\/wordpress\/?p=26","title":{"rendered":"Fix Mac eof"},"content":{"rendered":"<p>a link<\/p>\n<p>End of File Errors happen in pretty well every OS I&#8217;ve used (Wintel, UNIX,<br \/>\nMac, Atari and Commodore AMiga)&#8230; from time to time. What happens is that<br \/>\nthe file mapping file gets screwed (by a few bad bits, or an interrupted<br \/>\nsave or whatever) and this then sets attributes for that file which can be<br \/>\nway outta whack. For example if could tell the OS that the file is 2000<br \/>\nterabytes long, and contained in sectors that don&#8217;t exist on the volume in<br \/>\nquestion.<\/p>\n<p>When the time comes to access the file &#8230; the OS takes this screwed up<br \/>\ninfo and compares it to the volume characteristics it has on file and, in<br \/>\nthe MacOS and Wintel case (no version fo UNIX I&#8217;ve used treats this as a<br \/>\nfatal error) &#8230; crashes big-time because the conflict can&#8217;t be resolved.<\/p>\n<p>Solution &#8230; do regular file integrity checks using Nortons, TechTool,<br \/>\nApple&#8217;s Disk First Aid etc &#8230; and watch what they tell you. If they tell<br \/>\nyou a file is corrupted by a bad EOF don&#8217;t boot it. Try to repair it, and<br \/>\nif that&#8217;s not successful trash the puppy. Everyone does back-ups of<br \/>\ncrucial data files, so it should simply be a matter of copying it back<br \/>\nonto the machine from your backup.<\/p>\n<p>Often on the Mac these file related errors happen in Preference or app<br \/>\nassociated files that are loaded when the app loads &#8230; which can be a<br \/>\nbummer. But regular file integrity checks tend to nail the suckers as they<br \/>\nappear.<\/p>\n<p>If the file being corrupted is always the same, or if the files concerned<br \/>\nare being corrupted under the same sets of circumstances then you may have<br \/>\neither an extension conflict or a &#8216;bad&#8217; appplication. Also, check that<br \/>\nyou&#8217;ve installed all the OS and app bug-fixes from Apple and the<br \/>\napplication suppliers) <\/p>\n","protected":false},"excerpt":{"rendered":"<p>a link End of File Errors happen in pretty well every O [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-26","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/26"}],"collection":[{"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=26"}],"version-history":[{"count":0,"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=\/wp\/v2\/posts\/26\/revisions"}],"wp:attachment":[{"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=26"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=26"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/fredkuo.idv.tw\/wordpress\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=26"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}