THE SSL CERTIFICATE FOR *.POWERARCHIVER.COM HAS EXPIRED.

[klitos]

Hi,

Here’s some more detail on how to reproduce the “No end mark” problem I referred to in an earlier post.

1. Download the “Official” LHA utility for Win32. Search Google for the file LHA32106.EXE. For example, you may find it in http://www.asahi-net.or.jp/~GI8S-TKUC/lha32106.exe (note: I have not tested this and therefore cannot guarantee it to be virus-free).

2. Run LHA32106.EXE to extract the LHA32.EXE archive utility. This is a simple Win32 Console utility. To install it, just copy it into a directory pointed to by your PATH environment variable.

2. Create an LHA archive using the Explorer context menu. Let’s call it t.lzh.

3. In a Command Prompt window, type LHA32 t.lzh and press Enter. LHA32 will produce a listing of the archive, but before it does that it will produce a message box titled “UNLHA32 Error report (on execute_cmd)” and containing the text “No end mark. : ‘t.lzh’”.

If you look at the t.lzh in a hex editor, and compare it to one created by LHA32, you will notice that the “end mark” is just a NUL character as the last character of the file. You can “fix” the t.lzh file that Power Archiver created, simply by appending a NUL character to it, but it would be best if Power Archiver created it properly in the first place.

Regards,
Klitos

[ivan]

Thanks!

I will look into issue.

[ivan]

The issue will be fixed in 9.01.02.

Thanks!

[spwolf]

You can Test new per-release here:
http://www.powerarchiver.com/test/release/powarc901.exe

check if you are still having the same issue.

thanks,

[TBGBe]

In a Command Prompt window, type LHA32 t.lzh and press Enter. LHA32 will produce a listing of the archive, but before it does that it will produce a message box titled “UNLHA32 Error report (on execute_cmd)” and containing the text “No end mark. : ‘t.lzh’”.

Nope. I get error : “UNLHA32.DLL is necessary in order to practice this program” ??
UNLHA.DLL does not exist in the extracted directory. Guess that should be a seperate download??

However, using a hex file viewer - the lzh file created by PA 9.01.02 does have a NULL character at the end - so I guess it is OK?

[klitos]

Hi,

Sorry, I forgot you had to download UNLHA32.DLL separately. Do a Google search for “UNLHA32.DLL” and you’ll get links to download the latest version, currently ulh3191g.exe (version 1.91g).

I tried the 9.01.02 test version. Instead of UNLHA32.DLL complaining about “No end mark”, it now complains that the created LZH file has an “Invalid end mark”.

You said you looked at the generated file in a hex editor and it had an end mark of “NULL”. I did the same, but it had an end mark of 90 hex (instead of 00 hex). Now that’s strange.

Cheers,
Klitos

P.S.
By the way, I also noticed that installing this version of PowerArchiver forces the association of file types even when you don’t want it to. Just confirming what someone else said in another post. This can be annoying, when you’ve spent time carefully associating different archive file types with different utilities, and then this utility comes along and destroys your associations.

[TBGBe]

Hmm.
Created four archives with PA 9.01.02 (just 3 or 4 ASCII text files) - two were NULL terminated, two were not - just coincidence?

[spwolf]

@klitos:

Hi,
P.S.
By the way, I also noticed that installing this version of PowerArchiver forces the association of file types even when you don’t want it to. Just confirming what someone else said in another post. This can be annoying, when you’ve spent time carefully associating different archive file types with different utilities, and then this utility comes along and destroys your associations.

if you leave “Associate PowerArchiver with reccomended formats” option in setup checked, it will indeed change your associations ;-). I have tested it and unchecked that option - PowerArchiver did not associate itself with anything.