Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!ncar!cruff
From: cruff@ncar.ucar.edu (Craig Ruff)
Newsgroups: comp.sys.mac.programmer
Subject: Re: MacCompress is eating my hard disk
Keywords: MacCompress
Message-ID: <1543@ncar.ucar.edu>
Date: 8 Mar 89 15:29:48 GMT
References: <7282@spool.cs.wisc.edu> <875@internal.Apple.COM>
Reply-To: cruff@handies.UCAR.EDU (Craig Ruff)
Organization: Scientific Computing Division/NCAR, Boulder CO
Lines: 23

In article <875@internal.Apple.COM> alan@Apple.COM (Alan Mimms) writes:
>I've found that the problem is caused by the files created by MacCompress
>having non-zero VERSION numbers.  This is a NONO according to all Macintosh
>programming documentation.  Unfortunately, since virtually nothing does
>make this mistake, there are few utilities around for killing off these
>files.

Well, according to my copy of Inside Mac, it only mentions the version
number for MFS files, not HFS files.  And all of the HFS structures don't
have any reference to this stupid version number.  You have to shove a
zero into the proper place (probably under a different name)!

* FLAME ON *

If HFS doesn't support the version numbers, why doesn't it explicitly
set them to zero for you?!?  And if they really seem to be used, why
doesn't the documentation say so?!?

* FLAME OFF *
-- 
Craig Ruff      NCAR                         INTERNET: cruff@ncar.UCAR.EDU
(303) 497-1211  P.O. Box 3000                   CSNET: cruff@ncar.CSNET
		Boulder, CO  80307               UUCP: cruff@ncar.UUCP