SPITFIRE Frequently Asked Questions — Part 3
Tony Jones of Southern Cross BBS in Tasmania compiled this collection as “Part Three of an ongoing SPITFIRE Frequently Asked Questions library.” It contains 39 messages exported from a SPITFIRE system on October 1, 1994, covering Lakota, SFNET, SHILOH, utilities, modems, doors and system configuration.
Download the original SF-FAQ3.ZIP↓Archival note: The package also contains
ARSENAL.95, an unrelated BBS file-list advertisement duplicated in other source packages. It remains untouched in the downloadable ZIP but is not presented as part of the FAQ transcript.
Preserved messages
The filenames and message text below are retained in the package’s preserved filename order. That order is not presented as the original conversation sequence.
MSG1.19 — LAKOTA v1.4!
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:57:08.
DATE..... : 09-20-94 09:58:00
TO....... : Ken Whiton
FROM..... : Eric Lofgren
SUBJECT.. : LAKOTA v1.4!
Quoting KEN WHITON to MIKE WOLTZ concerning LAKOTA v1.4!:
┌─┤KEN WHITON to MIKE WOLTZ├───────────────────────────────────────────────┐
│ │█
│ MW>> 2) LAKOTA now allows an operator (user) to ADD or DROP message │█
│ MW>> conferences from their message conference queue via an offlin│█
│ MW>> reader. │█
│ │█
│ Does this mean that the CONTROL.DAT file will now list all conferences│█
│available on the host BBS, instead of just those conferences the user has │█
│selected for download? │█
└──────────────────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Sure does and works very well also.
Eric
---
■ Apex v4 ■ It's not hard to meet expenses, they're everywhere.
■ Sea Spray BBS Wilmot, N.S. (902)-765-6867 300 - 14400
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Sailing Smoothly With SPITFIRE
* Origin: Sea Spray BBS * Node_ID: A0902000MSG11.20 — Guildlines!
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:17:24.
DATE..... : 09-27-94 20:03:00
TO....... : All
FROM..... : Karl Ziegenmeyer
SUBJECT.. : Guildlines!
* Forwarded by KARL ZIEGENMEYER from the @SFNET conference.
* Original from MIKE WOLTZ to ZIGGY on 09-25-94.
Hello SPITFIRE/SFNET Sysop ...
First, if the content of this message is not applicable to you then
please accept my apology ... I am simply sending this message to all
SPITFIRE Sysops who participate in SFNET in an attempt to get needed
information out. It is 10:50 and I need to get the SFNET
International Hub up so this will be quick.
I had really hoped that mature, common sense would prevail and that
this message would not be necessary. Again, if this is not
applicable to you then please disregard this message.
SFNET DIRECTIVE:
Swear words and messages (including taglines) with a sexual
connotation are not allowed within SFNET. Both of these issues are
offensive to people and therefore are unacceptable conduct. We must
show a mature respect for all SFNET participants. Thank you so very
much for your understanding and cooperation in these matters.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * He died for me ... I will live for Him!
===
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001
---
■ SPEED 1.30 [NR] ■
* LAKOTA v1.4ß
* SHILOH v1.0ßf * "Ziggy's" Lapeer, Mi.
* Origin: "Ziggy's" * Node_ID: A0810000MSG15.19 — Re: SFEMB 0.41 Released
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:01:22.
DATE..... : 09-28-94 23:03:00
TO....... : Della Moore
FROM..... : Dave Turley
SUBJECT.. : Re: SFEMB 0.41 Released
╒═╡ƒrom: Della Moore╞════════════════════════╡τime: 09-23-94 17:26:00╞═╗
│ Will this version work with 3.4:)??? ║
│ ║
│ Della ║
└──────────────────────────────────────────────────────────────────────╜
It ought to...only major differences on your end is the new definition of
what a read-only conference is. SF3.4 & 3.5 differ on it. If you don't
use Read-only conferences, there shouldn't be a problem...
Later,
Dave
---
* SFEMB 0.41 [TS80001]
* SHILOH v1.0ßf * Home of SFATM!
* Origin: Sanctuary BBS * Node_ID: A0801000MSG17.19 — Re: SFEMB v0.31
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:01:52.
DATE..... : 09-28-94 23:09:00
TO....... : Steve Mcgraw
FROM..... : Dave Turley
SUBJECT.. : Re: SFEMB v0.31
╒═╡ƒrom: Steve Mcgraw╞═══════════════════════╡τime: 09-23-94 20:02:00╞═╗
│First, I can't get LAKOTA to run from the door section. It well ║
│could be somewhere in my setup files, but darn if I can figure it ║
│out. Any suggestions? ║
└──────────────────────────────────────────────────────────────────────╜
Don't know if your using it or not, but to load external doors you have to
be using the EMB.BAT file supplied. Does Lakota just not want to run or
what? What version of Lakota are you using?
╒═╡ƒrom: Steve Mcgraw╞═══════════════════════╡τime: 09-23-94 20:02:00╞═╗
│Second, I allow my users to choose between using the default Spitfire ║
│message system, or use SFEMB. I've noticed that messages that have ║
│been read and deleted using SFEMB still show as new messages waiting ║
│in the Spitfire default system. And the messages can't be re-deleted ║
│within Spitfire. It's not a big problem, but since I started using ║
│SFEMB, Spitfire shows my unread messages as up to 87. I pack my ║
│message base once weekly. Does that make a difference? ║
└──────────────────────────────────────────────────────────────────────╜
I'm not sure, didn't realize that that was a problem. Anybody out there
know if Mike Woltz uses something besieds the <Deleted> byte in the .PTR
file to show that a message is deleted?
╒═╡ƒrom: Steve Mcgraw╞═══════════════════════╡τime: 09-23-94 20:02:00╞═╗
│Third, a request. Would it be possible in future versions to allow ║
│inserting a text file anywhere within a message, as in Spitfire? ║
│There are many occasions where I would want to continue a message ║
│after a text file. ║
└──────────────────────────────────────────────────────────────────────╜
We'll look into it as the message editor gets more advanced.
╒═╡ƒrom: Steve Mcgraw╞═══════════════════════╡τime: 09-23-94 20:02:00╞═╗
│All the above being said, I want to repeat how much I enjoy SFEMB and ║
│would continue to use it, as is. ║
└──────────────────────────────────────────────────────────────────────╜
Thanks! Good to hear it...
Later,
Dave
---
* SFEMB 0.41 [TS80001]
* SHILOH v1.0ßf * Home of SFATM!
* Origin: Sanctuary BBS * Node_ID: A0801000MSG20.18 — LAKOTA 1.4
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:12:59.
DATE..... : 09-26-94 18:52:00
TO....... : Jacque Shipley
FROM..... : Neil Toland
SUBJECT.. : LAKOTA 1.4
Hello Jacque,
JACQUE SHIPLEY said to NEIL TOLAND on 09-25-94
JS> Lakota v1.4 is still in beta testing...
I thought this was the case, just wanted to be certain.
JS> Appreciated you sharing your previous message regarding all
JS> the help you have received on the net from the other Sysops.
Sure makes things easier for newbies like me. <g>
JS> There are some questions which will have to be addressed to
JS> Mike..
With the folks involved in SFNET, I really think that in most cases
others will be able to supply solutions. Especially the questions
from new sysops like me.
JS> but there are many, many more which many of us ole
JS> veterans can assist with,
Why do I have the feeling that someone else is going to quote the
above line back to you?
Thank You, Jacque and Take Care.
* MicroQwk #150000 * Ignorance is not bliss. Handy excuse though.
---
* LAKOTA v1.3
* SHILOH v1.0ßf * Wapello,Ia.(319)523-4309*Node_id:A0319004
* Origin: Wapello's Only Little BBS! * Node_ID: A0319000MSG20.19 — LAKOTA v1.4
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:02:25.
DATE..... : 09-28-94 08:58:00
TO....... : Mike Woltz
FROM..... : Peter Welch
SUBJECT.. : LAKOTA v1.4
MW> Please download the newest copy of LAKOTA v1.4 and completely test
MW> it. Hopefully it is ready for release ... I will wait for your test
MW> reports ... Thank you for your help.
Did d/l the latest Mike and it works perfectly here. Nice addition giving the
caller the option to log off after transfer and it works like a charm. GREAT
work Mike, I now turn my callers towards LAKOTA more than Jetmail (sorry DJ).
Peter...
---
* SPITFIRE v3.5
* SHILOH v1.0ßf * Flying the Spitfire Flag Since 1989.
* Origin: Tyler's Treehouse BBS * Node_ID: A0604000MSG21.18 — Three Day Waiting Period
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:13:36.
DATE..... : 09-26-94 19:13:00
TO....... : Bob St. Cyr
FROM..... : Neil Toland
SUBJECT.. : Three Day Waiting Period
BOB ST. CYR said to NEIL TOLAND on 09-25-94
BC> | OK if I butt in a minute?
BC>
BC> Why not....has it ever stopped you before? <VBG>.
Now, now, Bob, I was just trying to be polite.... <g>
BC> Thank you, Neil, for letting us know that you are able
BC> to get the help needed.
No question about it....all a fella has to do around here is ask.
I'm certain that sometimes, to the ol'hands, the questions seem
pretty foolish. What may seem painfully simple to experienced
users may be a huge problem for new users (me).
I'm hopeful that you ALL will continue to be as helpful as you've
been in the past.
In other words, just mutter to yourself "well that idiot" instead of
typing it. <VBG>
BC> And what the heck, conflicting answers can still
BC> be easily resolved.....with the old coin flip!
Seems that when I have had different solutions to a problem, each
solution has worked!
"More than one way to skin a cat."
BC> Do you think that we could carry this too far.....and that Mike would
BC> start feeling like the Maytag repairman?
Best wait three days to ask him <g>.
I've a hunch that he would rather write code than write messages.
Of course if he needs a break he can always go to General Chat
and bust right in! :-)
Thanks for your thoughts Bob. See ya later
* MicroQwk #150000 * Ignorance is not bliss. Handy excuse though.
---
* LAKOTA v1.3
* SHILOH v1.0ßf * Wapello,Ia.(319)523-4309*Node_id:A0319004
* Origin: Wapello's Only Little BBS! * Node_ID: A0319000MSG23.19 — Re: Message on your board
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:04:32.
DATE..... : 09-29-94 07:22:00
TO....... : Dave Turley
FROM..... : Mike Woltz
SUBJECT.. : Re: Message on your board
Hello Dave ...
DAVE TURLEY said to SYSOP on 09-28-94
DT> I noticed this the other day (fidonet messages crossed over) is
DT> this done with the concent of SFNET officials? If one wishes to
DT> cross other nets over does one have to get permision first?
Cross-linking (if that is the correct term) does NOT get the consent
of SFNET ... Quite the opposite ... We spent quite a bit of time and
money helping Sysops get these kind of messes straightened out ...
Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG24.19 — LAKOTA v1.4!
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:05:00.
DATE..... : 09-29-94 21:27:00
TO....... : Jim Lambert
FROM..... : Mike Woltz
SUBJECT.. : LAKOTA v1.4!
Hello Jim ...
JIM LAMBERT said to SYSOP on 09-10-94
JL> One other thing... I noticed what may simply be an undocumented
JL> feature. When altering pointers on all conferences and queued
JL> conferences, if you just hit enter rather than a number it will go
JL> back to the Lakota menu after 10 conferences. If you hit a number
JL> instead of the enter key, it will keep going to the end of the
JL> conferences. I just wanted to make sure you knew about this.
JL> Take care.
Jim, I know what you are talking about ... I have experienced the
same thing. I have tried my best to duplicate this problem with
LAKOTA v1.4 and I can't make it happen ... I will ask you to get the
newest copy of LAKOTA v1.4 and see if you can get this problem to
occur ... I will wait to hear from you ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG25.18 — SF Subscription Dates
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:15:09.
DATE..... : 09-26-94 10:38:00
TO....... : Brian Tafoya
FROM..... : Allan Miner
SUBJECT.. : SF Subscription Dates
BT> ══ quoting ALLAN MINER ═══
╒════ to MIKE WOLTZ ═══ ƒrom a message on 09-22-94 " ═════
│ I just received my v3.5 Registration and I began to impliment the
BT> subscriptio
│ date feature in the caller's database, but I haven't yet found a way to
BT> chang
│ a date back to N/A. So far, I have been able to set the date so far ahead
│ that
│ the notice won't come up for 15 years, but I would like to be able to change
│ specific callers back to a non-subscription account. Any help you can give
│ would be greatly appreciated.
╘════════════════════════════════════════ " end of quote ════
BT> Mike has already replied I'm sure, but all you do is enter 01-01-80.
BT> This will reset the date of expiration.
Okay, It werks!! Thanks for the help.
>-AM->
---
* SPITFIRE v3.5
* SHILOH v1.0 * Sysop want's to chat, hit ALT-H NOW!!!
* Origin: The EHS Information Exchange BBS * Node_ID: A0702002MSG25.19 — New Spitfire Backup Utili
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:05:51.
DATE..... : 09-28-94 18:11:00
TO....... : All
FROM..... : Jim Lambert
SUBJECT.. : New Spitfire Backup Utili
I recently came across a new Spitfire Utility at Buffalo Creek that
caught my eye. SF35Back is a utility that you can run manually or as an
event that will backup your critical Spitfire files to a floppy. The
author, Tony Jones, lives in Tasmania, Australia. He has given me
excellent support, and even called my BBS from Australia to help me.
I have agreed to be his registration point for the United States.
Registration is only $5 U.S. This is well worth taking a look.
It is available as SF35BACK.ZIP at Computer Works (205) 671-0092.
╔═══════>SF35BACK v2.2<════════════╗
║ SPITFIRE v3.5 BACKUP/RESTORATION ║
║ Uses PKZIP. Can be run as Event, ║
║ or Manually. ║
║ International Date Format and ║
║ Path Configurable. "Audio Alert" ║
║ for Backup/Restoration Complete. ║
║ Reports Viewer. ║
║ Written by Spitfire SysOp ║
║ Southern Cross BBS ║
║ Tasmania, Australia ║
║ Ph +61-03-432302 ║
╚══════════════════════════════════╝
---
■ QMPro 1.51 ■ Hollow chocolate has no calories.
* LAKOTA v1.4ß
* SHILOH v1.0ßf * SFNet, CircuitNet, Genesis Daily News, V.Everything
* Origin: Computer Works * Node_ID: A0205003MSG28.18 — Pre-Init. Failure
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:16:14.
DATE..... : 09-27-94 19:45:00
TO....... : Barry Hauser
FROM..... : Colin Royal
SUBJECT.. : Pre-Init. Failure
On 09-25-94 19:53, Barry Hauser said to All about Pre-Init. Failure.
Hi Barry,
BH> modem type: Zoom 14.4 v.32bis external
BH> String I am using:AT&F2&C1&D2S0=0S2=1S95=3X4
Try this init string: ATS0=0S2=1Q0E0V1M0H0W2S95=47&C1&D2&S1X4 (^M)
^^
Leave "^M" off to start, if
it still fails then add it.
I run a Zoom 14.4 and the book I have tends to lead me to belive
it'll work for yours also, since it has the external modem listed it in
too. Also I have saved this coonfiguration to both profiles in NVRAM and
use only "ATZ0^M" for my initialization string which forces the profile
0 to be loaded.
BH> Where to I get corrected SF35-1? I understood that it was on BC, but
BH> went last night (9/24) and all I could find was 7/15/94 copy.
SF 3.5 will have the date of 07/15/95 on all copies and bug fixes
until the next upgrade. This is due to the release date for SF 3.5 is
07/15/94. You have the necessary copy you need.
BH> I feel that (hopefully) these are minor problems that I have not set
BH> up right, but I've gone thru the docs and can't figure the problem out!
The above should help with you modem. If not Hollar and I'll did
farther from this end. I am glad to help.
Colin Royal
Gamers Paradise BBS
SD SFNet HUB A0605000
605-353-1309
... Documentation - The worst part of programming.
___ Blue Wave/QWK v2.12
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Running SpitFire 3.5 and PROUD OF IT!!
* Origin: Gamer's Paradise BBS * Node_ID: A0605000MSG3.24 — FROM/TO SYSOPS
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:19:34.
DATE..... : 09-28-94 07:36:00
TO....... : Louann Alger
FROM..... : Bob St. Cyr
SUBJECT.. : FROM/TO SYSOPS
| If you see a error code of 7, then look in the shiloh.doc. It
| gives all the error codes in there and check those items.
LouAnn....an EXITCODE=7 is a perfectly normal exit code when your node
had no messages to upload. Their SHILOEXP is going to prepare a .REP
packet irrespective of whether there are messages to be uploaded or not.
When your Hub runs SHILOIMP and finds no messages it returns the
EXITCODE=7.
This is covered in the Shiloh docs but you may have missed it in the
reading, it's under the part that says "SHILOIMP uses the following
exit codes:" The only two that have ever appeared to me are the 0 and
the 7.
* RM 1.3 00370 * SF350078 - A SPITFIRE pioneer!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * The Software Exchange, Carlisle, Pa, 717-243-9620 (28.8k)
* Origin: The Software Exchange * Node_ID: A0717000MSG35.18 — Sorry
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:18:19.
DATE..... : 09-28-94 07:14:00
TO....... : Tom Lacey
FROM..... : Mike Woltz
SUBJECT.. : Sorry
Hello Tom ...
TOM LACEY said to SYSOP on 09-26-94
TL> Just wanted to check in with you and let you know the new Lakota
TL> seems to be working just fine on my BBS, tried to get on your bbs
TL> yesterday...what a busy BBS..)
Thank you for your report, Tom ... Yup, Buffalo Creek's BBS normally
stays pretty busy ... I would gladly add additional nodes but more
nodes would mean more messages ... I am doing everything I can to
keep up with answering messages now and I just don't to be able to
get caught up.
TL> Everything is working fine except for the goodbye feature, is
TL> there a special way I have to configure that?
Tom, I believe that if you had the S2 register in your modem set to 1
(S2=1) then the <G>oodbye feature would work just fine (it should)
... However, I have decided against fighting that battle and I have taken
the <G>oodbye off the LAKOTA Main Menu ... I have now added an 'auto
log off' feature (pretty nice I think) ... You will want to download
the newest copy of LAKOTA and test it ... I will wait for your report
... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG35.19 — Re: LAKOTA v1.4
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:12:47.
DATE..... : 09-30-94 07:43:00
TO....... : Ken Kirkley
FROM..... : Mike Woltz
SUBJECT.. : Re: LAKOTA v1.4
Hello Ken ...
KEN KIRKLEY said to SYSOP on 09-28-94
KK> I am using Lakota of release 9/26/94 at 21:45. The auto log-off is
KK> functioning very nicely this go round. The ADD/DROP feature is
KK> also working as it is supposed to. Only one thing I have
KK> encountered....if you select auto log-off after an UPload, Lakota
KK> returns you to its menu screen instead of logging off. I tested
KK> this on my system and Ross's system. Did the same on both. Don't
KK> know if you meant to give that option on an upload or not?
KK> Otherwise it seems to be working quite well. I will be sure to let
KK> you know if anything else comes up. Let me express a big THANK
KK> YOU for listening to my suggestion. It is much appreciated.
Ken, I think that the copy of LAKOTA which you are using wasn't
completed. Please download the current copy and give it a try ... I
am hopefully that the current copy is a finished product ... I will
wait to hear from you ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG36.18 — SF in Path
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:18:35.
DATE..... : 09-28-94 07:19:00
TO....... : Colin Royal
FROM..... : Mike Woltz
SUBJECT.. : SF in Path
Hello Colin ...
COLIN ROYAL said to SYSOP on 09-27-94
CR> Yep, I am one of those who you don't understand about. For me
CR> the biggest reason for having SF in my path is due to some
CR> utilities I use for the BBS primarily, I also use in my manua disk
CR> maintenance. I find it less of a hassle when backing up the baord
CR> by having everything that it requires under the SF directory.
CR> Saves from remembering where to go to get the necessary files. May
CR> sound kinda lazy, but I have a hard enough time remembering wher I
CR> laid my head. <ETEG> Right now, not including file areas, my
CR> board alone is 43 Meg.
It causes no harm to have the SPITFIRE home directory included in the
path. However, SPITFIRE (or any other Buffalo Creek Software
product) does not require it ...
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG37.18 — "Dump"
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:18:53.
DATE..... : 09-28-94 08:12:00
TO....... : Bob Alger
FROM..... : Mike Woltz
SUBJECT.. : "Dump"
Hello Bob ...
BOB ALGER said to SYSOP on 09-27-94
BA> Apologies on the major "message reply dump"
BA> this morning. I believe I have the problem ironed out (famous
BA> last words)(G). It all started yesterday morning about 25 minutes
BA> before I was due at work. Suddenly my SFUSERS.DAT became
BA> "pregnant" - to the tune of just over 21 megs !!!
Bob, are you operating SPITFIRE under a front end program? If you
are then I believe that I can tell you what happened to your
SFUSERS.DAT file. I would guess that you are operating SFCHKUP using
the %1 command line parameter. You see, the %1 command line
parameter is ONLY to be used when SFCHKUP is executed within
SFINIT.BAT and when SFINIT.BAT is executed by SPITFIRE. The %1
represents the record number of the last caller when SFINIT.BAT is
executed by SPITFIRE thus making it easy for SFCHKUP to know who the
last caller was ... However, %1 represents something totally
different when SFCHKUP is executed in some other way than
SPITFIRE/SFINIT ... For example, %1 represents the baud rate of the
caller in a batch file executed by a front end program ... In such
case, if the caller was logged on at 14400 then SFCHKUP would think
the record number of the last caller is 14400 (a serious problem). I
hope that you understand what I am trying to explain ...
In the event the above 'guess' is accurate, then you are not
operating the newest copy of SFCHKUP because I have added protection
(in the newest version) against the above described potention
mistake.
BA> I reinstalled an older .dat file and began evaluating it,
BA> adding users that I could remember (including A0000000, in fact).
BA> Anyway, that's the situation, and hopefully, it's back to "smooth
BA> sailing" around here, at least for awhile.
Ah ha ... I understand why the duplicates ... No problem, Bob ...
SFDUPCHK does a pretty good job of catching duplicate messages.
BA> (all this while we're trying to get another 813 node up and
BA> running!!) (little
GREAT ... I really appreciate your promotion of and participation in
SFNET. I often think of the Alger family when I think of the
expected conduct within SFNET ... I guess that is because I want
SFNET to be a family style mail system.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG38.18 — ->A0515001
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:19:18.
DATE..... : 09-28-94 08:26:00
TO....... : Anthony Trollope
FROM..... : Mike Woltz
SUBJECT.. : ->A0515001
Hello Anthony ...
ANTHONY TROLLOPE said to SYSOP on 09-26-94
AT> I understand. You do receive a fair number of messages about
AT> the same questions don't you.
Anthony, I have been answering the same questions over and over for
6-7 years.
AT> I will miss the feature here but nightmares are to be avoided.
I don't think that you will miss the feature because it has been
replaced with a much better feature (auto log off) ...
AT> I am sure that you are right. I will try it again here..and I
AT> am sure that it will work as every thing else you have written
AT> has worked well on my system.
Anthony, you have to be using a revised copy of SPITFIRE v3.5 in
order for the LAKOTA ADD/DROP feature to work ...
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG39.18 — ->A0515001
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:19:37.
DATE..... : 09-28-94 08:29:00
TO....... : Anthony Trollope
FROM..... : Mike Woltz
SUBJECT.. : ->A0515001
Hello Anthony ...
ANTHONY TROLLOPE said to SYSOP on 09-26-94
BTW, I notice that the subject of your message is ->A0515001. I
don't know if you were attempting to route your message, however,
that routing style does not belong in the subject of the message ...
Rather, it needs to be the absolute first bytes a the message ...
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG4.18 — SHILOH
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:06:11.
DATE..... : 09-29-94 08:36:00
TO....... : Mike Woltz
FROM..... : Wizard
SUBJECT.. : SHILOH
Hi Mike
MW> Franz, the SHILOH error/exit levels are explained in the SHILOH
MW> documentation. In fact, I have always been kind of proud of those
MW> explanations (smiling).
Hmmmmm....when in doubt check the docs....hmmmmm....you're right....Sorry to
waste your time! Thanks. Next time I'll look before I engage my fingers! <BG>
Franz
---
* SPITFIRE v3.5
* SHILOH v1.0ßf * Olympic City of Sydney - Australia
* Origin: Wizard BBS * Node_ID: I0610000MSG40.18 — BBS
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:19:55.
DATE..... : 09-28-94 08:59:00
TO....... : Michael Trimble
FROM..... : Mike Woltz
SUBJECT.. : BBS
Hello Michael ...
MICHAEL TRIMBLE said to SYSOP on 09-26-94
MT> Uh, Mike, I am getting kinda sick of only having 5 file/msg/areas
MT> on my UNREGISTERED TriBBS. Yes, I'm cheap I guess, but I'm 13 and
Michael, are you telling me that TriBBS is crippleware rather than
shareware?
MT> don't have a real job yet. I am considering running Spitfire
MT> again. Do you know of any new Intel High-Speed modem stuff that
MT> would help me? I tried the SPITFIRE.DOC Index, and the Intel.txt,
It becomes very difficult for me to offer support regarding your
modem because I don't have a copy of your modem's manual ... Thus,
please understand that the below information is only an educated
guess.
Baud Rate: 19200
Pre-Init String: ATZ^M
Init String: AT&FS0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M
Hardware Data Flow Control: Yes
MT> and neither worked. Also, I have a CD-ROM (2 actually) that I
MT> would like to setup with Spitfire. Would I have to use SFROM?
No, you do not have use an external program to use a CD-Rom with
SPITFIRE. SPITFIRE handles a CD-Rom quite nicely.
MT> it doesn't answer, it does little good. I might want to be in
MT> SFnET, does that require FrontDoor? Also, is it free? Thanx for
MT> your time...
SFNET does not require the use of a front end program ...
Additionally, SFNET is (in the Buffalo Creek Software tradition of
treating people right) FREE ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
╔══[ The Sad Cafe ]════════════════╗
║ We thought we could change this ╟─┐
║ world with words like love and ║ │
║ freedom. ║ │
╚═╤════════════════════════════════╝ │
└──────────────────────────────────┘
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A05MSG41.18 — IDEA
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:20:30.
DATE..... : 09-28-94 14:22:00
TO....... : Dave Bannister
FROM..... : Mike Woltz
SUBJECT.. : IDEA
Hello Dave ...
DAVE BANNISTER said to SYSOP on 09-12-94
DB> Heres a simple request for the new spitfire..
DB>
DB> I noticed that when you read the bulletins and the MORE Prompt
DB> shows up and you hit 'S' for stop it stops all the bulletins...
DB>
DB> Can you make it so you can stop all the bulletins and also make
DB> it so you can stop just that one and continue with the others
DB> ones.
DB>
DB> I have hit 'S' too many times forgetting that it aborts all the
DB> bulletins..
DB>
DB> Thanks Mike! please think about this..
Dave, I guess that I didn't realize that SPITFIRE works the way that
you describe ... I have made a change ... If you want to have a look
to see if the change meets with your satisfaction, then the copy of
SPITFIRE within SF35-1.ZIP (on Buffalo Creek's BBS) contains the
change ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its f---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG42.18 — SF
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:21:03.
DATE..... : 09-28-94 14:29:00
TO....... : Colin Royal
FROM..... : Mike Woltz
SUBJECT.. : SF
Hello Colin ...
COLIN ROYAL said to SYSOP on 09-26-94
CR> Also, I remember something you said about the choice of ANSI
CR> or not when logging on. I agree with the option at the time of
CR> logon and support it. I would like to suggest maybe leaving it as
CR> is with a minor change(i think it would be) as to adding a user
CR> configurable option of setting ansi on for every call from the
CR> Your Statistics off the main menu. In effect if SF reads a
CR> particular code then the user would have ANSI, RIP or ASCII hen
CR> they log on, with a default choice as having a choice. If the
CR> caller is set to RIP then if RIP is not detected, default to a
CR> choice. (the caller may have cahnged terminal programs) Just a
CR> thought.
Colin, I personally cannot think of anything negative about requiring
a caller to make a choice of the type of graphics they desire each
time they log on ... I can think of a number of negative aspects if
your suggestion was implemented ... I receive your suggestion every
so often and I personally don't agree with the suggestion ... Are we
callers too lazy to 'press a key' to select our graphics option? I
suspect that other software must be written to automatically give
ANSI when an ANSI terminal is detected and RIP when a RIP terminal is
detected ... Frankly, I would not call a board back if a certain type
of graphics was forced on my just because the terminal program
supported the graphics ....
CR> Also, (Yep another thought. <BG>) Would a file area queue be a
CR> good asset to SF. For example, a caller only wants to access 5 of
CR> 50 file areas that are of interest to him/her. He/she could set
CR> the queue to include only those areas as with the message queue.
Thank you for your suggestion ... It will be considered ...
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG43.18 — Shiloh
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:21:25.
DATE..... : 09-28-94 15:51:00
TO....... : John Krone
FROM..... : Mike Woltz
SUBJECT.. : Shiloh
Hello John ...
JOHN KRONE said to SYSOP on 09-28-94
JK> Right, it flashes a set of numbers over and over quickly, it's
JK> just 1-7's then a few 1-9's. Almost as if it's reading all the
Yup, my design is causing the slowness ... I simply need to re-write
SHILOIMP ... Thank you for your help ...
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG44.18 — Gsz
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:22:06.
DATE..... : 09-28-94 15:53:00
TO....... : Dan Shaffer
FROM..... : Mike Woltz
SUBJECT.. : Gsz
Hello Dan ...
DAN SHAFFER said to SYSOP on 09-28-94
DS> One thing I forgot to mention was that the terminal program I use
DS> to test my rip screens with works fine for rips on your BBS. Also,
DS> All my welcome,goodbye,bulletin screens show up great. The only
DS> problem is with my menus and the buttons in them.
DS> Any Ideas?
Dan, I already gave you my ideas ...
If the RIP display files created by my MKSFMENU program don't work
for you, then please don't use MKSFMENU. I can tell you that the
files which you are able to view on Buffalo Creek's BBS were created
by MKSFMENU ... It works for me and it works for hundreds of other
people ... I am not trying to be smart (honestly) when I tell you
that if it doesn't work for you then don't use it ...
In the event that your WELCOME, GOODBYE, BULLETINS etc work fine,
then you should use the same program which you used to create those
file to create your RIP menus ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG46.18 — SF35-1.ZIP Packet
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:22:45.
DATE..... : 09-27-94 14:30:00
TO....... : Bob St. Cyr
FROM..... : Jim Lambert
SUBJECT.. : SF35-1.ZIP Packet
BSC>This is a new network, Bob. Compare it to a freshly planted garden in
>the Spring. The seeds that were planted for SFNET have now sprung thru
>the soil and the plants look healthy and will grow to be strong and
>sturdy! But along with those plants, Bob, as in any garden, there are
>weeds and growth that will rob the plants of some of the nourishment
>they need! Each of us as Spitfire sysops have to choose, are we
>to be one of the plants or one of the weeds? I vote for being part of
>the plant.....and hope that Bob Chalmers will join me.
Well put, Bob. Very well put!
Jim...
---
■ QMPro 1.51 ■ I feel more like I do now than I did before I started
* LAKOTA v1.4ß
* SHILOH v1.0ßf * SFNet, CircuitNet, Genesis Daily News, V.Everything
* Origin: Computer Works * Node_ID: A0205003MSG48.18 — Pre-Init. Failure
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:23:09.
DATE..... : 09-28-94 07:55:00
TO....... : Barry Hauser
FROM..... : Bob St. Cyr
SUBJECT.. : Pre-Init. Failure
| intermitent pre-init string failure
| went it does reset, it echos the init string anywhere from 2 to 8 times
| with 3 smiley faces after them, then it says "OK" Ready.....etc,etc.
Try preceding your initialization with about three delay characters,
like this ~~~.
| Where to I get corrected SF35-1? I understood that it was on BC, but
| went last night (9/24) and all I could find was 7/15/94 copy.
That's the one you want. The file is retaining it's original release
date.
* RM 1.3 00370 *
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * The Software Exchange, Carlisle, Pa, 717-243-9620 (28.8k)
* Origin: The Software Exchange * Node_ID: A0717000MSG49.18 — SHILOH EXIT CODES
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:23:31.
DATE..... : 09-28-94 07:30:00
TO....... : Walt Young
FROM..... : Bob St. Cyr
SUBJECT.. : SHILOH EXIT CODES
| Other than that...maybe with some more detail I could help more.
| I am having a similar problem with my node, keep getting error 7.
| But it was working fine the other day so don't know what
| changed.
Walt....your node may not have messages to export to you every day.
The SHILOH docs state that "When SHILOIMP attempts to import a mail
packet that contains no messages, an exit code of 7 is returned."
You can confirm this by running through your HEYSYSOP.LOG and notice
that on those days when you did import mail from your node an exit
code of 0 was returned, otherwise it will be 7.
---
■ RM 1.3 00370 ■ SF350078 - A SPITFIRE pioneer!
* LAKOTA v1.4ß
* SHILOH v1.0ßf * The Software Exchange, Carlisle, Pa, 717-243-9620 (28.8k)
* Origin: The Software Exchange * Node_ID: A0717000MSG59.18 — Re: Pre-Init. Failure
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:40:57.
DATE..... : 09-28-94 06:36:00
TO....... : Barry Hauser
FROM..... : Nick Folino
SUBJECT.. : Re: Pre-Init. Failure
-=> Quoting Barry Hauser to All <=-
BH> here are some of the problems I am having:
BH> intermitent pre-init string failure
BH> went it does reset, it echos the init string anywhere from 2 to 8
BH> times with 3 smiley faces after them, then it says "OK"
BH> Ready.....etc,etc.
I was having this problem and Mike set me SF09-94.ZIP it should be
available from BC......I talked with Mike and he says it's not really
a problem but more of an eyesore..........
BH> Occasionally it will drop callers right after the "Do you want ANSI?"
BH> I have gotten a couple of calls that will drop caller right away,then
BH> it will start to reset and then it show connect 1200??/75TX it pauses
BH> then shows NO CARRIER.
I've never seen this, but the update might help you out....
BH> On to another note, can anyone suggest a quality firm to buy shareware
BH> CD's from that are BBS ready??? If so, what is the average cost per
BH> CD? -!-
Chicago Computer Broker has some news CD's that are BBS ready, and come with
a book that contains file descriptions.......I don't think I paid over
$30/CD for their stuff.......
Also a lot of companies have Shareware CD's that are pretty good.....
NightOwl is an example
... Catch the Blue Wave!
___ Blue Wave/QWK v2.11
---
* LAKOTA v1.3
* SHILOH v1.0ßf * The Graphics Exchange BBS (717)628-4756
* Origin: The Graphics Exchange * Node_ID: A0717005MSG6.24 — FOSSIL DRIVER
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 22:20:23.
DATE..... : 09-29-94 10:59:00
TO....... : Walt Young
FROM..... : Della Moore
SUBJECT.. : FOSSIL DRIVER
WY> If you are using a 14.4 modem, Set all parameters in BNU, FD, and
WY> SFNODE to 19,200 and it should work smoothly. They should not
NOW I remember why I set everything to 19200<GRYNN>!!! Thanks:)!!
I knew that I must have had a reason sometime, but I was dipped if
I could remember what it was<LOL>!!!
Della
---
■ MegaMail 2.10 #613:Appreciate me now - and avoid the rush!
* SHILOH v1.0ßf * Have MOORE Fun!!
* Origin: Moore Fun BBS * Node_ID: A0417000MSG62.18 — Modem int
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:41:53.
DATE..... : 09-29-94 21:22:00
TO....... : Paul Rairdon
FROM..... : Mike Woltz
SUBJECT.. : Modem int
Hello Paul ...
PAUL RAIRDON said to SYSOP on 09-29-94
PR> Hello! i am sure this is a common problem people have with their
PR> bbs software but I am new to the sysop world and need help. i
PR> can't get my modem to int!!! Here is the deal. I am using a USR
PR> Sportster 14.4 fax/modem. i have tried all the int strings that
PR> come with the docs. i thought that my old 2400 internal modem was
PR> causeing problem so i put my 14.4 on com3 at IRQ5. Still no luck!
PR> Am not sure what to do next! Is there something I am missing.
PR> Serial port is set to 3 and the modem works fine on ather
PR> communications software. everyonce and a while when i enter a int
PR> string my modem makes a sound like it is connecting to a board.
PR> Please shed some light if possible.---Thank you
Paul, you have left some information out .. First, what version of
SPITFIRE are you working with? Second, what is happening (or not
happening) which causes you to think that you have a problem? In
other words, you left no details of the problem.
l will offer the below suggestions for your configuration ...
Baud Rate: 19200
Pre-Init String: ATZ^M
Init String: AT&FS0=1V1&H1&I0&R2&B1&N0&Y1B0Q0E0M0H0S2=1X4^M
Hardware Data Flow Control: Yes
I trust that this information will be helpful to you .. I will wait
to hear from you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG63.18 — Lakota/DSZ
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:42:34.
DATE..... : 09-28-94 20:38:00
TO....... : Richard Epling
FROM..... : Ross Cassell
SUBJECT.. : Lakota/DSZ
QUOTING Richard Epling who said this to Mike Woltz On 09-25-94 17:42:
RE> Hi, Mike. I have a question and a suggestion. Given how many
RE> questions and or problems that come up regarding LAKOTA and
RE> DSZ, and, given how well SFSENDIT works, I can't help
RE> wondering why you've stuck with having LAKOTA use DSZ to send
RE> the QWK packets it extracts. Why not have it use SPITFIRE's
RE> protocols like SFSENDIT does? Of course I have no real idea
Hi Richard,
SFSENDIT, writes to a field in the SFUSERS.DAT file that tells
Spitfire to send a file to the flagged user... So in essence the
Private File Waiting Code is within Spitfire explaining why the
available protocols are usable. SFSENDIT itself does not address the
COM port in anyway shape or form.. :)
RE> how much rewriting this would require, but with SFSENDIT being
RE> less than 6K, I can't see a change like this making much of a
RE> difference in the size of LAKOTA and it would eliminate any
RE> problems that come up due to the use of DSZ while at the same
RE> time providing more choices to the caller in terms of what
RE> protocol to use. With the addition of Zmodem to SPITFIRE, this
RE> makes sense to me and the Sysops could still offer DSZ as an
RE> external protocol if they want to so that choice could still
To do as you suggest would involve Mike building 'into' Spitfire
Lakota.. A few versions of Spitfire back, Spitfire used to contain
within itself Code to pack the message base and user files... To
make Spitfire faster, smaller and more memory efficient Mike took
that packing code out, thus the birth of SFPCKMSG & SFPCKUSR.. He
has separate modules written in Assembler to do those tasks, while
streamlining Spitfire. ( Lakota is also written in Assembler )
Now lets look back 8 months or more, Lakota is evolving, The version
we are testing now, the user can reset his/her queue offline via a
ADD/DROP function, Routing supported.. There is a Offline Mail
reader that works in close tandom with Lakota called Microqwk.
LAkota is fast, it consumes less than 25k and can hang with the big
boyz :)
Now its alot easier for Lakota to be a separate module from
Spitfire, for this reason:
If Mike incorporated Lakota into Spitfire, and for whatever reason
had to or wanted to make a revision to it, would entail releasing a
whole new SPITFIRE. That in itself is a upgrade nightmare..
Its easier to revise a module...
Besides, IMO, I like how Lakota works, aside from having it as the
'L' command on my message menu, I also can plug it in anywhere on my
system I desire, where a valid SFMAIN,SFMESS,SFFILE & SFDOORS.DAT
file is created which is what I do.
Best Regards
-=*)Ross(*=-
... "Incontinence Hotline, can you hold, please?"
___ Blue Wave/QWK v2.12
---
* LAKOTA v1.4ß
* SHILOH v1.0ßf * South Carolina's SFNET AreaCodeHub
* Origin: The Dark Corner BBS * Node_ID: A0803000MSG67.18 — Re: BBS
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:44:56.
DATE..... : 09-29-94 01:21:00
TO....... : Michael Trimble
FROM..... : Dave Turley
SUBJECT.. : Re: BBS
╒═╡ƒrom: Mike Woltz╞═════════════════════════╡τime: 09-28-94 08:59:00╞═╗
│Baud Rate: 19200 ║
│Pre-Init String: ATZ^M ║
│Init String: AT&FS0=0V1&C1&D2Q0E0H0M0W2S95=3S2=1X4^M ║
│Hardware Data Flow Control: Yes ║
└──────────────────────────────────────────────────────────────────────╜
Michael,
I just installed an Intel 144 Fax Modem and the factory pretty much are
already what you need for using locked baud rates, the init string could
probably be simplified to the following:
AT&FS0=0S2=1X4M0^M
Later,
Dave
---
* SFEMB 0.41 [TS80001] | Sanctuary BBS: Home of SFATM & SFEMB
* SHILOH v1.0ßf * Home of SFATM!
* Origin: Sanctuary BBS * Node_ID: A0801000MSG7.18 — SF Subscription Dates
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:07:14.
DATE..... : 09-26-94 11:11:00
TO....... : Allan Miner
FROM..... : Jim Lambert
SUBJECT.. : SF Subscription Dates
AM>I just received my v3.5 Registration and I began to impliment the
>subscription date feature in the caller's database, but I haven't
>yet found a way to change a date back to N/A.
Hi Allan. In an effort to help save Mike's time, you may want to
address messages like this to ALL rather than to Mike. The answer to
your question is to make the date 01-01-80. N/A will then appear.
Jim...
---
■ QMPro 1.51 ■ Oh, Lord, give me patience!...and please hurry!
* LAKOTA v1.4ß
* SHILOH v1.0ßf * SFNet, CircuitNet, Genesis Daily News, V.Everything
* Origin: Computer Works * Node_ID: A0205003MSG72.18 — Docs
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:47:14.
DATE..... : 09-29-94 08:41:00
TO....... : Jacque Shipley
FROM..... : Eric Lofgren
SUBJECT.. : Docs
Quoting KARL ZIEGENMEYER to JACQUE SHIPLEY concerning BBS Help:
┌─┤KARL ZIEGENMEYER to JACQUE SHIPLEY├────────┐
│ │█
│ > Ouch! My docs aren't that bad are they?│█
│ > │█
└─────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Well Jacque I can say I use them frequently. Since I d/l'd the latest
copy of SPITFIRE I did not get the manual so I printed it out and put
the pages in document protectors and into a large binder. I then
proceded to take a non-permanent ohp marker and marked alot of the new
things that I wanted to do on my BBS re subscriptions and such as well
as other things I refer to often. You should see it now. Already purple
pen everywhere. Time to get out the kleenex and start wiping it down
again. Thanks for the well written docs.
Eric
---
■ Apex v4 ■ What do you read ? GODISNOWHERE
■ Sea Spray BBS Wilmot, N.S. (902)-765-6867 300 - 14400
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Sailing Smoothly With SPITFIRE
* Origin: Sea Spray BBS * Node_ID: A0902000MSG74.18 — LAKOTA 1.4
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:52:08.
DATE..... : 09-29-94 11:38:00
TO....... : Neil Toland
FROM..... : Eric Lofgren
SUBJECT.. : LAKOTA 1.4
Quoting NEIL TOLAND to ALL concerning LAKOTA 1.4:
┌─┤NEIL TOLAND to ALL├──────────────────────────────────────────┐
│ │█
│Can anyone tell me if the New LAKOTA is currently avaliable for│█
│general download or, is it still being tested? │█
│Checked BCBBS the other day and only found 1.3 . │█
└───────────────────────────────────────────────────────────────┘█
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
Still testing Neil. It's coming along.
---
■ Apex v4 ■ Who did the owner of the first modem talk to?
■ Sea Spray BBS Wilmot, N.S. (902)-765-6867 300 - 14400
* LAKOTA v1.4ß
* SHILOH v1.0ßf * Sailing Smoothly With SPITFIRE
* Origin: Sea Spray BBS * Node_ID: A0902000MSG83.18 — Lakota 1.4beta
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:55:15.
DATE..... : 09-30-94 07:20:00
TO....... : Colin Royal
FROM..... : Mike Woltz
SUBJECT.. : Lakota 1.4beta
Hello Colin ...
COLIN ROYAL said to SYSOP on 09-29-94
CR> Just info you... I have played with the lakota auto log off
CR> by allowing the log off to go thru and then by aborting it a
CR> couple times. Works good! I haven't heard anyting else from the
CR> callers on lockups either. No reply necessary.
Colin, thank you for your report ... Please be sure that you are working
with the newest copy of LAKOTA v1.4 ... I am hopeful that the current
copy is a finished product ... Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG85.18 — Gsz
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:56:07.
DATE..... : 09-30-94 08:15:00
TO....... : Dan Shaffer
FROM..... : Mike Woltz
SUBJECT.. : Gsz
Hello Dan ...
DAN SHAFFER said to SYSOP on 09-29-94
DS> You were right the first time. For some reason my modems were not
DS> quite configured the same. My callers didn't have a problem,I did.
DS> Thank you for the advice,and I know I'm a pain some times,but I'm
DS> learning. The MKSFMENU works great and my rips were fine. :)
Dan, I am glad that you have found the problem ... Keep up the good
work. And you are not a 'pain' .... You are doing just fine ... We
were all new to the wonderful world of BBS at one time or another ...
Thank you.
Thank you for your support of Buffalo Creek Software products and
SFNET ...
Respectfully ....
]\/[ike
* MicroQwk #150001 * Nothin' ain't worth nothin' but its free!
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Home of SPITFIRE BBS
* Origin: Buffalo Creek's BBS * Node_ID: A0515001MSG88.18 — Docs
Exported from SPITFIRE Bulletin Board System on 10-01-94 at 21:56:40.
DATE..... : 09-30-94 05:41:00
TO....... : Eric Lofgren
FROM..... : Jacque Shipley
SUBJECT.. : Docs
══ quoting ERIC LOFGREN ═══
╒════ to SYSOP ═══ ƒrom a message on 09-29-94 " ═════
│
│ Thanks for the well written docs.
│ Eric
│
╘════════════════════════════════════════ " end of quote ════
Hi Eric,
Appreciate your compliment, Eric! I find I refer to them quite
often myself. An excellent idea to highlighting text that you
refer to frequently...makes locating the information much easier.
...Jacque
* MicroQwk #150002 * Complaints???...Place them here --> [ ]
---
* LAKOTA v1.4ß
* SHILOH v1.0ßg * Spittin' Fire Since 1988!
* Origin: The Mother Board BBS * Node_ID: A0515000Source note
Source: SF-FAQ3.ZIP, with compiler and purpose identified by its FILE_ID.DIZ. Message headers supply the dates, authors, recipients and subjects. No missing Parts One or Two were present in the supplied source folder, so their contents or survival are not inferred.