After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created. The archive that I attached was initially too big to send. When I reduced its size by deleting all but one file in the archive, then the error was made.

Here’s where it really gets crazy:

Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.) This corrupt archive is always larger than the .bh archive if it were created “new”. (“New” meaning: not Converted from another type, but created from the original files and folders.) Keep in mind that creating new .bh archives always results in a good archive.

Now, if I go back to the corrupt archive, convert it to .zip, .7zip, or .lzh, those archives test Okay!

I am coming up with a few CRC Errors in .bh archives.
…
After more testing, I have found that .bh files are correct until you add or delete any files from the archive. It is then that the CRC Error is created.
…
Using the Archive Converter to change any archive type to .bh also creates a corrupt archive. (At least PA sees it as corrupt.)

Your example does test as CRC error.
But I cannot reproduce any of these cases - for me each BH file created is testing OK.
After deleting files I tried both Closing and Renaming Archive.

@Charles:

[Converted] archive is always larger than the .bh archive if it were created “new”.

This may be only because you used Archive Converter with Maximum method. There was a bug and it will be fixed in BETA 4. In all other situations it should work fine - even with Archive Converter - Normal.

Here’s a good .zip archive for you to convert to .bh {Eddie Sweater Compliment}
Every time I convert it and then use the test feature to check it I get a CRC Error.
…
When I convert to BH with Normal Mode and try to open the archive, it asks me for a password – and I never added one!