In Celebrity News:
Forbes 100 Most Powerful Women use THIS for anti-aging
=======================================================
She was just voted 1 of Forbes 100 Most Powerful Women
Who are we talking about... Ellen Degeneres
Since that came out, rumors have started that she got a facelift.
Those are just haters talking because she looks so good.
See what she really used to look 20 years younger
Here -> http://www.omtup.com/ellen/facelift/rumors.index
We hope you enjoyed this celebrity update
if you would like to stop further updates write Update Notice Messages
at- one one eight Kecks Lane|R u f f D a l e, PA 15679 or http://www.omtup.com/slk9/sg40.jgo93
Should be del @FILE, case matters Also I suggest using /c echo @FILE for testing I have been using SS64.com for years. That site is a good reference. QueueHammer Dec 14 '09 at 16:51
1H is the full path, including name. @FILE is only the name, so if you're dealing with subfolders, it won't workNote that if you want files OLDER than 10 days, you need to specify -d "-10". -ve means "older than", +ve means "newer than". You can also specify DDMMYY or -DDMMYY format as the parameter to -d. When I tested it under Windows 7, @PATH was just the path, and @FILE was just the file name. I usedE for the del command. Chris Vesper Aug 18 '10 at 18:40Also, if you wish to get files from another drive: for example all rar files older than 30 days -m *.rar -d -30 -c "cmd /c echo These wil l be deleted @fname" These will be deleted "File1" These will be deleted "File2" I used this syntax on Win Server 2008: forfiles ysql_backup" /S /Mql /D -30 /C "cmd /c del @PATH" jI wish I could upvote more than once Thanks for this. also adding ECHO "Y" helped with the Are you sure ? messages like this: "cmd /c echo "Y" | del @PATH" at the end trekme Amazing, but too late for me as I've made the conscious decision to never write a batch file again, and force myself to go exclusively with PowerShell. Thanks. I should add that if the days range is less than whatever you are trying to delete, the error will state no matching files were found. This is correct.remember that the number of days should be negative, say for example /d -10 will delete everything before 10 days. A positive value makes almost no sense. Warning: If you are just trying to delete files you copied N days ago, this is not what you should use. I just copied some files and runpath" /S /C "cmd /c echo @file" /D -31' on them, and the files that were modified more than 31 days ago do appearThis answer works when "older than 7 days" is defined as "modified more than 7 days ago" rather than "created more than 7 days ago". How can the latter be achieved? TimS Oct 18 '13 at 10:50Unfortunately, on file share destination it gives the error: "ERROR: UNC paths paths (\\machine\share) are not supported"For the most part, this is a fairly impractical answer. If I have a directory with lots of data in it, there is will not work well. I'd go with one of the answer that does it "in place" adOct 1 '13 at 22:37@adamb0mb this is in no way impractical - if "destination" is on the same filesystem as "source", the move operation is quite lightweight. As robocopy is really robust, it will in fact work for any directory size, obscure file names, basically arbitrary path lengths and include directories if you need it to - something which surely cannot be said about many other Windows utilities. I would use rd /s /q c:\destination instead of the del command though or even use another robocopy /mir c:\emptydir c:\destination run to empty the directory if you expect trouble with file namesSeveral minor points: 1) at does not necessarily invoke command.com - apparently when command.com is invoked is a bit of a complex mystery; 2) command.com was introduced with MS-DOS; 3) cmd.exe can run most command.com scripts, but there are a few minor command.com things that don't work in cmd. Michael Burr Sep 29 '08 at 23:01
Hey Mike, if you have any specifics on command.com features that don't work on cmd.exe, I think it would be worth posting a separate answer on that. Chris Noe Sep 30 '08 at 0:02
It's been so long since I worked on Win9x or DOS the only thing I can remember is that you could do something like "cd ..." to go up more than one directory level (hey, I said minor, didn't I?). However, see my edited answer for info about command.com's processing on NT. Michael Burr Sep 30 '08 at 5:00
1
cmd.exe was introduced with NT 4.0 I believe, not windows 95. FlySwat Oct 1 '08 at 1:53
1
Chris: see the current version of the Wikipedia artic
No comments:
Post a Comment