Search found 7198 matches

by Alexander Riedel
Thu Aug 20, 2009 2:46 am
Forum: PrimalScript
Topic: New Open Save dialog issues
Replies: 3
Views: 895

New Open Save dialog issues

Well, Windows 7 is, as all new OSes, a new set of challenges. :-) I will look into those.
by Alexander Riedel
Wed Aug 19, 2009 5:14 am
Forum: PrimalScript
Topic: Primal Script using Powershell V1 not V2
Replies: 8
Views: 1724

Primal Script using Powershell V1 not V2

PrimalScript uses the PowerShell engine directly when you run scripts internally. That engine is in an assembly called System.Management.Automation.dll. The V1 version is usually found here: C:Program FilesReference AssembliesMicrosoftWindowsPowerShellv1.0 We do not specifically use that assembly, b...
by Alexander Riedel
Wed Aug 19, 2009 3:31 am
Forum: PrimalScript
Topic: Primal Script using Powershell V1 not V2
Replies: 8
Views: 1724

Primal Script using Powershell V1 not V2

PrimalScript uses the designated assembly to run PowerShell on a system regardless of PowerShell version.

I suggest you post in a Microsoft powershell forum to obtain information on how to remove old assembly versions.

We will try to do the same from our end.

Alex
by Alexander Riedel
Wed Aug 19, 2009 3:24 am
Forum: Wish List and Feature Requests
Topic: Feature Request: Streamline Updates
Replies: 6
Views: 691116

Feature Request: Streamline Updates

The PrimalScript update process is pretty much the same it has always been: You get the file, remove the old version and install the new one. It takes 44 seconds on my old machine here, including downloading. The questions I posed where pertinent to clear what you where aiming at. If you don't feel ...
by Alexander Riedel
Tue Aug 18, 2009 5:22 pm
Forum: PrimalScript
Topic: save as dialog,FileName length bug
Replies: 2
Views: 1148

save as dialog,FileName length bug

It will be fixed in the next service build.
In the meantime resize the dialog to increase the width of the field.

Alex
by Alexander Riedel
Tue Aug 18, 2009 5:02 pm
Forum: PrimalScript
Topic: PrimalScript 2009 Script Packager Crashes
Replies: 4
Views: 373

PrimalScript 2009 Script Packager Crashes

You are specifying the output file as c:CkPwdAge.exe While this is a valid file name specifier on an NTFS drive and designates a named stream called CkPwdAge.exe in a file named "C", it is not supported by PrimalScript's packager. You cannot store a package in an alternate stream of a file. You can ...
by Alexander Riedel
Tue Aug 18, 2009 3:20 am
Forum: PrimalScript
Topic: PrimalScript 2009 Script Packager Crashes
Replies: 4
Views: 373

PrimalScript 2009 Script Packager Crashes

Assuming you are using Script -> Script Packager...
Please go to "C:Documents and SettingsAlexMy DocumentsSAPIENScript Packages" and locate the .ESP file with the name you specified in the packager.
Please email that file to support@sapien.com.
by Alexander Riedel
Mon Aug 17, 2009 7:16 am
Forum: PrimalScript
Topic: PrimalPackager
Replies: 2
Views: 289

PrimalPackager

Still being worked on. Large number of early tester feedback and changes brought on by Windows 7 made it necessary to go back to the drawing board.

It's not dead by any means.

Alex
by Alexander Riedel
Mon Aug 17, 2009 7:13 am
Forum: Productivity Pack Support
Topic: ActiveXPosh IIS6 crash
Replies: 11
Views: 7064

ActiveXPosh IIS6 crash

That sounds like the component isn't even registered.
Did you run regasm on the dll?

If yes, go here:
http://www.dependencywalker.com/

and check the dependencies of the dll on YOUR system.
It will tell you what is missing, if anything.

Alex
by Alexander Riedel
Mon Aug 17, 2009 4:22 am
Forum: PrimalScript
Topic: Large .exe using script packager
Replies: 5
Views: 737

Large .exe using script packager

I'll see what we can do.