No sound after completing Boot Camp?

Hi everyone,
I recently discovered Boot Camp, and I had a spare Windows 7 CD lying around, so I figured that I might as well give it a shot and see what happened.
Everything went perfectly fine, down the the last detail, except for one thing. There's no sound! I tried booting from Mac OS X (as opposed to Win 7, which I'd been booting off of earlier), and still no sound. Not from YouTube, not from the system, nothing. I figured this was probably because of a missing driver, but unfortunately Apple is so concerned about helping you that they don't let you help yourself, and instead of simply redownloading the driver I'm forced to put up this post. In any case, could anyone redirect me to some sort of driver download page?
Any ideas would be appreciated,
Dylan
P.S. Apple - you might want to consider adding support options other than Express Lane. Not everyone's covered under warranty, and we's like some free support if you don't mind

you have to download the windows driver from the BootCamp.
First go to Mac and Open the BootCamp and download the windows driver.

Similar Messages

Bluetooth Keyboard/Mouse/Trackpad won't automatically connect after installing Boot Camp

Hey guys!
Another peculiar thing happened to me today with my 3-week-old maxed-out 2012 iMac (other than it kernel panicking when I powered it down the other day...did I mention this was 3 weeks old?).
After installing Boot Camp which I will never do again, my iMac (on the OS X side) no longer recognizes my stock Apple Wireless Keyboard, Magic Trackpad, or Magic Mouse automatically, until I press a button on the keyboard and wait 5 seconds, click the trackpad and wait 5 seconds, or click the mouse and wait 5 seconds.
(The Windows 8 Boot Camp side pairs with the devices immediately after Windows boots, which leads me to believe that the bluetooth devices are defaulting to look for Windows.)
One of my huge fears I had when considering purchasing an iMac is that the Bluetooth devices wouldn't immediately connect. Being a power-user with former Mac notebooks and working understandably fast having owned a web development company for 8 years now and not having to worry about Bluetooth device pairing, I'd like to think this fear is substantiated. But after first use (before installing Windows 8 with Boot Camp Assistant) it functioned normally and the iMac would automatically discover my peripherals and connect them by the time time computer turned on. I also had no trouble holding the Option key on boot to select a boot device....
Now, ever since I set up Windows 8 on the Boot Camp partition and paired the keyboard/mouse/trackpad to Windows, the Mac side completely ignores the keyboard/mouse/trackpad until I click a button on each.
I'm trying to keep it together but this is raging me out.
I went into Windows, immediately unpaired the 3 peripherals from windows and now use a wired keyboard/mouse with Windows (yay, desk space!), deleted the items entirely from the bluetooth panel, then booted to Mac and did the same thing. I then re-paired the devices to the OS X side andddd...no go! Still doesn't find them automatically. I am extremely upset by this and can't seem to fix it.
To summarize, my two issues are:
A. The iMac in OS X does not automatically recognize my bluetooth peripherals until I click a button on each and wait a couple seconds for them to pair.
B. I cannot hold Option to select a boot device (or choose Windows/Mac for example) because the computer doesn't recognize the keyboard until OS X boots and I press a key.
Please...for the love of god...someone help me, and stop me from formatting my entire computer over this issue.

I don't have a logitech mouse, but is it possible that the mouse is going to sleep during the reboot, and is thus unavailable when the OS is looking for it?

Trouble restarting Mac OS after using Boot Camp

I am using Mac OSx 10.6.8 and have Windows 7 on my Boot Camp. In probably 90 percent of the times I restart my Mac OS side after using Boot Camp, my computer freezes during the startup. I usually get to my desktop screen but my desktop icons don't fully load and it freezes, or if I try and open an application in my dock, I get the spinning ball of death and I have to restart.
A co-worker suggested opening in safe mode and then going to my preferences file and looking for any .plist file that appears corrupted and then deleting it before restarting. That usually works except for the times I can't find anything that looks corrupted. Also, there are times when it starts up and my dock is back to the computer's default setup. Sometimes my clock gets set to a different time as well.
On occasion, I've sometimes restarted as many as a dozen times before things kick in correctly.
I don't have any applications in the startup menu. This thing just has major problems restarting after using Boot Camp. (I have a co-worker with the same exact issue). It's a pain when I am in a hurry after using Boot Camp.
I don't have privileges to run disk utility or do anything similar so before I take it into my IT folks, I'm wondering if this is an issue with anyone else and if there is another solution.

