Registered: Nov 2002
From: Shropshire, England

Could not load: C:\DOCUME~1\WINDOW~1\LOCALS~1\Temp\nst22.tmp\nsExec.dll

I get this when trying to use nsExec
It worked before, but stopped working now.
All I have done is moved parts of my nsi script to seperate nsi files, since my script got so large.
Is this a bug due to the nsExec command being called from in a seperate (!include) file?

I ran my old map-compiler script (when nsExec worked), and it still happens.

Also, how do I use LogText?

-Stuart

__________________
afrowuk.co.uk

Quick Link | Report this post to a moderator | IP: Logged

Registered: Aug 2000
From:

Did you look to see if the file was there?

Quick Link | Report this post to a moderator | IP: Logged

Registered: Oct 2001
From: Jerusalem, Israel

b0 or b1? Please attach the script.

__________________
NSIS FAQ | NSIS Home Page | Donate $
"I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Quick Link | Report this post to a moderator | IP: Logged

Registered: Oct 2001
From: Jerusalem, Israel

To use LogText you have to compile your own version of NSIS with #define NSIS_CONFIG_LOG uncommented in Source\exehead\config.h. Then use LogSet to turn on/off the log and then you'll be able to use LogText (I think you can skip LogSet, not sure about it).

__________________
NSIS FAQ | NSIS Home Page | Donate $
"I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Quick Link | Report this post to a moderator | IP: Logged

Registered: Nov 2002
From: Shropshire, England

Another question...
Is there any way of copying all text in the LogText window, and then pasting it into a file?
I mean a script to do it, instead of the user doing it manually.

-Stuart

__________________
afrowuk.co.uk

Quick Link | Report this post to a moderator | IP: Logged

Registered: Oct 2001
From: Jerusalem, Israel

Well, you can do what NSIS does when the user right-clicks the log and chooses copy. This will require System.dll and I don't have much time now so you'll have to wait for tomorrow unless someone will figure it out before me

__________________
NSIS FAQ | NSIS Home Page | Donate $
"I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Quick Link | Report this post to a moderator | IP: Logged

Registered: Nov 2002
From: Shropshire, England

How is the figuring it out going

-Stuart

__________________
afrowuk.co.uk

Quick Link | Report this post to a moderator | IP: Logged

Registered: Oct 2001
From: Jerusalem, Israel

Here it is:
http://nsis.sourceforge.net/archive...;instances=0,11

__________________
NSIS FAQ | NSIS Home Page | Donate $
"I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Quick Link | Report this post to a moderator | IP: Logged

Registered: Nov 2007
From:

Kichik, I am using your Dump Log file script for the installer - but it doesn't log the uninstall -- is there a way to adapt this script to log the uninstall information??

thanks so much for the help!

Quick Link | Report this post to a moderator | IP: Logged

Registered: Oct 2001
From: Jerusalem, Israel

Well, the function in the example is not built for the uninstaller as you can see by its lack of "un." prefix. If you wish to use it in the uninstaller, rename it to un.DumpLog.

__________________
NSIS FAQ | NSIS Home Page | Donate $
"I hear and I forget. I see and I remember. I do and I understand." -- Confucius

Quick Link | Report this post to a moderator | IP: Logged