Engineer Executes Elaborate Revenge via Fake Disk Formatting Script
A former engineering student uses Borland C to orchestrate a long-term workplace prank.
1The Messaging Lab Environment
In the late 1990s, an engineering student named Joe worked at an Australian mobile carrier. The office culture was defined by frequent practical jokes, ranging from confetti traps to hidden prawn heads. While these pranks were common, one specific colleague named TF escalated the situation by constantly startling Joe with loud noises.
2Escalation of Workplace Harassment
TF frequently snuck up behind Joe to roar in his ear, aiming to provoke a physical jump. Joe found this behavior repetitive and unoriginal, leading him to plan a definitive act of revenge. He waited until his final week of employment, which coincided with TF attending a professional conference, to execute his plan.
3Technical Execution Strategy
Joe utilized the Borland C compilers installed on the office PCs to develop a deceptive program. The script was designed to mimic the visual interface of an MS-DOS disk formatting operation. To increase the perceived authenticity of the threat, the program wrote junk data to a temporary file, causing the disk activity light to flash.
4Automation and Timing
The engineer integrated his script into the autoexec.bat file to ensure automatic execution upon system boot. He programmed a specific delay, ensuring the prank would only trigger approximately five to six weeks after his departure. This strategic timing allowed Joe to be safely out of the office before the psychological impact occurred.
5The Moment of Impact
Weeks after Joe left the company, he received a phone call from a former colleague. The peer confirmed that TF had been terrified by the fake formatting screen, believing his data was being permanently erased. The program concluded by displaying a message that revealed the entire operation was merely a harmless prank.
6Psychological Warfare Tactics
By leveraging system-level automation, Joe transformed a mundane office computer into a tool for psychological retaliation. The use of the autoexec.bat file demonstrates a sophisticated understanding of legacy operating system behaviors. This approach ensured that the target experienced significant distress without actually causing any permanent data loss or system corruption.
7Professional Boundaries and Conduct
The incident highlights the thin line between office camaraderie and disruptive behavior in high-pressure engineering environments. While the prank was technically harmless, it reflects the potential for toxic dynamics when employees feel unsupported. Joe’s decision to leave the organization before the prank triggered suggests a calculated exit strategy from a difficult environment.
8Legacy of Workplace Pranks
This story serves as a reminder of how technical skills can be repurposed for non-professional agendas. While the outcome was viewed as a success by the perpetrator, such actions carry inherent risks in any corporate setting. Modern IT security protocols would likely prevent such unauthorized script execution on contemporary office workstations today.