From: mlewis@cssnet.wplace.UUCP (Mark Lewis)
Newsgroups: comp.bbs.waffle
Subject: Re: Super Poll beta release repeat polling program
Date: 31 Aug 92 01:55:31 GMT
Organization: The Waffle House, Waldo's Place USA


zeta@spectrx.saigon.com (Greg Youngblood) writes:
> I've written a program called SUPER POLL, and it is currently beta version .8
> right now.
> Super Poll allows a little more control over the polling process and repeat
> polling.  I believe Waf 1.65 has repeat polling ability, but I'm not sure to
> what control there is over it... and I believe it should work find with 1.65,
> but I was not able to test that.

does this SUPER POLL have "call collision" detection?? for that matter,
does ANY polling program for Waffle have "call collision" detection?!

i know that *true* "call collision" handling will probably be a bit of a
bear to handle but there should be at least one program that can detect
the RING of an inbound call and exit back to waffle so that it can be
answered!

to clarify -- *true* "call collision" detection software will answer the
call and pass off to Waffle (in this case) with the "waffle online
<baudrate>" call (actually, using an errorlevel to signal that a call
was answered and then having the .BAT file loop and make the Waffle
online <baudrate> call would be better due to the way these external
polling programs are set up)... in fact, IMHO, i firmly believe that the
BBS software should answer the phone instead of the modem...

    ie: software receives RING and sends ATA instead of modem being
        initialized with ATS0=1

... this is a MUCH better way of handling things. again this is just
*MY* opinion... i guess being in FIDONet and running FrontDoor and
Remote Access have spoiled me but i have never really liked the modem
answering on it's own...

on another note... i have found that UUCICO leaves the FOSSIL driver
port initialized and active when it exits.... this fact took several
weeks in tracking down. what was happening, on my system, was that all
of a sudden, the system would act like it was locked up (blank screen, 
hard drive access light stayed lit, characters being displayed on the 
screen one every 5 seconds or so, etc...) after i enabled BNU's 
diagnostics display panel, i saw that in these cases, the interrupt 
service routine was being called over and over and over.  eventually, it 
would work itself out but i just don't think that waiting 4 hours for a 
CTRL-ALT-DEL to take effect during this time period is reasonable 
(yes! i timed it once <<GRIN>>)... i am able to reproduce this at 
will... i have had to resort to telling BNU to deinitialize the port 
with a line in the .BAT file... it's a KLUDGE, but it works!

)\/(ark


<---------------------------------------------------------------------------->
 Mark Lewis           * DA-CON Consultants -- Creating Solutions since 1985 *
 FIFESNet 20:0/0                   {..}!duke!wolves!cssnet!wplace!mlewis UUCP
 FIDONet  1:3634/12                       mlewis%lee.fred.org@cerf.net USENet
 USENet->FIDONet Mark.Lewis@f12.n3634.z1.fidonet.org    wplace!mlewis CSS-Net
                   The Company is mine... The Words are mine...
                    The Thoughts are mine... The System is mine...