Does anyone have a copy of the Ansi KillProc NSIS plugin they'd be willing to send my way? I need it so I can compile the Chrome/Iron launcher, but the usual download site is down for maintenance and I can't seem to find a mirror.
Thanks!
New: Run-Command (Dec 2, 2024), Platform 29.5.3 (Jun 27, 2024)
1,100+ portable packages, 1.1 billion downloads
No Ads Nov/Dec!, Please donate today
Does anyone have a copy of the Ansi KillProc NSIS plugin they'd be willing to send my way? I need it so I can compile the Chrome/Iron launcher, but the usual download site is down for maintenance and I can't seem to find a mirror.
Thanks!
I'm not sure what's up with most of the plug-in downloads ATM, but I still had an ansi & unicode version of KillProcDLL plug-in sitting on my laptop.
Hope that's the one you need.
Ps.: About the Chrome/Iron Password plug-in for unicode, I done some work on it a while ago, and it seemed to work well with nsis unicode.
Edit: forgot to include the plug-in link.
Formerly Gringoloco
Windows XP Pro sp3 x32
Thanks for the plugin. The download is blocked atm - restrictions again - but I can get to it on another PC fairly soon. I'll let you know if that's the right plugin.
I took a look at your provided plugin source (in the comment you linked to), but that appears to be Ansi. Is that the right source for NSISu?
Also, I'd be grateful if you could compile it for me; I don't have access to Visual Studio, can't install Visual Studio, and don't want to add another layer of complexity by trying to use MinGW again. I'm convinced that was at least part of my problem when I tried rewriting the plugin last time.
Thanks for all the help with this!
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."
I didn't recompile the actual plug-in cause I found out it currently actually deals with utf-8, so all I done is make use of the CallANSIPlugin.nsh header file (which is a slightly updated version of the one used in PAL already).
Have a look at the way the plug-in is called in PluginsEx.nsh, then look in GoogleChromePortable.nsi it's called like:
${ChromePasswords::ImportPasswords},
${ChromePasswords::ExportPasswords} and
${ChromePasswords::HashPassword}
If you're more happy with calling the plug-in IronPasswords, there is nothing stopping you renaming the macro's (renming the dll-file is also possible, but could be confusing in the future).
Ps.: It's your lucky day, the ChromeP source package also includes the ansi & unicode version of the KillProc plug-in .
Formerly Gringoloco
Windows XP Pro sp3 x32
I'd suggest keeping the name so it will be easier to sync any changes.
Sometimes, the impossible can become possible, if you're awesome!
I looked through the Chrome Portable launcher, especially PluginsEx.nsh, and I really like the way that looks. Yay for not having to mess with the DLL's internals.
Using your code, I managed to get PAL and PortablePasswords to play nicely together, so Iron 9 Portable is uploading now.
As John suggested, I'm leaving the macro and plugin names alone; the less complex future updates are, the better.
"The question I would like to know, is the Ultimate Question of Life, the Universe and Everything. All we know about it is that the Answer is Forty-two, which is a little aggravating."