Here's the problem: I have a bunch of MPEG-4 files supplied by a client using the Sanyo Xacti HD1000 digital camcorder. They use a specific flavour of H.264 compression using AVCHD which Quicktime broke from v7.2 onwards. The results of my web research indicate that in order for me to open the files, I need to replace my QT 7.2 version of the H.264 codec with the QT 7.16 version.

So I've downloaded the older dmg file with 7.16. I've shown the package contents and need to open the Archive file in the package (apparently) so I can pull just the "QuickTimeH264.component" from it.

There's two files called "Archive" : there's "Archive.bom" and "Archive.pax.gz". I can't for the life of me figure out how to get the file I need. I've used Stuffit and BOMArchiveHelper, and have extracted a file called "Archive.pax" but that's as far as I can get.

Any help? Please?

<<bump>>

Not sure if this will do it, but who knows..

ditto -x --bom Archive.bom ~/someDirectory

Also it appears the Archive.bom might not contain the files, as I think it's only a list of files/paths, but I guess we will find out.

EDIT: and to extract the Archive.pax.gz this might be useful here.

Purana,

Thanks for that. I'm not a hard-core user so it took me a while to work out what I was meant to do with all the terminal commands to get it to work in my case.

So now I've extracted the "QuickTimeH264.component" folder and want to replace the newer version in System/Library/QuickTime but apparently I don't have privileges to replace it. I'm logged in as administrator but even changing the permissions for the folder doesn't seem to help.

Any further ideas?

Thanks.

Nevermind. I figured out a work-around. I deleted the old (newer version) folder (after making a copy of it first) and then copied in the new (older version) folder.

Hopefully this will work.

Cheers.

It may be because you are not a 'superuser', Although you are an administrator you still can't do 'everything'. The superuser is not enabled by default.

More info:

http://en.wikipedia.org/wiki/Superus..._and_Unix-like

If you are using the terminal you can overcome this by typing 'sudo' before the command otherwise you should enable the super user (see google), log in a root and try again .

edit: I'm to slow to type :P