Exclusive LG phones only from AT&T
November 22, 2006 10:30 AM PST
Apple confirms iSight-Classic conflict
We previously reported on an issue where iSight problems are caused by the Classic environment being active -- perhaps with some Classic application or component attempting to gain control of the iSight, preventing other applications from using it.
Apple has now confirmed this article in a cryptic Knowledge Base article that states:
"If the Classic environment is running and you attempt to video chat with iChat or use iSight in PhotoBooth, an alert message may appear that the iSight camera is in use by another application."
Apple's listed solution is to restart the computer.
Feedback? Late-breakers@macfixit.com.
Resources
I had the same problem but I did away with OS 9 stuff. My problem was having too many drivers for my USB Logitech Quickcam 4000. I had Macam, IOXperts, and the factory driver. I delete all and their associate files using spotlight & fastfind and just reinstalled the IOXperts. Now I not only cured the busy cam thingy, my cam works much better and clearer.
I know the old saying that whatever it is _you_ are running is mission critical, but seriously folks, let's get with the times and not complain about reliability in an operating system that was discontinued 5 years ago. You all are starting to sound like Windows users with their complaints about lack of "backward compatibility."
Things change, paradigms shift, companies move on. Classic is DEAD!
Well, for people who fully use Exchange, Entourage is no match for Outlook 2001. This is my major problem. Entourage needs to continuously re sync itself via IMAP and if your users have 1gb mailboxes and use public folders and calendars, this isn't practical. Trust me, I would be the happiest person in the world if I could stop supporting classic mode.
About the iSight conflict with PhotoBooth I have this very unusual problem with PhotoBooth hanging after a being open for several days as an test for some MacBook Pro 10.4.8 sleeping issue. When it PhotoBooth "crashes" I try to force quit the application will "disappear" from process table but I cannot relaunch it and the "marker" that the application is running in the dock shows it as running even though it is gone from the process table. I looked at the command line and attempted to to kill it it doesn't die. Sudo kill -9 doesn't die so something is seriously wrong. Any of you experience this?
True, that most mission critical applications have been migrated to OS 10* but there are a few classic applications have we have really no choice because either the original developer has merged out of existence, not supported any more or not in business no more. This happened when Apple announced that in 2004 that all machines built will not boot OS 9 and some companies bought hundreds of the older machines since even then some applications like Quark wasn't migrated to 10 yet.
- by TobiMcMini November 23, 2006 2:10 PM PST
- The same problem with my Canopus ADVC 55 Digital Video device ... but i'm on a Intel-Mac with OSX 10.4.8, Classic doesn't matter.
- Like this Reply to this comment
-
(6 Comments)Re-installed the latest combo-updater, the alert message still says "The DV device is in use by another apllication".
The same happens if i connect my DV-camera ... maybe this affects all FireWire video devices?
How can i downgrade to the original EFI ???? The Restore-Image doesn't work because the update was well done.