View Full Version : P2 cards in PBG4, mounting issues
05-06-2006, 05:35 PM
i'm using a powerbook G4 to import P2 cards into FCP 5.1. i've got the panasonic P2 driver software installed, and generally the cards mount and import fine. but at least once or twice per shoot, a P2 card will not mount, it won't show up on the desktop. i eject, re-insert, still nothing. then the computer won't recoginize any other P2 cards i insert. so then i have to restart the computer, and it recognizes cards again. for a while.
it's just getting to be a hassle having to keep restarting the computer on location... has this happened to anyone else out there?
Hey plexi (Gary),
Do you mind telling me where you got the P2 driver software from? I would appreciate it.
05-07-2006, 05:53 AM
here you go:
05-07-2006, 08:28 AM
Yes, it happens to me all the time. I end up rebooting at least once or twice during a shoot on location. It is a hassle.
05-07-2006, 11:08 AM
Ditto. I get about 6 to 10 card reads before i have to restart.
05-07-2006, 11:24 AM
From my investigation it's a problem with the Panasonic driver.
The card is recocnized by the computer (you get the eject icon in the Menubar) but it will not mount.
I always get it after my powerbook wakes up from sleep, so it might be that the driver is not capable managing sleep properly.
thanks for the link.
05-13-2006, 12:31 AM
Lemme relay this fun little Powerbook story:
A while back (nearly a year or so) I had installed OS 9 Classic onto my PB (had Tiger at the time). However, no matter WHAT I did, Classic would never fully load up, and the bar would just stop (not freeze, just stop) midway. My computer still ran, I could close and open classic, but still, no luck.
Took it to a local Apple store, had a "Mac Genius" take a look at it. After 30 min., we finally found the problem: I had also installed Divx on my computer, and one of the files created by Divx in one of the library folders needed to have a space put in it. No joke. A file was changed from something like "Divxmac" to "Divx mac"(don't remember the exact name, just using as an example). Suddenly, Classic worked PERFECTLY, no reinstall needed or anything.
Moral of the story: sometimes the most major problems can be caused by the most unrelated, stupidest stuff, and if that's the case, you might NEVER be able to find a solution on your own.
I AM concerned why there isn't an Apple support listing for P2 errors though. Between this and the crashing people are discussing in another thread, I'd say Apple either needs to get on the ball, or more people need to just take the time to contact Apple with their P2 problems instead of searching the net and giving up if they find no quick solution.