Skip to main content

Audio in Windows 7 with Boot Camp on Apple MacBook

I’ve been running Windows 7 Ultimate (32 bit) on a white Core2Duo MacBook for quite some time now but could never get the audio working and there was a red light coming out of the Aux port.  I was had used the Snow Leopard Boot Camp drivers on the CD and this had worked for most of the other devices.  Any drivers I downloaded and installed from the web failed to work.  I got a great tip for dealing with this problem on: http://discussions.apple.com/thread.jspa?threadID=1860928&tstart=0  The key seems to be running the installer Administrator in Vista compatibility mode…

  • Insert the Snow Leopard install CD
  • Browse to \Boot Camp\Drivers\IDT SigmaTel
  • Right-click the “SigmaTelSetup.exe” file and choose “Troubleshoot compatibility”
  • Choose “Troubleshoot program” choose the first tick box and hit “Next”
  • Choose “Windows Vista” and then “Next”
  • Choose “Start the program…” and then “Next”
  • The driver will now install, click on the progress balloon  on the bottom right of the screen and click the hyperlink to skip Windows Update driver checking
  • When the process completes you’ll just need to click the option to say it completed successfully and then hit “Close”.
  • Then choose to restart the computer

This did the trick for me anyway, I hope it does for you.

Comments

Popular posts from this blog

Resolve WSUS Server issue that gives "Cannot save configuration because the server is still processing"

This is a pretty infuriating error and can sometimes crop up as a result of running a "wsusutil reset" command. First of all, give the server some time, and then a bit more...  but you've probably already done this. These steps may help to resolve the situation: - Install Microsoft SQL Management Studio (free download) - Run SQL Management Studio and start to connect to the WSUS database - Enter this in the "Server Name" box:  \\.\pipe\MICROSOFT##WID\tsql\query - Expand the "Databases" tree - Right-click on "SUSDB" and choose "New Query" - Paste this query in:     UPDATE tbSingletonData     SET ResetStateMachineNeeded = 0 - You should see a message like "1 row affected", which is good - Quit SQL Management Studio - Open "Services" and restart the "WSUS Service" - Now, open WSUS

Logon Scripts in Group Policy not running

Problem  Was having difficulty with a logon script I had created and was deploying to users via Group Policy. The script was to customise printer settings for certain users. But it just wasn't running when the users would logon to their PCs. The GPO was applying properly, and I could run the script manually without issue. Cause It turns out that it was happening because, by default, logon scripts don't run for 5 mins after logon occurs on a Windows client PC. Solution This can be adjusted by setting the "Configure Logon Script Delay policy" to "Enabled" and then configuring a better delay. Note: if this policy is set to disabled or not configured, the default delay of 5 mins will apply. I initially set this delay to "0" but found that wasn't successful.  Perhaps the script needed a small delay. So I set it to "1" (1 minute) and it worked nicely. I must also note that during the troubleshooting process, I read many recommendations to e...

Convert Ruckus AP from Unleashed to ZoneDirector-managed

Here is the method to convert a Ruckus Unleashed AP to one which can be managed by a Ruckus ZoneDirector controller: - Login to https://support.ruckuswireless.com/ - Click "Downloads" - Choose the correct product, e.g. Ruckus R550 - Choose a "standalone" version along the lines of 118.2.0.0.875.bl7 or something similar - Agree to terms and download the software - Connect to the AP's IP address - It should open the setup wizard, showing "Unleashed Installation" - Click "Local Upgrade" - Choose the firmware image file you just downloaded - It will upload, process, and then be ready for upgrade when you click "Yes" - After this, the ZD should detect the new AP - The new AP will then need to be approved - The new AP will then be upgraded to the correct software by the ZD - The new AP will then reboot and should be ready to use - Don't forget that, for the ZD to even detect, let alone manage the new AP, it must have enough licenses