Yes, but what is the alternative? It probably does not make sense to attempt implementing the whole support for this already deprecate NTFS-specific API which is currently known to be used by one game only, which game probably works with those semi-stubs. That is probably a matter of proper fixme output to indicate that those semi-stubs are used.
On 10/26/22 17:51, Andre Brait (@andrebrait) wrote:
Hey there,
Just calling some attention to the fact just redirecting the transactional calls to their regular counterparts might cause save data corruption in the event of a write failing midway through it.
From [this page on alternatives to the transactional I/O API](https://learn.microsoft.com/en-us/windows/win32/fileio/deprecation-of-txf)
Applications updating a single file with "document-like" data
Many applications which deal with "document-like" data tend to load the entire document into memory, operate on it, and then write it back out to save the changes. The needed atomicity here is that the changes either are completely applied or not applied at all, as an inconsistent state would render the file corrupt. A common approach is to write the document to a new file, then replace the original file with the new one. One method to do this is with the ReplaceFile API.