Wireless Not Working under Boot Camp

Wireless works with Leopard and with VM Fusion, but when I use boot camp, it won't connect to DHCP. Tried manual ip address also, but no internet connectivity and can't ping my network.
Wired ethernet works fine with Boot Camp.

You may want to try posting your question over in the Boot Camp discussions:
http://discussions.apple.com/category.jspa?categoryID=237

Similar Messages

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.

Magic Mouse Not Working with Boot Camp.

Hi All,
I have a wired issue here. I installed Windows XP on my iMac 27" using bootcamp and all worked fine till one day my Magic Mouse stopped working in Windows. Now the funny part is windows is able to detect my mouse and says that the device is working normally but the green light under my mouse is OFF. No matter what i try i cannot get it to come on. But the moment i boot to Mac OS X the mouse works perfectly fine. My Apple Wireless KB works just fine in Windows. A USB mouse also works fine. I have also installed Parallels on my Mac and when i boot into the Windows partition using Parallels the Magic Mouse works fine. Any idea as to whats going on here.?
John.

I have a new (July 2009) iMac24 and neither the wireless mighty mouse nor keyboard work with Boot Camp XP Home Edition SP3. They install OK with the Bluetooth control panel, but then after five or ten seconds, drop out of the control panel and have to be discovered again. I spent two hours today with a Mac support expert, but no joy. We both gave up. It seems the wireless mouse/keyboard does not work with Boot Camp. If anyone hears of a solution, please let me know.

Mouse not working with Boot Camp after 10.5.7 update

I upgraded to 10.5.7 recently, and now my mouse doesn't work on Boot Camp. It doesn't seem to register, and I can't move the pointer. I tried this with two mice that worked just fine on the Mac OSX side. Any ideas? Has anybody else noticed this?

I have a new (July 2009) iMac24 and neither the wireless mighty mouse nor keyboard work with Boot Camp XP Home Edition SP3. They install OK with the Bluetooth control panel, but then after five or ten seconds, drop out of the control panel and have to be discovered again. I spent two hours today with a Mac support expert, but no joy. We both gave up. It seems the wireless mouse/keyboard does not work with Boot Camp. If anyone hears of a solution, please let me know.

I have wireless mouse does not work with boot camp

i have wireless mouse does not work with boot camp

Did you install the correct driver for your Windows version? Are you saying the mouse does not work in Windows after Windows is installed?

ISight is not working with boot camp

Hi,
I have a Macbook Pro and very satisfied with it. Formerly I worked with Windows XP, so I decided to buy a Macbook and use boot camp. Everything was fine. In my enthusiasm I bought the LED cinema display. Very good display but the iSight camera is not reliable working with boot camp. There is no driver available. Sometimes the camera is recognized as video device but mostly not. When the camera is not recognized then there is a yellow exclamation mark in the device manager. I don't know what to do. Is anybody working with boot camp and the iSight build in the LED cinema display? And what driver do you use? Hopefully I get some help here. Everything is working convenient except this issue.
Thank you, Frank

Sorry, I think I mixed some things. I tried several contellations to find out what is going wrong. The iSight is woking with my MacBook (and boot camp). But it is not working with other Laptops or PCs (all with Windows XP). It is working really rarely but not reliable and not replicatable. In all cases I tried only the USB connector from the LED cinema display. Audio, micro and hub is always working without problems. The iSight driver delivered with the Macbook is not working (only with the Macbook itself). If I had known this before I think I would buy the display although. The display is great. But it is a pity that the iSight is not working when you do not use Apple hardware. May be I will buy the Mac Pro in one or two years when I need a new PC. Perhaps someone can answer if Windows XP is working without problems on a Mac Pro? And is the iSight build in the LED cinema display working (Mac Pro and boot camp)?
Frank

Mic is not working on boot camp Win XP SP3

Hi everyone,
I have MacBook Por 2009 , 13-inch. I working on Boot camp 2.2 Win XP SP3 , but the Mic is not working .
I have searched many websites to find a fix this problem, but I can not find a solution
Please help me to fix that.
Thanks

Hi..yeah..can anyone help on this please..
im also experiencing the same problem..ive also tried realtek R249..
thanks...

