Funny thing is, it worked as such in the FORFILES command, which just passes 
the directory and runs it for each. Without putting quotes around it each, all 
those stupid windows folders (and files) with spaces in them get lost. It only 
takes the part before the first space char.

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" "

<each double line is one line before word wrap>

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


William "Chops" Westfield wrote:
> On Jun 11, 2008, at 1:52 PM, Dr Skip wrote:
> 
> 
> I haven't used gzip or the shell on windows very much, but...
> 
> Most (many?) unix utilities depend on the shell for wildcard  
> expansion.  The quotes around "d:\tmp.install\*.*", or calling from  
> the windows CMD processor rather than a unix shell, may suppress this  
> expansion, leaving gzip thinking that it needs to compress a file  
> literally called "*.*"
> 
> Perhaps you could use the recursion option (if it's present in the  
> windows gzip):
> 
> BillW
> 
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist