Dr Skip wrote:

> For instance, these both worked, except for the bombing out at what I think was 
> the "recycle bin":
> 
> d:\bin-test\FORFILES -pd:\ -s -m*.* -c"CMD /C if @ISDIR==TRUE 
> D:\bin-local\UNIX\usr\local\wbin\tar.exe -cvf "k:\@FILE.tar" "@FILE\*.*""
> 
> d:\bin-test\FORFILES -pk:\ -m*.tar -c"CMD /C 
> D:\bin-local\UNIX\usr\local\wbin\gzip.exe -fS .gz "k:\@FILE" "

What helps often with this is creating little batch files, in this case for
the command that is run by the for or forfiles loop, and/or around tar,
gzip and the like. This gives you more freedom to massage the action and
the input to the executables. For example, you can not call gzip if the
directory is the recycle bin and possibly avoid the "bombing".

> WSH seems like overkill, not to mention a learning curve. It just seems
> like this should work more easily...

It's a bit ugly to access the file system, but I didn't find it difficult
when starting from an example.

Another possibility is to use an evaluation copy of the 4nt shell; I found
that many things that don't work well in cmd.exe do work there.

And still another question is why you need the files ziped... maybe another
option gives you what you need; like for example using NTFS compression on
the backup drive, since you're working on WinXP.

Gerhard

-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist