Intel Mac required?

Is an intel mac required to use iPhoto'08?
I understand that it is required to use iMovie'08.
Thanks.

That's interesting. My dual 1.25 G4 does just fine with iPhoto 08. In fact, I believe it is faster. I've noticed that when I edit basic things like crops and go to the next image, it doesn't wait to apply the changes to the last image. It appears they are doing more things in the background which make my dual processor better suited than the faster G5 in your iMac.
Now, if I could only get it to work with iMovie. I guess it is time for a new computer soon. I upgraded my video card when Aperture came out only to find that it would then refuse to install because I did not have a G5.

Similar Messages

  • Photoshop CS4 on Intel Mac requires Rosetta to open. Why?

    Hello,
    I fresh installed 10.6.2 after upgrading my hard drive. I fresh installed Photoshop CS4. Installed all updates. When I tried to open Photoshop CS4, I was prompted to download Rosetta. Photoshop would not start. I installed Rosetta and Photoshop still would not start. I am running a Intel Core Duo 2 MacBook Pro with all updates installed. What gives?
    Ed

    Thanks for your reply;
    I erased the hard drive and installed Photoshop from Adobe's Download site. All is well now. My personal install disk may be defective.
    Ed

  • Booting Intel Mac Mini from PPC OS

    I had a PowerPC Mac Mini that booted off of an external hard drive. I just sold the computer, and bought a new Intel-based Mac Mini. I would like to have the new Mini boot off of the external hard drive also, so I can keep all of my settings and extensions pretty much the same. Is there any way I could make this work?

    You must erase and reformat the external hard drive. So Back Up anything of importance on that drive. The PPC Mac had to have the drive formatted with Apple Partition boot drivers in order to boot the Mac after a Mac OSX Install. An Intel Mac requires that the drive be formatted with GUID Partition boot drivers. This is all covered in the Disk Utility.app in the Utilities folder.

  • Do Intel iMacs Require High-Priced UPSs?

    I'm in the market for a UPS for my new iMac. I've never used one before, but I've experienced enough power glitches to now "graduate" from my trusty old surge suppressors.
    In the past, I've leaned towards APC surge suppressors, so I decided I'd look into APC UPSs. In doing my homework, I came across a rather interesting, and potentially disturbing, thread
    (see <http://forums.macworld.com/thread/100654?start=0&tstart=0>). Essentially (if it's correct), when selecting a UPS, one can't simply go by the power ratings in the specs of our
    Macs (they end up "understating" (in effect) the size of the UPS you will need). More of a concern, however, is the possibility that the Intel Macs may be a bit "too quick" for any of the
    "standard" UPS models (i.e., those based on the lower-cost, offline-technology designs, usually employed by UPS manufacturers for the home-computer/small-office market),
    and require one of the "premium" models (i.e., those based on the higher-cost—often,
    significantly higher-cost—line-interactive or online technologies).
    Has anyone had any experience that would support or refute this?

    You all seem to be calling upon your previous experience with APC products. And while I agree that experience is a great teacher, I’m not so sure how much of the experience you are relating is really relevant (i.e., the use of APC UPSs with recent-vintage Intel Macs). Quite frankly, I’m also not sure whether enough time has elapsed for the alleged issues raised by the APC tech to actually become issues for a lot of Mac users.
    So, was the tech “full of it,” and simply trying to “sell” the APC customer—who had contacted APC for tech support regarding his 3-month old UPS—or was the tech honestly trying to help the customer? And if the latter, did he know what he was talking about?
    My own experience with APC (limited as it is) combined with what I’ve seen and heard other folks say about the company, and the company’s overall reputation in the marketplace suggest that the tech probably was not trying to get the customer to needlessly buy a more-expensive unit. That leaves us with the question: Did he know what he was talking about?
    The tech made 2 specific clams: One relating to power requirements, the other to transfer-time requirements. Everyone here seems to be focusing on power requirements, so let’s try to pass judgment on that first.
    _Power Requirements_. The tech made the following statement:
    +Apple uses Power Factor Corrected power supplies in their computers. When we+
    +size a UPS for a computer with a Power Factor Corrected power supply, we+
    +multiply the watts by 1.25. So, for the purposes of choosing a UPS for your+
    +Mac, we would use a wattage of 280W x 1.25 = 350W. This would exceed the+
    +watt capacity of the BE550R which can handle a load of 330W. I will place a+
    +link here to a document that describes Power Factor Corrected power+
    supplies.
    He then provided the following link to a document located in the APC Knowledge Base:
    <http://nam-en.apc.com/cgi-bin/namen.cfg/php/enduser/std_adp.php?p_faqid=8883&p_created=1193079387&p_sid=JU8cSF2j& p_accessibility=0&p_lva=&p_sp=cF9zcmNoPTEmcF9zb3J0X2J5PSZwX2dyaWRzb3J0PSZwX3Jvd1 9jbnQ9NCZwX3Byb2RzPTAmcF9jYXRzPSZwX3B2PSZwX2N2PSZwX3NlYXJjaF90eXBlPWFuc3dlcnMuc2 VhcmNoX25sJnBfcGFnZT0xJnBfc2VhcmNoX3RleHQ9cGZj&p_li=&ptopview=1>.
    The document certainly seems to be “authoritative” in its discussion of “power factor corrected” power supplies and the Government’s updated Energy Star requirement (Energy Star 4.0, which took effect in July 2007—see <http://www.energystar.gov/ia/partners/fed_agencies/estar40.pdf>) that such power supplies be used in computers (e.g., desktops, notebooks, workstations, game consoles, and servers). So unless the document is wrong, or unless the tech is wrong about Apple’s compliance with Energy Star 4.0, it appears that the tech’s statement regarding the BE550R’s ability to handle the potential load of the customer’s post-July 2007 24” iMac is correct.
    _Transfer-Time Requirements_. The tech claimed that Intel Macs require a transfer time of 4-5 milliseconds but that the APC Back-UPS series (which includes the BE550R) has transfer rates of 8-10 milliseconds. He indicated that this mismatch may very well have been a contributing factor to the sudden spurt of daily shutdowns that the customer had experienced. He put it this way:
    +However, there is another consideration. Macs are more sensitive to power+
    +fluctuations than comparably sized PC's are. My assumption, based on the+
    +information provided, is that the BE550R may have been having very brief+
    +transfers to battery caused by harmonic distortion in the input power. This+
    +type of distortion is common and is not normally a problem. But, when your+
    +UPS transferred to battery, one of two things probably occurred. Either the+
    +overload issue caused your Mac to shutdown or the transfer time from on-line+
    +to battery caused the Mac to shutdown. The BE550R, being a Back-UPS ES, has+
    +a transfer time of around 8 - 10 milliseconds. The BR units have a transfer+
    +time of 4 - 5 milliseconds. We have noticed that Macs need a quicker+
    +transfer time than this. For this reason, we now recommend a Smart-UPS for+
    +all Macs. Our UPS configurator is being updated to reflect this+
    +recommendation. A Smart-UPS has a transfer time of 2 - 4 milliseconds which+
    +works well with Macs. So, to make a long story short, we would recommend an+
    +SUA750 for your Mac.+
    He was clearly somewhat more tentative about this transfer-time requirement than he was about the power requirement. And I have yet to see any changes made to the APC website to reflect these new “requirements.” Nevertheless, his presentation seems “reasonable,” and certainly doesn’t come across as a “sales job.” From a user perspective, I just hope it’s a matter of a thoughtful tech pointing to a technically possible issue that may never be of real practical concern.

  • Can I use OS9 as the start up disk on my Intel Mac?

    I have a new Intel iMac. I want to partition my hard drive, install OS9 and run the old system. I know I can't use "classic" on 10.4.7 but I wonder if I could simply install OS9 and reboot my computer. I don't need to move between the two, meaning I don't need to work in OS9 then instantly click and be in 10.4.7. I can deal with the inconvenience of rebooting.
    I'm having 3 problems
    #1, I have an old version of Photoshop. I'll buy the newest Photoshop someday but the latest version wasn't made for Intel Macs and it is very expensive. $600. I wonder if it runs slow on Intel Macs. Maybe I should wait for the next version.
    #2 I have a great Epson printer (875 DC) but Epson has not updated the print drivers for this model and probably won't. OK fine I can buy a newer better photo printer $550.
    #3 I have a "Nikon Coolscan 4000" film Scanner $1,300. This scanner is great in OS9 but the thing never worked in OS10 and now that I have this Intel iMac I downloaded the latest software update and the thing still doesn’t work and if the computer sleeps while the Nikon software is open it won't wake up and I have to restart.
    To sum everything up, can I run OS9 on my Intel iMac? I don't care if I have to work in OS9 then shut down and restart to work in 10.4.7 Can this Intel iMac understand OS9. If I try to restart using OS9 as the startup disk will I damage the computer? Will I screw things up and have to spend hours and days removing files and correcting problems?
    I feel like this computer is a fresh clean new baby and I'm afraid that if I start messing around with it I'll regret it.

    Hello,
    I have a new Intel iMac. I want to partition my hard
    drive, install OS9 and run the old system. I know I
    can't use "classic" on 10.4.7 but I wonder if I could
    simply install OS9 and reboot my computer.
    The problem here, is that the OS 9 environment / Operating System will only run on a PowerPC processor.
    The only reason that OS X will run on either processor, is that it was specifically designed to do so from the beginning.
    But, OS 9 and older were specifically written for the PowerPC / Motorola processors.
    So, you will need a machine with a PowerPC processor to run OS 9.
    Currently, there is one program that will enable OS 9 to run on an Intel Mac. But, it requires making a copy of the Power Macintosh ROM. So, it's legal use is questionable at best.
    http://www.gibix.net/projects/sheepshaver/
    This program works by emulating the PowerPC processor. And, it is reported to operate at roughly 1/8-th of native speeds. So, it could be pretty slow for productive photo work.
    #1, I have an old version of Photoshop. I'll buy the
    newest Photoshop someday but the latest version
    wasn't made for Intel Macs and it is very expensive.
    $600. I wonder if it runs slow on Intel Macs. Maybe I
    should wait for the next version.
    If it is a Mac OS X version, then it will run on the Intel systems. But, yes it will be slower. Usable, but slower.
    I haven't tried this program, so I cannot personally comment on it. But, even Steve Jobs admitted it was slow on the Intel Macs.
    #2 I have a great Epson printer (875 DC) but Epson
    has not updated the print drivers for this model and
    probably won't. OK fine I can buy a newer better
    photo printer $550.
    OS X comes with drivers for the Epson Stylus Photo 875. They are provided by the Gimp-Print layer. But, installed / select just like any other printer. So, as long as you can connect the printer using USB, then you can select the driver for the 875 and be fine (as long as this is the same printer).
    Otherwise, some people have reportedly installed PowerPC print drivers without trouble. I haven't tried it myself.
    #3 I have a "Nikon Coolscan 4000" film Scanner
    $1,300. This scanner is great in OS9 but the thing
    never worked in OS10 and now that I have this Intel
    iMac I downloaded the latest software update and the
    thing still doesn’t work and if the computer sleeps
    while the Nikon software is open it won't wake up and
    I have to restart.
    Can't really help you there.
    To sum everything up, can I run OS9 on my Intel iMac?
    I don't care if I have to work in OS9 then shut down
    and restart to work in 10.4.7 Can this Intel iMac
    understand OS9. If I try to restart using OS9 as the
    startup disk will I damage the computer? Will I screw
    things up and have to spend hours and days removing
    files and correcting problems?
    As mentioned above, the only method currently available to use OS 9 on an Intel system is that SheepShaver program.
    But, I would not expect good results with it for your uses. And, it's legal status would be questionable since you need to copy a ROM file from another Mac to use it (which goes against Apple's license agreement).
    I feel like this computer is a fresh clean new baby
    and I'm afraid that if I start messing around with it
    I'll regret it.
    Just make sure you have a good backup of everything before you start experimenting.
    I hope this helps.

  • Can I use a Power PC non intel Mac Mini as an external HD with my iMac 3.06

    Can I use a Power PC non intel Mac Mini as an external HD with my iMac 3.06 Intel Core Duo
    I can't figure out how to get this to work. Is it possible?

    WildBull wrote:
    Will it work if I connect via usb instead of firewire?
    No. There is no "USB Target Disk Mode".
    Just so we're clear, when you start your Mac mini in FireWire Target Disk Mode (TDM - holding T on startup), do you see a FireWire icon on the Mac mini's display? IIRC, it's not required that the Mac mini be connected to a display for TDM, but it would help diagnose whether or not the mini is actually starting in this mode.

  • How can you FORCE Classic mode to run on an Intel Mac? OS 9 emulation Rosetta Software Design

    Hello everyone, I had a few thoughts on running Classic mode on intel macs which I wanted to share.
    Now I know little about software design, but maybe someone who does could tell me if these ideas I had are at all feasible:
    Now in the first place I now that, technically, "Classic" mode went out back with Tiger because of the switch to Intel chips. Switching to Intel, Rosetta was required to "translate" pre and non-intel OSX applications, with the exception of Classic since Rosetta does not translate deep enough into the system to do that. As a substitute to Classic, SheepShaver, Basilisk II, etc. can be used to emulate OS 9, but these are very lousy applications compared to Classic mode.
    Is there ANY way whatsoever Rosetta could be edited, or Classic itself so that it will work on intel macs?
    (that is, with the exception of 10.7+ systems since these don't even use Rosetta)
    I know if Classic was placed on an intel mac, it would tell you to download Rosetta, but from there will crashes because frameworks in the system's library does not support (or was not designed for) Classic...
    So what I wanted to know:
    What if an old, Classic supporting PowerPC system's library folder was added to an Intel computer in a location other then that computers real system folder (as not to confuse the real, current system) and Classic manually edited so that it would search for the needed frameworks/etc files in the new location? Would it work?
    Since, after all, it now has the correct "system" to run on (which before Rosetta could not convert), do you think there's any chance it would work and function properly?
    Now beyond that, I wouldn't know the actual results (or consequences). I suppose the main problem to consider would be that the the PPC's system frameworks/etc wouldn't work at all on an Intel (which leads us back to Rosetta lacking in this area), and since those frameworks will be searching for other files in the system library (which would bring them to the current, Intel system) the same results would happen: crash! Or maybe sensing the system was mixed up, one or more files would try to "fix" themselves, and in turn destroy the computer's real system.
    So, would it be worth a try?
    I'd love to hear any other thoughts on running Classic on Intel...

    There is an "easier" way to acquire SheepShaver called Chubby Bunny and I have put together a post with some safe links that are relevant to this topic.  I see that emaculation is one of them.
    Why do you need OS 9 greater than 9.04?
    Feel free to let me know if you need any more help.
    With the newer Intel Macs, you have to run a Classic emulator such as SheepShaver, which requires you to extract the Mac ROMs from your older Classic Mac and then install Mac OS 9.
    A related program is Chubby Bunny, which comes bundled with all of that included.
    More information on SheepShaver:
    http://www.emaculation.com/doku.php/sheepshaver_mac_os_x_setup
    and
    http://www.everymac.com/mac-answers/mac-os-9-classic-support-faq/run-macos-9-on- intel-macs.html
    and more information about Chubby Bunny:
    http://www.macwindows.com/OS9_on_Intel_Mac.html#092408b
    and
    http://hackthemac.blogspot.co.uk/2008/08/chubby-bunny-old-virtual-machine.html
                                  [click on image to enlarge]

  • IChat does not work on intel macs

    Has anyone with an intel mac gotten this to work successfully? Of course you probably wouldn't be here if you did. But if anyone had problems and eventually resolved them. How?
    I've gone through the basics, opening ports; taking out the router (AirPort Express); turning off the firewall; unpluging everything, including the power cord; still nada. Everything is downloaded and up to date with security patches. My bandwith is unlimited on iChat and the intranet/Lan for Quicktime (and I've toggled on and off the instant on option) and I have a FTTH service with 100MBps ceiling on up and down and never hit anywhere near that (so it isn't a bandwith issue). Repaired permissions in disk utility about a million times. I've verified that the other computer I'm trying to connect to is up to snuff according to the suggested specs through the various blogs posted here.
    And frankly I'm at my wits end. I've given it my all, and can't get back to the apple store until this weekend, but if it isn't fixed there and then (if not before by the advice of you helpful folk), they're taking this DOA computer back and I'm taking my money back.
    So any last advice before my fateful trip to apple land? Anything I'm maybe over looking? Would posting the report from when it crashes help anyone sort this out? I'll do it anyway:
    Date/Time: 2006-03-15 23:04:42.731 +0900
    OS Version: 10.4.5 (Build 8H1455)
    Report Version: 4
    Command: iChat
    Path: /Applications/iChat.app/Contents/MacOS/iChat
    Parent: WindowServer [100]
    Version: 3.1.4 (432)
    Build Version: 1
    Project Name: iChat
    Source Version: 4320000
    PID: 2700
    Thread: 11
    Exception: EXCBADACCESS (0x0001)
    Codes: KERNPROTECTIONFAILURE (0x0002) at 0x00000000
    Thread 0:
    0 libTIFF.dylib 0x91b259e8 LZWDecode + 1139
    1 libTIFF.dylib 0x91b111c1 cgTIFFReadEncodedStrip + 257
    2 com.apple.ImageIO.framework 0x918ff23d getBandProcTIFF + 2359
    3 com.apple.ImageIO.framework 0x918e664f CGImagePlusUpdateCache + 329
    4 com.apple.ImageIO.framework 0x918e636b CGImagePlusCreateImage + 122
    5 com.apple.AppKit 0x9337fd16 -[NSBitmapImageRep _loadData] + 674
    6 com.apple.AppKit 0x9337eb8e +[NSBitmapImageRep _imagesWithData:hfsFileType:extension:zone:] + 5156
    7 com.apple.AppKit 0x9339c648 +[NSBitmapImageRep _imageRepsWithData:hfsFileType:extension:] + 92
    8 com.apple.AppKit 0x9339c0b9 +[NSImageRep imageRepsWithContentsOfFile:] + 646
    9 com.apple.AppKit 0x933f80aa -[NSImage _expandRep:] + 1330
    10 com.apple.AppKit 0x93378338 -[NSImage _expand] + 109
    11 com.apple.AppKit 0x93378201 -[NSImage size] + 127
    12 com.apple.iChat 0x0005d6a6 0x1000 + 378534
    13 com.apple.iChat 0x0005d653 0x1000 + 378451
    14 com.apple.iChat 0x00064677 0x1000 + 407159
    15 com.apple.iChat 0x000640eb 0x1000 + 405739
    16 com.apple.iChat 0x00063eee 0x1000 + 405230
    17 com.apple.iChat 0x00063dbe 0x1000 + 404926
    18 com.apple.iChat 0x00063d02 0x1000 + 404738
    19 com.apple.Foundation 0x926f104f nsnotecallback + 230
    20 com.apple.CoreFoundation 0x9084b861 __CFXNotificationPost + 345
    21 com.apple.CoreFoundation 0x9084308c _CFXNotificationPostNotification + 600
    22 com.apple.Foundation 0x9270ebda -[NSNotificationCenter postNotification:] + 117
    23 com.apple.Foundation 0x9270d047 -[NSNotificationQueue enqueueNotification:postingStyle:coalesceMask:forModes:] + 271
    24 com.apple.viceroy.framework 0x97416dcf -[VCNotificationGateway _postNewFrameNotifiation:] + 67
    25 com.apple.Foundation 0x92712259 __NSFireMainThreadPerform + 352
    26 com.apple.CoreFoundation 0x908557e8 __CFRunLoopPerformPerform + 82
    27 com.apple.CoreFoundation 0x9082263d CFRunLoopRunSpecific + 1213
    28 com.apple.CoreFoundation 0x90822179 CFRunLoopRunInMode + 61
    29 com.apple.HIToolbox 0x92ed28e0 RunCurrentEventLoopInMode + 285
    30 com.apple.HIToolbox 0x92ed1fe7 ReceiveNextEventCommon + 385
    31 com.apple.HIToolbox 0x92ed1e3e BlockUntilNextEventMatchingListInMode + 81
    32 com.apple.AppKit 0x93352ad1 _DPSNextEvent + 576
    33 com.apple.AppKit 0x933526be -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 137
    34 com.apple.AppKit 0x9334c443 -[NSApplication run] + 512
    35 com.apple.AppKit 0x93340397 NSApplicationMain + 573
    36 com.apple.iChat 0x000030d2 0x1000 + 8402
    37 com.apple.iChat 0x0007e7e5 0x1000 + 514021
    Thread 1:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x973f80ab CameraList_Thread + 423
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 2:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x973fa27b Queue_Get + 253
    2 com.apple.viceroy.framework 0x973f8eea -[VCNotificationGateway notificationGatewayProc:] + 209
    3 com.apple.Foundation 0x926f91b0 forkThreadForFunction + 123
    4 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 3:
    0 libSystem.B.dylib 0x9001ab3c select + 12
    1 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 4:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 ...ple.CoreServices.CarbonCore 0x90ca8dda MPWaitOnQueue + 198
    2 ...thesis.MacinTalkSynthesizer 0x167f2229 MTBEWorker::WorkLoop(MTBEWorker*) + 235
    3 ...thesis.MacinTalkSynthesizer 0x167f2397 MTBEWorkerStartMPTask + 17
    4 ...ple.CoreServices.CarbonCore 0x90ca8c34 PrivateMPEntryPoint + 51
    5 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 5:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 ...ple.CoreServices.CarbonCore 0x90ca8dda MPWaitOnQueue + 198
    2 ...thesis.MacinTalkSynthesizer 0x167f2229 MTBEWorker::WorkLoop(MTBEWorker*) + 235
    3 ...thesis.MacinTalkSynthesizer 0x167f2397 MTBEWorkerStartMPTask + 17
    4 ...ple.CoreServices.CarbonCore 0x90ca8c34 PrivateMPEntryPoint + 51
    5 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 6:
    0 libSystem.B.dylib 0x90037f27 machwaituntil + 7
    1 libSystem.B.dylib 0x9003a692 usleep + 82
    2 ....speech.synthesis.framework 0x918d2e52 PollChannelStatus + 38
    3 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 7:
    0 libSystem.B.dylib 0x90049337 semaphoretimedwait_signaltrap + 7
    1 ...apple.AddressBook.framework 0x9480ad54 -[ABRemoteImageLoader workLoop] + 158
    2 com.apple.Foundation 0x926f91b0 forkThreadForFunction + 123
    3 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 8:
    0 libSystem.B.dylib 0x9000a607 machmsgtrap + 7
    1 com.apple.CoreFoundation 0x9082295e CFRunLoopRunSpecific + 2014
    2 com.apple.CoreFoundation 0x9083382f CFRunLoopRun + 60
    3 com.apple.viceroy.framework 0x9746a063 Camera_IdleThread2 + 101
    4 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 9:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x9746d175 Camera_FrameThread + 1565
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 10:
    0 libSystem.B.dylib 0x9000a607 machmsgtrap + 7
    1 com.apple.CoreFoundation 0x9082295e CFRunLoopRunSpecific + 2014
    2 com.apple.CoreFoundation 0x9083382f CFRunLoopRun + 60
    3 ...le.QuickTimeUSBVDCDigitizer 0x15e13b8d APW::PTA::IsochronousThread::Start(APW::PTA::IsochronousThread*) + 297
    4 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 11 Crashed:
    0 com.apple.viceroy.framework 0x9743e4d2 GetCPUIdle + 909
    1 com.ecamm.iglasses 0x005d0623 PrintDebug + 25
    2 com.apple.viceroy.framework 0x97430bcb Conference_OnCaptureSound + 2449
    3 com.apple.viceroy.framework 0x974a7aa8 DeviceManager_OnCaptureSound(void*, float*, double) + 304
    4 com.apple.viceroy.framework 0x97449a79 Microphone_CallbackThread + 1557
    5 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 12:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x9744925f Microphone_NullDevice + 374
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 13:
    0 libSystem.B.dylib 0x90049337 semaphoretimedwait_signaltrap + 7
    1 com.apple.audio.CoreAudio 0x9145fb60 CAGuard::WaitFor(unsigned long long) + 212
    2 com.apple.audio.CoreAudio 0x9145fa82 CAGuard::WaitUntil(unsigned long long) + 66
    3 com.apple.audio.CoreAudio 0x9145e4f2 HP_IOThread::WorkLoop() + 690
    4 com.apple.audio.CoreAudio 0x9145e239 HPIOThread::ThreadEntry(HPIOThread*) + 17
    5 com.apple.audio.CoreAudio 0x91452875 CAPThread::Entry(CAPThread*) + 93
    6 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 14:
    0 libSystem.B.dylib 0x9000a607 machmsgtrap + 7
    1 com.apple.CoreFoundation 0x9082295e CFRunLoopRunSpecific + 2014
    2 com.apple.CoreFoundation 0x90822179 CFRunLoopRunInMode + 61
    3 com.apple.Foundation 0x9272e861 +[NSURLConnection(NSURLConnectionInternal) _resourceLoadLoop:] + 259
    4 com.apple.Foundation 0x926f91b0 forkThreadForFunction + 123
    5 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 15:
    0 libSystem.B.dylib 0x9001ab3c select + 12
    1 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 16:
    0 libSystem.B.dylib 0x9000a607 machmsgtrap + 7
    1 com.apple.CoreFoundation 0x9082295e CFRunLoopRunSpecific + 2014
    2 com.apple.CoreFoundation 0x90822179 CFRunLoopRunInMode + 61
    3 com.apple.Foundation 0x9275595e +[NSURLCache _diskCacheSyncLoop:] + 206
    4 com.apple.Foundation 0x926f91b0 forkThreadForFunction + 123
    5 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 17:
    0 libSystem.B.dylib 0x9001ab3c select + 12
    1 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 18:
    0 libSystem.B.dylib 0x90049337 semaphoretimedwait_signaltrap + 7
    1 ...apple.AddressBook.framework 0x947cda85 -[ABMetaDataController workLoop] + 357
    2 com.apple.Foundation 0x926f91b0 forkThreadForFunction + 123
    3 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 19:
    0 libSystem.B.dylib 0x9001090c read + 12
    1 com.apple.viceroy.framework 0x97446730 EncRspProc + 225
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 20:
    0 libSystem.B.dylib 0x9001e91c recvfrom + 12
    1 com.apple.viceroy.framework 0x9743ab5c RTPRecvRTP + 136
    2 com.apple.viceroy.framework 0x9749b91c RTPRecvProc + 647
    3 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 21:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x9743c4c6 SoundPlayer_AlarmThread + 282
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 22:
    0 libSystem.B.dylib 0x90049337 semaphoretimedwait_signaltrap + 7
    1 com.apple.viceroy.framework 0x97450036 Speaker_CallbackThread + 691
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 23:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 com.apple.viceroy.framework 0x9744c2d6 Speaker_NullDevice + 900
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 24:
    0 libSystem.B.dylib 0x90049337 semaphoretimedwait_signaltrap + 7
    1 com.apple.audio.CoreAudio 0x9145fb60 CAGuard::WaitFor(unsigned long long) + 212
    2 com.apple.audio.CoreAudio 0x9145fa82 CAGuard::WaitUntil(unsigned long long) + 66
    3 com.apple.audio.CoreAudio 0x9145e4f2 HP_IOThread::WorkLoop() + 690
    4 com.apple.audio.CoreAudio 0x9145e239 HPIOThread::ThreadEntry(HPIOThread*) + 17
    5 com.apple.audio.CoreAudio 0x91452875 CAPThread::Entry(CAPThread*) + 93
    6 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 25:
    0 libSystem.B.dylib 0x9001ab3c select + 12
    1 com.apple.viceroy.framework 0x97430e95 Conference_RecvThread + 249
    2 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 26:
    0 libSystem.B.dylib 0x900251e7 semaphorewait_signaltrap + 7
    1 ...le.QuickTimeUSBVDCDigitizer 0x15e1af7b APW::VDO::USBVDC::NativeQueue::WaitForFilledFrame() + 81
    2 ...le.QuickTimeUSBVDCDigitizer 0x15e21f8e APW::VDO::USBVDC::ConversionThread::Start(APW::VDO::USBVDC::ConversionThread*) + 54
    3 libSystem.B.dylib 0x90024b47 pthreadbody + 84
    Thread 11 crashed with i386 Thread State:
    eax: 0x00000000 ebx: 0x9743e156 ecx:0x011cbc0d edx: 0x00000000
    edi: 0x00000000 esi: 0x00000000 ebp:0xb06a7cc8 esp: 0xb06a7c20
    ss: 0x0000002f efl: 0x00010246 eip:0x9743e4d2 cs: 0x00000027
    ds: 0x0000002f es: 0x0000002f fs:0x00000000 gs: 0x00000037
    Binary Images Description:
    0x1000 - 0x17bfff com.apple.iChat 3.1.4 (432) /Applications/iChat.app/Contents/MacOS/iChat
    0x5c9000 - 0x5cafff com.ecamm.pluginloader Ecamm Plugin Loader v1.0.3 (1.0.3) /Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader
    0x5cf000 - 0x5e4fff com.ecamm.iglasses v1.3.2 (1.3.2) /Library/InputManagers/Ecamm/Plugins/iGlasses.plugin/Contents/MacOS/iGlasses
    0x5fd000 - 0x5fefff com.li.hao.saftloader 1.3.0 (423) /Library/InputManagers/Saft/SaftLoader.bundle/Contents/MacOS/SaftLoader
    0x16c0000 - 0x16c9fff com.apple.IOFWDVComponents 1.9.0 /System/Library/Components/IOFWDVComponents.component/Contents/MacOS/IOFWDVComp onents
    0x171a000 - 0x1755fff com.apple.QuickTimeFireWireDV.component 7.0.4 /System/Library/QuickTime/QuickTimeFireWireDV.component/Contents/MacOS/QuickTim eFireWireDV
    0x1761000 - 0x1790fff com.apple.QuickTimeIIDCDigitizer 7.0.4 /System/Library/QuickTime/QuickTimeIIDCDigitizer.component/Contents/MacOS/Quick TimeIIDCDigitizer
    0x17a2000 - 0x17befff GLDriver /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLDriver.bundl e/GLDriver
    0x17c5000 - 0x17e5fff GLRendererFloat /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloa t.bundle/GLRendererFloat
    0x15e12000 - 0x15e51fff com.apple.QuickTimeUSBVDCDigitizer 1.3.5 /System/Library/QuickTime/QuickTimeUSBVDCDigitizer.component/Contents/MacOS/Qui ckTimeUSBVDCDigitizer
    0x15ec6000 - 0x15ec6fff com.apple.bluetooth.SCOCoreAudioDriverIDPlugIn 1.7.2 (1.7.2f10) /System/Library/Extensions/IOBluetoothFamily.kext/Contents/PlugIns/IOBluetoothS COAudioDriver.kext/Contents/Resources/IOBluetoothSCOAudioDriverIDPlugIn.bundle/C ontents/MacOS/IOBluetoothSCOAudioDriverIDPlugIn
    0x160f8000 - 0x1621efff GLEngine /System/Library/Frameworks/OpenGL.framework/Resources/GLEngine.bundle/GLEngine
    0x16246000 - 0x1643bfff com.apple.ATIRadeonX1000GLDriver 1.4.24 (4.2.4) /System/Library/Extensions/ATIRadeonX1000GLDriver.bundle/Contents/MacOS/ATIRade onX1000GLDriver
    0x16757000 - 0x1675bfff com.apple.audio.AudioIPCPlugIn 1.0.0 (1.0) /System/Library/Extensions/AudioIPCDriver.kext/Contents/Resources/AudioIPCPlugI n.bundle/Contents/MacOS/AudioIPCPlugIn
    0x16777000 - 0x167a0fff com.apple.audio.SoundManager.Components 3.9.2 /System/Library/Components/SoundManagerComponents.component/Contents/MacOS/Soun dManagerComponents
    0x167e6000 - 0x16832fff com.apple.speech.synthesis.MacinTalkSynthesizer 3.4 /System/Library/Speech/Synthesizers/MacinTalk.SpeechSynthesizer/Contents/MacOS/ MacinTalk
    0x16a7e000 - 0x16a7ffff com.ecamm.iGlassesVDIG iGlasses v1.3.2 (1.3.2) /Library/Components/iGlasses.component/Contents/MacOS/iGlasses
    0x16a84000 - 0x16a8bfff com.apple.iokit.IOUSBLib 2.4.0 /System/Library/Extensions/IOUSBFamily.kext/Contents/PlugIns/IOUSBLib.bundle/Co ntents/MacOS/IOUSBLib
    0x175ab000 - 0x175aefff com.apple.iokit.IOQTComponents 1.4 /System/Library/Components/IOQTComponents.component/Contents/MacOS/IOQTComponen ts
    0x70000000 - 0x70105fff com.apple.audio.units.Components 1.4.2 /System/Library/Components/CoreAudio.component/Contents/MacOS/CoreAudio
    0x8fe00000 - 0x8fe4bfff dyld 44.17 /usr/lib/dyld
    0x90000000 - 0x9016efff libSystem.B.dylib /usr/lib/libSystem.B.dylib
    0x901be000 - 0x901c0fff libmathCommon.A.dylib /usr/lib/system/libmathCommon.A.dylib
    0x901c2000 - 0x901fefff com.apple.CoreText 1.1.0 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreText.framework/Versions/A/CoreText
    0x90225000 - 0x902fafff ATS /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ATS.framework/Versions/A/ATS
    0x9031a000 - 0x90769fff com.apple.CoreGraphics 1.258.23 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/CoreGraphics
    0x90800000 - 0x908c8fff com.apple.CoreFoundation 6.4.5 (368.26) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
    0x90906000 - 0x90906fff com.apple.CoreServices 10.4 (???) /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x90908000 - 0x909fbfff libicucore.A.dylib /usr/lib/libicucore.A.dylib
    0x90a4b000 - 0x90acafff libobjc.A.dylib /usr/lib/libobjc.A.dylib
    0x90af3000 - 0x90b56fff libstdc++.6.dylib /usr/lib/libstdc++.6.dylib
    0x90bc5000 - 0x90bccfff libgcc_s.1.dylib /usr/lib/libgcc_s.1.dylib
    0x90bd1000 - 0x90c41fff com.apple.framework.IOKit 1.4.2 (???) /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x90c56000 - 0x90c68fff libauto.dylib /usr/lib/libauto.dylib
    0x90c6e000 - 0x90f13fff com.apple.CoreServices.CarbonCore 682.9 (679) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore
    0x90f56000 - 0x90fbefff com.apple.CoreServices.OSServices 4.1 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServi ces.framework/Versions/A/OSServices
    0x90ff6000 - 0x91033fff com.apple.CFNetwork 129.10 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CFNetwo rk.framework/Versions/A/CFNetwork
    0x91045000 - 0x91055fff com.apple.WebServices 1.1.3 (1.1.0) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/WebServ icesCore.framework/Versions/A/WebServicesCore
    0x91060000 - 0x910defff com.apple.SearchKit 1.0.5 /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchK it.framework/Versions/A/SearchKit
    0x91113000 - 0x91131fff com.apple.Metadata 10.4.4 (121.35) /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadat a.framework/Versions/A/Metadata
    0x9113d000 - 0x9114bfff libz.1.dylib /usr/lib/libz.1.dylib
    0x9114e000 - 0x91301fff com.apple.security 4.2.1 (24989) /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x913ef000 - 0x913f7fff com.apple.DiskArbitration 2.1 /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    0x913fe000 - 0x91424fff com.apple.SystemConfiguration 1.8.5 /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
    0x91436000 - 0x9143dfff libbsm.dylib /usr/lib/libbsm.dylib
    0x91441000 - 0x914bafff com.apple.audio.CoreAudio 3.0.2 /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio
    0x91508000 - 0x91508fff com.apple.ApplicationServices 10.4 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
    0x9150a000 - 0x91535fff com.apple.AE 314 (313) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ AE.framework/Versions/A/AE
    0x91548000 - 0x9161cfff com.apple.ColorSync 4.4.6 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ColorSync.framework/Versions/A/ColorSync
    0x91655000 - 0x916d2fff com.apple.print.framework.PrintCore 4.4 (177.6) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ PrintCore.framework/Versions/A/PrintCore
    0x916ff000 - 0x917a9fff com.apple.QD 3.10.7 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ QD.framework/Versions/A/QD
    0x917cf000 - 0x9181afff com.apple.HIServices 1.5.2 (???) /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ HIServices.framework/Versions/A/HIServices
    0x91839000 - 0x9184ffff com.apple.LangAnalysis 1.6.3 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LangAnalysis.framework/Versions/A/LangAnalysis
    0x9185b000 - 0x91875fff com.apple.FindByContent 1.5 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ FindByContent.framework/Versions/A/FindByContent
    0x9187f000 - 0x918bcfff com.apple.LaunchServices 176 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ LaunchServices.framework/Versions/A/LaunchServices
    0x918d0000 - 0x918dbfff com.apple.speech.synthesis.framework 3.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ SpeechSynthesis.framework/Versions/A/SpeechSynthesis
    0x918e2000 - 0x91916fff com.apple.ImageIO.framework 1.4.4 /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/ImageIO
    0x91928000 - 0x919dafff libcrypto.0.9.7.dylib /usr/lib/libcrypto.0.9.7.dylib
    0x91a20000 - 0x91a36fff libcups.2.dylib /usr/lib/libcups.2.dylib
    0x91a3b000 - 0x91a57fff libJPEG.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJPEG.dylib
    0x91a5c000 - 0x91abafff libJP2.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libJP2.dylib
    0x91aca000 - 0x91acefff libGIF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libGIF.dylib
    0x91ad0000 - 0x91b07fff libRaw.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRaw.dylib
    0x91b0a000 - 0x91b4dfff libTIFF.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libTIFF.dylib
    0x91b53000 - 0x91b6dfff libPng.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libPng.dylib
    0x91b72000 - 0x91b74fff libRadiance.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ ImageIO.framework/Versions/A/Resources/libRadiance.dylib
    0x91b76000 - 0x91b76fff com.apple.Accelerate 1.2.1 (Accelerate 1.2.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
    0x91b78000 - 0x91bfbfff com.apple.vImage 2.2 /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.fr amework/Versions/A/vImage
    0x91c02000 - 0x91c02fff com.apple.Accelerate.vecLib 3.2.1 (vecLib 3.2.1) /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/vecLib
    0x91c04000 - 0x91c49fff libvMisc.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvMisc.dylib
    0x91c51000 - 0x91c76fff libvDSP.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libvDSP.dylib
    0x91c7d000 - 0x92200fff libBLAS.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libBLAS.dylib
    0x9223d000 - 0x925effff libLAPACK.dylib /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.fr amework/Versions/A/libLAPACK.dylib
    0x9261c000 - 0x926a0fff com.apple.DesktopServices 1.3.2 /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/Desk topServicesPriv
    0x926dc000 - 0x9290efff com.apple.Foundation 6.4.5 (567.26) /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x92a1a000 - 0x92af8fff libxml2.2.dylib /usr/lib/libxml2.2.dylib
    0x92b15000 - 0x92c02fff libiconv.2.dylib /usr/lib/libiconv.2.dylib
    0x92c12000 - 0x92c29fff libGL.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib
    0x92c34000 - 0x92c8bfff libGLU.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib
    0x92c9f000 - 0x92c9ffff com.apple.Carbon 10.4 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x92ca1000 - 0x92cb1fff com.apple.ImageCapture 3.0.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture. framework/Versions/A/ImageCapture
    0x92cbf000 - 0x92cc7fff com.apple.speech.recognition.framework 3.5 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecogni tion.framework/Versions/A/SpeechRecognition
    0x92ccd000 - 0x92cd2fff com.apple.securityhi 2.0.1 (24742) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.fr amework/Versions/A/SecurityHI
    0x92cd8000 - 0x92d69fff com.apple.ink.framework 101.2.1 (71) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework /Versions/A/Ink
    0x92d7d000 - 0x92d80fff com.apple.help 1.0.3 (32.1) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framewor k/Versions/A/Help
    0x92d83000 - 0x92da0fff com.apple.openscripting 1.2.3 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting .framework/Versions/A/OpenScripting
    0x92db0000 - 0x92db6fff com.apple.print.framework.Print 5.1 (192.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framewo rk/Versions/A/Print
    0x92dbc000 - 0x92e1ffff com.apple.htmlrendering 66.1 (1.1.3) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HTMLRendering .framework/Versions/A/HTMLRendering
    0x92e43000 - 0x92e84fff com.apple.NavigationServices 3.4.3 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/NavigationSer vices.framework/Versions/A/NavigationServices
    0x92eab000 - 0x92eb8fff com.apple.audio.SoundManager 3.9.1 /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CarbonSound.f ramework/Versions/A/CarbonSound
    0x92ebf000 - 0x92ec4fff com.apple.CommonPanels 1.2.3 (73) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels. framework/Versions/A/CommonPanels
    0x92ec9000 - 0x931bbfff com.apple.HIToolbox 1.4.5 (???) /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.fra mework/Versions/A/HIToolbox
    0x932c0000 - 0x932cbfff com.apple.opengl 1.4.8 /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
    0x932d0000 - 0x932ebfff com.apple.DirectoryService.Framework 3.0.1 /System/Library/Frameworks/DirectoryService.framework/Versions/A/DirectoryServi ce
    0x93339000 - 0x93339fff com.apple.Cocoa 6.4 (???) /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x9333b000 - 0x939f4fff com.apple.AppKit 6.4.5 (824.35) /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
    0x93d75000 - 0x93deffff com.apple.CoreData 90 /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData
    0x93e28000 - 0x93ee8fff com.apple.audio.toolbox.AudioToolbox 1.4.2 /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox
    0x93f27000 - 0x93f27fff com.apple.audio.units.AudioUnit 1.4.2 /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit
    0x93f29000 - 0x940defff com.apple.QuartzCore 1.4.4 /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
    0x94124000 - 0x94165fff libsqlite3.0.dylib /usr/lib/libsqlite3.0.dylib
    0x9416d000 - 0x941a6fff libGLImage.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dyl ib
    0x941e3000 - 0x9422afff com.apple.bom 8.3 (86.1) /System/Library/PrivateFrameworks/Bom.framework/Versions/A/Bom
    0x94234000 - 0x94269fff com.apple.vmutils 4.0.1 (87) /System/Library/PrivateFrameworks/vmutils.framework/Versions/A/vmutils
    0x942ab000 - 0x942bbfff com.apple.securityfoundation 2.1.1 (26040) /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoun dation
    0x942c8000 - 0x94305fff com.apple.securityinterface 2.1.1 (24989) /System/Library/Frameworks/SecurityInterface.framework/Versions/A/SecurityInter face
    0x94321000 - 0x94330fff libCGATS.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCGATS.A.dylib
    0x94337000 - 0x94342fff libCSync.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libCSync.A.dylib
    0x9438e000 - 0x943a8fff libRIP.A.dylib /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ CoreGraphics.framework/Versions/A/Resources/libRIP.A.dylib
    0x943ae000 - 0x9465ffff com.apple.QuickTime 7.0.4 /System/Library/Frameworks/QuickTime.framework/Versions/A/QuickTime
    0x947bf000 - 0x94907fff com.apple.AddressBook.framework 4.0.3 (477.6) /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
    0x94993000 - 0x949a2fff com.apple.DSObjCWrappers.Framework 1.1 /System/Library/PrivateFrameworks/DSObjCWrappers.framework/Versions/A/DSObjCWra ppers
    0x949a9000 - 0x949d2fff com.apple.LDAPFramework 1.4.1 (69.0.1) /System/Library/Frameworks/LDAP.framework/Versions/A/LDAP
    0x949d8000 - 0x949e7fff libsasl2.2.dylib /usr/lib/libsasl2.2.dylib
    0x949eb000 - 0x94a0ffff libssl.0.9.7.dylib /usr/lib/libssl.0.9.7.dylib
    0x94a1b000 - 0x94a38fff libresolv.9.dylib /usr/lib/libresolv.9.dylib
    0x94a3f000 - 0x94aa5fff com.apple.Bluetooth 1.7.2 (1.7.2f10) /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth
    0x94d61000 - 0x94df3fff com.apple.WebKit 417.9 /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
    0x94e4c000 - 0x94f2bfff com.apple.JavaScriptCore 417.9 /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/JavaScriptCor e.framework/Versions/A/JavaScriptCore
    0x94f5e000 - 0x95237fff com.apple.WebCore 417.22 /System/Library/Frameworks/WebKit.framework/Versions/A/Frameworks/WebCore.frame work/Versions/A/WebCore
    0x95393000 - 0x953b6fff libxslt.1.dylib /usr/lib/libxslt.1.dylib
    0x96100000 - 0x96112fff com.apple.speech.SpeechDictionary 3.4 /System/Library/PrivateFrameworks/SpeechDictionary.framework/Versions/A/SpeechD ictionary
    0x9652d000 - 0x9652dfff com.apple.vecLib 3.2.1 (vecLib 3.2.1) /System/Library/Frameworks/vecLib.framework/Versions/A/vecLib
    0x96a0c000 - 0x96a2dfff com.apple.speech.LatentSemanticMappingFramework 2.4 /System/Library/PrivateFrameworks/LatentSemanticMapping.framework/Versions/A/La tentSemanticMapping
    0x96a9d000 - 0x96b52fff libGLProgrammability.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgramma bility.dylib
    0x96b6c000 - 0x96b6dfff libGLSystem.dylib /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLSystem.dy lib
    0x96b6f000 - 0x96b74fff com.apple.agl 2.5.9 (AGL-2.5.9) /System/Library/Frameworks/AGL.framework/Versions/A/AGL
    0x96ca8000 - 0x96ca9fff com.apple.MonitorPanelFramework 1.1.1 /System/Library/PrivateFrameworks/MonitorPanel.framework/Versions/A/MonitorPane l
    0x973ef000 - 0x974d4fff com.apple.viceroy.framework 270.16 /System/Library/PrivateFrameworks/VideoConference.framework/Versions/A/VideoCon ference
    0x97bf2000 - 0x97bf4fff com.apple.DisplayServicesFW 1.8.2 /System/Library/PrivateFrameworks/DisplayServices.framework/Versions/A/DisplayS ervices
    0x97e1d000 - 0x989b9fff com.apple.QuickTimeComponents.component 7.0.4 /System/Library/QuickTime/QuickTimeComponents.component/Contents/MacOS/QuickTim eComponents
    0x992b6000 - 0x992c1fff com.apple.IMFramework 3.1.1 (427) /System/Library/Frameworks/InstantMessage.framework/Versions/A/InstantMessage
    0x992cb000 - 0x99437fff com.apple.MessageFramework 2.0.8 (749.3) /System/Library/Frameworks/Message.framework/Versions/B/Message
    Model: MacBookPro1,1, BootROM MBP11.0044.B02, 2 processors, Intel Core Duo, 2.16 GHz, 2 GB
    Graphics: ATI Radeon X1600, ATY,RadeonX1600, PCIe, 256 MB
    Memory Module: DIMM0/BANK 0, 1 GB, DDR2 SDRAM, 667 MHz
    Memory Module: DIMM1/BANK 1, 1 GB, DDR2 SDRAM, 667 MHz
    AirPort: spairportwireless_card_type_airportextreme (0x168C, 0x86), 0.1.12
    Bluetooth: Version 1.7.2f10, 2 service, 0 devices, 1 incoming serial ports
    Network Service: AirPort, AirPort, en1
    PCI Card: ethernet, sppci_ethernet, Airport
    Serial ATA Device: ST910021AS, 93.16 GB
    Parallel ATA Device: MATSHITADVD-R UJ-857
    USB Device: Built-in iSight, Micron, Up to 480 Mb/sec, 500 mA
    USB Device: Bluetooth HCI, Up to 12 Mb/sec, 500 mA
    USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, Up to 12 Mb/sec, 500 mA
    USB Device: IR Receiver, Apple Computer, Inc., Up to 12 Mb/sec, 500 mA
    any of that make any sense to anyone?
    Thanks for any help you can give, and feel free to share your similar frustrations,
    Jesse

    Hi Jester,
    Two things,
    The Quicktime setting is going to need to be 1.5Mb as iChat dislike LAN/Intranet
    iGlasses is not going to work with iChat unless you ask iChat to run with Rosetta.
    Go to the File Menu and use the Open With Rosetta option.
    This is because you may not have the iGlasses as a Unviversal coded Add-on. See the third bullet point.
    Update it if required. Delete it for Trouble shooting (Crashed Thread 11)
    The paths are in this bit
    0x5c9000 - 0x5cafff com.ecamm.pluginloader Ecamm Plugin Loader v1.0.3 (1.0.3) /Library/InputManagers/Ecamm/Ecamm Plugin Loader.bundle/Contents/MacOS/Ecamm Plugin Loader
    0x5cf000 - 0x5e4fff com.ecamm.iglasses v1.3.2 (1.3.2) /Library/InputManagers/Ecamm/Plugins/iGlasses.plugin/Contents/MacOS/iGlasses
    0x5fd000 - 0x5fefff com.li.hao.saftloader 1.3.0 (423) /Library/InputManagers/Saft/SaftLoader.bundle/Contents/MacOS/SaftLoader
    What is Saft or SaftLoader ??
    3:27 PM Wednesday; March 15, 2006

  • Intel Mac Pro w/10.4.7 - I need to access a 2003 Western Digital hard drive

    Hey another question for the gurus of Mac out there. Got an Intel Mac Pro running 10.4.7 and I need to access old information from someones else's Western Digital (internal/ external w/case) drive. It's a "WD1200JB-00RCA1" model drive from 2003. I've already tried using the case with firewire connection on both my laptop and Mac Pro, but it will not mount. I does get power though. I'm thinking of trying it internally, but know that the Mac Pro is picky about specific types and specs on drives. Just curious if anyone thinks I can make it work internaly without screwing up the drive or more importantly, the Mac Pro.
    Apparently this same drive was used internally on a mac back in 2003, but obvioulsy an older Mac. Any tips appreciated.

    That drive (according to WD) is a WD Caviar SE 120GB UDMA 100 IDE drive. Assuming everything is set-up correctly, external enclosures typically require the drive to be jumpered as and IDE master, then it should mount.
    The fact that it doesn't mount is not a good sign.
    You could try this internally in the spare optical drive bay - you'd need a 5.25" to 3.5" mounting kit. If I were to go this route, I'd disconnect the optical drive temporarily - the cables will reach better and you stand less chance of getting an IDE bus incompatability with the optical drive.
    I think the default set-up for the MacPro IDE bus is Cable Select so you may need to look into jumpering the drive dor this (CSEL)

  • MPEG on Intel Mac

    I'm just wondering if anyone else has had issues playing .mpg
    files in authorware on an Intel Mac? When I try to play them I get
    and error about 'unable to load external movie driver'. These
    videos work find on non-Intel macs and they even play fine in
    QuickTime on the Intel macs but when they are played through
    authorware I get the error.
    Appreciate any suggestions

    Not yet having an Intel-Mac, I can't try this nor offer
    certain
    suggestions...
    How are you trying to play the movies in Authorware? Using
    the movie
    icon, I'd guess. And that should be fine...
    But if that's not working, try the QT Sprite (Insert >
    Media >
    Quicktime)? Just as something to try.
    Since that would require QT to be loaded on the PC version,
    if it works
    as a solution, you may have to setup two movies - one the
    movie icon and
    one the QT Sprite - and play either one based on OSNumber...
    Erik
    ahess24 wrote:
    > I'm just wondering if anyone else has had issues playing
    .mpg files in
    > authorware on an Intel Mac? When I try to play them I
    get and error about
    > 'unable to load external movie driver'. These videos
    work find on non-Intel
    > macs and they even play fine in QuickTime on the Intel
    macs but when they are
    > played through authorware I get the error.
    >
    > Appreciate any suggestions
    >
    Erik Lord
    http://www.capemedia.net
    Adobe Community Expert - Authorware
    http://www.adobe.com/communities/experts/
    http://www.awaretips.net -
    samples, tips, products, faqs, and links!
    *Search the A'ware newsgroup archives*
    http://groups.google.com/group/macromedia.authorware
    *The Blankenship Caveat: Note that direct linking to http
    content
    through any Authorware icon will likely fail if a proxy
    server is present!*

  • Filemaker Pro loses applescript ability on intel mac

    Hello
    I am trying to install FMP6 on an intel mac. However when I do so, it loses all its applescript ability. Filemaker scripts no longer compile.
    If I go to the applescript library, click the 'add' button, navigate to my filemaker application, it spits up this error: "Unable to add the application or extension because it is not scriptable". This does not happen on a PPC machine. It adds the application perfectly.
    Does anyone have a workaround for this ... other than going back to a PPC or upgrading Filemaker - I mean a workaround to get the dictionary working on an intel mac.

    Short answer: You can't. Buy an older Mac that supports OS 9 booting or Classic mode with OS X 10.4 or earlier.
    Longer answer: There are third party OS 9 emulators that run on Intel Macs. One of them allows one to run OS 9.0.4. But these generally require one to have an OS 9 boot ROM image, and AFAIK there's no way to get one of these that complies with Apple's licensing requirements, other than buying an older Mac that supports OS 9 booting. As such it is against this forum's Terms of Use to discuss it further here. Google is your friend.

  • Using two displays simultaneously on an early intel mac mini

    I would like to connect my Apple display and an LCD TV to my early Intel Mac Mini using a DVI-D splitter and DVI-D cable to the DVI input on the TV. I don't know if this Mac Mini's video card has a single or a duel DVI output. I'm assuming it has to have a duel output to be able to have both displays on at the same time. Also, from what I've read previously in the discussions, I assume I'll have hook up the audio output also, assuming the video works. Thanks for any help.

    I'm pretty sure that can't work for a variety of reasons. Primarily the DVI output on the mini has a single digital output, not two. It has been shown that it can output VGA analog and DVI digital simultaneously when booted under Windows, but the OS X driver for the GMA950 does not support that same trick. So I don't think you are going to be able to do what you want unless you run Windows.
    You could try add-on hardware if you really have your mind set on this. There are USB-to-video adapters out there on the market. They are reported to work pretty well with the caveat that they can't be used for things like full screen video which requires more bandwidth than USB can supply. But for a mostly static display, like using a mail reader or a browser without too much animation, or a spreadsheet, etc., they work well enough.

  • New Intel Mac mini: Is 1G Ram Enough?

    Hello everyone.
    I intend to get my dad and my sis (upgrade from her old iMac G3) each a new Intel Mac mini Core Solo.
    I understand that the new Intel Mac mini shares the ram memory between the processor and the "in-built" graphics... also understand from an Apple KB docu that it is best to pair the same ram to maximise efficiency or something...
    My dad will be mainly in iPhoto, organising his digital photos, burning CDs and touching up a bit here and there; And both of them will be using mainly to surf, email, chat, maybe a bit of word processing etc - I would say "light to moderate work"
    So is 1Gb of Ram enough for the processor and the graphics? I would probably try to max out as big a hard disk for them... and a 19" monitor...
    Thanks and cheers

    If he can afford it, I would recommend putting 2-1G modules in there. OS X loves RAM and will call for even more running apps under Rosetta.
    How To Determine Your Memory Needs >>
    -Bmer
    Mac Owners Support Group
    Join Us @ MacOSG.com
     An Apple User Group 
    ITMS: MacOSG Podcast >>
    Disclaimer required by Apple Discussions Terms of Use: MacOSG - a non-profit Apple User Group - may receive some form of compensation, financial or otherwise, from my recommendation or link.

  • Which Intel Mac for Music Recording, Please?

    Hi--
    I'm brand new here. I'm a music professional who is in the middle of switching my recording setup toan Intel Mac-based studio, running either Logic Pro or Digital Performer (once it's ready for Intel Macs, that is).
    I've got an indie filmscoring job coming up--my second. The first was done without a computer--never again!
    I require some meqasure of portability--I'll be travelling between San Diego and central Mexico a few times throughout the process, either driving or occasionally flying.
    So last week I ordered a MacBook Pro 17" notebook with a 2.16 Ghz processor, a 100 gig, 7200 rpm drive and 2 gigs of RAM. I have been assured by friends and contascts in the filmscoring word that this is enough horsepower to run the applications I'll need to run (mostly the recording and sequencing software, plus Quick Time).
    However...I just bought my wife a 17" Intel iMac. Whoa. What a cool machine! Looking at the specs, I see it has a 1.83 Ghz dual processor, a 160 gig drive (don't know the speed offhand) and while it only comes with 512 mb of RAM I know it's upgradable to at least 2 gigs, right?
    So my question is this: is the performance going to be higher on a suped-up iMac than the suped-up MacBookPro? Does anyone have an educated guess about this? The notebook has a faster processor, but...it is a laptop with a laptop drive, which are typically not as fast as a desktop drive from what I understand.
    Many thanks!
    Doug

    If I may wade in--
    Strictly speaking from a travel/immigration perspective, you are less likely to have trouble with Mexican Customs with the MacBook Pro than with the iMac 17" or 20". The immigration laws allow foreigners to enter with a personal portable computer duty free. Something as large as an iMac is possibly tempting to a corrupt official, whether they are eying it for themself or as a opportunity to pocket a chunk of change to allow you to bring it in. We have a presidential election in July, and I have noticed the old corruption creeping back in at the borders and internal customs check points that existed pre-Vicente Fox. Corrupt agents going back to the good-old-days, when it was common to supplement one's monthly salary any way one could. Do yourself a favor and go powerful, and yet less conspicuous.

  • Eastwest Gold Bundle doesn't work on intel macs

    I got Eastwest Symphony Orchestra Gold Bundle today and just found out that it wouldn’t work with Logic 8 because it’s not Universal Binary. Now what's the best way to solve this problem? I've read that I need to spend another $300 on Kontakt just to HOST the eastwest in Logic 8 in MacBook Pro, aside of just spending $600 on the Gold Bundle. You know that's quite mad. I got the Logic Studio for $150 (academic in university store) and it works so well without any registration hassle. By contrast Eastwest comes with out of date VISE installer, tons of updating requirements, multiple visits to Native Instruments, and after all it doesn't work in your DAW if you use Intel Macs, which includes EVERY apple computer in stores right now. How can people of Eastwest sleep at night?
    Anyways, I'm looking for solutions. Any work around? Please help! And thank you!
    Tim

    This probably doesn't help but...
    If you do end up forking out the $$ for Kontakt, you will have purchased a FANTASTIC program that also happens to include a pretty extensive sample library. I do like EWQL Gold better than the VSL subset that comes with Kontakt, but the VSL subset is only a part of what comes with Kontakt.
    In any case, to really get the best of EWQL Gold, you will be much better off if you get Kontakt or Play. The Kompakt software is OK, but for a whole orchestra, it is much more convenient to have a full sampler IMHO.

Maybe you are looking for