🚀 go-pugleaf

 
      At work, I had a new manager who needed a good joke played
   on him. In the office, we had a font edit program for the IBM
   EGA monitors. He didn't know this. The program would allow you
   to edit fonts and then save them to a .COM file that when 
   executed, would load the font into memory.
     One day, while bored, I started to edit the standard font.
   With out going into details, suffice to say I made some of the
   characters interesting. Most importantly, I made the ! a space,
   so when it was typed, you would get a space on the screen.
   I then named the file !.COM (say this coming didn't you? :-)
   I then edited various batch files to include !.COM. The two most
   important ones were his AUTOEXEC.BAT and NET.BAT. So, as soon
   as he booted his screen would show funny characters. Quit by
   accident while looking through his autoexec.bat, he deleted the
   line containing !.COM (which of course looked like a blank line
   to him.) From then on, his computer booted ok, but everytime he
   logged onto the network, the screen would do funny things. Well,
   since his computer had been having trouble with the network for
   sometime now, he was convinced it was the network or hardware.
   I then one day removed the line in his NET.BAT file so things
   looked ok. But then, whenever he left his desk, I would reach
   over and type !.COM. So, it appeared to him that his computer
   was still acting funny. I finally let in and told him.
 
     He then surprised me with his creativity! (He had never struck
   me as THAT creative.) I booted my computer one day and started
   working. Everything was fine until I tried hitting the 'm' key.
   An 'n' appeared on the screen. I looked down at the keyboard,
   and hit 'm' and a 'm' appeared on the screen. But something looed
   awfully funny with they keyboard. I finally had to grab another
   keyboard and compare it key by key with mine. Sure enough 
   something was funny about mine. He had removed the 'm' and 'n'
   keycaps and switched them. He then used ANSI.SYS to edit swap
   the function of the keys. So, when I hit the newly appointed
   'm' and 'n' keys, they worked jsut fine, they were just in the
   wrong place. I fixed it immediately. I didn't let him on until
   a week later that I had found out...