Add file: if code or data-as-text, surround it with code tags. But be sure you've made it a small, representative sample, with any personal information redacted. A thousand bytes or so should suffice. The notion is -- reduce your problem code to something that reliably demonstrates the problem without including all the "other" important (and not so important) parts.

Pictures are basicly no-no's here in the Monastery except one small one on your user page. While it's an imperfect solution, if the screenshot (I'm guessing, but pls confirm that you mean it's a picture of interaction with your script) can be linked from any server that's publicly accessible, including those that specialize in that sort of service.

HOWEVER, that's frowned upon (among other reasons, because

1. There's no assurance the picture (or file if binary) will still be on the remote server when some future reader wants to know what's in it
2. the Monk(S) who's inclined to try to help must now visit an unknown and likely untrusted website to 'buy a pig in a poke,' i.e., your file with unknown and possibly malicious content
3. and, assuming the aforesaid Monk(s) does so, the very process is another step that adds to the time s/he is donating to your problem.

So better, figure out how to state your problem without requiring all that; preferably, without recourse to any external source...

For more, please see

• On asking for help
• How do I post a question effectively?
• Markup in the Monastery
• I know what I mean. Why don't you?
• Perl Monks Approved HTML tags
• What shortcuts can I use for linking to other information?
• Writeup Formatting Tips

And, not just BTW, while an informative subject is helpful, so is "brief." Your title is on the long side!