Hmm, OK, well I have rebuild PAR 0.80 from source, and re-installed wxperl and now everything is working fine... I'm fairly sure that if I re-installed the binary version of par then this would re-occur though. Any ideas why?

Thanks all. This is a major improvement for me. I still have quite a few bugs, but not sure how best to announce them, since I don't have good reproducable cases for most of them.

For example, I manually build an intermediate par file, then remove the Wx dll's, then build the exe. However, if the Wx dlls aren't then in the patch when I run the final exe, something goes mad, consumes all available ram in the machine until it falls over in a heap... If I build the exe without --gui then the last thing I see on the console is the message about being unable to "locate loadable object for module Wx in ...". To be fair this may not be a par issue at all... I didn't think to check what happens normally if I just delete the dll's.... Ooops, will go and do that next!

Thanks again

Ed W

Reply via email to