nsExec issues

bSecRes · 3rd August 2003, 22:17

Running on 2k/XP I'm having no problems, but 9x I only get errors. I am aware of the 8.3 path issue but that isn't the problem. Not even test.nsi in the contrib\nsExec folder works. This had previously worked. I updated my CVS for the first time in a while and now it is broke.

When I reinstall NSIS back to b3 it works fine.

Afrow UK · 3rd August 2003, 22:27

What happens.
Error messages?
?

-Stu

bSecRes · 3rd August 2003, 22:29

nsExec::Exec '"Path" parms'
Stack has "error" on top. Error means it couldn't execute the file. BTW if you need latest CVS compiled at 8192 or higher let me know. I'll upload makensis zipped.

Afrow UK · 3rd August 2003, 22:32

Thanks,
What is the full nsExec cmd path you are applying?

-Stu

bSecRes · 3rd August 2003, 22:36

Read the test.nsi file.
I also tried:
SetOutPath $TEMP
nsExec::Exec 'mybat.bat'

SetOutPath $TEMP
nsExec::Exec '"$TEMP\mybat.bat" parms'

And about 16hours worth of other permutations and combination all with and without /CMD preceding the path section to no avail. EXEC, ExecToStack, and ExecToLog or whatever all fail as well.

bSecRes · 3rd August 2003, 22:38

Perhaps I didn't actually answer your question now that I reread it. C:\windows\temp

kichik · 3rd August 2003, 22:47

Confirmed. If Ramon doesn't answer I'll try to fix it myself.

kichik · 3rd August 2003, 23:25

Fixed in latest CVS version.

bSecRes · 3rd August 2003, 23:26

You guys rock.

3rd August 2003, 22:17	#1
bSecRes Junior Member Join Date: Jul 2003 Location: LA USA Posts: 37	nsExec issues Running on 2k/XP I'm having no problems, but 9x I only get errors. I am aware of the 8.3 path issue but that isn't the problem. Not even test.nsi in the contrib\nsExec folder works. This had previously worked. I updated my CVS for the first time in a while and now it is broke. When I reinstall NSIS back to b3 it works fine.

3rd August 2003, 22:47	#7
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Confirmed. If Ramon doesn't answer I'll try to fix it myself. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

3rd August 2003, 23:25	#8
kichik M.I.A. [NSIS Dev, Mod] Join Date: Oct 2001 Location: Israel Posts: 11,343	Fixed in latest CVS version. NSIS FAQ \| NSIS Home Page \| Donate $ "I hear and I forget. I see and I remember. I do and I understand." -- Confucius

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

3rd August 2003, 22:27	#2
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	What happens. Error messages? ? -Stu

3rd August 2003, 22:29	#3
bSecRes Junior Member Join Date: Jul 2003 Location: LA USA Posts: 37	nsExec::Exec '"Path" parms' Stack has "error" on top. Error means it couldn't execute the file. BTW if you need latest CVS compiled at 8192 or higher let me know. I'll upload makensis zipped.

3rd August 2003, 22:32	#4
Afrow UK Moderator Join Date: Nov 2002 Location: Surrey, England Posts: 8,434	Thanks, What is the full nsExec cmd path you are applying? -Stu

3rd August 2003, 22:36	#5
bSecRes Junior Member Join Date: Jul 2003 Location: LA USA Posts: 37	Read the test.nsi file. I also tried: SetOutPath $TEMP nsExec::Exec 'mybat.bat' SetOutPath $TEMP nsExec::Exec '"$TEMP\mybat.bat" parms' And about 16hours worth of other permutations and combination all with and without /CMD preceding the path section to no avail. EXEC, ExecToStack, and ExecToLog or whatever all fail as well.

3rd August 2003, 22:38	#6
bSecRes Junior Member Join Date: Jul 2003 Location: LA USA Posts: 37	Perhaps I didn't actually answer your question now that I reread it. C:\windows\temp

3rd August 2003, 23:26	#9
bSecRes Junior Member Join Date: Jul 2003 Location: LA USA Posts: 37	You guys rock.