Reply to thread

Help Support UKworkshop.co.uk:

Message: <blockquote data-quote="nickds1" data-source="post: 1516754" data-attributes="member: 14992">I think we should be careful when guessing why some application or other is becoming progressively more unreliable.The filesystem in use on a Windows box maybe FAT (unlikely), FAT32 or NTFS. It's largely irrelevant which one is in use, though NTFS has better recovery than FAT32.The filesystem is responsible solely for storing the data in the file on the storage medium; it had no say in or knowledge of the contents or internal structure of the file itself.The structure of the file is controlled by the application, not windows or the filesystem in use. Some file structures are complex and can become unwieldy and even corrupt over time due to latent bugs in the application, e.g. buffer overflows.Then we have the actual storage media. Spinning discs (the traditional hard drive) and solid-state discs (SSDs) behave in very very different ways under the hood. Specifically, their failure modes differ in cases of exceptional events and edge conditions, eg. power or media failures and timing issues.In top of all that, you have caches, specifically write caches which may be on any or none of the operating system, the PC's disc controller and the physical disc itself. If a write cache is enabled but is not a write-through cache or is a "lazy writer" and is not battery-backed, then that is yet another potential source of issues.And there's more (operating system upgrades etc), but this is getting boring...So, it's perfectly possibly for a program to seem to become unreliable over time, but the underlying reason or reasons can be complex and could lie in several seemingly unconnected areas.</blockquote>

Verification

Reply to thread

Help Support UKworkshop.co.uk:

Join the conversation!

Register today and take advantage of membership benefits. It's FREE!

Don't like ads?

Did you know that registered members can turn off the ads?