Allow me to re-post what I wrote about this last year:
Not that the Star Trek writers ever knew it, but "Court Martial" has turned out to have a fairly decent, real-world explanation for its computer glitch, which I have sussed out from working in a modern data center facility. The logic goes like this:
1) You can have tens of thousands of programs (called jobs) on a mainframe computer system. Each job does something that somebody wants done. Spock's chess program would be a job he runs on the mainframe.
2) Some of the standard, commonly used parts of those jobs ("parts" meaning frequently used blocks of code) are not duplicated tens of thousands of times; that would be stupid. For efficiency, they are packaged as mini-programs, called procedures, and stored in the procedure library.
3) When a job runs, it "calls" whichever of those standardized procedures it needs. The procedure library is a common resource available to all jobs.
4) When Finney messed with bridge surveillance video, he was creating a deep fake. He had to corrupt or disable some procedure code to get his forgery past the audit software that sniffs every job for unauthorized changes.
5) Spock's chess program called up a procedure whose code had been purposely corrupted by Finney. It kept playing chess, but at a degraded performance level.
Not that the Star Trek writers ever knew it, but "Court Martial" has turned out to have a fairly decent, real-world explanation for its computer glitch, which I have sussed out from working in a modern data center facility. The logic goes like this:
1) You can have tens of thousands of programs (called jobs) on a mainframe computer system. Each job does something that somebody wants done. Spock's chess program would be a job he runs on the mainframe.
2) Some of the standard, commonly used parts of those jobs ("parts" meaning frequently used blocks of code) are not duplicated tens of thousands of times; that would be stupid. For efficiency, they are packaged as mini-programs, called procedures, and stored in the procedure library.
3) When a job runs, it "calls" whichever of those standardized procedures it needs. The procedure library is a common resource available to all jobs.
4) When Finney messed with bridge surveillance video, he was creating a deep fake. He had to corrupt or disable some procedure code to get his forgery past the audit software that sniffs every job for unauthorized changes.
5) Spock's chess program called up a procedure whose code had been purposely corrupted by Finney. It kept playing chess, but at a degraded performance level.