Setting up a conference is all dependent on how you want things to be
configured. For example in your message conferences, you might want a
conference for each message network that you carry, or in your file
conferences, you might want to separate your bases by type of files. All your
utility files in one conference, and all your door files in another. It's all
dependent on what you want your message and file system to look like, I will
setup one file conference and one message conference to show you the basics,
but with a little practice and thought, you can make a really complex system,
that simplifies the differences.
1. First off, select what you want to separate; if it's a file area look at
the type of files that you have. One conference setting that is popular
is the separation of adult files from the rest. This is a setting that I
will set up for you to show you the basics.
2. Next, enter the file conference editor and enter in the name and access,
for an example look at the screen below:
______________________________________________________________________________
\_________ . __________ . __ | ________ __ . ___/
// \ : \ \\ | \ : \ \\ \ : \ jp
__/ \ | \ \ : \\ . \ \ \ | \\
\_________/____| //_____/_____ _/__________/______/_______/___ ' /
[iniquity2.0] |____/ ========= /__________/ =============== \\____________/
(Iniquity File Conferace Editor):::::::::::::::::::::::::::::::
::: Current Conference 1
(A) Key A
(B) Description Adult Bases
(C) ACS S75
([) Previous Conference
(]) Next Conference
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
À: iq config % arrows: move lightbar enter/key: select escape: quit menu :Ù
I have created a conference for the adult file bases, with a key selection
of 'A' and a description of 'Adult Bases', also note the access level, it
is set for security level 75 meaning that only those with a SL of 75 or
greater will have access to this conference.
______________________________________________________________________________
\_________ . __________ . __ | ________ __ . ___/
// \ : \ \\ | \ : \ \\ \ : \ jp
__/ \ | \ \ : \\ . \ \ \ | \\
\_________/____| //_____/_____ _/__________/______/_______/___ ' /
[iniquity2.0] |____/ ========= /__________/ =============== \\____________/
(Iniquity File Conference Editor):::::::::::::::::::::::::::::::
::: Current Conference 2
(a) Key B
(b) Description Regular Bases
(c) ACS S50
([) Previous Conference
(]) Next Conference
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
À: iq config % arrows: move lightbar enter/key: select escape: quit menu :Ù
I have also created a conference that will be used for the regular file
areas, a different key is used, and a new description has been entered,
but note the access level, S50, this means that anyone with SL or 50 or
greater can access this conference.
3. Last, I will edit my file areas to utilize the conference system in a more
dynamic way, I limit the access to the file area via the conference. Look
at the example I have created below.
______________________________________________________________________________
\_________ . __________ . __ | ________ __ . ___/
// \ : \ \\ | \ : \ \\ \ : \ jp
__/ \ | \ \ : \\ . \ \ \ | \\
\_________/____| //_____/_____ _/__________/______/_______/___ ' /
[iniquity2.0] |____/ ========= /__________/ =============== \\____________/
(Iniquity File Area Editor):::::::::::::::::::::::::::::::
::: Current Area 1
(a) Description Pr0n
(b) Filename JPEG1
(c) File Path C:\INIQ\FILES\JPEG1
(d) Area Sponsor Discofunk 1978
(e) Access ACS XA
(f) Upload ACS =
(g) Download ACS XA
(h) Password
(i) Sort Method Filename
(j) Sort Direction Ascending
([) Previous Area
(]) Next Area
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
À: iq config % arrows: move lightbar enter/key: select escape: quit menu :Ù
By changing the access ACS code to XA, I have limited access to those who
only have access to the conference with the key of 'A'. The user must be
in that conference before they will view this particular file area.
Note: A message conference system works much the same way only it deals with
the message bases instead of the file bases. Here's how you'd go about
setting up a message conference.
1. First off, select what you want to separate; if it's a message area look
at the type of message bases that you want to have. One conference setting
that is popular is the separation of adult message areas from the rest.
This is a setting that I will set up for you to show you the basics.
2. Next, enter the message conference editor and enter in the name and
access, for an example look at the screen below:
______________________________________________________________________________
\_________ . __________ . __ | ________ __ . ___/
// \ : \ \\ | \ : \ \\ \ : \ jp
__/ \ | \ \ : \\ . \ \ \ | \\
\_________/____| //_____/_____ _/__________/______/_______/___ ' /
[iniquity2.0] |____/ ========= /__________/ =============== \\____________/
(Iniquity Message Conference Editor):::::::::::::::::::::::::::::::
::: Current Conference 1
(a) Key A
(b) Description Adult Message Networks
(c) ACS S75
([) Previous Conference
(]) Next Conference
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
À: iq config % arrows: move lightbar enter/key: select escape: quit menu :Ù
I have created a conference for the adult message bases, with a key
selection of 'A' and a description of 'Adult Message Networks', also note
the access level, it is set for security level 75 meaning that only those
with a SL of 75 or greater will have access to this conference.
3. Last, I will edit my message areas to utilize the conference system in a
more dynamic way, I limit the access to the file area via the conference.
Look at the example I have created below.
______________________________________________________________________________
\_________ . __________ . __ | ________ __ . ___/
// \ : \ \\ | \ : \ \\ \ : \ jp
__/ \ | \ \ : \\ . \ \ \ | \\
\_________/____| //_____/_____ _/__________/______/_______/___ ' /
[iniquity2.0] |____/ ========= /__________/ =============== \\____________/
(Iniquity Message Area Editor):::::::::::::::::::::::::::::::
::: Current Area 1 of 200
(a) Description Adult Discussions
(b) Filename ADULT
(c) Msg Area Type Local message area
(g) Area Sponsor SysOp
(h) Access ACS CA
(i) Post ACS CA (1) Unhidden No
(j) Max Messages 200 (2) Real Names Yes
(k) Password (3) Private Yes
(l) QWK Name ADULT (4) Mandatory No
(m) Messages 0 (5) Anonymous Yes
([) Previous Area
(]) Next Area
ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
À: iq config % arrows: move lightbar enter/key: select escape: quit menu :Ù
By changing the access ACS code to C, I have limited access to those who
only have access to the conference with the key of 'A'. The user must be
in that conference before they will view this particular message area.