Subj : A little help...
To   : Sean Dennis
From : mark lewis
Date : Thu Apr 27 2006 05:53 pm

SD> Then comes the fun part of setting up two levels for every security
SD> level - one for telnet and one for dialup.

MT> Why?  Do you want them to behave differently (and how)?

MT> Maybe what's really in order is some MECCA in the login that does
MT> "if night and baud xxx, then add time"?

i was thinking the same basic thing except that i'd do it in the bat/cmd file
that loads the bbs and use that time to next event parameter like you
originally thought of...

ie: the following 4DOS code from a live system ;)


:bbscaller
 set dd=   JanFebMarAprMayJunJulAugSepOctNovDec
 set dy=%_dow %_day %@substr[%dd%,%@eval[%_month * 3],3] %_year
 set speed=%@word[1,%@line[dobbs%task%.bat,0]]
 set port=%@word[2,%@line[dobbs%task%.bat,0]]
 set t2event=%@word[3,%@line[dobbs%task%.bat,0]]
 set event=-T%t2event%
 set ecc=%@word[5,%@line[dobbs%task%.bat,0]]
 set baud=%speed%%ecc%
 set CIDinfo=%@word[6,%@line[dobbs%task%.bat,0]]

 if %t2event% GT 5 goto callok

 echo.
 echo TIME TO NEXT EVENT TOO CLOSE! Notifying caller...
 echo.
 dtr com%port%: on
 echo Sorry! There is a System Event in %t2event% minutes. >> com%port%:
 echo You do not have enough time to do anything.  >> com%port%:
 echo Please try again after the event has passed. >> com%port%:
 wait 10
 dtr com%port%: off
 wait 1
 dtr com%port%: on
 wait 1
 at com%port%: h
 wait 1
 dtr com%port%: off
 wait 1
 goto start

:callok
 os2title RA Node %task%
 %ra%\ra.exe -e10 -%node% -b%baud% -c%port% %event%



)\/(ark


* Origin:  (1:3634/12)