How it Works
Commodore
Loading...
C-NET 128 v7.0
User Manual
126 pgs553.78 Kb0

Commodore C-NET 128 v7.0 User Manual

C-NET 128 v7.0
- TABLE OF CONTENTS -
1.0 INTRODUCTION
1.1 Trialware
1.2 Usage Agreement
1.3 Copyright
1.4 Program and Manual
1.5 Limitations of Remedies
1.7 Acknowledgment
1.8 User Support
1.9 Registration Form
2.0 BACKGROUND INFORMATION
2.1 V7 Development History
2.2 Incompatibilities between V6 and V7
2.2.1 Sysops Upgrading from V6 to V7
2.2.2 Network Connectivity
2.2.3 Net E-Mail & Subs
2.3 User Port or Swiftlink/Turbo232 System
2.4 Modem Information
2.5 Known Problems
2.6 V7.5 Plans
3.0 HARDWARE CONFIGURATION
3.1 Modems
3.2 Floppy Disk Drives
3.3 Hard Disk Drives
3.4 Video Output
3.5 Cartridges
4.0 SOFTWARE INSTALLATION
4.1 Decompressing the Files
4.2 Checklist of C-NET 128 v7.0 Files
4.3 Setting Up Your C-NET 128 V7.0 System
4.3.1 Planning Your System
4.3.2 Copying Files
4.4 Loading the Configuration Program
4.5 System Configuration
4.5.1 Scan System
4.5.2 Format Disks
4.5.3 System Parameters
4.5.4 Edit Modem Strings
4.5.6 Create User Date Files
4.5.7 Saving Your Configuration
4.6 Load Files into a RAM Expansion Unit
5.0 GOING ON-LINE
5.1 Booting the Program
5.2 Setting Time and Date
5.3 Load and Run C-Net
5.4 Creating the System Operator Account
5.4.1 Logging on for the First Time
5.4.2 New User Application
5.5 The C-NET ‘Waiting For Call’ Screen
5.5.1 The Status Window
5.5.2 The System Activity Monitor (S.A.M.)
5.5.2.1 C-Net v7.0 System Monitor
5.5.2.2 S.A.M. Screen 1 (System Variables)
5.5.2.3 S.A.M. Screen 2 (Communication Statistics)
5.5.2.4 Large Clock
5.5.2.5 System Activity Chart
5.5.3 Monitoring and Control System (M.A.C.S.)
5.6 Options When Logging onto the System
6.0 SYSTEM OPERATOR CONTROLS
6.1 Sysop Status
6.2 Access Change
6.3 Local Mode
6.4 Time Still Remaining
6.5 Chat Mode
6.6 New Users
6.7 Printer
6.8 Upload/Download
6.9 Message Bases
6.10 C-NET FAX
6.11 Upload Credits
6.12 Removing the Status Window
6.13 Special Keys
7.1 Chat Request/Chat Mode
7.2 Feedback
7.3 Help
7.4 System Information
7.5 Last Call Date
7.6 New User File
7.7 Logoff
7.8 Password Change
7.9 Quit
7.10 Status
7.11 Time and Charges
7.12 User Information
7.13 Color/Graphics Mode
7.14 Activity Queue
7.15 Account Information
7.16 Credit Information
7.17 Edit Everything
7.18 Edit Preferences
7.19 Edit Terminal
7.20 Edit User Profile
7.21 Send Mail
7.22 C-Net Version
7.23 Extra Commands
7.24 Summary of Commands
7.25 Control Characters
8.0 THE MAIN COMMAND LEVEL
8.1 Message Bases
8.2 Edit Terminal Parameters
8.3 General Text Files
8.4 Electronic Mail
8.5 System News
8.6 Program Files
8.7 System Maintenance
8.8 Uploading/Downloading
8.9 User List
8.10 Dating System
8.11 Voting System
8.12 BBS Listing System
8.13 Edit Profile
8.14 Auto-validation
8.15 Accounting Summary
8.16 Re-logon
8.17 Account Summary
8.18 Activity Queue
8.19 Today’s Callers
8.20 Immediate Processing
8.21 Command Stacking
8.22 Maintenance Commands
9.0 THE ACCOUNTING SYSTEM
10.0 ELECTRONIC MAIL SYSTEM
10.1 Message Notification
10.2 Mailboxes
10.3 Personal Address Book
10.5 Listing Messages
10.6 Reading Messages
10.7 Options After Reading a Message
10.7.1 Responding to a Message
10.7.2 Forwarding a Message
10.7.3 Downloading an Attached File
10.7.4 Adding an Address to your Personal Address Book
10.7.5 Archiving a Message
10.9 Sending a File
10.10 Deleting Mail
11.0 USER LIST
11.1 Output Order and Transverse Direction
11.2 Quick List
11.3 Search Restrictions
11.4 Where the Search Begins
11.5 The Listing
12.0 G-FILES AND P-FILES SYSTEMS
12.1 Level Commands
12.2 Selecting an Item
12.3 Additional Commands Available in G-files/P-Files
12.4 G-File and P-File Maintenance Help
12.5 G-Files On-Line Store Editing
12.6 Multi-Net and the On-Line Store
13.0 NEWS SYSTEM
13.1 Listing News Files
13.2 Reading News Files
13.3 Adding News Files
13.4 Killing News Files
13.5 Editing News Files
14.0 THE MESSAGE AND FILE BASES
14.1 Essential Commands
14.2 Moving Around the Base
14.3 Selecting Items
14.4 Other Commands
14.5 Maintenance Commands
14.6 Direct Disk Exchange Mode
15.0 MESSAGE COMMAND INTERPRETER (MCI)
16.0 THE EDITOR SYSTEM
16.1 Saving/Loading Text in the Editor
16.2 Seeing What Has Been Entered
16.3 Manipulating Text
16.4 Insert Mode
16.5 Line Numbers
16.6 Word Wraparound/Text Formatting
16.7 Shaping the Text
16.8 Specifying a Line Range
16.9 Visual Editor
16.10 Extra Editor Commands
17.0 MAINTENANCE SYSTEM
17.1 ACCESS CONFIGURATION
17.2 SYSTEM COMMANDS
17.2.1 View System Activity Graph
17.2.2 View System Activity Monitor
17.2.3 Edit System Activity Monitor
17.2.4 Edit Time Restrictions
17.2.5 Reload CN File
17.2.6 Make Time Adjustment
17.2.7 Change Maintenance Password
17.2.8 Change System Font
17.3 USER COMMANDS
17.3.1 Edit User Account
17.3.2 Edit Access Group
17.3.3 New Account Creator
17.3.4 Reserved Account Creator
17.3.5 View System New User Information
17.3.6 Update User Groups
17.4 LOG COMMANDS
17.4.1 Auto-Maintenance Log
17.4.3 Caller Log
17.4.4 P/G-File Log
17.4.5 Upload/Download Log
17.4.6 Network Activity Log
17.4.7 New User/Guest Log
17.4.8 System Feedback
17.5 MAIL COMMANDS
17.5.1 Electronic Mail Configuration
17.5.2 Write Forced Mail
17.5.3 Remove Forced Mail
17.6 FILE MANIPULATION
17.6.1 Read File
17.6.2 Write File
17.7 DOS INTERFACE
17.7.1 Execute DOS Command
17.7.2 Read Disk Directory
17.7.3 Change Current Drive
17.7.4 Move Files
17.7.6 Blocks Free Check
17.7.6 Block Free Check & Write To Disk
17.8 NETWORK COMMANDS
17.8.1 Set Bridge Connections
17.8.2 Edit Network Connections
17.8.4 Send Net Feedback
17.8.5 Edit Node Parameters
17.8.6 Send Net Mail
17.8.7 Send Net File
17.9 EDITING THE FUNCTION KEY MACROS
18.1 Utility P-File Overview
18.3 Preferences Editor
18.4 Auto-backup Utility Configuration
18.5 Message Generator
18.6 Call-Back Validation Configuration
18.7 Bad Numbers File Creation
19.0 NETWORKING
19.1 What is a Network
19.2 Network Mapping
19.3 Network Security
19.3 Common Questions Asked
19.4 Multi-Net Support
19.5 Setting up Multi-Net
19.6 Network Maintenance
19.7 General Network Commands in System Maint
19.8 Editing Network Message Bases
19.9 Saving Network Message Bases
19.10 Changing a Network Sub to Normal Sub
19.11 Multi-Net and E-Mail
19.12 Future of Multi-Net
19.13 What Happens When Multi-Net Runs
19.14 Network Guidelines
19.15 Multi-Net v2.0
19.16 Added Programs
20.0 C-TERM
20.1 Control in Terminal Mode
20.2 Other Parameters
20.3 Disk Options
20.4 Selecting Files
20.5 Capture Buffer
20.6 Phonebook/Auto-dialer
21.0 TECHNICAL INFORMATION
21.1 Programming Tips
21.2 Memory Map
21.3 Peek and Poke Commands
21.4 Basic Sys Commands
21.5 Basic Variable
21.6 Access Flags
21.7 Breakdown of Main Program Routines
21.8 Basic Error Codes
21.9 Files That Can be Written
21.10 Menus by the Numbers
22.0 ADDITIONAL INFORMATION
22.1 Changes to prg.* files
22.2 Galactiwars changes
22.3 Main Event Wrestling
22.4 Use of Zed-128 to Edit Network Files
22.5 Flow Charts
22.6 Explanation of Prg* Files APPENDICES
APPENDIX A Understanding Access Groups APPENDIX B COMMANDS
Nacti.* File Format Nstrt.* File Format
( vi)
- INTRODUCTION -
1.0 INTRODUCTION
Welcome to the world of telecommunications on your Commodore 128. C-NET 128 v7.0 is the next step in the evolution of the C-NET Bulletin Board System (BBS). It is, in our opinion, the most sophisticated bulletin board system available for the 128, and is sure to prove itself to you. Please take the time to read completely through the introductory and setup chapters before attempting to operate the program; this will ensure a successful configuration the first time. The balance of this manual has been provided to detail all of the many enhanced features of version 7.0 just waiting to be discovered! This chapter contains all the warranties, support, and legalities.
1.1 TRIALWARE
Shareware is a “Try-Before-You-Buy” concept of marketing software.
Trialware is a special case of shareware. Trialware is time-limited in some way, typically in either license or the features of the application or both. C-NET 128 v7.0 is being distributed as trialware, and is time­limited in that the program will cease to function after a predetermined time. The program is not crippled in any way. In this way, you are assured of being able to properly evaluate the program and make an informed purchase descision.
The C-NET 128 v7.0 Trialware software is freely distributable although not free of charge – if you continue to use it you are required to pay for it. Trialware makes this time limit cleaner and clearer.
Copyright laws apply to both shareware and commercial software, and the copyright holder retains all rights. The only exception is that the copyright holder may grant the right to copy and distribute the software, either to anyone or to a specific group.
1.2 USAGE AGREEMENT
C-Net 128 v7.0 (from now on referred to as the PROGRAM) is being distributed as Trialware. Trialware gives you the opportunity to evaluate the software before purchasing it.
It is NOT Public Domain or Free of Charge. Using this program requires you to accept the following terms and conditions:
1. You may use this copy of the PROGRAM on an evaluation basis. The evaluation period is 30 days.
2. If you enjoy the program and want to receive the benefits of being a registered C-Net System Operator (Sysop) then you must purchase the software. Fill out the registration form in section 1.9 along with your payment of twenty dollars ($20) in U.S. currency and mail it to R. Eric Pearson to register your copy.
3. You may freely distribute the PROGRAM shareware files or diskettes on the condition that each copy contains all of the original unmodified PROGRAM files.
4. You may NOT modify the machine language (INTRO, ML, M2, M3, M4.0, M5, SUBS.O, UDS.O or and of the PROTO files) or remove any copyright notices from any of the other programs or files, charge any fee for the distribution of the program, or take any action that would violate the copyright rights of the owner.
This product is protected by copyright law and international treaties. Unauthorized reproduction or distribution of this program, or any portion of it, may result in severe civil and criminal penalties, and will be prosecuted to the maximum extent possible under law.
1.3 COPYRIGHT
The PROGRAM and its related DOCUMENTATION are copywritten.
YOU MAY NOT REMOVE ANY OF THE COPYRIGHT NOTICES WITHIN THIS PRODUCT AT ANYTIME; ANYWHERE!
1.4 PROGRAM AND MANUAL
The PROGRAM and the MANUAL (‘SOFTWARE’) are provided ‘AS-IS’ without warranty of ANY kind, either express or implied, with respect to accuracy or suitability for any particular application. Should the PROGRAM or MANUAL prove defective, you (and not R. ERIC PEARSON) must assume the entire cost of all necessary servicing or repair. Further, R. ERIC PEARSON does not warrant, guarantee, or make any representations regarding the use of, or the results of use of, the PROGRAM in terms of quality, correctness, accuracy, reliability, currentness, or otherwise, and you rely on the PROGRAM and results solely at your own risk.
R. ERIC PEARSON does not warrant that the PROGRAM or MANUAL will meet your requirements or that the operation of the PROGRAM will be uninterrupted or error free.
Furthermore, if you do not agree to these terms of sale, then you MUST DESTROY any copies of the PROGRAM.
1.5 IMITATIONS OF REMEDIES
In no event will R.ERIC PEARSON be liable to you for any damages in excess
of your registration fee paid, including, without limitation, any lost profits, business goodwill or other special, incidental or consequential damages arising out of the use or inability to use the PROGRAM, or for any claim by any other party, even if R.ERIC PEARSON has been advised of the possibility of such claims or damages. This warranty gives you specific legal rights and you may also have other rights which vary from state to state.
1.6 UPDATE AND CUSTOMER SUPPORT POLICY
In order to be able to obtain any customer support or updates of this PROGRAM, you must complete and return the enclosed registration card to R. ERIC PEARSON along with your registration fee. If R. ERIC PEARSON is made aware of ANY breech of ANY part of this agreement by you, R. ERIC PEARSON is under no obligation to make available to you any customer support or updates to the PROGRAM even though you have made payment of the applicable update fees.
Updates that you receive at a reduced ‘update fee’ are considered replacements for your current software. When you receive any update of the C-NET product, you must DESTROY all previous versions of the software.
1.7 ACKNOWLEDGMENT
You acknowledge that you have read this agreement, understand it, and agree to be bound by its terms and conditions by using the PROGRAM. You also agree that this agreement is the complete and exclusive statement of the agreement between parties and superseded all proposals or prior agreements, verbal or written, and other communications between the parties to the subject matter of this agreement.
Should you have any questions concerning this agreement, please contact in writing:
R. ERIC PEARSON 245 Shear Hill Rd. Mahopac, NY 10541
1.8 USER SUPPORT
Thank you for trying the C-NET BBS. This MANUAL is a detailed description of the features and capabilities of the PROGRAM. However, if you have any questions left unanswered, or if you discover any problem with any part of the PROGRAM, please feel free to contact us by e-mail at CNET128@AOL.COM.
Support is available from the C-NET 128 Web Site:
http://ourworld.compuserve.com/homepages/cnet128/cnethome.html
and from C-Net Support BBS’s:
S.T.A.R.-Link BBS (The Home of C-Net 128) (914) 621-4135
or
The Batcave BBS (303) 252-0735
or
The Northern Outpost BBS (403) 622-3395
1.9 REGISTRATION FORM
To register your copy of C-NET 128 v7.0 print-out and fill-in the following form and mail it along with your registration fee of $20 in U.S. Funds to:
R. ERIC PEARSON 245 Shear Hill Rd.
Mahopac, NY 10541
First Name: Last Name: Street Address 1: Street Address 2: City: State/Province: Zip Code: Country: Telephone Number: E-Mail Address: BBS Name: BBS Telephone Number: You System Operator Handle: BBS Serial #:
System Information:
1. Do you use a hard drive with your BBS? If yes, which make and model?
2. Do you use and type of RAM Expansion (REU, RAMLink, etc.)? If yes, which?
3. What type of modem do you use (make/model)?
4. Do you own a Swiftlink or Turbo232 cartridge?
5. Do you own a SCPU (Super CPU) by CMD?
2.1 V7 DEVELOPMENT HISTORY
C-Net 128 has required extensive changes in both the Machine Language programs and Basic 7.0 code in order to operate with the Swiftlink/Turbo 232 interface and high-speed modems. C-Net 128 7.0A wedges the NMI
interrupt handler with ML code to receive data from the modem. Characters received are placed in the normal 255 byte RS-232 input buffer. This allowed the “Main” portion of the BBS to operate with existing code with only minor modifications to the ML program. However, it was quickly found that the U/D protocol programs bypassed this functionality and used their own separate code to access the modem. This is why so many of the PROTO files had to be modified. C-Net 128 7.0 does not use an output buffer, instead it writes output characters directly to the Swiftlink/Turbo232 transmitter for increased speed.
One of the major challenges in creating version 7 was the upload/download protocol files and consequently the networking (which uses the Punter protocol to send and receive files). First I had to reassemble the three U/D Protocol files; PROTO 0, PROTO 1 and PROTO 5. PROTO 0 was the most difficult since I did not have the source code for it. I had to reverse engineer or disassemble the ML and then fix any assumptions the disassembler made. Then figure out exactly what each line was doing since there were no comments to aid me. After reassembling each PROTO file I then tested them with the existing RS-232 modem routines. After each PROTO was working with the existing routines my first idea was to try to “patch” each PROTO to work with the Swiftlink/Turbo 232. I tried this for a couple of weeks but with only moderate success, mostly due to timing problems, the code was unstable and finally abandoned. Then I decided to make Swiftlink only versions of each PROTO. This was a major decision because from the start I had intended to keep compatibility with older RS-232 modems. C-Net 7 is still compatible now with the older modems with one exception; when you set up your system you have to decide which you’ll be using since there are now two versions of each Upload Download PROTO file (PROTO 0, PROTO 1 and PROTO 2). Getting back to the development, the U/D protocols were ripped and rewritten. A version of each was created that would only work with the Swiftlink/Turbo 232.
I was just about to release version 7, in fact an Alpha version was released to a limited number of C-Net SysOps for testing, when I started hearing how people were worried about Year2000 compliance both in the C-Net world and DS-2. Both programs had similar Year2000 issues. Also I was hearing how the C-Net Electronic Mail system was inferior to comparable BBS programs. So I pulled V7 back into development and began analyzing the BBS for Year2000 issues. The Y2K fix actually went in very quickly, probably within a month. The first time watching the date roll over to 1/1/2000 was pretty cool. However, I eventually uncovered a major bug in the Message Base ML where the index would become corrupted. Now next to the UD Base the Message Base in C-NET is probably the most complicated program. Probably 80% of what goes in the Message Bases is done through ML. This bug stumped me for over a month to the point where I put everything down and walked away from it for the entire summer. Eventually I came back to it and after tearing apart the ML and tracing every line I fixed it.
As I mentioned above the E-Mail subsystem was in dire need of enhancement and I had actually begun work on it some months before. So with the message base bug squished I finished the enhancements to the e-mail system (except for a couple of things, see the Known Problems section) and about a hundred other little changes here and there. Here’s just a few of those:
1. Reduced the size of PRG.LOGON by moving some code to PRG.LOGONTWO (strange things happen when a PRG gets too large, believe me and read section 21 if you plan to do any C-NET programming)
2. Redesign of PRG.NET-ASSEMBLE and PRG.AMAINT.
4. Redesign of E-Mail.
5. Added System Monitor
6. Added HELP for System Operator at Waiting for Call screen.
7. Added Last 10 Caller Screen toggle at Waiting for Call screen.
8. Redesign of SysOp Interface.
2.2 INCOMPATIBILITIES BETWEEN V6 & V7
2.2.1 SysOps Upgrading from v6.x to v7
The follow is a list of files from v6 that are not compatible with v7. Meaning, the v6 format of these files has changed in v7. Most files will have to be deleted and then recreated using v7.
If a recommendation says "SCRATCH" you should manually scratch the files from DOS.
If a recommendation says "LOG" you should manually write down on a piece of paper all pertinent information.
Because of time constraints conversion programs are not available.
User Data files - These will self correct after a user logs on and logs off. Although First Call and Birth Date information will be lost and need to be re-entered. If you can wait I am considering a conversion program, probably to be released with patch number one.
All E-mail files - recommend scratch all v6 mail files before running v7.
All Message Base files - recommend log, then delete message bases from v6 using the KL # command.
The C-Term Phonebook (sys.phonebook) - recommend log, then scratch and recreate using v7.
P-File Directory’s - recommend log, then delete using v6 and recreate using v7.
G-File Directory’s - recommend log, then delete using v6 and recreate using v7.
Note: v6.X U/D files are 100% compatible with v7. There are still Year2000 problems with the way file upload dates are stored, but these problems should not effect the overall BBS even if not fixed before 2000. The only effect I can foresee is that old files will be erroneously reported as new.
2.2.2 Networking Connectivity
In order for a C-Net 7.0 system to network with C-Net v6.x systems properly, the C-Net v6.x system must be using PRG.NET-TRANS (v6.3). This version of NET-TRANS has been modified to fix timing problems between the systems.
2.2.3 Net E-Mail & Subs
In order for v6.x systems to correctly receive networked e-mail and sub­board messages they must be running PRG.NET-MAIL (v6.1X) and PRG.NET-UNPACK (v6.1X). These versions have special filtering logic that will correctly translate v7 date fields to v6
Before setting up your C-NET v7.0 BBS you need to decide if you will be running with a modem that interfaces with the Commodore 128 through the User Port or through a Swiftlink/Turbo232 cartridge. User Port modems will only be able to sustain speeds up to 2400 BPS, while modems using a Swiftlink/Turbo232 will be able to attain much greater speeds. C-NET v7.0 during testing was able to maintain speeds up to 28,800 BPS with a Swiftlink cartridge and should be able go higher still with a Turbo232.
2.4 MODEM INFORMATION
In order for your modem to work correctly with C-Net v7.0 it MUST be able to report DCE connect speed as opposed to DTE speed. DCE (or Data Communications Equipment) speed is the speed at which the modems connect. DTE (or Data Terminal Equipment) speed is the speed at which your computer connects to your modem.
Most modern high-speed modems have an AT command to enable DCE reporting. It may be an S-Register setting or a normal AT command. For example, my Cardinal 28.8 uses S95 to enable DEC reporting. Some other modems use the AT command W2 to enable it. Refer to your modem manual or contact your modem manufacturer for assistance in determining the correct command for your specific modem.
You will also need to determine the command to “lock” your modem at a specific BPS rate. Again most modems use an AT command to do this. Commonly, I have found, this command is AT&Nn where n is a number corresponding to the speed you want to “lock”. For example, AT&N2 would “lock” your modem at 1200 BPS. When I say “lock” I mean that when the correct AT command is issued your modem will ONLY attempt to connect at the designated speed. If it cannot connect at the designated speed it will hang-up. This “locking” is required for the Networking portion of C-NET.
The modified SU or Set-Up program now allows you to enter an initialization string, a hang-up string and the strings required to lock your modem at specific BPS rates.
CN 3360 - Send a command to modem appending a carriage return.
3500 - Clear the line, hang-up. 3860 - Retrieve one character the RS-232 input buffer.
M3 SYS4939 - Wedges the NMI handler and initializes the Swiftlink/Turbo232
2.5 KNOWN PROBLEMS
Following is a list of known problems (a.k.a. bugs) or features by subsystem that did not make the release date:
Electronic Mail
1. Retrieving File Attachments - Only the New Punter protocol works for retrieving file attachments at this time. This bug will be fixed in a patch release at a later date.
2. Reply with/File Attachment – Did not make the release date, will be included in the first patch.
3. Networked Return Receipts and File Attachments – Not implemented yet pending Network Administrator approval.
U/D Subsystem
1. The U/D Subsystem is not Year 2000 compliant. Dates are still stored in MMDDYY format. Since I plan to rewrite the U/D System for V7.5 I didn’t see the point of patching the existing system. Secondly, since it is to be a major rewrite it didn’t make the release date. And finally without a conversion program, all C-NET SysOps with huge U/D sections would have to recreate them since the headers will be incompatible.
Message Base Subsystem
1. There is currently a limit of 255 total messages (posts & responses) per message board. This will be increased to around the C-NET V6 default of 232 post and 718 total messages (posts & responses) in the first patch release.
Main System:
1. SY Command – Certain functions of the DOS Shell DO NOT work while on­ line. It WILL crash your board if you attempt to load a Basic 7.0 program.
2. MF Command – The Move File command only works in Local Mode. It seems this is the way it was originally designed. I plan to take a look at and include a fix in the first patch.
3. Visual Editor – The Visual Editor is currently being modified to allow on-line use. Although it still functions now, use may be erratic.
2.6 V7.5 PLANS
Following is a list of enhancements that for one reason or another did not make it into V7 of C-NET but might make it into a future release.
Allow drives 8-30 and partitions above 9 New Visual Editor C-Net FAX Redesigned U/D Section QWK Mail Support Punter Timeout & PEEK PRG.NET-STORE
- HARDWARE CONFIGURATION -
3.0 HARDWARE CONFIGURATION
This section will assist you in choosing the correct computer equipment for use with C-NET v7.0 BBS.
3.1 MODEMS
There are two basic types of modems that are compatible with the program; User Port modems and modems that can be used with a Swiftlink/Turbo232 cartridge. Of the User Port modems there are 3 different types that are compatible:
1650 modem and anything compatible (Westridge, Video 7, Total Telecommunications) Mitey Mo and anything compatible (Hesmodem II) Hayes Smartmodem and anything compatible (Prometheus ProModem, Commodore 1670, Linker, US Robotics Courier, Supra Modem 2400). 1200 and 2400 baud may be used with Hayes compatible modems only.
A modem is considered ‘Hayes compatible’ only if it understands basic ‘AT’ commands such as ATV0, ATH, ATS0=x, ATS7=x, ATX1, and ATA, RS-232 interfaces, which are necessary to connect most Hayes compatible modems to the Commodore 128, must be tested separately for their compatibility with C­NET 128. RS-232 interfaces that have been successfully tested include the MSD and the Omnitronix brands.
3.2 FLOPPY DISK DRIVES
Generally, any disk drive that can be connected to your 128 and used normally with SAVE, LOAD, and OPEN commands, can also be used with C-NET v7.0. Disk drives that have been successfully tested in the past include the 1541, 1571, SFD-1001, MSD-d2, Indus GT, PET 4040, 8050, 8250, 9060,
9090. IEEE interfaces, which are necessary to connect SFD-1001’s and other parallel disk drives must be tested separately for compatibility. The only IEEE interface that has been successfully tested is the Skyles Quicksilver
128. There are two terms, however that you must be familiar with when configuring your C-NET v7.0 BBS. When reference is made to a disk drive DEVICE, it is referring to the unit as a whole. A disk drive may have one or two openings each referred to as a DRIVE. A brand-new disk drive has a DEVICE number of 8. If you plan to connect more than one disk drive to the 128 for use with the PROGRAM, you must insure that each disk drive has a unique DEVICE number (see disk drive instructions for information about changing the device number of a unit). A disk drive with one disk capability is said to be a DRIVE 0. With a two-disk drive unit, the individual disk units are numbered 0 and 1 (see disk drive instructions to which slots are which).
3.3 HARD DISK DRIVES
Hard drive manufacturers have recently discovered the enormous market potential that exists among Commodore computer users, primarily because of the bulletin board systems that they operate. At the time of this publication, we have used two different hard drives, the first, and the one
used the longest by the Author, is the Lt. Kernel hard drive. Also, successfully tested is the CMD hard drive. Before you purchase a hard drive, please contact us first for the latest compatibility information.
When configuring your hard drive, you may configure your hard drive any way you wish, however, it is suggested that you make at least 3 LU’s (partitions), (0 for system disk, 1 and 2 for whatever else you wish to use them for. It is also suggested that you reserve at least 15,000 to 20,000 for LU 0. This will leave you enough room for al the system files, your message bases (both local and network), as well as all the P-files (on-line games) that you wish to use).
3.4 VIDEO OUTPUT
C-NET uses the 80-column video chip exclusively for screen output. You MUST be using and RGB monitor or a specially created MONOCHROME (one color only) cable plugged into the RGB output driving a composite monitor. This cable may be made by connecting pin 7 of the RGB output port to the tip of an RCA connector and pin 1 to the ground of the same plug. Also, the 40/80­column key at the top of the 128’s keyboard must be depressed at all times.
3.5 CARTRIDGES
No form of ‘FAST LOAD, MACH128, etc. or other types of software cartridge can be successfully used with C-NET 128 v7.0, but will only interfere and cause numerous problems.
- SOFTWARE INSTALLATION -
4.0 SOFTWARE INSTALLATION
This section covers the configuration of the program, explaining step by step the procedure that you must follow before the program will be ready to place ‘on-line’.
4.1 DECOMPRESSING THE FILES
All of the C-Net v7.0 files were compressed using Wraptor V3 for the Commodore 64 from Loadstar. You can decompress these files using a Commodore 64 or Commodore 128 in 64 mode. 128 mode means the 40/80 column switch is NOT depressed and you are holding the Commodore key down when you start your Commodore 128 or you type “GO64” and press return while in 128 mode.
In order to decompress the files you must have a copy of Wraptor V3. A copy of this program is available for download from the C-NET 128 Web site or you can contact Loadstar at their Web site (http://www.loadstar.com) to obtain a copy.
You should decompress all the .WR3 files to separate1581 diskettes. Or if you have a higher capacity drive such as a CMD FD-2000, CMD Hard Drive or a Lt. Kernel Hard Drive, you could decompress all the files to a single drive. If you are using a Hard Drive it is recommended that you copy all of the files to the first partition or LU. From now on the diskette(s) or DRIVE where you decompressed all the archive files to will be know as your C-NET INSTALL DISK(s).
4.2 CHECKLIST OF C-NET 128 v7.0 FILES
Following is a list and brief description of files you should have after decompressing all of the V7.0 archives.
MACHINE LANGUAGE PROGRAMS: CNETBOOT – Loader program for C-NET 128 V7.0 M2 M3 M4.O – ML to save and restore the SysOp Status Window and cursor position M5 – RAM Loader ML – Main ML program. PROTO 0 – Punter Protocol ML. PROTO 1 – ASCII Protocol ML. PROTO 101 – Net Pauq ML. PROTO 4 ­PROTO 5 – X-MODEM, Y-MODEM Protocols PROTO 6 – C-Term ML PROTO 7 – Editor ML PROTO 8 – Visual Editor ML PROTO 9 – Basic Interface ML SUBS.O – Message Base ML UDS.O – UD Base ML
BASIC 7.0 PROGRAMS: C1 – Loader Program CN – Main C-NET Program (always in memory) PRG.AMAINT – Auto-Maintenance Program PRG.AMAINT1 – Auto-Backup Program, chained to PRG.AMAINT PRG.AMAINT2 – “This Day in History” Program, chained to PRG.AMAINT PRG.BAUDSET PRG.BRAIN PRG.CLEANUP PRG.COLLECT PRG.COPYFILES PRG.DATA EDITOR PRG.DATING PRG.DOS – DOS Command Interface PRG.DOWN – Program to down the BBS, SysOp Help menu PRG.EMAIL – C-NET Electronic Mail Program. PRG.EXCHANGE PRG.FAX – Under construction PRG.FILES – P/G-Files Program PRG.FMAIL PRG.GEDIT PRG.HDTIME – Reads real-time clock if available and calculates current day. PRG.LOGOFF – Logoff options PRG.LOGON – Main Logon Program, Waiting for Call Loop PRG.LOGONTWO – Second Part of Logon PRG.MACS CHANGER ­PRG.MAINT – System Maintenance Program PRG.NET-ACTIVATE PRG.NET-APP PRG.NET-ASSEMBLE – Main Network engine PRG.NET-BLDFILE PRG.NET-CONFIG – Configure Network Connections
PRG.NET-CONNECT PRG.NET-DIST PRG.NET-EASY PRG.NET-FBACK PRG.NET-MAIL PRG.NET-MAP PRG.NET-NEWS PRG.NET-NOW PRG.NET-ORDERS PRG.NET-PARMS PRG.NET-PULL PRG.NET-SEND PRG.NET-SEND FIX PRG.NET-SORT PRG.NET-SU PRG.NET-SUB EDIT PRG.NET-SUBS PRG.NET-TEST PRG.NET-TRANS PRG.NET-UNPACK PRG.NET-UTIL PRG.NEW USER – Run when a new user logs on PRG.NEWS – C-Net News Sub-system PRG.NEWSCAN PRG.NS – Net Send E-Mail PRG.PERIOD PRG.PROFILE PRG.RAM – Loads files into RAM Expansion Unit PRG.RELREAD – Read relative files PRG.RES-ENTRY PRG.SEARCHTEXT PRG.SEND WELCOME PRG.SERVICES PRG.SETUP – C-NET Initialization Program PRG.SKY-AVERAGES PRG.SMAINT PRG.STATS PRG.SUB-DIST PRG.SUBS – Message Base Engine PRG.TERM – Built-in terminal program PRG.TRANSLATOR PRG.U/D – U/D Base Engine PRG.UEDIT – User Edit Program PRG.ULIST – User List Program PRG.UMAINT PRG.USEREDIT PRG.UTILITIES – SysOp Utilities PRG.VDATA – Dump version data for PRG files PRG.WEED – Weed Message Bases SU – System Configuration Program
SEQUENTIAL FILES:
DATA FILES: CHRSET#1 – Alternate Character Set/Font CHRSET#2 – Alternate Character Set/Font CHRSET#3 – Alternate Character Set/Font
CHRSET#4 – Alternate Character Set/Font TRATBL 0 – Translation table 0 TRATBL 1 – Translation table 1
4.3 SETTING UP YOUR C-NET 128 V7.0 SYSTEM
4.3.1 PLANNING YOUR SYSTEM The C-NET 128 Bulletin Board system works on the premise of different DEVICES and DRIVES for different operations. When planning your system you need to keep this premise in mind.
A basic C-NET 128 system needs DEVICES or DRIVES defined as the following:
THE SYSTEM DISK – Should always be DEVICE 8, DRIVE 0. On a system using a hard drive the SYSTEM DISK should utilize DEVICE 8 and the first PARTITION OR LOGICAL UNIT (LU) on that device. The SYSTEM DISK houses the main machine language and basic programs required when running C-NET 128. Also all of the User Data, System Help Files, and News Files.
THE P-FILES DISK – Can be another DEVICE or DRIVE (Partition or LU for Hard Drive users). The P-FILES DISK houses all the program modules (PRG files or also referred to as “Doors”) required for the various sub-functions of C­NET 128. Examples of these program modules might be the Electronic Mail engine, the Message Base engine, On-Line Games, etc.
THE E-MAIL DISK – Can be a separate DEVICE or DRIVE (Partition or LU for Hard Drive users). The E-MAIL DISK houses all the mail files for your users. Also in V7 it is the storage disk for any file attachments to messages. When planning your E-MAIL DISK you should keep all of these factors in mind as they all relate to how much disk space you will need to allocate for e-mail. C-NET 128 requires 20 blocks for the basic E-Mail files for each user (these include In-Box, Sent Mail, Archive and Personal Address Book. A simple formula for calculating your specific disk need is:
DISK SPACE NEEDED = PLANNED USER BASE * (20 BLOCKS + THE SIZE OF THE MAXIMUM ALLOWABLE FILE ATTACHMENT)
NOTE: It is HIGHLY recommended that you put E-Mail on it’s own DEVICE (for disk drive users) or it’s own partition or LU (for hard drive users). Not only for the obvious reasons of required disk space but also the sometimes erratic nature of relative files.
THE G-FILES DISK - Can be another DEVICE or DRIVE (Partition or LU for Hard Drive users). The G-FILES DISK houses all the General Text Files available on you BBS for on-line reading and/or downloading. Examples of these general text files might be the rules and regulations for your BBS, extra Help files, FAQs, etc.
ETCETRA DISK - Can be another DEVICE or DRIVE (Partition or LU for Hard Drive users). The ETCETRA DISK houses all of the system log files for C­NET 128. These include the file transfer log, caller log, system error log, etc. Log files are generally rather small in size as far as disk space, that is as long as you provide timely maintenance.
4.3.2 COPYING FILES WARNING!!!! DO NOT use a ‘fast hack em’ files copier to transfer files from the C-NET INSTALL DISKS -- they have been proven to be very unreliable
and dangerous to data integrity!!!
Your SYSTEM DISK and P-FILES DISK must be properly formatted or partitioned before starting this procedure. For instructions on formatting a disk see the instruction manual for you diskette drive or hard drive. Or if no manual is available there are resources on the Internet such as the COMP.SYS.CBM newsgroup when you could get and answer.
You should load and use a file copier program such as Jim Butterfield’s “Copyall” or the 1571 “Unicopy” or CMD’s “Fcopy” for the following procedure.
Next, you should copy the following system files from the C-NET INSTALL DISK to your designated SYSTEM DISK:
CNETBOOT ML C1 CN M2 M3 M4.o SU PRG.SETUP PRG.RAM *M5
All SYS.MENU* files All SYS.HELP* files All PROTO * files SUBS.O UDS.O TRATBL 0 TRATBL 1
*M5 must only be included on each disk if you plan to load sequential files into the RAM expander from that disk
Finally you should copy all of the PRG to your P-FILES DISK. PRG.SETUP and PRG.RAM can be excluded since they should be already on your SYSTEM DISK. Other OPTIONAL PRG files that can be excluded and their impact on your system areas follows:
PRG.DATING – Disable the on-line dating subsystem. ALL PRG.NET-* FILES – If you don’t plan on running the networking software.
4.4 LOADING THE SYSTEM CONFIGURATION PROGRAM
Ensure you Commodore 128 is in 128 mode by depressing the 40/80 button and that you monitor has the 80 column RGB mode selected.
For users running from a diskette based system (no hard drive), before going any further, make a backup of your C-NET SYSTEM DISK. Use this backup as your main program disk. DO NOT use your master copy for any writing to, or running of the BBS.
NOTE: For users of hard drives:
Lt. Kernel hard drives: You should create a BASIC file called ‘autostart’ containing the single line:
1 BLOAD“CNETBOOT”:SYS14336
CMD hard drives: Your should create a BASIC file called ‘boot’ containing the single line:
1 BLOAD“CNETBOOT”:SYS14336
C-NET will automatically boot from the hard drives when powered on with these files in place.
For users with floppy diskette systems, insert the C-NET SYSTEM diskette into device 0, and power-up the Commodore 128. At the ready prompt type:
BOOT”CNETBOOT”
And hit the RETURN key.
Regardless of which type of system you are using, a few moments after booting the following menu will appear on the screen.
(1) Set-up the C-Net BBS (2) System configuration
Select “(2) System Configuration” by pressing the down arrow key using either the cursor arrow keys (the ones on the top of the keyboard) once to move the light bar pointer down, then the RETURN key. Once the system configuration program has finished loading, you will be instructed to insert all system disks, and then to press RETURN. You should remove the C­NET Program Disk, then insert blank or erasable disks into every disk drive connected to the system (leave the SYSTEM DISK in drive 8 for floppy users). After pressing the RETURN key, C-NET will let you know that the system is not yet configured, then a menu of eight options will appear. To properly configure the system, you must select the options in the following order:
4.5 SYSTEM CONFIGURATION
4.5.1 SCAN SYSTEM
Computer type JiffyDOS Detect RAM Expansion RAMLink Real-Time Clock Total Drives Drive Types Printer Detect
4.5.2 FORMAT DISKS
Disks must be formatted and completely empty before they may be used with C­NET. Systems with only hard drives may skip this section, providing they have formatted all the Logical Units (Lt. Kernel) or partitions (CMD) prior to loading the C-NET software. Press RETURN with the lightbar is highlighting option “(1) Format Disks” to begin formatting disks. You will be asked for the DEVICE and DRIVE location of each disk that is to be formatted. After a disk is formatted, you will be informed of the disk
drive status. If there is an error, you should first try another erasable disk before having the disk drive unit checked for problems. Continue to select device and drive numbers until all disk drives contain empty, newly formatted and error-free disks. Go back to the main menu by pressing RETURN when you are asked for another device for formatting.
4.5.3 SYSTEM PARAMETERS
Now move the lightbar to the second option “(2) System parameters”, and press RETURN. For this screen and the following configuration screens, you will be given cursor control using the four control arrows at the top of the keyboard. To change an item on the screen, simply begin typing and press the RETURN key when finished. To exit a screen press the ESCAPE key that is located at the top left corner of the keyboard.
1) System disk -- device and drive number for storage of all system information (user files, help files, machine language programs, main basic programs). If you are using a hard drive, your system disk MUST be configured to 8,0 (CMD drives recognize 8,1 as 8,0).
2) E-Mail disk -- device and drive number for storage of all inter­ user messages.
3) Etcetera disk -- device and drive number for the storage of all system logs (file transfer log, call log, error log, feedback, new user information, etc.).
4) G-Files disk -- device and drive number for storage of C-NET’s general text and information file system.
5) P-Files disk -- device and drive number for storage of all program modules (the system’s modules and on-line games). For hard drive users, it is best to use 8,0 as your device and drive numbers for this. That way, all your program files are in one place, and the hard drive does not have to look all over for program files.
6) Output Feedback, Logs -- The two numbers on line 6 tell C-NET where to direct system files. The first number directs written text messages such as feedback and new user information. The second number directs the ‘logs’ of caller sign on/sign off activity as well as system errors. (1) In a position here indicates disk file output to the Etcetera disk (2) Indicates printer output (3) Indicates output to both disk and printer (0) Indicates no output at all. *Editor’s note: I have found that it is best to have a printer hooked up to your BBS, and have all logs printed out to printer as well as disk. It is much easier to follow and track errors using both disk and printed matter. (7) Login identifier -- The login identifier is a two-character prefix to all user ID’s of the system. Both characters must be uppercase letters, or numbers. DO NOT use punctuation symbols. (E.g., “FW” would be used for a BBS with the name Future World.) (8) DCD Invert -- This entry should ALWAYS be set to 0 if you are using modem type 0, 1. But can be either a 0 or a 16 for modem type 2 and 4; depending on your RS-232 interface, and whether it supports normal or inverted carrier detection
9) Printer Device – This is usually 4 or 5. Check your printer interface instructions to be sure.
10) Printer Secondary (address) – This is usually 7, but check your printer interface instructions to be sure.
11) Modem Type -- Set according to the following list: (0) Mitey Mo, Hesmodem II (1) 1650, Westridge, Total Telecommunications, Video 7 (2) Hayes compatibles (extended return code set and non­ verbose mode must be supported). C-NET waits for a ring, sends ATA, then waits for a connect code --1 for 300 baud, 5 for 1200 baud, or 10 for 2400 baud. “+++” and ATH are sent to hang up. If a dip switch for DTR exists, set it for always on (true). (3) Commodore 1670 (this modem does not support ATA while the phone is ringing -- so must always be set to auto­ answer mode.) (4) A Hayes compatible (type 2) modem with DTR (Data Terminal Ready) control ability for fast hang-ups. The RS-232 interface must also support the DTR pin connection to the modem. If a dip switch for DTR exists, set it for line signal (not always on). If a dip switch exists on any modem for CD (carrier detection), insure that it is set for line signal (not always on). (5) Swiftlink/Turbo232 Cartridge
12) Idle Baud Rate -- Baud rate at which the computer should conduct conversation with the modem while the system is waiting for a call. This means, the maximum baud rate of the modem that you are using.
13) Default Text Color -- A color code (0 to 15) for color of all system prompts and status displays. I would suggest against using 0 (black) as a default text color.
14) Drive Secondary Address -- When writing to files, 1571’s tend to write faster (when writing to the backside with the old bug­ filled ROM’s) with a secondary address of 1. Most other drives don’t mind this 1. Lt. Kernel hard drives will not function with a secondary address of 1, so you must change the 1 on this line to a 2 if you are using the Lt. Kernel.
15) Network/Amaint Hour -- This is the time of day (in military time, 0 is midnight, 12 is noon, etc.) that auto-maintenance will occur. Auto-maintenance is described more fully in chapter
18.
16) 2400 Baud Fine Adj – Only necessary for modem types 0-4
16) Real-Time Clock –
17) System Hard Drive – 0=NONE, 1=CMD HD, 2=Lt. Kernel
18) Expansion RAM – 0=NONE, 1=1700, 2=1750
When you have finished this screen, press ESC.
4.5.4 EDIT MODEM STRINGS
INITIALIZATION STRING Build a modem initialization string with the following elements. Refer to your modem manual to verify correct commands.
EO - Echo OFF
QO - Display Result Codes
X4 - Set Level of Result Codes Displayed V1 - Verbal Result Codes &C1 - Normal CD (Carrier Detect) Operations &D2 - Normal DTR (Data Terminal Ready) Operations W2 - Connect Message Control
NOTE: Some modems may use an S-Register to set Connect Message Control. The Cardinal 28.8 I tested and Practical Peripherals modems use S95 while the Zoom 33.6 offered by CMD uses W2 as does most Boca modems. Refer to your owners manual.
Completed initialization string should be something like the following:
ate0q0x4v1&c1&d2w2 or ate0q0x4v1&c1&d2s95=1
HANG-UP STRING
Now build a modem hang-up string. Most modems use H0 to hang-up the modem so the command would be:
ath
LOCK MODEM STRING
I have found most modems use AT&Nn to lock modem speeds (Cardinal, Zoom, US Robotics, Boca) but you should still check your modem manual to confirm these values.
After confirming all of your modem settings hit ESCAPE to go back to the System Configuration menu.
4.5.5 ENTER ACTIVATION CODE
C-NET 128 V7.0 is Time-Limited Shareware (or Trialware). This means that the PROGRAM will cease to function after a predetermined amount of time. When you purchase the software and send in the Registration Form, you will be given an Activation Code. A valid Activation Code will disable the predetermined deactivation date for the PROGRAM.
4.5.6 CREATE USER DATA FILES
You should now select the sixth option. You will be warned that this will erase any existing user data. Enter a ‘Y’ to continue. You will be asked for a number of user accounts to initially reserve disk space for -- it is a good idea to slightly overestimate this number (a good number to start with is 200). After this number of user accounts is exceeded, the files should automatically grow to accommodate any new accounts. It will take several minutes to create the user data files. NOTE: Some disk drives may not like to expand the user data files on an as needed basis, so it may be a good idea to reserve all of the space you think you will ever require right now! Each complete user account requires slightly less than one disk block.
4.5.7 SAVING YOUR CONFIGURATION
Select option #8 “Save Configuration” and when prompted to “Save Changes” type Y for Yes. Now that your configuration is saved, select option #9 to exit the System Configuration utility and to load the BBS.
NOTE: Option #9 no longer prompts you to reset your computer. Instead it reloads CNETBOOT. This was an enhancement to V7.
4.6 LOADING FILES INTO A RAM EXPANSION UNIT
If you have a 1700 or 1750 RAM expander, or a CMD RAMLink, C-NET is able to make use of it to store three types of files: (1) Program modules (prg.* files) (2) File transfer protocols and machine language overlays (proto* files) (3) Sequential files which are read by the system from start to finish, that is, any completely NON-DATA SEQ files (such as menus, g-files, welcome and exit files, not including message base entry files). Sequential files stored in the expander may not exceed 10,240 bytes (approximately 40 disk blocks).
The RAM expanders are divided into banks of 64K bytes (about 256 disk blocks). The 1700 has 2 of these banks; the 1750 has 8. C-NET is not able to load a file partially into one bank, and continue it into another -- a file must fit entirely into one bank. This means that if as C-NET loads a file into the expander, it finds not enough room in the current bank for the file it is attempting to load, it will move to the next bank, leaving some memory in the previous bank unused. The result is this: optimally, a 1700 can store 512 blocks, but because some of the memory at the end of each of its two banks must be wasted, the 1700 may only be good for 480, or even 430 blocks. The same situation holds for the 1750, which can (under optimal circumstances) hold 2048 blocks. You will have to observe the loading process (next chapter) to see if you have over-extended the memory of your expander.
To use a RAM expander, designate a blank and formatted disk as your “RAM loading disk” and copy to it all files you wish to load into the RAM expander, as well as the files “prg.setup” and “m5” from the C-NET master disk. You may use multiple disks for program/proto files, and a separate
disk for sequential files. If you use multiple disks, you need only include “m5” on your sequential files disk, and “prg.setup” on the last disk you will be loading from (this is your sequential files disk if you are using a separate disk for them).
Any files NOT included on these disk (s) for loading into the RAM expander must be copied to the appropriate disk (s) in the same manner as someone who is not using a RAM expander would.
- GOING ON-LINE -
5.0 GOING ON-LINE
After you have configured you system by following the instructions in section 4, this chapter explains you how to put your system on-line and ready to receive calls.
5.1 BOOTING THE PROGRAM
C-NET must be booted from device 8. If you have either a 1571 or 1581 master, insert the master disk into the appropriate disk drive. If you have a two-disk 1541 master, insert disk ‘one’ into either a 1541 or 1571 drive. If you have a device 8 hard drive, and have copied the master disk to LU 0 or partition 1, and have created the autostart or boot file described in chapter 3, you need not insert any disks. Now, power up the computer. If for any reason you are booting from a copy of the boot files in any other format, the command:
BOOT“CNETBOOT”
should be all that is needed to get things moving.
When the light bar menu appears, press RETURN to select ‘(1) Set-up the C­Net BBS.’
If no activity is detected from the keyboard at this light bar menu for a period of approximately 30 seconds, C-NET will automatically skip the date entry prompts, and skip the ‘insert disks’ prompts in an effort to put itself on-line. What this means is, if your system will autoboot when powered-on, and all of the boot files are present on device 8, C-NET will take itself the rest of the way to “waiting for a call” in the event of a power failure. The date used for set-up will be either the last date entered by yourself, or the date of the last user’s sign-off. If you are using a CMD device with a real-time clock the program will read the internal clock and insert that time and date. A command is provided in system maintenance to change the date on-line.
5.2 SETTING THE DATE AND TIME
First the month will be set. Use the up and down arrows to change the month displayed.
If for any reason any characters other than a valid month is displayed in the month location, insure that a fresh copy of the file ‘d’ is placed on your boot disk, and re-boot the system. When the correct month
abbreviation is displayed, press the RETURN key. Now you must set the date. To change the date, use the number keys, either on the numeric keypad or at the top of the keyboard. When the correct date is displayed, press the RETURN key. Enter the year, hour and minute in the same manner. Finally, you must press either ‘A’ or ‘P’ to select AM or PM, respectively. The date you enter will be stored in the file ‘d’ on your boot disk. NOTE: To protect the boot code from ever becoming overwritten by saved program code on the master disk (or a back-up), never validate (collect) the disk.
5.3 LOAD AND RUN C-NET
When you have finished setting the date and time, another menu will be displayed, giving you a chance to correct the date and time if you have made a mistake. If the date and time are correct, select the option to ‘(2) Load and Run C-Net’ to continue. If the load proceeds correctly, several seconds later, C-NET will clear the screen and will auto-detect if you have a RAM expander connected to your system. If a RAM expander is found C-NET will ask if you would like to load PRG files into RAM. If you are not using a RAM expander, the program will display ‘REU not found’ and will continue on.
If you intend to load any PRGs into the RAM expander, first remove the C­NET master disk from the drive, then insert your RAM loading disk. Press ‘Y’ to begin loading p-files. As p-files are loaded, each file name and stored location in the RAM expander will be displayed. The bank number will always begin at 0, and increment as a bank fills and another must be used. The 1700 may use only banks 0 and 1; the 1750 may use banks 0 to 7. The program will load as many PRG files into memory as possible.
NOTE: The program loads PRG files into the RAM expander in the order it finds them on the P-File Disk. To optimize RAM loading you should order your directory so the PRG files are in batches of 60000 blocks (or as close as possible).
Once one disk of P-Files has been loaded, and if there is still room in memory, you will be given the option to load the P-Files from another disk. If you intend to do so, remove the first disk, and then insert the next before answering ‘Y’. Once you are finished loading P-Files, you are then given the option to load sequential files. If you intend to load sequential files into the expander, remove the P-Files loading disk and insert the sequential files loading disk before answering ‘Y’ at the prompt. DO NOT FORGET TO INCLUDE THE FILE ‘m5’ AND ‘prg.setup’ AS DESCRIBED IN CHAPTER 3. Note that you must load at least one P-File before being able to load any sequential files into RAM.
If you have selected not to load p-files into RAM or if you have finished filling the expander, you will next be instructed to insert all system disks, and press RETURN. Before pressing RETURN, insure that the disks that you configured the system onto are placed into their correct drives, the disk drives are all on, and your modem is turned on, if it has a power switch. If the system has been configured correctly, the disks will spin for several minutes as the program goes through all set-up routines. Soon, the “C-NET: Waiting for call” message and ‘System Monitor’ screen will be displayed.
5.4 CREATING THE SYSTEM OPERATOR ACCOUNT
If this is a brand new BBS, after booting the system for the first time there will be no user data. Not even an account for you the System Operator. So, the first thing you need to do is create an account for yourself with all the rights and privileges that will allow you complete and utter control of your system.
Following is a walkthrough to get you started.
5.4.1 LOGGIN ON FOR THE FIRST TIME
From the “Waiting for call” screen access the light bar controls (the four arrow keys in the upper right hand corner of your keyboard). Press the “right arrow” key until the light bar has highlighted the letters “LO”. Now press the “up arrow” key to toggle the “LO” option on. You will notice a check mark appear to the left of the letters “LO” and simultaneously the screen will clear and the system will be prompting you to hit the INST/DEL key. Hit the INST/DEL key now.
When the “LOGON:” prompt appears type:
NEW
And hit RETURN. You will now be placed in the “New User Application” (see section 5.4.2 for more information). Fill out the requested information and follow the prompts. After you have completed the “New User Application” and have practiced logging in by typing your new ID and PASSWORD you should after following the “Logon Flow” (see section 5.4.3 for more information) arrive at the MAIN prompt.
Now you need to give yourself System Operator access. Access the light bar arrow controls one more time. Press the “left arrow” key once so the letter “AC” is highlighted. Then press the “up arrow” key to toggle the option on. A check mark should appear to the left of the letters “AC”. Now on the left-hand side of the Status Screen (where your information is now displayed), in the middle you will see the letters “AC” again. Accessing the light bar arrow keys, press the “right arrow” key until the value next to the letters “AC” is the letter “e”. System Operator access should be at level 14, the highest access level possible in C-NET. The letter “e” in hexadecimal equals 14. Now press the “up arrow” key again to toggle the “AC” option off on the light bar (the check mark should be removed from the left of the letters). Now at the MAIN prompt type the letter “O” for OFF and hit RETURN. You will be prompted if you would like to logoff the system. Press “Y” for Yes. You will be prompted if you like to leave Feedback, press “N” for No. The system will log you off and save your new access information.
You are now a System Operator. Good Luck!
5.4.2 NEW USER APPLICATION
Entering NEW (which you will have to do initially to become a user of your own system) will begin the new user application process. The status window will display ‘new user login in progress’ to the left of the time remaining (TIME=) display until the new user login process has been completed, or, if it is aborted, another user logs on. The file ‘sys.new user’ (if present on your system disk) will be displayed at this time. The new user login
process consists of these four parts:
(1) General information (a handle to use on the system, a real name, a phone number, a password, two lines of address, and a birth date). (2) Terminal parameters (computer type, whether or not lower case will be used, screen width in columns, screen length in rows, whether or not linefeeds are required after carriage returns, whether or not the ‘More?’ option will be used, the user’s chosen level of system help, the user’s time zone, and whether or not the user is ‘private’). Several of these parameters require further explanation:
‘MORE?’ OPTION: If enabled, will cause screen output to be paused after the screen is filled, until the user presses a key. If the ‘N’ key is pressed at a ‘More?’ prompt, an attempt will be made to abort the output.
HELP LEVEL: If set at ‘beginner’ will cause the system to display important commands before every command level prompt. If set at ‘novice’ these command helps are suppressed. If set at ‘expert’ other system files, such as entry information to message bases and file transfer areas is also suppressed.
TIME ZONE: A use may select a number of hours (-23 to +23) that his particular time zone is different relative to the system will display all dates (normally displayed in system time) relative to any given user’s time zone -­ as if the system were in his own time zone.
PRIVATE: If a user selects that he does not want his info private, all other users are able to perform commands to display his real name, address, phone number and birth date. That is, the user does not mind that other people on your system can view his normally confidential information.
(3) Miscellaneous questions. As initially programmed the system requests the user’s occupation and favorite color for your information. This information (along with the personal statement to follow) is written into a file for your review -- it is not retained by the system. You may alter the miscellaneous questions by changing the DATA statement on line 62048 of the file ‘prg.new user’. The first data element, an integer, tells how many questions (in quotation marks) are to follow.
(4) A personal statement (a chance to type a paragraph or two briefly explaining anything else that needs explaining).
The ‘prg.new user’ has been updated a bit. It now allows zip codes of 9 digits. That allows for the new zip codes, as well as the Canadian Postal Code. The program also defaults to ‘new Commodore’ prompts for new users. It doesn’t ask the user for his state/province, since it already has that information from the phone number area code that the user inputs. It does allow the user to change the state/province when it verifies the data from
the user in case there is an error. Users must put something in the address question, and when asked for the user’s personal name, it prompts the user to input both first and last name.
If you create a file ‘sys.badnames’ on your system disk, the system will allow you to disallow certain handles or handle fragments from being used on the system. Again, refer to section 16.1 for information about creating files. Each line of the file should be written to contain a separate pattern. Use the left arrow character (underneath the ESC key) to represent spaces, before, after, or contained within patterns. For example, if you enter TOM on one line, the system will not allow TOM TURKEY, ATOM or ATOMIZER to be used as handles. Using _TOM instead will allow ATOM and ATOMIZER, but not TOM TURKEY because the line _TOM must match a space before TOM. Entering _BAG_ will not allow handles containing the word BAG, but will allow BAGGAGE and ABAGALE, because the line _BAG_ must match spaces on either side of the word BAG.
When the new user process has completely finished, the user is automatically given an access grouping of 0. Local callers, however, may have a way around this!
When the system is fully operational, you may configure a feature known as AUTO CALL-BACK VALIDATION. Auto call-back validation allows you to have your system automatically use the modem to call new users back who live within your system’s local calling area, and give them a predetermined access grouping other than zero. Use the program file ‘prg.utilities’ to configure this feature. A program file like ‘prg.utilities’ must be added to a system p-files library and executed (see chapter 11) to be usable. This feature is only available for use with the Hayes compatible and the 1670 modems.
If there are prefixes of another area code besides your own that are also local to you, you must enter the second area code followed immediately by the prefix within the second area code for each such prefix when asked for prefixes by the ‘prg.utilities’ configuration program.
A new mod that has been made for C-Net 128, is one called ‘prg.send welcome’. After a new user has used the auto-validation, the next time they log on, the program asks for his last four digits of his/her phone number. It then writes your ‘sys.aboard’ to their mail box automatically. So be sure you have written a ‘sys.aboard’ text file welcoming your new users.
5.4.3 LOGON FLOW
The following occur once a user has successfully logged on to the system (not aborted by INSTANT login):
(1) The user is informed of the number of calls that he has remaining to make to the system this day (only if not an infinite number more).
(2) The file ‘sys.welcome’ will be displayed (if present on the SYSTEM DISK). Note: if the user used ‘!’ following his logon ID when signing on, this file will be suppressed. Another way to go through this file quickly is to hit the space bar as soon as it appears, and then the file will abort.
(3) The system will check the directory of system news files, to see if there are any new files to be displayed to the user. If so, there will be at this time.
(4) If the user hasn’t called since his last birthday, the system will greet him with “Happy Birthday!” All new users fall into this category.
(5) The system will offer to check all message bases for new messages. If the user selects to do so, the system will construct a table of message base names, the number of messages on each, followed by the number of new messages on each.
(6) If the user new mail waiting for him, he will be informed of the new mail.
(7) Another handy feature in C-Net, is what is called the instant logon. A user may use their Login ID followed by an exclamation mark (!) (e.g. EC251!). The BBS will then ask for the user’s password. Once that has been verified, the user is taken directly to e-mail if he/she has any waiting for them, otherwise, they are taken directly to the Main Prompt. That way, the user can bypass all the questions that are asked in the logon process.
The MAIN command level is where the user is normally placed after this has been completed.
Another handy little item, is when the sysop is in system maintenance, and he/she is reading the new user information, the sysop can use the ‘X’ command to automatically send a welcome e-mail to the new user. That way, the user feels that he/she is welcome to the board and may spend more time with your board instead of calling other boards.
5.5 C-NET ‘WAITING FOR CALL’ SCREEN
5.5.1 THE STATUS WINDOW
The status window consists of the bottom five lines of the screen, which is displayed at all times, except during usage of C-NET’s built-in terminal program and the visual editor. When a user calls into the system, the status window will display many variables and statistics of his account. His status will remain displayed even after he signs off -- up until another user calls in.
The first half of the first line contains the ‘on-line’ functions menu, “SY AC LO TR CH NW PR UD MB FX” which is explained in detail in chapter 5. At the far right of the first line, appears the number of minutes remaining for the user until automatic log-off (TIME = xx). If a user has no time limit, TIME = 95 will constantly be displayed. Between the on-line functions menu and the time remaining display, exists space, which will, while a user is using the system, contain the most recently executed command, and the system prompt the command was entered from.
The next three lines will contain information about the most recent user’s account, which will be separated into sections for easy interpretation. The sections are coded as follows:
Loading...
+ 96 hidden pages
Buy Points How it Works FAQ Contact Us Questions and Suggestions Privacy Policy Cookie Policy Terms of Use