Creative COW SIGN IN :: SPONSORS :: ABOUT US :: CONTACT US
FORUMS: listlist (w/ descriptions)archivetagssearchhall of fame

Problem with Leopard and P2 Cards

Cow Forums : Panasonic HVX - HPX (P2)
Problem with Leopard and P2 Cards
by Marcus van Bavel on Dec 5, 2007 at 6:30:03 pm

When you mount a P2 Card in Leopard (OS 10.5.1), using either the HVX200, or the Dual System Adaptor, or a P2 Drive, the CONTENTS folder and all the subfolders have file locks on them.

So you cannot write a new clip or modify the metadata.

Trying to remove the lock with Finder (command-I and uncheck the lock) does not work. Anyone have any luck removing these locks in Leopard?




Respond to this post     Return to posts index

Re: Problem with Leopard and P2 Cards
by Fred Connors Jr on Dec 6, 2007 at 2:04:04 pm

Marcus

Just a silly question.

Is the card in write protect?

Fred

The Troupe - Modern Media Design & Production

Respond to this post     Return to posts index

Re: Problem with Leopard and P2 Cards
by Arthur Aldrich on Dec 7, 2007 at 2:23:44 am

I have experienced this myself, and have heard from others with the same problem.

Obviously, Apple has changed something in Leopard.

-
Art Aldrich

Leader, NJ FCP UG

www.njfcpug.org

Respond to this post     Return to posts index


Re: Problem with Leopard and P2 Cards
by Marcus van Bavel on Dec 7, 2007 at 3:49:03 pm


[Arthur Aldrich] "Obviously, Apple has changed something in Leopard."

Yep

I'm discussing it now with Apple developer support. I'll post an update here when they have something constructive to say about it.







Respond to this post     Return to posts index

Re: Problem with Leopard and P2 Cards
by Marcus van Bavel on Dec 11, 2007 at 1:32:35 am

[Marcus van Bavel] "I'm discussing it now with Apple developer support. I'll post an update here when they have something constructive to say about it."

They've declared it an official bug and will be sending me progress reports. It affects all FAT-16 volumes apparently (a P2 Card is a FAT-16 volume).

Their only suggested workaround was put it on a Windows machine and turn off the Read-Only flags. Since that's not really practical I guess we just have to wait for the fix.






Respond to this post     Return to posts index

<< PREVIOUS THREAD   •   VIEW ALL THREADS   •   PRINT   •   NEXT THREAD >>


FORUMSTUTORIALSMAGAZINEDVDsBOOKSPODCASTSEVENTSSERVICESNEWSLETTERNEWSBLOGS

© CreativeCOW.net All rights are reserved.

[Top]