>Disabling the write caching for SMARTDRV.EXE seemed to help the file >corruption problems ( but not always, of course :-) ). As a rule ot thumb, you should never have write caching enabled on a PC. Too many chances that you'll run Windows and have it freeze. <g> One problem that I had with 2.6 was that SMARTDRV would 'remember' the previous versions of files, even after changes were made. This was more than an inconvenience when BUILDing APPlications, since the new changes wouldn't kick in at the new run-time. My solution was to have a BUILD.PRG that, before it issued the BUILD APP command, would reset SMARTDRV using: ! SMARTDRV /R