Perl script works but fails Windows binary compilation

[daluu]

This node falls below the community's threshold of quality. You may see it by logging in.

[ww]

If you don't care enough to make it readable, why should I care enough to offer help?

On asking for help, How do I post a question effectively?, Markup in the Monastery, I know what I mean. Why don't you? and Perl Monks Approved HTML tags.

[dasgar]

daluu, if you want to increase the odds of getting help, I'd recommend doing the following with your post:

• Encapsulate your code and error messages in <c></c> tags as choroba has suggested.
• Considering the length of your code, use the <readmore> tags.
• Provide the flags/options used with PAR and perl2exe.

In its current state, your post is extremely difficult to read. In essence, you're asking others to spend 30 minutes or more to decipher your post so that they can understand what's going on and then take further time to provide assistance. If you can clean up the formatting a bit as choroba and I are recommending you to do, I think you'll find others much more willing to assist.

[choroba]

Please, use <code> tags to format the code and data. Some basic hints to formatting are displayed below the editing box with links to further details.

[ikegami]

<code></code> won't work since his text includes </code>, but <c></c> would.

It's also way too long. It's extremely rare that more than 20 lines are needed to demonstrate a problem, and even that is much more than normally needed.

[marto]

Ugg, as everyone else has mentioned, please spend some time formatting and using 'preview' to check your posts before submitting them. The easier you make it for people to read the more likely they are to spend time helping you.

pp hasn't been part of the PAR module for some time now, I suggest you upgrade.

"Unrecognized character \xEF at script/genVpLoadPALTemplate.pl"

Did you search google for this error message in this context? Looks like a UTF-8 BOM problem to me. Make sure your text editor isn't adding BOMs.

Also Perl 5.8.7 is five years old. Consider upgrading.

[aquarium]

Most of the 5.x turn my perl code into exe programs are largely out of date/synch with OS and Perl updates. As you can see mileage varies. I've recently PARed a little backup script and turned into exe, which i had to fight extensively as the exe would just silently exit. in the end some random hacking (nothing related to prerequisite modules) got it going. i spent a lot of time trawling google to find the tid-bit that helped. also note that it's possible that your 30 day trial of perl2exe is expired and may have some bearing. if it's very important to get your script as exe maybe pay for perl2exe and get some support from them?
as noted by others, you'll need to reformat your code/output/question so that it's more readable..i'm not either wanting a headache trying to decipher your full post.