Vista large file handling problem
-
quite some time ago, I had a similar problem with the old pkzip program and random bad file problems. Turns out it was an overclocking problem with the CPU. I put it back to the "rated" speed and everything worked fine... :sigh:
Steve _________________ I C(++) therefore I am
The setup I have can crank out a boost of about 65 to 70% if I o-clock it and cool it with water, but I haven't even touched that yet.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
It makes sense if you're not using "self repairing" p2p protocol. FTP/HTTP are prone to errors and if you get an error while downloading an image, it's much easier to redownload one of the eleven 700MB files rather than redownload 7.7GB.
And, of course, there's the fact the IE can't download single files larger than 4GB...
-
Has anyone else seems something like this?? I've seen similar problems, but only handlgin files acrossed network connections. This problem occurs on both 32 and 64 bit versions of Vista. Anyway, I picked up the VS2010 CTP, which, of course, comes on a Virtual Server hard drive file. Unpacked, this thing weighs in at 24GB+. You get it in a self-extracting WinRAR, across (11) 700MB files. Now, once you have the files, it's a simple matter of launching the first one to extract the contents. Simple enough, right?! OK. Start the extraction on a Vista machine and WinRAR will tell me that one of the RAR files is corrupted, say #4. Alright, I just downloaded a new copy of that file and restarted the extraction. Again, another file is bad, this time #7. OK, another download and restart. This time, it says that file #2 is bad. Wait a minute, that file worked fine before! Now, I'm doing this on a newly built Intel Q9550 Quad Core with two Seagate 1.5TB drives in RAID-1. These particular drives have been known to cause problems in a RAID setup if the drives are using an older firmware. Checked with Seagate and my drives should not have the RAID problems because they have been fixed in the latest and greatest firmware release, which my drives both have. There are no known issues with the RAID controller built into the Intel P45 chipset. So I figure I'll just get a new copy of all the files, downloaded on an XP machine and saved to an external USB 80GB drive. 2 hours later... I startup WinRAR on the XP machine and verify, repeated, that the entire 11 file set tests OK. Great! Everything passes! I take that same drive and attach it to the Vista machine and re-run the same tests on those 11 files. The tests fail, again and again, showing failures in different files of the archive every time. :wtf: Now, it gets interesting. It seems that there are known problems with Explorer on Vista copying large files over network connections, but those were supposed to be fixed in SP1. Curious... Since I can't unpack this archive on the Vista machine, I go back to the XP machine to do it. It works perfectly and I've got a very large and happy 24GB VHD file now. I copy that back to the USB drive and go back to the Vista machine. The ONLY way I could get a good copy of that file onto the RAID setup was to open a CMD prompt and use XCOPY to copy the file! :WTF: Anyone else heard of this??
Dave, That is very odd, and I've not had that exact same problem, but one very much like it: On Windows Vista, in a VM, I have an installer that fails to copy files. Each time I run the installer, it fails on a different file. But if I take that exact same CD/Installer and run it on XP, it works fine. I thought, at the time, perhaps it had to do with the fact that I was running Vista in a VM ... but after reading your post here, now I'm not so certain. FYI - these were small files (100k or so).
:..::. Douglas H. Troy ::..
Bad Astronomy |VCF|wxWidgets|WTL -
Has anyone else seems something like this?? I've seen similar problems, but only handlgin files acrossed network connections. This problem occurs on both 32 and 64 bit versions of Vista. Anyway, I picked up the VS2010 CTP, which, of course, comes on a Virtual Server hard drive file. Unpacked, this thing weighs in at 24GB+. You get it in a self-extracting WinRAR, across (11) 700MB files. Now, once you have the files, it's a simple matter of launching the first one to extract the contents. Simple enough, right?! OK. Start the extraction on a Vista machine and WinRAR will tell me that one of the RAR files is corrupted, say #4. Alright, I just downloaded a new copy of that file and restarted the extraction. Again, another file is bad, this time #7. OK, another download and restart. This time, it says that file #2 is bad. Wait a minute, that file worked fine before! Now, I'm doing this on a newly built Intel Q9550 Quad Core with two Seagate 1.5TB drives in RAID-1. These particular drives have been known to cause problems in a RAID setup if the drives are using an older firmware. Checked with Seagate and my drives should not have the RAID problems because they have been fixed in the latest and greatest firmware release, which my drives both have. There are no known issues with the RAID controller built into the Intel P45 chipset. So I figure I'll just get a new copy of all the files, downloaded on an XP machine and saved to an external USB 80GB drive. 2 hours later... I startup WinRAR on the XP machine and verify, repeated, that the entire 11 file set tests OK. Great! Everything passes! I take that same drive and attach it to the Vista machine and re-run the same tests on those 11 files. The tests fail, again and again, showing failures in different files of the archive every time. :wtf: Now, it gets interesting. It seems that there are known problems with Explorer on Vista copying large files over network connections, but those were supposed to be fixed in SP1. Curious... Since I can't unpack this archive on the Vista machine, I go back to the XP machine to do it. It works perfectly and I've got a very large and happy 24GB VHD file now. I copy that back to the USB drive and go back to the Vista machine. The ONLY way I could get a good copy of that file onto the RAID setup was to open a CMD prompt and use XCOPY to copy the file! :WTF: Anyone else heard of this??
I would check the memory on the computer. My experience is that in 98% of the cases, file corruption is caused by bad memory. Windows has a stupid (imao) habit of buffering even really large files in memory before writing to harddrive.
-
Has anyone else seems something like this?? I've seen similar problems, but only handlgin files acrossed network connections. This problem occurs on both 32 and 64 bit versions of Vista. Anyway, I picked up the VS2010 CTP, which, of course, comes on a Virtual Server hard drive file. Unpacked, this thing weighs in at 24GB+. You get it in a self-extracting WinRAR, across (11) 700MB files. Now, once you have the files, it's a simple matter of launching the first one to extract the contents. Simple enough, right?! OK. Start the extraction on a Vista machine and WinRAR will tell me that one of the RAR files is corrupted, say #4. Alright, I just downloaded a new copy of that file and restarted the extraction. Again, another file is bad, this time #7. OK, another download and restart. This time, it says that file #2 is bad. Wait a minute, that file worked fine before! Now, I'm doing this on a newly built Intel Q9550 Quad Core with two Seagate 1.5TB drives in RAID-1. These particular drives have been known to cause problems in a RAID setup if the drives are using an older firmware. Checked with Seagate and my drives should not have the RAID problems because they have been fixed in the latest and greatest firmware release, which my drives both have. There are no known issues with the RAID controller built into the Intel P45 chipset. So I figure I'll just get a new copy of all the files, downloaded on an XP machine and saved to an external USB 80GB drive. 2 hours later... I startup WinRAR on the XP machine and verify, repeated, that the entire 11 file set tests OK. Great! Everything passes! I take that same drive and attach it to the Vista machine and re-run the same tests on those 11 files. The tests fail, again and again, showing failures in different files of the archive every time. :wtf: Now, it gets interesting. It seems that there are known problems with Explorer on Vista copying large files over network connections, but those were supposed to be fixed in SP1. Curious... Since I can't unpack this archive on the Vista machine, I go back to the XP machine to do it. It works perfectly and I've got a very large and happy 24GB VHD file now. I copy that back to the USB drive and go back to the Vista machine. The ONLY way I could get a good copy of that file onto the RAID setup was to open a CMD prompt and use XCOPY to copy the file! :WTF: Anyone else heard of this??
Last year I struggled with random corruption problems on an XP Pro box. I eventually narrowed it down to what turns out to be a known incompatibility between Seagate Barracuda 7 SATA drives and the nForce4 chip set. What made it confusing is that it only happened under very high loads, especially when the network system was also under load. (For the curious, I bought a PATA drive and it's been fine since--my performance actually went up a tick, though that's probably due to it being a Barracuda 10 series.) One thing I learned; Seagate is very coy about problems with anything but standard configurations. They have yet to acknowledge the problem I've mentioned--partly understandable since the drives work perfectly fine with any other chip set, but still aggravating. In this case, my gaze falls squarely on your RAID setup. I'll wager that XP Pro would have the same problem on the same hardware. In any case, I'd dump it ASAP since it will cause other headaches.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
-
I would check the memory on the computer. My experience is that in 98% of the cases, file corruption is caused by bad memory. Windows has a stupid (imao) habit of buffering even really large files in memory before writing to harddrive.
Memory tests out OK for 3 straight days. Not a single problem.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Last year I struggled with random corruption problems on an XP Pro box. I eventually narrowed it down to what turns out to be a known incompatibility between Seagate Barracuda 7 SATA drives and the nForce4 chip set. What made it confusing is that it only happened under very high loads, especially when the network system was also under load. (For the curious, I bought a PATA drive and it's been fine since--my performance actually went up a tick, though that's probably due to it being a Barracuda 10 series.) One thing I learned; Seagate is very coy about problems with anything but standard configurations. They have yet to acknowledge the problem I've mentioned--partly understandable since the drives work perfectly fine with any other chip set, but still aggravating. In this case, my gaze falls squarely on your RAID setup. I'll wager that XP Pro would have the same problem on the same hardware. In any case, I'd dump it ASAP since it will cause other headaches.
Anyone who thinks he has a better idea of what's good for people than people do is a swine. - P.J. O'Rourke
I thought the same thing, but the files also failed tests running straight off of a USB connected drive, no RAID invovled.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
Memory tests out OK for 3 straight days. Not a single problem.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Then my best bets would be on the controller, cabling, harddrives, motherboard or even the antivirus. In that order
-
I thought the same thing, but the files also failed tests running straight off of a USB connected drive, no RAID invovled.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Seems that you have tested two different OS with different drivers (32bit vs 64bit), different cables and controllers and tested the memory. Only the MB and processor left. And to me, personally, problems with the processor is only rumours on the internet.
-
I thought the same thing, but the files also failed tests running straight off of a USB connected drive, no RAID invovled.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008I just remembered another error source you might want to check. If your network adapter is using a TCP Offload Engine your TCP stack is partly or fully bypassed and all Checksum and Sequence number calculations are done in the hardware. So if the buffer is faulty...
-
I just remembered another error source you might want to check. If your network adapter is using a TCP Offload Engine your TCP stack is partly or fully bypassed and all Checksum and Sequence number calculations are done in the hardware. So if the buffer is faulty...
The fileset I'm using now was downloaded on an XP machine and checks out fine on that machine, repeatedly. It unpacks perfectly and the drive image works in Virtual PC.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008 -
The fileset I'm using now was downloaded on an XP machine and checks out fine on that machine, repeatedly. It unpacks perfectly and the drive image works in Virtual PC.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008Sorry, I have to learn to reread the first message in the thread before answering.
-
Has anyone else seems something like this?? I've seen similar problems, but only handlgin files acrossed network connections. This problem occurs on both 32 and 64 bit versions of Vista. Anyway, I picked up the VS2010 CTP, which, of course, comes on a Virtual Server hard drive file. Unpacked, this thing weighs in at 24GB+. You get it in a self-extracting WinRAR, across (11) 700MB files. Now, once you have the files, it's a simple matter of launching the first one to extract the contents. Simple enough, right?! OK. Start the extraction on a Vista machine and WinRAR will tell me that one of the RAR files is corrupted, say #4. Alright, I just downloaded a new copy of that file and restarted the extraction. Again, another file is bad, this time #7. OK, another download and restart. This time, it says that file #2 is bad. Wait a minute, that file worked fine before! Now, I'm doing this on a newly built Intel Q9550 Quad Core with two Seagate 1.5TB drives in RAID-1. These particular drives have been known to cause problems in a RAID setup if the drives are using an older firmware. Checked with Seagate and my drives should not have the RAID problems because they have been fixed in the latest and greatest firmware release, which my drives both have. There are no known issues with the RAID controller built into the Intel P45 chipset. So I figure I'll just get a new copy of all the files, downloaded on an XP machine and saved to an external USB 80GB drive. 2 hours later... I startup WinRAR on the XP machine and verify, repeated, that the entire 11 file set tests OK. Great! Everything passes! I take that same drive and attach it to the Vista machine and re-run the same tests on those 11 files. The tests fail, again and again, showing failures in different files of the archive every time. :wtf: Now, it gets interesting. It seems that there are known problems with Explorer on Vista copying large files over network connections, but those were supposed to be fixed in SP1. Curious... Since I can't unpack this archive on the Vista machine, I go back to the XP machine to do it. It works perfectly and I've got a very large and happy 24GB VHD file now. I copy that back to the USB drive and go back to the Vista machine. The ONLY way I could get a good copy of that file onto the RAID setup was to open a CMD prompt and use XCOPY to copy the file! :WTF: Anyone else heard of this??
Well, it could be problems with the protocol you are using and a good integrity check would be nice. I'm unfamiliar with your WinRAR verification, as I don't use it. Is that supposed to verify the 24GB file that is extracted or act as a CRC32 checksum of sorts for the 11 you downloaded? If possible, you should have the source MD5 their copies of the 11 files, then MD5 each one after you download. This will ensure the same thing was delivered. If the downloads are getting corrupted, then choosing a different protocol (FTP or SCP?) might work out. Of course, it might be messed up at the source or a problem with how your machine is handing the VM. I've had trouble moving VM's. If I didn't use the clone feature, the new copy often screwed up. Virtualization has gotten complex enough that this problem could have many causes. (sighs)
-
Well, it could be problems with the protocol you are using and a good integrity check would be nice. I'm unfamiliar with your WinRAR verification, as I don't use it. Is that supposed to verify the 24GB file that is extracted or act as a CRC32 checksum of sorts for the 11 you downloaded? If possible, you should have the source MD5 their copies of the 11 files, then MD5 each one after you download. This will ensure the same thing was delivered. If the downloads are getting corrupted, then choosing a different protocol (FTP or SCP?) might work out. Of course, it might be messed up at the source or a problem with how your machine is handing the VM. I've had trouble moving VM's. If I didn't use the clone feature, the new copy often screwed up. Virtualization has gotten complex enough that this problem could have many causes. (sighs)
NimitySSJ wrote:
Well, it could be problems with the protocol you are using
No choices. It's HTTP or nothing. This is Microsoft serving up the files we're talking about here. They download just fine on any other machine in the house.
NimitySSJ wrote:
I'm unfamiliar with your WinRAR verification, as I don't use it.
It's just another PKZIP variant.
NimitySSJ wrote:
Is that supposed to verify the 24GB file that is extracted or act as a CRC32 checksum of sorts for the 11 you downloaded?
Like PKZip, it has the ability to test the archive integrity.
NimitySSJ wrote:
f possible, you should have the source MD5 their copies of the 11 files, then MD5 each one after you download.
As I said, this is Microsoft we're talking about. There is no MD5, and the files checkout and unpack just fine on my XP boxes. The exact same files on the exact same drive they sit on (USB external) fail checks and will not unpack on Vista 32 or Vista 64.
NimitySSJ wrote:
If the downloads are getting corrupted
No, they're not - verified countless times.
NimitySSJ wrote:
Of course, it might be messed up at the source or a problem with how your machine is handing the VM.
I'm not doing this under a VM. The files CONTAIN the hard drive image of a VM. There's no virtualization involved in this process.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007, 2008