<![CDATA[Coworker just ran into a utility that, when trying to save a file, bailed with a scary warning because the file size was a multiple of 4096.]]>Coworker just ran into a utility that, when trying to save a file, bailed with a scary warning because the file size was a multiple of 4096. This was one of the Ancient Errors... (and yes, adding a newline char solved the "problem")

]]>https://board.circlewithadot.net/topic/de4468e8-f9d1-49d0-8912-2d8f551a40c7/coworker-just-ran-into-a-utility-that-when-trying-to-save-a-file-bailed-with-a-scary-warning-because-the-file-size-was-a-multiple-of-4096.RSS for NodeFri, 15 May 2026 09:12:48 GMTTue, 28 Apr 2026 14:14:29 GMT60<![CDATA[Reply to Coworker just ran into a utility that, when trying to save a file, bailed with a scary warning because the file size was a multiple of 4096. on Tue, 28 Apr 2026 16:17:20 GMT]]>@danlyke it's exceedingly likely that you know, and perhaps even worked on, this particular utility. And it would have been old when you did.

]]>https://board.circlewithadot.net/post/https://social.taupehat.com/users/me/statuses/116483230298272176https://board.circlewithadot.net/post/https://social.taupehat.com/users/me/statuses/116483230298272176Tue, 28 Apr 2026 16:17:20 GMT<![CDATA[Reply to Coworker just ran into a utility that, when trying to save a file, bailed with a scary warning because the file size was a multiple of 4096. on Tue, 28 Apr 2026 15:41:51 GMT]]>@me yikes, and having ymodem flashbacks.

]]>https://board.circlewithadot.net/post/https://researchbuzz.masto.host/users/danlyke/statuses/116483090748522209https://board.circlewithadot.net/post/https://researchbuzz.masto.host/users/danlyke/statuses/116483090748522209Tue, 28 Apr 2026 15:41:51 GMT<![CDATA[Reply to Coworker just ran into a utility that, when trying to save a file, bailed with a scary warning because the file size was a multiple of 4096. on Tue, 28 Apr 2026 14:42:50 GMT]]>@ai6yr @me

There was a software copy protection system back in the dawn of time - it encrypted the executable, and wrote decryption information in the slack space past the end of some system file on disk, using the unused bytes in the last disk sector allocated to that file.

Problem was, it didn't check the length of the file it chose to write to - if there wasn't enough room in that slack space, it just happily overwrote the next sector with a few bytes of key and filled the rest with 0.

A rare occurrence, but known to have caused mystery data deletion when programs using that copy protection system were installed.

]]>https://board.circlewithadot.net/post/https://mindly.social/users/PhilSalkie/statuses/116482858719883539https://board.circlewithadot.net/post/https://mindly.social/users/PhilSalkie/statuses/116482858719883539Tue, 28 Apr 2026 14:42:50 GMT