Wireless keyboard not working with Boot Camp

I have a brand new 15" Macbook Pro. I need to run Windows for work so I installed Boot Camp and Windows 8.1. I have a HP wireless keyboard with a USB dongle. It will not work at all. Windows recognizes that I've plugged in the dongle but the keyboard won't work at all. It's a brand-new keyboard and the batteries show full charge. All drivers look good in device manager. When I went thru the Windows troubleshooter, which is typically worthless, it said something about the dongle being USB 2.0 and the Mac's USB is 3.0. But shouldn't it be backward compatible? It has no problem with my old wireless mouse with a USB dongle.
I also notice a significant difference in the clarity on my dual external monitors with Windows instead of OSx. The colors aren't as sharp and the text isn't as clear - kind of fuzzy. Is that just how it goes with boot camp, or is there anything I can do, like maybe an upgraded driver, to get the same clarity on my dual monitors with Windows like I get with OSx?
Any help is appreciated.

Unfortunately I can't turn off Bluetooth in Win 8.1. I go to the page where i should see the slider and the page just spins and spins. I thought my install might be hosed so I blew it away and did a fresh boot camp install. Still no joy; BT still spins - and I still can't connect to the USB keyboard. I can plug the dongle in and see it in devices, and it says it's ready to go but the keyboard doesn't work. It's brand-new and has worked on a Windows box so I know it's not a bad keyboard. Maybe time to go back to a Windows box and ditch boot camp?

IMac with 3TB Fusion drive will not partition under Boot Camp

I have a 27" iMac with a 3TB Fusion drive and I am using 10.8.4.
I am trying to install Windows 8 Pro with Boot Camp. Everything starts well enough, but once I get to "Create a Partition for Windows" and setting a 505 GB Windows partition, it begins the process, but then seems to stop progressing with the status indicator pretty much stopped at a point directly under the "d" in the "Status: Partitioning disk.."
I've let it run for the past 1.5 hours and it hasn't budged.
This is not my first attempt at doing this on this machine. I tried manually partitioning with Disk Utility which pretty much ended up in a disaster that I was able to repair with some difficulty. That was covered in this thread.
I realize that 3TB drives were not supported under 10.8.3, but I thought that was fixed. Am I wrong?

This is a bit of a guess and you might have do a bit of further reading to understand what I am trying to say but basically:
When you buy a Mac - its Hard Disks come partitioned using the GPT partitioning scheme that is used for the UEFI boot process (All new Windows 8 badged computers have UEFI now as well - Macs have been using it for years). This is opposed to the old MBR partitioning scheme that was used with the BIOS boot process.
There are quite a few limitations of the MBR partitioning scheme including:
1. A limit of 4 partitions per volume
2. A limit of 2 TB per partition
3. Poor support for AHCI
When you run Boot Camp - it turns your partitioning into a hybrid of the two, so you get stuck with all the limitations of MBR - with the second bullet point above I suspect of giving you issues.
You have a couple of possible solutions:
1. Test with having all partitions less than 2 TB
or
2. (Technical) Try and install Windows 8 in EFI mode - its a bit tricky at the moment and a little bit of work - but I have it working on my MacBook Pro (although I do have nVidia graphics driver issues that you may or may not encounter as well). See my wiki at multiboot.info for links if you want to attempt this

Airport will only work under Boot Camp XP

Up until a few days ago both my Mac Pro and iMac were working perfectly, both have Boot Camp installed and my girlfreind and I switch reguarly between OSX and XP.
Then the other day we both lost all networking on the OSX sides. The airport works fine under XP.
OSX says that it is connected yet does not get an IP address. I have tried swapping the drivers for older versions, removing the system prefs and rebooting, specifying an IP, reseting the router (Linksys) to factory settings, connecting via an ethernet cable, different channels on the router, different security types, no security at all. OSX just is not communicating with the router at all. I'm sure it isn't a hardware fault as the network is fine under XP. The network also has a PS3, PSP and Wii all working fine.
I'm very frustrated and have waste a whole day wrestling with this issue. Any help?

Same as running Windows on any hardware. You need a program to mount an .iso.
The other question might by 'why' but that is besides the point.
Or why this didn't work (lots of options)
http://www.google.com/search?q=mount+iso
http://win.softpedia.com/dyn-search.php

