SAPIEN Technologies

I know that when I packaged the HTA script in Admin Script Editor, Admin Script Editor has a pathvariable generated during the execution of the packaged script. It was through this path variable that I could use to output the log file to the packaged HTA script's current folder. I wish PrimalScript ...

I know that when I packaged the HTA script in Admin Script Editor, Admin Script Editor has a pathvariable generated during the execution of the packaged script. It was through this path variable that I could use to output the log file to the packaged HTA script's current folder. I wish PrimalScript ...

I wrote an HTA script using the VBscript language. When I package my HTA script with PrimalScript 2009, I have the extracted script file output to the %temp% folder. I have a need to write the information generated by this HTA script to a file in the same folder as the packaged script. What is the w...

I wrote an HTA script using the VBscript language. When I package my HTA script with PrimalScript 2009, I have the extracted script file output to the %temp% folder. I have a need to write the information generated by this HTA script to a file in the same folder as the packaged script. What is the w...

HTA packaged script

I repackaged the script with the latest version of PrimalScript, and the error appears only at the end of the run. However, if I ran the unpackaged script using cscript, no error shows up. The script was packaged with PrimalScript installed on Windows XP Service Pack 3. I need to package the script ...

I did not encode the vbscript. I simply packaged the script right out of PrimalScript editor.

The script is very straightforward - no other script to call within the script except the functions and subroutines within the script.

But when I ran the script outside of the PrimalScript package (using cscript), I don't see this error.

Regardless of where the issue is, the packaged script should indicate the line where the error was generated from.

Alexander, I did not use any strange characters within the script. Nor did I use any international characters. Since the packaged script does not show any line number when it generated this error, I cannot pin point where location of the code that generated this error. The fact that when I ran the s...