Hello guys.
I'm trying to get the System Plugin work with me.
Everything I use it I, the EXE always that it's used in crashes.
My theory is that either I'm not putting some needed stuff in the script for the System Plugin to work or I've got a corrupt system.dll file.
So if somebody could either look at my script or link to a new download of the system plugin (I can't find it anywhere, I've googled and it does NOT come with NSIS).
Thanks.
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on BlueSky
Follow us on Facebook
Follow us on LinkedIn
Follow us on Mastodon
Follow us on Twitter
System plugin does come with NSIS - NSIS\Plugins\System.dll
Anyway, if I had to guess, you can't set an environment variable named '~'
I got that from TaffinFoxCroft's Python Portable code.
The system plugin does NOT come with it. I've looked and it's not in there, I've tried the portable version and the regular.
Thanks anyway.
System::Call 'Kernel32::SetEnvironmentVariableA(t, t) i("~", "$EXEDIR\$SETTINGSDIRECTORY").r0'
I've never heard of the ~ variable. If you run phenny via python portable, it does work portable. At least one that I used worked.
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
Hello gluxon. First things first: the C isn't a capital in my name.
Second of all, the system plugin does actually come with NSIS, chances are it got deleted somewhere down the line. Try re-installing the latest version.
The reason to why Python Portable redirects ~ is because a lot of python apps are written to be cross-platform (but mainly linux) so they use ~ which on linux is your home directory, but on windows is the equivalent to USERPROFILE. So by redirecting ~ not only is it making IDLE work properly, its also letting a lot of python apps work portably as well.
But there’s no sense crying over every mistake,
You just keep on trying till you run out of cake.
It is accessed as ~ under *nix, but the environment variable is HOME (%HOME%, $HOME). DON'T try setting ~ - it won't (or at least shouldn't) work.
I am a Christian and a developer and moderator here.
“A soft answer turns away wrath, but a harsh word stirs up anger.” – Proverbs 15:1
Still, that doesn't really help.
actually it does to be honest, your problem is that you are not understanding the said solution
see the HOME, TEMP are all Windows Variables, so using ~ is not a valid variable in windows, your best bet is to use HOME
your friendly neighbourhood moderator Zach Thibeau
Yes, I've gotten rid of that but the EXE still crashes on launch.
Alright, I haven't seen your script (just read the comments here), but are you using the following code?
I guess that "$EXEDIR\$SETTINGSDIRECTORY" causes the problem, because its something like "X:\PortableApps\ExampleApp\X:\PortableApps\ExampleApp\Data\settings".
Try that:
Actually, no.
This is a launcher I'm not really planning on releasing for PortableApps.com
And I prefer making $SettingsDirectory "Data\settings" instead of "[x]:\PortableApps\[AppName]Portable\Data\settings"
Thanks for helping though.
*looks at script now*
Maybe it crashes because you redirect APPDATA and HOME. Some apps don't like that, so try redirecting only HOME.
Actually...
I tried this yesterday but forgot to post.
All my plugins are crashing.
I took the system.dll calls out of the script and tried it (3rd time I've done this, but with a different result), the FindProcDLL crashes, then, I take that out and the newadvsplash.dll crashes.
I know it's crashing because windows vista is reporting it, with the plugin's name.
What is up?
This isn't happening with any of my other 4 or 5 Launchers.
NSIS Portable or NSIS installed?
Too many lonely hearts in the real world
Too many bridges you can burn
Too many tables you can't turn
Don't wanna live my life in the real world
BOTH!!!
I've even reinstalled... like 3 times.
Are you somehow using unicode plugins with an ANSI version of NSIS or vice versa?