issue on scripting syntax on x64

The following script runs normally on a x32 environment, and end without
finding the exe on a x64. What could be the issue?

Dim WSHShell
Set WSHShell = CreateObject("WScript.Shell")
WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
WSHShell.CurrentDirectory = WSHShell.CurrentDirectory & "\my_program_folder"
WSHShell.Run "my_exe.exe /param1 /param2"

Any help would be appreciated.

"Tyler Durden" <> wrote in message
news:...
> The following script runs normally on a x32 environment, and end without
> finding the exe on a x64. What could be the issue?
>
> Dim WSHShell
> Set WSHShell = CreateObject("WScript.Shell")
> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
> "\my_program_folder"
> WSHShell.Run "my_exe.exe /param1 /param2"
>
> Any help would be appreciated.

Have you tried using a fully qualified path for your .exe file, instead of
relying on a working directory that may or may not be correct?

"Pegasus [MVP]" <> wrote in message
news:...
>
> "Tyler Durden" <> wrote in message
> news:...
>> The following script runs normally on a x32 environment, and end without
>> finding the exe on a x64. What could be the issue?
>>
>> Dim WSHShell
>> Set WSHShell = CreateObject("WScript.Shell")
>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>> "\my_program_folder"
>> WSHShell.Run "my_exe.exe /param1 /param2"
>>
>> Any help would be appreciated.
>
> Have you tried using a fully qualified path for your .exe file, instead of
> relying on a working directory that may or may not be correct?
>

If you are certain the exe is in the specified subfolder of the folder where
the VBScript is saved, perhaps something similar to this would work better:
===========
Dim WSHShell, strCmd

Set WSHShell = CreateObject("WScript.Shell")
strCmd = "%comspec% /c """ & Wscript.ScriptFullName _
& "\..\my_program_folder\my_exe.exe"" /param1 /param2"
Wscript.Echo strCmd
WSHShell.Run strCmd, 2
========
The statement to echo strCmd is for troubleshooting, to make sure the
command is correct. Note the path and file name are in quotes, and quotes in
a quoted string must be doubled.

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--

full qualified path is not possible as the app is portable, so drive letter
can change.

"Pegasus [MVP]" <> wrote in message
news:...
>
> "Tyler Durden" <> wrote in message
> news:...
>> The following script runs normally on a x32 environment, and end without
>> finding the exe on a x64. What could be the issue?
>>
>> Dim WSHShell
>> Set WSHShell = CreateObject("WScript.Shell")
>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>> "\my_program_folder"
>> WSHShell.Run "my_exe.exe /param1 /param2"
>>
>> Any help would be appreciated.
>
> Have you tried using a fully qualified path for your .exe file, instead of
> relying on a working directory that may or may not be correct?
>

on x32 still worked fine, could not test it on a x64 yet. would be possible
to do it without cmd.exe?

thank you!

"Richard Mueller [MVP]" <rlmueller-> wrote in
message news:%...
>
> "Pegasus [MVP]" <> wrote in message
> news:...
>>
>> "Tyler Durden" <> wrote in message
>> news:...
>>> The following script runs normally on a x32 environment, and end without
>>> finding the exe on a x64. What could be the issue?
>>>
>>> Dim WSHShell
>>> Set WSHShell = CreateObject("WScript.Shell")
>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>>> "\my_program_folder"
>>> WSHShell.Run "my_exe.exe /param1 /param2"
>>>
>>> Any help would be appreciated.
>>
>> Have you tried using a fully qualified path for your .exe file, instead
>> of relying on a working directory that may or may not be correct?
>>
>
> If you are certain the exe is in the specified subfolder of the folder
> where the VBScript is saved, perhaps something similar to this would work
> better:
> ===========
> Dim WSHShell, strCmd
>
> Set WSHShell = CreateObject("WScript.Shell")
> strCmd = "%comspec% /c """ & Wscript.ScriptFullName _
> & "\..\my_program_folder\my_exe.exe"" /param1 /param2"
> Wscript.Echo strCmd
> WSHShell.Run strCmd, 2
> ========
> The statement to echo strCmd is for troubleshooting, to make sure the
> command is correct. Note the path and file name are in quotes, and quotes
> in a quoted string must be doubled.
>
> --
> Richard Mueller
> MVP Directory Services
> Hilltop Lab - http://www.rlmueller.net
> --
>
>

