Category : BASIC Source Code
Archive   : BASNET6.ZIP
Filename : QB-NET.TXT

 
Output of file : QB-NET.TXT contained in archive : BASNET6.ZIP
Thank you for expressing interest in the BASNet.

BASNet is a network
specializing in BASIC programming. It is not limited to a single version
of BASIC or to a single compiler vendor.

The network will consist of 20 conference. These conference fall into
two broad groupings:
1-10 BASIC Language from generic to specific topic conferences
11-20 BASIC Vendors --conference for and by a vendor of software
products relating to BASIC
At a later date we may expand although this will be resisted.
> 21 Added vendors at such time needed
> 30 Special projects area if 1-10 fills and space is needed

Initial Conferences:
1 BASIC SNIPPETS
Aimed at accumulating a collection of short subprograms that
perform a usable task. The collection can then be discussed
in this area and additional knowledge imparted for the group
benefit.
2 BASIC Chit-Chat
An unstructured area to discuss everyone's favorite programming
language. It will also contain general information and announcements
for the group as a whole. It is the only conference area where
general, informational postings may be left.
3 BASIC Novice
A help forum for the novice programmer. This is the place to
discuss all those "dumb" questions that we all had when we began
our programming efforts.
4 Visual BASIC
It may be all BASIC programmers next language. It currently
runs only under windows and is event driven.
5 Low Level--ASM and INTERRUPT
Getting intimate with the hardware, BIOS and Operating System
6 Doors and Communications
Discuss the problems and pitfalls of programming communications
programs
7 Consulting
A place for those who earn their living writing BASIC code
8 Utilities
Writing system level utilities in QB and the librarys that assist
in those goals--PDQ and QBTiny
9 Hardware
Every programmer needs to know about that necessary evil. Talk
about getting intimate with ports and chips. Potential violance
makes this one R-rated...
14 Crescent--Commercial Vendor
15 TeraTech--Commercial Vendor
16 Hanlin Software
Talk to the author of the shareware library that started it all.
Tom's first library was for QB when most QB users still used
line numbers.
17 Power BASIC
The "other" BASIC from Spectra Publishing. There are a lot of
added features to lure a QB programmer into the fold.
18 VENDOR
a place for vendors to meet users. Also a place for those vendors
who don't want to maintain a separate conference of their own or
who's conference was discontinued. Advertising is welcome on any
remotely related BASIC products.
19 Off-Topic
A place for your ads, graphics or whatever that's not allowed in
the "real" conferences.
20 HUB
will be used as a temporary startup conference. A place where
the startup details can be ironed out. This (and all conferences)
will be public and no private administrative or sysop conference
is contemplated.

Proposed/Potential conference additions:
PROJECTS
Temporarily assigned for group projects that might be of interest
to various participants

VENDOR CONFERENCES
ANY vendor may have a conference. He becomes the de facto host. He
keeps the conference as long as it remains an active forum. The net
will make available areas 11-20 as vendor conferences and, after filling,
the least active conference will be on the bubble for

Network Operations:
The network's primary hub will be The Toolkit BBS located in
Northwest Indiana--near Chicago (219)696-3415 HST Dual Standard
The network will be based on the QNET/RNET packet handling systems.

FIDO afficinados can use the primary hub for that mail standard--
COM-DAT BBS (503)681-0543 HST or (503)640-0728 V32b

Becoming a member BBS:
All boards are welcome to become members of this network. This
is without an approval process or any voting and multiple boards
in the same calling area are able to carry the conferences.

Becoming a member HUB:
Any node willing to provide access to their regional compatriots
is welcome to begin operating as a HUB. They may not charge for
the echo but may charge for basic access. Any node not interested
in such a program is welcome to call another HUB and the primary
HUB (Toolkit) will always grant free mail access.

Conference Hosts:
Each conference area will decide on a conference host. This is
by open ballot within the conference. Any host may also be
removed based on similar voting--the majority of those voting to
rule.

Network Rules:
The network will run without imposing any major restrictions.
The following rules will apply and all attempts will be made to
avoid adding more:

1. Limit Quoting
Overquoting causes unnecessary expense to the sysop--who's
typically absorbing the cost of frequent LD calls to provide
the messages to the participants. Please always keep that
in mind when quoting along with the axiom LESS IS MORE>
2. Personal Attacks
are unacceptable. If a participant develops a reputation for
such acts, his local system will be asked to remove him from
the echo for a period of time as a cooling off period. If
after such a period such attacks are resumed the system will
be required by the network to remove his access to the BASNET.
3. No ANSI graphics except in OFF-TOPIC

Cross-network echoing:
Any other network is welcome to echo any or all of the conferences.
Their only requirement is that they assure that their member boards
will support the limited rules and not impose additional rules on
the participating boards concerning these conferences.



BBS requirements/request:
Upon becoming a member the member bbs is asked to:

Make available the network packet for users as a free download and
request its downloading by all those who they are provide with access
to these conference.

Report their participation to The Toolkit via a private message to the
sysop of their status and any status changes. This message to include:
BBS Name
Sysop Name
Phone Number
Location
Modem used
BBS software
Short (3-line max) Bio of the board
Conference carried
It should be provided in format:

Set up the bulletin group for the associated conferences. These
bulletins are standard information for the conference participants
and maintain by the conference host via the main hubs. If you bbs
software does not permit conference bulletins, they may be carried
as part of the network packet or as a separate archive.

Two types of board will be supported. Partial participants--those
boards who carry only part of the conferences being made available.
FULL participating boards will setup a block of conference and
include all active and inactive conferences as a block. This allows
for quick setup of new or temporary conferences

THE TOOLKIT BBS Ken Prevo Lowell, IN 219-696-3415 HST DS ALL Conf.
The Toolkit is a programmer and power user board carrying every possible
file for the BASIC programmer as well as an eclectic mix sure to warm the
cockles of all computer users. 1.2+ gigabytes of files always available.
This information will be added to the list of boards carrying the echo
and will become part of the network packet.

Files that will be available for download distribution from The Toolkit.
QBBlt##.ARJ -- bulletins associated with conference ##
BASNET.ARJ -- a packet for sysop and users about the net and its operation.
QB!##!##.ARJ -- the archived messages from the conferences

IF YOU ARE INTERESTED, The Toolkit BBS is at 219-696-3415. The board is
a call-back system. If you are interested but it's a one-shot call, you
can quickly get on the board's mini area using HANLIN SOFTWARE as the
name and SHAREWARE as the password. This will allow you to leave a
message to the sysop--be sure to sign it with your real name as the
message source is always shown with the erzatz name you're loggin on under.
I may also set up a special network area and if that's done you'll see
info about it at the time of logon.



  3 Responses to “Category : BASIC Source Code
Archive   : BASNET6.ZIP
Filename : QB-NET.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/