| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | -j and REP packets. |
SH> :aftercall
SH> if exist c:\max\olr\node01\tinysbbs.rep c:\max\doors\trep\upload.cmd
SH> Will that work? the one thing I can't do is write
I think so.
SH> still tweaking the above as it seems to fail on the
SH> filename of the uploaded file sometimes,
SH> and other times it works.
SH> I think I'm also going to put a quick login button in
SH> the first mecca screen that blasts you
SH> right to the QWK menu to cut down on errors on the
SH> above mess to log in. ;)
You could simplify by creating a restricted user eg. "QWKUpload"
and assign it a "QWKUpload" privilege that uses a LoginFile.
Access.Ctl:
========================================
Access QWKUpld
Level 1
Time 10
Cume 8440
LoginFile Misc\QwkUpld
Flags UploadAny Hangup
End Access
========================================
QwkUpld.mec:
========================================
menu_cmd Msg_Upload_QWK
[Key_Poke]c:\max\doors\trep\tinysbbs.rep
========================================
upload.cmd:
========================================
maxp.exe -n0 -k -j"QwkUpld;y;{password}"
========================================
Then you can run upload.cmd after each upload, which would allow multiple
uploads per session after the latest *.rep file is cleared. It would also
negate additional input from the user eg. passwords.
Nb. This is a concept only.
--- Maximus/2 3.01
* Origin: Top Hat 2 BBS (1:343/41)SEEN-BY: 3/0 633/267 640/954 712/0 313 550 620 848 @PATH: 343/41 138/146 392 123/500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.