It's well known by w2K users for the fact that many of us had 'lost' forms with a power failure :( Only automation suggested up to date was putting control panel invokation to startup which I din't take. It should be possible to do via winAPI but never tried since takes only few seconds to do manually:) Instead of control panel I go through win.explorer.

Right click on a disk, properties, Select hardware
Per disk select properties\disk propperties and remove checkmark

Cetin

>Cetin,
>
>I'll try out NTFS after I get this new machine to do everything I was able to do on my old one.
>
>I confirmed your observation about Write caching. Thanks very much for mentioning that, because I'd never have guessed! I wonder if this is common knowledge among those who use Win2K Pro, and if there is some automated procedure to avoid the extra manual steps on every reboot.
>
>Mike
>
>(SNIP)
>>
>>Michael,
>>You already have good advices. Few additions :
>>-Think of NTFS soon. It's not true you would have problems connecting from win9x machines. I have 2 partitions where one is FAT32 and win9x installed (dual boot). Sensitive data is on NTFS. I can connect to any one from anywhere (including remote from notebook -win9x- that's generally at home). NTFS is for security + its cluster size is 512K by default (1/8th of min possible on FAT32).
>>-Write caching on win2K is 'reset' to ON with each boot. It's a bug or feature of win2K and you better set it manually to OFF on each boot.
>>Cetin