probleempje met het bestand zelf?..
als dat het enige bestand is dat problemen geeft...
[google=crc errors]:
link:
What causes CRC Errors
The "Bad CRC1" or "Bad CRC2" error message is caused by the data in your TP's eeprom somehow becoming corrupted, that is some of the data has changed outside the control of the BIOS software.
Cyclic Redundancy Check (CRC) is a mathematical calculation on a block of data resulting in a number that can be used to uniquely identify the data as a "fingerprint" for a block of data.
When the BIOS performs the CRC calculation and then checks the result with a CRC that was previously stored in the eeprom and the two don't match as they should, then your TP reports a "Bad CRC" error.
Depending on the area of the eeprom involved it may report CRC1 or CRC2 etc.
Between the time you switch ON your late model TP [the ones fitted with 24RF08 eeprom] and when your operating system starts to boot, the eeprom will have been accessed about 3,300 times.
It takes very little going wrong for one of those 3,300 accesses together with the numerous write cycles to and from the eeprom to write to the wrong location, one missing clock cycle or one single glitch will do it, when that occurs you have a CRC ERROR.
Whenever the BIOS writes new data to an area of the eeprom it recalculates and stores a new CRC for that new data in the eeprom.
A CRC error can occur in a TP if there is an interruption to the running of the BIOS software between the writing of new data into the eeprom and the storing of the newly calculated CRC, it can also be caused by out of control hardware during sudden loss of power.
If you take any late model TP fitted with a 24RF08 eeprom and remove the main battery, then run it just from the AC adaptor, and during the boot process pull out the plug from the AC adaptor to the wall socket, 9 times out of 10 you will have a CRC Error, do it 3 or 4 times and I guarantee you will have a CRC ERROR!
That is a precise simulation of exactly what will happen if your TP's battery is not holding a charge and the AC power suddenly fails, while you are on an important business trip miles from home or even in another country.
NO TAMPERING INVOLVED, that's what the manufacturer may try to tell you caused the problem, not so, it's simply not a 100% foolproof design and could be a LOT better.
Complete power failure during boot, or a flat main battery or an Operating system crash can all cause CRC Errors.
As you can see there is abundant opportunity for a CRC error to occur.
You didn't design the TP, they did, you purchased it from them in good faith at a premium price because you trusted in their brand name reputation and ability to design reliable equipment.
You may be able to politely but firmly point out to the manufacture of your TP, that it does bears most of the responsibility to extract you from this predicament and that you do know that they can fix it, rest assured THEY CAN FIX IT.
You may be able to convince the manufacturer of your TP to fix the problem for you. You didn't design the TP, they did.
The manufacturer of your TP CAN FIX A CRC ERROR, they may tell you otherwise, but logic dictates that if I can fix it, so can they!
edit:
bij cisco staat
het volgende over crc (cyclic redundancy check) errors..
[
Voor 100% gewijzigd door
jazz op 10-10-2003 11:40
]
:strip_exif()/u/56825/SL1200.gif?f=community)
/u/18178/logo-60x60.png?f=community){kind=logo}
Heb je hier al tussen gekeken? [search=Draytek corrupt]
:strip_icc():strip_exif()/u/78771/sluuut.jpg?f=community)