Microsoft Technology Licensing, LLC

Darrell L Aldrich

Alan Aitken Ramaley

Thomas W Olsen

David M Buchthal

A computer-implemented process for replacing old files having old names on a permanent storage medium with new files in volatile memory. Some of these files may be opaque files, which are old files that have become new files without undergoing any changes, other than possibly name changes. The primary steps of this replacement can comprise first saving the non-opaque new files onto the permanent storage medium and assigning them temporary filenames. An opaque recovery file listing the old name and a temporary name for each opaque file is created. A primary recovery file listing the temporary name and a final name for each new file is created. After the names of the opaque files are changed to their temporary names, the names of the non-opaque old files are changed from their old names to backup names. Then, the names of the new files are changed from their temporary names to their final names. The recovery files and the old files can be deleted. If an event leaves the program performing the primary steps in control but unable to complete the replacement, then the old files can be restored to the permanent storage medium. If an event prevents completion of either a replacement attempt or a restoration of the old files, completion of the replacement can again be attempted at a later time using the recovery files. The described processes can be applied to saving HTML documents, each of which typically comprises multiple files.

File save method for HTML files using recovery files including a list with temporary and final names for replacement files

A computer-implemented process for replacing old files having old names on a permanent storage medium with new files in volatile memory. Some of these files may be opaque files, which are old files that have become new files without undergoing any changes, other than possibly name changes. The primary steps of this replacement can include first saving the non-opaque new files onto the permanent storage medium and assigning them temporary filenames. An opaque recovery file listing the old name and a temporary name for each opaque file is created. A primary recovery file listing the temporary name and a final name for each new file is created. After the names of the opaque files are changed to their temporary names, the names of the non-opaque old files are changed from their old names to backup names. Then, the names of the new files are changed from their temporary names to their final names. The recovery files and the old files can be deleted. If an event leaves the program performing the primary steps in control but unable to complete the replacement, then the old files can be restored to the permanent storage medium. If an event prevents completion of either a replacement attempt or a restoration of the old files, completion of the replacement can again be attempted at a later time using the recovery files. The described processes can be applied to saving HTML documents, each of which typically includes multiple files.

Safe save method of HTML files using recovery files including a list with temporary and final names for replacement files

A computer-implemented process for simulating, in an HTML-formatted primary file, certain user-expected characteristics of an electronic document containing an embedded file. In response to initiating a save operation for a primary file to be saved as an HTML document, a file embedded within the primary file is detected. In turn, a support file is created for storage, in a separate storage location and physically removed from the primary file, to logically represent the embedded file. In addition, a current file list, which is associated with the primary file, is created and saved to the storage mechanism, typically the hard disk drive for the computer. When the HTML-formatted primary file is opened in a work session, the editor can open a link to each support file identified by the file list. In response to conducting a save operation for a primary file, an inquiry can be conducted to determine if a prior file list is associated with the primary document. If a prior file list is located, then the current file list is compared to the prior file list. This comparison operation is completed to determine whether support files identified by the prior file list are no longer identified by the current file list. The support files not identified by the current file list, but identified in the prior file list, are deleted from the hard disk of the computer because the corresponding embedded files have been deleted by edit operations for the primary file.

Growing community of inventors

Redmond, WA, United States of America

Darrell L Aldrich