![]() ![]()
Could someone test that this patch works on there machine? and verify that downloads to a Windows 7 mapped drive work ok? I have attached a patch which sets the file pointer to the end of file only when the file it is first opened and the append flag is set. I think the problem arises due to a bug in Windows 7 SMB2 where data is cached before been committed to disk(The file is the correct size on the shared drive, but after writing a few chunks to the file the Windows API IO functions see the file as empty with a length of Zero bytes) Do we have to do this before every write(Each subsequent write automatically moves the file pointer). #NETDRIVE 64 BIT WINDOWS 7 DOWNLOAD#SetFilePointer should move the file pointer to the end of file before every write so that it can append data to the file when the download is resumed. #NETDRIVE 64 BIT WINDOWS 7 CODE#I have stepped through the code in the debugger and it looks like this error occurs due to SetFilePointer returning 0 for the end of file after correctly writing a sequence of 32k chunks to the file. I can reproduce this bug consistently with the link posted by peterdk. If I save to a local drive first, then copy to the network it works fine. I am running 3.5.5.Įvery file that I download and save directly to a mapped network drive is corrupt. ![]() If I download directly to a mapped network drive and attempt to run the file I get, "The file is not a valid win32 executable." I can download with IE to the mapped network drive okay. I can download to my local computer fine. Windows 7 Ultimate (bought off the shelf) member of a Windows 2003 R2 domain. ![]() if i download a file to the network share using ie8 or chrome, no corruption. if i download on my local disk and then copy on the network share, works without problems. I did a clean reinstall of win7, latest firefox, and as soon as i download directly to my network share, i cant open them. Same corruption problem with win7 圆4 rtm, and a network share on win 2008r2. Trying to find a workaround (or a solution) as I like to keep my downloads centralized in one location. IE downloads are fine and do not seem to be affected by this issue. Or if Firefox is located on an XP machine and the share is on a Win7 machine then it is okay. When share is located on an XP machine then it is okay. I am using Windows 7 x86 and 圆4 RTM build 7600 and I get this error with Firefox 3.0.11, 3.5.1, and 3.5.2. Some relevant excerpts from the forum thread: There are some non-related issues posted there, but some people are having the same issue. There is quite a large forum thread here about the problem When I save it to an existing corrupt file it suddenly works. It looks like the downloading is only corrupt if a new file is made. The download should just save correctly to the network. It looks like since Firefox 3, somehow the handling of saving downloads to a network drive is corrupted.ġ.Make a network share in Win7, mapped to a Drive letterĢ.Download 10mb+ file in Firefox directly to the network drive However,when I downloaded these files directly to my harddisk instead of using the network drive, all went well. I was getting worried that my raid5 disk was somehow borked, since all my larger file downloads, that I stored directly to the network drive, got corrupt. I have a server that I access as a network drive share in Windows 7. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |