//flex table opened by JP

Click to See Complete Forum and Search --> : Winzip CRC Errors


Nixona
12-30-1999, 03:16 PM
Anyone that can help me with CRC errors in extracting files for a setu program? The programs are 3dMark 99 and 2000. I can use Quickzip to get around these errors, but the programs arent working right. I get corrupted file, decoding, and format errors that hault the programs. Are these due to the crc errors? I've downloaded a few times, whats going on? I shouldnt be getting all these errors..should I? they halt the program...I can get a benchmark from 99 version, no demo, and nothing from 2000. Downloaded 3 times I think, all from different servers.

socalgal
12-30-1999, 03:27 PM
I don't know if this will help as I didn't encounter CRC errors, but I did have problems installing 3DMARK2000.

What finally worked for me is, I downloaded into a folder I created on my desktop (instead of my downloads folder) and it extracted and installed fine from its own folder. (Thanks to Chainsaw!) Also, I use WinZip. http://www.winzip.com/

[This message has been edited by socalgal (edited 12-30-1999).]

Nixona
12-30-1999, 03:47 PM
I'll try that here soon...I do use winzip, but something I read said if you get CRC errors, use quickzip. I did, got the problems. I think I'm probably having your problem...only just my own little worse way http://www.sysopt.com/forum/smile.gif

Nixona
12-30-1999, 04:13 PM
Ok, that got around the CRC errors, but I still have problems. Corruption of Files, or non existant file errors. But, I also installed glsetup today, to fix a gaming problem. IT fixed the problem initially, but later I discovered it's causing screen distortion...I think it may be time to cut ye olde losses and start over

socalgal
12-30-1999, 05:44 PM
Hmm, sorry to hear it Nixona. I really don't know what to tell you. Except (and I have no proof of it) sometimes if I get a screwy download, I'll try to redownload with my security settings set to medium (I disable everything). But I don't know if that is even a cause/solution. http://www.sysopt.com/forum/frown.gif

As far as the glsetup - again I'm 404.

Try Run: sfc to see if you can find those corrupted files.

Maybe hang out a bit... someone will think of something...

oxOGradiusOxo
12-30-1999, 06:58 PM
Sometimes when I zip file is corrupted, the problem can be fixed by using a small DOS program bundled with the PKzip package called "PkZipFix.exe"

You can download the 8kb file from my website here. members.tripod.com/opticeuphoria/PKZIPFIX.EXE (http://members.tripod.com/opticeuphoria/PKZIPFIX.EXE)

Place this file in the same directory as the ZIP file you are wanting to fix. [i.e. c:\windows\desktop]
Then from an MS-DOS prompt, while in the c:\windows\desktop (if that's where the PKZIPFIX.EXE and the ZIP file are located) type: PKZIPFIX.EXE NAMEOFTHEFILE.ZIP <--- replace NAMEOFTHEFILE with the actual name of the file.

Depending on how big the file is, it will reconstruct the zip structure and hopefully fix those CRC errors. The new zip file called ZIPFIX.ZIP (or something similar) will be placed in the same directory you're currently working in. Open that file and see if the same errors occur.

I've had this same DOS zip package since I bought my 1st 486DX2 computer. The PKZIPFIX will work on *most* corrupted zip file depending on the error.

Any more questions?

Ladies and gentlemen.. we have a winner!
=[Gradius]=

Nixona
12-30-1999, 08:56 PM
Nope, Didnt work. Still get the same errors. It says it reconstructs structure, but stil have the problems.

oxOGradiusOxo
12-30-1999, 09:40 PM
This is a little easier to understand, and may help you out better than I could explain it. http://www.sysopt.com/forum/smile.gif

A CRC error indicates that some data in your Zip file is damaged. CRC stands for “cyclic redundancy check”. It is a calculation made from all the data in a file to insure accuracy in transmission. When you add a file to a Zip file, WinZip calculates a CRC value for the file and saves the value in the Zip file. When you later extract the file from the Zip file, WinZip calculates the CRC of the extracted file and compares it to the value stored when the file was zipped. If these two CRC values do not match, the file that was extracted does not match the original file, and WinZip will display a “CRC Error” message.

When the data in a Zip file is damaged, it may not be possible to extract all of the files from the Zip file correctly. Damaged data can affect the entire Zip file, multiple files, or just one file.

Why CRC Errors Occur
There are many possible causes for data damage. Among the most common is telephone line noise or some other transfer error when downloading a Zip file from an online source such as the Internet, CompuServe, or AOL. Such an error can introduce invalid data into a Zip file. Some other possible causes include exposure of disks to excessive temperatures or magnetic fields, cross-linked disk sectors, and mechanical problems with disk drives.

What to do if a CRC Error Occurs
The best solution to the problem of a damaged Zip file is to try to obtain another copy of the file. For example, use your backup copy of the file or get a new copy from the original source. If you obtained the Zip file by downloading it, then downloading it again will almost always solve the problem.

Possible corruptions:
From Internet ---> Hard Drive - Phone Line
From Internet ---> Hard Drive - Hard Drive

Check your phone line first. If you can hear any static on it listening through a phone, then it's enough to cause problems and amke your modem lose packets and corrupt data while on the internet. You can have your phone company come over for free and check the phone lines to see why you're getting the bad static. You might also want to replace the phone cord running from your modem to your outlet.

If your hard drive gets hot or if your system is overclocked, the hard drive can start to corrupt your data and cause all kinds of wierd system errors. Easiest way to fix this, don't overclock OR cool down your case a little.


Why.. you shouldn't have? Oh, you didn't..
=[Gradius]=


[This message has been edited by oxOGradiusOxo (edited 12-30-1999).]