ZIP UDF (zipfldr.dll library)

[RobK]

The error returned from _Zip_InternalDelete is different than the other functions (hence marked as internal). In this case, it means that the file was not deleted. I'll look into this further tomorrow on some older XP machines here at work (all my main machines are Win7 now, as well as my home computers), and try and find out where exactly it is failing. Truthfully I need to add a bit more error checking in that function.

Is there a way to call _Zip_DeleteItem without a pop-up dialog confirming delete? I not sure where the prompt dialog originates is it the For $oVerb in $overbs loop?

[wraithdu]

The zipfldr.dll library is invoked through the Shell.Application object. I only have the amount of control that is provided by the library. It does not implement everything available in the Shell.Application object. That's a round-about way of saying no, I can't prevent that popup... which is why I wrote the kludgy internal function. Review this thread please, as many questions like yours have been asked regarding the operation of the zipfldr library, esp relating to the available Flags options.

[wraithdu]

Fuck me sideways.

This is going to take a while to fix. The real problem is that XP's implementation of the zipfldr library cannot walk sub directories automatically. So you can't do $obj.NameSpace("...\file.zip\some\sub\dir"). Which means I have to do it manually with loops of NameSpace, ParseName, and GetFolder. FUCK.

[Melba23]

wraithdu,

After that last post I presume we are correct in thinking that you are slightly miffed?

M23

[wraithdu]

A tad.

[guinness]

It probably doesn't help matters but I don't envy you at all wraithdu!

Amat Victoria Curam

[wraithdu]

I'm not feeling very victorious, even though I felt fairly prepared when originally re-writing this one... just goes to show...

So I think I fixed everything but the InternalDelete function. The point of this function, while kludgy, was to non-interactively delete files from archives. The idea was to create a temp directory then move the files out of the archive with the MoveHere method. This works great on Win7, but fails on WinXP. This means don't try to overwrite files in archives on XP, it will fail with an error. Use the _Zip_DeleteItem function (interactive) first to remove the old files, then add the new ones. If anyone has any suggestions, please speak up, cause I'm out of ideas.

Everything else should work though now. I'll update the first post in a minute, so I'll need some testers.

[RobK]

I'm not feeling very victorious, even though I felt fairly prepared when originally re-writing this one... just goes to show...

So I think I fixed everything but the InternalDelete function. The point of this function, while kludgy, was to non-interactively delete files from archives. The idea was to create a temp directory then move the files out of the archive with the MoveHere method. This works great on Win7, but fails on WinXP. This means don't try to overwrite files in archives on XP, it will fail with an error. Use the _Zip_DeleteItem function (interactive) first to remove the old files, then add the new ones. If anyone has any suggestions, please speak up, cause I'm out of ideas.

Everything else should work though now. I'll update the first post in a minute, so I'll need some testers.

Recompiled with new version. I am getting this error on execution on XP and Win7 machines.

Compressed (zipped) Folders Error

The specified directory C:\Documents and Settings\Administrator\Local Settings\Temp\~xcsofli.tmp\EventLogBkup is empty, so Compressed (zipped) Folders cannot add it to the archive.

After select OK the application just hangs.

Just started to look into the problem.

Rob

Edited July 1, 2011 by RobK

[wraithdu]

I tested on XP with no errors. I'll need some code to reproduce and test against.

edit

n/m, I see the problem. And again, gonna be difficult to work around on XP. Essentially the zipfldr library is complaining when trying to add an empty directory (which is currently how it creates subdirs for files). Originally this was why I used the GUID type files to add directory structure then delete the temp files with _Zip_InternalDelete.

When I was testing I was using multiple subdirs, in which case this error doesn't appear. I guess it only appears on a single subdir level. Again, I can't think of a solutions on XP since the InternalDelete function doesn't work. The temp file deletion step would be interactive.

You can work around it for now by creating your directory structure somewhere then adding it to the zip.

Edited July 1, 2011 by wraithdu

[wraithdu]

I'm gonna revert a few changes to reinstate the temp file creation/deletion some subdirs work again. As I mentioned, this will fail on XP, so you'll have to work around it on your end, sorry.

[RobK]

