My problem “faded” away after i read this article on the Plextor Website:
Article ID. G00012
Why do I get data corruption or CRC errors with Windows XP or NT?
In rare instances, the Windows Operating Systems will generate event errors when writing data to a Plextor PX-W2410TA, PX-W4012TA, or PX-W4824TA, or generate CRC (Cyclic Redundancy Check) errors when opening large self-extracting files from the CD. The data errors may cause the systemâ€™s UDMA driver to step down to PIO mode. PIO mode does not use CRC to check for data errors. PIO mode is much slower, and the system must be reset to UDMA for optimum performance.
This situation will generally occur when the IDE cables are routed too close to each other, or run parallel to each other for more than a few inches. The phenomenon is called â€œcrosstalkâ€, and is caused when signals from one cable or wire are picked up by another cable or wire that is too close. The higher data transmission speeds of UDMA can cause â€œringingâ€ of a signal, generating an electrical field that can affect signals on an adjacent cable, much like a radio picking up static when near high-power electrical lines. Crosstalk can be reduced or eliminated by an air gap between cables.
Some vendors coil up the cables or tape them together for â€˜neatnessâ€™, or run one cable atop another when routing from the motherboard to the peripherals. The solution to crosstalk is to separate the cables by a few inches, or replace the standard IDE cables with UDMA 80-pin cables. The UDMA 80-pin cable uses the same 40-pin connector as the standard cable, but adds ground lines between the signal lines to reduce or eliminate crosstalk.
It is also possible the system motherboard ATAPI controller may not meet timing specifications. Installing the jumper on the drive UDMA connector quite often will alleviate this problem.
Now i bought two shieldef UDMA-133 cables and everything is working fine.
Maybe you can include this in a Sticky Thread.
Greetings from Germany