Text 1058, 60 rader
Skriven 2008-11-19 08:14:12 av Mike Luther (1:117/3001.0)
   Kommentar till text 1057 av Johan Zwiekhorst (2:292/100)
Ärende: More stuff gone!
========================
 JZ> Hi Mike!


 JZ> A file deletion doesn't actually remove the file, only 
 JZ> the directory entry. So the infected code remains on 
 JZ> the storage media even after the file was deleted. If 
 JZ> you want to be extra sure, you can order PAVCL to 
 JZ> overwrite the file with zeroes before deleting it. 
 JZ> That way, no infected code remains hidden on your 
 JZ> storage volume.

Aha!  Now I think I'm understanding this.  So a 'deletion' isn't an actual
deletion from the bytes actually stored on the disk.  That because, as
'normal', when you delete a file, the operating system only removes the file
name from the file directory, leaving the bytes stored in whatever sectors on
the disk where it was.  The operating system then being able to reuse that disk
area at a later time.

Ordering PAVCL to overwrite the file with zeroes before deleting it actually
destroys the bad byte pattern on the disk before clearing the file directory of
that file.  Which in my thinking is a true deletion.

I guess, hopefully, the last question here is what name pattern does PAVCL use
to 'delete' the file from the directory by renaming it to something else?  Is
there a set 'pattern' of name creation letters used for this?  And, whether or
not there is a set pattern for this, the original file name in the directory,
displayed (hopefully) on the same line for each file in the report file PAVCL
creates, is how we go about directing a REXX program, which runs only if error
code 12 is returned on exit from PAVCL, to then either actually delete the
file, leaving whatever sector data is there on the hard disk?  Or .. as an
alternative .. to move that file to a quarantine directory for either study or
whatever later?  With out information list from PAVCL the trigger for our REXX
program to generate whatever actual log file creation and work analysis file we
wish from that?

By chance, since you have and furnished a sample REXX file for the download
process, do you happen to have a REXX file that will generate an example of how
you process this?

What I want is to move the bad data to a quarantine directory like Norman
offered us the choice to do.

 JZ> If you call PAVCL from a batchfile, you can use IF 
 JZ> ERRORLEVEL ... as the very next command to test for an 
 JZ> exit code equal to or greater than the given number. 
 JZ> In REXX, the special variable RC will have the exit 
 JZ> code and can be used as any numeric variable.

This I am familiar with.  What I would like to have is a sample of what to do
in the REXX code after we get into the error exit with a found item or more.

Thanks!


--> Sleep well; OS/2's still awake! ;)

Mike @ 1:117/3001

--- Maximus/2 3.01
 * Origin: Ziplog Public Port (1:117/3001)