home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
SF35_1.ZIP
/
README.NOW
< prev
next >
Wrap
Text File
|
1994-07-15
|
6KB
|
128 lines
July 15, 1994
Greetings:
We at Buffalo Creek Software would like to take this opportunity
to thank you for your support and promotion of SPITFIRE.
START *** CONVERTING SHAREWARE SPITFIRE v3.5 TO A LICENSED COPY
---------------------------------------------------------------
First, copy the shareware SPITFIRE.EXE, SPITFIRE.OVR and SF35SN
package (SF35SN package is provided by Buffalo Creek Software to
licensed SPITFIRE Sysop who have selected the SPITFIRE v3.5
download/upgrade option) files into your SPITFIRE home directory.
Then execute <serial number>.BAT. You should see the below example
appear on your monitor:
╒═════════════════════════════════════════╕
│ SF35SN Version 1.0 │
│ Buffalo Creek Software │
│ Copyright (C) by Mike Woltz, 1994 │
└─────────────────────────────────────────┘
Success!
Thank you for your support of SPITFIRE!
This converts the shareware copy of SPITFIRE v3.5 into your licensed
copy of SPITFIRE v3.5.
END *** CONVERTING SHAREWARE SPITFIRE v3.5 TO A LICENSED COPY
-------------------------------------------------------------
In the event you are upgrading to SPITFIRE v3.5 from SPITFIRE v3.4,
then please follow the directions listed below.
Begin by placing SF34_35.EXE in each SPITFIRE HOME directory per
node and executing it. After running it in each of the SPITFIRE Home
directories it should be erased from the drive(s). Messages will appear
on the screen as SF34_35 works to update the necessary files to SPITFIRE
v3.5 format. This will allow you to follow the conversion process. To
better understand what is taking place during the conversion, the
required updates SF34_35 performs during the conversion process are
listed below:
1) Reads information from the old SFNODE.DAT file and
creates a new SFNODE.DAT compatible with SPITFIRE v3.5.
2) Updates the SFMCONF.DAT and sets the Message Entry
Security field to:
a) the same security as the Message Conference
Security, provided the conference is not configured
as read-only.
b) a security of 999, provided the conference is
configured as a read-only conference.
3) Removes all the ^E from all display files contained in
the directory configured as the SPITFIRE Display File
Path
4) Removes the <H>...Hurry Message Scan and <N>...Non-Stop
Message Scan from the SFMSG.MNU file.
*** NOTE *** If the BBS uses display files for the Message Menu,
the MSG<x>.BBS/CLR/RIP display screens will also need to be
modified by the Sysop so that these features no longer appear on
the display screen.
Once SF34_35 has finished the conversion process, you will need to:
1) Erase the SF34_35 conversion utility.
2) Copy SPITFIRE.EXE and SPITFIRE.OVR from the SPITFIRE
v3.5 distribution diskette so that it overwrites the
previous version system files.
3) Copy the SFCALLOG.DAT from the SPITFIRE v3.5 distribution
diskette so that it overwrites the existing SFCALLOG.DAT file.
The above steps are REQUIRED to convert from SFv3.4 to SFv3.5!!
Below is a list of optional steps you may wish to complete in order
to take advantage of the many new features available in SFv3.5:
To receive fax calls, use the ALT+M to configure the Fax
Connection Result Msg, Fax Answer String and Fax Initialization
string for your Fax Modem and create a SFFAX.BAT which will contain the
necessary commands for receiving the fax.
With the internal ZModem file transfer protocol, it is recommended
that ZModem be removed as an external protocol. This will require
modifying SFEXTDN.BBS and SFEXTUP.BBS in the directory of your
configured Display File Path. In addition, the appropriate
SFEXTUP<x>.BAT and/or SFEXTDN<x>.BAT should be deleted.
To use the expanded Subscription BBS support, configure the Expired
Security option and the Expired Warning option in SPITFIRE's ALT+Z
configuration window. Use your favorite text editor or screen
generating program to create the new SFSUBCHG.BBS/CLR/RIP and
SUBWARN.BBS/CLR/RIP display files and place them in the directory
configured as your Display File Path. Create or modify your
questionnaire files to use the new questionnaire file option, $<x>$ to
automatically adjust the caller's subscription date by <x> number of
days.
To take advantage of the expanded node chat features, create a RAM
drive (referring to the DOS documentation if needed) to be used as the
Node Chat Drive. Next, use ALT+Z configure the Node Chat Drive within
SPITFIRE.
Create a NUCALLER.* file which contains BBS information, BBS
subscription forms, BBS RIP Icons, etc. that you wish to make available
to new callers logging on your BBS.
Create any FA<x>.TXT files you may choose in order to take advantage
of the extended download drive/directory feature.
If your modem can interpret caller ID information and you wish this
information to be recorded by SPITFIRE in CALLERS.LOG, then you will
need to set the Number Of Rings in the SPITFIRE ASYNC configuration
window to at least 2 and you will have to properly configure your modem.
Thank you & ENJOY,
Ann Woltz