Search found 6534 matches

by Alexander Riedel
Tue Jun 19, 2018 7:43 am
Forum: PowerShell Studio
Topic: PowerShell Cache Builder High Memory/CPU Usage
Replies: 1
Views: 48

Re: PowerShell Cache Builder High Memory/CPU Usage

The Cachebuilder process gets started when it is detected that the cache is out of date, the product gets re-installed or, as you did, instruct PowerShell Studio to rebuild the cache. As the name 'cachebuilder' implies, that is what it does. Since it has to load every single module installed on your...
by Alexander Riedel
Sun Jun 17, 2018 1:22 pm
Forum: Customer Service
Topic: Oracle DB using IQDriver through Sapien PowerShell Studio
Replies: 1
Views: 126

Re: Oracle DB using IQDriver through Sapien PowerShell Studio

Please post in the correct product forum or in the general PowerShell section and provide the information requested.
From your question it is unclear whether this refers to PowerShell Studio specifically or Windows PowerShell in general.
by Alexander Riedel
Fri Jun 15, 2018 3:36 pm
Forum: Installation Issues
Topic: Installing Powershell Studio via System Center Configuration Manager (SCCM)
Replies: 1
Views: 161

Re: Installing Powershell Studio via System Center Configuration Manager (SCCM)

Basically it is a Windows Installer bug. One that is not very likely to be fixed by Microsoft. You will need to obtain the prerequisites and install them separately beforehand via SCCM. Please email support@sapien.com and we can provide you with the download links. Please include your SAPIEN ID and ...
by Alexander Riedel
Wed Jun 13, 2018 1:08 pm
Forum: PowerShell Studio
Topic: MSI plus batch file
Replies: 5
Views: 406

Re: MSI plus batch file

Please be a little more precise in your post. "Did not accept folder.", for example. The dev team tells me they do not validate folders, so you need to tell who did not accept what. "Did not like command". I doubt there was a messagebox that said "Ew, I do not like this command" :D And "did not work...
by Alexander Riedel
Wed Jun 13, 2018 10:52 am
Forum: PowerShell Studio
Topic: MSI plus batch file
Replies: 5
Views: 406

Re: MSI plus batch file

Specify C:\Windows\Sysnative\cmd.exe
That should call the right thing on 32 and 64 bit machines
(Note: I did not try that)
by Alexander Riedel
Wed Jun 13, 2018 8:44 am
Forum: PowerShell Studio
Topic: MSI plus batch file
Replies: 5
Views: 406

Re: MSI plus batch file

Try adding it as
cmd /c file.bat
I am assuming this is for a custom action?
by Alexander Riedel
Tue Jun 12, 2018 10:55 am
Forum: VBScript
Topic: VBS to exe using PrimalScript 2018 arguments
Replies: 4
Views: 197

Re: VBS to exe using PrimalScript 2018 arguments

Don't know what your script does or what you call "wait for arguments" means.
Generally you would use InputBox for getting user input.
Can you provide an actual code sample?
by Alexander Riedel
Mon Jun 11, 2018 4:28 pm
Forum: PrimalScript
Topic: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts
Replies: 11
Views: 379

Re: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts

Oh that is my bad. We changed compiler / Visual Studio version between your version and what I have and that simply will not go together.
My apologies, I should have thought of that.
Please try with the next service build that will include all the new bits.
by Alexander Riedel
Sun Jun 10, 2018 7:33 am
Forum: PrimalScript
Topic: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts
Replies: 11
Views: 379

Re: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts

There is some old setting that would on demand connect the VBScript debugger to the ActiveX Powershell host. It should not be active and would also apply to 32 bit, but it would explain what you see. So I am attaching a version of scriptdebugger64.dll with that particular stretch of code removed to ...
by Alexander Riedel
Sun Jun 10, 2018 6:06 am
Forum: PrimalScript
Topic: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts
Replies: 11
Views: 379

Re: PrimalScript 2018 Not Allowing 64 bit Debug on VBS Scripts

I will investigate. There should not be any dependency on PowerShell V2 being installed. If that is indeed the case it will be removed. As you correctly state this would be a bug. Please stand by.