Re^5: Newbie cmd prompt problem

So... the second time it ran obviously.

Maybe it also ran the first time, but the program is written in such a way to not print stuff to stdout

You can try http://live.sysinternals.com/procexp.exe to see if the program really ran

Or even try using depends.exe like this depends.exe /c /f:1 /pb /ot:temp.txt ...perl.exe foo.pl ... to see if the program really ran the first time

It is a very weird problem I know. Even the teacher couldn't figure it out.

Doesn't sound too weird , just sounds like both you and the teacher are tired/confused/new

Maybe your perl-installation is crippled. Long ago I downloaded a portable strawberryperl on WindowsVista(?) and windows wouldn't let me unzip it because of some malware protection feature ... or some UAC ...

so maybe your user account isn't getting a UAC prompt on first run, but its running with lower privileges on the second run

or maybe you got some kind of anti-malware/anti-spyware/or something that is interfering (unlikely but you can never tell)

You must be a Mac user?

I'm on windows. The things that show up in folders are called icons/files, they're not called windows ... now if you had said file-window it might be more obvious what you're talking about

remember I'm not peeking over your shoulder at your monitor, so "the window" doesn't tell me what it is

Comment on Re^5: Newbie cmd prompt problem Download Code

Replies are listed 'Best First'.
Re^6: Newbie cmd prompt problem by nquiton (Novice) on Sep 12, 2013 at 00:39 UTC
You are correct about using proper terminology. My Mom calls me all the time and I have to figure out what she really means. Plus, I have been teaching software (including Windows) for 15 years, so I should know better! I did figure out the problem (I think) I had spaces in my file name and when I removed theme, it worked:-)Now I just have to figure out all of the errors in my code. I wish I was more left brained and less right brained... at least right now.	[reply]
Re^7: Newbie cmd prompt problem by Anonymous Monk on Sep 12, 2013 at 01:00 UTC
I hope you aren't this guy My computer broked down after perl install all grown up 10 years later.	[reply]
Re^8: Newbie cmd prompt problem by nquiton (Novice) on Sep 12, 2013 at 01:13 UTC
LOL. Nope, I'm not that guy. 1. because I'm female and 2. because I was chasing boys at 12, not playing with computers:-)AND I wouldn't be posting if my computer was "shatting flames". I'd be tossing it onto my front lawn and running for a fire extinguisher:-)	[reply]
Re^7: Newbie cmd prompt problem by Anonymous Monk on Sep 12, 2013 at 02:29 UTC
We've all been there :) talking to yourself out loud is a pretty good debugging technique :) 1 / 2 In this list of links there are a few that discuss quoting command line arguments, super short version `perl "path with spaces yada da"` ... when you drag/drop a file onto cmd.exe the resulting filename is usually quoted	[reply] [d/l]
Re^6: Newbie cmd prompt problem by Anonymous Monk on Sep 12, 2013 at 00:00 UTC
Regarding possibilities, Ultimate guide to Windows 7 security -- Use AppLocker, BitLocker to Go and other Microsoft security tools mentions blocking perl.exe from running via applocker	[reply]