Windows 666

I'm sure you've heard of codenames before. But this ain't the one you are familiar with. Codenames are the holding names of Windows versions before they hit the final version. When we were making the beta for Windows 7, we accidentally called the beta files Windows 66.6, and you can find these 66.6 files in current version of Windows if you look hard enough.

It was just a normal day at the Microsoft office. Everyone was working, and doing their jobs normally. I got a strange call from an unknown number, kind of acting like someone needed help.

I pick up the phone.

"Hello!" I said in a kind polite manner. ""Hi there." said the voice back. I then responded, "Thank you for calling Microsoft technical support. How can I assist you today?" The voice responded: " I need help with your Windows version. I then said: "Please specify the name of the Windows version. Is it millennium, 3.1, Windows for Workgroups 3.11, 95, 98, NT 4.0, Microsoft Chicago, Windows Whistler, Windows Longhorn, Windows 2000, Windows XP, Windows ME, NT 5.0 beta, etcetera?" The voice responded: "Windows 66.6" I then responded: "What is happening?" the voice said: "I'm not the problem here, it's you." The voice suddenly turned demonic and said: "YOU'RE NEXT." The phone immediately hung up.

Just as I was about to leave my office for the day, all Windows computer showed a red screen of death, no, not from the PS2, it was the blue screen of death, but demonically altered. 66.6 started appearing everywhere on the Windows desktop and start menu, then suddenly flash red and white, and for a split second I saw the number 666, no 66.6, just 666. A rat attack on all computers in the vicinity of my computer were attacked by EMP blast, and it wasn't normal. Blood red started Illuminating the entire room, and into my eyes as well. I couldn't see the EMP blast because all the blood red was in the way. When the blood red was cleared, all computers were dead. Except for one. My computer. My office computer had stayed put. All other computers attacked by the EMP blast were dead. Just as I was about to leave again the error message sound boomed from the computer. I saw the following error: "File: hal.dll is corrupted and has had to be closed. All data related to file has been removed." Afterwards another message arose on the screen. I got the following error: "File: RSOD.exe created. Directory: not found." Another message box arose on the screen. It read: "File: 666.vbs created. Directory: C:/Windows/System32/Config/System/666/666.vbs" One final message box arose on the screen. It read: "Directory: C:/Windows/System32/ is corrupted and has been deleted. 666.VBS file moved to desktop. All other data related to directory has been removed." After that I got a Windows rsod. And when the computer Rebooted, the following message arose: "Windows could not start because the following files are missing or corrupt: boot.ini, hal.dll, 666.vbs. Please re-install a copy of the above files." What was extremely terrifying was 666.vbs was a required system directory file for my computer, even though it was created by Windows 66.6. And just like that, all the computers had died. I give you one final message: .-- .. -. -.. --- .-- ... ....... -.... -.... .-.-.- -.... ....... .-- .. .-.. .-.. ....... .-. . - ..- .-. -. ....... -... . ....... .-. . .- -.. -.-- ....... -. --- - ....... .- ..-. .-. .- .. -..