sorry for digging up an old thread, but what was the problem?

HT4818 after installing boot camp 4 on mountain lion " Missing operating system"

Hello
I hade a small Windows 7 partition , so after updating to mountain lion , I wanted resize win partition .
I made an image of it , then deleted win partition from utility disk , ( wrong idea )
I didn’t notice that boot camp could erase win partition , anyway I have tried several times , and always after reboot boot camp
I get the same
Missing operating system .
If I boot from dvd install win or if i boot from the boot win partition.
hd and partitions looks OK to utility disk
Any idea to fix the problem ?

I presume that you've followed the instructions for sideloading the iMac Windows drivers into your install via USB stick? (wasn't aware the EFI recognized the SD slot as storage on boot. Now i know)
I always found more success in just slipstreaming the drivers and install.xml file onto a custom Win7 DVD rather than the USB approach when trying with my Late 2009 27" iMac. The Win7 installer needs that enclosed .xml file in the driver package to tell it where to find the drivers so that they be loaded when the Win7 image extracts itself.
If you're using mountain lion, then you should be receiving the proper Win7 driver set. If you wanted to create a custom image, then you can use an ISO file, the driver package and disk utility to make something you can use. Either that or you learn what edits your install.xml file needs to point the installer properly and check it manually.
I don't know what links you have so i'll just include everything:
Installing boot camp on a Late 2009 iMac:
http://support.apple.com/kb/TS3173
Direct link to Late 2009 iMac-specific Windows drivers.
http://support.apple.com/kb/DL995
I'd try a USB stick and the iMac-specific driver set. It should steer your insolent windows installer correctly.
Hope this helps.

Lion forgets mouse settings after using boot camp on my 24" iMac. How do I retain the mouse speed setting?

Lion always forgets my mouse speed setting after using Boot Camp. How do I retain this info in Lion?

After I posted my question this thread showed up in the side bar. Too bad it didn't show up when I searched the forums prior to posting.
https://discussions.apple.com/thread/3242008?start=0&tstart=0

Folder with question mark on startup after using boot camp!!!

im getting a folder with a question mark on startup after using boot camp. it shows up for a second, then the apple logo pops up and OSX boots normally. i wouldnt be concerned except this folder with the question mark usually shows up when the computer cant find the startup disk or OS. so in fact what is happening is that my macbook cant find the startup disk for a second and then seems to find it. is anybody else having this problem. i dont like it and want to get rid of it. help!!

This is correct.
I wonder how it can be that in the System Preferences - Startup Disk - OS X volume can become "deselected" like it was... I had to re-highlight the OS X volume and all is well.
b
MBP & Mac Mini Mac OS X (10.4.6) http://www.therottenapple.net/phpbb

HT3986 i was trying to download windows 7 on mac book air 10.8.2.seems like i didnt copy my windos disk on the usb properly at the begining,so after the boot camp steps the screen is black and telle me to put the write disk.

i was trying to download windows 7 on mac book air 10.8.2.seems like i didnt copy my windos disk on the usb properly at the begining,so after the boot camp steps the screen is black and telle me to put the write disk.
eventually i made a coorect usb windows 7 and put it back to continue as it was saying so,but there is no change and the screen still is dark and says no bootable disk ,insert.
how to solve the problem?

Right now I have 6 different systems installed. Windows XP, 7, and 8 plus Linux Mint, Commodore, and OS X Snow Leopard (for old times sake), all running on Mountain Lion.
I recommend reading the user manual as it greatly helps getting through the steps, however an intuitive person should pick it up fairly easily.
Thanks to BobTheFisherman for the link.
There are other ways to get Windows on a Mac but I'm a big fan of open-source software.
Give it a try. You might like it or it may not be your cup of tea.

Slow boot up after removing boot camp

I removed boot camp aftering realizing that I barely use it and hoping that the boot up time would be as quick as when I bought my mac a year ago. However, the boot up time is just as slow even after removing boot camp. I have gone into system preferences and chosen mac ox as the primary disk but nothing happens. Please help!

Check the setting in the Startup Disk pane of System Preferences.
(54095)

Windows 8.1 Not Working Properly after Updating Boot Camp Drivers to 5.1