I think most exe program will run fine without using %comspec% /c. In that
case:

strCmd = """" & Wscript.ScriptFullName _
& "\..\my_program_folder\my_exe.exe"" /param1 /param2"

This still encloses the path/filename in quotes, in case there are any
spaces in the path.

--
Richard Mueller
MVP Directory Services
Hilltop Lab - http://www.rlmueller.net
--

"Tyler Durden" <> wrote in message
news:eGU6K%...
> on x32 still worked fine, could not test it on a x64 yet. would be
> possible to do it without cmd.exe?
>
> thank you!
>
> "Richard Mueller [MVP]" <rlmueller-> wrote in
> message news:%...
>>
>> "Pegasus [MVP]" <> wrote in message
>> news:...
>>>
>>> "Tyler Durden" <> wrote in message
>>> news:...
>>>> The following script runs normally on a x32 environment, and end
>>>> without finding the exe on a x64. What could be the issue?
>>>>
>>>> Dim WSHShell
>>>> Set WSHShell = CreateObject("WScript.Shell")
>>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>>>> "\my_program_folder"
>>>> WSHShell.Run "my_exe.exe /param1 /param2"
>>>>
>>>> Any help would be appreciated.
>>>
>>> Have you tried using a fully qualified path for your .exe file, instead
>>> of relying on a working directory that may or may not be correct?
>>>
>>
>> If you are certain the exe is in the specified subfolder of the folder
>> where the VBScript is saved, perhaps something similar to this would work
>> better:
>> ===========
>> Dim WSHShell, strCmd
>>
>> Set WSHShell = CreateObject("WScript.Shell")
>> strCmd = "%comspec% /c """ & Wscript.ScriptFullName _
>> & "\..\my_program_folder\my_exe.exe"" /param1 /param2"
>> Wscript.Echo strCmd
>> WSHShell.Run strCmd, 2
>> ========
>> The statement to echo strCmd is for troubleshooting, to make sure the
>> command is correct. Note the path and file name are in quotes, and quotes
>> in a quoted string must be doubled.
>>
>> --
>> Richard Mueller
>> MVP Directory Services
>> Hilltop Lab - http://www.rlmueller.net
>> --
>>
>>
>
>

"Tyler Durden" <> wrote in message
news:...
> full qualified path is not possible as the app is portable, so drive
> letter can change.

That only means you cannot pre-specify what the fully qualified path is. But
surely your script can determine what it should be, find the file, and then
run it?

/Al

> "Pegasus [MVP]" <> wrote in message
> news:...
>>
>> "Tyler Durden" <> wrote in message
>> news:...
>>> The following script runs normally on a x32 environment, and end without
>>> finding the exe on a x64. What could be the issue?
>>>
>>> Dim WSHShell
>>> Set WSHShell = CreateObject("WScript.Shell")
>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>>> "\my_program_folder"
>>> WSHShell.Run "my_exe.exe /param1 /param2"
>>>
>>> Any help would be appreciated.
>>
>> Have you tried using a fully qualified path for your .exe file, instead
>> of relying on a working directory that may or may not be correct?
>>
>
>

That's what I want


"Al Dunbar" <> wrote in message
news:%23s$...
>
> "Tyler Durden" <> wrote in message
> news:...
>> full qualified path is not possible as the app is portable, so drive
>> letter can change.
>
> That only means you cannot pre-specify what the fully qualified path is.
> But surely your script can determine what it should be, find the file, and
> then run it?
>
> /Al
>
>> "Pegasus [MVP]" <> wrote in message
>> news:...
>>>
>>> "Tyler Durden" <> wrote in message
>>> news:...
>>>> The following script runs normally on a x32 environment, and end
>>>> without finding the exe on a x64. What could be the issue?
>>>>
>>>> Dim WSHShell
>>>> Set WSHShell = CreateObject("WScript.Shell")
>>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>>>> "\my_program_folder"
>>>> WSHShell.Run "my_exe.exe /param1 /param2"
>>>>
>>>> Any help would be appreciated.
>>>
>>> Have you tried using a fully qualified path for your .exe file, instead
>>> of relying on a working directory that may or may not be correct?
>>>
>>
>>
>
>
>

