Forum Home
Press F1
 
Thread ID: 124401 2012-04-24 21:22:00 Has anyone noticed, that if you copy the firefox install file across a network Speedy Gonzales (78) Press F1
Post ID Timestamp Content User
1271697 2012-04-24 21:22:00 It says its corrupt. It seems to be the only install file that says this. But if I delete the install file (on the computer I copied it to), then copy it across again, its fine

I copied other files across the network (that have digital sigs - ie: MS install files). And they're fine. I dont have to copy them twice, for the install file to install

Any idea, why the FF install file, is the only install file that says its not valid / corrupt. When I copy it across the network the first time. But its fine, the 2nd time?
Speedy Gonzales (78)
1271698 2012-04-24 22:10:00 Maybe the first time it just got corrupted from packet loss. Slankydudl (16687)
1271699 2012-04-24 22:19:00 Could be that, but why doesnt it happen to any other file, that I copy across the network? Speedy Gonzales (78)
1271700 2012-04-24 23:32:00 Maybe there's a bad spot on your HDD in an area offering just enough space for the FF installer, so each time you copy it across it gets dumped into the same bad spot.
Try leaving the bad copy there (rename it perhaps) and then see if any subsequent transfers get reported as corrupt.

The other side of the coin applies too.

Maybe the HDD on the source machine has a bit on the HDD that is giving some variable reads and intermittently corrupting the transfers.

I've had other occasions to suspect that Windows is doing a shonky job of verifying files. Dunno if it is still possible to set an environment variable or similar (eg registry setting) to set Verify ON for all file read/write activities.

It may even be that they've deliberately suppressed it as many internet based transfer errors are either permissable (eg media with fault tolerance) or more easily remedied with a Refresh page rather than with an error dialog that would just confuse the majority of users. Convenience for the novices versus accuracy and reliability for the power users.
Paul.Cov (425)
1271701 2012-04-25 00:49:00 If the packets were lost then they would simply be re-sent.

If the HDD had a faulty sector, it should detect it as faulty and reallocate it when trying to write to it, thus unlikely it would write to that exact same sector twice in a row.

Also, the file transfer would stop during the HDD checking the sector which could be up to several minutes.


I would blame it on some kind of software interfering with the file itself, maybe an antivirus program, or even a virus.
Agent_24 (57)
1271702 2012-04-25 00:53:00 Not a virus, I scanned this morning its clean (well on here anyway). I scanned the other PC the other day, it was clean. Only AV program I have is MSE (just updated it to V4 earlier today). Its just strange its only 1 file (the firefox install) thats corrupt after sending it over the network. Other files (I've sent across are fine). I wont worry about it too much. Just wondered if anyone else had come across the same thing Speedy Gonzales (78)
1271703 2012-04-25 00:59:00 Are you copying to a non-NTFS filesystem? It might be losing some extra information contained in an alternate data stream and having some problem coping with that.

It's funny though, now that I think about it I seem to remember having a similar issue...
Agent_24 (57)
1271704 2012-04-25 01:04:00 Nope both are NTFS formatted. Over GB nics. Using a GB switch Speedy Gonzales (78)
1271705 2012-04-25 01:25:00 Hmm odd, just tried another port on the switch it was OK. Then put it back in the port it was in. Copied the FF install file again. It was fine. Maybe the cable wasnt in far enough?? But then other files (should) have had the same prob. Oh well. Speedy Gonzales (78)
1