annoying corrupt file problem

[celeritas]

When launching some .exes on my Win2k Adv. Server box (1 NTFS HD, 1 FAT32 HD) that were copied through my network, I get intermittent errors; CRC failures, "bad media or installation file," etc. The files launch fine on the "source" PCs (all Win2kPro FAT32), but something happens to them when they arrive on the Adv. Server box. The funny thing is that zip files containing .exe's will extract just fine; it's the .exe's themselves that have problems. BTW, the source/destination file sizes match exactly...

I ran defrag, scandisk (everything was OK). Have newest McAfee antivirus software installed; scanned for virii in Windows & even booted from McAfee AV floppy and scanned every file in DOS mode. It said something like "unable to read boot sector" -- NTFS or virus? Hmm. For what it's worth, McAfee says it's clean. I also checked the partition/BIOS settings, and the computer seems to be detecting everything properly. I swapped the PC100 RAM stick for another and changed the NIC+settings. Nothing helped.

I think I've covered most of the bases, but if I'm missing something please let me know. Thanks. I think I remember this happening on another Win2k server/NTFS box I was working on; I'm pretty sure reformatting with FAT32 made the problem go away...

 

[vi edit]

I've had many a problems trying to manipulate zip files over network. I get the same corrupt errors as you.

I usually get them when I try to extract a zip that is on a remote pc to a local HD. Winzip usually throws a fit and says it's corrupt.

I've also had problems where I have copied the winzip archive from a remote pc to the local HD and then tried to extract it locally. Same problem. I'm not sure what it is. It could be a bug in Winzip.

My easiest solution is to run winzip from the pc that the archive is on, and then extract it to the shared folder that you want it to go to.

 

[celeritas]

Hmm. Interesting, but in my case it's the .exe's that are throwing a fit on the one box, not the .zips. I tried to do a fdisk /mbr, and even got Service Pack 1, critical updates, etc. from Windows Update, and copied files directly to the FAT32 drive, then the NTFS drive, but nothing has made any difference so far. Maybe I'll try to download a large .exe directly from the Internet to that box and see if it says it's bad. Another weird thing I noticed... When I test/confirm that an .exe is OK, copy it over to Adv. Svr. box (where it isn't OK), then copy it back to the "source" PC, it complains that it's corrupt on that box as well -- but like I said, the file sizes match exactly all around. Weird.