I'm gonna revert a few changes to reinstate the temp file creation/deletion some subdirs work again. As I mentioned, this will fail on XP, so you'll have to work around it on your end, sorry.

All I really want to know is how can I remove the GUID files from the zip? The internal delete fails and there is no way to delete without prompts from the _Zip_DeleteItem method.

Your advice is appreciated.

Rob

[wraithdu]

Pretty simple, do not add items to subfolders using the $sDestDir parameter. Create your directory structure from the root on your local file system, create your files in that structure, then add the root directory to the root of the zip file ($sDestDir = ""). This way the AddItem function won't try to create any directory structure and will not create those temporary files.

[Tippex]

I had a problem when attempting to use _Zip_List with the full pathname specified in a UNC format:

//hostname/directorypath/filename.zip

(instead of the usual drive letter because my multi-user application couldn't depend on the same drive mappings)

Fortunately all I had to do was to comment out this line in the ZIP.au3 UDF for _Zip_List:

If Not _IsFullPath($sZipFile) Then Return SetError(3, 0, 0)

and this accepted the UNC.

UNC is short for Universal Naming Convention or Uniform Naming Convention and explained here: http://en.wikipedia.org/wiki/Path_(computing)#POSIX_pathname_definition

Is there a neater way that will not negate the IsFullPath check please?

[BrewManNH]

Windows uses the double backslash to indicate a UNC path, not the forward slashes you have.

EDIT: I read on that linked page that it will accept the forward slashes in windows, but this XP system I'm on will not find a network share with forward slashes, but will find it with back slashes. YMMV

Edited September 9, 2011 by BrewManNH

[Tippex]

Agreed.

So please may this correction be made to the ZIP.au3 which is successful? (thanks in anticipation)

; #FUNCTION# ====================================================================================================

; Name...........: _IsFullPath

; Description....: Determines if a given path is a fully qualified path (well, roughly...)

; Syntax.........: _IsFullPath($sPath)

; Parameters.....: $sPath - Path to check

;

; Return values..: Success - True

; Failure - False

; Author.........: torels

; Modified.......: Tippex/BrewManNH

; Remarks........: Windows UNC path inclusion

; Related........:

; Link...........:

; Example........:

; ===============================================================================================================

Func _IsFullPath($sPath)

If StringInStr($sPath, ":\") Then

Return True

ElseIf StringInStr($sPath, "\\") Then

Return True

Else

Return False

EndIf

EndFunc ;==>_IsFullPath

[Whiper]

Hello!

Is there a way to automate adding a password to .zip files?

Thank you!

[wraithdu]

The shell object on which this UDF is based does not support passwords.

[sigil]

I can't get the basic example to work. I'm running XP Pro SP3.

Here's the code:

#include <_zip.au3>

; create a test directory
$dir = @DesktopDir & "\mydir"
DirCreate($dir)
; create some files
For $i = 1 To 3
    FileWrite($dir & "\file" & $i, "")
Next
; create the ZIP
$file = _Zip_Create(@DesktopDir & "\test.zip", 1)
ConsoleWrite("err: " & @error & @CRLF)
_Zip_AddItem($file, $dir)
ConsoleWrite("err: " & @error & @CRLF)
; add it to a subdir
_Zip_AddItem($file, $dir, "dir1\dir2")
ConsoleWrite("err: " & @error & @CRLF)
; remove dir
DirRemove($dir, 1)

When I run this, I get the error message:

(...my include path here...)\_zip.au3 (131) : Error in expression.:

Until IsObj($oNS.ParseName($sNameOnly))

Until IsObj(^ ERROR

I haven't made any changes to the UDF. I've been looking on MSDN to figure out if there's something wrong with the way ParseName is being called here, but I haven't had any luck so far. Any ideas?

Edited October 18, 2011 by sigil

[wraithdu]

Are you sure you have a full copy of the UDF, and not a copy/paste error? Other than that I'll need a lot more info, as that example works for me.

Additionally, start reading from post #95 about problems adding files to subdirs on WinXP.

[sigil]

Are you sure you have a full copy of the UDF, and not a copy/paste error?

I copied the UDF today from what you have in post #1. Is there a more current version?

Other than that I'll need a lot more info, as that example works for me.

What other info would be most helpful?

I'm using AutoIt 3.3.6.1.