Commodore C-NET 128 v7.0 User Manual page 120

environment to edit the Npauq.* file will not work.
Zed-128, then you can read and edit the file.
files in one file, the only other difference that you will notice, is that
there are @@ (reversed) symbols every now and then.
a counter and must be in the pauq file.
**NOTE** DO NOT try to edit an outgoing Npauq.* file, only edit incoming
Npauq.* files. The reason for this, is the proper placement of the
counters. The counters must be in the proper place.To edit the incoming
Npauq.* file, load it into Zed-128 (remember, you may need to use an REU or
RamLink to get enough memory, as some of the Npauq.* files may be a little
large). Once you have the Npauq.* file in memory, you then have to
manually break down the file.
any problems. Use the control-M keys to set the mark for delete and the
control-D to delete lines as required.
Nstrt.*, etc., as required.
each file as needed.
scratch any Npauq.*, Nsubs.*, Nlist.*, etc., files, as well as any nr.*
files. The reason for this is to cut down on duplications
Your Nmail.* file will have the same type of setup as the Nsubs.*, except
that the header is only five (5) lines long rather than seven (7).
first line will have an asterix and the name of who the mail is being sent
to. The next line will be the origin BBS.
sending the net mail and the fourth line will be who sent it.
line will be the date stamp.
marks in front of each line.
mail is not distributed properly, so when you are checking you net log
'NL', see if there has been any net mail.
sysop or users have received any mail.
the sysop or some non-deliverable mail, use the 'ND' command to break down
the dead mail. Sometimes an error can happen and mail may not be
distributed to the proper individuals.
22.4 FLOW CHARTS
Caped Crusader has been good enough to make up two flow charts to show what
happens when a person responds to a message in the base, and what happens
when your board receives an incoming message pack from a networked board.
These two flow charts will follow at the end of this manual.Also included
as extra sheets, is what a sample Nacti* file would look like as well as an
Nstrt* file. These are printed out so you have an idea of what information
they contain, and are for informational purposes only.
22.5 EXPLANATION OF PRG.* FILES
This chapter will try to explain (in simple and short detail) what each
main prg.* file does.
programming, just a very short explanation.
C-Net 128 is a marvel as a BBS program.
small programs.
for it to work.
That little feature makes lots of memory room for other things, as well as
speeding up the program.
What I will try to do, is to let you know what each program does, but I
will do it in alphabetic order.
program file 'cn'.
cn This is the main program file.
I have found this is the best way to solve
Once you have done that, then you can edit
Before you move the files back onto your 8,0 drive,
Once again, the text will have exclamation
One item to not forget here, is sometimes net
This is not meant to be a course on basic
The BBS does not have to have the whole program in memory
The software only loads what required in order to operate.
The only exception here is the main
However, if you use
Other than having all the N*
This symbol is used as
Save the files as Nsubs.*, Nlist.*,
The third line will be who is
The log will tell you if the
If you see that there was some for
The BBS program is made up of many
This is the file that
The
The last