7 ms·
Damaging the 'environment' was allowed, so it's disappointing not to see any code that tries to disable or destroy the hardware by: * Overheating or overvoltin
by FatalLogic 12y ago
Damaging the 'environment' was allowed, so it's disappointing not to see any code that tries to disable or destroy the hardware by:
* Overheating or overvolting the CPU, GPU or other components
* Erasing boot firmware or boot settings stored in flash memory (and rebooting)
I know there are protection mechanisms, which may be impossible to circumvent, but you can try...
- maaku 12y agoThere was the HCL (halt-and-catch-fire) opcode as a submission...
- FatalLogic 12y agoThat opcode promises so much, but delivers so little :/