| ActiveMac | Anonymous | Create a User | Reviews | News | Forums | Advertise |
|
|
|
User Controls |
|
New User |
|
Login |
|
Edit/View My Profile |
|
|
|
|
|
|
|
ActiveMac |
|
Articles |
|
Forums |
|
Links |
|
News |
|
News Search |
|
Reviews |
|
|
|
|
|
|
|
News Centers |
|
Windows/Microsoft |
|
DVD |
|
ActiveHardware |
|
Xbox |
|
MaINTosh |
|
News Search |
|
|
|
|
|
|
|
ANet Chats |
|
The Lobby |
|
Special Events Room |
|
Developer's Lounge |
|
XBox Chat |
|
|
|
|
|
|
|
FAQ's |
|
Windows 98/98 SE |
|
Windows 2000 |
|
Windows Me |
|
Windows "Whistler" XP |
|
Windows CE |
|
Internet Explorer 6 |
|
Internet Explorer 5 |
|
Xbox |
|
DirectX |
|
DVD's |
|
|
|
|
|
|
|
TopTechTips |
|
Registry Tips |
|
Windows 95/98 |
|
Windows 2000 |
|
Internet Explorer 4 |
|
Internet Explorer 5 |
|
Windows NT Tips |
|
Program Tips |
|
Easter Eggs |
|
Hardware |
|
DVD |
|
|
|
|
|
|
|
Latest Reviews |
|
Applications |
|
Microsoft Windows XP Professional |
|
Norton SystemWorks 2002 |
|
|
|
Hardware |
|
Intel Personal Audio Player 3000 |
|
Microsoft Wireless IntelliMouse Explorer |
|
|
|
|
|
|
|
Site News/Info |
|
About This Site |
|
Affiliates |
|
ANet Forums |
|
Contact Us |
|
Default Home Page |
|
Link To Us |
|
Links |
|
Member Pages |
|
Site Search |
|
Awards |
|
|
|
|
|
|
|
Credits |
 |
