Boot Camp, W7Pro, Premiere Pro - and Thunderbolt

I've seen only a handful of video or articles that says I can get W7 Pro to see a Thunderbolt external drive under Boot Camp.  It seems that it can be done, though there may be some limitations (that I am not concerned about).  But the articles are all by high-end tech pros.  I was wondering if any regular-folk users on this forum have gone this route, and what type of problems you may have faced.
If it helps to know, we will try this on a 27" imac purchased this week.  Thanks in advance.

Great! It seems Boot Camp is the right choice for my purposes.
One more question...
I assume I'll need to install anti-virus software once Windows is installed. I've been using Avast without problems for years. Is it compatable with an installation of this nature, or is there a more compatable anti-virus program? I wouldn't touch Norton with a barge pole.
Thanks again. :-)

Similar Messages

  • Boot Camp, XP, Macbook Pro and a Cinema Display

    Add these things together and what do you get? Frustration enough to beat my head against the wall.
    If I get my Cinema Display to work at all when connected to the MBP in XP, it's because I said a prayer to Bill Gates, or I looked away at just the right time, or some other arcane mystical crap because without changing Display parameters at any time, it's a completely random crap shoot on whether or not XP will send output to my Cinema Display. I can't get clamshell mode to work at all. So, I cripple my video capabilities when I actually manage to get output to the Cinema Display.
    I loaded the Boot Camp XP drivers and CCC app from Ati's site. They don't help. They don't run. They want 2.0 .Net framework, and somehow, with all the patches and crap downloaded and installed from microsoft they still don't work. I get errors of missing implementation files. The whole thing is buggier than ****. Had to find and install 2.0 .Net framework, then patch it. Still nothing works right.
    I am my wits end and frustrated beyond belief. Anyone at all have suggestions to help? I've tried three times to get help from Applecare, and I either get told they can't help me, or I get put on hold then hung up on.

    Same problem with a brand new (today) 20" CInema Display. Annoying but not a big issue until now.
    MacBookPro 2.16 2Go RAM 20" CInema Display   Mac OS X (10.4.10)  

  • I have installed Windows 7 using Boot Camp on Macbook Pro OSX 10.9.3, I'm not able to connect to wireless and its not showing as well in network sharing. Please help

    I have installed Windows 7 using Boot Camp on Macbook Pro OSX 10.9.3, I'm not able to connect to wireless and its not showing as well in network sharing. Please help

    Hello Bhagyeshree
    Check out the articles below to troubleshoot issues with connecting to Wi-Fi. Start with creating a new Network Location and then search for a Wi-Fi network and if that does not work, then go through second article to troubleshoot the issue further.
    OS X Mavericks: Add a network location
    http://support.apple.com/kb/PH13788
    Wi-Fi: How to troubleshoot Wi-Fi connectivity
    http://support.apple.com/kb/HT4628
    Regards,
    -Norm G.  

  • Dual monitor not working under Boot Camp on Mac Pro ATI HD 2600 XT

    Recently got a brand new Mac Pro with ATI Radeon HD 2600 XT graphics card.
    On the Mac side (Leopard), everything works perfectly: my second monitor (a plasma screen connected with HDMI to the second DVI of the ATI card via HDMI/DVI adapter) is fully recognized and it works as an extended desktop or in Mirroring mode.
    Under Boot Camp (Windows XP Pro) however, NOTHING: the second monitor always appears in the display properties, but it is grayed out (inactive), and when I try to activate it, it switches back to being grayed out immediately and nothing gets displayed on it.
    After reading all the posts I can find on the topic, I tried the following (in pretty much every possible combination - Thank god for WinClone that allows me to restore the Boot Camp basic install image without having to reinstall Windows from scratch every time):
    a) Bootcamp 2.0 (installed by default by Bootcamp assistant)
    b) Update to Bootcamp 2.1
    1) Windows XP Pro SP2c vanilla install (from my Windows XP pro install disk)
    2) Update to Windows XP SP3 (I tried with and without BC 2.1: both worked -> BC 2.1 didn't seem to be required for SP3 - maybe because this is a mac pro and not a MB or MBP)
    i) ATI drivers installed by default by Boot Camp assistant (BC 2.0) or by BC 2.1
    ii) Latest ATI drivers found on ATI web site specifically under Boot Camp / Mac Pro.
    Note: Interestingly, the catalyst installer worked ok (provided .NET framework 2.0 is installed though), but it seems that the Radeon BootCamp/Mac Pro driver set itself from ATI's web site does NOT include a driver for the HD 2600 XT - so when I install this driver set, it tells me that no compatible hardware was found...
    iii) Latest ATI drivers found under Windows XP (these did include one driver specifically for the Radeon HD 2600 XT)
    NOTHING seems to work. I read posts (most of the from late last year) about ATI Catalyst utility showing a 3rd monitor at some point, but I never got any 3rd monitor showing in any of my many many trials with Catalyst. I have yet to get a single image appear on my plasma under Bootcamp Windows. I don't believe its the hardware because everything works great on the max OS X side.
    I am actually considering switching to an NVidia 8800 GT just to get the dual screen to work under BootCamp/Windows XP because I really need it and I read everywhere that drivers for NVidia are far better than ATI ones.
    Any advice? What should I try next before getting an 8800 ?
    Is there a diagnostic utility that I can use to test my config including the GC?
    Thanks!

    Hi there aside from my laptop I have an iMac 20" with the same HD 2600 XT card. I recently installed the Catalyst 8.6 driver by using a driver mod from driverheaven, I use Vista 32. By installing it this way I got boosted performance and many issues with the bootcamp drivers were fixed. As you may already know the ATI drivers do not install on bootcamped macs usually but the mod tool fixes this. Its unofficial so do so at your own risk but try it out and see if you get the second monitor if not just rollback. Hope this helps and I didn't want to say too much about the 8.6 driver mod because it may not be allowed here but google will provide any answers.

  • Boot Camp Installation: Definition of, and insights into "External Drives"?

    I'm recovering from a logic board failure. One casualty was that I lost my prior Boot Camp installation of Windows on my main internal hard drive. :-( Wondering if I can install Windows anywhere other than the main internal hard drive so I can maximize space on my OSX main internal drive?
    From what I've gathered, installing Windows 7 Boot Camp is very difficult (and perhaps impossible?) on an external hard drive. However, what's not entirely clear is what constitutes an "external drive".
    Questions:
    1. Can I install a bootable installation of Windows 7 using Boot Camp (obviously not running OSX in this scenario) on either the:
         A) Data Doubler 7,200 drive
    or
         B) Express Card 34 SSD drive
    2. Can I also install Parallels (on the main internal OSX drive), then while in OSX launch (a much slower) Windows from location A or B?
    Context:
    1.  On a late 2011 MBP 17' (version 8,3), I've replaced the stock hard drive (7,200 rpm) with a much faster OWC SSD Drive. (Awesome upgrade, btw!)
    2. The internal apple dvd device was removed and the stock hard drive was inserted in this location using OWC Data Doubler. (Also, very nice.) An extra challenge here is that the dvd drive is now an external device. I have a Windows 7 install disc, but I'm not sure if it will be recognized during the installation process?
    3. This model MBP has an ExpressCard 34 slot, for which I can buy an SSD drive. Never used this slot and have read mixed reports on boot ability.
    Any and all insights greatly appreciated!

    Yoüf wrote:
    Many thanks for the helpful response, Loner T.  I think I've got it. To install Windows through BCA on the Optibay drive, I temporarily move it to the main SATA bay. I can then temporarily put the DVD drive back in the Optibay. So here's a question: In doing this, I would no longer have an OSX boot drive (since I'm temporarily removing my OSX boot SSD). It's been a while since I used BCA, so my memory is fuzzy (sorry), but does the BCA process need a working OSX install on the drive in the SATA bay?
    The SSD with OSX boot is normally (for your specific scenario) kept in an external enclosure (USB/FW/TB) to boot from and run BC and partition the disk in the main SATA bay.
    You mention that modifying the BC info.plist causes issues. I lost you a little here. Using the method you describe (move the Optibay drive to the SATA location, run BCA to install Windows, then move the drive back to the Optibay location), does the BC info.plist need to be modified or not?  If yes, a few more details would be welcomed. If not, what prompted this thought?
    If you have a functional Optical drive and the designated Windows-to-be in the proper bays, the BC info.plist modifications are unnecessary, and can cause other grief, and are best avoided.
    Thanks also for the bleeptobleep post. It says to use a USB3/Thunderbolt external drive (which I do have); however, my MBP (version 8,3) only has USB2 ports. I realize that a USB2 port will read a USB3 external drive, but was wondering if this limitation is a deal breaker for a bootable Windows system, or if it just means that things will be really, really, tragically slow due to low transfer rates. Any idea on this aspect?
    USB3 can cause problems for Windows 7 installer, bot not as many issues for Windows 8+. It is better to stick to USB2, but you are correct it will be slow. OSX can boot and will use RAM much more aggressively, unless it has to go back to the USB (2/3) when things may give you a beach ball. Windows 7/8 are less friendly for caching the whole OS and applications in RAM, and may be slower. A TB connection is much faster (TB2 even better).
    BTW: Bummer that the ExpressCard slot can't work for booting into Windows. That would be pretty slick. I've seen some older posts by folks who were once able to do this, but seemingly only with early versions of OSX. Apparently newer OSX versions either did away with this feature, or seriously complicated the process. Would love to find a workaround if one exists.
    You can test it, but may have some issues finding storage for ECards.
    (Dumb question: on this forum, how are you threading comments into a quoted block of text? Are you using HTML or is there some easier way?)(((
    Under the "Reply" bar at the top, there is an icon with a "quote" and a "speech" bubble, which is used to quote posts. You can either quote from a previous post, or select a line (or more) of text and click on that icon.

  • After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.

    After Security updation of Windows 7 in Boot Camp (Mac Book Pro with Retina Display) on 13-Nov-2013, Windows 7 Desktop Gadgets are not working properly.
    This is boot camp problem, because in other normal notebooks (e.g. SONY VAIO, Lenovo with Windows 7) the gadgets are working normally.
    I am attaching the screen shot of Desktop Gadgets and Security updates of Windows 7.
    Kindly solve this issue ASAP.
    Shailendra Gupta
    <edited by host>

    You are not addressing Apple, but a community of unpaid volunteers. So ASAP won't cut it. Also, you should refrain from posting personal information (like your email address) in the body of your comments, as this is part of the community usage guidelines.
    Have you reinstalled the latest Boot Camp Windows 7 drivers, just in case Microsoft overwrote some of them during the Windows 7 security update?
    If you want to communicate issues with Apple about Boot Camp and OS X, click on the link. Just don't hold your breath on receiving a response.

  • Why is "edit in Audition" greyed out in Premiere Pro and After Effects?

    Since the CC 2014 launch, the option in in Premiere Pro and After Effects to "edit in Audition" is greyed out. Right-clicking a clip in Premiere Pro doesn't have an option for Audition. I cannot send my compositions, sequences or clips to Audition for audio editing. I contacted an Adobe Support personnel earlier this evening. They suggested to go into my Mac's System Preferences and enable a root user, log out of my account, log into the root user, shut down and boot up into safe mode. None of these scenarios worked. It is still greyed out, in both user accounts.
    Is this a known issue? I even uninstalled and reinstalled Audition. Still nothing. All my Adobe apps are updated. My Mac is updated. Again, never had this issue before.
    I'd appreciate any assistance!
    Thank you!
    Cheers,
    Evan Lockhart

    I may have an answer for you, but not sure if my resolution will work for Macs.
    First, here's my system and initial info. I'm using a work computer, operating system is Windows 7. I just upgraded to Adobe CC 2014 about a week ago, and I also uninstalled the previous versions of all my Creative Cloud programs after installing the new versions (CC 2014 doesn't just update the previous version, it installs a new program and doesn't automatically uninstall the previous CC programs). Not sure if the uninstall is necessary, for this resolution to work.
    Anyway, after I installed Premiere Pro CC 2014 and Audition CC 2014, the Edit Clip in Adobe Audition command was available from the Edit menu in the Menu bar, but was disabled in the right-click menu for the sequence (for the right-click menu, it was visible, but greyed out and disabled). When I tried to use the command from the Edit menu in the Menu bar, it gave me a dialog box to fill out and it created a new folder (titled "Adobe Audition Interchange"). So, the command, when selected from the "Edit menu" obviously uses a different process than the command from the right-click menu. Anyway, I didn't want a new folder created or to fill out a dialog box, I just wanted it to behave like it used to. Basically, when I right-click the sequence and select Edit Clip in Adobe Audition from the right-click menu, it just opens Audition and the audio waveform is visible.
    I was able to resolve this and get the right-click command working by reading a couple of articles on this same issue from Adobe CC (not CC 2014) and using those to figure out how to fix this in Adobe CC 2014.
    Here's what I did:
    I had to locate my .sesx files in my system. They are NOT in the same location as they were for the previous version of CC (at least, they weren't for me). I had to use the Search command and look for .sesx extensions to locate them.
    Found them under the path C:>Users>Public>Public Documents>Adobe>Audition>7.0>Session Templates. Note that (for me), there was a folder titled 6.0 on the same level as the 7.0 folder. I selected the 7.0 folder as that folder contained the most recent set of .sesx files. I checked the 6.0 folder and those were the .sesx files from the previous version, so I deleted that folder just as a clean-up step.
    I right-clicked on one of the .sesx files in the Session Templates folder and then selected Open with from the right-click menu. The Open with dialog box displays and provides a list of programs.
    I selected Adobe Audition CC 2014 from the list of programs (you may have to browse to find it) and then selected Always use the selected program to open this kind of file. I then clicked OK to submit the configuration command and close the Open with dialog box.
    I restarted Premiere Pro CC 2014 and the Edit Clip In Adobe Audition command was now enabled on the right-click menu and was working properly.
    I wept with joy..... OK, not really, but I'm always irritated at ridiculous regression errors and a lack of thorough testing of new software versions, so I am happy to resolve frustrating issues.
    Don't know if this will help you, or if you already resolved your issue. Either way, good luck!
    ~ Jim

  • Premiere Pro and AME crashes hole iMac

    Hello together
    today I set up my brandnew iMac 27 with 3.4 ghz i7 and GeForce GTX 680XM. Now i tried to render some importet projects (stored on my drobo) and premiere pro and Media Encoder crashes a few times my hole system. I have to mention, that I did the GPU-Hack for the Cuda acceleration.
    But I tried it also without GPU-acceleration and just in this moment my hole Mac crashes again while rendering after 1-2 minutes.
    below is one of the error-reports:
    Interval Since Last Panic Report:  35 sec 
    Panics Since Last Report:          2
    Anonymous UUID:                    3ADC0CCC-8C3E-34D3-152C-289AF67D7662
    Tue Feb 12 17:26:19 2013
    panic(cpu 6 caller 0xffffff80046b7e75): Kernel trap at 0xffffff80046a3722, type 14=page fault, registers:
    CR0: 0x0000000080010033, CR2: 0x0000008000000038, CR3: 0x000000001a1a304d, CR4: 0x00000000001606e0
    RAX: 0x0000000000000000, RBX: 0xffffff803b078860, RCX: 0x0000000000000000, RDX: 0x0000008000000000
    RSP: 0xffffff839405bb40, RBP: 0xffffff839405bb90, RSI: 0x0000000000000060, RDI: 0x0000000000582d43
    R8:  0x0000000000000000, R9:  0x0000000000000001, R10: 0x0000000000fd2000, R11: 0x0000000000000246
    R12: 0xffffff8022ae3b40, R13: 0x000000000000000c, R14: 0x000000019e5da000, R15: 0xffffffffffffff9f
    RFL: 0x0000000000010246, RIP: 0xffffff80046a3722, CS:  0x0000000000000008, SS:  0x0000000000000010
    Fault CR2: 0x0000008000000038, Error code: 0x0000000000000000, Fault CPU: 0x6
    Backtrace (CPU 6), Frame : Return Address
    0xffffff839405b7e0 : 0xffffff800461d626
    0xffffff839405b850 : 0xffffff80046b7e75
    0xffffff839405ba20 : 0xffffff80046cd3bd
    0xffffff839405ba40 : 0xffffff80046a3722
    0xffffff839405bb90 : 0xffffff80046778b7
    0xffffff839405be60 : 0xffffff8004670c2b
    0xffffff839405bf20 : 0xffffff800495af43
    0xffffff839405bf50 : 0xffffff80049e060a
    0xffffff839405bfb0 : 0xffffff80046cdc03
    BSD process name corresponding to current thread: Adobe Premiere P
    Mac OS version:
    12C3103
    Kernel version:
    Darwin Kernel Version 12.2.1: Thu Oct 18 12:13:47 PDT 2012; root:xnu-2050.20.9~1/RELEASE_X86_64
    Kernel UUID: 3F93B852-872F-3DF0-BCF8-46D48024C422
    Kernel slide:     0x0000000004400000
    Kernel text base: 0xffffff8004600000
    System model name: iMac13,2 (Mac-FC02E91DDD3FA6A4)
    System uptime in nanoseconds: 1591787384351
    last loaded kext at 7017365571: com.nvidia.CUDA     1.1.0 (addr 0xffffff7f85f16000, size 12288)
    last unloaded kext at 164420432471: com.apple.driver.AppleFileSystemDriver     3.0.1 (addr 0xffffff7f868c6000, size 8192)
    loaded kexts:
    com.nvidia.CUDA     1.1.0
    com.logmein.driver.LogMeInSoundDriver     1.0.0
    com.attotech.driver.ATTOiSCSI     3.4.1b1
    com.TrustedData.driver.VendorSpecificType00     1.7.0
    com.apple.driver.AppleBluetoothMultitouch     75.19
    com.apple.driver.AppleHWSensor     1.9.5d0
    com.apple.iokit.IOBluetoothSerialManager     4.1.2f9
    com.apple.filesystems.autofs     3.0
    com.apple.driver.AppleMikeyHIDDriver     122
    com.apple.driver.ApplePlatformEnabler     2.0.6d1
    com.apple.driver.AGPM     100.12.81
    com.apple.driver.X86PlatformShim     1.0.0
    com.apple.driver.AudioAUUC     1.60
    com.apple.driver.AppleHDA     2.3.5fc12
    com.apple.driver.AppleUpstreamUserClient     3.5.10
    com.apple.iokit.IOUserEthernet     1.0.0d1
    com.apple.GeForce     8.0.6
    com.apple.Dont_Steal_Mac_OS_X     7.0.0
    com.apple.driver.AppleMikeyDriver     2.3.5fc12
    com.apple.driver.AppleIntelHD4000Graphics     8.0.6
    com.apple.driver.AppleSMCLMU     2.0.3d0
    com.apple.iokit.BroadcomBluetoothHCIControllerUSBTransport     4.1.2f9
    com.apple.driver.AppleLPC     1.6.0
    com.apple.driver.ApplePolicyControl     3.2.13
    com.apple.driver.AppleIntelFramebufferCapri     8.0.6
    com.apple.driver.AppleBacklight     170.2.5
    com.apple.driver.AppleMCCSControl     1.1.11
    com.apple.driver.MaxTranserSizeOverrideDriver     3.1.7
    com.apple.AppleFSCompression.AppleFSCompressionTypeDataless     1.0.0d1
    com.apple.AppleFSCompression.AppleFSCompressionTypeZlib     1.0.0d1
    com.apple.BootCache     34
    com.apple.driver.XsanFilter     404
    com.apple.iokit.IOAHCIBlockStorage     2.3.1
    com.apple.driver.AppleFWOHCI     4.9.6
    com.apple.driver.AppleSDXC     1.4.0
    com.apple.driver.AppleUSBHub     5.5.0
    com.apple.driver.AirPort.Brcm4331     612.20.15
    com.apple.iokit.AppleBCM5701Ethernet     3.5.0b9
    com.apple.driver.AppleAHCIPort     2.5.1
    com.apple.driver.AppleUSBEHCI     5.5.0
    com.apple.driver.AppleUSBXHCI     1.5.1
    com.apple.driver.AppleEFINVRAM     1.7
    com.apple.driver.AppleACPIButtons     1.7
    com.apple.driver.AppleRTC     1.5
    com.apple.driver.AppleHPET     1.8
    com.apple.driver.AppleSMBIOS     1.9
    com.apple.driver.AppleACPIEC     1.7
    com.apple.driver.AppleAPIC     1.6
    com.apple.driver.AppleIntelCPUPowerManagementClient     196.0.0
    com.apple.nke.applicationfirewall     4.0.39
    com.apple.security.quarantine     2
    com.apple.driver.AppleIntelCPUPowerManagement     196.0.0
    com.apple.driver.IOBluetoothHIDDriver     4.1.2f9
    com.apple.driver.AppleMultitouchDriver     235.29
    com.apple.iokit.IOSerialFamily     10.0.6
    com.apple.kext.triggers     1.0
    com.apple.driver.DspFuncLib     2.3.5fc12
    com.apple.iokit.IOAudioFamily     1.8.9fc11
    com.apple.kext.OSvKernDSPLib     1.6
    com.apple.iokit.IOSurface     86.0.3
    com.apple.nvidia.nvGK100hal     8.0.6
    com.apple.NVDAResman     8.0.6
    com.apple.iokit.IOBluetoothFamily     4.1.2f9
    com.apple.iokit.AppleBluetoothHCIControllerUSBTransport     4.1.2f9
    com.apple.driver.AppleThunderboltEDMSink     1.1.8
    com.apple.driver.AppleThunderboltEDMSource     1.1.8
    com.apple.driver.AppleHDAController     2.3.5fc12
    com.apple.iokit.IOHDAFamily     2.3.5fc12
    com.apple.iokit.IOFireWireIP     2.2.5
    com.apple.driver.AppleSMBusPCI     1.0.11d0
    com.apple.driver.X86PlatformPlugin     1.0.0
    com.apple.driver.AppleSMC     3.1.4d2
    com.apple.driver.IOPlatformPluginFamily     5.3.0d47
    com.apple.driver.AppleGraphicsControl     3.2.13
    com.apple.driver.AppleBacklightExpert     1.0.4
    com.apple.iokit.IONDRVSupport     2.3.6
    com.apple.driver.AppleSMBusController     1.0.11d0
    com.apple.iokit.IOGraphicsFamily     2.3.6
    com.apple.iokit.IOUSBMassStorageClass     3.5.1
    com.apple.driver.AppleUSBHIDKeyboard     170.2
    com.apple.driver.AppleHIDKeyboard     170.2
    com.apple.iokit.IOUSBHIDDriver     5.2.5
    com.apple.iokit.IOSCSIBlockCommandsDevice     3.5.5
    com.apple.iokit.IOFireWireSerialBusProtocolTransport     2.1.1
    com.apple.iokit.IOSCSIArchitectureModelFamily     3.5.5
    com.apple.iokit.IOFireWireSBP2     4.2.2
    com.apple.driver.CoreStorage     296.10
    com.apple.driver.AppleUSBMergeNub     5.5.0
    com.apple.driver.AppleUSBComposite     5.2.5
    com.apple.driver.AppleThunderboltDPOutAdapter     1.8.9
    com.apple.driver.AppleThunderboltDPInAdapter     1.8.9
    com.apple.driver.AppleThunderboltDPAdapterFamily     1.8.9
    com.apple.driver.AppleThunderboltPCIUpAdapter     1.2.6
    com.apple.driver.AppleThunderboltPCIDownAdapter     1.2.6
    com.apple.iokit.IOFireWireFamily     4.5.5
    com.apple.driver.AppleThunderboltNHI     1.6.3
    com.apple.iokit.IOThunderboltFamily     2.1.8
    com.apple.iokit.IO80211Family     510.4
    com.apple.iokit.IOEthernetAVBController     1.0.2b1
    com.apple.iokit.IONetworkingFamily     3.0
    com.apple.iokit.IOUSBUserClient     5.5.0
    com.apple.iokit.IOAHCIFamily     2.3.1
    com.apple.iokit.IOUSBFamily     5.5.0
    com.apple.driver.AppleEFIRuntime     1.7
    com.apple.iokit.IOHIDFamily     1.8.1
    com.apple.iokit.IOSMBusFamily     1.1
    com.apple.security.sandbox     220
    com.apple.kext.AppleMatch     1.0.0d1
    com.apple.security.TMSafetyNet     7
    com.apple.driver.DiskImages     344
    com.apple.iokit.IOStorageFamily     1.8
    com.apple.driver.AppleKeyStore     28.21
    com.apple.driver.AppleACPIPlatform     1.7
    com.apple.iokit.IOPCIFamily     2.7.3
    com.apple.iokit.IOACPIFamily     1.4
    com.apple.kec.corecrypto     1.0
    Model: iMac13,2, BootROM IM131.010A.B05, 4 processors, Intel Core i7, 3.4 GHz, 32 GB, SMC 2.11f14
    Graphics: NVIDIA GeForce GTX 680MX, NVIDIA GeForce GTX 680MX, PCIe, 2048 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738424255352D474E2D4620
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3831554738424255352D474E2D4620
    Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D534F384758334D314131363030433131
    Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1600 MHz, 0x029E, 0x434D534F384758334D314131363030433131
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xF4), Broadcom BCM43xx 1.0 (5.106.98.100.15)
    Bluetooth: Version 4.1.2f9 11046, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en1
    PCI Card: pci11c1,5901, sppci_ieee1394openhci, Thunderbolt@11,0,0
    Serial ATA Device: APPLE HDD ST3000DM001, 3 TB
    Serial ATA Device: APPLE SSD SM128E, 121.33 GB
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: Ext HDD 1021, 0x1058  (Western Digital Technologies, Inc.), 0x1021, 0x1d130000 / 8
    USB Device: hub_device, 0x0424  (SMSC), 0x2412, 0x1d180000 / 3
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x828b, 0x1d181300 / 7
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0x1a130000 / 5
    USB Device: Apple Keyboard, apple_vendor_id, 0x0250, 0x1a132000 / 6
    USB Device: USB Storage, 0x05e3  (Genesys Logic, Inc.), 0x0716, 0x1a120000 / 4
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8511, 0x1a110000 / 3
    FireWire Device: Drobo3, Drobo, 800mbit_speed
    I hope anybody can help me, it's a wedding video with deadline....

    I would venture to guess that adobe would tell you to disable the hack altogether and retest. It could be worth a shot. And I don't mean just shutting of the gpu in prefs, i mean actually disabling the pref.

  • Boot camp assitant mac pro 10.8.2

    Hi there,
    I am trying to set up boot camp on my MacBook and am completely stuck (likely due to stupidity but bear with me).
    I try to open Boot Camp Assistant but it tells me
    "You must update your computers Boot ROM firmware before using this setup assistant"
    I then carry out a check on my Boot Rom version and find this is
    Mémoire:          16 Go
      Vitesse d’interconnexion du processeur:          5.86 GT/s
      Version de la ROM de démarrage:          MP41.0081.B07
      Version SMC (système):          1.39f5
      Version SMC (support pour processeur):          1.39f5
    Système de fichiers :           Mac OS étendu (journalisé)
              Bus de connexion :           SATA
    i have 3 hdd sata and i try to install win7 on of the disk
    How can I resolve this"computer says no" issue?

    hi
    thanks for your answer
    i donwload
    Mac Pro EFI Firmware Update 1.4
    i try but the message "This update is not necessary on this computer."

  • I need to reinstall my computer, how do I deal with Premiere pro and After effects?

    Hello,
    As my question states I need to reinstall my computer (laptop) and I'm not quite sure on how to deal with Premiere pro and After effects.
    I am thinking that I need to do some sort of backup and save my projects and footage on a sepparate drive.
    If I reinstall my computer, install my creative suit production premium, and move back all of my projects and footage, won't I have to re-link every single clip?
    I am currently workning on several different projects and having to re-link everything is something I don't even want to think about, that would take me days if not weeks.
    Another option on my mind would be to use Creative cloud. I do have the free version but I have never used it even once before and I'm not quite sure what the purpose of the cloud is and if this is a way to use it.
    I have no idea how to go about this computer reinstalation without either loosing tons of work or having to re-link every single clip used.
    I am videoediting only as a hobby so I have no experience working with other people and sharing projects or the like, wich is my understanding of what the cloud is for.
    Any and all help would be grealty appreciated, I know this is probably really easy but ever since i got my Suit I haven't reinstalled, upgraded och changed my computer so I am just clueless as to how to go about this.
    I have Creative suit production premium, I also have the free Creative cloud.
    It is only Premiere pro and After effects that I am using and am worried about.
    Thank you for any help.
    -Lisa Kajupank
    (and oh, I just notice my name - umustbejoking - I think I just wrote that cause they wouldn't let me use anything else, saying it was already taken. So nevermind that haha.)
    Message was edited by: umustbejoking

    If the computer's running Mac OS X, move the cursor to the very top of the computer's screen, click on Store, and choose Authorize this Computer.
    If the computer's running Windows, press the Alt and S keys and choose Authorize this Computer, or click here, follow the instructions, click on Store in the menu bar, and choose Authorize this Computer.
    (84620)

  • I'm trying to import a sequence into premiere pro and suddenly a few sections are 'media offline'

    I'm trying to import a previous premiere pro sequence into premiere pro and suddenly a few sections are 'media offline' (it has always worked up until now).  I would be able to relink the clips but the offending ones aren't showing up in the project's clip bin. To make things worse I can't drag and drop the corresponding clips from my finder into the clips bin and then 'replace clip with' in the timeline, as the clips in the project have been renamed, and are synced up to audio (this is a 90 minute feature film).
    Can anyone help??!!

    Right click on the offline clips and select Reveal in Project.  This will call up the bin they're in, where you'll be able to relink.

  • Nikon D7000 .MOV files in Premiere Pro and After Effects CS5.5

    I recently upgraded from Production Premium CS5 to CS5.5. Initially Nikon D7000 .MOV files used in previous CS5 Premiere Pro project would not play well in CS5.5. Now .MOV files do work in both PP and AE CS5.5. Here are the steps I followed. Not recommending you follow my steps exactly, just providing info for those that are interested.
    1.       Launch Premiere Pro CS5.5 and open previous PP CS5 project, convert project to CS5.5 and rename project file as not to replace previous CS5 project file.
    a.       At this point .MOV files do not play in new project or in AE CS5.5
    b.      Close Premiere Pro and After Effect if still running.
    2.       Using Adobe Bridge CS5.5, batch rename;
    a.       Make copies of original files to new folder location while renaming file extension from .MOV to .mpg
    b.      Let Adobe Bridge finish creating all new thumbnail previews.
    c.       Leave Bridge running in background.
    3.       Launch Premiere Pro CS5.5, let Premiere finish recreating thumbnail previews if needed.
    a.       Attempt to preview existing .MOV file in project. It worked for me.
    b.      Attempt to play sequence containing .MOV files. It worked for me.
    c.       Attempt to play or modify sequence .MOV files in AE CS5.5 via Dynamic Link within Premiere. It worked for me.
    d.      Close Premiere Pro project and AE projects if open.
    4.       Create new Premiere Pro project and sequence
    a.       Import a different Nikon D7000 .MOV file not previously used or renamed.
    b.      Attempt to play this newly imported .MOV file. This worked for me as well.
    c.       The new, previously un-renamed .MOV file also worked in AE CS5.5 for me.
    I will perform additional tests but at the moment Nikon D7000 .MOV files are working for me in CS5.5 after initially performing a batch rename in Bridge CS5.5 from .MOV to .mpg and letting Bridge create preview files. Even .MOV files not renamed now work.
    An example of Nikon D7000 footage edited with Adobe Premiere Pro CS5.5, After Effects CS5.5, and Sound Booth CS5 can be seen on my blog, http://stevelandonsmyth.typepad.com/steve-landon-smyths-blog/2011/07/my-first-hd -video-shoot-with-nikon-d7000.html
    My system: MacBook Pro 17" 2.3 GHz i7 quad core, 8GB RAM, 500MB SSD
    Message was edited by: Steve Landon-Smyth

    Hello,
    I see 2 post in this thread from Todd that say they are working on a fix and it should be out soon.  One is from July, the other from August.  It is now Sept 7th and I still see no patches or fixes for any bugs.  I spent 400 dollars on an upgrade, but is this upgrade going to be supported?
    This is making me rethink upgrading to the .5's in the future.
    It is a minor bug to most, but in that sense it should be an easy quick fix. Am I wrong? Is this really a complicated issue?
    I apologize if this comes off like a rant, but thats kinda what it is.  It is not hard to batch rename files, but its a pain to have to relink all those files in PP.

  • IMac Drive Failures and Boot Camp - large install experience and question

    We have a large 24" iMac install, purchased in August of '08, 49 machines spread across 6 offices. All run Windows Vista in Boot Camp as their primary (and mostly sole) operating mode - I will be happy to explain why after we get this cleared up, but that is not the point of this question.
    We have had 11 hard drive failures, a rate of over 22% in one year. No machine has failed twice. The equipment was purchased in different groups so a bad lot is unlikely. I am aware that there is an HD failure issue with the iMac's but this seems to be extreme. Personally I've been building apples and pc's since my first apple kit, have a mac plus in a box somewhere, and am fond of these machines (as is the staff) but I've never seen a failure rate like this.
    It has been suggested that it is the use of Boot Camp that is causing these failures. While I have seen viruses over the years that can lead to hardware failure I've never seen validated (or even simply non-malignant) software have the same effect.
    Any thoughts on this? Could BC be the cause? Is this failure rate unusual? Have folks heard of similar cases? Thanks.

    no one has any thoughts on this?

  • Premiere pro and media encoder CC problem

    Hi guys,
    I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
    I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
    This is the error report, please help:
    Process:    
    Adobe Media Encoder CC [946]
    Path:       
    /Applications/Adobe Media Encoder CC/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
    Identifier: 
    com.adobe.ame.application
    Version:    
    7.2.0.43 (7.2.0)
    Code Type:  
    X86-64 (Native)
    Parent Process:  launchd [136]
    User ID:    
    501
    Date/Time:  
    2014-02-10 08:44:28.001 +0100
    OS Version: 
    Mac OS X 10.8.5 (12F45)
    Report Version:  10
    Interval Since Last Report:     
    1264 sec
    Crashes Since Last Report:      
    1
    Per-App Interval Since Last Report:  24 sec
    Per-App Crashes Since Last Report:   1
    Anonymous UUID:                 
    7E711766-8C55-00D3-811F-852F73421407
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_CRASH (SIGABRT)
    Exception Codes: 0x0000000000000000, 0x0000000000000000
    Application Specific Information:
    terminate called throwing an exception
    abort() called
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib   
    0x00007fff9483c212 __pthread_kill + 10
    1   libsystem_c.dylib        
    0x00007fff8d74ab24 pthread_kill + 90
    2   libsystem_c.dylib        
    0x00007fff8d78ef61 abort + 143
    3   libc++abi.dylib          
    0x00007fff96ff79eb abort_message + 257
    4   libc++abi.dylib          
    0x00007fff96ff539a default_terminate() + 28
    5   libobjc.A.dylib          
    0x00007fff8f49d887 _objc_terminate() + 111
    6   libc++abi.dylib          
    0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
    7   libc++abi.dylib          
    0x00007fff96ff5424 std::terminate() + 16
    8   libc++abi.dylib          
    0x00007fff96ff658b __cxa_throw + 111
    9   com.adobe.dvacore.framework  
    0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
    10  com.adobe.AMEAppFoundation.framework
    0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
    11  com.adobe.Batch.framework
    0x0000000105c0a842 AMEBatch::Initialize() + 2194
    12  com.adobe.ame.application
    0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
    13  com.adobe.ame.application
    0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
    14  com.adobe.exo.framework  
    0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
    15  com.adobe.ame.application
    0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
    16  com.adobe.ame.application
    0x0000000100056a38 main + 424
    17  com.adobe.ame.application
    0x0000000100003f74 start + 52
    ==========================
    Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

    Hi mawe81,
    Thanks for posting on Adobe forums,
    Please follow this document  http://adobe.ly/1f2EHCg
    and let us know if this fix your issue or not.
    Regards,
    Sandeep

  • Premiere Pro and Media Encoder crash while rendering H.264

    Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
    It's only while rendering H.264 - other formats seem to work fine.
    And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
    It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
    I've tried disabling CUDA and my overclock to no avail. Please help!

    On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
    I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
    Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
    I cant even
    If I find a way to fix either of these problems, I will post straight away.

Maybe you are looking for