home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Carsten's PPE Collection
/
Carstens_PPE_Collection_2007.zip
/
S
/
SNUKE.ZIP
/
SNUKE.DOC
< prev
next >
Wrap
Text File
|
1994-01-28
|
6KB
|
123 lines
───────────────────────────────────────────────────────────────────────────────
SimpleNUKE v1.0 = an easy-to-use nuke-ppe
a
Nemesis '94 production
written by: The Brain /Razor 1911
───────────────────────────────────────────────────────────────────────────────
Introduction:
─────────────
Many people have been asking me for a WORKING nuke-door.. Well, here is my
first attempt. I know KnoX (from our team) made a nuke, but since I was not
able to modify his nuker, I decided to make another. This is not to compete,
but just for my lazyness. I know there are some(/lotsa) bugs (and unfinished
features)....
Files included:
───────────────
SNUKE.DOC - You're reading it
SNUKE.PPE - Add this to your CMD.LST
SNUKE.CFG - Configuration
SNUKE.EXE - dir/file update util for $$LOGOFF.BAT
SNUKE1.EXE - used by SNUKE.PPE
SNUKE2.EXE - used by SNUKE.PPE
NUKE.PPE - Sample nuke-access handling
NUKE.PPS - Sample nuke-access handling (source)
Installing/configuring:
───────────────────────
I won't give a detailed description here, just add the PPE to your CMD.LST with
the full path and it's security level (I'll get back to the level later). Dump
all files in one path, and you should not experience any problems. The
SNUKE.EXE should be placed in your $$LOGOFF.BAT, if changing a dir wasn't
possible during run-time, this util will try to update the dir during recycle.
As you might expect, our configuration file will allow you to change nearly
everything, so don't complain about that, just make sure you have the node-path
set correctly!!
Individual nuke access:
───────────────────────
I preferred giving users individual access to the nuker or not, this is not
as simple as you might expect... My solution is using an unused conference as
nuke-access flag. On Nemesis, I selected conf 10, this is not a JOINable
conference. If I want to give a user nuke-access, I just register the user in
conf 10. To get this working, I used a front-end PPE called NUKE.PPE which
checks if the user is registered in conf 10. This is the easiest I hope...
Usage:
──────
After starting the nuke, you'll get a filename-prompt. And what do you think
you should do here? Right, enter the file description (wildcards are allowed
as you are used to). The nuker will scan the upload-dir FAST, it won't check
the DIR.TXT, but just searches the file in the corresponding path.
NOTE: The nuker will only search in the upload-directory, ofcourse you
could imagine a setup where it's essential to scan multiple paths,
but get real... We only want to nuke recent files don't we??
You can select which file(s) you want to nuke and after this selection, every
file you selected will be processed seperately. If the uploader can be found
(this might not be possible if the log-filehas been deleted, or it was never
uploaded (/locally uploaded)) the programm will ask how many times to nuke
the upload-credits. You can enter a negative number here to GIVE CREDITS!
Now, the downloader(s) will get there credits back, if you want....
The next step determines the nuke-comment, this comment is placed below the
file and its description. If you select 'own comment', you can enter your
personal comment, or leave the line empty for no comment at all.
Now the system will ask what to do with the file, [N]uke it (make a 0-byte
file for rejection), [L]eave unchanged (don't hurt the file), [D]elete (just
terminate the damn thing). If you nuked or deleted the file, SNUKE will ask
for a size-replacement. This is a 8-character text placed over the file-size.
If you select 'own replacement' and enter an empty line, the size won't be
replaced.
After nuking all files, you are asked to generate nuke-reports. This means, a
message will be send to the uploader of every nuked file. I recomment doing so,
so the uploader knows why his credits were reduced.
Final:
──────
I'm not planning to spread this util widely. Not because I'm lazy or anything,
but I don't like getting questions from every lamer around... If you have
any questions or suggestions or anything, leave mail on Agents of Fortune,
State of Devolution, Mirage, or ofcourse on Nemesis!
The Brain
Nemesis '94
───────────────────────────────────────────────────────────────────────────────
NEMESIS:
───────────────────────────────────────────────────────────────────────────────
Running the best PCBoard 15.1 setup ever...
4 NODES:
──────────
31-74-Zyxel19k2 / 31-74-Zyxel19k2 / 31-74-DS9k6 / 31-74-HST
STAFF:
────────
The Brain - Supervisory, PCB-coding
KnoX - PCB-coding
NAiLZ - Screens, bull... KOUD! D00D!
REMOTE PPE SUPPORT:
─────────────────────
Agents of Fortune (sysop:Butcher)
I will upload most recent updates to the Razor conference.
If you're not in Razor, try leaving mail...
───────────────────────────────────────────────────────────────────────────────