| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | FQQ.doc 1/2 |
Telegard Bulletin Board Software, v3.10
Telegard Frequently Asked Questions
Last Updated:
Monday, 04 Janurary, 1999 - Telegard 3.09.g2
1.0 General Telegard Information
1.01 Where can I find support?
1.02 Does Telegard have a web site?
1.03 Where can I find Telegard related files?
1.04 What language is Telegard written in?
1.05 What operating systems does Telegard work with?
1.06 What are the native Telegard versions for platforms?
1.07 History of Telegard
1.08 Is Telegard Year 2000 Compliant?
1.09 Has Telegard changed that much?
2.0 Reference files and documentation
2.01 Where can I find Telegard documentation?
2.02 Are there other FAQs out there?
2.03 What are each of the reference files used for?
2.04 Documentation while online
3.0 Installation & third-party utilities
3.01 What is a fossil driver? Why is it required?
3.02 Common Fossil drivers
3.03 Common fossil driver settings
3.04 I have a fossil driver, but Telegard won't answer...?
3.05 Using a frontend mailer, all callers appear to be
communicating with Telegard at 2400 bps... why?
3.06 Sample Operating System setups
3.07 I want to create Telegard third-party utilities. How?
3.08 Why won't Telegard start?!
4.0 Telegard Maintenance
4.01 What maintenance is required by Telegard?
4.02 What is the INDEX utility included with Telegard?
4.03 What is the USERS utility included with Telegard?
4.04 How to I delete Users who have been marked for deletion?
4.05 What are the FA2FB/FB2FA utilities included with Telegard?
4.06 How can I delete users automatically?
5.0 Language Support
5.01 How does the language system in Telegard work?
5.02 How do I display files from a language line?
5.03 How do I run scripts from a language line?
5.04 How do I use the ~&# MCI codes in other places?
5.05 How do I disable script logging (my logs keep filling
up with my pause scripts, etc.)?
5.06 Are you sure it's okay to change the language file?
5.07 What is this new line 0344 in the g2-sp3 language file?
6.0 Message Areas
6.01 How do I remove deleted messages from Telegard?
6.02 What external message packers are available?
6.03 How do I allow user file attaches?
6.04 How do I edit messages once they are posted?
6.05 How do I get a full screen editor in Telegard?
6.06 Why does Telegard not have an internal FSE?
6.07 How do I get my mail batch file to recognize that
messages were posted during the last call? What
errorlevels are used?
6.08 How do I get the mail waiting (MW) command to update
lastread pointers when the scanning is done?
6.09 How do I get nodelist lookups to work? What nodelist
formats does Telegard use?
6.10 What are the limits to the message system?
7.0 File Areas
7.01 How do I import new protocols?
7.02 My LHA protocol is messing up, why?
7.03 My RAR protocol is messing up, why?
7.04 My DSZ/GSZ protocols seems to not work, why?
7.05 Why is BIMODEM not working well with Telegard?
7.06 General protocol troubleshooting
7.07 Can Telegard handle long filenames like in Win95?
8.0 Doors
8.01 How can I show real names in my doors?
8.02 How can I not log door use?
8.03 How can I limit door time use?
8.04 Why are there two door.sys formats in Telegard?
8.05 Why is there a doorfile.scr script?
8.06 How do I handle doors in multi-node setups?
9.0 Scripts
9.01 How do I parse IF/NOT statements for empty strings?
9.02 My scripts do not seem to run, why?
9.03 What is the logon.scr and logoff.scr for?
9.04 How do I use the scripts?
9.05 Why do some of my menu commands not work in scripts?
9.06 What is this {at}*{at} stuff in scripts?
10.0 Miscellaneous
10.01 What does ACS/MCI stand for?
10.02 When and where are the IRC chat sessions?
10.03 How can I get my files hatched out to TG Sysops?
10.04 Is the Telegard source code out for the public?
10.05 Why does my ansi files not show the Y/N/C prompt?
10.06 What is PWE Encryption
10.07 Why do I get a "You can't change that at your
SL" error
when I edit my user account? Is it a safety feature?
10.08 What is this THD I hear about?
10.09 How do I add netmail into Telegard for squish?
10.10 How do I add netmail into Telegard for jam?
10.11 How do I make my automessage pause?
10.12 How do I make my bulletins display .ans files?
10.13 How do I stop MCI codes from expanding in menus?
10.14 I've deleted a user and packed the user index/files but
now Telegard keeps getting an error when loading. Why?
10.15 How do I make new menus for Telegard?
10.16 How can I display menus to certain security levels?
10.17 Should I use the -O Telegard parameter?
10.18 Will Telegard have a shuttle logon system?
10.19 How can I display files on a certain date?
10.20 Can I hide my email base from general area list?
10.21 How can I reset my logging graphs?
10.22 Does Telegard support Caller-ID?
10.23 Are there any Telegard Security holes?
10.24 My new CD-ROM won't work in Telegard. Why?
10.25 What is the Telegard file_id.diz description max length?
10.26 I'm getting Run Time Error #105 often, why?
10.27 How do I set it up so only users of a certain ACS can
access the system at certain times?
10.28 I want to make changes to the System Configuration, how?
10.29 TG shows today's call log wrong, yet it's correct, why?
10.30 Can I get on the TG BBS list that comes with TG?
10.31 Are there any good native OS/2 protocols for TG/2?
10.32 My TG/2 protocols are unsuccessful regardless of the
transfer, why?
10.33 How do I setup Netmodem with Telegard?
10.34 What software is good for TG to Telnet in WinXX platform?
10.35 I have a Lan setup but keep getting Mode 64 errors, why?
10.36 How can I display files by a certain day of the week?
11.0 Contributing Authors
11.01 Frequently Asked Question maintainers
11.02 Frequently Asked Question contributers
CONTENTS
1.0 General Telegard Information
1.01 Where can I find support?
Our official support conference is carried by Fidonet, with
the tagname TG_SUPPORT. This echomail conference is visited
by the author, the alphas, the betas, and regular users as
well--all in one location to help out with your problems.
Many other networks carry Telegard and BBS related conferences
where Telegard support can be received, such as SysOps TechNet,
FishNet, AdventureNet and more than a dozen others.
Limited Telegard support is also available on the Internet,
at both our official WWW sites, and those of dedicated users
who have created their own sites. See section 1.02 for
a starting point.
In addition, several of the alpha and beta sites hold online
Q&A sessions on the Internet Relay Chat. See section 10.02
for further details.
When you report problems, it's good to give as much data (TG
settings, etc.) as possible. You can do this by capturing
TG screens to a file. This can be done by using ALT-P
anywhere you wish to capture some info.
1.02 Does Telegard have a WWW site?
The official WWW site for Telegard can be found by visiting
http://www.telegard.net. The authors homepage is available
by visiting http://www.interlog.com/~strike. There are
numerous other Telegard sites on the world wide web as well.
The official FTP site for Telegard can be found by visiting
ftp://telegard.net/pub/tg. A text listing of files is
available at the site, and an HTML version is available by
visiting http://www.interlog.com/~strike/tgfiles.html.
1.03 Where can I find Telegard related files?
The most comprehensive location of Telegard releases and
utilities is our official Telegard FTP site (see section
1.02). It carries all the files given to the Telegard team
for distribution.
In addition, Fidonet carries a File Distribution Network and
Telegard has an FDN area under the tagname TG_SUP. New files
for distribution (both from the Telegard team and from other
third party authors) will be hatched (distributed) in this
file area.
1.04 What language is Telegard written in?
Telegard is written primarily in Borland Pascal, with the
core routines in Assembly and a few functions/utilities
written in C++.
The Telegard/2 port is written in Virtual Pascal/2 instead of
Borland Pascal.
1.05 What operating systems does Telegard work with?
DOS (Microsoft, IBM PC and Caldera OpenDos/DrDos), Microsoft
Windows 95, various flavors of Linux under DosEmu, and IBMs
OS/2 Warp are the platforms which Telegard has been proven to
work well with at this time.
1.06 What are the native Telegard versions for platforms?
There are currently only two native versions of Telegard, and
they are for DOS and OS/2. Other platforms might be
considered if the necessary compilers can be obtained for
those platforms and Telegard works well with that platform.
1.07 History of Telegard
None of the history contained herein should be considered
gospel. There are many rumors and half-truths swirling
around the history of Telegard, and only the recent history
has been recorded.
Wayne Bell is considered the "Godfather" of Telegard, which
was based off early publically distributed versions of
Bell's WWIV BBS software in pascal (this part of history is
still in contention by some...).
Carl Mueller obtained that code and improved on it, creating
the first versions of Telegard.
Eric Oman took over the code, and improved Carl's work. He
was inexperienced however and had to call upon his then
friend Martin Pollard. Todd Bolitho would later join the
team. Several versions were released during this time,
culminating in the 2.5 standard release. Shortly afterward,
Todd left the team due to "creative differences" with
Martin. Eric left due to it being "not fun anymore".
Martin, left alone, continued development work on Telegard
until he was slapped with a legal lawsuit by Eric which
temporarily stopped development. At that point, the latest
standard release was still 2.5, but the beta versions 2.5i,
2.5j and 2.5q were floating around for use.
Telegard did not die, however, as version 2.7 would come out
in 1991. This last version would be the mainstay of Telegard
systems for years to come, while Telegard development would
continue behind closed doors until Martins departure in 1993.
In September 1993 the Telegard project was handed over to Tim
Strike, a utility author and Telegard beta site. In November
1993, the code changeover was complete, and by December 1993
the first beta version was available to the beta team
(2.80.b1). The first 3 betas would mark the restoration of
features that 2.80.b1 had gutted, and by 2.80.b4 the message,
file and door routines had been rewritten. 2.80.b5 marked
the introduction of Jam and Squish, and 2.80.b6 was the debut
of the new file system. After almost a year and a half of
development, the first public version of the new Telegard
would be released as a gamma version, 2.99.g1 in July 1995.
Telegard 3.0 would be released a year later, quickly followed
by the patch versions 3.01 and 3.02. A year later, in
November 1997, the first gamma version for the 3.10 series
would be released, 3.09.g1. Around July 5th, 1998 3.09
gamma 2 was released which was the first release for the full
native OS/2 (TG/2) version. Shortly after a supplemental
pack #3 was released which fixed some minor bugs.
1.08 Is Telegard Year 2000 Compliant?
Telegard version 3.09.g3 and below are not. The new versions
starting with 3.09.g1 are Year 2000 aware, and by 3.09.g3
should be completely Year 2000 compliant.
1.09 Has Telegard changed that much?
Yes, most definitely. Since the days of Telegard 2.7 the
software has been completely re-done from ground up. The
file system has drastically changed in format and speed. The
message system no longer uses a proprietary mail system
(using Telemail from 2.5 and 2.7 days), and now supports the
standard formats of Squish and Jam directly. Telegard also
now boasts a powerful script system, an extended menu system,
new multinode features, and a language system to provide
multilingual support.
2.0 Reference files and documentation
2.01 Where can I find Telegard documentation?
You will find all the documentation for Telegard in the
/docs/ folder off your main Telegard directory. There will
be one main documentation file and several supporting
reference files for quick use.
2.02 Are there other FAQs out there?
Yes. In the Fidonet TG_SUPPORT conference there are some
postings of other FAQs, including how to setup TG with a
mailer and a basic security FAQ for sysops. These are posted
often or upon request. They are also compiled into a archive
called TGFAQ##.zip which can be found on the main ftp site.
Other people maintain FAQs in this echo including some for
telnet setups, netmail and the like.
2.03 What are each of the reference files used for?
All the reference files have a .REF extension to them.
* acs.ref is for quick access to what each ACS code is.
* colors.ref is text on the TG color code system.
* command.ref is the valid command line parameters for TG.
* errors.ref are notes on common error codes for TG and their
supporting meaning in an attempt to help you fix problems.
* fa2fb.ref notes on the new TG file utilities and how to use
them effectively.
* funckeys.ref is the list of common function keys in TG.
* language.ref is used in times when you need to recover a
lost/damaged Telegard language file through 10 steps.
* mci.ref is the list of TG MCI codes
* menus.ref are notes on every menu command and key code used
in Telegard menus with explanations of their use.
* script.ref are the commands that are valid to use in the new
Telegard scripting language.
* textfile.ref is a list of common and obscure text files that
every sysop can use to customize their bbs fully.
2.04 Documentation while online
There is no online documentation while using Telegard.
However, most Telegard prompts accept the ? command, which
will bring up a context help menu outlining the operations
available for that prompt.
One very overlooked spot for online help is that of the menu
editor. While editing menus you don't need to know the
command keys by heart or need the documentation--using ? will
bring up a list of available menu groups, and using a group
code followed by ? will give you a list of available menu
commands.
3.0 Installation & third-party utilities
3.01 What is a fossil driver? Why is it required?
A fossil is an extension of a PC's BIOS that is for serial
communications. It is needed by most software and doors
to improve the communications for modems especially the high
baud rate modems (9600+). Telegard requires a fossil driver
to communicate properly with your modem. That fossil driver
must also be configured properly for your computer, *and* for
your operating system.
3.02 Common Fossil drivers
There are several popular fossil drivers out there including
X00, BNU, Winfossil and SIO.
3.03 Common fossil driver settings
Most fossil drivers should be loaded through the config.sys
file. You should consult the fossil documentation for more
extensive help beyond this document's scope. But here are
some common settings:
1) X00
Load it through config.sys like:
DEVICE=c:\X00.sys E 1 B,0,38400 T=1024 R=1024
^ ^ COM1 = Port 0
One port enabled
2) BNU
Load it through Config.sys like:
DEVICE=C:\BNU.SYS /L:1=38400 /F+ /Z0 /R:1024 /T:1024
^ COM2 = Port 1
3) Winfossil
Winfossil should be run in Win95 (it won't work in 16-bit
Windows (Windows 3.1, WFWG 3.11, etc)). If you're using
Windows NT you should get the WinFossilNT version. You
should have WinFossil keep the port open during an MS-DOS
session. The Early version of WinFossil 1.12 was not
stable as release .004. So anything after that should
work. Just remember not all fossils work with ALL CPUs.
Some common settings/info:
(This example from John Rumery)
Port ID: 0001
Port Name: COM2
(Select the port number (0000-0003) for COM1-COM4
respectively for your modem's port number...mine is COM2,
port ID 0001).
Locked Baud Rate: 115200 (Most 28k8 and higher modems)
57600 (most 14k4 modems). (Actual locked rate will depend
upon which UART chipset you have)
Rx Buffer: 8192
Tx Buffer: 8192
(You'll have to play with these settings to see which
ones give your system the best transfer rate. 8192 is
fairly reliable and gives 2650-2750 cps transfer rates on
*MY* system, your actual cps transfer rate may vary).
On/Off selections (Check boxes throughout the setup screen)
(Note: I use check and clear to tell what the selection
box looks like...if there is a check in the item selection
box, I use check and if clear, I use clear.)
Selection Item
Box Description
+++++++++++++++++++++++++
Check Enable Fossil
Check Don't Release Timeslice While Carrier Detected
Clear Release Timeslice When No Port Activity Detected
Check Enable Performance Statistics Monitoring
Check Reflect COM Port State to VCD When Passing Port
Check Automatically Open Port When Use Detected
Check Keep Port Open During MS-DOS Session
4) SIO OS/2 Fossil
Load SIO/VSIO in your CONFIG.SYS instead of COM/VOM
(remember to remark VOM/VCOM entries out):
DEVICE=SIO.SYS (COM1,3F8,IRQ4,-) (COM2,2F8,IRQ3,-)
DEVICE=VSIO.SYS
(other settings are outlined in the SIOUSER.TXT
documentation included with SIO).
Unregistered Sio.sys - SU.exe can't lock port
The ,- to enable DOS, OS2 and SIO file sharing. The - is
required if you want your users to stick around when
entering doors for TG/2 or TG/dos.
In addition to the SIO/VSIO drivers, if you need to run
DOS doors under Telegard/2, or are using Telegard/dos are
your BBS software, then you will need to add the line
DOS_DEVICE=VX00.SYS to your DOS session settings.
Add fixpacks 1-8 as timeslicing had problems for some
bbses
Lastly, There is a command in the OS/2 config.sys
MAXWAIT=3 change the 3 to a 1 to improve uploading and
downloading in TG/2 or TG/dos. (NOTE: The MAXWAIT command
may not need changing, depends on the system.
3.04 I have a fossil driver, but Telegard won't answer...?
If you are experiencing problems, such as the modem not
answering or the communication rate operating at ~300 bps,
then please check over the following items:
(1) Has the fossil driver been correctly setup to use the
correct comport? Fossil drivers use port numbers that
are one less than the comport reference number; i.e. COM1
= Port 0, COM2 = Port 1, etc. Ensure that you have setup
your fossil driver correctly.
(2) If you have a high speed modem, have you locked the fossil
port associated with your modem? If not, then this can
cause the modem to communicate with Telegard incorrectly
(such as at 300 bps). Refer to your fossil documentation
on how to correct this; for X00 for example, you must
specify the comport and rate to lock with, such as:
device=x00.sys e b,0,115200
(3) Have you tried another fossil driver brand? Occasionally
certain fossil drivers just don't work with certain
hardware configurations.
(4) Are you using the latest *official* release, or a beta?
Often the betas have 'features' which really aren't
features, and can cause more problems than good. The
converse is also true though; sometimes the final releases
have similar 'features'.
3.05 Using a frontend mailer, all callers appear to be communicating
with Telegard at 300 or 2400 bps... why?
There is no quick answer however there are three common ways:
1) Fossil problems: The fossil driver is likely configured
incorrectly for the locked baud rate or locked port
setup. Consult 3.02 for further information.
2) Batch file/errorlevels: You might not be giving the
right errorlevel from your front end mailer to Telegard.
Make sure TG is detecting the correct baud rate if not
then its likely the batch file.
3) Modem Init string: Many modem initialization strings
might be giving the incorrect settings. For example
modems might be reporting the DTE connection rate instead
of the proper rate. In which case you should consult
your modem documentation (in many cases this can be
fixed by adding W2 to the modem init string if your modem
supports this command).
3.06 Sample Operating Systems setup
The following are some sections on common settings and
suggestions that work with Telegard. While these settings
or suggestions do not work with every system they are here
to provide a outline for you to start with.
1) Windows 3.1
The following PIF profile is a general profile:
Program Filename : C:\COMMAND.COM
Optional Parameters : /E:1024 /C D:\TG\TELEGARD.EXE -N2 -L
Start-up Directory : D:\TG
Video Memory : High Graphics
Memory Requirements : KBR 468 KBD -1
EMS Memory : KBR 0 KBD 0
XMS Memory : KBR 468 KBD -1
Execution : Background
Close Window on Exit
MultiTasking BP 400 FP 400
Monitor Ports : Emulate Text Mode
Other Options : Allow Fast Paste, PrtSc
(This setup uses all XMS memory)
2) Windows 95
Here are some steps to ensure TG works well under Win95:
1. Get WinFossil. Suggestions for WinFossil:
Enable the fossil for the correct port.
Lock the baud rate at either 57600 or 115200, depending
on how your modem is setup in Windows. I recommend 57600
because at higher rates the possibility of interference
is greater. Set both the TX and RX buffers to 8192 or
higher. Then on to the options checklist. Make sure
these options ARE checked.
1. Don't release timeslice while carrier detected
2. Reflect COM port state to VCD when passing port
3. Automatically open port when use detected.
4. Keep port open during MS-DOS session.
Then make sure these options ARE NOT checked.
1. Release timeslice when no port activity detected.
The other options are yours to configure.
2. Edit the Shortcut you made in windows (Either in the
start menu, or on the desktop). Go to the "MISC" tab.
Turn the "Idle Sensitivity" all the way down (to the
left). Also under the "MISC" tab uncheck the
"Always
Suspend" option in the "Background"
area. Under the
"MEMORY" tab, give the node all the mem it may need,
preferably leave the EMS and XMS options on "Auto".
Also to help prevent incompatibilities, make sure the
"Conventional" memory option is set to
"Auto" and the
"Protected" box is checked. You might want
to set the
"Environment" option to at least 512 bytes or more.
There is another FAQ that gives more detail if needed.
Ask in the official support echo and we can furnish
if the above does not help you.
3) OS/2
Tips for Telegard/Dos under OS/2 (until we get more
Telegard/2 experience).
Important Points on Telegard/Dos under OS/2
1> Make sure you have DOS-OS/2 support installed in your
OS/2.
2> Recommend using SIO fossil.
3> If using SIO, make sure that DEVICE=VX00.SYS is in your
CONFIG.SYS file. TG will NOT run without it.
4> OS/2 will sense that TG is a DOS program and will
automatically drop to DOS if you're using a OS/2 native
mailer (i.e. BinkleyTerm/2, T-Mail, etc.).
5> From your front end mailer, call TG as you normally
would.
6> Use an OS/2 native mailer- makes the system run faster. :)
3.07 I want to create Telegard third-party apps/utilities. How?
Anyone can write third-party support programs or utilities
for Telegard. You do not have to be on the official
development team (like a beta site). All you need is
to obtain the TG development kit. You can find this file
on the Telegard Web site (see 1.02) by the name of
TGDEV###.zip where ### is the version number like 3.09 for
3.09+ TG versions. It contains both C and Pascal structures
for programmers to write their own support programs. If you
would like to distribute your Telegard related application
or utility after it is completed, please see section 10.03.
3.08 Why won't Telegard start?!
There tend to be numerous reasons for this and the common ones
are:
1) No fossil (see 3.01-3.04)
2) Indexes error - re-read the docs you skipped a step.
2) Command line for Telegard itself.
There are two common settings for TG.
Local: [For Sysop login] - Telegard -L -P -N#
Users: [For Users login] - Telegard -B%1 -X%2 -C%3 -Q
-N# is the node number for TG
-B, -X and -C are given info by your front end mailer
if you run one in this fashion.
For details on the command line refer command.ref.
4.0 Telegard Maintenance
4.01 What maintenance is required by Telegard?
Telegard is, for the most part, self-maintaining. The index
files are designed to work without interruption and most of
the data files automatically handle packing and removal of
unused records.
That said, the Telegard index files do require some minor
maintenance to maintain top performance. It is recommended
that you:
(i) Run INDEX SORT ALL on a nightly schedule
(ii) Run INDEX BUILD ALL on a weekly schedule, if not every
couple of days
4.02 What is the INDEX utility included with Telegard?
INDEX.EXE is a utility that maintains and controls the
intricate Telegard indexes and configurations. It is a
program that is vital to the proper operation of Telegard.
You should refer to 4.01 on proper use of this utility.
INDEX.EXE was not designed to be run while a user is online;
this is for several reasons, but the main reason is it
modifies files which the online user will access at some
point (and cached pointers may no longer be accurate after an
external re-indexing). Indexing should *ONLY* be run when a
user is *NOT* online--regardless of whether the system is
single node or multinode.
You can run index /? to see how to use the utility.
It can index the areas (file/msg), files, qwk, shortmsg,
users files separately or through all at once. The operation
on those files are to build (make/remake), renumber or sort
those files. The final option this program does is a LIMITS
function which can resize the number of file and msgs bases
your system can have. Why use this program?
1) For nightly maintenance
2) To rebuild corrupt or damaged files
3) To increase your system number of file/msg bases.
One last common mistake is the INDEX LIMITS use. Most supply
the incorrect command line parameter. If your system needs
to have 500 file and 500 msgs bases yet TG won't allow that
you will need to run INDEX LIMITS. In this case it should
be INDEX LIMITS 500 500 not the common mistake of INDEX LIMITS
#500 #500 which will not work.
4.03 What is the USERS utility included with Telegard?
USERS.EXE is the utility which maintains your user database.
USERS.EXE allows you to pack away deleted users (unlike 2.7,
Telegard 3.0 does not automatically reuse deleted accounts).
USERS.EXE also allows sorting of the userbase -- first it
sorts by security level, and then it sorts by user name
within each security level echelon.
You can use Users /? to view how to use the program. Since
the help screen is self-explanatory no need to give details
here on it.
4.04 How to I delete users who have been marked for deletion?
Unlike previous versions of Telegard, 3.02 and 3.10 do not
automatically purge the users from your user database.
Deleted users are left in your database, and their records
are not overwritten by new users, nor are they removed from
the data files.
Users marked for deletion can be removed from your data file
with the 'pack' option of the USERS.EXE utility. After
packing your user file, you will need to rebuild the user
indexes, using the 'build users' option of INDEX.EXE. The
most common sequence of events in your nightly maintenance
is as follows:
users pack
users sort
index build users
4.05 What are the FA2FB/FB2FA utilities included with Telegard?
These are utilities which give older programs that access
the Telegard 3.02 file system formats, rather than the newer
and faster) 3.10 file system format. This will allow you to
keep some of your legacy file system utilities working with
the newer release of Telegard. Please consult the reference
file FA2FB.REF in your /docs/ folder for more information.
4.06 How can I delete users automatically?
This was briefly touched in 4.03 but there are several ways
you can do this. Here is one method:
For that validation level, set the expiration level to the
number of days you want the user deleted after.
Add the following line to your LOGON.SCR:
MENU OZ=
You could modify that to have more of a ACS feature as well.
The OZ=30 part sets the expiration date to 30 days from the
current date. Therefore, every time a user calls they are
effectively extending the life of their account to 30 days
from that date.
Run USERS PACK EXPIRE on a nightly basis to ensure that
anyone who's account has expired is removed from the system.
--- Fringe BBS
* Origin: The Fringe BBS - Only the best >TG< - 904-733-1721 (1:112/91)SEEN-BY: 633/267 270 5030/786 @PATH: 112/91 123/500 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.