Rick C. Hodgin

I'm using an app where I include Client7z. I have a scenario where I'm sending a pointer to an empty string and the password length is 0. Will Client7z and 7z.dll use that combination and create an empty password on the file? It's showing up as Encrypted +.

I had the same bug in another project. Could not find it. I worked around it by using a #define malloc(a) my_malloc(a), which added 16 bytes to the a length. I knew it was an overrun but I could not find it. Tried memory leak tools. Nothing identified it. Finally I wrote my own malloc() tools, which I called meminate. It patterned a leader and trailer block to every allocation, and on realloc or free, it validated the pattern. Came down to one line. Needed to allocate (length + 1) instead of length....

Over the past few years I've been using Client7z as a baseline for interacting with 7z.dll. I've written a host of supporting algorithms around these base abilities you've exposed in 7-Zip. Our apps have been used by thousands of users on hundreds of sites. It's given our apps an ability that sets it apart from other apps. I wanted to write and say very sincerely thank you, Igor, for all you've given to the computing world. Your kindness and generosity is very much valued by this man from the United...

I was able to get this to work by updating code in FileStreams.cpp::Open() and OpenShared(). In Open() I use a flag I setup in Client7z to determine if it should be shared open or exclusive open, and then call: In class: NWindows::NFile::NIO::CInFile m_file; In Open() function: If shared --> m_file.OpenShared(fileName, true); If not shared --> m_file.Open(fileName);

I've been able to set the L"x" and L"he" properties in Client7z. Is there a list of properties and values that are valid? I need the property for opening files to archive in shared mode.

Thank you for all your assistance, Igor. My offer remains open. If there are any programming tasks you would like some help on, please feel free to ask. I have been able to create an integrated package using 7z.dll for its archive operations. I have options to create ZIP or 7z files, using level 3 compression (determined by manager). It works to create, extract, and test, and I have the ability to extract to memory, and build from memory using the array of memory buffers you indicate above. It is...

If I'm doing memory-to-memory, what do I use for input/read stream? That's similar to how I modified FileStreams.h, except that I implemented code for each function. It works well as is. I'll probably leave it for now. I'll try CBufPtrSeqOutStream for performance comparison.

If I'm doing memory-to-memory, what do I use for input/read stream?