Zlib UDF

[monoceres 190]

I wrote this because I wanted a simple way to compress data in memory instead of files.

And because rasim has done an excellent job with his 7Zip udf that handle files I did not include any file support.

Following functions exists:

_Zlib_Version()

_Zlib_Shutdown()

_Zlib_Startup($Filename = "zlibwapi.dll")

_Zlib_CalculateAdler32($DataPtr, $DataSize)

_Zlib_Uncompress($CompressedPtr, $CompressedSize, $UncompressedPtr, $UncompressedSize)

_Zlib_Compress($InBufferPtr, $InBufferSize, $OutBufferPtr, ByRef $OutBufferSize, $CompressionLevel = $Z_DEFAULT_COMPRESSION)

_Zlib_CompressBinary($binary, $CompressionLevel = $Z_DEFAULT_COMPRESSION)

_Zlib_UncompressBinary($compressedbinary, $UncompressedBinaryLength)

More info in the UDF.

Example:

#include "zlib udf.au3"
  _Zlib_Startup()
  $bin=StringToBinary("hahahahahahahahahahahehe")
  $binlen=BinaryLen($bin)
  
  $compressed=_Zlib_CompressBinary($bin)
  
  $uncompressed=_Zlib_UncompressBinary($compressed,$binlen)
  
  MsgBox(64,BinaryToString($bin),"Original:"&@CRLF&$bin&@CRLF&@CRLF&"Compressed: "&@CRLF&$compressed&@CRLF&@CRLF&"Uncompressed: "&@CRLF&$uncompressed)
  _Zlib_Shutdown()

Download:

zlib_udf.au3

Previous downloads: 33

Zlib dll download:

http://www.zlib.net/

Ps. If anyone want to continue adding functions to this, go ahead I won't probably work anymore one this anyway

Edited January 9, 2009 by monoceres

[ptrex 89]

@monoceres

Tested and approved.

Very nice as usual !!

regards,

ptrex

[James 376]

I tested this too Works well, not sure when I will need it though.

Are there any limitations?

[JRSmile 17]

WOW i already thought of a way to include more dll sources in binary string form in my sources but lower the size.. this is the perfect way to do so, THANK YOU VERY MUCH.

Edited January 8, 2009 by JRSmile

[monoceres 190]

Thanks guys

@James

As far as I know there are just the regular autoit limitations

@JRSmile

Yeah, compressin' stuff directly in memory is so much cooler than those pesky files

[wraithdu 79]

Figured I'd test this out. I'm not sure what version everyone is using, but I just downloaded v1.2.3, and the function calls use cdecl, so the UDF crashes in current form. And the filename is zlib1.dll.

Edited January 9, 2009 by wraithdu

[Andreik 63]

Nice work, monoceres.

[monoceres 190]

Figured I'd test this out. I'm not sure what version everyone is using, but I just downloaded v1.2.3, and the function calls use cdecl, so the UDF crashes in current form. And the filename is zlib1.dll.

I'm using the one from zlib.net and it's named zlibwapi.dll (_Zlib_Startup has an optional parameter specifying the dll name though). I'm also pretty sure that the __stdcall calling convention is used because when I called the dll from a vc++ app with the cdecl calling convention the app crashed and the debugger whined about "wrong calling convention used"

[wraithdu 79]

Yeah, that's weird. I downloaded it just last night from the link in your first post. I know you know what you're talking about, so it's strange.

Here's the link I used - http://www.zlib.net/zlib123-dll.zip

It has the different filename and calling convention.

[monoceres 190]

Yeah, that's weird. I downloaded it just last night from the link in your first post. I know you know what you're talking about, so it's strange.

Here's the link I used - http://www.zlib.net/zlib123-dll.zip

It has the different filename and calling convention.

You're right

I downloaded the dll from here:

http://www.winimage.com/zLibDll/

Very stupid mistake and I will update the UDF to use the standard dll from the official zlib website

Edit: Done!

Edited January 9, 2009 by monoceres

[wraithdu 79]

No biggie. Keep up the great work!

[monoceres 190]

I'm thinking of changing the behaviour of _Zlib_CompressBinary so it adds a 4 byte header that contains the length of the original data, any thoughts of that? It would be much easier to use the compressed data in your script if you don't have to pass around the original length all the time

?

[trancexx 982]

This is nice and useful.

btw, I think I found native api compression method available. Uses LZW algorithm.

edit:

... ok, I got it. Will make new thread not to be offtopic here.

Edited January 10, 2009 by trancexx

[Xand3r 0]

Any ideea why

_Zlib_CompressBinary(0xff00ff00,9); (0x78DA63F8CFF09F010005FF01FF)

returns a different value than php's gzcompress ?

php:

echo bin2hex(gzcompress(convert('ff00ff00'),9));




        function convert($hexString) // converts a hexstring to a binary string
        {
                $hexLenght = strlen($hexString);
                // only hex numbers is allowed
                if ($hexLenght % 2 != 0 || preg_match("/[^\da-fA-F]/",$hexString)) return FALSE;

                unset($binString);
                for ($x = 1; $x <= $hexLenght/2; $x++)
                {
                        $binString .= chr(hexdec(substr($hexString,2 * $x - 2,2)));
                }

                return $binString;
        }

// php output: 0x78dafbcff09f010005fe01ff

[monoceres 190]

Any ideea why

_Zlib_CompressBinary(0xff00ff00,9); (0x78DA63F8CFF09F010005FF01FF)

returns a different value than php's gzcompress ?

The data is not 9 bytes long. It's an integer so it's 4 bytes.

You might also want to use a binary string in autoit as well. "0xff00ff00" is the way to do it.

[goldenix 1]

This is my Code I tried & it results in -3

What does -3 mean?

#include <INet.au3>
#include "zlib_udf.au3"

  _Zlib_Startup()
  $bin=_INetGetSource('http://g.e-hentai.org/non-h')
  $binlen=BinaryLen($bin)
  
  $uncompressed=_Zlib_UncompressBinary($bin,$binlen)
  
  ConsoleWrite($uncompressed & @CRLF & @CRLF)  
  
  
  _Zlib_Shutdown()

[prazetto 11]

Thats have incompatibilities with general zlib.

If you try to using gz_uncompress($string) in php

or using other zlib library will give you

uncompressed data plus sign: "?".

For example:

Compress this string with script.

"The quick brown fox jumped over the lazy dog."

will output decompressed data in other decompressor

program:

"The quick brown fox jumped over the lazy dog.?"

I'm saw in hex editor and compare output of your

script and general zlib output and in a few last

byte are differs.

So here is my problem.

Oh man do you have problem solving?

[flashlab 1]

This is my Code I tried & it results in -3

What does -3 mean?

#include <INet.au3>
#include "zlib_udf.au3"

  _Zlib_Startup()
  $bin=_INetGetSource('http://g.e-hentai.org/non-h')
  $binlen=BinaryLen($bin)
  
  $uncompressed=_Zlib_UncompressBinary($bin,$binlen)
  
  ConsoleWrite($uncompressed & @CRLF & @CRLF)  
  
  
  _Zlib_Shutdown()

'$bin' in '$binlen=BinaryLen($bin)' should be the size of original data

[Ximorro 0]

Hi monoceres.

Good work, simple and effective solution!

Did you implemented your idea about storing uncompressed data size?

It's very strange the DLL needs that information, is there any other call in the library that doesn't have that requirement?

It's very limited, to decompress you must now the size of the original data, it's almost as having to know the original data itself...

[Ward 109]

Try my zlib UDF, uncompressed size is not needed.