The extra added bonus to F-response is that it offers up a live, read-only, environment to play with while that painfully slow image is running.
There's something wrong with the script? BONK!
Something got screwed up when I copied it over from Linux? BONK!
My Perl environment is not the polished marble that Harlan's is? Well, maybe.... BONK!
WTH is going on here? Thought 1 turns out to be correct. This is a dependency issue. Even after you've been through your environment 10 times and all your dependencies look sweet, there's the registry.pm file in the right path and you've contacted the developer because you've ruled out everything else. (sorry Harlan, I owe you expensive scotch when we finally meet). It's really very clear in all of it's perly non-clarity. It can't locate Parse/Win32Registry.pm and this is clearly a misplaced file in a directory path right? Not exactly.
From the command line type "ppm" for the perl package manager, go to view and check "all packages". Glory, Glory, Hallelujah. There's a package called Parse-Win32Registry. Right click and install that bad boy.
Coders are a bubble off; I'm telling you.
Next trick: Path variables.
The command "dir" sucks, "ls" does not
ls, grep, cat, and a whole host of others are available in the unxutils package. Go downlaod it and install it and while you're on the web grab strings and grep.
Once you've got all these ported apps installed you don't want to cd into a specific directory to use them right? You want to be able to use the command like you're the one in control.
Editing your $PATH is the answer.
Right click my computer and go to properties--go to "advanced"--"environment variables"
Highlight "PATH" and click edit. Use a semicolon as a separator and add the full system path to your sexy new executables.
Pretty soon your path can look like mine:
And my $PATH is dead sexy.