proggy that will delete ANYTHING AT ALL no matter what!!-not a joke

  • Thread starter Thread starter yup!
  • Start date Start date
On Fri, 23 Jan 2004 21:21:55 -0500, Duddits <[email protected]>
wrote:

Hi Dud
Nope - didn't even touch the file let alone the directories.
Thanks for the suggestion

Anyone else want to join the bandwagon..

Just to repeat the problem:-
Directory called 'recycler' - inside is another directory called
'Nprotect'.
NTFS disk
Norton is NOT installed
Nothing - but nothing- so far has been able to remove this or anything
else in the recycler directory. Please see previous posts.
Bdelete; dell later; gippo; symclean (or whatever); Erasure; -- don't
work. RM tried stand alone and with 'NTFS read' but not worky.
 
If it is NTFS did you try disabling windows file protection and then
deleting the file?
 
Bob Adkins wrote:
| On Sun, 18 Jan 2004 12:53:03 +0000 (UTC), yup! <[email protected]>
| wrote:
|
||
||
|| Thanks - tried it at 23:10 17/01/04 ----- didin't work _said
|| files were inaccessable.
|| Your help was appreciated though.
||
|| Anyone else got any ideas??
|
|
| Try this. Never tried it myself, but it looks good.
|
| http://www.tacktech.com/display.cfm?ttid=170
|
| Bob

Y'lost me. This goes to a web page about a program that restores
the contents of the recycle bin after you install a
Norton/Symantec utility.

Is this relevant to the thread?

I'm confused.

Richard
 
Bob Adkins wrote:
| On Sun, 18 Jan 2004 12:53:03 +0000 (UTC), yup! <[email protected]>
| wrote
||
|| Thanks - tried it at 23:10 17/01/04 ----- didn't work _said
|| files were inaccessable.
|| Your help was appreciated though.
||
|| Anyone else got any ideas??
|
Click to expand...
---------------------------------------->
I recall seeing this in a thread several weeks past, but cannot
recall if the posters participating had tried RM.EXE. v1.4
by Mark Adler. This thingie is an 'industrial wipe out', and
MUST be treated with caution. I have never seen it to fail ...
except by my own negligence. Of course .. it cannot touch
anything which is in actual use at the moment of trying to
kill it. Particularly when used in DOS, RM.EXE is a thing
of extreme danger to a lay person who does not pay some
attention to what is happening. It does not ask questions or
prompt any kind of confirmation. Danger Danger Caution.
 
|
|
| > Bob Adkins wrote:
| > | On Sun, 18 Jan 2004 12:53:03 +0000 (UTC), yup!
<[email protected]>
| > | wrote
| > ||
| > || Thanks - tried it at 23:10 17/01/04 ----- didn't work
_said
| > || files were inaccessable.
| > || Your help was appreciated though.
| > ||
| > || Anyone else got any ideas??
| > |
| ---------------------------------------->
| I recall seeing this in a thread several weeks past, but cannot
| recall if the posters participating had tried RM.EXE. v1.4
| by Mark Adler. This thingie is an 'industrial wipe out', and
| MUST be treated with caution. I have never seen it to fail ...
| except by my own negligence. Of course .. it cannot touch
| anything which is in actual use at the moment of trying to
| kill it. Particularly when used in DOS, RM.EXE is a thing
| of extreme danger to a lay person who does not pay some
| attention to what is happening. It does not ask questions or
| prompt any kind of confirmation. Danger Danger Caution.
|
|

It sounds like this program is a good candidate to be run from a
DOS batch file that contains the command, "Pause." Thus, it could
be given a "safety" step.
This could be accompanied by a simple screen design and a
statement this way:

echo off
pause
echo Are you sure?
echo You cannot recover from this process.
echo Continuing will cause (insert consequences here)
echo Stop this routine! -- break out now: Press <CRTL> and
<BREAK> echo SIMULTANEOUSLY.
echo or
Press any other key to continue
(the last line is added by the DOS Pause command)
echo on

This may have to be adjusted for newer versions of DOS than I'm
thinking of.

Richard
 
Do not execute the DOS Batchfile that I submitted yesterday
without knowing the DOS conventions for your version of Windows!
I wrote this simply as an example. It is untested! It should be
edited the right way.

The last thing that you want to happen is for what I wrote to
blast the dangerous utility into execution, destroying the
contents of your hard disk in a flash.

So, don't do it, OK?

Richard

| | ---------------------------------------->
| | I recall seeing this in a thread several weeks past, but
cannot
| | recall if the posters participating had tried RM.EXE. v1.4
| | by Mark Adler. This thingie is an 'industrial wipe out',
and
| | MUST be treated with caution. I have never seen it to fail
....
| | except by my own negligence. Of course .. it cannot touch
| | anything which is in actual use at the moment of trying to
| | kill it. Particularly when used in DOS, RM.EXE is a thing
| | of extreme danger to a lay person who does not pay some
| | attention to what is happening. It does not ask questions or
| | prompt any kind of confirmation. Danger Danger Caution.
| |
| |
|
| It sounds like this program is a good candidate to be run from
a
| DOS batch file that contains the command, "Pause." Thus, it
could
| be given a "safety" step.
| This could be accompanied by a simple screen design and a
| statement this way:
|
| echo off
| pause
| echo Are you sure?
| echo You cannot recover from this process.
| echo Continuing will cause (insert consequences here)
| echo Stop this routine! -- break out now: Press <CRTL> and
| <BREAK> echo SIMULTANEOUSLY.
| echo or
| Press any other key to continue
| (the last line is added by the DOS Pause command)
| echo on
|
| This may have to be adjusted for newer versions of DOS than I'm
| thinking of.
|
| Richard
|
 
Back
Top