From: "Tony Ingenoso" 

Oh, DIR /B on an empty directory produces nothing BTW.

So something like DIR /B > \foobar produces a zero length file called
foobar. Simply COMP'ing (or FC'ing) a known zero length file with the DIR
results should do it.  If the COMP/FC mismatches, then there's something in
that directory.


"Tony Ingenoso"  wrote in
message news:3efa0b6f$1{at}w3.nls.net...
> IF /?  (then check out the EXIST option)
>
> "Chris Robinson" 
wrote in message
news:3EF9C540.66D7A5AF{at}NOSPAMtotalise.co.uk...
> > I have a share set up on one of our PC's that's set to have Everyone as
> > Full Controll.  The idea being that if we get any Virus's that propogate
> > to network shares, we'll know about it.  I want to write a batch file
> > that checks the Directory periodically (I'll use task scheduler) and, if
> > it finds a file in there, does a NET SEND to my PC so I know something
> > could be wrong.
> >
> > I've tried a few things so far, but the one I'm working on at the moment
> > is this (NT4, SP6 btw) - Prior to running the batch file, I've created a
> > text file from "dir > testdir-clean.txt" that is
basically the test
> > directory with no files in it (i.e. "Clean"):
> >
> > *****Start of Batch File*****
> >
> > dir c:\testdir > testdir-current.txt
> > fc /L c:\testdir-clean.txt c:\testdir-current.txt
> >
> > IF ERRORLEVEL 1 GOTO _POSSVIRUS
> >
> > IF ERRORLEVEL 0 GOTO _NOVIRUS
> >
> > :_POSSVIRUS
> > NET SEND mypcname File detected
> > EXIT
> >
> > :_NOVIRUS
> > EXIT
> >
> > *****End Of batch File*****
> >
> > So, "fc" is file compare and "/L" compares
the files as ASCII text.  The
> > idea being that if it detects a difference, then another file is present
> > in the directory.  I'm not 100% certain on the use of the ERRORLEVEL
> > section though and this is the bit that doesn't seem to be working atm -
> > any ideas?
> >
> > Cheers,
> > Chris.
> >
>
>

--- BBBS/NT v4.01 Flag-4