Hi all!
Recently I had a problem with the sound in Windows 8.1 using BC v5. That problem was resolved by updating the Boot Camp Drivers to 5.1. Now I've more problems than before.
1. Some service are not loading at all at the startup (which did before)
The Boot Camp service is not loading automatically at startup, other Windows Services are not loading at the startup after updating the Boot Camp Drivers (Windows Update)
2. Microsoft Office cannot verify license for the product.
This problem is due to the services that won't start automatically. I can't even do a repair of MS Office 2013... Even though it's a legal version of MS Office.
There are many many more problems I think... I just haven't discovered them yet which is very very annoying. When I was using Windows 8.1 with the Boot Camp Drivers version 5 there were few bugs than now...
Please is there any notice of these errors? Or am I the only one who is experiencing these errors??? Please give me some answers!
Thanks in advance!!

I updated them by downloading the zip file from the Apple site...
I've just updated Mac OS X and it seems that this was the solution... Everything works fine! (For now)

Windows 8 crashes and with the error "kernel_security_check_failure" after installing Boot Camp drivers.

Hi!
I've got a new 27" iMac (late 2013), and I was going to install Windows 8.1 (64-bit) to be able to play a few games.
Everything went smoothly (installed normally via Boot Camp Assistant), and after the Windows setup, the Boot Camp drivers needed to be installed. After this, the computer rebooted, but crashed at a blue screen with the error called "kernel_security_check_failure".
It rebooted a few times on its own, but after a few times, I got some options, and I chose to "refresh" the Windows 8 install, meaning it would reset the install while keeping my files (even though I didn't have any, as I never got to use it). This took some time, but it worked, and it booted into W8.
The Boot Camp drivers had been removed though, so I had to reinstall them. After they had reinstalled, the computer rebooted and the same blue screen with the same error hit me.
Something tells me that some of the BC drivers are messing things up. I can't find any information on this elsewhere.
Would it be possible to install only selected drivers, to eventually find out which driver is causing the problem?
All help is greatly appreciated!

I finally gave up, reloaded everything, this time, using WIn 8.1 Pro, not Enterprise. After I did the updates, patches, Norton 360, shut computer down and connected the external drives, and booted up...and got the BSOD. This time, I went to Microsoft and downloaded the Windows Debugger, and think I may have found the problem...NORTON!
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Am conrtacting them, but, here's the Debugger output:
Microsoft (R) Windows Debugger Version 6.3.9600.17029 AMD64
Copyright (c) Microsoft Corporation. All rights reserved.
Loading Dump File [C:\Dump\MEMORY.DMP]
Kernel Bitmap Dump File: Only kernel address space is available
************* Symbol Path validation summary **************
Response                         Time (ms)     Location
Deferred                                       SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Kernel Version 9600 MP (8 procs) Free x64
Product: WinNt, suite: TerminalServer SingleUserTS
Built by: 9600.17085.amd64fre.winblue_gdr.140330-1035
Machine Name:
Kernel base = 0xfffff802`0f87e000 PsLoadedModuleList = 0xfffff802`0fb482d0
Debug session time: Tue Jun 17 00:48:52.131 2014 (UTC - 6:00)
System Uptime: 0 days 0:03:09.864
Loading Kernel Symbols
Loading User Symbols
Loading unloaded module list
*                        Bugcheck Analysis                                    *
Use !analyze -v to get detailed debugging information.
BugCheck 139, {3, ffffd0002852d3e0, ffffd0002852d338, 0}
*** ERROR: Module load completed but symbols could not be loaded for SYMDS64.SYS
*** ERROR: Module load completed but symbols could not be loaded for SYMEFA64.SYS
Probably caused by : SYMDS64.SYS ( SYMDS64+71be6 )
Followup: MachineOwner
6: kd> !analyze -v
*                        Bugcheck Analysis                                    *
KERNEL_SECURITY_CHECK_FAILURE (139)
A kernel component has corrupted a critical data structure. The corruption
could potentially allow a malicious user to gain control of this machine.
Arguments:
Arg1: 0000000000000003, A LIST_ENTRY has been corrupted (i.e. double remove).
Arg2: ffffd0002852d3e0, Address of the trap frame for the exception that caused the bugcheck
Arg3: ffffd0002852d338, Address of the exception record for the exception that caused the bugcheck
Arg4: 0000000000000000, Reserved
Debugging Details:
TRAP_FRAME: ffffd0002852d3e0 -- (.trap 0xffffd0002852d3e0)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=ffffe00059c129f0 rbx=0000000000000000 rcx=0000000000000003
rdx=ffffe0005718d2a0 rsi=0000000000000000 rdi=0000000000000000
rip=fffff8020f9e8cdb rsp=ffffd0002852d570 rbp=0000000000000000
r8=0000000000005aa0 r9=00000000000007ff r10=ffffd00066cc8000
r11=ffffe00059963040 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei pl nz na pe cy
nt! ?? ::FNODOBFM::`string'+0x682b:
fffff802`0f9e8cdb cd29            int     29h
Resetting default scope
EXCEPTION_RECORD: ffffd0002852d338 -- (.exr 0xffffd0002852d338)
ExceptionAddress: fffff8020f9e8cdb (nt! ?? ::FNODOBFM::`string'+0x000000000000682b)
   ExceptionCode: c0000409 (Security check failure or stack buffer overrun)
ExceptionFlags: 00000001
NumberParameters: 1
   Parameter[0]: 0000000000000003
DEFAULT_BUCKET_ID: LIST_ENTRY_CORRUPT
BUGCHECK_STR: 0x139
PROCESS_NAME: System
CURRENT_IRQL: 2
ERROR_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_CODE: (NTSTATUS) 0xc0000409 - The system detected an overrun of a stack-based buffer in this application. This overrun could potentially allow a malicious user to gain control of this application.
EXCEPTION_PARAMETER1: 0000000000000003
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
LAST_CONTROL_TRANSFER: from fffff8020f9ddae9 to fffff8020f9d1fa0
STACK_TEXT:
ffffd000`2852d0b8 fffff802`0f9ddae9 : 00000000`00000139 00000000`00000003 ffffd000`2852d3e0 ffffd000`2852d338 : nt!KeBugCheckEx
ffffd000`2852d0c0 fffff802`0f9dde10 : ffffe000`59c8cc40 00000000`00000000 ffffe000`54b71040 fffff800`1d6d40b6 : nt!KiBugCheckDispatch+0x69
ffffd000`2852d200 fffff802`0f9dd034 : 00000000`00000000 00000000`00000000 ffff6d2d`50094127 fffff802`0f81458f : nt!KiFastFailDispatch+0xd0
ffffd000`2852d3e0 fffff802`0f9e8cdb : ffffc000`061df4e0 ffffc000`061df4e0 ffffc000`061dfbf8 00000000`00000000 : nt!KiRaiseSecurityCheckFailure+0xf4
ffffd000`2852d570 fffff800`1d7a0be6 : ffffe000`59e10120 fffff800`1d794388 ffffe000`54dfe9c8 fffff800`1d735f7c : nt! ?? ::FNODOBFM::`string'+0x682b
ffffd000`2852d5a0 fffff800`1d7a54e2 : ffffc000`061df4e0 ffffc000`061dfbf8 ffffc000`061df550 fffff800`1d7367ea : SYMDS64+0x71be6
ffffd000`2852d5d0 fffff800`1d737f20 : ffffc000`061df378 ffffc000`061dfbf8 00000000`00000000 ffffc000`05a9bf18 : SYMDS64+0x764e2
ffffd000`2852d620 fffff800`1d73e171 : ffffc000`051e6a88 ffffc000`05a9bf18 ffffc000`05a9bf18 ffffe000`5988cb00 : SYMDS64+0x8f20
ffffd000`2852d650 fffff800`1d782027 : ffffc000`061ea018 00000000`00000000 ffffe000`58409008 fffff800`1d794388 : SYMDS64+0xf171
ffffd000`2852d680 fffff800`1d79af21 : ffffc000`061ea018 ffffd000`2852d8c9 ffffe000`58409008 00000000`10000004 : SYMDS64+0x53027
ffffd000`2852d6c0 fffff800`1d9a3bb3 : ffffe000`58409078 fffff800`1d98b3e8 ffffe000`58409008 ffffd000`2852d8c9 : SYMDS64+0x6bf21
ffffd000`2852d6f0 fffff800`1d9a91fa : ffffe000`5840a1a8 ffffe000`58409008 00000000`00000000 ffffe000`00000000 : SYMEFA64+0xe9bb3
ffffd000`2852d720 fffff800`1d9ae015 : 00000000`00000000 00000000`00000000 ffffd000`2852d8c9 ffffe000`58a10e60 : SYMEFA64+0xef1fa
ffffd000`2852d760 fffff800`1d9adf4c : 00000000`01820201 ffffe000`58a10e60 ffffe000`58a10e60 ffffe000`58a10be0 : SYMEFA64+0xf4015
ffffd000`2852d790 fffff800`1d9b294c : ffffe000`59e0a150 ffffe000`58a10e60 ffffe000`5988ca80 ffffe000`58a10e60 : SYMEFA64+0xf3f4c
ffffd000`2852d7c0 fffff800`1d9a2435 : ffffd000`2852d8a0 ffffe000`599a4010 ffffd000`00000000 ffffe000`59e0a010 : SYMEFA64+0xf894c
ffffd000`2852d7f0 fffff800`1d6d528a : 00000000`00000000 ffffe000`59e0a070 ffffe000`5604e300 ffffe000`58a10e60 : SYMEFA64+0xe8435
ffffd000`2852d820 fffff800`1d71bf76 : ffffd000`2852d960 00000000`00000000 ffffe000`5604f900 ffffe000`571dab10 : fltmgr!FltpPerformPreCallbacks+0x31a
ffffd000`2852d930 fffff800`1d6d413a : ffffe000`57170dd0 ffffe000`571dabd0 ffffe000`59cf18c0 fffff802`0fd411a7 : fltmgr!FltpProcessShutdownRequest+0x122
ffffd000`2852d9b0 fffff802`0fbf7518 : ffffe000`57170dd0 00000000`00000001 ffffe000`571dabd0 fffff802`0fb54a90 : fltmgr!FltpDispatch+0x13a
ffffd000`2852da10 fffff802`0fbf7273 : 00000000`00000001 00000000`00000000 00000000`00000001 00000000`00000000 : nt!IopShutdownBaseFileSystems+0xb8
ffffd000`2852da90 fffff802`0fbfb722 : fffff802`0fbfb4b0 00000000`00000000 ffffe000`59963040 ffffe000`59963040 : nt!IoShutdownSystem+0x127
ffffd000`2852db10 fffff802`0f8d1adb : fffff802`0fbfb4b0 ffffd000`2852dbd0 00000000`00000000 ffffe000`59963040 : nt!PopGracefulShutdown+0x272
ffffd000`2852db50 fffff802`0f94d794 : ffffe000`59965800 ffffe000`59963040 ffffe000`59963040 ffffe000`54b71040 : nt!ExpWorkerThread+0x293
ffffd000`2852dc00 fffff802`0f9d85c6 : ffffd000`66c40180 ffffe000`59963040 ffffe000`59965800 00000000`00000000 : nt!PspSystemThreadStartup+0x58
ffffd000`2852dc60 00000000`00000000 : ffffd000`2852e000 ffffd000`28528000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x16
STACK_COMMAND: kb
FOLLOWUP_IP:
SYMDS64+71be6
fffff800`1d7a0be6 33d2            xor     edx,edx
SYMBOL_STACK_INDEX: 5
SYMBOL_NAME: SYMDS64+71be6
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: SYMDS64
IMAGE_NAME: SYMDS64.SYS
DEBUG_FLR_IMAGE_TIMESTAMP: 51f84c44
FAILURE_BUCKET_ID: 0x139_3_SYMDS64+71be6
BUCKET_ID: 0x139_3_SYMDS64+71be6
ANALYSIS_SOURCE: KM
FAILURE_ID_HASH_STRING: km:0x139_3_symds64+71be6
FAILURE_ID_HASH: {bf9be68b-5f04-08d4-3152-3d420dc362f6}
Followup: MachineOwner

BSoD after installing Boot Camp 3.0 into Win 7 Pro x64

I installed Windows 7 Professional x64 into the partition created by the Boot Camp Assistent (3.0.4), the whole windows setup worked just fine and finished as usual. Then, after the final reboot to finish the windows setup I installed the Boot Camp software and drivers from my 10.6 DVD. The setup finished and promted me to restart the system - no problems so far. But just as Windows rebooted and was about to show the desktop, it crashed with with a BSoD providing no precise imfomation as to which driver could have caused it.
I have re-installed Windows and Boot Camp about ten times now, and no matter what I tried, the result always remained the same.
I booted in Safe Mode and tried to update to Boot Camp 3.1 and 3.2, but near the end of the setup it shows that Keyagent and MacHAL could not be installed (Setup said the Updates were installed successfully though).
When I rebooted Windows normally it was still the same - BSoD just when the desktop was about to be shown.
I have absolutely no idea what causes this. The BSoD only shows a hex-code, but I wasn't able to write it down since it disappears too quick and I don't know how to 'pause' using the integrated keyboard.
• Computer is a MBP mid '09 running 10.6.8 with all updates
• Boot Camp version is 3.0
• Provided drivers on the Snow Leopard DVD are for XP and Vista/Vista x64 only, but since the setup completes without any error message I assume those Vista drivers are OK
• Windows - as stated above - is a 7 Professional x64
So, does anyone have an idea what might be the problem and/or how to solve this issue?
If any possibly useful information missing please ask and I'll add them.
Thanks in advance

Well, at least my Windows won't boot after renaming them to *.sys.old.
But anyway, these two drivers aren't the cause, instead it's actually BootCamp.exe and/or the trackpad or keyboard drivers.
This guy had the exact same problem and the 'solution' was to disable BootCamp.exe.
https://discussions.apple.com/message/10301692#10301692
I finally managed to install all Boot Camp updates but still nothing has changed; as soon as I launch BootCamp.exe or change settings for the trackpad the system crashes.
It seems I have two options now: Use Windows without "Tap to click", "Secondary Tap" and modified keyboard settings, or find suitable trackpad/keyboard drivers.
Speaking of which, is there any chance to get Boot Camp drivers for Win 7? Maybe this would solve my problem since I only have Vista/x64 drivers which I used for Win 7.
Thanks!

No audio on OS X side after installing boot camp

After installing Leopard and then boot camp (with Windows Vista) I find that audio doesn't play through the external speakers on the mac side of my computer. I can hear a faint, tinny sound on the internal speaker. Strangely, audio plays fine when running the Vista side.
Has anyone else experienced this problem? I understand boot camp replaces an audio driver. I'll report this to apple support when I manage to get through.

Thanks for the quick response.
Yes, did that. Hardwire connection.
Tried Network Utility - pinged my router at 192.168.1.1 - no answer.
Also used a Network Setup Wizard (but don't know how I got there) and was unable to do a setup - it wanted a DHCP Client ID - - and my ISP (three different techs) told me that they don't use a client ID.
Also called Apple support - I've had this mini for a little over 100 days, so he wanted $49 for one time support or $149 for Apple Care. He gave me several hints and directions to try, and also made an appointment for me at my local Apple store. Buy I'd much rather solve it here and learn a little about Macs and OS X.

Internal Microphone doesn't work (after installing Boot Camp 3.1)

I have installed Boot Camp 3.1, and after this installation, my internal mic doesn't work (ONLY IN WINDOWS XP).
I tried to fix the problem with several manners (hardware test in CONTROL PANEL / SOUND .../ VOICE TAB / VOICE RECORDING; reinstalling drivers and hardware etc), but I can't get success (for example, the test results: SORRY, NO SOUND IN MIC...).
On the other hand, when I boot as Mac (Snow Leopard), I can use the mic (in skype, for example), without problem.
I note that ear plug (connector in the back of the iMac) doesn't work too.
Somebody can help me in this case ?
Regards
JGFilho

i got a macbook pro, 2 weeks ago, the 2.53Ghz unibody aluminium, the desing of this mac is great even tough the system specs are really low for the price actually, im happy with it(the hardware)...
The only reason i got this is cause apple claims to support windows, i like Mac OS, but i work on windows i need it... if theres no windows capability in mac i wouldnt ever buy one, so this issue is really bothering me A LOT. my impresions about apple are changing after seing this topic filled with questions and not a single moderator answer, go and check a logitech forum and see how they take care about user problems.

2010 Mac Pro Boot Camp - Refuses to boot Windows after installing Boot Camp drivers

Hey all,
I have a quad 3.2Ghz 2010 Mac Pro with a Radeon 5870 and 8 GB RAM.
I have 2 10000RPM WD Raptor drives, the first drive is my Lion boot drive. The 4th bay contains the second Raptor which has Windows 7 Ultimate 64 bit installed. Bay 2 has Time Machine, bay 3 has a Windows backup drive.
I had first installed Windows and the Boot Camp drivers a few months ago and everything was humming along smoothly. Monday I tried to boot into Windows and it crashed immediately after the black Booting Windows screen started to change to the login window. This happened repeatedly. Nothing changed on the system that I am aware of. Whenever I tried to boot windows again, it booted into the repair mode. That did not seem to work because after running the repair it would still not boot.
So I did what is usually required of Windows, and that was to reinstall. I reformatted the hard drive, ran Boot Camp assistant, and started the install.
Everything was peachy so far, so I tried to reinstall the Boot Camp drivers (4.0). Did a reboot. Same problem. Doh!
So I did ANOTHER reinstall, and everything was fine. But this time I tried to install the Boot Camp drivers off the os install disc that came with my Mac (3.1). Still no go!
So finally I did my third reinstall and after that I did not install Boot Camp drivers. However, I did load up the CD and individually installed drivers for the Apple Mouse, Apple Keyboard, Cinema Display, etc. No problems whatsoever. Everything is actually still humming along fine.
So it looks like running the full Boot Camp install for some reason no longer works. Which means I am missing the Apple Boot Camp control panel, but that's not really a big deal. Althought it's quite annoying to not have the functionality of the special Mac keyboard keys like volume control, etc.
Has anyone run into this? I thought it might be a hardware problem but my Mac OS X OS exhibits no problems whatsoever.
Thanks!

Thank you to The hatter.
I have a Mac Pro mid 2010 with a SSD and several internal hard disks. For some time I was trying to install Windows 7 on a fresh boot camp volume on a new WD 7200rpm 1TB hard disk. It was taking hours to install, and then I had a series of failures to reboot that proved permanent. The Window Repair utility would come up and took forever to repair the volume - but failed to actually do so, requiring completion reinstallation of the bootcamp volume. This occurred three times, between 1 day and 2 months after installation. I had already moved the Windows drive in to drive slot 1 of the Mac Pro.
Eventually I gave up and installed boot camp on a secondary partition of the SSD. This worked fine, however is limited in capacity. So yesterday I thought I would try to install Windows on the hard disk again. The Windows installer took many hours to do its thing, and eventually a message came up that the installation had failed.
I took your tip about possible hard disk failure, and ran Techtool Pro surface scan. It turns out that there are lots of bad blocks being reported. According to Micromat's documentation, the bad blocks being reported are those that may be in critical areas of the disk that cannot be mapped out. They recommend low level reinitialisation (with zeros) to map out the bad blocks, if possible. I am now running Apple's Disk Utility to do this, and fingers crossed that this reinitialisation succeeds, or I will have to replace the drive.

Vista Blue Screen after Successful Boot Camp installation (32 and 64 bit)

OK so there are a number of people with issues relating to the BSoD after a successful (or not) implemetation of Bot Camp and Windows XP and/or Vista. One of the identified problems relates to the NVIDIA GEforce 9600m GT display driver which crashes out AFTER windows performs its update routine.
Having removed and installed the partition (to ensure a clean install each time), the inescapable conclusion is that the NVIDIA driver is to blame for the crash dump, but it is one of the many MS updates that is the root cause of the failure. If you do a clean install of Vista 32 or 64 Ultimate and install the Boot Camp 2.1 (build 1256) and DO NOT allow updates, the system is not only stable, it runs like a train!
I have Contacted AppleCare about this (as my new MBP is only a few days old) and they have not even heard of the problems. NVIDIA have obviously got issues with something as the driver has been updated to a BETA on their web site, but this will not work on a Mac as it cannot seem to find the hardware to allow the update to complete.
If (like me) you have bought an MBP for support issues for both Mac and Windows users, this is a showstopper and one that is about to cause me to ask for my money back. So far, the nice shiny and new MBP is back in its box pending a 140 mile trip back to Exeter from whence it came.
SHARK!

Boot Camp was a response to public challenges at the time to see who could find how to install Windows on a Mac - which is totally okay thing.
Then you want Apple to do more than any normal PC vendor selling a laptop where people have to do things like deal with BIOS, drivers and all the things you have had to deal with, for Windows.
I'm not disagreeing, let alone arguing, I agree that hardware abstraction layer type stuff Apple would need to do. But I don't think Apple needs to do more than get Windows installed. Drivers, AV, and all the stuff that comes with Windows doesn't change. But it should not BSOD when you install something you are told you need.
I wouldn't be surprised though to see Windows 7 eventually support Apple hardware out of the box so to speak.
Cookie cutter answers are part of today's customer experience "level one" is no level at all, but a lot of times - and it takes a lot of work - to translate feedback and problems into "cook book" before you get to the troubleshooting (level 2 and above).
Which is why I read sites like MacIntouch; subscribe to MacFixit (tons of articles on a CD along with shareware). And books.
Nvidia has terrible drivers in OS X on the Mac Pro (workstation) while ATI has had very good drivers and OpenGL support.
I prefer to have more choice and freedom when it comes to drivers. As for engineering and how things get qualified (use to see even SCSI hard drives had to be qualified for both the OS; the controller to be used; driver version; firmware; etc).
What I see is the first shipped BIOS/EFI firmware on any device or system is not the one you want.
Back in the 70's I was introduced to "bleeding edge" but we would get premiere on-site support if we were willing to install, adopt, some new IBM service, software/hardware. And sometimes we were there on Sunday on holiday weekends.
One person just could NOT after doing everything under the sun, get Adobe CS4 to install on their new $5000 Mac Pro 2009. Got a new system, worked perfectly.
In 2008 Early Mac Pro, most all systems would freeze on wake from sleep. Took two months before an EFI update was issued that cured the problem. There is/was also a problem with "inrush current" and PSU.
I had Blue Screen with Vista. Repeatedly.
At first I thought it was a new MICROSOFT 4000 keyboard.
Later I wondered if it was my Apple OEM Nvida 7300GT (and some are failing but it worked in OS X) so I bought 2nd, a PC 8600GTS.
And pull 3rd party PCI Express controllers (FW800, SATA 1x, SATA 8x cards).
Came away and thought "oh, it was the 3rd party card" when that seemed to work.
Around the same time I had bought a new WD Caviar 750GB SATA drive.
It was that drive that would cause problems with Vista after the install.
I thought it was something in Microsoft Windows Update that was causing my personal ****, not my equipment. And MS for their drivers. Somebody else's.
And mind you, I would go through install half a dozen times, try installing Boot Camp before updates, after updates, not at all, add AV software.
I finally -- after a full year -- learned a lot (don't learn from things just working and I still say it has always been "Plug and Pray" PnP ) things work. I know the frustration and aggravation and the wish that things were different somehow.
The BSODs that I got were not from Apple Boot Camp. I even ran my system w/o Boot Camp for six months. And this time, with Win7, everything worked fine, wake, sleep, networking, no need for Apple drivers. At all.
I hang out on a forum where people build their own, X58 board, Intel Core i7, eVGA graphics. And how to get even DDR3 to work, and then how to get the most out of and push it to the extreme, then throttle back a notch.
The nice thing about that is you learn from it, like you do from racing and sports, to build a better mousetrap.
Nvidia is bleeding. Even as they and ATI want to stay on leading edge. Intel is contracting (even as they have their best cpu technology ever coming out) and costs that should go into R&D may be harder to "justify" or all the prototype programmers engineers and testing labs. Everything is more commoditized than ever.
Bottom line: I have Leopard 10.5.6. It has Boot Camp 2.1.2 version, later than the 2.1 download. And there has not been a single update posted online. But my original Leopard DVD 10.5.0 has the SAME contents packaged as 2.0 as were in the 1.4 Beta. I spend $129 for a new DVD to get the latest drivers. Make sense?? of course not.
Oh, and my Mac with 64-bit hardware, cpu, the EFI BIOS is 32-bit so no official support from Apple to install BC 2.1.2 or use Vista 64-bit. Snow Leopard will be 64-bit kernel, require and enforce 64-bit drivers. Should be interesting. Because technically, and logic, would say I don't have a true 64-bit BIOS environment.
Got an iMac? not supported with 64-bit. MacBook 2008 had 64-bit support, but not the "Late 2008" there you need MacBook Pro. And yet everyone wants to address more than 2GB (Apple EFI32 allows access to 3.3GB on some, 1.9GB on others, and in my Mac Pro? limited to 1.9GB memory in Windows.... so you know I don't want to run a Xeon workstation in Windows 32-bit.

No sound after completing Boot Camp?

Similar Messages

Maybe you are looking for