There seems to be a problem with the master file table (MFT) when creating temporary files. It fragments the MFT and will not allow the system to boot up; NTLDR is Missing. Refrence:
http://support.microsoft.com/default...b;en-us;320397 and
http://support.microsoft.com/default...b;en-us;174619
I have created a document management apllication that allows users to check in folders containing documents of various file types. One of the methods I used to safeguard the project folder is to create a duplicate folder. I am using the File System Objects to manage\manipulate the files. The transfer of files from the project folder to the doc manager is done against the temp directory. In the event the process fails restoration is a matter of rolling back the data transaction, deleting the newly added files, deleting the temp directory and the users project folder is left unchanged. If the transfer takes place successfully then the temp dir and the project folder are both deleted.
In addition files that exist in the doc managers vault are renamed and flagged for deletion prior to being replaced by a revision. After the project folder is successfully transfered then files flagged for deletion are deleted. Restoration in event of an error invloves renaming the file.
I know one alternative would be to simply transfer files from the project folder to the doc managers vault. But the files are going through a compression routine and if something were to happen mid-stream it would not be pretty. The documents in the project folder are very valuable and need to be protected against error.
If you have any ideas on a better way to safeguard the documents or any knowledge of the stated problem with the NTLDR file missing I would like to here from you.
Thanks in advance.
Larry
Larry Asher