I will move this thread to the registered users section then. Please make sure to register your license key so you have access to the appropriate forum section.
Search found 8476 matches
- Tue Nov 11, 2008 2:26 am
- Forum: PrimalScript
- Topic: Multiple PrimalScript 2007 and RunAs
- Replies: 6
- Views: 1602
- Tue Nov 11, 2008 1:45 am
- Forum: PrimalScript
- Topic: Multiple PrimalScript 2007 and RunAs
- Replies: 6
- Views: 1602
Multiple PrimalScript 2007 and RunAs
Is this a trial version?
- Mon Nov 10, 2008 3:55 am
- Forum: PrimalScript
- Topic: Multiple PrimalScript 2007 and RunAs
- Replies: 6
- Views: 1602
Multiple PrimalScript 2007 and RunAs
Is this on a trial version? What edition? Build?
Please also provide OS information.
Please also provide OS information.
- Sat Nov 08, 2008 3:43 am
- Forum: PrimalScript
- Topic: Lines In Excess of 8128 characters
- Replies: 2
- Views: 1662
Lines In Excess of 8128 characters
Hi DJ. It's the same message you have seen for XML or some of your ASP code files where the line length exceeds 8128 characters. PrimalScript will insert newlines to be able to load the file. If you don't want the original file modified, do not save the reformatted file. At this time there is no way...
- Tue Nov 04, 2008 7:13 am
- Forum: PrimalScript
- Topic: F7 (Run) results flash by
- Replies: 3
- Views: 1398
F7 (Run) results flash by
You probably only see a DOS box with a command not found error.
Put the full path to python.exe in the place where "python.exe" is now by itself. That should make it work. Or, add pyhon's install path to your PATH statement.
Alex
Put the full path to python.exe in the place where "python.exe" is now by itself. That should make it work. Or, add pyhon's install path to your PATH statement.
Alex
- Mon Nov 03, 2008 3:29 am
- Forum: Wish List and Feature Requests
- Topic: Exit Code for Script Packager EXE
- Replies: 4
- Views: 3716
Exit Code for Script Packager EXE
I am running 4.5.574 and it appears to work fine.
As always it really depends on what options for the package you are using. Without knowing these it's hard to determine what you are looking at.
Alex
As always it really depends on what options for the package you are using. Without knowing these it's hard to determine what you are looking at.
Alex
VbScripts
Topic moved by moderator.
- Tue Oct 28, 2008 6:16 am
- Forum: Productivity Pack Support
- Topic: ActiveXPoSH syntax?
- Replies: 27
- Views: 24789
ActiveXPoSH syntax?
PowerShell.exe obviously has a return code that you could check if you where running each command as a seperate process. ActiveXPosh is a custom PowerShell host, it doesn't simply shell out to PowerShell.exe, so that does not apply here. All the Cmdlets you run from ActiveXPosh run in the same shell...
- Tue Oct 28, 2008 5:56 am
- Forum: PrimalScript
- Topic: PS 4.1 E running on vista 64
- Replies: 20
- Views: 5079
PS 4.1 E running on vista 64
This problem seems to be systematic to 64 bit Windows versions.
The way an argument it passed to an executable is not differentiating between a 32 and 64 bit process.
We'll check how we can work around this.
Alex
The way an argument it passed to an executable is not differentiating between a 32 and 64 bit process.
We'll check how we can work around this.
Alex
- Tue Oct 28, 2008 5:53 am
- Forum: Productivity Pack Support
- Topic: ActiveXPoSH syntax?
- Replies: 27
- Views: 24789
ActiveXPoSH syntax?
PowerShell really has no 'exit codes'.
If you want to know what a cmdlet returned, assign it to a value and query that value.
Or am I misunderstanding something?
If you want to know what a cmdlet returned, assign it to a value and query that value.
Or am I misunderstanding something?