home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #1
/
monster.zip
/
monster
/
SPITFIRE
/
FFOX_007.ZIP
/
FIREFOX.DOC
< prev
next >
Wrap
Text File
|
1994-02-05
|
50KB
|
1,177 lines
FireFox version 0.07-34
Fido compatible mailer
written for
Spitfire Bulletin Board System 3.4
Copyright 1993, 1994
Alexander Erne
All rights reserved
Release date
February 5, 1994
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Index.
Index .............................................. 1
Introduction ....................................... 2
Features ........................................... 3
Getting started .................................... 4
Upgrading FireFox .................................. 5
The FireFox Setup Utility .......................... 6
The FireFox Setup Utility
Edit FireFox system data ........................... 7
The FireFox Setup Utility.
Edit FireFox node information ...................... 9
The FireFox Setup Utility.
Edit FireFox node conference data ................. 11
Special conferences ............................... 13
Sending echo-mail ................................. 14
Sending net-mail .................................. 15
Exporting mail .................................... 16
Importing mail .................................... 17
Disclaimer and user agreement ..................... 18
Copyright notices ................................. 19
Credits ........................................... 20
1
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Introduction.
When I first joined the Dutch Fido-net Foundation (DFF) I immedi-
ately got into trouble, because the software I was using was not
100% compatible with the Fido-standards. After a very short
'fight' I was abandoned from the network in february 1992. From
that moment on I wanted to create a 100% compatible mailer
importer / exporter for Spitfire, but I thought that it would be
much to complicated to create such a program so I never tried. In
November that year I gave it an other thought, and downloaded all
the Fido technical standards. When I had them all, I started to
create the main program, and after one month the first version
was available: FireFox 0.01-32. This version was only capable to
export messages from Spitfire. The first version that could
import messages was 0.03-32. This version was released at the end
of february 1993. All the first releases were tested by two
wonderful man whom I would like to give my special in this
introduction
Henk van de Goor and Maurice Elfert, thanks for all the testing
you both have done, without you, I would never have made it this
far!
Diemen, may 31, 1993
2
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Features.
- Supports all the 512 message conferences of Spitfire.
- Very fast importing and exporting of messages.
- Logging in Spitfire's HEYSYSOP.LOG style.
- 100% compatible with the Fido technical standards.
- Effective use of the Spitfire message structure.
- Simple to install and use.
- Possible to attach to more than one Fido compatible
networks.
- Support for multi-user/multi-tasking environment.
- Easy to use setup program.
- Easy sending instructions for net-mail messages.
- Possibility to send and request files from the Spitfire
message-base.
In the future FireFox will become an independent front-end for
Spitfire and shall do all the mail handling like most front-ends
do for several other BBS programs.
3
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Getting started.
To install FireFox you don't need to do very much. If this is the
first time you install FireFox on your system, all you need to do
is create a directory where FireFox will reside (i.e.
C:\FIREFOX). Next you need to do is run the FireFox Setup Utility
by typing FFSETUP at the DOS prompt.
The FireFox Setup Utility will create four directories. These
directories are a work-directory, an import-directory, an export-
directory and a nodelist-directory. In the work-directory FireFox
will place the message configuration files (*.CFG and *.DAT). The
import-directory will contain all the files that are received by
the front-end you are using. These files are incoming mail-
packets, and files that were sent by other nodes on the network.
The export-directory will contain the mail-packets that were
created by FireFox when you are exporting messages. This direc-
tory will also hold the control-files that will send files to
other nodes (*.FLO) and that will request files from other nodes
(*.REQ).
The FireFox Setup Utility will search for the Spitfire home-
directory in C:\SF. If this directory could not be found, or if
this directory does not hold the Spitfire node files, the FireFox
Setup Utility will as you to enter the correct Spitfire home-
directory.
After you have run the FireFox Setup Utility, the directory
structure of your harddisk might look like this:
C:\
+--SF
| +--WORK
| +--MESSAGE
| +--EXTERNAL
+FIREFOX
+--WORK
+--IMPORT
+--EXPORT
+--NODELIST
4
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Upgrading FireFox.
When you are already using FireFox on your system, you need to
read this section.
The FireFox 0.07-34 package also includes a Upgrade Utility (this
is called UPGRADE.EXE). This utility enables you to upgrade from
FireFox 0.06-33 to FireFox 0.07-34. The main difference between
this version and the previous one, is that this version uses
structured configuration files, and that previous version only
used ASCII typed files.
To upgrade, all you need to do is run the Upgrade Utility, and
add on the command-line the file you want to upgrade. It is
recommended to upgrade the FIREFOX.CFG file first (otherwise you
might forget this file). You can do this by typing this on the
DOS prompt:
UPGRADE FIREFOX.CFG
The Upgrade Utility will create a backup file of the old file,
called FIREFOX.CF!. So if the upgrade didn't go well, you can
always restore the old file.
Next you need to upgrade the message configuration files in the
work-directory.
First you need to copy the Upgrade Utility to the work-directory.
Than you can upgrade all the message configuration files the same
way as you upgraded the FIREFOX.CFG file. This can be done by
typing this on the DOC prompt:
UPGRADE FF_CONFS.CFG
Also in this case the Upgrade Utility will create backup files of
your old message configuration files. In the example above, the
backup file will be called FF_CONFS.BAK.
NOTE In FireFox 0.06-33 the message configuration was
handled by only one file. FireFox 0.07-34 handles the
message configuration by two files with the same name,
but they carry the extension .CFG (for the configura-
tion) and .DAT (for the message data).
5
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
The FireFox Setup Utility.
FireFox version 0.07-34 has its own setup program called the
FireFox Setup Utility. This program can be executed from the DOS
prompt. With the use of this program you can maintenance all the
paths that FireFox uses, the configuration of all the node data,
and the configuration of all the message conferences.
When you start the FireFox Setup Utility you shall see a menu
that contains three options like this:
+---------------------------------------------------------------+
| FireFox 0.07-34 Setup Utility |
| Copyright 1993,1994 Alexander Erne - All rights reserved |
| Contact via BBS The Tower - 3120-6900028 - FidoNet 2:2801/157 |
| |
| 1. Edit FireFox system data |
| |
| 2. Edit FireFox node information |
| .CFG file to edit [FF_CONFS] |
| |
| 3. Edit FireFox node conference data |
| .DAT file to edit [FF_CONFS] |
| |
| Q. Quit |
+---------------------------------------------------------------+
In this menu you can select 1, 2, 3 or Q.
When you select '1', you are able to change the FireFox system
data. These data are the file paths that FireFox uses.
When you select '2', you are asked to enter the name of the file
that you want to edit (FF_CONFS default. the file carries .CFG as
extension). Then are able to change the node information.
When you select '3', you are asked to enter the name of the file
that you want to edit (FF_CONFS default. the file carries .DAT as
extension). Then you are able to change the conference data.
When you press 'Q' you will be returned to the DOS prompt.
6
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
The FireFox Setup Utility.
Edit FireFox system data.
When you have selected option '1' from the first menu in the
FireFox Setup Utility, you will be able to edit the FireFox
system data. The FireFox Setup Utility will display a screen that
looks like this:
+---------------------------------------------------------------+
| FireFox 0.07-34 Setup Utility |
| Copyright 1993,1994 Alexander Erne - All rights reserved |
| Edit FireFox system data |
| |
| FireFox home-directory [C:\FIREFOX\ ] |
| FireFox work-directory [C:\FIREFOX\WORK\ ] |
| FireFox export-directory [C:\FIREFOX\EXPORT\ ] |
| FireFox import-directory [C:\FIREFOX\IMPORT\ ] |
| FireFox nodelist-directory [C:\FIREFOX\NODELIST\ ] |
| FireFox log-file [C:\SF\WORK\FIREFOX.LOG ]|
| Spitfire home-directory [C:\SF\ ] |
| Front-End mail-directory [C:\FRONTEND\MAIL\ ] |
| Convert .FLO/.REQ to .MSG [No ] |
| (Registered version only!) |
| |
| [H] FireFox home-directory [L] FireFox log-file |
| [W] FireFox work-directory [S] Spitfire home-directory |
| [E] FireFox export-directory [M] Front-End mail-directory |
| [I] FireFox import-directory [C] Convert .FLO/.REQ to .MSG|
| [N] FireFox nodelist-directory [Q] Quit |
+---------------------------------------------------------------+
In this menu you are able to select one of the ten keys displayed
above. The exact meaning and function of these keys is explained
here below.
When you select 'H', you are able to edit the path to the home-
directory that FireFox uses. You need to keep in mind, that the
FireFox Setup Utility does not copy the FireFox configuration
file (FIREFOX.CFG) to the new directory. This directory should
hold all the executable files of FireFox.
When you select 'W', you are able to edit the path to the work-
directory. When you change this directory, the FireFox Setup
Utility will not copy the contents of the old work-directory to
the new one. This directory should hold all the message configur-
ation files.
When you select 'E', you are able to change the export-directory.
With the option 'I', you are able to change the import-directory.
7
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Both the export and the import-directory may reside anywhere on
your system, as long as the two directories are not the same. In
the export-directory all the outgoing mail-packets, the file-send
(*.FLO) and file-request (*.REQ) files will be placed. The import
directory will hold all the incoming files from your front-end.
When you select 'N', you are able to change the nodelist-direct-
ory. There this directory is not yet used by FireFox you might
want to delete the nodelist-directory, and redirect it to the
work-directory, or the FireFox home-directory.
When you select 'L', you are able to change the path and file-
name of the log file that FireFox creates.
When you select 'S', you are able to change the home-directory of
Spitfire. This directory is the directory from where you boot
your Spitfire BBS. If you enter a invalid home-directory for
Spitfire, you will be notified that the entry was wrong, and you
will be asked to re-enter the home-directory for Spitfire.
When you select 'M', you are able to set a path to the (net)mail
directory of the front-end you are using. To determine the
directory, please consult the documentation of your front-end.
When you press 'C', you can toggle FireFox to convert *.FLO and
*.REQ files to *.MSG while exporting mail. Yes means that the
files will be converted, No means that you FireFox will do
nothing with these files.
When you press 'Q', you will be returned to the first menu of the
FireFox Setup Utility.
NOTE The options 'M' and 'C' have only effect when you have
registered your version of FireFox. This is because the
converted *.FLO and *.REQ files will be placed as a
*.MSG file in the front-end (net)mail directory.
8
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
The FireFox Setup Utility.
Edit FireFox node information.
When you have selected option '2' from the first menu in the
FireFox Setup Utility, you will be able to edit the FireFox node
information. The FireFox Setup Utility will display a screen that
looks like this:
+---------------------------------------------------------------+
| FireFox 0.07-34 Setup Utility |
| Copyright 1993,1994 Alexander Erne - All rights reserved |
| Edit FireFox node information - using file FF_CONFS.CFG |
| |
| SysOp log-in name [SYSOP ] |
| SysOp real name [ ] |
| Your nodeno. [ 0: 0/ 0. 0] |
| Destination nodeno. [ 0: 0/ 0. 0] |
| Packet password [ ] |
| Compress mail-packet [No ] |
| Compress command [ ] |
| Compress parameter [ ] |
| Decompress command [ ] |
| Decompress parameter [ ] |
| Strip 'RE:' [No ] |
| |
| [L] SysOp log-in name [M] Compress mail-packet |
| [R] SysOp real name [C] Compress command |
| [Y] Your nodeno. [I] Compress parameter |
| [D] Destination nodeno. [U] Decompress command |
| [P] Packet password [O] Decompress parameter |
| [Q] Quit [S] Strip 'RE:' |
+---------------------------------------------------------------+
In this menu you are able to select one of the twelve keys
displayed above. The exact meaning and function of these keys is
explained here below.
When you select 'L', you are able to change the name that you
(the SysOp) uses to log-in to the BBS. This name is set by
default to 'SYSOP'.
When you select 'R', you are able to change your real name. This
name is normally empty, and it should be filled by your name, or
the handle you want to use when you echo messages to other
systems.
NOTE The options 'L' and 'R' are related with each other. If
FireFox exports a message, and FireFox encounters the
name you said to be your log-in name, FireFox will
9
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
automatically replace the name with the name you
entered to be your real name. FireFox works the same
way when importing. The log-in name is also used for a
special option in FireFox. Whenever a user writes a
message, and the user tells Spitfire to delete the
message when send, FireFox will export the message, and
place your log-in name in the to-field. The message
will also be made private.
When you select 'Y', you are able to edit your nodenumber.
When you select 'D', you are able to edit the destination node-
number. This node is mostly your HUB, or Host. When you are a HUB
or Host yourself, the destination nodenumber can be one of your
nodes.
When you select 'P', you are able to set a password for the mail-
packets. The password will be used both when importing and
exporting. You need to inform the person on the destination node
of the password you are using in your mail-packets.
When you press 'M', you can toggle FireFox to use compressed
mail-packets. Yes means that FireFox uses compressed mail-
packets, No means that FireFox will only create uncompressed
mail-packet.
When you select 'C', you are able to edit the compress command.
This entry must carry the extension the file has (i.e. .EXE, .COM
or .BAT). The file you enter to be your compress command, has to
be in the FireFox home-directory, or in the PATH you have set.
When you select 'I', you are able to enter parameters that have
to be used with the compress command. Whatever parameter you
enter here, you must add a (valid) 'move files to compressed
file' parameter. FireFox does not delete the compressed mail-
packets!
When you select 'U', you are able to edit the decompress command.
This entry must carry the extension the file has (i.e. .EXE, .COM
or .BAT). The file you enter to be your decompress command, has
to be in the FireFox home-directory, or in the PATH you have set.
When you select 'O', you are able to enter parameters that have
to be used with the decompress command.
When you press 'S', you are able to toggle FireFox to strip the
'Re:' in the message subject. Yes means strip the 'Re:', no means
import the message subject like it is.
When you press 'Q', you will be returned to the first menu of the
FireFox Setup Utility.
10
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
The FireFox Setup Utility.
Edit FireFox node conference data.
When you have selected option '3' from the first menu in the
FireFox Setup Utility, you will be able to edit the FireFox node
conference data. The FireFox Setup Utility will display a screen
that looks like this:
+---------------------------------------------------------------+
| FireFox 0.07-34 Setup Utility |
| Copyright 1993,1994 Alexander Erne - All rights reserved |
| Edit FireFox node conference data - using file FF_CONFS.DAT |
| |
| Spitfire conference : 1 |
| Conference name : SysOp messages |
| Net-Mail : No |
| Message routing : No |
| |
| Fido conference name [FIREFOX ] |
| Mark messages 'SENT' [Yes] Record 1 of 1 |
| Conference tag-line Spitfire conference : 1 |
| >[This is your tag-line... ]|
| |
| [A] Add conference [<] Previous Spitfire conference|
| [F] Conference name [>] Next Spitfire conference |
| [M] Mark 'SENT' [S] Select Spitfire conference |
| [T] Tag-line [-] Previous FireFox conference |
| [Q] Quit [+] Next FireFox conference |
+---------------------------------------------------------------+
In this menu you are able to select one of the ten keys displayed
above. The exact meaning and function of these keys is explained
here below.
When you select 'A', you can add a new conference to the node
conference data you are currently editing. When the FireFox Setup
Utility has added a new conference you it will directly display
the conference data, with the defaults shown above.
When you select 'F', you are able to change the Fido conference
name. By default the name is 'FIREFOX', but you can change it
into any conference name you want.
NOTE FireFox uses two special names for the Fido conference
name. These are '_NETMAIL' and "_BAD_MESS'. You can
read more about these conference names in the section
'Special conferences'.
When you press 'M', you can toggle FireFox to set imported and
exported to sent, when messages are imported or exported in this
11
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Spitfire conference. Yes means that FireFox will only export the
messages once, and while importing the messages, the messages
will not be exported again. No means that FireFox constantly will
export the messages .
When you select 'T', you can edit the tag-line that will be
placed in the * Origin-line.
Using the '<' and '>' keys, you can browse through the Spitfire
conferences. The FireFox Setup Utility will only display the
conference number, the conference name, the netmail-flag and the
allow route-flag of the conference within Spitfire.
When you press 'S', you select the Spitfire conference number
that is currently shown on the screen to be the conference
matching the Fido conference name.
Using the '+' and '-' keys, you can browse through the conference
data FireFox uses when importing and exporting mail.
When you press 'Q', you will be returned to the first menu of the
FireFox Setup Utility.
12
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Special conferences.
As already said before, FireFox uses two special Fido conference
names. These names are '_NETMAIL' and '_BAD_MESS'. The aim and
the use of there conferences will be explained in this section.
The '_BAD_MESS' conference (or better the bad message conference)
is a conference that you can use optionally. This conference will
not export any mail, but only import mail that can not be
imported in any other conference, because the Fido conference
name is not defined in the node conference data. Any message
imported in this conference will be imported the way the message
was written. Only the subject of the message will be changed by
FireFox. The first part of the subject will contain the word
'AREA:' followed by the Fido conference name. Next thing in the
subject will be the separation mark '|', and then the original
subject. If you did not specify a bad message conference, and
FireFox encounters a message from a Fido conference that could
not be found in the node conference data, the message will be
rejected, and FireFox will make a record of the rejected message
in the log-file.
The '_NETMAIL' conference is a conference you really need to add
to the node conference data. In this conference all the messages
send by net-mail will be received. You are also able to send
messages from this conference by net-mail, and even to send and
request files! Whenever FireFox imports a message send by net-
mail, FireFox makes a record of it in it's own log-file, but also
in Spitfire's HEYSYSOP.LOG. If you do not add this conference to
your node configuration data, you might miss some very important
messages that were especially send by net-mail. The usage of this
conference is explained in the section 'Sending net-mail'.
13
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Sending echo-mail.
When you want to send a message by echo-mail to other systems on
a Fido compatible network, you need to enter a message in a
conference in Spitfire that has toggled the netmail-flag on.
When you select the menu option in the Spitfire message menu to
write a message, Spitfire will ask you to what conference you
want to save the message. You can enter here the number of a
message conference that has the netmail-flag turned on. When you
have entered the conference in which you want to write your
message, Spitfire will ask you if you want to send the message
via net-mail, you answer Yes. Then Spitfire asks if you want to
purge the message after it is send. When you answer No, the
message will normally exported. When you answer Yes, the message
will be exported, and then the message will be changed a bit. The
message will be addressed to the SysOp's log-in name, and the
message becomes private. This option has been build in in Fire-
Fox, to avoid a user to give your BBS a bad name by echo-mail,
without you even noticing it.
Than you are asked to who you write the message, just type the
name to who the message is addressed. The same goes for the
carbon copies. Then you are asked for a subject. Here you need to
enter the subject you want to type about.
When Spitfire asks if the message has to be public, you must
enter Yes. If you enter No, only on your BBS the message will be
private, and on other BBS' public.
Then you can just type your message, and when you are finished,
you can save it. FireFox will export the message to the destina-
tion node if you included the message conference in the node
conference data.
14
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Sending net-mail.
To send net-mail messages, you need to set both the net-mail flag
and the allow route-flag to on in Spitfire. When you want to send
a message via net-mail, the procedure is quite the same as when
sending an echo-mail message. The only difference is, that you
can only send net-mail messages in the conference where you set
the allow route-flag to yes. When you enter a net-mail message,
Spitfire will ask you to if you want to send this message via
netmail. On this question you answer Yes. Then Spitfire will ask
you if you want to route this message. On this question you also
answer Yes. Next thing Spitfire wants to know, is where you want
to route the message to. In this field you can enter '<NM>',
'<FS>' or '<FR>', all this three options followed by a valid
nodenumber.
The '<NM>' means that you want to send a net-mail message to the
nodenumber that you write directly behind it (there are no spaces
allowed between the '<NM>' and the nodenumber!).
The '<FS>' means that you want to send one of more files to the
node you specify directly behind it (also here there are no
spaces allowed between the '<FS>' and the nodenumber!). The
message must contains a list of files that you want to send to
the node you specified. The list of files do need to contain the
complete path and filename. When you enter a '^' before a file,
the file will be automatically deleted after it is send. FireFox
will create a *.FLO file of the files you have placed in the
message.
The '<FR>' means that you want to request one or more files from
the nodenumber you have specified (also here there are no spaces
allowed between the '<FR>' and the nodenumber!). The message must
contain a list of files that you want to request. FireFox will
create a *.REQ file of the files you have placed in the message.
As already said, the nodenumber behind the '<NM>', '<FS>' and
'<FR>' has to be a valid nodenumber. Examples of valid node-
numbers are 2:2801/157, 2:2801/157.1, 2801/157, 2801/157.1, 157
and 157.1. If you use any other kind of structure for the node-
number, it might cause FireFox to run down in some error-message
(I did not test this part... <G>).
15
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Exporting mail.
When you have created the FireFox system data, the node informa-
tion data and the node conference data as explained in the
sections about the FireFox Setup Utility, you can start to
exchange messages with other BBS' who are carrying the same Fido
compatible network as you are.
First you have to export the messages your users have written on
your BBS to other systems. This is very easy. You just type the
following on the DOS prompt:
FIREFOX EXPORT
or
FIREFOX EXPORT <filename>
You must be sure that you type this in the FireFox home-direct-
ory. When you do not enter a <filename>, FireFox will automati-
cally use the node information data and the node configuration
data in FF_CONFS. If you do not want FireFox to use these con-
figuration file, you can enter any valid configuration file that
you have created with the use of the FireFox Setup Utility. The
same goes also when you are importing mail.
When you have entered this, FireFox starts exporting the messages
from your BBS. The messages FireFox exported are messages that
are not deleted, and that do have the Netmail-flag set to Yes.
When exporting FireFox displays the number of the message that is
currently being exported, the number of the Spitfire conference
where the message comes from, and the name of the Fido confere-
nce. When no message is being exported, after the Fido conference
name you van see the word 'Scanning' flashing. At that moment
FireFox is scanning for the next message to be exported.
When FireFox has finished exporting the messages, it will auto-
matically try to compress the messages with the compress command
you have specified in the FireFox Setup Utility for the configur-
ation files you are using to export.
If the compress command could be found, the mail-packet that was
created will be compressed into a *.MO1, *.TH1, *.WE1, *.TU1,
*.FR1, *.SA1 or *.SU1 file, depending of the day of the week you
are exporting your messages. This compressed file will be sup-
ported by a *.FLO file. This *.FLO holds information for the
frond-end you are using about the mail-packet that has to be
transmitted.
If FireFox could not find the compress command you have specified
in the FireFox Setup Utility, FireFox will only create a *.OUT
file. This *.OUT file is the message-package that normal should
be compressed. Some front-ends support this file.
16
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Importing mail.
Just like exporting mail, importing mail is quite simple too. You
can start to import mail when you have received your mail from
your HUB or Host. To import mail all you have to enter at the DOS
prompt is:
FIREFOX IMPORT
or
FIREFOX IMPORT <filename>
Also when importing mail you must enter this syntax in the
directory where FireFox resides. For the description of <file-
name> I would like to refer to the previous section.
As FireFox starts to import the messages, it will first search
for the decompress command you have specified in the FireFox
Setup Utility in your PATH or in the current directory. After
the decompress command was found, FireFox tries to find any
*.MO?, *.TH?, *.WE?, *.TU?, *.FR?, *.SA? and *.SU? file. If one
or more of these files were found, FireFox automatically decom-
presses them. Secondly FireFox tries to find any *.OUT file.
If any of the files above has been found, FireFox will check if
the packet password, as defined in the FireFox Setup Utility
matches. If the packetpassword does not match, FireFox will skip
the mail-packet, and compress it to a file called SKIPPED in your
import-directory. Then FireFox starts to import the messages that
these files contain. The import goes very fast, and FireFox shows
the current number of the message that is now importing, the
number of the Spitfire conference where the message is imported
to and of which Fido conference the message comes from.
17
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Disclaimer and user agreement.
The author can not be held responsible for any damage to hard- or
software that could be occurred due to the use of FireFox or any
other program belonging to the FireFox package.
De-compiling, disassembling or any other kind of reverse-engin-
eering is strictly forbidden. Changing any part of the original
FireFox package is also forbidden.
The shareware version of FireFox may be distributed freely in the
original package. A registered version of FireFox is registered
to only one person, and therefor it is forbidden to distribute a
registered FireFox package.
FireFox is provided under the shareware concept. This means that
you may use FireFox for a short trial period, after that trial
period you must decide if you want to buy the program. If you do
not want to buy FireFox, you must stop using FireFox immediately,
and you may never use FireFox again. To register FireFox, you
need to fill out the ORDER.FRM file, add the registration fee of
$ 20.00 (add the needed P&P) and return this form to me.
Unregistered versions of FireFox have a short delay of 15 seco-
nds, and when exporting and importing messages. You will also
encounter a 15 seconds delay every time you enter the first menu
of the FireFox Setup Utility. Whenever FireFox exports a message
written on your BBS, FireFox will place '[Unregistered]' on the
tearline of the message. Further more, you are not able to
convert *.FLO and *.REQ files to *.MSG files.
Because FireFox is being written in parts, this version of
FireFox will work until June 30, 1995.
18
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Copyright notices.
FireFox, this documentation and the files belonging to
FireFox are Copyright 1993,1994 by Alexander Erne.
All the rights on FireFox, this documentation and the
files belonging to FireFox are worldwide protected by
the Dutch Law. Any violation of these rights will be
prosecuted according to the Dutch Law.
In this documentation I have revered to some other programs. I
also have used some Turbo Pascal units that hold specific rights.
Here is a list of these programs (listed in alphabetic order).
* BC-Share, a very good file-sharing unit is (C)1990 by
Mike Woltz of Buffalo Creek Software.
* Fido, the basic standards are (C)1986-1990 by Randy
Bush, Pacific Systems Group.
* Spitfire is (C)1987-1993 by Mike Woltz of Buffalo Creek
Software.
* Turbo Pascal version 6.0 is (C) 1983-1990 by Borland
International Inc.
Support.
Here are some places you can be sure to find the latest version
of FireFox, and where you can ask me questions about FireFox.
First of all my home-address:
Alexander Erne
Burg. de Kievietstraat 86
1111 GR Diemen, The Netherlands
You can also reach me on my BBS: BBS The Tower, phone# 3120-
6900028, FidoNet 2:2801/157, or leave me a message in the inter-
national SPITFIRE conference.
On these BBS' you can also find the latest version of FireFox:
Animal BBS - 3120-6975558, FidoNet 2:2801/156
WindowsBBS - 3120-6230966 (23.00 - 06.30 cet)
Buffalo Creek's BBS - 1-515-225-8496
Of course will every new version of FireFox also be placed on the
Spitfire Filebone.
19
FireFox 0.07-34
Copyright 1993, 1994
Alexander Erne
All rights reserved
Credits.
Now it is time for me to thank some great people without whom I
would not be able to write FireFox.
Francien van Lent. My girl-friend. Thanks for all the support you
gave me while I was writing FireFox. You surely are a great
support to me.
Henk van de Goor and Maurice Elfert. I have already mentioned
these two great guys in the introduction of this document. I
would like to thank them both for testing FireFox. They showed
their patience. Even when I messed up their entire message base
in the first releases of FireFox...
Mike Woltz. For giving us all this great BBS program called
Spitfire. Surely without him I would not even start writing
FireFox <G>.
Further more I would like to thank you for giving FireFox a try
on your system. I hope FireFox will fill in all the needs you
have when handling Fido-mail...
20
