RichardH has asked for the wisdom of the Perl Monks concerning the following question:

This node falls below the community's minimum standard of quality and will not be displayed.

Replies are listed 'Best First'.
RE: PerlEx
by lemming (Priest) on Nov 15, 2000 at 21:15 UTC
    Have you started by looking at Troubleshooting at ActiveState?
    I'm afraid just saying it went kaput is not going to help people figure out your problem.
RE: PerlEx
by Fastolfe (Vicar) on Nov 15, 2000 at 21:07 UTC
    I'm sure there are people here that can help you with this, but I'm wondering why you don't just go to ActiveState tech support and ask them?
      Tech support for PerlEx sucks. It took them two weeks to get to a question I asked and then didn't provide a solution for it. The problem I had was related to a bug in both program and documentation, so I think they should have paid more attention to it; but the bug I was needing a fix for had been filed by other four months before and they hadn't yet gotten to it. Given this evidence of poor support I had to stop trying to use the product. (And PerlEx comes as closed-source binary, which also sucks)

      If you want more attention then you may need to buy a support contract. You can also look at their bug-tracking system to see if your problem has been experienced by others.