in reply to More on Hiding DOS Windows
in thread Hiding the DOS window..

Is there a slight difference in how the registry associations are set up in the two cases, e.g., in what is quoted and what isn't? It's been a couple of years since I used Windows enough to mess with registry assocations, so the details are fuzzy in my mind, but ISTR that sometimes little easy-to-miss things like whether the %1 was inside the same quotes as the filepath or a separate set of quotes could make a big difference. Also you don't mention what happens if you double-click a .pl file in explorer.exe; that might help diagnose whether the problem has more to do with the association itself (more likely) or the way the big commercial program is handling it (also possible).

"In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."  — Pratico & Van Pelt, BBHG, p68

Replies are listed 'Best First'.
Re^2: More on Hiding DOS Windows
by wa4otj (Beadle) on Feb 20, 2005 at 17:14 UTC
    The "big commercial program" (BCP) masks how it handles it, so I don't know exactly what it is doing. BUT, if I set up the call as "Run Program" "\Perl\bin\wperl.exe" with parameters of "Perlscript.pl" "Parameters", it works perfectly. If instead, I make it "Run Program" "Perlscript.pl" "Parameters" the parameters are lost when file associations are set to call wperl for .pl extensions, whereas if the associations are set for perl.exe, the parameters are not lost.

    It may be that I will have to change every call to the first format. That might be acceptable, but it will mean a lot of work going thru the massive data set and locating every place a Perl script has been inserted. I don't even mind the work, it's the mistakes I will make doing it, plus the fact that when reviewing the data for troubleshooting purposes BCP hides the actual parameters. Thus I cannot easily tell at any point what Perl script is being invoked if I make these changes. Annoying.

    Looking at the registry, I don't really see any difference in how they are set up. To change the associations I just right-click on a .pl file and select open with... Choose program... and select Perl.exe or Wperl.exe. It seems pretty transparant, but I am tripping over this silly little anomaly.

    Thanks for the help. Any additional suggestions are most welcome.

    Nat

[reply]
      To change the associations I just right-click on a .pl file and select open with... Choose program... and select Perl.exe or Wperl.exe.

      I am totally guessing here, but this might be related to your problem. That method of setting up associations does not expose all the details to you. You might ought to look under View->Folder Options->File Types to see the details of how the file association is set up. It is quite possible that the association is not getting set up 100% correctly. If you've never worked with the File Types settings before, consult your local Windows guru.

      "In adjectives, with the addition of inflectional endings, a changeable long vowel (Qamets or Tsere) in an open, propretonic syllable will reduce to Vocal Shewa. This type of change occurs when the open, pretonic syllable of the masculine singular adjective becomes propretonic with the addition of inflectional endings."  — Pratico & Van Pelt, BBHG, p68
[reply]
        That got it. Thanks!

        Now my scripts are running invisibly with no DOS Boxes popping up and annoying the users.

        Thanks All,

        Nat

[reply]

      It sounds like BCP is not passing the parameters correctly. Either fix the association of .pl files to use wperl or try "Run Program" "\Perl\bin\wperl.exe" "Perlscript.pl Parameters".

[reply]

In Section Seekers of Perl Wisdom