Do not post any licensing information in this forum.
Thank you for posting, manyone.
Here are some hints to help you get an accurate and complete answer to your question.
Ask in the best forum:
- - Scripting question? For questions about Windows PowerShell or other scripting languages, use Scripting Answers.
- Software question? For questions about PowerShell Studio, PrimalScript, or other SAPIEN products, use Product Support Forums for Registered Customers.
- Trial question? For questions about trial versions of any SAPIEN product, use Trial Software Questions.
Anticipate follow-up questions!
Did you remember to include the following?
- 1. Product, version and build
2. 32 or 64 bit product
3. Operating system, e.g. Windows 7 64 bit.
4. Attach a screenshot, if applicable
5. Attach logs, crash reports, etc., in a ZIP file
*** Make sure you do not post any licensing information ***
manyone wrote:is it possible to bypass the path of the executable to the unpacked executed script ?
I cannot tell what you are asking from the question. What do you mean by "bypass"? "Bypass" what?
i have packaged a hta script with PS
this executable is anywhere in the filesystem, let's say x:\any\where\script.exe
this exe is unpacked at execution time to c:\temp\12345.hta
but i need to know the path of the executable in the script, so the question again:
is it possible to give this information at execution time to the unpacked script (as argument/parameter or anything else) ?
Verify by adding this to the load procedure
i thought, that in an older version a system argument exists, which can passed to the script as argument, but i dont remember.
perhaps i think about a feature of another script packager.
You can post in Customer Service to see if the Sapien people have any ideas on how to get what you need.
Who is online
Users browsing this forum: No registered users and 1 guest