Whilst masticating on , Roy J. Tellason (1:270/615)
wrote to Alan Hess:
AH>> :Donuttin
AH>> waitn 120
AH>> goto loop
RJT> What's that one for?
Ignore it - it's a relic from my dos bbs days when I needed to busy the
system for two minutes (120 seconds.) I no longer need or use it, and
actually forgot it was still referenced in the .cmd file. Sorry about that.
AH>> :Overnite
AH>> call overnite.bat
AH>> goto loop
AH>> :Makenl
AH>> call domakenl.bat
AH>> goto loop
These two above: Overnite) run my nightly dos bbs utilities such as hlist,
which creates my list of all files available to callers, and Makenl) runs
once a week to process my nodelist segment (I'm a netmail hub.)
AH>> :Squishmail
AH>> call runos2.cmd mail.cmd
AH>> goto loop
RJT> Invoking another instance of the command processor there in that
RJT> middle line?
I believe it could be (heck, my expertise level is close to nil. I just know
it works.) It's just starting another session - I included the runos2 and
rundos cmd files later in the post, as you probably saw. They make use of
OS/2's Start command.
AH>> :F9_key
AH>> list2 newusers.txt
AH>> muep
RJT> A different user editor, I guess. I just use the one that's
RJT> built-in, does this one work okay with max 3.01?
Yes, it does. I was just accustomed to an external user editor, as I think
they make things like deleting and purging users easier, bu your mileage may
wary.
AH>> cd\nodes
AH>> bonk
AH>> goto loop
There's an OS/2 analog to Bonk, but I liked Bonk better.
AH>> :F5_key
AH>> call runos2.cmd packbase.cmd
AH>> goto loop
Packbase.cmd runs Sqpackp. I forgot to post that file. Here it is:
----- packbase.cmd begins -----
D:
cd\squish
Sqpackp d:\max\area.dat
cd\max
----- packbase.cmd ends -----
AH>> :F4_key
AH>> i:
AH>> cd tcpip\bin
AH>> REM Dial Other Internet Providers
AH>> SLIPPM.EXE
AH>> goto loop
RJT> More details on this stuff would be welcomed. One of the things
RJT> I left out of my earlier post was GIGO and FX-UUCICO, the
RJT> latter of which might be a problem. I have a dialup uucp
RJT> connection for email.
The above allows me to use my bbs line to access my internet provider.
Slippm.exe is IBM's Dial Other Internet Providers program. Normally, I use
my voice line to access the net, but, during the day, I don't like to tie up
the voice line (some people actually do call us .) As the bbs is least
busy during the day, I make use of the line for my own purposes.
I can't help you with e-mail - I get it via regular fidonet modem call from
an echo hub in my net. I'm sure someone else will step in to assist you with
that. I also don't run any doors, so that would also be a question for
someone else.
AH>> :BBS_336
AH>> :BBS_312
AH>> :BBS_288
AH>> :BBS_264
AH>> :BBS_240
AH>> :BBS_216
AH>> :BBS_192
AH>> :BBS_168
AH>> :BBS_144
AH>> :BBS_120
AH>> :BBS_96
AH>> :BBS_72
AH>> :BBS_48
AH>> :BBS_24
AH>> :BBS_12
AH>> :BBS_3
AH>> goto Loop
RJT> Why are these all bunched together and why do they just loop?
RJT> Or am I missing something here?
This is likely also a vestige of the dos days. When a call comes in to Bink,
it generated an errorlevel. By trapping that level and using it to spawn
Max, the caller got the proper estimates for time of downloads and uploads.
BBS_336 is a 33600 connect, BBS_312 is a 31200 connect, BBS_288 is a 28800
connect, and so on.
AH>> :Error
AH>> Echo
RJT> What's that one?
If there's a serious error that halts Max, the system beeps and the message
below is displayed.
AH>> Echo Serious Error - Maximus Halted.
AH>> Goto End
AH>> :End
AH>> EXIT
AH>> ----- runmaxp.cmd ends -----
AH>> These use the OS/2 "Start" command:
RJT> Which, as I understand it, doesn't let you switch to that
RJT> process to see what's going on. Is that the case?
No. You can easily switch. Ctrl-Esc brings up a list of processes, and you
can switch to whichever you wish to view. Alt-Esc switches from one process
to the next, usually in the order in which they were started. I often view
the unpacking of mail if it comes in while I'm at the machine.
AH>> After mail arrives:
AH>> ----- mail.cmd begins -----
AH>> echo off
AH>> D:
AH>> cd\squish
AH>> sq386p in out squash -fd:\max\echotoss.log
AH>> REM sqlinkp -fd:\max\echotoss.log
RJT> Why the REM here?
I don't use Sqlink - it took too long, and none of my users were using the
message read commands that read linked threads, anyway. Plus, with all the
echoes, so many threads have their subject lines changed eventually, and thus
become unfollowable by Sqlink. Why make the drive be accessed any more than
necesssary, I decided.
AH>> erase d:\max\outbound\*.bsy
AH>> cd\max
AH>> scanbldp MATRIX
AH>> erase echotoss.log
AH>> ----- mail.cmd ends -----
AH>> All message areas except netmail are squish format.
RJT> That one is here, too.
I had netmail as squish, but I had to go back to *.msg because the makenl
program requires a *.msg netmail area.
RJT> I'll save these and use 'em as a starting point, at least...
I got the runos2 and rundos .cmd files from a fellow sysop when I was
convinced by he and others to switch to os/2 2.11. I was extremely reluctant
- I had DV/QEMM, thhey did what I wanted, and os/2 seemed overwhelming (it
still is - there's so much I don't know, but that's my fault.) For several
months, I ran basically the same bbs setup I had run under DV in os/2 (I
called it BBS in Dos, and started it in my startup folder), while playing
with setting up the os/2 versions (which I called BBS in os/2.) Worked fine.
Once I got the os/2 setup working, I made the full switchover (including
HPFS), and have never regretted it for a second. OS/2 is so much faster,
more reliable, and more configurable than DV/QEMM, which were fine programs
in their own right. *adh*
--- Msged/2 4.10
---------------
* Origin: Nerve Center - Source of the SPINAL_INJURY echo! (1:261/1000)
|