nsExec problem

Afrow UK · 17th February 2003, 20:52

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

rainwater · 18th February 2003, 03:39

Did you look to see if the file was there?

kichik · 18th February 2003, 14:53

b0 or b1? Please attach the script.

kichik · 18th February 2003, 18:24

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).

Afrow UK · 18th February 2003, 19:02

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

kichik · 18th February 2003, 19:10

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

Afrow UK · 19th February 2003, 18:07

How is the figuring it out going

-Stuart

kichik · 19th February 2003, 19:15

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

Irish2007 · 29th February 2008, 19:57

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!

kichik · 1st March 2008, 14:35

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.

yudyzhao · 16th February 2010, 11:17

kichik, I used your dumplog in my installer script. But the install.log content is unreadable at all because I created the installer by Unicode NSIS. Is there Unicode system.dll available or any other way to solve this problem?

Thanks a lot.

kichik · 16th February 2010, 11:26

System plug-in already supports Unicode. You just have to call the right functions (W instead of A) with the right parameter types (w instead of t).

yudyzhao · 17th February 2010, 14:00

kichik, thanks a lot. Problem is solved!

ptz · 8th December 2011, 14:32

Quote:

Originally Posted by kichik

System plug-in already supports Unicode. You just have to call the right functions (W instead of A) with the right parameter types (w instead of t).

I receive an unreadable file too (2.46 Unicode), and I don't understand the instruction kichik gave above regarding how to modify the function (http://nsis.sourceforge.net/Dump_log_to_file) to make it readable. Help is appreciated.

Thanks.

Afrow UK · 8th December 2011, 15:23

Use SendMessageW instead of SendMessageA and you need to use LVM_GETITEMTEXTW instead of LVM_GETITEMTEXT (google the value). You may also need to change the &t to &w but check the Unicode System plug-in readme for that.

Edit: You may also need to use different FileWrite functions but again check the Unicode NSIS manual.

Stu

ptz · 8th December 2011, 15:52

Oh, excellent, switching to LVM_GETITEMTEXTW did the trick. Thanks, Stu.

17th February 2003, 20:52	#1
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	nsExec problem 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

18th February 2003, 14:53	#3
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	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

18th February 2003, 18:24	#4
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	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

18th February 2003, 19:10	#6
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	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

19th February 2003, 19:15	#8
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	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

18th February 2003, 03:39	#2
rainwater Senior Member Join Date: Aug 2000 Posts: 397	Did you look to see if the file was there?

18th February 2003, 19:02	#5
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	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

19th February 2003, 18:07	#7
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	How is the figuring it out going -Stuart

29th February 2008, 19:57	#9
Irish2007 Junior Member Join Date: Nov 2007 Posts: 4	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!

1st March 2008, 14:35	#10
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	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

16th February 2010, 11:17	#11
yudyzhao Junior Member Join Date: Sep 2009 Posts: 7	kichik, I used your dumplog in my installer script. But the install.log content is unreadable at all because I created the installer by Unicode NSIS. Is there Unicode system.dll available or any other way to solve this problem? Thanks a lot.

16th February 2010, 11:26	#12
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	System plug-in already supports Unicode. You just have to call the right functions (W instead of A) with the right parameter types (w instead of t). NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

17th February 2010, 14:00	#13
yudyzhao Junior Member Join Date: Sep 2009 Posts: 7	kichik, thanks a lot. Problem is solved!

8th December 2011, 15:23	#15
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	Use SendMessageW instead of SendMessageA and you need to use LVM_GETITEMTEXTW instead of LVM_GETITEMTEXT (google the value). You may also need to change the &t to &w but check the Unicode System plug-in readme for that. Edit: You may also need to use different FileWrite functions but again check the Unicode NSIS manual. Stu

8th December 2011, 15:52	#16
ptz Junior Member Join Date: Nov 2011 Posts: 8	Oh, excellent, switching to LVM_GETITEMTEXTW did the trick. Thanks, Stu.

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode