Category : Various Text files
Archive   : GFILES.ZIP
Filename : BBSLOSER.TXT

 
Output of file : BBSLOSER.TXT contained in archive : GFILES.ZIP
_______ _ _______
/| \\ / \ // |\
(( //| _____\\<=--=--=--=--= =--=--=--=--=>// ___ |\\ ))
\\ ////| | \\ Written by: // / \ |\\\\ //
//\\ // / | | \\ // / | \ \\ //\\
(( ))< <<<| | >> The Trash Compactor << | |>>> >(( ))
\\// \\ \ | | // \\ \ | / // \\//
\\ \\\\| | // Documentary: The LoserUsers \\ \___/ |//// //
)) \\| //<=--=--=--=--= =--=--=--=--=>\\ |// ((
\|_____// \_/ \\_____|/

.lh9

Introduction:

Inevitably, I'll be asked this question, so let me address it now. "Why did
you write this file ?".
ùÍ
The answer is simple. After being subjected to losers for 20 months of
BBSing, it sometimes becomes difficult to cope with them. Much the same way
you'd feel if you lived close to the gay populace of San Francisco, seeing
these people becomes a matter of fact. There's not much you can do to prevent
it... So what do you do about them? You use them as a topic for generating
humour, although of course they themselves generate quite alot of humour
without any prompting whatsoever.

This file is dedicated to the SysOp who has sufferred many months of facing
the reality of the cranial capacity of the average "Joe Public" out there, and
is close to packing the whole thing in out of utter frustration.

I want to stress that this is in essence a "war" between LoserUsers and
SysOps, and the SysOps must not give in! It is possible to defeat the
LoserUser, and this file will hopefully help some poor soul out there who's
sufferring from the LoserUser Blues. I may not be much of a psychiatrist, but
I know what I've gone through and what has given me the strength to continue.
Thus, what follows is a comprehensive "LoserUser Manual" if you will, touching

on just about all the topics concerned with those mindless fools who log onto
your system day and night. Sit back and relax folks, cause this could take
awhile.

Heartfelt thanks go to:

- The LoserUser who designed the credits at the top of this file.
- LJS for inspiring me to write this.
- Inspector Gadget without whom I'd have been unable to write this from an
experienced point of view.
- To the pre-pubescent Rodent who has supplied me with much humourous aspects
on the average 15 yr old (actually, he's a decent guy and undeserving of the
critique, but how can I resist?)
- Several SysOps around town who have shared experiences with me leading to a
few examples of losers in this file.
- All the LoserUsers of T.O., without which this file could never exist.


* Disclaimer *

This file contains no proper names, in order to protect their identity. Any
names which in some way, shape or form, resemble real-life people is purely
co-incidental. If this file is offensive to some, please be reminded that it
is intended as a source of humour only, and no intention of direct criticism
is intended. The author can in no way, shape or form, be held responsible
for damages incurred, directly or indirectly, as a result of this file,
whether they be physical, psychological or otherwise. Parental discretion is
advised as the material that follows may be offensive to some.


Part 1: The Types of LoserUsers.

In the BBS community, you can usually fit losers into one of the below
categories. More likely than not, the loser will fit into several different
categories simultaneously. A brief description of the categories follow:
1) The BBS loser.
This guy is your typical brainless loser. Most losers fall into this very
general category.
2) The "Leech".
This is the guy who is obssessed with the acquisition of "wares". He will
do anything in his power to increase his library. That usually includes
sucking download areas dry, hence giving the term "leech".
3) 64-Syndrome.
This is a general disease suffered by some people in the community. While
based around the Commodore 64, the disease also affects various other
users, including Atari and Radio-Shack users. These people seem to have
been somehow adversely affected by the nature of their computer
(although that doesn't neccessarily mean that they would not have shown
"loser" symptoms had they bought an Apple or IBM).
More often than not, this disease is just a more precise manifestation of
the first in the list, with the difference that they cannot comprehend
some very simple and standard BBSing concepts.
4) The "hacker".
This is an unfortunate category, which really does the term "hacker" no
justice, yet is the only appropriately technical term which I can think
of. These people like to think of themselves as hackers, but a much
better term is "pest". They incessantly try to crash BBS'es.
5) The non-descript user.
These people aren't full-blooded losers, but generally, these are the
people who log onto BBS'es and never post a single message; if it weren't
for the userlog, one would find it hard to believe just how often they
call and tie up the system.
6) The Non-SysOp.
This is perhaps the most serious of the types of losers. These people,
for one reason or another, decided that they wanted to become a "SysOp"
(I use that term loosely!). Not even the psychiatrists can figure these
people out, but I will take my shot at it.

All these types of users plague BBSes in their own way; some groups are more
prevalent than others in various situations. It is very important that you note
the various percentages of types of losers who frequent your individual system;
based upon these facts, only THEN can you form a battle-plan.



Part 2: The Traits of a Loser.

We will take the groupings one by one, and discuss the signals prevalent
within each category. There are many things that will give a loser away, and
its virtually impossible to cover them all, however I will try...

Type A: The BBS Loser
The most important part of the general BBS loser is that he(she?!) has
absolutely no brain whatsoever. This lack of grey matter expresses itself in
many ways, and thus there are perhaps more examples of something that indicates
a LoserUser in this category than any other. Unfortunately, the lack of a brain
precludes these social outcasts from being able to understand (much less
perform) many of the basics of BBSing.

Firstly, these people cannot understand instructions. Now, perhaps you
cannot quite grasp the severity of what this means! Think of all the places in
a BBS where people are asked to follow rules, both explicitly and implicitly.

a) Logging on for the first time, it is the norm for users to be subjected to
some sort of a message which they cannot interrupt, outlining the "rules" of
the BBS. Apparently, LoserUsers never read this message, and use their
ignorance as a crutch when a SysOp gets pissed off at their failure to
comply with the regulations of the system.
SysOp: What the hell is wrong with you, you moron? Didn't you read the
RULES?! It says "No Aliases". Can you understand that, or are you
saying that your name is REALLY "Psycho Clam"?
Loser: Hello?
SysOp: YES!! Can you read?
Loser: Ya
SysOp: What did the rules say about aliases?
Loser: I dunno
SysOp: Why not?
Loser: I didnt see nothin on aliases
SysOp: It says "NO ALIASES". Wouldn't you say that that means that you
can't read?
Loser: Well I didnt see it ok
SysOp: Obviously. If you must, call back and log on again. This time try to
read the rules.
* Connection terminated *

b) Losers seem to have EXTREME difficulty entering their phone numbers. How
this is so difficult has always and continues to baffle me. Remember, don't
let it bother you. Its all a part of the LoserUser scheme to drive us into
the asylum THEY used to be in. Here's a classic example:
BBS: Enter your phone number: A/C-###-####
Loser: (hits return)
BBS: Enter your phone number: A/C-###-####
Loser: (hits return)
BBS: Enter your phone number: A/C-###-####
Loser: 000-0000
BBS: Incorrect format
Enter your phone number: A/C-###-####
=--> SysOp interrupts...
SysOp: Whats your problem? Do you know what a phone number is?
Loser: Ya
SysOp: Do you know what your phone number is?
Loser: 545-6754
SysOp: Ok, so enter it. And remember to enter your area code.
BBS: =--> Chat ended
Enter your phone number: A/C-###-####
Loser: 545-6754
BBS: Incorrect format
Enter your phone number: A/C-###-####
=--> SysOp interrupts...
SysOp: Holy shit! Do you know what an "area code" is?
Loser: Ya
SysOp: So put in your area code! Now whats your phone number?
Loser: 545-6754
SysOp: With your AREA CODE!
Loser: 416-545-6754
BBS: =--> Chat ended
Enter your phone number: A/C-###-####
Loser: 545-6754
* Connection terminated *

c) Perhaps one of the most common displays of the inability to read comes in
the posting of messages. How many times have you seen people try to end a
message with "done", "/e", "/ex", "/es", ".s" when it clearly says that you
should use "/s" to "send" the message? Even worse is the guy who after
trying 2 or 3 of the above, just starts hitting until the message
is full. These messages are hard to read as the text scrolls off the screen
before you have a chance to read it all. But then again, being written by a
loser, it's probably to your benefit that you couldn't read it.

Then, of course, so often messages posted in a conference deal with some
topic which plainly should be posted in some other conference. Again, these
losers just don't seem to understand that the title of the conferences
should somehow give them an idea of where to post something. Then, there's
the loser who posts the same message on 3 different conferences, just to
make sure all the losers read it (losers often aren't even aware that the
other conferences exist, let alone what they're for).

d) Now, invariably, SysOps find themselves chatting with losers. This is
perhaps the single most difficult and taxing chore of running a BBS. A solid
loser can drive you to drink at the best of times, and force you into a
state of temporary insanity at worst (to date, thank God, we still don't
know of any SysOps who committed suicide following a chat with a loser).
Firstly, losers must be taught that it is "chat" protocol to leave a blank
line between what they say, to indicate that they are finished saying
whatever and are now waiting for a reply. Chatting with a loser is so boring
and frustrating because of the speed he's typing at, without making the
SysOp decide whether or not the gumby has finished typing. Next,
understanding a loser is sometimes a difficult chore. The loser seems to
have his own vocabulary. Essentially, they use many words which are obvious
misspellings of regularly used words. The only theory I've been able to come
up with that accounts for this bizarre behaviour is that they do this to
cover up the fact that they make spelling mistakes every 5 or 6 words, so
this way you're never sure if he misspelled it, or whether its just another
part of his regular "vocabulary". Remember that losers (based on the number
of times they select the main menu as their command) have a hard time
remembering the 20 or so options available to them on the BBS, let alone the
English language. Chatting with one of these people is similar to talking
with a caveman (or Arnold Schwartzenegger; only difference is that Arnie's
smart... He carries a gun with him so no-one bothers him, and he never logs
onto a BBS). What is really disturbing are situations where you heap sarcasm
and criticism on a loser, and he doesn't even realize it! An example:
SysOp: Good day. What did you want to ask me?
Loser: Wow, are u the SysOp?
SysOp: No, I'm the zit on your face.
Loser: Iv never talk to SysOp be4. This is awesum!
SysOp: Whatever. What do you want?
Loser: How do i get more acces to the BBS?
SysOp: If you contribute, call regularily, and prove yourself worthy of a
higher access level, you'll get it.
Loser: So what button do i push?
SysOp: What?!
Loser: How do i get acces?
SysOp: You don't.
Loser: Howcum?
SysOp: Cause I said so.
Loser: Ok. But like can i get more time on the BBS?
SysOp: No.
Loser: Oh. U r a k00l d00d thow cant i get to do more stuff?
SysOp: No. Listen I have to split. Talk to you later.


Type B: The Leech

This is the newest victim of a highly contagious virus that is spreading
throughout the land of micro-computing; I refer to it as "NWS" or "New-Wares
Syndrome". You might wonder why I use the term "victim"; I must stress that it
is a VIRUS. Many losers catch it, it might be the AIDS of computing. Again, you
must be a loser in order to catch it, and once you've got it, it sort of dwells
on you for awhile before eventually levelling off at a certain plateau and
finally receding. This NWS cycle may last anywhere from one to six years,
depending on the individual. Simply put, the virus affects the central nervous
system of the brain, which results in some form of insanity when the person is
faced with the possibility of obtaining new software for his computer. In the
very early manifestation, the bulk of interest lies in games; later more
advanced strains of the virus cause the person to place more interest in
utility programs, some business application software, and other miscellaneous
material. Perhaps one of the most heart-wrenching cases is the person, who in
his crusade for new wares, decides to put up an AE or CatFur line in the hopes
that it will bring new wares to him (these people have many things to learn
about users and their willingness to upload!). NWS feeds on the ego/power trip
of the individual who things he's a big "stud" whom everone (other LoserUsers)
admires and looks up to. They will do almost ANYTHING to obtain that new ware.
This includes sending literally tons of e-mail asking various other LoserUsers
if they want to trade, and giving the their latest list of "tradeable"
commodities. The funny thing is that very little ever comes of these messages,
because the person who receives it merely sends back a list of his latest
wares. More often than not, because they are on an ego-trip, they disdain
trading with someone they don't know, because they firmly believe that they
have more wares than the other person, and thus don't want to "give up" any of
their "super-wares" to get something else. The net effect is that it wastes a
whole pile of disk space and nothing else. Usually a post on the "wares"
conference is as much a statement of position as it is a request for new wares.

Of course, this person displays symptoms of NWS in other places besides just
BBS systems. Generally they are highschool students (12-19 yrs old), and as
such, the school they attend is the major source of their wares. They have no
scruples, and will engage in radical tactics, such as stealing disks belonging
to a rival ware-monger. The school is their showcase for new wares; they derive
ultimate satisfaction from being the first person in the school to boot up a
new ware; they claim (naturally) that the game (it's usually a game) is
"totally, super-awesome, absolutely incredible, fucking amazing", etc. Rivals
of course try to play down the significance of the ware, and just boot up their
latest ware on the nearest possible computer and try to drag away some of the
other guys audience. Contacts are meticulously made and kept; NWS sufferers
seem to sacrifice their ego-trip for a select number of people, referred to as
"contacts", who get them the majority of their new wares.

An advanced "leech" will, if he has enough status, become a member (or,
heaven forbid, even START) a user group. (Some people refer to them more
accurately as "LoserGroups".) This group is usually truncated to a three-letter
acronym for an equally useless long version of the name. These groups
represents the ultimate plateau in the complete ware-monger. There is only one
thing better than knowing "the coolest, most awesome dood from the states", and
that is being part of "the coolest, most awesome usergroup" in town. The only
good thing about the members who actively participate in these groups and
widely publicize their participation (by signing all their messages, even
e-mail, with the insignia of their awesome group; especially on software they
have acquired, in an attempt to make people believe they "cracked" it, and also
on any wares uploaded to AE/CatFur lines).


Now, eventually, the people who suffer from NWS and have some amount of
cranial capacity begin to transform. The first sign is the down-play of the
significance of games. Instead, they turn to the art of placing their aliases
on the various software packages that they own. After they have mastered this,
and placed their name on a sufficiently great number of software packages, a
very few people progress to the next stage of computer literacy. Some (gag)
will actually begin to program (in BASIC of course). A fewer number still will
become "crackers" and a very miniscule number will become machine language
programmers, leaving only bad memories of the "ware-monger days". An
unfortunate part of the NWS virus is that in some cases it directly leads to
the sufferer becoming a "SysOp". Of course telecommunications is an excellent
method of acquiring new wares. Because of this, some develop the idea that if
they set up a BBS or AE/CatFur line, that new wares will come to their front
door. These systems are indeed to be avoided. Fortunately, this stage
eventually wears off, and the system goes down, allowing intelligent people to
heave sighs of relief.


Type C: 64-Syndrome

These are the users who have been misled by some salesman that they do
indeed own a computer. They can be some of the worst losers you will encounter
Šon a BBS because they are ignorant even though they don't think they are.

Most C-64 users stick to C-64 BBS systems (thankfully), but those who
venture from their own territory have a habit of terrorizing other systems...
Now, before I get myself into really hot water, let me tell you that there are
exceptions... Not ALL C-64 users are "losers" (Come on... Amongst those
thousands of people, SURELY there must be at least one?!). There are a number
of C-64 users who are ignorant, and freely admit it. Others just sit back and
"observe" rather than participate (thus becoming another type of loser, the
"nondescript user"), in some cases fortunately for the rest of us. Some are
just out exploring and are in some awestruck state of mind that is consistant
with a 10 year old getting an autograph from Mr. T. But it is the others that
we must be concerned about; the C-64 owner who has been brainwashed to such a
degree that one would think he's a KGB implant. These people seriously believe
not only that they own a computer, but are proud of it and even worse are
completely convinced that their computer is "the best".

Firstly, there's been a rumour circulating that 95% of C-64 losers were
previous residents of mental institutes. There is no truth to this. It is the
direct fault of their upbringing, and thus the blame should lie completely with
the parents (after all, if it weren't for them, we wouldn't have to put up with
the slime...). It is a simple fact that most C-64's are bought by misinformed
parents of 12 year olds, the victims of equally ignorant salesmen. The child,
subjected to this machine in early stages of development seems to be vulnerable
to some form of brain damage, especially in cases where the child was forced to
justify and defend his machine against others.

As these people mature, they seem intent on sticking to their opinion that
their parents were right, and that they are the owners of an amazing machine.
When you know of someone like this in your community, it is usually a pretty
simple matter to merely avoid the nuisance, and not get into any "deep"
discussions with him. However, when these people acquire "modems" for their 64,
they are then lethal weapons. These scourge plague decent BBS systems, and is
the singly most frustrating person for a SysOp to deal with. Typical of their
cranial capacity, it is easy to spot a 64 Syndrome sufferer; he's the guy who
posts a message "APPIL SUCK SHIT" on the main conference. Why post it on the
main conference when there's a "war" board set aside specifically for people
like him? He doesn't even know that it exists! Remember that 95% of all C-64
BBSes consist of one general conference which includes public messages and the
closest they get to "e-mail" messages. Why, in perhaps the most classic case of
ignorance with regards to multiple-conferencing, one bright C-64 user, when
asked why he didn't post a message about a new BBS in the BBS board replies,
"I don't know the number"... You don't get it, do you? I myself said "hunh?" a
few times before I realized the truth of the situation and was sent onto the
floor uttering peals of unbounded laughter... Why, this moron actually thought
that you had to phone another number to be able to post on that "board". Holy
shit, folks, think of the problems writing a quick-scan routine for a system
like that would pose!

Another excellent way of recognizing the C-64 user, is by analyzing what he
types... And, no, I'm not referring to the fact that nothing he says makes any
sense, but rather that he has never heard of "uppercase characters". Everything
is typed in lowercase, and it's only the fact that most systems translate
lowercase to uppercase that the guy manages to enter any actual commands. Be
carefull though, because some lowercase-only users have everything appear in
uppercase. The reason for this is that, naturally, they cannot grasp the idea
of "configuring" the BBS to their capabilities and thus when it asks them if
they have lowercase support, they just hit and it assigns the default of
uppercase only.

Here's another sure-fire way of identifying a user as a C-64 user...
Remember that on their BBSes, you post a public message by addressing a message
to "ALL". Well, if you spot someone in the e-mail section apparently trying to
send someone a letter, and then see:
BBS: Send mail (Y/N) ?
Loser: Y
BBS: Send to [First Name] ?
Loser: ALL
BBS: [ Last Name] ?
Loser: ALL
BBS: User: [ALL ALL] Confirm (Y/N) ?
Loser: Y
BBS: Post public messages in the conferencing system, you Commie Loser!

Also, some of these people do not understand that Apples are DIFFERENT from
C-64's... They seem to believe that they can download some Applesoft program,
or some Daltoned game and expect it to run on their machine.

There are no doubt some other signs of C-64 users that you will notice as
time goes by, but the preceeding are the most blatant examples, and as well as
being a pain to the system, can also be used for comic relief. More on that
later.

Type D: The "Hacker"

This is the idiot who tries incessantly to crash your BBS. These "hackers"
can attain several plateaus of achievement. There are several "classic" methods
of crashing BBSes, which these people seem to think might still work, and it is
through these that you can recognize this type of loser.

What follows is a list of commonly used techniques to try and crash a
system:

a) When the BBS asks for Usercode/Account #, the gumby will just start entering
a continuous stream of carriage returns... The BBS gets bored after awhile
and hangs up.
b) The fool will try to sign on as record #1 (Ie: Account of 1), and then try
to "hack" the password. A classic laugher is someone trying to use "M1PQ" or
another pswd that was one of very few possible under Net-Works. It's even
funnier when the system isn't even running on Net-Works...
c) The guy will log on as new, and try to use the name "SYSTEM OPERATOR" or
"SysOp" or the name of the SysOp.
d) Another technique is to log on with the name of the SysOp, except to leave a
blank as the first character of the name.
e) Here's one thats a little more complex... They try to hang the system by
hitting Ctrl-S and then hanging up.
f) Or how about this one? The gumby calls, and as soon as it connects, he hangs
up and calls back as quickly as possible. He tries this over and over, until
he finally gives up.
g) Then, there's the infamous usage of 9E99 at various prompts...
h) How about the fool who tries to overload memory by entering the fullest
possible message over and over again?
i) For those systems that used the Micromodem or APL/SSM card, there was the
infamous Ctrl-Y feature...

