Tony Marques

Off the top of my head you would need to indeed use multiple calls... as you already don't trust what 7z created or just did so... for %%f in (*.bak) do (7z.exe a %%f.7z %%f -mx=9 -mmt=32 & ( 7z.exe t %%f.7z && del %%f || echo Error: 7z testing )) Your concern is this line below which should be exactly the same as "-sdel" ... so "&&" aka "if ok" then ... for %%i in (*.bak) do 7z.exe a %%i.7z %%i -mx=9 -mmt=32 && del %%i P.S. I've added 7z to the path, but really I actually would set 7z_exe="C:\Program...

Off the top of my head you would need to indeed use multiple calls... as you already don't trust what 7z created or just did so... set 7z="C:\Program Files\7-Zip\7z.exe" for %%f in (*.bak) do (%7z% a %%f.7z %%f -mx=9 -mmt=32 & %7z% t %%f.7z && del %%f)

I was about to start a new topic... here is what I was going to write: I was testing some large 2GB archives with thousands of files and I just wanted it to quickly abort after the first error, rather than continue for 3 minutes only to tell me that hundreds of additional files also have CRC errors or some such thing. There should be a quick/abort option to timeout on the first error, and actually if specified (to perhaps even go faster) reorder testing proceedures to check common or quickly tested...

I was about to start a new topic... here is what I was going to write: I was testing some large 2GB archives with thousands of files and I just wanted it to quickly abort after the first error, rather than continue for 3 minutes only to tell me that hundreds of additional files also have CRC errors or some such thing. There should be a quick/abort option to timeout on the first error, and actually if specified (to perhaps even go faster) reorder testing proceedures to check common or quickly tested...

I may have asked for this before, but but to repeat myself can I request an option to perhaps use something like -tz to "touch" the archive while creating or updating or even after the fact to touch the archive with the date/time of the LATEST item in the archive? for example 7z a -tz new.zip dir* would create a new.zip not with the current date/time but with the date/time of the latest item in the things archived... or a simple command 7z u -tz old.zip that wouldn't update old.zip but just only...

I may have asked for this before, but but to repeat myself can I request an option to perhaps use something like -tz to "touch" the archive while creating or updating or even after the fact to touch the archive with the date/time of the LATEST item in the archive? for example 7z a -tz new.zip dir* would create a new.zip not with the current date/time but with the date/time of the latest item in the things archived... or a simple command 7z u -tz old.zip that wouldn't update old.zip but just only...

I've asked for this before, but but to repeat myself can I request an option to perhaps use something like -tz to "touch" the archive while creating or updating or even after the fact to touch the archive with the date/time of the LATEST item in the archive? for example 7z a -tz new.zip dir* would create a new.zip not with the current date/time but with the date/time of the latest item in the things archived... or a simple command 7z u -tz old.zip that wouldn't update old.zip but just only change...

I've asked for this before, but but to repeat myself can I request an option to perhaps use like -tz to "touch" the archive while creating or updating or even after the fact to touch the archive with the date/time of the LATEST item in the archive? for example 7z a -tz new.zip dir* would create a new.zip not with the current date/time but with the date/time of the latest item in the things archived... or a simple command 7z u -tz old.zip that wouldn't update old.zip but just only change external...