Prev: Odd Mail problem
Next: How much disk space to upgrade Tiger to Leopard?
From: Michael H. Phillips on 2 Jun 2010 04:56
After a series of crashes (Time Machine and Hard Drive spin-down trouble,
mentioned in another thread), some files have changed their 'Kind'. E.g.
Hogwasher documents have changed from 'Hogwasher.app Document' to 'Unix
Executable File'. This is causing Hogwasher to be wildly unstable.

I've run Disk Warrior and TechTool to no avail. Getting info on a corrupt
file and a new file generated by Hogwasher shows no difference except in file
Kind.

Anyone know how I can correct the file Kind?

--
Michael

mhphillips at gmail dot com

From: Phil Taylor on 2 Jun 2010 05:38
In article <hu56bv$p7j$1(a)news.eternal-september.org>, Michael H.
Phillips <mhp(a)odtaa.invalid> wrote:

> After a series of crashes (Time Machine and Hard Drive spin-down trouble,
> mentioned in another thread), some files have changed their 'Kind'. E.g.
> Hogwasher documents have changed from 'Hogwasher.app Document' to 'Unix
> Executable File'. This is causing Hogwasher to be wildly unstable.
>
> I've run Disk Warrior and TechTool to no avail. Getting info on a corrupt
> file and a new file generated by Hogwasher shows no difference except in file
> Kind.
>
> Anyone know how I can correct the file Kind?

Just guessing here, but if Hogwasher is a Carbon app it may depend on
having the filetype and creator OSTypes set on its files to work
correctly. The modern OS considers these obsolete and ignores them in
favour of file extensions to determine the file kind. I don't know of
any way you can fix this under OS X - you would have to copy the files
over to a system running OS 9 (or Classic) and use one of the old
utilities e.g. ResEdit or FileTyper to fix it.

Phil Taylor
From: Chris Ridd on 2 Jun 2010 06:10
On 2010-06-02 10:38:08 +0100, Phil Taylor said:

> In article <hu56bv$p7j$1(a)news.eternal-september.org>, Michael H.
> Phillips <mhp(a)odtaa.invalid> wrote:
>
>> After a series of crashes (Time Machine and Hard Drive spin-down trouble,
>> mentioned in another thread), some files have changed their 'Kind'. E.g.
>> Hogwasher documents have changed from 'Hogwasher.app Document' to 'Unix
>> Executable File'. This is causing Hogwasher to be wildly unstable.
>>
>> I've run Disk Warrior and TechTool to no avail. Getting info on a corrupt
>> file and a new file generated by Hogwasher shows no difference except in file
>> Kind.
>>
>> Anyone know how I can correct the file Kind?
>
> Just guessing here, but if Hogwasher is a Carbon app it may depend on
> having the filetype and creator OSTypes set on its files to work
> correctly. The modern OS considers these obsolete and ignores them in
> favour of file extensions to determine the file kind. I don't know of
> any way you can fix this under OS X - you would have to copy the files
> over to a system running OS 9 (or Classic) and use one of the old
> utilities e.g. ResEdit or FileTyper to fix it.

Mac creator codes and file types can still be set in Snow Leopard;
Xcode comes with a command-line tool called SetFile which does this and
I'm sure there are free GUI utilities which will do the same.

--
Chris

From: TOG on 2 Jun 2010 06:11
On 2 June, 09:56, Michael H. Phillips <m...(a)odtaa.invalid> wrote:
> After a series of crashes (Time Machine and Hard Drive spin-down trouble,
> mentioned in another thread), some files have changed their 'Kind'. E.g.
> Hogwasher documents have changed from 'Hogwasher.app Document' to 'Unix
> Executable File'. This is causing Hogwasher to be wildly unstable.
>
> I've run Disk Warrior and TechTool to no avail. Getting info on a corrupt
> file and a new file generated by Hogwasher shows no difference except in file
> Kind.
>
> Anyone know how I can correct the file Kind?
>
Had precisely this problem at work recently, after a switch to a new
server. Simply changing the file suffixes (to .doc, .xls, .qxd, .pdf
etc etc) cured it, although it was a monumental PITA to rename each
file individually.
From: Michael H. Phillips on 2 Jun 2010 07:03
On Wed, 2 Jun 2010 10:38:08 +0100, Phil Taylor wrote:

> Just guessing here, but if Hogwasher is a Carbon app it may depend on
> having the filetype and creator OSTypes set on its files to work
> correctly. The modern OS considers these obsolete and ignores them in
> favour of file extensions to determine the file kind. I don't know of
> any way you can fix this under OS X - you would have to copy the files
> over to a system running OS 9 (or Classic) and use one of the old
> utilities e.g. ResEdit or FileTyper to fix it.

I checked the Type and Creator Codes with FileType and they are the same on a
corrupt file and a freshly generated file.

Neither file has a file extension.

--
Michael

mhphillips at gmail dot com

 |  Next  |  Last
Pages: 1 2
Prev: Odd Mail problem
Next: How much disk space to upgrade Tiger to Leopard?