RC>PM> RC>PM>         The modem is getting stuck in an invalid state.
RC>PM> RC>PM>         The odd thing is that I have yet to have it happen
RC>PM> RC>PM>         here,  so its hard to fix what I can't duplicate.
RC>PM> RC>PM>         I do have S30=90 set here.  S30 (if all is working
RC>PM> RC>PM>         correctly)  causing the modem to disconnect after
RC>PM> RC>a certain period Patrick, i've also had this happen (about 15
RC>PM> RC>times) on my bbs since upgrading my supra external to the
RC>PM> RC>latest data pump and beta flash. Version 17 was better... I
RC>PM> RC>just put version 18 on last night...maybe it will be better.
RC>PM> I'll try the S30 setting also. 
RC>PM>         The 15 modems here on the BBS were still running fine
RC>PM>         with the -18 code this morning.
RC>I had a modem lockup yesterday with the 18 beta. The S30 option seems
RC>to have reset the modem fine but Frontdoor could not initilize the
RC>modem before it reset. The modem gets 'hung' when a user logs off the
RC>bbs...so frontdoor restarts trying to init the modem which is still
RC>hung until the limit in the S30 parameter is reached. By that time
RC>frontdoor has aborted. I'm going to work with my frontdoor setup and
RC>batch file to see if I can work around it.....have frontdoor or my
RC>batch file 'loop' until it can re-init the modem.
        Interesting.   TBBS here just keeps "hitting" at a modem until
        it comes back, or provides a valid CONNECT message, or the
        end of time.
        I would likely say that if you set S30=90 (15 minutes) and
        the system has looped without good results for 20 minutes
        that its time for an automated alert...
RC>Thanks,
RC>Richard
RC>...This copy of ProBoard has been unregistered for 238 days!
RC>---
-Patrick Moore
 Sysop of Supra BBS 
CMPQwk1.42 331þIs the latest ROM code in your modem and the modem(s) it 
lls?
--- FLAME v1.1
---------------