If you use regular PA, you can create a backup job (.pbs file) and one of the option is a time (and size) filter. You can set a specific date – or specify files created or changed in the last x number of hours, days, etc. (see the attached image)
'Create the string with parameters for PACOMP
strCompressionString = PACOMP & " -a -P " & Chr(34) & ArchiveName & Chr(34) & " " & Chr(34) & pstrFileName & Chr(34)
WshShell.Run strCompressionString, 0, True
```The command and the parameters sent to PACOMP will be displayed when you run the script.
Look at this line in the script
strCompressionString = PACOMP & " -a -P " & Chr(34) & ArchiveName & Chr(34) & " " & Chr(34) & **pstrFileName** & Chr(34)
What's the value of **pstrFileName** when you run the script? Is it only the filename or is it the filename with the full path?
There’s nothing you can do about it. If you have forgot your password, then the content of the zip file is lost forever. The whole point of using passwords on archive is to prevent access to it if the password is incorrect.
Hello, i found a “folder Date” bug in conversion of archives. After conversion looks all OK … but if you unpack the converted archive, date for all folders and sub-folders doesn’t match to date stored in archive.
This bug occurs for all converted archives types (7-zip, cab, rar, tar, Lha, Bh …) except zip. (after unpacking all dates for “zip” are OK)
“Rar” archive: There is a another bug. If you convert archive eg. from zip -> Rar all folder structure is lost. There are only files no folders. Message “Some archives have not been converted”
Note: DATE bug
Similiar bug “Add to archive…” for all archive types (except zip)
“rar” date and folders are not stored
we have one computer that we can reproduce it on and 3 where we cant… interesting issue.
Can you see any logic in this? So far the reported problem happens on Win 7 Ent. Ed. 64-bit and Win 2008 Server 64-bit.
Have you the same version of OS installed on the 4 machines you have tested it in?
If the OS is the same in all 4 machines, then it would be hard to explain why you can only reproduce it on 1 of the 4 machines, but working properly on the other 3. Like you said, it’s an interesting issue.
The only difference between our versions of Win 7 is that I have the English Edition and you have the French Edition.
The question then is why is it working for me, but not for you. It would help if someone else could recreate this error. @abecrow:
If it helps, I also have winrar installed on the machine, and msys (which contains the tools tar and gzip (functional)). I’ve tested my computer by deleting the MSYS tools and such, I get the error message for PACOMP.
I doubt that will come into conflict with winrar.
I don’t think WinRAR would cause this kind of problem. However I’m sure eventually we will find the cause of this problem.