Well, Lonk, for some of us, reading, understanding, and modifying code from others is just another way to learn. Don't you think we would do the same if we had access to the O/S source? Maybe we'd close some Windows buffer overrun holes! I had access to the Unix SVR2 source and was credited with fixing a bug in the terminal session init code (WAY too many years ago).
Back to the topic...
The short answer to the original question is "yes", replacing the source determination code with a fixed path will work. In fact, I've done this and simply reference "JT.exe" since it is available via the system PATH or it isn't installed in my environment.
Jens appears to have written this piece of code to account for other people installing the JT executable in various locations. Since he isn't clarvoyant and can't know where you've installed it OR assume it's available via the PATH, this code searches the most common locations to insure it is available. It is an example of good coding when you are writing for a universal audience.
Changing is best done by commenting out the original code (or - heaven forbid!! temporarily using a GOTO to jump over it) and adding your own code changes. Follow this with lots of testing!! You should be aware that when you modify someone else's code, they shouldn't be expected to help you debug it. But by all means, tear it apart and rewrite it. If we all didn't do that, we wouldn't improve each others code - and we'd all close our minds to new ideas.
Finally, if you make changes that add functionality, or potentially improve performance or reliability, post your chanegs for discussion and review in the Scripts topic with an explaination of what you did.
Glenn
_________________________
Actually I
am a Rocket Scientist!