Now, of course these are just a few of the many methods these people will
use to try and obtain access to the system. They'll try typing in various
different words and control characters at the password prompt, and the list
goes on and on.

These people have some sort of a brain disorder which leads them to believe
that they are "great", "awesome", etc... They couldn't possibly discover a new
way of crashing a particular system; they merely use information that they've
heard elsewhere. If people would only stop writing "How to" g-files, we'd have
alot less losers of this type. This is the same guy, who after reading a file
on "How to Build a Thermo-Nuclear Device", actually tries to build it. He gets
snagged when he gets to the "weapons-grade plutonium"; his daddy doesn't work
for a terrorist organization. He tries to substitute lead (he thinks the
graphite in pencils is lead) and catches shit from his folks for making a mess
of the house.


Type E: The Non-descript user

If indeed there can be a "good" loser, this is him. It's hard to even notice
that he exists... The only time you become aware of all the non-descript users
ÿûare occasions where you swear and curse and ask yourself, "Why does no-one
ever
post any messages?". These people are the perfect example of a malignant
tumour. They are active users of the BBS; they regularily read the new material
on the system, but the SysOp only realizes that they are there when he looks at
his log to find these names he's never heard of before. He comes in and sees
that so far he's had 35 calls today; he quick-scans and finds two new messages,
both of which were posted by his co-SysOp.