Network Adapter not working on Boot camp (windows 8)

I have recenlty installed Windows 8 via Boot camp and every thing okay except Wireless connection not detect and I found that there is ? mark on Network adapter in the Device manger which means there is a problem installing the device. I have uninstalled and reinstalled but nothing happend.
I try to serach for a solution but I could not Please help me with that!

Hello, you managed to solve the problem?
I'm having the same problem and still not found the solution.

Wireless not working on boot

I have an older PC (so it's not moving much...), and I'm trying to set up wireless connection trough a USB wireless adapter (Ralink Technology, Corp. RT2501USB Wireless Adapter).
I have the correct drivers installed, and everything set up (doulbe checked of course).
The wireless setup during boot-time does not works, and prints the error message
Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security
If I run iwgetid immeadiateley after login, I get the following output:
$ iwgetid wlan0 -ra
00:00:00:00:00:00
On the other hand, if I try a
sudo /etc/rc.d/network start
after I log in, it works flawlessley.
I've tried the following:
--> setting WIRELESS_TIMEOUT to 10 seconds, does not works (only after boot)
--> double checking the setup lines
--> reading the /etc/rc.d/network script, and executing the commands manually, it works
$ sudo /etc/rc.d/network stop
$ sudo iwconfig wlan0 essid BodorWLAN key s:wikey
$ sudo iwgetid wlan0 -ra
[the MAC-ADDRESS of wlan0, differring from 00:00:00:00:00:00]
--> stopping and starting the /etc/rc.d/network script, it works
--> editing /etc/rc.d/network to print out the used varialbes and more verbose error messages (I've restored it since then, so I cannot post the results, all seemed to be ok.)
/etc/config.d/wireless:
# Settings for wireless cards
# For each wireless interface declared in INTERFACES (in rc.conf), declare
# a wlan_${IF} variable that contains the arguments to be passed to
# iwconfig(8). Then list the original interface name in the
# WLAN_INTERFACES array.
#wlan_eth0="eth0 mode managed essid default"
#WLAN_INTERFACES=(eth0)
/etc/rc.conf:
# /etc/rc.conf - Main Configuration for Arch Linux
# LOCALIZATION
# LOCALE: available languages can be listed with the 'locale -a' command
# HARDWARECLOCK: set to "UTC" or "localtime", any other value will result
# in the hardware clock being left untouched (useful for virtualization)
# TIMEZONE: timezones are found in /usr/share/zoneinfo
# KEYMAP: keymaps are found in /usr/share/kbd/keymaps
# CONSOLEFONT: found in /usr/share/kbd/consolefonts (only needed for non-US)
# CONSOLEMAP: found in /usr/share/kbd/consoletrans
# USECOLOR: use ANSI color sequences in startup messages
LOCALE="hu_HU.UTF-8"
HARDWARECLOCK="UTC"
TIMEZONE="Europe/Budapest"
KEYMAP="hu"
CONSOLEFONT="lat2-16.psfu.gz"
CONSOLEMAP=
USECOLOR="yes"
# HARDWARE
# MOD_AUTOLOAD: Allow autoloading of modules at boot and when needed
# MOD_BLACKLIST: Prevent udev from loading these modules
# MODULES: Modules to load at boot-up. Prefix with a ! to blacklist.
# NOTE: Use of 'MOD_BLACKLIST' is deprecated. Please use ! in the MODULES array.
MOD_AUTOLOAD="yes"
#MOD_BLACKLIST=() #deprecated
MODULES=()
# Scan for LVM volume groups at startup, required if you use LVM
USELVM="no"
# NETWORKING
# HOSTNAME: Hostname of machine. Should also be put in /etc/hosts
HOSTNAME="curly-desktop"
# Use 'ifconfig -a' or 'ls /sys/class/net/' to see all available interfaces.
# Interfaces to start at boot-up (in this order)
# Declare each interface then list in INTERFACES
# - prefix an entry in INTERFACES with a ! to disable it
# - no hyphens in your interface names - Bash doesn't like it
# DHCP: Set your interface to "dhcp" (eth0="dhcp")
# Wireless: See network profiles below
#Static IP example
#eth0="eth0 192.168.0.2 netmask 255.255.255.0 broadcast 192.168.0.255"
eth0="dhcp"
wlan0="dhcp"
wlan_wlan0="wlan0 essid BodorWLAN key s:wikey"
INTERFACES=(eth0 wlan0)
# Routes to start at boot-up (in this order)
# Declare each route then list in ROUTES
# - prefix an entry in ROUTES with a ! to disable it
gateway="default gw 192.168.0.1"
ROUTES=(!gateway)
# Enable these network profiles at boot-up. These are only useful
# if you happen to need multiple network configurations (ie, laptop users)
# - set to 'menu' to present a menu during boot-up (dialog package required)
# - prefix an entry with a ! to disable it
# Network profiles are found in /etc/network.d
# This now requires the netcfg package
#NETWORKS=(main)
# DAEMONS
# Daemons to start at boot-up (in this order)
# - prefix a daemon with a ! to disable it
# - prefix a daemon with a @ to start it up in the background
DAEMONS=(syslog-ng dbus hal network openntpd netfs crond alsa)
Note: I modified sensitive information (passwd, stb.)
I'm running out of ideas, since the network script appears to be working always except at boot time.
Last edited by dragonfi (2010-06-11 15:44:52)

Activating the usb hooks in the ramdisk did not done the job, as the network demon only runs late in boottime (maybe I'm just being imprecise, i'm meaning the part, where it already entered the final runlevel).
On the other hand, I did tracked down the problem, and I beliveve it's some kind of desing-flaw in the wireless USB utility. (Or I'm just not aware of a certain feature in it.)
I modified /etc/rc.d/network to resend the iwconfig to the device after the 2 second sleep, and it seems to work sometimes.
/etc/rc.d/network: (added lines in wi_up())
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
# wireless settings
[ -f /etc/conf.d/wireless ] && . /etc/conf.d/wireless
# ethernet bonding settings
[ -f /etc/conf.d/bonding ] && . /etc/conf.d/bonding
# bridge settings
[ -f /etc/conf.d/bridges ] && . /etc/conf.d/bridges
# dhcpcd settings
[ -f /etc/conf.d/dhcpcd ] && . /etc/conf.d/dhcpcd
ifup()
if [ "$1" = "" ]; then
echo "usage: $0 ifup <interface_name>"
return 1
fi
eval ifcfg="\$${1}"
# Get the name of the interface from the first token in the string
if [ "$ifcfg" = "dhcp" ]; then
ifname="$1"
else
ifname=${ifcfg%% *}
fi
/sbin/ifconfig $ifname up
wi_up $1 || return 1
if [ "$ifcfg" = "dhcp" ]; then
# remove the .pid file if it exists
/bin/rm -f /var/run/dhcpcd-${1}.pid >/dev/null 2>&1
/bin/rm -f /var/run/dhcpcd-${1}.cache >/dev/null 2>&1
/sbin/dhcpcd $DHCPCD_ARGS ${1}
else
/sbin/ifconfig $ifcfg
fi
return $?
wi_up()
eval iwcfg="\$wlan_${1}"
[ "$iwcfg" = "" ] && return 0
/usr/sbin/iwconfig $iwcfg
[[ -z "$WIRELESS_TIMEOUT" ]] && WIRELESS_TIMEOUT=2
sleep $WIRELESS_TIMEOUT
#added line below because wlan0 does not play nice..
/usr/sbin/iwconfig $iwcfg
bssid=`iwgetid $1 -ra`
if [[ "$bssid" = "00:00:00:00:00:00" ]]; then
printhl "Could not associate $1 - try increasing WIRELESS_TIMEOUT and check network is WEP or has no security"
return 1
fi
return 0
ifdown()
if [ "$1" = "" ]; then
echo "usage: $0 ifdown <interface_name>"
return 1
fi
eval ifcfg="\$${1}"
if [ "$ifcfg" = "dhcp" ]; then
if [ -f /var/run/dhcpcd-${1}.pid ]; then
/bin/kill $(cat /var/run/dhcpcd-${1}.pid)
fi
fi
# Always bring the interface itself down
/sbin/ifconfig ${1} down >/dev/null 2>&1
return $?
iflist()
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
printf " $ifline:\t"
else
printf "$ifline:\t"
fi
eval real_ifline=\$${ifline#!}
echo $real_ifline
done
rtup()
if [ "$1" = "" ]; then
echo "usage: $0 rtup <route_name>"
return 1
fi
eval routecfg="\$${1}"
if grep -q :: <<< $routecfg; then
/sbin/route -A inet6 add $routecfg
else
/sbin/route add $routecfg
fi
return $?
rtdown()
if [ "$1" = "" ]; then
echo "usage: $0 rtdown <route_name>"
return 1
fi
eval routecfg="\$${1}"
if grep -q :: <<< $routecfg; then
/sbin/route -A inet6 del $routecfg
else
/sbin/route del $routecfg
fi
return $?
rtlist()
for rtline in ${ROUTES[@]}; do
if [ "$rtline" = "${rtline#!}" ]; then
printf " $rtline:\t"
else
printf "$rtline:\t"
fi
eval real_rtline=\$${rtline#!}
echo $real_rtline
done
bond_up()
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
eval bondcfg="\$bond_${ifline}"
if [ -n "${bondcfg}" ]; then
/sbin/ifenslave $ifline $bondcfg || error=1
fi
fi
done
bond_down()
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
eval bondcfg="\$bond_${ifline}"
/sbin/ifenslave -d $ifline $bondcfg || error=1
fi
done
bridge_up()
for br in ${BRIDGE_INTERFACES[@]}; do
if [ "$br" = "${br#!}" ]; then
# if the bridge already exists, remove it
if [ "$(/sbin/ifconfig $br 2>/dev/null)" ]; then
/sbin/ifconfig $br down
/usr/sbin/brctl delbr $br
fi
/usr/sbin/brctl addbr $br
eval brifs="\$bridge_${br}"
for brif in $brifs; do
if [ "$brif" = "${brif#!}" ]; then
for ifline in ${BOND_INTERFACES[@]}; do
if [ "$brif" = "$ifline" ] && [ "$ifline" = "${ifline#!}" ]; then
ifup $ifline
eval bondcfg="\$bond_${ifline}"
/sbin/ifenslave $ifline $bondcfg || error=1
unset bond_${ifline}
fi
done
/usr/sbin/brctl addif $br $brif || error=1
fi
done
fi
done
bridge_down()
for br in ${BRIDGE_INTERFACES[@]}; do
if [ "$br" = "${br#!}" ]; then
/usr/sbin/brctl delbr $br
fi
done
case "$1" in
start)
if ! ck_daemon network; then
echo "Network is already running. Try 'network restart'"
exit
fi
stat_busy "Starting Network"
error=0
# bring up bridge interfaces
bridge_up
# bring up ethernet interfaces
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
ifup $ifline || error=1
fi
done
# bring up bond interfaces
bond_up
# bring up routes
for rtline in "${ROUTES[@]}"; do
if [ "$rtline" = "${rtline#!}" ]; then
rtup $rtline || error=1
fi
done
if [ $error -eq 0 ]; then
add_daemon network
stat_done
else
stat_fail
fi
stop)
#if ck_daemon network; then
# echo "Network is not running. Try 'network start'"
# exit
#fi
stat_busy "Stopping Network"
rm_daemon network
error=0
for rtline in "${ROUTES[@]}"; do
if [ "$rtline" = "${rtline#!}" ]; then
rtdown $rtline || error=1
fi
done
# bring down bond interfaces
bond_down
for ifline in ${INTERFACES[@]}; do
if [ "$ifline" = "${ifline#!}" ]; then
ifdown $ifline || error=1
fi
done
# bring down bridge interfaces
bridge_down
if [ $error -eq 0 ]; then
stat_done
else
stat_fail
fi
restart)
$0 stop
/bin/sleep 2
$0 start
ifup|ifdown|iflist|rtup|rtdown|rtlist)
$1 $2
echo "usage: $0 {start|stop|restart}"
echo " $0 {ifup|ifdown|iflist|rtup|rtdown|rtlist}"
esac
# vim: set ts=2 noet:
I wrote a sript and chnaged network to this script in my rc.conf, it appears to be working now.
/etc/rc.d/myscript:
#!/bin/bash
. /etc/rc.conf
. /etc/rc.d/functions
ifup()
/sbin/ifconfig wlan0 up
/usr/sbin/iwconfig wlan0 essid BodorWLAN key s:admin
sleep 2
/usr/sbin/iwconfig wlan0 essid BodorWLAN key s:admin
dhcpcd wlan0
return $?
ifdown()
if [ -f /var/run/dhcpcd-wlan0.pid ]; then
/bin/kill $(cat /var/run/dhcpcd-wlan0.pid)
fi
/sbin/ifconfig wlan0 down >/dev/null 2>&1
return $?
case "$1" in
start)
stat_busy "Starting Network"
ifup
stat_done
restart)
stat_busy "Restarting Network"
ifdown
ifup
stat_done
stop)
stat_busy "Stopping Network"
ifdown
stat_done
echo "usage: $0 {start|stop|restart}"
esac
My only question now is that how could I achieve the same solution in a more elegant way, I'm a bit confused, because the above script does the exact same stuff that my modified /etc/rc.d/network would supposed to be doing.
Last edited by dragonfi (2010-06-12 19:27:38)

