💾 Archived View for clemat.is › saccophore › library › ezines › textfiles › ezines › TLG › tlg-074.t… captured on 2021-12-04 at 18:04:22.

View Raw

More Information

-=-=-=-=-=-=-

                 ______________
                |  ___    ___  |
                | |_  |  |  _| |  ______           ______
                |___| |  | |___| |_    _|        /        \
                      |  |         |  |         |   /----\/
                      |  |         |  |         |  |
                      |  |         |  |         |  |    ___
                      |  |         |  |  __     |  |   <_  | Issue #:074
                     _|  |_       _|  |_|  |    |   \___/  | Date:07/30/96
                    |______|  () |_________| ()  \________/ ()
                     _ / /                            \ \ _
                   / _ /    ThE LONE GUNMEN Presents:   \ _ \
                  | |                                      | |
                  | |         Compiled Batch Bombs         | |
                  | |          Written By: Yankee          | |
                  | |                                      | |
                  | |                                      | |
                  |  \____________________________________/  |
                   \________________________________________/






Introduction
~~~~~~~~~~~~
    I just finished reading a .tlg. text by Dark Raven about the usefulness
of batch programming in creating ba-ba-bombs and virii.  It was a cool file,
but I felt he left out some important things, so I'm writing this file as an
extension on the same topic.  Hope ya don't mind, dude.
                                     ���
    Lemme tell ya a little about my batch programming experience.  My first
PC (yea, I used to use an Apple IIGS) was an ancient IBM PCjr I found at my
grandfather's.  Well, what the hell can you do with one?  I decided to learn
some batch programming.  It's some of the most useful computer stuff I ever
learned, and if you're a SysOp, it's something yout just gotsta know.
                                     ���
    Back on topic ... I easily learned how batch files could be really
dangerous (hey, why else would we be talking about them?), so now, whenever
I see one I know I'm gonna need to run, I first pop into Edit or whatever
and look through it to make sure there aren't any nasties hiding in there
waiting for the first dumbass to go and run them.  But I'm, as responsible
members of the cyber elite, you all do this too so yous won't get fucked bad,
right?
                                     ���
    So, ya see, if you're gonna try and screw a SysOp over, it's going to
take more than just a batch, because the can view it, right?  Well, I have a
solution: get a batch file compiler.  I saved you the trouble and included
one in this zip called TurboBAT.  What is does is looks at your batch file
and generates an .Com executable.  I hope you see where I'm going with this.
Once you compiler it into an .Com, the end-loser won't be able to view the
code w/o disassembling the thing, and no one bothers doin that everytime they
want to run an .Com!

Instructions
~~~~~~~~~~~~
    I included a batch file in this zip called Compile.Bat.  It will take
care of all the commandline stuff with TurboBAT, just make sure that they're
in the same directory.  Execute it with Compile {Filename.Bat} and it will
compile it into an .Com which you can distribute wherever.
                                     ���
    Because it's a lame piece of PD software, TurboBAT adds an unreg'd
message to the beginning of the .Com, which would tip off anyone that there
is a foot aplot, so just hexedit the message out with BEdit, also included.

Hints
~~~~~
  � Name your final .Com something like Install.Com, Upgrade.Com, or
    Tlg_App.Com.  I'm so sure some dude is going to run an .Com like
    Destroy.Com or Bomb.Com.  And avoid things like RunMe1st.Com.  I
    never run them, but it works on some people.
  � Use some Echos in your batch file to tell the user that it's going to do
    something normal, something unsuspicious, so the user won't suspect
    anything.
  � TurboBAT adds some extensions to the Dos batch language that can only be
    used if compiled with TurboBAT.  A useful command is BOOT WARM [or] COLD.
    I suggest using COLD because it'll work better under a multitasker.
    Here's some other useful ones ...

            BEEP frequency duration
            DELAY seconds
            COLOR [BRIGHT] [BLINK] fgcolor ON bgcolor

Conclusion
~~~~~~~~~~
    Um, have fun, and let me know if you have any troubles.
    Thanks to Dark Raven for the original idea.


      ��copyright july nineteen nighty-six by yankee of the lone gunmen��
SAUCE00Compiled Batch Bombs               Yankee              ThE Lone Gunmen[TlG]19960730�Pb