home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
UFL100.ZIP
/
UFL.DOC
< prev
next >
Wrap
Text File
|
1995-06-25
|
24KB
|
755 lines
... AE Production's Present ...
... UFL v1.00 ...
... Copyright (c)1995 ...
...Protection Plan... :)
As with all software that is released out in todays circuit lines, we
must mention that we are not liable for any damages done by our
software.
Why is this? Well, we dont need to add this extra section about
liability etc... but to give you some insight on why you see that
message on just about everything you download.
You may NEVER see a bug at all... and with UFL i doubt you will.
Any bugs that ARE found please write us!!! We will IMMEDIATELY
remove them.
...About...
UFL is a ( User File Listings ), The basic idea is to allow the user
(whomever) it may be, to create a file listing of files that they have
available on THEIR system, that, may be kinda old, really old, or people
who simply dont upload :o.
They can take their time adding files and descriptions etc... on their
own file listing. They may execute the EDIT command whenever they are
prepared to add another file to their list.
"UFL will NOT allow a user to edit any other file listing but their own"
Not only are users able to create file lists, but they can also view all
other users file lists that are available.
Another GREAT kick to it is that, you the sysop, do not have to go
threw the harrasment of file requests etc.... At least slow them down
a GREAT deal.
UFL will also INFORM the owner of the files that were requested at the
time he/she logs back into the door.
This is just a small portion of what this POWERFUL online door can do!!
-------------------------------------------------------------------------
...SPECIAL THANKS...
To: THE MUSIC BOX BBS SysOp: MUSIC MAN
Ph: 609-461-???? Note: Original ßeta Test Site Of UFL.
-------------------------------------------------------------------------
...How To Set It Up To Run With Your BBs...
To set up the door is not to difficult, Simply set up a batch file, which
would be the easier way, and add the following lines...
1: CD\<path to door executables>
2: UFL.EXE C:\BBS\<path to drop file>
1. Is the path where you have unzipped the door in.
2. Is to simply Load UFL and the path is where your dropfile is. A drop-
file is simply a file that is created before a door executes. Such
names as....
DORINFO#.DEF
DOOR.SYS
EXITINFO.DEF
etc...
And have your bbs call the .BAT file.
Many different formats, if UFL dont work with yours please mail us and
we'll make sure that the very next version supports it, or will work
regardless.
UFL has many upgrades to come...
***OPTION***
A couple ways can be used to set up UFL, you can announce it inside your
doors menu, or you can simply set it up as a command on most bbs's.
The first user into the door will have no choice but to create a listing
or simply exit back out. Users can also remove their own file listings.
CONTENTS
──────────────────────────────────────────────────────────────────
CONFIGURING UFL ............................................. P
[L] oad Database ............................................ 1
[I] nformation .............................................. 1
[G] o To BBS ................................................ 1
[R] equest File ............................................. 2
[F] ile Menu ................................................ 2
[D] isconnect ............................................... 3
[A] ll Requests .............................................
[T] oggle Pause ............................................. 3
[V] iew Listing ............................................. 3
[C] reate Listing ........................................... 3
[E] dit Listing ............................................. 4
[?] Re-Display .............................................. 5
[S] earch User .............................................. 5
[P] age SysOp ............................................... 5
[H] elp ..................................................... 5
UFLCFG.EXE .................................................. 6
UFLMAINT.EXE ................................................ 6
About: REQUESTS and RETURN SLIPS ............................ 7
Requesting When File Already Has been sent to another user? . 8
Useing UFL locally .......................................... 9
REGISTERING ................................................. 10
FUTURE ...................................................... 11
──────────────────────────────────────────────────────────────────
P]
CONFIGURING UFL
---------------
Ufl v1.00 can be configured now more than we were going to allow..
you can configure the following...
How many entrys slots for "OWNERS"
How long a page will last in beeps....
The name of the logoff screen "ANS/AVT/ASC/RIP"
The name of the logon screen "ANS/AVT/ASC/RIP"
COLORS IN LIST#.LST
-------------------
The Header Color
The Filename color
The OFFLINE Color
The Size Description color
The Description color
-------------------
The Communications Port Address
The Communications Port IRQ
Type UFLCFG and press ENTER
-----------
| PAGE 01 |
-----------
...[L] OAD_DATATBASE...
This command is not all to important by any means, it will simply
"re-load" the database that currently gets loaded when a user logs
into the door.
...[I] NFORMATION...
Again, not very important, this command will simply show the user
the credits of UFL.
...[G] O_TO_BBS...
This command will ship the user back to the bbs, simple enough...
-----------
| PAGE 02 |
-----------
...[R] EQUEST_FILE...
This is a very intelligent command, this command will allow the user
to request a file, upon pressing "R", the user will have a choice of
choosing 2 more commands, they are....
(L)ist (Q)uit
If the user press's "L" to List, then it will show/list the users
that currently have ADDED THEMSELVES to the database, these are the
users who have begun to create their own file lists.
It will display to the user the "LIST #" and "OWNER OF THE LIST",
they will then be asked which list they would like to request from,
here they enter the "LIST #" and it will display the owners list.
Upon doing all of this, when the list is finally done being displayed
they are asked for the filename they want to request.
Thats basically it "on the requesters side", but for UFL it creates
a database of all requested files, when the owner of ANY file that
was requested logs into the door they are shown the database of ONLY
the requested files of THEIR list. Along with the Name of the user
who requested it/them, and the DATE as well.
When the request is being shown to them, the only option they have
is to (C)ontinue, or (Q)uit without looking at any other request's
that were made from his/her listing.
***IMPORTANT*** ***IMPORTANT*** ***IMPORTANT*** ***IMPORTANT***
With the UNREGISTERED Version of UFL, you recieve a data pack of 50
requests at one time. Now, this could do fine "IF" your owners of
their file lists kill their "Request Slips" that have been sent to
them by the requester.
See, each time a user requests a file from a specific user, a
REQUEST SLIP is sent to the owner of the file that was requested,
when the owner of these slips logs into the door, he/she will
be shown automatically all the requests from him/her since the
last time in.
The ONLY way that the users can KILL/DELETE these request slips is
by doing what they are supposed to do, and thats by sending the
requested file. After the file has been sent, then the request
slip is automatically removed from the database.
...FILE_MENU...
The POWER of UFL? Not all of it! :) but does contain a rich amount
of it!!!
Here when a user comes into the file menu, "Which is very intelligent"
the user will see 4 commands.
[U]pload Request [C]heck Requests
[D]ownload Request [Q]uit To Main
Now, dont worry!!! NO'ONE CAN JUST UPLOAD A FILE!!! we've thought
about that well ahead, in order for a user to be able to UPLOAD,
THEY _MUST_ HAVE HAD A REQUEST SLIP!!!! Not only that, BUT, when
the owner of the file being requested go's to upload the file, he/she
cant just enter in any old filename, the program is set to recieve
the FILENAME that was requested!!! There is no prompt asking for
a filename to be recieved!!!
And, if there simply were no files requested, no command will do
anything!! "As far as the uploading is concerned, you are shipped
back to the main menu.".
This way, we know we're getting what is supposed to be sent!!! and
not some hacker trying to stuff our HD.
Alot of work has gone into this section, Not saying that the rest is
junk or anything! But we've typically went out of our way to try and
make your system as safe as possible from harmful users.
[U]pload
--------
When a user goes into the file menu and picks Upload, a few databases
are scanned, if no request slips from any other users exist for that
current user, then they are shipped back to the main menu.
If there is a request slip, then they are shown it, and have the choice
of sending THAT FILE. Or, they can simply wait, and the slip will
remain in the database till they upload the file.
-----------
| PAGE 03 |
-----------
...[D] ISCONNECT...
This command will DISCONNECT/HANGUP the user... they do not need to go
back to the bbs to hangup.
...[T] OGGLE_PAUSE...
This will toggle the more/pause prompt, mainly needed for when viewing
long listings, or HELP.
*NOTE* This command may be removed in future versions and replaced,
as UFL will do the toggling on its own.
...[V] IEW_LISTING...
This command will bring a prompt up, in the UNREGISTERED there is a
prompt like the following...
Which List (1-15):
In the REGISTERED Version you will have "currently" the following prompt
Which List (1-999):
Here, Which List means "View Which Owner List", This may be more
complicated trying to explain than doing. If a few users have gone into
UFL and used the (C)reate command, then added files to their personal
list, then "Which List (1-999)" is the number of a owners file list.
Did you get that? :) Well, if not, dont worry, its really pretty simple
when you simply just do it.
...[C] REATE_LISTING...
Creating a listing is what must be done first if the user is planning on
creating his/her own file list. No creation needs to be done if the
user is only trying to view other file lists.
Assumeing the user wants to create a file list, he/she would press 'C'
and be asked if they are sure they want to create a listing. If so,
then UFL automatically creates their record based off of their handle.
After pressing 'Y'es for the 'Are you sure ...' question, the user is
returned back to the Command Menu. Now, the user has created a data-
base of their own, and now may 'E'dit their list. We describe the
'E'dit function next on PAGE 4.
-----------
| PAGE 04 |
-----------
...[E] DIT_LISTING...
This may be the most complicated command, "Intelligence Wise". Here when
the user choose's to [E]dit their file list...
They MUST have used the [C]reate command 1st. If not they will recieve
a message informing them that they were not found in the database, and
they cannot edit any lists.
If a database has been [C]reated, then when the user choose's [E]dit
they will be shown their information about their database, this would
look something like this....
Owner Of List : <Users Name/Handle>
List # : <The users number in database>
Num. Files : <Total Number of files in users list>
Filename : <Filename of users list#.lst>
Then when done displaying this information, the user be will be handed
a command line menu.
(A)dd File (V)iew List (K)ill (Q)uit :
(A)DD
-----
When (A)dd File has been choosen, a prompt will display asking for the
FILENAME of the file that the owner wants to add to the list. Then
after the FILENAME, they are asked for the "An Aprox. Size", this is
just a rough idea of how big the file is. Then finally, they are
asked for a "1" line description, After this has been completed the
UFL database is updated and the users current LIST#.LST is created.
To determine different users we use a header to describe each users
own file to other users when viewing.
(V)IEW
------
Chooseing the (V)iew option will display to the owner his/her own file
list, and return them to the command menu.
(K)ILL
------
This command will DELETE the current owners LIST#.LST. *NOTE* This
will not destroy the user from the database. No option has been
implemented to destroy a user from the UFL Database. This option
WILL exist in the very next upgrade.
*NOTE* Timeing on this document is behind on the program completion
so, the option to remove a user from the UFL Database may
exist.
(Q)UIT
------
Simply enough, this command will allow the owner to quit editing
his/her file list.
-----------
| PAGE 05 |
-----------
...[?] RE-DISPLAY...
This command will help some who have any type of interference, such as
line noise mess there screen up, they can "re-display" the menu.
...[S] EARCH_USER...
Again, this is another command with a bit of intelligence, This option
will allow the online owner/viewer to SEARCH for a user, if the user is
found, then a little list pops up about the Owner.
Continuously after that, a command line menu will appear, this menu
will ask if the user would like to view the "FOUND" owner's list of
files.
...[P] AGE_SYSOP...
This little command will allow the online user to page you, "The SysOp"
into a chat.
...[H] ELP...
A very nice feature, here EVERY command is convered and its all imbedded
into the program. An online help command. Although, you can create
your own text file and add it to the configuration program and instead of
displaying the online help database, it will display the text you've went
ahead and created.
Be sure to make sure you do explain in your text correctly, so your users
do not get confused.
-----------
| PAGE 06 |
-----------
UFLCFG.EXE
----------
User File Listings v1.00 Configuration Program. This program will allow
you to configure UFL to an extent.
The following options are available....
Setting the LogOff screen filename,
Setting the sysop page length,
Setting the total entrys allowed,
Setting the Help screen filename,
"Setting the total entrys allowed"
----------------------------------
At this time, with the UNREGISTERED version you cannot have more than
15, but you may lower the total if there is a need to do so, This is
the biggest disadvantage not counting the delays. REGISTERED you get
a 75 user database.
If you try to save the configuration with more than 15, it will
default back to 15.
Setting the FILE#.LST Header Color
Setting the FILE#.LST Filename Color
Setting the FILE#.LST Offline/Size Color
Setting the FILE#.LST Description Color
Setting the SysOp Chat Color
Setting the Users Chat Color
( Setting the chat colors needs a little explaining.... Each color for )
( each the SYSOP and USER starts from 1 to 9. Now, you can go higher, )
( but going higher affects the background and foreground. If you only )
( wanted to have a single color for each user in chat, the you would )
( specify a single digit. )
( )
( Exp: Sysop Color = 1 ( Blue ) Users Color = 8 ( Dark black ) )
( )
( If you wanted to add a background color for both sysop and user you )
( would do the following.... )
( )
( Exp: Sysop Color = 18 ( Dark-Black on Blue ) )
( User Color = 51 ( Blue on Magenta ) )
( )
( Typically, most of the time, you will most likely want single colors! )
Setting the current IRQ for your port....
-----------------------------------------
MAKE SURE YOU SET THIS CORRECTLY!!! RUN UFLCFG.EXE TO SET
UFLMAINT.EXE (REGISTERED VERSION)
------------
This program should be thrown into your bbs maintnance batch file so that
it will continue to check UFL database's for dates etc...
UFLMAINT.EXE takes care of all maintnance needed....
( This program deletes any files left and not picked up after 30 days )
*NOTE*
This feature may be added to version 2.0, but if as with all future
upgrades, the price will rise. So register now and make out!!!
You'll recieve this utility at the time it is completed.
-----------
| PAGE 06 |
-----------
...ABOUT REQUEST AND RETURN SLIPS...
This page will explain to you all about the requests and return slips.
First, when a user REQUESTS a file, a REQUEST SLIP is sent to the owner
of the file.
When the owner of the file logs on, he/she will see the request slip.
They then just continue, go to the file menu and send the request,
once the request has been sent, a return request slip is sent to the
requester, and the request in the database is removed.
2nd, the user who requested the file, "like said a moment ago" will
recieve a return slip. They from there on must delete their own
return slips.
-----------
| PAGE 08 |
-----------
Requesting A File Thats Been Sent To Another User Already
.........................................................
If a file has been sent already to another user, and that
user has not downloaded it yet, and another user requests
that same file, they will be asked if they would like to
download it if it already exists. They will not have to
wait for another copy, "Which would be pretty sensless".
*Note* Remember, ALL files uploaded are sent to the main
UFL Directory.
-----------
| PAGE 10 |
-----------
Useing UFL Locally
------------------
Going into UFL locally you can do everything a user could do online.
Except for a few acceptions, To get rid of any return slips that may
have been sent to you when you requested a file, you too! have to
download your file. ( UFL will realize that you are local, and will
skip the actual transer section.
It will NOT delete the file after you have downloaded it locally!
You should MOVE the file that you requested to your own personal dir.
When sending a user a request file, it's all the same as downloading
a request.
-----------
| PAGE 10 |
-----------
PRICES...
---------
In Standard Usage, $25, In Company Usage, $60
If this copy of UFL has been registered for standard use, it may NOT be
used for COMPANY usage.
If you need a copy for COMPANY usage, you must register for one...
-----------
| PAGE 11 |
-----------
Future Of UFL
-------------
Many ideas are flowing for UFL. We can say this...
The Next Version...
1. Will contain more configuration options
2. Will allow a user to upload his/her own LIST#.LST to replace their
current one. "If they dont feel like doing it online".
3. Will allow more than 1 header in FILE#.LST, a owner of a list will
be able to add new "Header Topics", such as C Files, Asm Files...
etc...
4. Multi-Node support
And others...
...CLOSEING OUT...
. .. .....RECIEVE THIS WHEN YOU REGISTER...... .. .
With the UNREGISTERED VERSION you recieve a 10 second delay, as well as
only 15 available slots at one time. REGISTERED VERSION COMES WITH 115
available slots, if there is a need for such higher numbers of slots,
then we'll add them.
With the REGISTERED VERSION their are no delays, and larger OWNER
slots... as well as all future versions free of charge, and a larger
REQUEST bank. Plus comes with the very needed UFLMAINT.EXE program.
Also, with the REGISTERED version, you recieve a DATACFG.EXE utility!!
This utility will allow you to REMOVE users from the database if they
have tooken months to bother even going into the door and checking on
their requests.
As well as a VERY USEFUL FUTURE ONLINE DOOR.
And remember, UFL is a high quality program, and will increase in its
intelligence as well in future upgrades.
A New (H)elp is also being "imbedded" in Next version... (Added Already)
See ORDER.FRM.
Thank you for takeing the time to view the software and hope you find it
VERY useful.
..BUGS..
One final word, If you happen to find a bug or two, please let us know!!
Even if you live around the corner, mail us a letter....
Thank You,
Thomas V. Russella