.

.

I avoid write caching like the plague. My first experience with it was with pre-Windows DOS 4, the thankfully short-lived version between 3 and 5 (HD volumes larger than 32 MB). MS added disk caching to DOS 4 and enabled write caching by default, without bringing it to users' attention.
 
Unbeknownst to me, my boss' 17-year old son, who was hanging around the office all summer (this is Motorola by the way, not some small operation), was put to work by a couple of my engineers doing some dirty work that they were too lazy to do (configuring new PCs for customers). He installed DOS 4 instead of the tested and approved DOS 3. These PCs were running real-time SCADA control system software with large databases.
 
Then the calls started coming in about corrupted databases. It took some time and plenty of aggravation to figure out that it was an OS issue, that the PCs had DOS 4 installed instead of 3, and then all of the time it took to figure out what Mickeysoft had done. Really p'ed off some important customers.
 
I called it the Itamar virus (the little s**t's name).
 
Write caching writes to RAM. It then needs to be written to disk. If ANYTHING interrupts that process, your destination file is corrupted. Trust me on this...there are a LOT of things that can AND do interrupt that process.
 
My recommendation? AVOID.

.

.