home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
GENUTIL
/
IRCDOR15.ZIP
/
ircdoor.doc
< prev
next >
Wrap
Text File
|
1997-02-07
|
36KB
|
851 lines
IRCDOOR 1.50 Manual
Copyright (c) 1996 by Andrew Eigus
Table of Contents
1. ...Introduction
2. ...Software and Hardware requirements
3. ...License agreement
4. ...Disclaimer
5. ...Installation instructions
6. ...IRC commands supported by IRCDOOR/2
7. ...IRCDOOR/2-specific commands
8. ...Comments
9. ...Registration information
10. ...IRCDOOR/2 distribution information
11. ...Contact information
1. Introduction
What is IRC?
IRC stands for "Internet Relay Chat". It was originally
written by Jarkko Oikarinen (jto@tolsun.oulu.fi) in 1988.
Since starting in Finland, it has been used in over 60
countries around the world. It was designed as a replacement
for the "talk" program but has become much much more than
that. IRC is a multi-user chat system, where people convene
on "channels" (a virtual place, usually with a topic of
conversation) to talk in groups, or privately. IRC is
constantly evolving, so the way things to work one week may
not be the way they work the next.
Good, what is IRCDOOR?
IRCDOOR/2 is an advanced 32-bit OS/2 Internet Relay Chat
client with main purpose of being able to be run from a BBS
(Bulletin Board System) as an external door program, that
would allow BBS users to IRC. Yes, it means that you could
*dramatically* increase your BBS popularity by adding IRC
service for your BBS users. Imagine a user who finds out
that something is much bigger, better and cooler than
a simple chat on BBS! Imagine a user who opens your Internet
service menu and starts a chat session on the Internet!
The following is a brief list of features that are supported
in current version of IRCDOOR/2:
-- natural 32-bit application capable of running simultaneously
at as many lines as you wish to register it for
-- as a BBS door supports TTY/ANSI interface
-- supports DORINFO1/DOORSYS drop-file formats
-- supports most standard IRCII 2.8 commands plus some
additional /CTCP-request commands and some specific
to IRCDOOR-only commands eg: /WHOELSE, /TIMELEFT, etc.
-- easy to setup (most options can be specified via command
line)
-- can be run in local mode too as a normal IRC client program
-- runs from any native OS/2 BBS that supports "hot" (open)
com port handles
-- flexible configuration
-- extensive Maximus BBS support (MEX code provided)
-- custom colors and other settings through config file
-- ability to be run from a DOS BBS under OS/2
-- pidentd (RFC 1413) service support
2. Software and Hardware requirements
Requires IBM PC (80486 is recommended), Internet connection
via ethernet, SLIP/PPP etc., IBM OS/2 version 2.0 or 3.0 and
IBM IAK (Internet Access Kit) with 32-bit TCP/IP libraries
(files: TCP32DLL.DLL and and SO32DLL.DLL). The Ray Gwinn's
SIO FOSSIL driver is also recommended for better perfomance.
SIO is also necessary if you are going to run IRCDOOR from
a DOS based BBS.
3. License agreement
IRCDOOR/2 IS COPYRIGHT AND PROPERTY OF ANDREW EIGUS, AN
INDEPENDENT SOFTWARE DEVELOPER (FREELANCER). NONE OF THE
PORTIONS CONTAINED IN THE IRCDOOR/2 DISTRIBUTION PACKAGE CAN
BE RESELLED, MODIFIED, DISASSEMBLED OR REPRODUCED IN ANY WAY
WITHOUT THE AUTHOR'S PERMISSION. PERMISSION IS GRANTED TO
ANYONE TO DISTRIBUTE THE ENTIRE PACKAGE IN THE NON-MODIFIED
FORM, PROVIDED THAT ALL FILES ARE KEPT IN THE DISTRIBUTION
ARCHIVE.
IRCDOOR/2 IS NEITHER PUBLIC DOMAIN, NOR FREEWARE. IRCDOOR IS
SHAREWARE SOFTWARE. YOU MAY EVALUATE IT FOR A TRIAL PERIOD OF
28 DAYS, AND THEN WHETHER REGISTER, OR DISCONTINUE USING IT.
4. Disclaimer
THIS SOFTWARE PROVIDED "AS-IS", WHICH MEANS THAT THERE IS
ABSOLUTELY NO WARRANTY PROVIDED BY THE AUTHOR. IN NO EVENT
THE AUTHOR WILL BE LIABLE TO YOU FOR ANY DAMAGES ARISING OUT
OF THE USE OF ANY PART OF THIS PROGRAM.
5. Installation instructions
Installation instructions are sub-divided in three sections.
Section 5.1 describes the door installation details for non-
Maximus BBS users, section 5.2 describes door installation
instructions for Maximus BBS, and sysops who are running a
DOS-based BBS under OS/2 should read sesction 5.3.
5.1 Installation for non-Maximus OS/2 BBS systems
a) Create an empty subdirectory in your BBS [doors]
directory called IRCDOOR. Let's say i am using Lora BBS,
and a path to my door games is C:\LORA\DOORS\, so i
create a directory C:\LORA\DOORS\IRCDOOR.
b) Unzip the distribution IRCDOOR archive to that directory,
so it would contain AT LEAST the following files:
IRCDOOR.EXE
IRCDOOR.CFG
IRCDOOR.HLP
c) Next, set up your BBS software for this door to be run; use
either DOOR.SYS (recommended) or DORINFO?.DEF format drop-
file. It should be created prior to running IRCDOOR by your
BBS software (see your BBS manual for details). Your BBS
software might be able to pass some information to IRCDOOR
via command-line: IRC server name, port number, etc. Even
some parameters in the drop-file can be overriden through
a command-line. See command-line switches in the Comments
section for more information about IRCDOOR/2 command line
parameters.
Your BBS software MUST be able to pass an open com port
"handle" parameter to IRCDOOR. IRCDOOR will NOT work in
the remote mode without port handle and BBS drop file path
specified as command-line arguments. (see -p and -d options
in the command line parameters paragraph). I recommend you
to create an OS/2 command file, for example IRCDOOR.CMD,
that will run the door. Here is sample command file:
@echo off
cd \lora\doors\ircdoor
if "%1"=="" goto local
if "%1"=="0" goto local
:remote
rem *** change the path below to specify a path to YOUR
rem *** drop file. In multinode environments, this usually
rem *** depends on a node number.
ircdoor -p%1 -dc:\lora\node%2\door.sys -k%2 -sirc.funet.fi -$6666
goto quit
:local
ircdoor -l -uSysOp -nSysOp -r"My Name" -sirc.funet.fi $6666
goto quit
:quit
cd \lora
This small command file above will do the job. It requires
two arguments: 1 - "hot" com port handle and 2 - BBS node
number. The node number will be used to specify a target
directory (path) for/to a drop file. IRCDOOR will automatically
determine drop file type by it's name. See command line
switches for more information.
d) Edit your STARTUP.CMD file in your system root directory
and add there the following line:
erase c:\ircdoor_home_directory\nodeinfo.* >nul
This command will erase old node information files from the
IRCDOOR home directory. Ircdoor_home_directory must be
replaced with the directory name where IRCDOOR/2 files are
located.
IRCDOOR/2 creates and uses nodeinfo.* files in it's home
directory and it automatically deletes them when a user
exits the door. But if you encounter a system crash during
the time when IRCDOOR is running, you should manually
remove nodeinfo.* files from it's home directory to prevent
IRCDOOR from thinking that it is running at the moment.
That's why the best way to avoid this is to insert that
mentioned erase command above to your STARTUP.CMD file so
whenever your system reboots, old IRCDOOR node information
files will be deleted.
There are many different types of BBS software for OS/2, and
most support passing various parameters via command line, and
most are able to write standard BBS drop-files (DOOR.SYS or
DORINFO?.DEF). If this is not your case, and you are
experiencing problems on how to setup a door, please contact
me at the address given at the bottom of this document. If
you own a DOS BBS, please see paragraph 5.3, which describes
how to setup IRCDOOR for a DOS BBS.
5.2 Installation for Maximus/2 3.x system
* Assume that your Maximus directory is C:\MAX, and your doors
are in C:\MAX\DOORS. Assume that your MEX directory is
C:\MAX\M, and your MECCA directory is C:\MAX\MISC. If this
is not your case, simply replace the paths where they
appear in future.
a) Create IRCDOOR directory under your DOORS directory:
C:\MAX\DOORS\IRCDOOR.
b) Unzip (copy) IRCDOOR distribution files to that directory.
c) Copy IRC.CMD file into your Maximus directory and check if
all the paths are specified correctly in there.
d) Copy IRC.MEX (and IRC.VM) to C:\MAX\M directory (or where
your MEX files are located)
e) Edit MENUS.CTL and add there (where you want) something
like that:
Mex M\IRC Normal "IRC"
so when a user selects 'I' from your Internet menu, IRC.VM
mex code will be run. IRC.VM mex code will at first create
a DOOR.SYS file in your node-dependant directory (for
single-node BBSs edit IRC.MEX so it would call DOORSYS.BBS
instead of DOORSYS2.BBS), and then will prompt a user to
choose the IRC server to use. You can manually change the
IRC.MEX file to present other (closer) IRC servers to your
BBS users.
f) Copy DOORSYS2.MEC (and DOORSYS2.BBS) to C:\MAX\MISC
directory or wherelse your MECCA files are located. Edit
DOORSYS2.MEC if necessary to specify YOUR BBS node
directories. By default, DOORSYS2 MECCA script file will
write DOOR.SYS drop-file in C:\MAX\NODEn directory, where
'n' is an active node number. Change it if your node
directories are in different locations, or you are running
a single node BBS. If you have a single node BBS, simply
edit IRC.MEX to call DOORSYS.BBS instead of DOORSYS2.BBS,
and then edit IRC.CMD so it will pass valid path to
DOOR.SYS file.
g) Compile IRC.MEX with MEX and DOORSYS2.MEC with MECCA (if
changes were made), compile MENUS.CTL with SILT. Last time
check whether everything is ok and all paths are correctly
specified in the files mentioned above.
h) Edit your STARTUP.CMD file in your system root directory
and add there the following line:
erase c:\ircdoor_home_directory\nodeinfo.* >nul
This command will erase old node information files from the
IRCDOOR home directory. Ircdoor_home_directory must be
replaced with the directory name where IRCDOOR/2 files are
located.
IRCDOOR/2 creates and uses nodeinfo.* files in it's home
directory and it automatically deletes them when a user
exits the door. But if you encounter a system crash during
the time when IRCDOOR is running, you should manually
remove nodeinfo.* files from it's home directory to prevent
IRCDOOR from thinking that it is running at the moment.
That's why the best way to avoid this is to insert that
mentioned erase command above to your STARTUP.CMD file so
whenever your system reboots, old IRCDOOR node information
files will be deleted.
Then run Maximus and check it out. If you have problems with
configuring IRCDOOR/2 for your system, first refer to the
chapter 5.1 (Installation for non-Maximus BBS systems), and
if you still have no luck, feel free to write to the author.
See the information at the bottom of this document to find
out how to reach me by electronic mail.
5.3 Installation for a DOS-based BBS
It is possible to run IRCDOOR/2 from a DOS BBS like Maximus (DOS),
Renegade, Remote Access, etc. The following describes what you'll
need to do to setup the door for your DOS BBS:
a) Create an empty subdirectory in your BBS [doors]
directory called IRCDOOR. Let's say i am using Lora BBS,
and a path to my door games is C:\LORA\DOORS\, so i
create a directory C:\LORA\DOORS\IRCDOOR.
b) Unzip the distribution IRCDOOR archive to that directory,
so it would contain AT LEAST three files:
IRCDOOR.EXE
IRCDOOR.CFG
IRCDOOR.HLP
c) Next, set up your BBS software for this door to be run; use
either DOOR.SYS (recommended) or DORINFO?.DEF format drop-
file. It should be created prior to running IRCDOOR by your
BBS software (see your BBS manual for details). Your BBS
software might be able to pass some information to IRCDOOR
via command-line: IRC server name, COM port number (instead
of a hot handle), etc. Even some parameters in the drop-file
can be overriden through a command-line. See command-line
switches in the Comments section for more information about
IRCDOOR/2 command line parameters.
Now, some important things. IRCDOOR program expects open
com port handle parameter to be specified on command line,
however, when running from within a DOS BBS, handles are
not available, thus you will need to pass a COMx port device
parameter at command line instead of a com port handle;
where 'x' is a number of a COM port device to open.
Below is a sample DOS batch file to do the job. It executes
IRCDOOR in either remote or local mode, and passes a COM port
device name including port number, so that IRCDOOR could open
COM port device if running in remote mode. IRCDOOR is programmed
as it can be run from within a DOS session, so here it is called
from a DOS batch file:
@echo off
cd \lora\doors\ircdoor
if "%1"=="" goto local
if "%1"=="0" goto local
:remote
rem *** the following command causes IRCDOOR not to use ready
rem *** port handle, but to open the COM port device.
rem *** Change the path below to specify a path to YOUR
rem *** drop file. In multinode environments, this usually
rem *** depends on a node number.
ircdoor -pCOM%1 -dc:\lora\node%2\door.sys -k%2 -sirc.nada.kth.se
goto quit
:local
ircdoor -l -uSysOp -nSysOp -r"My Name" -sirc.funet.fi $6666
goto quit
:quit
if exist nodeinfo.%2 erase nodeinfo.%2
rem *** back to BBS directory
cd \lora
This small DOS batch file above will do it. It requires
two arguments: 1 - com port number and 2 - BBS node number.
COM port number is used to open a serial port device, and
the BBS node number is required to specify a full
path (including filename) to your BBS drop file. IRCDOOR will
automatically determine drop file type by it's name, therefore
the name of a drop file is required too. See command line
switches for more information about parameters.
d) Edit your STARTUP.CMD file in your system root directory
and add there the following line:
erase c:\ircdoor_home_directory\nodeinfo.* >nul
This command will erase old node information files from the
IRCDOOR home directory. Ircdoor_home_directory must be
replaced with the directory name where IRCDOOR/2 files are
located.
IRCDOOR/2 creates and uses nodeinfo.* files in it's home
directory and it automatically deletes them when a user
exits the door. But if you encounter a system crash during
the time when IRCDOOR is running, you should manually
remove nodeinfo.* files from it's home directory to prevent
IRCDOOR from thinking that it is running at the moment.
That's why the best way to avoid this is to insert that
mentioned erase command above to your STARTUP.CMD file so
whenever your system reboots, old IRCDOOR node information
files will be deleted.
6.0 IRC commands supported by IRCDOOR/2
The following is a list of IRCII commands currently
implemented in IRCDOOR/2:
/LIST Lists all current irc channels, number of
users, and topic. (slow and can terminate
connection on some servers)
Example on /LIST command: /LIST -min 10
/NAMES Shows the nicknames of all users on each
channel
/JOIN <channel> Join the named channel. All non-commands
you type will now go to everyone on that
channel. Channel must start with the '#'
character. If you are on a channel, the
/JOIN command will also automatically
get you out of the channel you are cur-
rently in, and will bring you to the
specified one.
Example on /JOIN command:
/JOIN #usa
/MSG <nick> <msg> Sends a private message to the specified
person. Only the specified nickname will
see this message.
Example on /MSG command:
/MSG Hoolio Hello Hoolio!
/NOTICE <params> Params are identical as to /MSG command,
the only difference to /MSG command is that
/NOTICE sends a notice, not a message.
Example on /NOTICE command:
/NOTICE Dink Here i am. :-)
/NICK <nick> Change your nickname
When you're connected, your BBS login name
is usually taken as the default 'nickname'
for yourself. You may wish to change this
with this command.
Example on /NICK command:
/NICK IRCD00R
/QUIT or /BYE Exits IRC.
/HELP Gets IRCDOOR online help menu. When using
online IRCDOOR help system, use ENTER and
numeric keys to navigate around. When
IRCDOOR displays a [more] message on your
screen, you might wish to quit listing by
pressing ESCAPE or Q key.
/WHO <channel> Shows who is on a given channel,
including nickname, user name and host,
and realname.
/WHOIS <nick> Shows the "true" indentity of someone
Use this often to make sure you know who
you are talking to, because nicknames are
NOT owned so any number of people could
use a nickname.
/WHOWAS <nick> This command asks for information about a
nickname which no longer exists. This may
either be due to a nickname change or the
user leaving IRC.
/MODE <params> Allows both usernames and channels to have
their mode changed. This can be only used
by channel operators. The <params> should
contain valid parameters for the /MODE
command i.e. the channel name, the
nickname (when appropriate), and the /MODE
command switches. The following listed are
some most used /MODE commands:
/MODE <channel> <+|->o <nick> - take/give the channel operator
privileges for the specified
user.
/MODE <channel> <+|->i - change invite-only flag for
the specified channel.
/MODE <channel> <+|->p - change private flag for the
specified channel.
/MODE <channel> <+|->s - change secret flag for the
specified channel.
/MODE <channel> <+|->t - change topic-setable flag for
the specified channel.
/MODE <channel> <+|->n - set/unset no messages to
channel from the outside flag.
/MODE <channel> <+|->m - change moderated channel flag
for the specified channel.
/MODE <channel> <+|->l <lim> - set/unset the user limit to
channel.
/MODE <channel> <+|->b <user> - set/unset a ban mask to keep
the specified user out of the
channel.
/MODE <channel> <+|->v <user> - give/take the ability to speak
on the moderated channel.
/MODE <channel> <+|->k <pass> - set/unset a channel password.
Examples on /MODE command:
/MODE #latvia -o Kaspariic
/MODE #gonnabe +b *!*@microsoft.com
/KICK <params> The KICK command can be used to forcibly
remove a user from a channel. It 'kicks
them out' of the channel (forced PART).
This can only be used by channel opera-
tors. The <params> consist of the spaced
<channel>, <nick> and <comment> options.
Note: the <comment> option is not
obligate.
Example on /KICK command:
/KICK #ircdoor Lamer Lamers not allowed
/INVITE <params> The INVITE message is used to invite users
to a channel. The <params> should consist
from parameter <nickname>, which is the
nickname of the person to be invited, and
parameter <channel>, which is the target
channel to invite the user to.
Example on /INVITE command:
/INVITE JohnDoe #legends
/TOPIC <params> The TOPIC message is used to change o
view the topic of a channel. The <params>
can contain two parameters: the <channel>
and the <topic>. The topic for channel
specified in the <channel> is returned if
there is no <topic> parameter given. If
the topic parameter is present, the topic
for that channel will be changed, if the
channel modes permit this action, and if
you are the channel operator.
Example on /TOPIC command:
/TOPIC #switzerland Weather In Switzerland
/PART <channel> Lets you leave the specified channel. You
may also use the /LEAVE command to leave
a channel, but generally you won't need
to use this command because /JOIN will
automatically get you out of current
channel and bring you to the specified one.
/CTCP <nick> <cmd> The /CTCP command sends a CTCP request
to the specified user on IRC. The <cmd>
parameter is a valid CTCP request command.
The following are supported CTCP request commands:
CLIENTINFO Obtains information about other IRCDOOR/2
internal CTCP request commands.
PING Will generate a reply on remote's "PING"
message.
TIMELEFT This is internal IRCDOOR/2 CTCP command
that let's an IRC user to query how much
time is left for the IRCDOOR/2 user.
This only applies to remote BBS users.
USERINFO Obtains user information on a client. User
information includes user's name, city,
nickname, IRC server he is connected to,
and IRCDOOR/2 version information.
VERSION Obtains version information on a client.
IRCDOOR/2 version information will be sent.
Examples on /CTCP command:
/CTCP MisterX CLIENTINFO
/CTCP JohnDoe VERSION
/PING <client> The PING message is used to test the
presence of an active client at the other
end of the connection. It can be used to
ping clients, servers and nicknames.
/VERSION <server> The VERSION message is used to query the
version of the server program. An optional
parameter <server> is used to query the
version of the server program which a
client is not directly connected to.
Note: for getting versions for clients,
use the /CTCP <nick> VERSION command.
/SERVER <params> This command allows you to change current
IRC server without exiting the door. This
command may not be available if SysOp
doesn't want to allow remote users to
change IRC servers. The <params> consist
of two parameters, <server> and <port>.
<server> specifies a server to connect
to, and <port> is an optional port number,
or 6667 if not specified.
Example on /SERVER command:
/SERVER irc.funet.fi 6666
/QUOTE <params> The /QUOTE command lets you to send a custom
reply to IRC server. For example, some IRC
servers on Undernet require clients to send
the PONG reply. With "/QUOTE PONG" command
the PONG reply is sent back to the server.
You may also use /QUOTE command to send any
other commands, which are not nativaly
supported by IRCDOOR.
7.0 IRCDOOR/2-specific commands
/TIMELEFT The /TIMELEFT command lets the user to
check how much time left for his IRC
session. This only applies to the remote
BBS callers. For local callers, their
session time is not limited.
/WHOELSE The /WHOELSE command lets the user to
review who else is using IRC from the
same BBS at that present moment.
8. Comments
-------------------------------------------------------------
As you can see, IRCDOOR/2 is full of features that could
make your BBS users feel happy. There is lot of work spent
to make the IRCDOOR as good as it is now, and i'd like to
thank the following people who have been alpha-testing IRCDOOR
and helped me a lot:
Bob Juge,
Andy Tarasov
I am also thankful to my wife, Nataly, my father Longin,
and to all my friends who were understanding me why i
could not go for holidays, and for their advise on where
to go next. :)
-------------------------------------------------------------
Some words about me: i am independent programmer and i
am interested in job opportunity in other countries.
I have experience in DOS, Windows and now OS/2 programming,
and i am looking for a company wishing to employ me at a
constant or contract job. If you could help me with this,
please let me know As Soon As Possible!
You are welcome to visit my WWW home page at my own WWW server:
http://www.andrews.net.lv/~mrbyte
The IRCDOOR home is
http://www.andrews.net.lv/software/ircdoor.html
Check it out! There is also a growing FAQ list about the door.
-------------------------------------------------------------
IRCDOOR/2 Command-line usage:
ircdoor [{-p<handle> -d<dpath>} | {-l}] [-h<hostname>
-n<nickname> -u<username> -r<realname> -s<server>
-$<port> -t<time> -k<node>] [flags]
Information about parameters:
-p<handle> specifies an open OS/2 com port "handle" to use or
a com port device name (including the port number).
If you are going to run IRCDOOR from a OS/2 BBS, then you
should specify a open com port handle number as a parameter.
<handle> is not a number of a com port, it's a handle that the
OS returns when you open com port under OS/2. Normally an OS/2
BBS can pass a com port handle to an external program, doors,
etc. Maximus BBS software is a typical example. However, if
your BBS software cannot pass a com port handle through
command line (common for DOS BBS software), you will need to
pass a COM port device name directly, instead of a handle.
For example, the following command causes IRCDOOR to open
COM1 port device:
ircdoor.exe -pCOM1 -dC:\RENEGADE\DOOR.SYS -s"irc.nol.net"
-d<path> specifies a full path to created door drop-file.
The path SHOULD include filename too. Supported drop-files
are currently DOOR.SYS and DORINFO?.DEF. If i receive
submissions to add support for more drop-file formats, i will
be add to do so.
The -p and -d switches specified on command line indicate that
the door should be run from a BBS, obviously in remote mode.
See sample OS/2 command file for reference.
-l parameter indicates that the door should be run in local
mode. Note: if -p or -d (or both) are omitted, the door will
assume local mode as well.
-h<hostname> specifies local host name for your machine. This
is usually localhost, specified in your IAK configs. Local
host value is used to register a particular IRC user on IRC
server.
-n<nickname> specifies nickname to use for IRC. By default,
BBS alias of a user will be read from BBS drop-file, and
used as nickname. However, it can be specified via command
line too.
-u<username> specifies local user name on your machine. The
username and the localhost are two things that construct the
e-mail address of a IRCDOOR/2 user. If it's not specified,
username of 'ircdoor' will be used. This option is only
available in the registered version of IRCDOOR.
-r<realname> indicates user's real name to use for
registering on IRC server. Realname (as well as nickname) is
automatically read from BBS drop-file, and presented to a
user upon the start. This option is only allowed in the
registered version of IRCDOOR.
-s<server> indicates IRC server name or IP address to connect
to. Consider using IRC server that is closer to your location.
There are some servers provided in the IRC.MEX sample code,
but if you don't live in Scandinavian countries or Baltics,
consider using other IRC servers than those.
-$<port> parameter is used to specify a port number for the
server. Normally, it is 6667. This is also by default.
However, you can always specify a non-standard port number
for IRC.
-t<time> parameter specifies time (in seconds) for the IRC
session. This only works in remote mode. If your BBS software
cannot pass time value in seconds, let me know and i'll add
support for minutes. :) Note: the value is automatically
read from BBS drop-file. Override it (if you wish) from the
command line.
-k<node> parameter specifies a BBS node number, on which
IRCDOOR is run. This parameter is only required if the node
information cannot be obtained from the BBS drop-file e.g.
DORINFO?.DEF, or IRCDOOR is running in local mode.
Now about flags:
Flags are used to toggle some operational stats of the
IRCDOOR/2. They are specified as a normal switch, and a
plus "+" or a minus "-" should be added to enable or
disable a particular option. The following are flags used
in current version of IRCDOOR/2:
-o When enabled (through -o=on/off), all remote user's input
and output will be shown on the sysop's local screen.
This is useful if you want to see who is doing what
and where on IRC, ;) but it might consume some system
resources to display the information on your screen.
This option is enabled by default.
-------------------------------------------------------------
If you cannot or wish not to setup IRCDOOR/2 with your BBS
software, but if you would like to see how the door looks
in practice, feel free to telnet to:
andrews.net.lv (194.8.7.67)
and see it with your own eyes. You might be able to figure
out whether it's fair enough to register, then.
What are differences between the registered and unregistered
versions of IRCDOOR/2?
The following is a list of features that are currently
disabled in the shareware version, and are fully available
when you register your copy of IRCDOOR:
- time for the IRC session is limited to 10 minutes. The
registered version allows to change it to whatever you
want.
- channel op's commands (/MODE, /KICK, /INVITE, /TOPIC)
and /CTCP requests aren't available in the shareware
version. They are fully available in the registered
version.
- username and realname cannot be changed in the shareware
version. You might set them only in the registered
IRCDOOR version.
9. Registration information
As stated in the license agreement, IRCDOOR/2 is distributed
as "shareware". By this, it is meant that the IRCDOOR/2
user can use the door for a limited time of 28 days, and
then whether register, or discontinue using it.
If you wish to register your copy of the IRCDOOR/2, please
see the file REGISTER.TXT and ORDER.FRM for registration and
order information.
10. IRCDOOR/2 distribution information
Latest shareware versions of IRCDOOR/2 should be obtained from
the following sites:
ftp.dcbalt.vernet.lv (*)
/base2/bbsfiles/comm/bbsdoors/ircdoor/ircdor*.zip
juge.com (*)
/ircdoor/ircdor*.zip
hobbes.nmsu.edu
/os2/network/tcpip/ircdo*.zip or /os2/incoming/ircdo*.zip
IRCDOOR/2 can be file-requested across Fidonet under magic
name 'IRCDOOR' from the following nodes:
2:5100/33 (telnet: bbs.dcbalt.vernet.lv) (*)
1:106/2000 (telnet: juge.com) (*)
(*) - IRCDOOR/2 distribution site.
11. Contact information
If you encounter problems using the door, find bugs, etc.,
please feel free to contact the author at one of the
following e-mail addresses below:
mrbyte@andrews.net.lv,
mrbyte@dcbalt.vernet.lv,
mrbyte@unix.dcbalt.vernet.lv
or, you can reach me on Fidonet at 2:5100/33 (my BBS), or
even telnet directly to my BBS (andrews.net.lv) and
leave a comment to the SysOp. If you wish to test the door,
you can register on my BBS as a new user and try the door
by yourself.
Happy IRC!
Andrew Eigus (aka Mr. Byte)
7/Feb/96
EOF