Your top Windows 7 questions, answered | |
|
||
| Time: 09:54 EST/14:54 GMT | News Source: ZDNet | Posted By: Kenneth van Surksum | ||
|
Ed Bott: Since Windows 7 launched on October 22, my e-mail inbox has been deluged with questions, comments, and pleas for help. I can’t possibly reply to them all personally, so I thought I would answer some of the most common/interesting/provocative questions here. So, without further ado… | ||
|
Write Comment
Return to News |
Displaying 1 through 25 of 164 Last | Next |
The time now is
6:43:09 PM
ET.
Any comment problems? E-mail us |
| #1 By 15406 (216.191.227.68) at 11/13/2009 3:47:20 PM |
|
Just today, I received the answer to MY most important question: why does my Win7 box barf when copying files over USB when Vista never had a single problem doing the same operation?
Answer: http://support.microsoft.com/kb/976972 Hotfix available as of three days ago. |
| #2 By 23275 (68.117.163.128) at 11/13/2009 5:51:57 PM |
|
#1, It's not a Microsoft problem, but they did provide the fix.
You see, Windows 7, and Windows Server 2008 R2 support SMB2. XP and derived systems, like W2K3 use SMB1. The controllers and ports on some systems only support SMB1. Windows 7/WS08 R2 will first try SMB2 and then attempt SMB1 if that fails. If the device can't report back as to which version it is using, the request switches back and forth between the two. In rare cases, it will fail entirely. The behavior results from device manufacturers failing to fully implement available support. WS08 R2 Server operators/builders have had a miserable time - even with higher end Intel boards and cages - same drill. In other cases, software from Adobe has as bad a time on Windows 7 when saving to, or reading from mapped shares where XP is the client and WS08 is on the back end. Intel has had to provide fixes as well. The Hotfix, tells the 7 system to simply use SMB1, which sucks, because the potential for leveraging things in SMB2 (IPV6, greater intelligence per packet and nifty Teredo and Rally technology features are lost). Personally, I'd pitch the boogered up drive in the trash and pop for an Antec external housing like the MX-1 http://www.antec.com/Believe_it/product.php?id=NzA0MjIx and use its included back-plane to provide for an eSATA II port and fit it out with a decent 1 TB drive from WD. Yeah, I know... Latch will say "Windows 7 requires that people buy all new equipment..." Well... no, but when the choice is between pitching a POS external drive using a USB interface or cutting off 7's legs... I'd rather pitch the drive and go with something better. |
| #3 By 15406 (99.240.77.173) at 11/13/2009 7:34:53 PM |
| #2: It's been bugging me so much at this point I don't care who's fault it was as long as someone provides a fix. I'm quite surprised it came to this. I would think that x64 + nForce 6+ + 4GB+ is a common configuration and someone would have reported a problem during the betas and RCs. I'm copying 2.5 GB now and we'll see how it goes. |
| #4 By 23275 (68.117.163.128) at 11/13/2009 8:00:00 PM |
|
It's the controller on the USB drive.
There is so much data out there for device manufacturers. When you build, to a baseline, or otherwise, there is enough information from MS and in the channel that it is not hard to find the right mix of parts that will perform optimally against available WHQL drivers for any version of Windows out there. It makes all the difference and especially early in an OS's lifecycle and just as it was possible to provide great user experiences with early versions of Vista, it is the same with Windows 7. For example, anyone now building their own rig on the P55 isn't doing themselves any favors, but those building on ASUS X-58 based boards with i7's are in for a real treat with Windows 7. In time the 55 will come along, but it isn't even in the same universe as the older X-58 (just as an example). Enthusiast builders normally know every mm of their rigs and set up in advance all the latest drivers and firmware and build until the rig is almost perfect. |
| #5 By 15406 (99.240.77.173) at 11/14/2009 8:09:07 AM |
|
#4: The copy fiinished without a hitch.
You claim it's the controller on the USB drive. How do oyu reconcile that the exact same hardware worked perfectly under Vista? It seems to me that it was a problem with the Win7 USB port driver. Regardless, it's fixed and now a non-issue (for me.) Less technical users will suffer with it until SP1 next summer. |
| #6 By 23275 (68.117.163.128) at 11/14/2009 11:01:16 AM |
| #5, Because each was designed to use SMB1 and the controller/driver from that manufacturer is incomplete and it cannot tell Windows 7 which version to use - so it will hunt back and forth between the two. Microsoft provided a Hotfix to force the OS to use SMB1 first, vice looking for SMB2 |
| #7 By 15406 (99.240.77.173) at 11/15/2009 8:29:23 AM |
| #6: How is it that you know so much about this exact problem? If the Win7 USB driver can't get confirmation from a device as to what it level it supports, it should use the most compatible mode instead of bouncing between the two for whatever bizarre reason it would do that. |
| #8 By 12071 (124.168.167.122) at 11/16/2009 5:50:12 AM |
|
There's currently an issue affecting the handling of SMBv1 and SMBv2 in Windows 7:
http://computerworld.co.nz/news.nsf/scrt/E9592E1A9719742ACC25766F0066B38D Make sure your firewall is blocking 139 (which should be just about by default) and 445. |
| #9 By 23275 (68.117.163.128) at 11/16/2009 9:12:33 AM |
|
#7,8, The two issues are not related and the bug @8 affects more than just Windows 7.
|
| #10 By 15406 (216.191.227.68) at 11/16/2009 11:53:35 AM |
| #9: I'm still waiting for your stunning technical insight into how hardware that works under XP and Vista fails under Win7 but works again after a patch, and somehow it's the hardware's fault. |
| #11 By 241766 (216.191.227.68) at 11/18/2009 9:50:00 AM |
| Latch: Does this issue involve only a single USB device, or multiple devices? Have you tried other devices, such as various external USB hard drive enclosures or various USB thumb drives? Do some work, and others not work? This test could help point to where the real problem lies. |
| #12 By 23275 (68.117.163.128) at 11/18/2009 10:45:38 AM |
|
#10,11, Latch's issue would likely relate to any USB device to which he was writing large files in/out to. The issue, as I have tried to explain relates to how the device is able to interact with the operating system and while MS is providing work arounds and future releases, the underlying matter has less to do with the new OS than it does with how many devices, including those connecting through iTunes, are implemented. Just guessing here, but I am willing to bet Latch has a nForce 6 or higher chipset, 4GB of RAM or more and is running an x64 based version of Windows 7. He probably has an nVidia 7600GT GPU and an inelegant install of applicable drivers for that card. To explain how and or the why of this would fills books and the remaining hard drive space on Awin's server array. Everything from the SRV Paged/Non-Paged pool to memory hole mapping and how memory is being allocated in support of file transfers is in play here. His USB drive's controller simply cannot tell the OS what it needs, when, or for how long and the OS keeps asking it for information it has no clue how to provide or where to write that information. It keeps doing this until there is no more addressable space into which it can write and the system hangs. The GPU has a role, too and depending upon which driver is being used on what rev, it's going to grab a chunk and not let go. All the while the chipset is unable to manage how memory is mapped and remapped.
If you fit into the category above, have 4GB of RAM or more and use an nForce 6 or higher chipset with Windows 7 x64, please consider the following: http://support.microsoft.com/kb/976972 |
| #13 By 15406 (216.191.227.68) at 11/18/2009 11:33:43 AM |
|
#11: All my USB devices were hosed: thumb drive, external HDD and Blackberry. The patch I mentione din #1 fixed the issue.
#12: Hey Sherlock, you don't miss a trick. Yes, I'm running nForce 6 + W7 x64 + 4GB RAM, just like I alluded to in #3. And thanks for the helpful link that I had already posted in #1. It was obviously a USB port driver problem. nForce 6 has been around for years, and XP/Vista had no problems with it. After a patch, all is well again. |
|
Write Comment
Return to News |
Displaying 1 through 25 of 164 Last | Next |
The time now is
6:43:09 PM
ET.
Any comment problems? E-mail us |