Bluetooth m.mouse & keyboard not working in Boot Camp on XP

I'm not sure if this is a common problem, but it's doing my head in.
I recently installed Windows XP (SP2) on Boot Camp, the mouse and keyboard had worked fine, and I was able to hold down Option key to choose prefered OS on startup no problem. I then tried to connect to my work network to use the internet (and operate stuff) to discover that I needed to download network drivers. I figured out I needed to insert OSX install DVD and follow the prompts, which I did, setup wizard was enacted and the drivers were (I believe) downloaded.
After restarting the computer I've discovered that I'm now unable to use the bluetooth mighty mouse OR keyboard! I've tried plugging in a USB PC mouse, but that's still not working. So I tried restarting and holding down the option key in the hope of switching back to OSX, but I can't even do that! everytime I restart it goes straight to Windows XP, I've tried several times, pressing the Option key at different points of the restart phase to try and get to the choice screen, but to no avail.
I have a new(ish) 27" Apple iMac running OSX Snow Leapord
Any help appreciated

I've been able to source a PC USB keyboard (along with the mouse), but still unable to get any response from the computer. Doesn't seem to matter if they're plugged in before I restart in windows either.

LED cinema display doesn't work under boot camp

I just installed Boot Camp and Windows 7 x64 on a Macbook Pro 2010 (6,2) with and NVIDIA GeForce GT 330M 256MB video card. The Boot Camp drivers automatically installed during the process. I plugged in my 27 inch LED Cinema Display, which works just fine on the OS X side. However, the screen was dark, as if it wasn't plugged in.
Audio does go through the Cinema Display.
I have tried to repair the drivers twice by running the Boot Camp support software. I also tried to run the NVIDIA driver installation software separately. It failed.
So, what can I do to get the Cinema Display working?
Thanks.

I found a solution that worked for me. I deleted from my USB drive the Boot Camp support software that I had downloaded from the Apple website and downloaded in its place the support software through the Boot Camp Assistant program. I ran setup.exe, did the repair option and restarted. I then went to the NVIDIA driver install application on the USB drive and ran it. This time, it worked! I restarted the computer and both the laptop display and the Cinema Display lit up.
Originally, and during the previous 3 times trying to repair the drivers, I saw the ATI graphics driver getting installed. Somehow, it appears that the NVIDIA drivers didn't install before.
I hope this helps others.

Option Key not working with Boot Camp.

Hi all,
I installed Boot Camp on my new Alu Imac 24" (wired keyboard) and when booting up the option key that should bring up the boot options doesn't work. Is this a known fault with the slimline keyboard and Boot Camp??
I have tried all different combinations of power button and Option key but nothing works.
Any suggestion?
Cheers

have you updated with iMac Software Update 1.0
and latest firmware?
see here:
http://www.apple.com/support/downloads/imacsoftwareupdate10.html
Thanks,
den
.

Wireless Not Working under Boot Camp

Similar Messages

Maybe you are looking for