| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 72985 | 2006-10-03 12:43:00 | CRC incorectly reporting errors | Ire (10920) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 488933 | 2006-10-05 07:50:00 | yeah crc is good, wheres the rust sorry? :D |
jesse_jax (9283) | ||
| 488934 | 2006-10-06 00:37:00 | GF's suggestion of bad memory is still valid: the mention of .BAT files perplexed me. ;) CRC errors are very often an indicator of bad memory. Downloads should produce an error message if something has gone amiss in the transfer; reading a disk should give a disk error message. .CAB files are compressed, and carry a CRC (cyclic redundancy check) code which is compared with the result of a calculation carried out by the decompression utility. Decompression requires a perfect file. If the file (as "seen" by the utility) isn't exactly correct, you will get a "CRC error". The commonest cause of that is bad memory. It might mean that the decompression is using memory areas which isn't usually in use (.CAB files are often big -- that's why they are compressed) or areas which usually just contain (and corrupt) data, which frequently does no harm, except causing programmes to give wrong answers. :groan: If you are lucky, it will crash the OS. :D So test the memory. |
Graham L (2) | ||
| 1 2 | |||||