ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

DonationCoder.com Software > Finished Programs

DONE: Req: (Autohotkey script ): auto unzip zip files in a folder recursively ?

<< < (4/5) > >>

jity2:
No problem skwire ;)
Thank you ;)

I did more tests with 2 other problematic folders on vista and it worked fine ;)

I did other tests on xp (will do them on vista later) and RecurUnZip is working fine again. ;)

I have just found one bug (I don't think it is xp related!) :
In the folder : H:\1_123_u\2009\Mebo07-10_2009  I have two subfolders (and nothing else) :
H:\1_123_u\2009\Mebo07-10_2009\Mebo09_2009
 and
H:\1_123_u\2009\Mebo07-10_2009\Mebo10_2009

Both these subfolders contain one or more zip file(s). example :
H:\1_123_u\2009\Mebo07-10_2009\Mebo09_2009\exa01.zip
...etc

When I use RecurUnZip and give him the same folder : H:\1_123_u\2009\Mebo07-10_2009
alas it unzip the zip file here:
H:\1_123_u\2009\Mebo07-10_2009\
but not here:
H:\1_123_u\2009\Mebo07-10_2009\Mebo09_2009\exa01\
...

Thanks in advance ;)

jity2:
Hello,

After much more tests all this morning, here is what I have found :

Vista
If I use 7-zip for zipping and the last RecurUnZip version (using 7-zip fo runzipping), it works great (same size octets & same files numbers). ;)
The only small problem being that there may be some problems when later one wants to delete files [path+filenames] longer than 260 characters.
Solutions (*): go one parent folder before and rename the folder with a shorter name and it should delete the folder and the longname file inside.
( (**) this seems normal as since 2007: "7-Zip now supports file pathnames longer than 260 characters."
http://209.85.229.132/search?q=cache:FC3rWIF2MQEJ:www.7-zip.org/history.txt+260+characters+7+zip&cd=1&hl=en&ct=clnk&client=)

Xp
If I use 7-zip for zipping (done under vista), and unzipping in XP the last RecurUnZip version (using 7-zip fo runzipping),it works ok.
But is it not working fine for [path+filenames] that have more than 260 characters (i.e. the 3 folders were I had problems originally with unziplify and winrar). The files seems properly unzipped but are not exactly of the same octet size and not really accessible in the Xp explorer.
The solution I have found is to:

Use this freeware (I have tried many others but they failed under vista!):
Pathscanner (http://www.parhelia-tools.com/products/pathscanner/PathScanner.aspx) and list files that are longer than 260 characters.

Tip: Pease note that it is better to know in advance where the zip file will be unzipped and how long that path will be!

Personal example :
I zip this folder (folder path = 56 characters)
C:\Users\jity1234\Desktop\1234567\0 1234567 dec09\1 OT1\
which gives this file :
C:\Users\jity1234\Desktop\1234567\0 1234567 dec09\1 OT1\1 OT1.zip


But when I unzip the zip file I use into another place: ( folder path = 32 characters)
H:\archive\2009\0 1234567 dec09\1 OT1.zip
it gives :
H:\archive\2009\0 1234567 dec09\1 OT1\[unzipped_files_here]  ( folder path = 38 characters)


So there is a difference of 18 (56-38) characters less in my destination folder of the unzipped file than the original folder.
I have to keep in mind this when I check the path characters number before zipping the original folder.
In my case : 278 characters (260 Vista limit + 18 of difference) limit should be fine. ;)
So I rename and/or save text copy of files (usually html files in my case) in my original folder before zipping.
 

I hope this helps and thanks in advance to skwire. ;)



(*) other possibilities:
- http://ccollomb.free.fr/unlocker/
- rigth click on the folder, uncheck "read only". Then, click on "advanced" and check "ready to be archived" and "compress what is inside" (sorry rough translation from french!)

(**) more infos on this 260 characters limit
http://www.windowsreference.com/windows-2000/file-pathname-character-limitations-in-windows/
http://stackoverflow.com/questions/265769/maximum-filename-length-in-ntfs-xp-and-vista
http://stackoverflow.com/questions/449652/how-to-create-a-copy-of-a-file-having-length-more-than-260-characters
http://msdn.microsoft.com/en-us/library/aa365247%28VS.85%29.aspx
http://www.codinghorror.com/blog/archives/000729.html

skwire:
So, jity2, can we call this Coding Snack completed?

jity2:
Hello skwire,

So, jity2, can we call this Coding Snack completed?
--- End quote ---

Short answer: yes ! ;)


Long answer (in case it may help other persons) :
With "path scanner" I use the 273 limit (= 278 - (260-255)) as vista limit is 260 and xp limit is 255 !



*
Unziplify found a new kind of bug ("the file seems to be corrupt") as there was 4 htm files with this size:
.htm 1ko
related folder 1Mo

When I checked the .htm in firefox, not everything has been saved properly (firefox loaded the missing info from the internet).

note: all the 4 htm files (and related folders) had names starting with "www." ! May be a bug in Firefox ? I try to repeat this firefox but this time everything was saved properly!  :huh:


*
Another error found ("the file seems to be corrupt") by unziplify :
Inside the related folder on one html file, there was a tiny file that vista could not have access to.
Solution: save the text and deleted .htm and related folder.




*
I have use the freeware "CSDiff 5" (http://download.cnet.com/CSDiff/3000-2248_4-10009023.html) so I could find the what was the missing file in the case just above.
To my surprise, I have found a real (small) bug in unziplify :
If there is
" ' "
 or
" << "
or
" " "
 (spaces not included) in the [.htm + related folder] name unziplify transform into strange characters.
note: the folder size in octet and file number is exactly the same !  :huh:
Hopefully I can still load the html file in firefox and read the text correctly. The only problem being that images contained inside the related folder are not loaded in firefox but can be openned manually in the explorer. ;)


Many thanks again for your help ;)

nkormanik:
Slightly different request, Skwire....  Instead of asking for a destination folder, and creating a different directory structure.

I would prefer that any archive simply be replaced with an unarchived folder, or the contents of the archive.  In place, in present directory structure.

This is what the old program unziplify did (no longer available, and apparently stopped working due to some Windows system upgrade).

What do you think?

Thanks!

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version