home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
PCBOARD
/
CW_PM_31.ZIP
/
POWERPAK.DOC
< prev
next >
Wrap
Text File
|
1994-01-12
|
69KB
|
1,181 lines
· · · ┌────────┐ · · · ·
· · │ ┌──┐ │ ·
· · · ┌───────┤ └──┘ ┌┴───────┐ · ·
· │ ┌──┐ │ ┌────┤ ┌──┐ │ · ·
│ └──┘ │ │ · │ └──┘ │ .
. │ ┌────┤ │ │ ┌─────┘ . ·
· · │ │ · └──┘ │ │ · ·
· │ │ │ │ · ·
· └──┘ · └──┘ · ·
. .
The PCBoard PPE PowerPack! 01-12-94 v3.1 Author: Cliff Watkins
Page 02 <BF-Ratio> Ratio adjustments the way PCBoard used to! Adjust
ratios by files, bytes, skip until # of files etc.
Page 03 <BBSListr> A full featured BBS list door, allows searches by
many criteria as well as adding new BBS listings!!
Page 04 <ConfJoin> Vastly improves the PCBoard J command! Now you can
have menus for each net or conf group on your BBS!
Page 05 <SubscriP> Permit "instant subscription upgrades" on your BBS
without the hassle of dealing with C.C. companies!
Page 08 <Pro-Vote> Set up Voting Booths and/or Opinion Polls on your
BBS, up to 32 of them! Show results, tallies, etc.
Page 09 <TimeZone> Setup time slots on your BBS and this does it like
none other ever! Options galore and NO user limit!
Page 11 <MsgQuest> Take script questionnaire answer files, logs them,
inserts them into your msg base addressed to you!
Page 12 <HowHeard> Adjust users security levels based on responses to
the "How did you hear of us" type questions.
Page 13 <WelcoMat> If you know what users are going to call you, you
can put them in here to upgrade upon their logon!
Page 14 <SpeedLim> If you want to allow only "certain" users to call
you at a certain speed and no others, use SpeedLim
Page 15 <UserNews> Allow your users to enter their own news snippets!
Similar to "grafitti" but a bit more professional!
Page 15 <Time-Adj> Allow certain sec levels to have "time used" reset
with every logon. By sec level so not like PCBoard
Page 16 <Pro-Menu> Never again worry about "security specific menus"!
Displays which commands are available/unavailable!
Page 17 <PPE-Menu and Force-It> Two free, simple but very useful PPE's
for your use (or your non-use <g>).
Page 18 <Intelec PPE> The Ultimate! Freeware Database and Application
Generator for the Intelec Network. Check it out
Page 19 <History!> Page 20 <Registration and Support Info>
┌────────────────────────────────────────────────────────────────────┐Page
│ BF-Ratio PCBoard 15.1 PPE Security Level Adjuster <Shareware> │ 02
└────────────────────────────────────────────────────────────────────┘
This PCBoard 15.1 PPE, when placed in the security specific logon file
can adjust users security level by either file or byte ratios. You can
setup BF-Ratio as "no adjust til # of file DL's = 5" (or whatever #).
BF-Ratio Installation.
Install BF-Ratio by placing the full BF-RATIO.PPE command into any of
the security specific screens that you want to adjust. On my system,
my level 21 users must maintain a 5:1 byte ratio. If they exceed it I
want them "adjusted" to security level 20. My security specific logon
screens for both levels contain 1 line each as follows:
!D:\PPE\PPP\BF-RATIO.PPE B 20 5 21 5 <- my 20. security file
!D:\PPE\PPP\BF-RATIO.PPE B 20 5 21 5 <- my 21. security file
The reason I have the "same" line in both is so that BF-Ratio will ad-
just level 20 users "back to level 21" when they correct their ratios.
By placing this in the security specific logon files, the user is ad-
justed (or not) each time they call in. I know that PCBoard supports a
"real time" ratio adjuster, that's great. But I'm from the old school,
I prefer that the security level be "changed" as well so I can control
things such as amount of time that leaches get (PCBoard ratios do not
support this). By changing sec levels, now I can have a different news
screen, different time allotments, different menus, control access to
doors, etc. I am not interested in a ratio method that ONLY controls
byte or file access, I want it ALL <g>.
Now I'll describe the "commandline" that follows each of the BF-Ratio
PPE commands in these security specific logon files:
┌── B= Bytes F= Files (Adjust by bytes or files)
│ ┌── If Exceeds ratios, adjust to this sec level
│ │ ┌── Ratio that if exceeded adjust will occur
│ │ │ ┌── If Ratio corrected adjust to this sec.
│ │ │ │ ┌── Skip until downloads meets/exceeds.
│ │ │ │ │
!D:\PPP\BF-RATIO.PPE B 20 5 21 5
By using this method, there is as much flexibility as possible so that
you can customize this easily to suit your systems' needs.
BF-Ratio Config File.
The config file, and all BF-Ratio files, must be in the same directory
as the BF-RATIO.PPE file. The config file MUST be called BF-RATIO.CNF.
Here's a sample BF-RATIO.CNF file, an expanation of this file follows.
┌─────────────────────────────────────────┐
│ Your BBS Name │
│ 00000 (or your registration number) │
│ Validation Code (given when registered) │
└─────────────────────────────────────────┘
Line 1 = Who registered to
Line 2 = 00000 (if unregistered) or your registration number
Line 3 = Validation Code (if unregistered leave blank)
┌────────────────────────────────────────────────────────────────────┐Page
│ BBSListr PCBoard 15.1 PPE BBS List PPE Utility <Shareware> │ 03
└────────────────────────────────────────────────────────────────────┘
BBSListr does more than most BBS List utilities. Aside from A)dding
to the list, it also gives you the ability to search the list by
multiple fields, such as by BBS software, Area Code, Modem Type, State,
Country, Meg Size, # of Nodes, Access Policies and more. It's a VERY
complete and compact utility!
The installation of BBSListr is very. Just install as a command in the
PCBoard CMD.LST file and you're all set. There's a little bit you will
to do with the config file (explained below). For more info on the PCB
CMD.LST file, please see your PCBoard 15.1 docs. The config file MUST
be located in the same directory as BBSLISTR.PPE and it MUST be called
BBSLISTR.CNF. An explanation of the config file follows:
Config File Details
┌────────────────┐
│ Intelec Online │ -> Who registered to (a BBS name or SysOp name)
│ 00000 │ -> Registration number (00000 if unregistered)
│ ##### │ -> Validation code (assigned upon registration)
│ BBSLISTR.LST │ -> Pull Path AND Filename to the "BBSLISTR.LST"
│ 1 │ -> This is the total number of "entries" in the
└────────────────┘ BBSLISTR.LST file. BBSListr maintains this #
for you automatically! If you are starting a
brand new list, make this a 0. If you add a
BBS to the list to start it off you'll find
this number is incremented to 1 by BBSListr.
BBS Listr gives your users a very easy to use menu! Nothing's easier!
┌────────────────────────────────────────────────────────────────────┐
│ │
│ BBS Lister - Main Menu │
│ │
│ A Add To List S Search List G Goodbye │
│ │
│ V View List Q Quit To BBS │
│ │
└────────────────────────────────────────────────────────────────────┘
It also provides many different search criteria, very complete indeed.
┌────────────────────────────────────────────────────────────────────┐
│ Search Criteria │
│ 1 By State 4 By BBS Type 7 By Meg Size │
│ 2 By Country 5 By Modem Type 8 By # of Nodes │
│ 3 By Area Code 6 By Access Policy 9 By Text String │
└────────────────────────────────────────────────────────────────────┘
This gives you an idea of the way the BBS list is formatted:
**********************************************************************
PCB Intelec Online 516-868-1741 v.32bis NY Baldwin R 18/ 2
Intelec Network Host BBS - Professionals Only - Over 18 Only!
**********************************************************************
PCB Big Apple BBS 516-536-1546 v.32bis NY Rockvlle Ctr R 11/ 1
Planet Earth, Intelec, Smartnet and MSI networks, 1000's of files
**********************************************************************
┌────────────────────────────────────────────────────────────────────┐Page
│ ConfJoin PCBoard 15.1 PPE J Command Replacement <Shareware> │ 04
└────────────────────────────────────────────────────────────────────┘
Make your PCB J command customized for the networks your BBS carries!
Installation of ConfJoin is really very simple. ConfJoin should be
installed in your CMD.LST as a replacement for the J command. Go into
PCBSetup CMD.LST section (B: File Locations, B: Configuration Files)
Now go to the CMD.LST section and F2 to edit it. Add a line as shown:
Command Security PPE/MNU File -or- Keystroke Replacement
======= ======== ========================================
J 5 E:\PCB\PPE\CONFJOIN.PPE
Make the security level at whatever you desire, it is a good idea to
make it the same as you defined in the "User Security Levels" section
of PCBSetup. Lastly, then add the full path and filename to ConfJoin.
For more info on CMD.LST see PCB docs. ConfJoin allows you to group
networks (up to 32 at this time) and display them to your users in a
much more organized manner. For those running just a single network,
such as myself, I have my conferences grouped into categories instead
by network (ie; Administrative, Tech_Support, Vendor_Support etc) and
I've included them as samples. The configuration file must be located
in the same directory as CONFJOIN.PPE. A sample CNF file is explained
below and MUST be called CONFJOIN.CNF. Remove the comments if you use
the one below:
Your BBS Name
00000 (or your registration number)
Validation Code (given when registered)
E:\PCB\PPE\CJMENU ;Path/filename of the Menu of networks or categories
8 ;Total number of networks or categories listed below
E:\PCB\PPE\CJ-A ;Path/filename submenu of network #1 or category #1
E:\PCB\PPE\CJ-I ;Path/filename submenu of network #2 or category #2
E:\PCB\PPE\CJ-G ;Path/filename submenu of network #3 or category #3
E:\PCB\PPE\CJ-T ;etc etc etc...
E:\PCB\PPE\CJ-V ;and so on up to 32 (max) if you have that many. If
E:\PCB\PPE\CJ-P ;not, then simply end the config file with the last
E:\PCB\PPE\CJ-R ;category, but make sure the no. on line 5 of config
E:\PCB\PPE\CJ-E ;file matches the number of networks or categories!
Also, for those users who know exactly what conference they wish to
join, ConfJoin recognizes stacked conference no./name of (ex:) J 225,
and drops them into the requested conference, bypassing the menu. The
users who know just where they are going should not be penalized <g>.
Full PCBoard conference security, additional time, etc is maintained.
Notes
It appears that at the "end of message" PCBoard prompt, the J command
can be invoked. Apparently the PCBoard J command at this prompt isn't
the same as the J command from the "main prompt" since even with my
ConfJoin installed as a J command replacement in CMD.LST, PCB ignores
it at an "end of message" prompt J command. Solution, make your CNFN
file look like this one single line ----> !E:\PPE\CJ\CONFJOIN.PPE
or whatever your path/filename to ConfJoin really is. Then even if J
is issued at an End of Message prompt ConfJoin will still be invoked.
I'm not sure why PCBoard works this way, but this is a work-around...
┌────────────────────────────────────────────────────────────────────┐Page
│ SubscriP PCBoard 15.1 PPE Instant Subscribers! <Shareware> │ 05
└────────────────────────────────────────────────────────────────────┘
Do you want to offer instant subscriber upgrades to your users? Do you
hate dealing with credit cards and CC companies? Do you wish there was
an easier and more affordable way? Well, guess what... Now there is!
This PCBoard 15.1 PPE utility will allow you to accept subscriptions,
and to let the new subscriber be upgraded *instantly*. This program is
for SysOps who do not or cannot accept credit cards from their users.
This will show the users your subscription options (up to 10) and will
upgrade them based on the information in the SUBSCRIP.OPT file. In the
registered version of SubscriP, the program will track when the user's
subscription amount is "due" and if this date is exceeded and you have
have not rec'd their check, it will downgrade them to the level you've
setup as well as removing any "conference registrations" that SubscriP
gave to them (you configure this in the file SUBSCRIP.OPT). I will ex-
plain SUBSCRIP.OPT and other files more, but first the installation,
it's the easiest part of all.
SubscriP Installation.
Ensure that you have the "Notes PSA" installed, this is a requirement
for proper operation of SubscriP.
Go into the CMD.LST and make a command called SUBSCRIP or SUB or other
appropriate name. See below, and use an appropriate security level.
Command Security PPE/MNU File -or- Keystroke Replacement
══════════════ ════════ ═══════════════════════════════════════
1) SUBSCRIP 10 D:\PPE\SUBSCRIP.PPE
The user-portion of SubscriP is now installed (wasn't that easy)!
* (The following checking feature is available only when registered)
Now we need to install the "checking portion" of SubscriP. If you want
SubscriP to check for the "due date" for you then it must be installed
in one of the display screens with a commandline of S. I use it in my
"security specific display screens" so that it only checks subscribers
and not each user. My subscriber sec level 41 specific file (called 41
natcherly) contains one line and it looks like this (notice that there
is an "S" on the PPE commandline):
!D:\PPE\SUB.PPE S
Also notice that this is the same PPE. This checking feature is built
right into the SubscriP PPE! The "checking portion" is now installed!
Let me explain how and why this works:
When a subscription is purchased, a line is written into the notes PSA
that looks similar to this (I use #3, you can use whichever you like):
╔════════════════════════════════════════════════════════════════════╗
║ Edit User Record (Caller Notes) Record # of # ║
║ ║
║ Name : HOWARD STERN ║
║
║ Line 3 : 5 On 10-31-93 a check for $25.00 is due. ▒
┌────────────────────────────────────────────────────────────────────┐Page
│ SubscriP PCBoard 15.1 PPE Instant Subscribers! <Shareware> │ 06
└────────────────────────────────────────────────────────────────────┘
Whenever one of my level 41 subscribers logs on it checks in the notes
PSA to see if the "check has arrived". When a check arrives I go into
that user's record, go to line 3, and tap the space bar thus clearing
out this entry. If a user calls after the date in the "Notes PSA" and
I've not gotten a check (and have not cleared their "entry") then this
program will detect the date and it downgrades the user to the expired
security level.
(The due date checking and messages are only enabled when registered)
Whenever a user subscribes SubscriP sends a message to the SYSOP so he
or she is aware that a user is forwarding a check and when it is due.
Whenever a user's "due date" is past due, SubscriP sends a message to
the both the user and the SysOp, informing both of the situation. You
can customize this message to the user to suit your particular style.
The SubscriP Config File. (It must be called SUBSCRIP.CNF and must be
located in the same directory as the SUBSCRIP.PPE)
┌────────────────────────────────────────────────────────────┐
│ Your BBS Name │
│ 00000 (or your registration Number) │
│ Validation Code (assigned Upon Registration) │
│ D:\PPE\SUB\ (location of display files, use the backslash) │
│ Number of days to wait for check (we suggest 10-14 days) │
│ The line number in the "Notes PSA" to use (I use number 3) │
│ The MINimum security level to permit purchases. │
│ The MAXimum security level to permit purchases. │
│ The total of subscription options (1 if unregistered) │
└────────────────────────────────────────────────────────────┘
If you put a sec level of 0 in CMD.LST, a 20 on line 7 and 50 on line
8 of CNF file, you can allow all users to "see" your options but limit
actual usage to those between security levels 20 and 50. This is added
for more flexibility.
SubscriP also keeps 2 logs, one for those who've subscribed (for added
sense of security) called SUBSCRIP.YES and a 2nd log of those who ran
SUBSCRIP.PPE but didn't subscribe called SUBSCRIP.NO (for the curious)
SubscriP Display Files. They are the files that SubscriP will look for
when running for display purposes. You must use these names and they
must be located in the directory as defined in line 4 of the CNF file.
These are the file names and their respective descriptions:
SUBSCRIP.ADD - Additional display, so I use it for my mailing address.
SUBSCRIP.DSP - This is the actual menu choice display shown to users.
SUBSCRIP.EXP - If check doesn't arrive, this text is messaged to user.
SUBSCRIP.NOS - This is displayed if user has insufficient to purchase.
SUBSCRIP.NXT - This is displayed if usr exits without making purchase.
SUBSCRIP.TOO - Shown when a users' security is too high for purchase.
SUBSCRIP.UPG - Displayed when a purchase is made and user is upgraded.
SUBSCRIP.WEL - The opening "welcome screen" shown when it's first run.
SUBSCRIP.OPT - This is the options table which is explained next page.
You can use PCBoard color macros in the display files. SUBSCRIP.OPT is
NOT a display file, it's for data. These files are ready-made on the
Support BBS in directory #1 on the main board, available first call...
┌────────────────────────────────────────────────────────────────────┐Page
│ SubscriP PCBoard 15.1 PPE Instant Subscribers! <Shareware> │ 07
└────────────────────────────────────────────────────────────────────┘
SUBSCRIP.OPT (Subscription Options) data file. Here is how mine looks:
┌──────────────────┐
│40 5 365 2500 341 │
│41 5 365 4000 341 │
│40 5 730 4500 341 │ (start info in column one):
│41 5 730 7000 341 │
│42 5 365 7500 341 │
└──────────────────┘
Line 1 is for subscription option 1, line 2 is for option 2 and so on
through 10 subscription option if you have that many (Only 1 option is
enabled the unregistered version).
The first number in each line is for the subscriber security level for
that particular option.
The second number in each line is for the "expired security level". If
payment is not rec'd by due date then the user is downgraded to this.
The third number in each line is for the "days to expire" better known
as the good old expiration date. Mine are 365 and 730 for 1 and 2 year
subscription terms.
The fourth number in each line is the cost of the subscription and it
must be shown it "totals cents". If I charge $25 for a level then it
must show 2500 as the 4th number for that option. If I charge $50 for
for another level then the 4th number for that option must be 5000 and
so on.
The 5th through 14th #'s are for conferences that may be part of the
subscription plan (ie CD-Rom conference, etc). I only show 1 above but
you can have up to 10 confs here as my example on the line below shows
42 5 365 5000 341 10 17 25 42 112 75 52 2257 513
42 is the new security level for this subscription option.
5 is the expired security level.
365 is for a one year subscription term.
5000 is for a $50.00 cost
All the numbers shown above between 341 and 513 would be registered
for this user. We are hoping to add conference registration by "range"
but haven't figured the best approach yet.
As part of the "due-date checking" feature, if a check isn't rec'd yet
and a user is downgraded, ALL these conference registrations are also
removed from the user's record.
┌────────────────────────────────────────────────────────────────────┐Page
│ Pro-Vote PCBoard 15.1 PPE Voting and Polls! <Shareware> │ 08
└────────────────────────────────────────────────────────────────────┘
The installation of Pro-Vote is fairly simple. Pro-Vote should be in-
stalled into your CMD.LST as the command (usually VOTE) that you wish
to assign to it. The configuration, questionnaire & display files must
be located in the same directory as the PRO-VOTE.PPE. A sample config
file is explained below and must be called PRO-VOTE.CNF.
The Pro-Vote MAIN Config File:
┌────────────────────┐
│ Intelec Online │ -> Who registered to (a BBS name or SysOp name)
│ 00000 │ -> Registration number (00000 if unregistered)
│ ##### │ -> Validation code (assigned upon registration)
│ E:\PV\PRO-VOTE.DSP │ -> Full path/filename to menu of poll options.
│ 5 │ -> The # of polls that you've config files for.
└────────────────────┘
The Pro-Vote POLL Config File:
For Poll #1 you need a separate config file called PRO-VOTE.01,
for Poll #2 the config file is called PRO-VOTE.02 and so on,
But start all info in column (1). This file is 23 lines.
Question To Ask ; Line 1 - Question (up to 75 chars)
1 ; Line 2 - Total Votes from this question
8 ; Line 3 - Total number of Options
MsgQuest ; Line 4 - Option #1
0 ; Line 5 - Number of votes option 1 got
ConfJoin ; Line 6 - Option #2
0 ; Line 7 - Number of votes option 2 got
HowHeard ; Line 8 - etc...
0 ; Line 9 - "
TimeZone ; Line 10 - " Options can be as many
1 ; Line 11 - " as 65 chars in length!
WelcoMat ; Line 12 - "
0 ; Line 13 - " When starting a new poll
Pro-Vote ; Line 14 - " make line #2 a 0 as well
0 ; Line 15 - " as lines 5, 7, 9, 11, 13
SpeedLim ; Line 16 - " and each subsequent odd-#
0 ; Line 17 - " line that follows.
Intelec! ; Line 18 - "
0 ; Line 19 - "
; Line 20 - "
0 ; Line 21 - "
; Line 22 - "
0 ; Line 23 - "
The Poll USER NAMES File:
For Poll # 1 it's called PRO-VOTE.01N, Poll # 2 is PRO-VOTE.02N and so
on. Pro-Vote appends the user's name to this file as soon as the user
answers a particular Questionnaire/Poll so that they can't "re-answer"
the same one. Pro-Vote creates this file automatically for every Poll
answered so you really don't have to worry about creating it yourself.
Pro-Vote supports up to 32 different polls (5 in unregistered version)
┌────────────────────────────────────────────────────────────────────┐Page
│ TimeZone PCBoard 15.1 PPE Time Slot Manager! <Shareware> │ 09
└────────────────────────────────────────────────────────────────────┘
The installation of TimeZone is fairly simple. TimeZone should be in-
stalled into logon script questionnaire (my setup is shown below). Run
PCBSetup, go to File Locations and then to the Questionnaires section
as shown below. Now in my setup, the file defined below as "LOGON" is
not actually a script questionnaire, but it's really a text file, also
shown below. Substitute file names and paths that apply to your setup.
You must also enable the "Notes PSA" in the user records. See PCB doc.
╔════════════════════════════════════════════════════════════════════╗
║ File Locations ║
║ NewUser/Logon/Logoff Questionnaires ║
║ ║
║ Name/Loc of New Reg Questionnaire : E:\PCB\MAIN\LOGONNEW ║
║ Name/Loc of Answers to New Reg. : ║
║ ║
║ Name/Loc of Logon Script Quest. : E:\PCB\MAIN\LOGON ║
║ Name/Loc of Logon Script Answers : ║
║ ║
║ Name/Loc of Logoff Script Quest. : E:\PCB\MENU\BYE ║
║ Name/Loc of Logoff Script Answers : ║
║ ║
║ Press F2 to edit the NEWASK file or F3 to edit the NEWASKG file ║
╚═ hh:mm ══ mm-dd-yy ══ F1 ═ help ═══ caps: OFF num: OFF ins: OFF ═╝
My "LOGON" script questionnaire really only consists of two lines, the
first one is the only applicable one for the installation of TimeZone.
Change the path to fit your setup though. here's my LOGON script file:
!E:\PPE\TIMEZONE\TIMEZONE.PPE
!E:\PPE\UAI\UAI.PPE
Please note that the ! in the above paths needs to be in column one!
This is all that is needed to be done to call TimeZone whenever users
call into your system. That's the installation, now to configure it...
The configuration file must be located in the same directory as the
TIMEZONE.PPE and must be called TIMEZONE.CNF.
Config File Details
┌────────────────┐
│ Intelec Online │ -> Who registered to (a BBS name or SysOp name)
│ 00000 │ -> Registration number (00000 if unregistered)
│ ##### │ -> Validation code (assigned upon registration)
│ A or B │ -> See notes on A/B switch (You will love this)
│ 60 │ -> The "exempt" security level (blank if none)
│ 22:30 │ -> The time when TimeZone is to be "activated".
│ 06:30 │ -> The time when TimeZone is to be de-activated
│ 1 │ -> Which note line to write time slot or EXEMPT
└────────────────┘ to in user's record. Enter time slot as (ex)
02:30-03:30 in the 1st 11 spaces in the note
field. Don't put anything else in this field!
See note below on the EXEMPT flag in the user
record notes.
┌────────────────────────────────────────────────────────────────────┐Page
│ TimeZone PCBoard 15.1 PPE Time Slot Manager! <Shareware> │ 10
└────────────────────────────────────────────────────────────────────┘
The A/B Switch!
There are now two methods of operation in TimeZone now! A, the standard
way I've seen any time slot utility operate, is that you assign a user a
"minutes window". If they call in any time during that window then they
are granted access with their full amount of allotted time. Problem here
is that if a user has 30 minutes allotted and calls at the very "end" of
his or her window, there's the possibility of this user running into the
next users "window". Scenario: John Smith has a time slot of 06:30-07:00
and Jim White has a window of 07:00-07:30. They both have 30 minutes per
day allotted to them. If John Smith calls at 06:59 he can tie up the BBS
until 07:29. Now, Jim White has only 1 minute in which to make his time
window. Thus the B Switch! When using this B method of operation you can
prevent the above scenario from happening. If John Smith calls at 06:45,
instead of having his full 30 mins, now he only has 15 mins, preventing
him from interfering with Jim White's time slot. I do this by adjusting
the "time left" info in the user record, *not* the time used info. This
way if they call back when TimeZone is not enabled they have their full
allotment of unused time. But there are the traditionalists <g> who will
prefer to run this the "standard" way, and if so, just use the A Switch.
Exempt Flag Options
There are two ways of exempting users from being effected by TimeZone's
operation. One is exempting all user with xx security level or higher by
entering this desired security level on line 5 of the config file. (Ex:)
If you want to exempt level 60 users and higher from being "cut off" by
TimeZone, place a 60 in line 4 of the config file. If there's a user who
has a securoty level below 60 and you want to exempt this user as well,
then place EXEMPT in the first 6 spaces of the notes field. Note: If you
are using the "B method" of TimeZone, this "exemption method" won't let
them have more time than what would exceed TimeZone's "starting time".
The other way of exempting users on an individual basis is to place the
string EXEMPT in the designated user record note field. This method WILL
totally exempt the user from any type of time adjustments that TimeZone
would normally attempt to make on the user regardless of who's time slot
this user may infringe upon. This should not be used too frequently but
has been included to make TimeZone the most effective and flexible way
to manage time slots on your system.
What It Does To Who
If a user calls you when TimeZone is enabled, and they do not have a
slot, they will be displayed the time, the time frame that TimeZone is
enabled, and then logged off.
If a user calls you when TimeZone is enabled, and they DO have a time-
slot, if they called when it was their proper time they will be shown
a screen showing that TimeZone has let them pass. But if they called
outside of their assigned time slot, they'll be displayed the current
time, and what their time slot IS, and then it logs them off. Also, if
you want to run TimeZone on one node only (or specific nodes) then on
this (or these) nodes you'll need to update that nodes' PCBOARD.DAT to
reflect a "different" logon script that contains TimeZone in it only.
┌────────────────────────────────────────────────────────────────────┐Page
│ MsgQuest PCBoard 15.1 PPE Scripts to Msg Bases <Shareware> │ 11
└────────────────────────────────────────────────────────────────────┘
This PCBoard 15.1 PPE utility will take the answer file from a PCBoard
questionnaire and insert it into your message base. It is configurable
as far as who you want it addressed to, whether you want it public or
private, echoed or not echoed, the subject line, which message base to
insert it into and even answer logging. MsgQuest can handle up to five
script questionnaires, each one with different configuration options.
MsgQuest will insert the script answer file into the message base you
configured it to, then it deletes the script answer file so that it is
not re-inserting the same answer file over and over again. That is why
we strongly recommend that you use the logging option!!! Also, we are
concerned about message security, we urge you to use SYSOP or another
"secure name" in the "Msg From" line(s) of the config file.
Installation of MsgQuest is now finally simple! MsgQuest comes with a
companion utility called FORCE-IT.PPE, which I'll explain in a moment.
First, install MsgQuest as a command in CMD.LST (preferably MSGQUEST).
Then, change your PCBTEXT prompt number 103 to look like:
%D:\PCB\MAIN\PCBTEXT.103
or whatever path you would like to use. Next, you should make the file
PCBTEXT.103 to match your file path. Here's the 2 lines my PCBTEXT.103
file with an explanation following:
@INCONF@Questionnaire (@OPTEXT@) info saved.
!D:\PPE\PPP\FORCE-IT.PPE MSGSQUEST
The first line in PCBTEXT.103 replaces the prompt now missing from the
PCBTEXT file. The second, the one calling the FORCE-IT.PPE, takes it's
commandline (MSGQUEST) and once the questionnaire is saved, FORCE-IT
stuffs the MSGQUEST cmd into the keyboard buffer thus running MsgQuest
immediately *after* the questionnaire is saved. This may be confusing
to some of you not familiar with PCBoard or PPEs but due to the timing
of how PCB processes it's scripts it's necessary. Otherwise, MsgQuest
will try to process script answer files before it is actually saved by
PCBoard (figure that one out!). But it is working fine on my system!
MsgQuest Config File.
Every script questionnaire that you want configured is to have 8 lines
in the config file. Replace the lines in the sample config file with
appropriate paths, file names and options for your particular needs.
Line 1 = Your Board name here
Line 2 = Registration Number | Both are assigned when
Line 3 = Validation Code | you register MsgQuest
Line 4 = Any string you want (like ****) to use as a script separator
Line 5 = Message base number to insert this answer file into
Line 6 = Path and Filename of answer file "as defined in PCBSetup"
Line 7 = Name of the "log file" you desire (blank if none, See NOTES)
Line 8 = Subject line for the message inserted from this script
Line 9 = Msg To (addressed to you or SYSOP or whatever name, IN CAPS)
Line 10 = Msg From (SYSOP or MSGQUEST) (IN CAPS)
Line 11 = Message security (either R for R/O or N for public)
Line 12 = Echoed or not (1 for echoed or 0 for not echoed)
Repeat lines described for script 1 (lines 4-12) for up to 15 scripts!
MsgQuest will only process one script in the "unregistered" version.
┌────────────────────────────────────────────────────────────────────┐Page
│ HowHeard PCBoard 15.1 PPE New Caller Upgrader <Shareware> │ 12
└────────────────────────────────────────────────────────────────────┘
This PCBoard 15.1 PPE, when placed in your newuser logon script, lets
you assign up to 5 options to "How did you hear of us" or "Why are you
calling" type questions. Based on their response you can upgrade to a
specific security level, add a note to Comment Line 2, add xxx days to
exp date (or a non-expiring date) or you can even register them in a
private conference. Response can be configured individually so that no
one response gets the same upgrade options!
Installation of HowHeard is fairly straight-forward. Here is how I do
it. My new caller logon script looks like this, just 2 lines:
!E:\PPE\HOWHEARD\HOWHEARD.PPE
!E:\PPE\WELCOMAT\WELCOMAT.PPE
The first line is for HowHeard, the other is for another PPE I wrote.
There are a number of ways you can do this... you can put HOWHEARD.PPE
in your scripts, but there's no guarantee the user will answer them...
You need to create a menu file for the user to choose a "how I heard"
option, you can use PCBoard's @Xxx color macros but you need to number
the options in sequence with how listed in the config file (to follow)
HowHeard Config File.
The config file, and all HowHeard files, must be in the same directory
as the HOWHEARD.PPE file. The config file MUST be called HOWHEARD.CNF.
Here's a sample HOWHEARD.CNF file, an expanation of this file with it.
┌─────────────────────────┐
│ Your BBS Name │ Who HowHeard is registered to
│ 00000 │ 00000 if unregistered - or your reg number
│ Validation Code │ Validation Code (unregistered leave blank)
│ E:\PPE\HH\HOWHEARD.DSP │ Path/Filename of the options display file.
│ 2 │ How many options provided in config file.
│ Looking To Join Intelec │ 30 Chars for Comment2 Field in User Record
│ 40 │ New Security Level
│ 0 │ Days to Add to Exp Date (0=non-exp)
│ 1 │ Which conference to register the user in
│ Calling About The PPE's │ Lines 10-13 are same descriptions
│ 30 │ as lines 6-9 but for option 2.
│ 182 │ The registered version supports
│ 106 │ up to 5 different upgrades!
└─────────────────────────┘
All but the first 5 lines are optional, but if not used there's little
point in even using this utility. If there's a field in the configfile
that you do not wish to use (such as registration in a conference) you
must leave the line empty (blank). The Comment 2 field is limited to
30 characters. If the New Security Level field is left blank then the
security level as defined in PCBoard will be kept. If it is not used,
as with any field in the config file, you must leave an empty (blank)
line in it's place. The Days To Add to Exp Date are the number of days
to add to the date the script is answered (refered to as today's date)
and if left blank then the number of days to exp in PCBoard is kept.
If you want to assign a non-expiring exp date to a response, then put
a 0 in this entry for this response. There, I hope I haven't confused
anyone, I understand what I wrote <g>
┌────────────────────────────────────────────────────────────────────┐Page
│ WelcoMat PCBoard 15.1 PPE New Caller Upgrader <Shareware> │ 13
└────────────────────────────────────────────────────────────────────┘
This PCBoard 15.1 PPE utility will search a list of predefined names,
and if a match is found it will upgrade them to the security level you
decided on. Why? I was in a situation recently where I knew a handful
of specific users were going to be calling my board. I did not want to
pre-register all of them since A) it would have been more time than it
took to write this utility and B) I wanted them to enter complete info
into the address areas of the user records. But... I also wanted them
(and only them) to be upgraded instantly and I also wanted them to be
displayed a screen that told them I was "putting out the welcome mat"
for them and that they were instantly upgraded. Well this utility will
do all this. You select the usernames (up to 250) that you want to put
out the welcome mat for, you select the security level that you want
them upgraded to, and you customize the display file that they'll see
upon their upgrade. And... WelcoMat is intelligent, it can tell if the
caller has been upgraded already and if so, it "cancels operation" and
the caller is not shown the display all over again.
WelcoMat Installation.
Installation of WelcoMat is fairly straight-forward. Hopefully you are
already familiar with PPEs so I don't have to get overly verbose here.
Here's how I do it. My new caller logon script looks like this, just 3
lines:
!E:\PPE\WELCOMAT\WELCOMAT.PPE
!E:\PPE\HOWHEARD\HOWHEARD.PPE
The 1st line is WelcoMat, the other 2 are other PPEs I use that prompt
the user for city & state and other settings info. This way, if a user
calls me who is not in "the list" then the other PPE's ask for addi-
tional address and settings info anyway. Anyway, there is a number of
ways you can do this. You can place the WELCOMAT.PPE in your bulletins
to upgrade name matches only when the bulletin is read. It's up to you
as PCB's PPE feature makes it the most flexible BBS software ever!
WelcoMat Config File.
The Welcomat config file MUST be called WELCOMAT.CNF and must be located
in the same directory as WELCOMAT.PPE. This is very important!
┌────────────────────────┐
│ Intelec Online │ Your BBS Name
│ 00000 │ 00000 if unregistered or your reg number.
│ Validation Code Here │ Validation code given upon registration
│ E:\PPE\WM\WELCOMAT.LST │ List of names that you want to upgrade.
│ E:\PPE\WM\WELCOMAT.DSP │ Path/Filename displayed to upgraded callers
│ 50 │ Sec level you want "name matches" upgraded to.
│ 1 │ Lines 7 through 36 are for conferences
│ 106 │ that you want "matches" Registered in.
│ 107... etc │
└────────────────────────┘
The WELCOMAT.LST is an ascii list of user names with just 1 exception.
the first line is the total number of names in the list. Then lines 2
through 251 are for user names, one name per line... it's that easy...
The WELCOMAT.DSP can contain @X codes and is displayed when upgraded.
┌────────────────────────────────────────────────────────────────────┐Page
│ SpeedLim PCBoard 15.1 PPE Low Modem Speed Filter <Shareware> │ 14
└────────────────────────────────────────────────────────────────────┘
This PCBoard 15.1 PPE, when placed in your logon script, lets you have
some "low modem speed" callers get passed your high speed modem limit.
Why??? In general, I keep 2400 baud callers off my system. But I have
some 2400 baud callers whom I thoroughly enjoy their membership on my
system already. These great callers I placed in my Speed Limit configs
and regardless of their 2400 connection they can still get through! It
lets them know their speed is low, but that we're passing them through
anyway. I hope you have a use for it, I know I do...
Installation of Speed Limit is fairly straight-forward. Here is how I
do it. My new logon script looks like this, just three lines:
!E:\PPE\TIMEZONE\TIMEZONE.PPE
!E:\PPE\SPEEDLIM\SPEEDLIM.PPE
!E:\PPE\UAI\UAI.PPE
The second line is for Speed Limit, the other 2 are other PPE's I use that
check time slots or prompt the user for city & state and other settings
info. Now...at registered user logons areeven new user logons, the speed
is checked by Speed Limit. Remember to make the "lowest modem speed" in
PCBSetup the SAME as in your Speed Limit configs! This is important!!
Speed Limit Config File.
┌────────────────────────────┐
│ Your BBS Name │
│ 00000 │
│ Validation Code │
│ 2400 │
│ E:\PPE\SPEEDLIM\SAMPLE.LST │
│ E:\PPE\SPEEDLIM\SAMPLE.DSP │
│ E:\PPE\SPEEDLIM\SAMPLE.LOG │
└────────────────────────────┘
This config file MUST be called SPEEDLIM.CNF and MUST be located in the
same directory as the SPEEDLIM.PPE program. This is important!
Line 1 = Your BBS Name
Line 2 = 00000 for unregistered (or your registration number)
Line 3 = Validation Code (assigned when registered)
Line 4 = Speed to activate SpeedLim for "name checking" (Same as PCB)
Line 5 = Path/filename of name list you want passed at this speed
Line 6 = Path/filename of display shown those not in list (Before hangup)
Line 7 = Path/filename of "log" (to see just who got bumped off your BBS)
Speed Limit Names List File
┌───────────────────┐
│ 2 │ -> How many names in this list
│ TommyThe Tortoise │ -> Name number 1
│ SammyThe Snail │ -> Name number 2 etc......
└───────────────────┘
Speed Limit Sample Display File (See Config File Above)
┌────────────────────────────────────────────────────────────────────────┐
│I'm very sorry, but I'm afraid your modem speed is too low for this BBS.│
│There are only a handful of callers here at this speed and I do not have│
│enough room for more 2400 baud callers. If you upgrade to a higher speed│
│modem we'd love to have you calling here, but until then we can't do it.│
└────────────────────────────────────────────────────────────────────────┘
┌────────────────────────────────────────────────────────────────────┐Page
│ UserNews PCBoard 15.1 PPE User-Entered News File <Shareware> │ 15
└────────────────────────────────────────────────────────────────────┘
UserNews does more than most user-entered news utilities. Aside from
A)dding to or V)iewing the list, it gives you the ability to S)earch
the list by Date OR Text entries as well!
The installation of UserNews is very. Just install as a command in the
PCBoard CMD.LST file and you're all set. There's a little bit you will
to do with the config file (explained below). For more info on the PCB
CMD.LST file, please see your PCBoard 15.1 docs. The config file MUST
be located in the same directory as USERNEWS.PPE and it MUST be called
USERNEWS.CNF. An explanation of the config file follows:
Config File Details
┌────────────────┐
│ Intelec Online │ -> Who registered to (a BBS name or SysOp name)
│ 00000 │ -> Registration number (00000 if unregistered)
│ ##### │ -> Validation code (assigned upon registration)
│ Path/FileName │ -> The Path/FileName to the bulletin/news file.
└────────────────┘
┌────────────────────────────────────────────────────────────────────┐
│ Time-Adj PCBoard 15.1 PPE Time-Adjuster <Shareware> │
└────────────────────────────────────────────────────────────────────┘
Installation of Time-Adj is extremely simple. Time-Adj is to be placed
in the "security specific logon file" for any user you want to adjust
to their "full time allotment". Any caller that you permit Time-Adj to
adjust their time, if they are allotted 30 mins per day then Time-Adj
will adjust them to 30 minutes each time they call regardless of any
time they may have used earlier that day. PCBoard allows an either/or
setup when it comes to this feature. Now, you can make this a security
specific feature of your board. For information on "security specific
logon display files, consult your PCB manual for details. MY security
specific logon file for level 85 callers (called 85.) looks like this:
!E:\PPE\TIME-ADJ.PPE
Please note that the ! in the above paths needs to be in column one!
This is all that is needed to be done to call Time-Adj whenever users
call into your system. That's the installation, now to configure it...
Config File Details
┌────────────────┐
│ Intelec Online │ -> Who registered to (a BBS name or SysOp name)
│ 00000 │ -> Registration number (00000 if unregistered)
│ ##### │ -> Validation code (assigned upon registration)
└────────────────┘
The configuration file must be located in the same directory as the
TIME-ADJ.PPE and must be called TIME-ADJ.CNF.
┌────────────────────────────────────────────────────────────────────┐Page
│ Pro-Menu PCBoard 15.1 PPE Ultimate Main Menu! <Shareware> │ 16
└────────────────────────────────────────────────────────────────────┘
Pro-Menu is one of the most unique PCB "main menus"! It knows for each
user what commands are available and which commands aren't and it lets
the user know which are which. "Security specific menus" are no longer
necessary. This is a sample of what the menu looks like:
┌───────────────────────────────────────────────────────────────────────────┐
│ 01-12-94 Pro-Menu v3.1 12:08 PM │
└───────────────────────────────────────────────────────────────────────────┘
■ Means the Command is unavailable at your current security level
┌───────────────────────┐ ┌───────────────────────┐ ┌───────────────────────┐
│■ J Join a Conference │ │ D Download a File │ │ I Initial Logon Scrn │
│ A Abandon Conference │ │ DB Download In Batch │ │ M Mode Graphics │
│ C Comment To SysOp │ │ U Upload a File │ │ O Operator Page │
│■ E Enter a Message │ │ UB Upload In Batch │ │ V View Your Settings │
│■ K Kill a Message │ │ F File Directories │ │ W Write Settings │
│ R Read Messages │ │ L Locate a Filespec │ │ X eXpert Mode Toggle │
│ Y Your Messages │ │ N New Files Scan │ │ OPEN a DOOR │
│ Q Quick Msg Search │ │ T Transfer Protocol │ │■ USER Listing │
│ B Bulletin Menu │ │ Z Zippy Files Scan │ │ WHO Else Is Online │
│ P Page Screen Length │ │■ S Script Question'r │ │ CHAT With a User │
│ G Goodbye / Logoff │ │ H Help With Cmds │ │■ TEST File Integrity │
└───────────────────────┘ └───────────────────────┘ └───────────────────────┘
While there are no annoying "unregistered" displays in this menu, reg-
istration replaces the "Pro-Menu v3.1" in the header with the name of
your BBS, lets you add up to three additional commands to the menu for
PPE's etc... as well as allowing security specific "footers" (like the
1 shown below) to give specific security level users more information!
┌───────────────────────────────────────────────────────────────────────────┐
│ You are at a new caller security level. You may use the VERIFY command to │
│ be upgraded. But ALL callers here must be validated for complete access. │
└───────────────────────────────────────────────────────────────────────────┘
Installation of Pro-Menu is EASY! Copy your current "BRDM menu files"
to a safe place and remove all but the "main menu" (the specific file
as defined in PCBSetup. If this is BRDM then that's the only file that
should be there (except when using RIP, this isn't RIP compatible). In
the BRDM file there should be only 1 line, the line that calls the PPE
and it should look like this: !D:\PPE\PPP\PRO-MENU.PPE But of course
the string must start in column one.... Now the config file:
Intelec Online Your BBS Name
1001 Reg Number (when registered, 00000 if unreg'd)
79228 Validation Code " " "
D:\PPE\PPP\MENU Footer File (security specific files supported)
10 1st additional command security level
INTELEC 1st additional command
Apply To Net 1st additional command description
The registered version will let you add (3) additional commands to the
menu display. Use this for PPE program commands, etc. Repeat lines 5-7
for up to two more commands (lines 8-10 and 11-13). The security level
should match the sec level as defined in CMD.LST for proper displaying
and also... the command and description cannot be longer than 19 chars
total. If longer than 19 characters between the "2" fields the display
will be very mucked up. Mine: "INTELEC" & "Apply To Net" are 19 chars.
┌────────────────────────────────────────────────────────────────────┐Page
│ PPE-Menu PCBoard 15.1 PPE PPE Menu Displayer <Freeware> │ 17
└────────────────────────────────────────────────────────────────────┘
PPE-Menu is used to display all your PPE commands. It is pretty basic
right now as all it does it display a file with the commands you place
into it. But as it is simple it is one of the easiest ways to display
a text file to your users for a particular command.
Installation of PPE-Menu is really very simple. PPE-Menu should be
installed in your CMD.LST as a replacement for the J command. Go into
PCBSetup CMD.LST section (B: File Locations, B: Configuration Files)
Now go to the CMD.LST section and F2 to edit it. Add a line as shown:
Command Security PPE/MNU File -or- Keystroke Replacement
======= ======== ========================================
UTILITY 20 E:\PPE\PPP\PPE-MENU.PPE UTILITY.DSP
Make the security level whatever you desire, since this only displays
the file menu and does not override your PPE utility security levels.
The file to be displayed must be located in the same directory as the
PPE-MENU.PPE. Next, in the BRDM menu you need to add the command as
defined in the CMD.LST. Mine is called UTILITY (shown above), but you
can call this whatever you like. Lastly, follow the PPE command with
the filename that you want this command to display. Use it for other
things as well!
┌────────────────────────────────────────────────────────────────────┐
│ Force-It PCBoard 15.1 PPE The Command Stuffer <Freeware> │
└────────────────────────────────────────────────────────────────────┘
Installation of Force-It is really quite simple. Force-It can be
installed in your "security specific logon screens". You can use this
PPE to force new users into a registration PPE (or Doors but that is
already handled by PCBoard) or any other purpose you might want. For
example, I give new callers a security level of 10 as defined in my
PCBSetup. My sec specific logon screen has one line in it as follows:
!D:\PPE\PPP\FORCE-IT.PPE VERIFY
The ! goes into column one (but you should know this at this stage)
VERIFY is the command which activates my registration routines. But,
if VERIFY was an ascii file in the same directory as the FORCE-IT.PPE
then it would take the contents of that file and stuff them into the
keyboard instead of issuing the filename as an actual command. I have
done this to leave as much flexibility in the PPE as I possibly can.
┌────────────────────────────────────────────────────────────────────┐Page
│ Intelec PPE PCBoard 15.1 PPE Intelec Network PPE <Freeware> │ 18
└────────────────────────────────────────────────────────────────────┘
What is Intelec PPE? - It's a complete online "database" utilizing the
IN_yymm.ZIP distribution file from the Intelec Network (only the very
best BBS QWK network ever). It searches or displays the node-listing,
scans the conference listing by conference type, text etc. It displays
our other files as well, such as the network rules, the mistakes file,
conference changes and more. It can scan for hubs by state, area code,
software, modem type, etc. Or it can scan the entire nodelist for the
very same criteria. Also added is the ability to flag or download the
current IN_yymm.ZIP distribution file. And Intelec PPE KNOWS which is
the "current file" based on the current date. Each month, Intelec PPE
updates itself to display the correct file name for flag or download.
And as always, the Intelec PPE serves as an "application generator"!
SysOps running PCB ver 15.1 can use INTELEC.PPE installed in CMD.LST.
SysOps running PCB ver 15.0 should call the Intelec Host BBS for a PPE
that will work on your BBS. See my directory #1 for it. This release
breaks the old INTAPP.PPE into *2* separate PPE's. The main one, as I
mentioned above is called INTELEC.PPE. The second is the "application"
portion of this PPE and is called INTELAPP.PPE. If you enable the app-
lication feature of Intelec PPE (see config file) then all you need to
do is place this PPE in the "same directory" as the above INTELEC.PPE.
Also, this new version (v3.0) won't work with distribution files prior
to 01/01/94 so look for our file called "IN_9401.ZIP" for this to work
And ONLY install the INTELEC.PPE in CMD.LST, and NOT the INTELAPP.PPE!
INTELEC.PPE calls INTELAPP.PPE automatically if you have this enabled.
Command Security PPE/MNU File -or- Keystroke Replacement
======= ======== ========================================
INTELEC ?? F:\IN\INTELEC.PPE
If you're an international member using the DD-MM-YY date format, then
place the letter I on commandline in CMD.LST like: F:\IN\INTELEC.PPE I
The Intelec PPE Config file: INTELEC.CNF
Intelec Online <- (Your BBS's Name)
CLIFF WATKINS <- (Your (SysOp) Name but use all CAPS here!)
38 <- (Regionals # on your BBS, 0 if not a hub)
Y <- Enables application feature (N to disable)
D:\PPE\IN\APPLFORM.IN <- \
D:\PPE\IN\NETRULES.IN <- \
D:\PPE\IN\CONFLIST.IN <- \
D:\PPE\IN\NODELIST.IN <- > - - IN_yymm.ZIP distribution file.
D:\PPE\IN\ABOUT_IN.IN <- /
D:\PPE\IN\CHANGES!.IN <- /
D:\PPE\IN\MISTAKES.IN <- /
D:\PPE\IN\INTELEC.LST <- This is the master app list file.
D:\PPE\IN\INTELEC.ANS <- This is the temporay answer file.
Intelec PPE posts a PRIVATE message to the SysOp on their Main Board.
Intelec PPE posts a PUBLIC message in the Intelec Regional conference.
We strongly urge you to place the name INTAPP into your PCB TCAN list.
If you are a Hub, number of Regionals conf on line 3 and Y on line 4.
If you are a Node, place a 0 on line 3 and N on line 4 of config file.
┌────────────────────────────────────────────────────────────────────┐Page
│ What's New In the PCBoard PPE PowerPack This Release? │ 19
└────────────────────────────────────────────────────────────────────┘
What's new in ConfJoin:
Changed ConfJoin so that it will do a search right from the commandline.
It did already but not "correctly". If a user type at the main prompt:
J S ADMIN it would bring them to the "what text to search for prompt".
In other words ConfJoin was losing the 2nd parameter, or as above it lost
the ADMIN. Now it will not. J S <text string> will now go right into the
actual search. Also, it is now compiled with the 2.0 compiler so I re-
commend anyone still using this with PCBoard 15.0 to check out 15.1...
What's new in SubscriP:
Added to config file a line for "maximum sec level" so you can prevent
those *over* a particular sec level from using it and possibly being
"downgraded". Also added another line to config file to display file
to caller to explain why they're too high to make a purchase so they
are not left in the dark when they try to help support your board.
Also, this and all future PPP PPE's will be compiled with the v2.0
compiler, recommended for PCBoard v15.1 SysOps only. If you're still
using PCBoard v15.0, check out v15.1, it's really running very good!
What's new in Intelec PPE:
New to this release is the INTELEC.CNF file (see prev. page). Intelec
hubs (Super Reg's, Regionals or Hubs) can utilize the application gen-
erating part of this PPE. Nodes can still utilize every other part of
the util though since only hubs need the application part of this PPE.
REMOVE the comments and use YOUR own paths in place of mine. It's also
to be located in the same place as the INTELEC.PPE. I did this so that
our distribution files do not need to be in the same place as the PPE!
All the PPE's here have been updated to be able to accept a global reg
number! They have all been recompiled with the v2.0 PPLC compiler for
use with PCBoard version 15.1!
Coming Soon to the PCBoard PPE PowerPack:
I want to reveal what I'm working on now <g> but I'm going to hold off
for a little while longer. But I have seen plenty of programs written
lately that I KNOW I can do better with, and I will. And I won't do it
under a "release of the day" method but I'll make all fixes available
as soon as they're made. But I won't flood Salt Air with them <ahem>.
Those who order the entire PCBoard PPE PowerPack not only receive free
FUTURE upgrades for every PPE in the PowerPack, but will automatically
be registered for EVERY PPE added to the PPE PowerPack in the FUTURE!
To ensure this benefit, those SysOps who order the entire PPP will get
one registration number good for ALL current & future PowerPack PPE's!
If you ordered my PPE's before and since the entire PPP package is now
offered complete at 20% off the total price, I will take what you paid
and subtract it from the total current price and give you 20% off that
and you too can take advantage of this deal! Want more? If you are an
Intelec SysOp you'll get 30% off on top of that! The PPP for ½ price?
It's true but the offer is for a limited time and can end at any time!
┌────────────────────────────────────────────────────────────────────┐Page
│ Registration and Support │ 20
└────────────────────────────────────────────────────────────────────┘
You have 30 days to evaluate these PPE's. Then you must register them
or stop using them. Also, you use this PCBoard PPE PowerPack at your
own risk. I will not be responsible for lost data or any damage that
the use/misuse of these PPE's may cause. They have all been thoroughly
tested on my system and work flawlessly here but I'm just covering my
assets. If you have any ideas, suggestions that can improve on any of
these PPE's, let me know in the Intelec Network's PPL conference. I am
also found on Salt Air BBS in the PPLC or PPE Conferences for support!
Oh yeah, you can also reach me on my BBS at the numbers shown below.
To Register any or all of these fine PPE utilities, use the reg form
shown below (clip). Registration entitles you to free future updates!
Registration grants you a license to use these PPE's on the (one) BBS
that it is being registered to and licenses may not be transferred.
Please check off the PPE's you are registering
┌─────────────────┐ ┌─────────────────┐
│ SubscriP $15 │ [ ] │ ConfJoin $10 │ [ ]
├─────────────────┤ ├─────────────────┤
│ Pro-Vote $15 │ [ ] │ HowHeard $ 5 │ [ ]
├─────────────────┤ ├─────────────────┤
│ BBSListr $15 │ [ ] │ Time-Adj $ 5 │ [ ]
├─────────────────┤ ├─────────────────┤
│ UserNews $10 │ [ ] │ WelcoMat $ 5 │ [ ]
├─────────────────┤ ├─────────────────┤
│ TimeZone $15 │ [ ] │ SpeedLim $ 5 │ [ ]
├─────────────────┤ ├─────────────────┤
│ MsgQuest $10 │ [ ] │ BF-Ratio $ 5 │ [ ]
├─────────────────┤ ├─────────────────┤
│ Pro-Menu $10 │ [ ] │ To Be Announced │
└─────────────────┘ └─────────────────┘
╔═════════════════════╗ ┌─────────────────┐
║ * Freeware! * ║ │ Total │ ____
║ Intelec PPE ║ └─────────────────┘
║ Force-It PPE-Menu ║ Order the complete PPP package for 20% off ($92)
╚═════════════════════╝ and be registered for all our future PPE's too!!
See previous page for more details on this offer
┌────────────────────────────────────────────────────────────────────┐
│ Your BBS Name: _________________ Password on my BBS: ________ │
│ SysOp's Name: _________________ Your D.O.B.: __-__-__ │
│ Your BBS Phone: ___-___-____ Voice Phone: ___-___-____ │
│ Street Addr: _________________ State: __ │
│ Your City: ____________ Country: ___ │
└────────────────────────────────────────────────────────────────────┘
To register the above programs send checks or money orders payable to
Cliff Watkins at the address shown below. If you are outside the US
please only use Postal Money Orders in US $. Non-U.S. personal checks
can't be accepted. Please don't send cash! Allow time for Snail Mail.
Then you can call my board (Intelec) for your registration number(s).
(516) 868-0662 (D/S 16.8) Public 9am - 10pm (EST) private other times
(516) 868-1741 (v.32 bis) Public 24 hours a day. (2400 not supported)
Cliff Watkins PO Box 212 Baldwin, NY 11510-0212