However, if I knew how to do that, then I wouldn't be posting the question here and I would be working on it already

At http://aspn.activestate.com/ASPN/Mail/ you'll see there's a libwin-32 mailing list. It's all but dead ... but there's possibly still a few people subscribed to that list (eg Jan Dubois) willing and able to help with the problem.

Alternatively a simple bug report, without any proposed solution, to either rt.cpan.org (as tye suggested) or a Bugzilla report (see http://bugs.activestate.com/help.cgi) might prove fruitful. Jan Dubois is closely associated with fixing bugs in both ActiveState and the libwin package - but it's probably more appropriate to file your report with rt.cpan.org as it's really a libwin bug (rather than an ActiveState bug).

Cheers,
Rob

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.