From: Davoud on 30 Apr 2010 20:10 I did more research following my earlier post (which drew only one response, as Mr. Oates took the opportunity to bash Microsoft). The problem is, AFAIK, limited to the latest generation MacBook Pro's with Core i5 and Core i7 processors, and the Boot Camp utility that ships with these machines. The error messages in Windows 7 troubleshooting are: "Intel(R)Series/3400 Series Chipset Family USB Universal Host Controller - 3B36 has a driver problem Intel(R)Series/3400 Series Chipset Family USB Universal Host Controller - 3B3B has a driver problem" There is also a missing driver for the "Teredo Tunneling Pseudo Interface" (IPV4/IPV6 related). Like other hardware and software drivers, these should be installed by BootCamp, but they are apparently not installed. One report says that this bug affects Win 7 32-bit and 64-bit and XP Pro 32-bit. Essentially, then, it seems that it is not possible to run Windows on the latest generation of MacBook Pro's. If anyone reading this has installed the above named OS's on a latest-generation MB Pro and has not experienced these problems, I would appreciate hearing about it. Davoud -- I agree with almost everything that you have said and almost everything that you will say in your entire life. usenet *at* davidillig dawt cawm
From: David Empson on 30 Apr 2010 22:05 Davoud <star(a)sky.net> wrote: > I did more research following my earlier post (which drew only one > response, as Mr. Oates took the opportunity to bash Microsoft). > > The problem is, AFAIK, limited to the latest generation MacBook Pro's > with Core i5 and Core i7 processors, and the Boot Camp utility that > ships with these machines. The error messages in Windows 7 > troubleshooting are: > > "Intel(R)Series/3400 Series Chipset Family USB Universal Host > Controller - 3B36 has a driver problem > > Intel(R)Series/3400 Series Chipset Family USB Universal Host Controller > - 3B3B has a driver problem" The above two could be problems with Apple's Boot Camp drivers for the new MacBook Pros. Did you install the drivers using the DVD which came with the computer? (I'd expect this sort of problem if you used the one on the retail Snow Leopard DVD, for example, since the new MacBook Pros have new hardware components.) > There is also a missing driver for the "Teredo Tunneling Pseudo > Interface" (IPV4/IPV6 related). That's nothing to do with Apple. The Teredo Tunneling Pseudo Interface is a software driver which comes with Windows, that is responsible for encapsulating IPv6 traffic inside IPv4 packets, to allow them to travel through an IPv4 NAT router without being corrupted. It has nothing to do with the hardware - it is all handled at a higher level. <http://technet.microsoft.com/en-us/library/bb457011.aspx> (Not yet updated to describe Windows 7.) > Like other hardware and software drivers, these should be installed by > BootCamp, but they are apparently not installed. > > One report says that this bug affects Win 7 32-bit and 64-bit and XP > Pro 32-bit. Essentially, then, it seems that it is not possible to run > Windows on the latest generation of MacBook Pro's. > > If anyone reading this has installed the above named OS's on a > latest-generation MB Pro and has not experienced these problems, I > would appreciate hearing about it. I have the latest MacBook Pro but don't have Boot Camp set up on it (nor do I have Windows 7), so can't help directly. -- David Empson dempson(a)actrix.gen.nz
From: Mark Conrad on 30 Apr 2010 23:09 In article <300420102010129229%star(a)sky.net>, Davoud <star(a)sky.net> wrote: > If anyone reading this has installed the above named OS's on a > latest-generation MB Pro and has not experienced these problems, I > would appreciate hearing about it. Davoud, it will take my new 17" MacBook Pro about two weeks to arrive, but I will be happy to load up the 64-bit Win-7 and try to duplicate the problem. So far, I have refrained from installing the 64-bit version of Windows-7 until more drivers are available for it. With my older MacBook Pro running the 32-bit version of Windows-7, the crashes do not occur. One place you might check is the knowbrainer.com moderated forum: <http://www.knowbrainer.com/pubforum/index.cfm?page=viewForumCategory&ca tegoryId=2> There is a moderator on that site who runs 64-bit Windows-7, but he runs it on late model Intel i7 PC hardware, he signs as "Chucker". (Chuck Runquist) Chuck might be able to steer you where to download the drivers, he is extremely helpful and should know where to download the missing drivers - - - plus he worked with Microsoft and was also was a team leader for a bunch of Dragon programmers. Only hassle is that you would have to join the forum to post, because it is moderated. Mark-
From: Davoud on 30 Apr 2010 23:52 David Empson wrote: > Davoud wrote: > > > I did more research following my earlier post (which drew only one > > response, as Mr. Oates took the opportunity to bash Microsoft). > > > > The problem is, AFAIK, limited to the latest generation MacBook Pro's > > with Core i5 and Core i7 processors, and the Boot Camp utility that > > ships with these machines. The error messages in Windows 7 > > troubleshooting are: > > > > "Intel(R)Series/3400 Series Chipset Family USB Universal Host > > Controller - 3B36 has a driver problem > > > > Intel(R)Series/3400 Series Chipset Family USB Universal Host Controller > > - 3B3B has a driver problem" > > The above two could be problems with Apple's Boot Camp drivers for the > new MacBook Pros. This is almost certainly the case. Others are experiencing the same problem with the new generation MacBook Pro's. I do not know about other Mac models. > Did you install the drivers using the DVD which came with the computer? Yes. It appears that the drivers are missing from Boot Camp in the version that ships with the new MBP's. > (I'd expect this sort of problem if you used the one on the retail Snow > Leopard DVD, for example, since the new MacBook Pros have new hardware > components.) > > > There is also a missing driver for the "Teredo Tunneling Pseudo > > Interface" (IPV4/IPV6 related). > > That's nothing to do with Apple. The Teredo Tunneling Pseudo Interface > is a software driver which comes with Windows, that is responsible for > encapsulating IPv6 traffic inside IPv4 packets, to allow them to travel > through an IPv4 NAT router without being corrupted. OK, but could there not still be a separate Apple driver needed? Whatever the case, the network runs just fine... > > It has nothing to do with the hardware - it is all handled at a higher > level. > > <http://technet.microsoft.com/en-us/library/bb457011.aspx> > > (Not yet updated to describe Windows 7.) > > > Like other hardware and software drivers, these should be installed by > > BootCamp, but they are apparently not installed. > > > > One report says that this bug affects Win 7 32-bit and 64-bit and XP > > Pro 32-bit. Essentially, then, it seems that it is not possible to run > > Windows on the latest generation of MacBook Pro's. > > > > If anyone reading this has installed the above named OS's on a > > latest-generation MB Pro and has not experienced these problems, I > > would appreciate hearing about it. > > I have the latest MacBook Pro but don't have Boot Camp set up on it (nor > do I have Windows 7), so can't help directly. AFAIK, only Apple can help -- with a Boot Camp update. Interestingly, I installed Parallels 5.0 on the machine and it has been running with out a hitch for about 1/2 hour. That's about 25 minutes longer than its record when booted directly. Hmmm. I don't know what that means. It has given me time to D/L Safari and make it the default browser, at least! And it has let me download two sets of updates and restart successfully. (After an interruption here it has now been running for 45 minutes.) Windows under Parallels would not activate automatically on-line, but that is not unusual. The automated telephone activation worked well enough, however. Thanks, Davoud -- I agree with almost everything that you have said and almost everything that you will say in your entire life. usenet *at* davidillig dawt cawm
From: David Empson on 1 May 2010 04:22 Davoud <star(a)sky.net> wrote: > David Empson wrote: > > > Davoud wrote: > > > > > I did more research following my earlier post (which drew only one > > > response, as Mr. Oates took the opportunity to bash Microsoft). > > > > > > The problem is, AFAIK, limited to the latest generation MacBook Pro's > > > with Core i5 and Core i7 processors, and the Boot Camp utility that > > > ships with these machines. The error messages in Windows 7 > > > troubleshooting are: > > > > > > "Intel(R)Series/3400 Series Chipset Family USB Universal Host > > > Controller - 3B36 has a driver problem > > > > > > Intel(R)Series/3400 Series Chipset Family USB Universal Host Controller > > > - 3B3B has a driver problem" > > > > The above two could be problems with Apple's Boot Camp drivers for the > > new MacBook Pros. > > This is almost certainly the case. Others are experiencing the same > problem with the new generation MacBook Pro's. I do not know about > other Mac models. > > > Did you install the drivers using the DVD which came with the computer? > > Yes. It appears that the drivers are missing from Boot Camp in the > version that ships with the new MBP's. > > > (I'd expect this sort of problem if you used the one on the retail Snow > > Leopard DVD, for example, since the new MacBook Pros have new hardware > > components.) > > > > > There is also a missing driver for the "Teredo Tunneling Pseudo > > > Interface" (IPV4/IPV6 related). > > > > That's nothing to do with Apple. The Teredo Tunneling Pseudo Interface > > is a software driver which comes with Windows, that is responsible for > > encapsulating IPv6 traffic inside IPv4 packets, to allow them to travel > > through an IPv4 NAT router without being corrupted. > > OK, but could there not still be a separate Apple driver needed? > > Whatever the case, the network runs just fine... If IPv4 is working, then there is no hardware driver involved to get IPv6 working on top of it; even IPv6 working directly on the same network hardware would be fine. The Ethernet hardware might need a driver from the vendor, but the same driver would be used for all protocols. > Interestingly, I installed Parallels 5.0 on the machine and it has been > running with out a hitch for about 1/2 hour. That's about 25 minutes > longer than its record when booted directly. Hmmm. I don't know what > that means. Nothing. Parallels implements a virtual machine, so Windows running inside Parallels is using drivers supplied by Parallels. They don't have direct access to the Mac's hardware. Any hardware features needed by Parallels are indirectly using drivers in Mac OS X, which work fine. Boot Camp drivers have nothing to do with running Windows in a virtual machine. -- David Empson dempson(a)actrix.gen.nz
|
Next
|
Last
Pages: 1 2 Prev: How do you get Win app itself to nearly fullscreen in VirtualBox? Next: [Bump]: home, net |