CompuServe Messages

re: late night party girls That was a great story! *8^) I have what I consider a good story, although it's off topic. Here it is, in case you're interested: A few years ago, when I had an A2000 (I use an A3000T now), I was running a local bbs called Viking. There was a local hacker who had been going around calling PC BBS's, getting them to drop to DOS, then reformatting their hard drives. This action was usually preceded by loads of offensive messages directed at various people and naturally resulted in the guy being booted off of the system. This became his justification for that type of revenge. In those days, bbs's running 500mb hard drives were not common and when I'd hear how they're data was wiped out. In many cases, they didn't have a recent back-up of their hard disk. They were caught off-guard by this guy and he knew it. Sooo, I fired off some messages to him when I spotted his alias on another system. Naturally, this got his back up, so he soon found out I was running a bbs and registered under a false ID, using someone else's telephone line. Soon afterwards the offensive messages and threats started appearing. What he didn't know was that I was using an Amiga and the ansi codes he was using to try and get the computer to drop to DOS weren't working. I don't think the guy had a job because he spent over a week calling all day and night, tying up the line, trying to kill my bbs by stopping users from accessing the system. Some users managed to get on and were informed what was happening so that they'd hang in there with me until I resolved the problem. Here's my solution (finally): I theorized that there was a good possibility that the term he was using was ansi-sensitive. (What's good for the goose…) So, I dug out some old docs on PC ANSI codes and put together my little suprise. I could have had my suprise easily automated, but I wanted to be there to "push the button" when he called again. So, I had it set up to activate when I hit a macro key. He called, and I hit the key. Before proceeding, my little ansi-bomb displayed a note to him that basically could be summed up as "Nutz to you!". Then the ansi code flowed right into his system, catching him totally off-guard. In under 2 seconds, my bomb reconfigured his keyboard, blanked his screen and cursor, and just generally screwed his system up really well. A day later, after resetting everything, he called back and I happened to be there again. Just as he began saying "F*** you!", I hit the macro again. After that, he never called back. Awwww… I shared this simple solution with other Amiga and PC sysops and noone was bothered by him anymore. The PC sysops made their own ansi-bombs in such a fashion that would not affect the host computer. That was probably the most satisfaction I've had from that computer, outside of general applications. *8^) -= Vance =- Image Master Internet: viking@freenet.edmonton.ab.ca