Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Alternative Operating Systems > mbp 2.2 isight bootcamp 1.3 vista

mbp 2.2 isight bootcamp 1.3 vista
Thread Tools
Fresh-Faced Recruit
Join Date: Dec 2006
Status: Offline
Reply With Quote
Jul 9, 2007, 11:55 AM
 
i used to have mbp 2.16 c2d ... installed vista and bootcamp 1.3...no isight driver problem...now i'm using mbp 2.2 santa rosa platform...installed vista...the isight driver can't be installed...already tried alot of ways but still having the same issue...onyone having the same problem?? are there solution?? please help..
     
Fresh-Faced Recruit
Join Date: Jul 2007
Status: Offline
Reply With Quote
Jul 9, 2007, 01:41 PM
 
I don't have much to offer except to say that isight doesn't work on my Vista installation on a 2.4 MBP either.
     
Fresh-Faced Recruit
Join Date: Nov 1999
Location: Iowa City
Status: Offline
Reply With Quote
Jul 13, 2007, 09:47 PM
 
the santa rosa isight camera has a different USB device code

Compare the hardwareid in Device management to the codes listed in the isight.inf file

The usb device code has to match the codes in the driver.

The driver would need to be updated in order to work with the camera.

I tried editing the inf file to match the USB code for the isight camera - no dice.
     
Administrator
Join Date: Apr 2001
Location: San Antonio TX USA
Status: Offline
Reply With Quote
Jul 16, 2007, 07:51 AM
 
"Early adopter syndrome" is a pain, eh? Right now there are a bunch of PC products that don't have drivers. The iSight cameras in MBPs not having drivers should not be a major surprise. Vista drivers seem to be slightly different from XP drivers, and I'm not sure how, but it's pretty obvious that new drivers will be a major issue for a while, if for no other reason than the coders need time to write them.

Having a different device code can mean a simple upgrade in the hardware or a completely different device-and it could be as different as being from a completely different vendor too. Tinkering with drivers is like pushing buttons on an unlabeled panel just to find out what they'll do; you may be fine, or you may find the self destruct button by mistake. At least goofing up a driver that doesn't work won't blow anything up.
Glenn -----
OTR/L, MOT, Tx
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 05:33 PM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2