bummer
I was SO bummed yesterday morning as I spent hours restoring my system
after my little encounter with the snake. Through sheer luck I lost very
little, including nothing in Windows (as yet discovered). I lost a folder
here, a folder there, including subfolders several levels deep, and I'm
sure I'll find something missing months from now! What a little bastard!
He certainly has no future in programming. I wouldn't buy software from
him, would you? And then he goes and blames his friend and asks us to
leave him alone. What a chump! What a pathetic child. At least I can
take comfort in the fact that I am in good company -- except for him, this
IS good company!
Meanwhile, I know I'll hesitate before I run shrouded or bound code again.
Several
people have mentioned things like hex dumps, and David Gay mentioned
VSHIELD which caught the snake in time. Please mention the sources of
these tools. I want! I need! In the meantime, the idea of taking
deltree,
etc. off your path before running exe files is a very good idea, but it
will only protect against relatively crude attacks. Seems you could just
launch your exe from a batch file as
set holder=%path%
set path=
c:\whereitis\dangerous.exe
pause
set path=%holder%
set holder=
If you run out of environment space in this swap out, alter your config.sys
file to include a line like:
Shell=command.com /E:768 /P
where the /E:768 reserves 768 bytes (default is 256 (?) and increments are
in 16 (?) bytes) and /P
sets this instance of command.com as permanent. If you are running from a
DOS box (a new shell instance) you don't actually have to reset the path
after running the program, but it is good form to do so.
Hope your restorations are swift and complete!
John Cannon
|
Not Categorized, Please Help
|
|
