> Have tcl scripts in .bat files that expect arguments. Works fine in
> XP. When run in win7, the script does not receive the values passed as
> parameters.
> Net: argc is 0; argv is empty.
> Have taken UAC to lowest level. Have changed the properties to enable,
> read, write, execute, etc.
> All scripts are in c:\program files (x86)\star.
> e.g
> runtranslator.bat contains the following
> shell-translatorTCL.bat "/Star/sims/source_scenarios/IF_test.ssc"
> shell-translatorTCL.bar contains the following
> cd \Star\SIDE\sp_translator
> sdd_scripttranslator.tcl %1 %2 %3 %4 %5 %6 %7 %8 %9
I see that you rely on the associations. What happens if you change the
line to:
On Tuesday, May 8, 2012 10:53:38 AM UTC-4, Arjen Markus wrote:
> On 2012-05-08 16:39, rick h wrote:
> > Have tcl scripts in .bat files that expect arguments. Works fine in
> > XP. When run in win7, the script does not receive the values passed as
> > parameters.
> > Net: argc is 0; argv is empty.
> > Have taken UAC to lowest level. Have changed the properties to enable,
> > read, write, execute, etc.
> > All scripts are in c:\program files (x86)\star.
> > e.g
> > runtranslator.bat contains the following
> > shell-translatorTCL.bat "/Star/sims/source_scenarios/IF_test.ssc"
> > shell-translatorTCL.bar contains the following
> > cd \Star\SIDE\sp_translator
> > sdd_scripttranslator.tcl %1 %2 %3 %4 %5 %6 %7 %8 %9
> I see that you rely on the associations. What happens if you change the
> line to:
On Tuesday, May 8, 2012 1:52:13 PM UTC-4, rick h wrote:
> On Tuesday, May 8, 2012 10:53:38 AM UTC-4, Arjen Markus wrote:
> > On 2012-05-08 16:39, rick h wrote:
> > > Have tcl scripts in .bat files that expect arguments. Works fine in
> > > XP. When run in win7, the script does not receive the values passed as
> > > parameters.
> > > Net: argc is 0; argv is empty.
> > > Have taken UAC to lowest level. Have changed the properties to enable,
> > > read, write, execute, etc.
> > > All scripts are in c:\program files (x86)\star.
> > > e.g
> > > runtranslator.bat contains the following
> > > shell-translatorTCL.bat "/Star/sims/source_scenarios/IF_test.ssc"
> > > shell-translatorTCL.bar contains the following
> > > cd \Star\SIDE\sp_translator
> > > sdd_scripttranslator.tcl %1 %2 %3 %4 %5 %6 %7 %8 %9
> > I see that you rely on the associations. What happens if you change the
> > line to:
On Tuesday, May 8, 2012 10:53:38 AM UTC-4, Arjen Markus wrote:
> On 2012-05-08 16:39, rick h wrote:
> > Have tcl scripts in .bat files that expect arguments. Works fine in
> > XP. When run in win7, the script does not receive the values passed as
> > parameters.
> > Net: argc is 0; argv is empty.
> > Have taken UAC to lowest level. Have changed the properties to enable,
> > read, write, execute, etc.
> > All scripts are in c:\program files (x86)\star.
> > e.g
> > runtranslator.bat contains the following
> > shell-translatorTCL.bat "/Star/sims/source_scenarios/IF_test.ssc"
> > shell-translatorTCL.bar contains the following
> > cd \Star\SIDE\sp_translator
> > sdd_scripttranslator.tcl %1 %2 %3 %4 %5 %6 %7 %8 %9
> I see that you rely on the associations. What happens if you change the
> line to:
On Tuesday, May 8, 2012 1:56:41 PM UTC-4, rick h wrote:
> On Tuesday, May 8, 2012 1:52:13 PM UTC-4, rick h wrote:
> > On Tuesday, May 8, 2012 10:53:38 AM UTC-4, Arjen Markus wrote:
> > > On 2012-05-08 16:39, rick h wrote:
> > > > Have tcl scripts in .bat files that expect arguments. Works fine in
> > > > XP. When run in win7, the script does not receive the values passed as
> > > > parameters.
> > > > Net: argc is 0; argv is empty.
> > > > Have taken UAC to lowest level. Have changed the properties to enable,
> > > > read, write, execute, etc.
> > > > All scripts are in c:\program files (x86)\star.
> > > > e.g
> > > > runtranslator.bat contains the following
> > > > shell-translatorTCL.bat "/Star/sims/source_scenarios/IF_test.ssc"
> > > > shell-translatorTCL.bar contains the following
> > > > cd \Star\SIDE\sp_translator
> > > > sdd_scripttranslator.tcl %1 %2 %3 %4 %5 %6 %7 %8 %9
> > > I see that you rely on the associations. What happens if you change the
> > > line to:
On Tuesday, May 8, 2012 2:47:42 PM UTC-4, rick h wrote:
> On Tuesday, May 8, 2012 1:56:41 PM UTC-4, rick h wrote:
> > On Tuesday, May 8, 2012 1:52:13 PM UTC-4, rick h wrote:
> > > On Tuesday, May 8, 2012 10:53:38 AM UTC-4, Arjen Markus wrote:
> > > > On 2012-05-08 16:39, rick h wrote:
> > > > > Have tcl scripts in .bat files that expect arguments. Works fine in
> > > > > XP. When run in win7, the script does not receive the values passed as
> > > > > parameters.
> > > > > Net: argc is 0; argv is empty.
> > > > > Have taken UAC to lowest level. Have changed the properties to enable,
> > > > > read, write, execute, etc.
> > > > > All scripts are in c:\program files (x86)\star.
Op woensdag 9 mei 2012 00:49:31 UTC+2 schreef Andreas Leitgeb het volgende:
> rick h wrote:
> > One last thought (question): why, using references, was the script initiated, but no parms passed?
> Probably, because the "open"-binding for extension .tcl specifies
> tclsh.exe(with correct path) but no parameters.
I have checked the association for .tcl files on my system:
assoc .tcl
.tcl=ActiveTclScript
Apparently the definition of "ActiveTclScript" is: c:\tcl86\bin\wish86.exe "%1" %*
(That is the information I get from the file manage I use. I have no clue as to how to set that, but it is probably stored in the Windows registry)
The point is: with "%1" wish86 gets the file name, with %* it probably gets all the other command-line parameters as well.