I'll try and give feedback here.

"Richard Mueller [MVP]" <rlmueller-> wrote in
message news:%...
>I think most exe program will run fine without using %comspec% /c. In that
>case:
>
> strCmd = """" & Wscript.ScriptFullName _
> & "\..\my_program_folder\my_exe.exe"" /param1 /param2"
>
> This still encloses the path/filename in quotes, in case there are any
> spaces in the path.
>
> --
> Richard Mueller
> MVP Directory Services
> Hilltop Lab - http://www.rlmueller.net
> --
>
> "Tyler Durden" <> wrote in message
> news:eGU6K%...
>> on x32 still worked fine, could not test it on a x64 yet. would be
>> possible to do it without cmd.exe?
>>
>> thank you!
>>
>> "Richard Mueller [MVP]" <rlmueller-> wrote in
>> message news:%...
>>>
>>> "Pegasus [MVP]" <> wrote in message
>>> news:...
>>>>
>>>> "Tyler Durden" <> wrote in message
>>>> news:...
>>>>> The following script runs normally on a x32 environment, and end
>>>>> without finding the exe on a x64. What could be the issue?
>>>>>
>>>>> Dim WSHShell
>>>>> Set WSHShell = CreateObject("WScript.Shell")
>>>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
>>>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
>>>>> "\my_program_folder"
>>>>> WSHShell.Run "my_exe.exe /param1 /param2"
>>>>>
>>>>> Any help would be appreciated.
>>>>
>>>> Have you tried using a fully qualified path for your .exe file, instead
>>>> of relying on a working directory that may or may not be correct?
>>>>
>>>
>>> If you are certain the exe is in the specified subfolder of the folder
>>> where the VBScript is saved, perhaps something similar to this would
>>> work better:
>>> ===========
>>> Dim WSHShell, strCmd
>>>
>>> Set WSHShell = CreateObject("WScript.Shell")
>>> strCmd = "%comspec% /c """ & Wscript.ScriptFullName _
>>> & "\..\my_program_folder\my_exe.exe"" /param1 /param2"
>>> Wscript.Echo strCmd
>>> WSHShell.Run strCmd, 2
>>> ========
>>> The statement to echo strCmd is for troubleshooting, to make sure the
>>> command is correct. Note the path and file name are in quotes, and
>>> quotes in a quoted string must be doubled.
>>>
>>> --
>>> Richard Mueller
>>> MVP Directory Services
>>> Hilltop Lab - http://www.rlmueller.net
>>> --
>>>
>>>
>>
>>
>
>

Have you echo'd out WSHShell.CurrentDirectory just to make sure it is where
you think it is? Also do you have "On Error Resume Next" in the script?

"Tyler Durden" wrote:

> That's what I want
>
>
> "Al Dunbar" <> wrote in message
> news:%23s$...
> >
> > "Tyler Durden" <> wrote in message
> > news:...
> >> full qualified path is not possible as the app is portable, so drive
> >> letter can change.
> >
> > That only means you cannot pre-specify what the fully qualified path is.
> > But surely your script can determine what it should be, find the file, and
> > then run it?
> >
> > /Al
> >
> >> "Pegasus [MVP]" <> wrote in message
> >> news:...
> >>>
> >>> "Tyler Durden" <> wrote in message
> >>> news:...
> >>>> The following script runs normally on a x32 environment, and end
> >>>> without finding the exe on a x64. What could be the issue?
> >>>>
> >>>> Dim WSHShell
> >>>> Set WSHShell = CreateObject("WScript.Shell")
> >>>> WSHShell.CurrentDirectory = WScript.ScriptFullName & "\.."
> >>>> WSHShell.CurrentDirectory = WSHShell.CurrentDirectory &
> >>>> "\my_program_folder"
> >>>> WSHShell.Run "my_exe.exe /param1 /param2"
> >>>>
> >>>> Any help would be appreciated.
> >>>
> >>> Have you tried using a fully qualified path for your .exe file, instead
> >>> of relying on a working directory that may or may not be correct?
> >>>
> >>
> >>
> >
> >
> >
>
>
>