Posted by: @palkat

↑

This is a forum I am really looking forward to for all the many and great memories that current and past SysOp's have to share. From the history and makings of their own BBS, to the way one would deal with the pesty youth of their BBS that just wanted access to the Warez (not that I was like that! 😆 ).  The memories of the silence and dark of night that would be interupted with a caller and the sounds of the drives spinning and lights flashing from the modem and drives.  There is just so much and like I said, I am looking forward to reading all those many great memories.

The SysOp's Lounge is also a great place for current SysOp's to share information in regaurds to networks, users, support and advice.

So with all that said there is one person that made me think of creating this forum, he has many, many great memories from his many years in BBSing past and current. He has shared a good amount of these tales with me over the years and I always enjoy hearing them and I know others would too.

So @Bucko, and all you others here is a place for your many memories and experiences to be shared with all!!! 😉 

I terrorized my users. The worst thing I ever did was buy a Multiplexer (muxer) for my Lt kernal. I would change files while users were online, one night this user of mine logged in and when he hit SB to get into the subs, I had replaced SB with a file which printed to the screen Are you going to do something in the subs or just look at the screen like a dope?? Then it returned him to the main prompt. He hit it again and it did the same thing. I then replaced it back to the original file and he did it again and it went right in with no issues. He leaves me feedback saying he thinks the BBS is broken as it wouldn't let him in the subs and the BBS called him a dope! I responded back the next day saying I don't know what he was talking about but keep an eye on things going forward. 

Another time, a local Image SysOp kept taking files I had written and removing my name from it, "Blah Blah Blah Written by Bucko" he would take out the Bucko and put his handle in. I told him to stop the BS and he continued doing it. So one day I had enough of the BS and decided to get even with him. He was running 1581, 1571, and 1541 drives. I added in the end of a new plus file I wrote, a hidden line of code. In the first line of the program I put a ad$="Bucko":gosub996 then in the line Written by it said &"Written by"+ad$ The only issue was 996 didn't exist to the eye! Line 996 was invisible In 996 it was a very simple line 996 x=8:ifad$<>"Bucko"then998

997 return

998 x=8:open15,x,15:print#15,"n0:dickwad,09":close15:x=x+1:goto998

Anyone who knows Commodore basic knows what that line will do. It formatted his drives! I waited about 3 weeks, and I get a frantic call from him that there is a backdoor in Image BBS that someone knows it and formatted his drives! What can he do to get his BBS back online??? I told him do you have backups, he said no I run on Floppies, so I said you are shit out of luck guess you have to restart everything. I don't think his BBS ever came back online. He deserved what he got. 

Like I said I was a true dick. I even wrote a replacement ZZ command. Any Image SysOp will tell you, ZZ puts you into local SysOp Mode. I had the co-sysOp of the above mentioned board kept hitting ZZ to try to get into my local mode. I wrote a +.ZZ which asked you if you were sure you really wanted to hit ZZ if you answered NO, it just wrote it to the log that the user hit ZZ and aborted it. If they hit yes, the BBS then would tell them they screwed up bigtime and they would be logged off. The program then would drop their access level to 0 and automatically create a f.HANDLE file which when they logged back on would tell them that the last time they were on the BBS they hit ZZ and were given a chance to abort yet they didn't so their account is going to be deleted. If they want to logon as a new user again they can but there are no guarantees they will be allowed access again. This user got caught up in it then had the balls to tell me I was an ass for doing it to him that it was a mistake. He lost his account for 2 months! LOL

I can go on with more things I did but then you might really think I am a dick!!!