Compartilhar via

A Small Percentage of Error...

  • Artigo

A recent post in the XP Embedded forum highlighted an issue related to running vb scripts on Embedded runtimes that I meant to blog about... so here it is!

It seems a bug fix that was incorporated into SP2 was only a partial fix (for whatever reason). This fix affected the registry keys for the Windows Script Host component- basically some of the registry keys were all missing the "%1%" parameters. The fix was applied and there was no apparent issues running scripts on Embedded. However, it turns out that this change did not cover all scenarios. It appears that another value is required in order to be able to run a script from a folder that has a space in the file name e.g Program Files.

If you are experiencing this issue then make the following changes to the registry key values in your configuration or in the runtime (remember to be careful whenever editing anything directly in the registry!):

HKLM\JSEFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\JSEFile\Shell\Open\Command %11%\WScript.exe "%1" %*

HKLM\JSFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\JSFile\Shell\Open\Command %11%\WScript.exe "%1" %*

HKLM\VBEFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\VBEFile\Shell\Open\Command %11%\WScript.exe "%1" %*

HKLM\VBSFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\VBSFile\Shell\Open\Command %11%\WScript.exe "%1" %*

HKLM\WSFFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\WSFFile\Shell\Open\Command %11%\WScript.exe "%1" %*

HKLM\WSHFile\Shell\Open2\Command %11%\CScript.exe "%1" %*

HKLM\WSHFile\Shell\Open\Command %11%\WScript.exe "%1" %*

(append the %* entry to the registry key value)

Happy scripting!

- Lynda