Frankly, what the non-descript user does is use up a record in the userfile
and tie up the system. That's all. These are the same people who will
graduate from highschool, or wherever, without having any idea of what they
want to do with their lives, and subsequently go on to be wealthy construction
workers.


Type F: The Non-SysOp

By far the most unfortunate classification of loser, and the type of guy who
gives BBSing and SysOps a bad name. These people are solely responsible for
turning hundreds of people off BBSing...

But, by another token, this is the easiest person to spot, and the easiest
to ridicule. Now, first, lets try to establish how a Loser-SysOp is "born"...

Most importantly, it seems that in almost ALL cases of the loser-SysOp, that
these people were active BBS LoserUsers at the time at which they became
"SysOps". Below are a typical series of events that leads to a loser wanting to
become a SysOp, and how to "diagnose" that type of BBS Loser-SysOp.

Ša) Joe is a type B loser; a "ware-monger". He, being obsessed with the
acquisition of new "warez", has come up with a brilliant new idea on how to
obtain them, and become recognized as a "stud" at the same time... He
decides to put up an AE and/or CatFur line. This way, other ware-mongers
like himself will call, and he (being a stud) forces them to give him some
new "amazing, totally awesome new ware" in order for them to log on (just to
discover that he's running on one or two 140K drives with nothing on them).
Typically, the person also labels his system "elite" in a flagrant attempt
to attract the larger names in ware-monging. Of course, these losers also
are forever in quest of having "the most AWESOME AE (and/or) CatFur line" in
the area, but this poses a problem... To be able to meet the challenge of
this label, they cannot simply put up a system... it has to be unique, and
the only way to put up a unique system is to "do some mods". (Ahem...) This
can be translated as "making modifications to the system's program". But,
unfortunately for them, this requires "programming skills" of which they
have none. They then go on a search to find some well-known "ware-monger"
who will agree to do the "mods" for him.

This type of system is almost always down, as the loser-SysOp is usually
using his computer (trading with some ware-monger, or ha... calling other
AE/CatFur lines). The system is also down for periods of time while the
ware-monger of the "SysOp's" choice fouls up the program. One more excellent
way to spot this type of person is to look for BBSes that are forever saying
"We are down cuz the computers broke", or "We'll be down for 3 weeks 'til we
get these amazing new mods done!".

Another method of detecting this type of person is to examine the hardware
that the system runs on. If you spot a BBS/AE/CatFur that runs on two 140K
drives, well, thats the classic loser-SysOp. (I mean, I've known two people
who've put up ...ahem... tried to put up a system on 1 drive, but atleast
they were intelligent enough to realize that they couldn't possibly keep it
up (let alone add AE) and gave up. But the person who firstly runs a BBS off
one drive and THEN also insists on running CatFur off the second drive...
Well...! My friend, you've just hit the jackpot; the loser-supreme... This
person should never have found his way into telecommunications, or computing
for that matter because obviously he neither has the ability to reason, nor
does he understand basic hardware concepts. Folks, these are the people upon
whom I heap the most scorn... One to three conferences, with never more than
five to ten messages per conference, an "elite" label (he doesn't have the
disk space for more than 20-40 users anyways), a system that gives you a
system error 4 times out of 10 when you either try to send mail or post a
message, and then, to top it all off, a useless ware on D2, sometimes one
side of a four-sided game (obviously the rest won't fit...). The hearty and
sadistic people (like me) have a field-day with these wimps... Now, in
keeping with my opening statement, I'm not going to mention names or systems
but I think that those of you who closely follow the Toronto BBS scene know
exactly where I take this information...

b) Herbert is your typical 12 year old proud owner of a Commodore 64, and has
seen how "awesome" modems are from the home of his best-friend. He instantly
sets his aim on putting up a BBS... After several months, he finally has
enough money to buy a "modem", and puts up his BBS. For several months, the
BBS serves its purpose; amongst his peers, he has risen to the level of a
true "stud". His being the SysOp of a BBS gives him just about the same
status as having a 16 year old, well developed and gorgeous "chick".
However, problems arise...




  3 Responses to “Category : Various Text files
Archive   : GFILES.ZIP
Filename : BBSLOSER.TXT

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: http://www.os2museum.com/wp/mtswslnk/