PA2004–>Error with LHA

jweinraub

Whenever I try to make a LHA archive, I get the following error:

Access violation at address 0065F672 in module ‘POWERARC.EXE’. Write of address 0237A86A.

The program then freezes and requires me to kill the task.

Decompressing already compressed LHA files seems to have no problems.

Is there also a way to get backwards compatibility with LZH (LHArc) as well? Thanks so much for all your help in this fine app!

spwolf

Can you please outline step by step what exactly are you doing?

thanks!

jweinraub

Create New Archive

Save as type drop down and use LHA

type in my file name and select save

i add the files i like to be incooproated into my archive.

program then exploded as previously described.

jweinraub

PS- Sorry for delay. I was away from my computer for the past few days! :)

ivan

Hello!

We cannot reproduce it - although there was already one post about similar situation, we think there might be something special in your configuration so we will keep eyes open.

jweinraub

this is weird bc i did a full format, install windows xp sp2 and i get this error. odd.

davidsplash

can you try this is safe more and can you post the file here so we can check it it might be archive problem only specific to that archiver. what archiver created it whats in it what are the filke names of the files inside it size and also date created

TBGBe

@jweinraub:

Create New Archive
Save as type drop down and use LHA
type in my file name and select save

i add the files i like to be incooproated into my archive.

program then exploded as previously described.

The things involved are:

Temporary Directory
Path/Filenames/Type/Size of selections to be archived
Are files “locked” by another program/anti virus

Can you give more details of 1) and 2) ??
Does it happen if you try to archive (LHA) a single file?

jweinraub

This only happens for LHA archives. Single file or multiple files. I have not tried safe mode. This has happened when nothing was installed other than windows sp2 and PA2004.

ivan

The issue will be fixed in upcoming 9.1 - this week!