ERROR: Illegal Pathname detected! Spaces inside Pathname are not allowed

Luni · 17th February 2006, 16:00

Hi!

After not successfully search the web for view hours I decided to post my problem.

I'm using MakeNSIS v2.14 (log version). Previously I was using a 1.x Version.

In the Directory Page, when I push the "browse" button a message box appears (3 times) with following contents:

ERROR
Illegal Pathname detected!
Spaces inside Pathname are not allowed

After confirming that message box three times I can select a path.

That behavior is only present on Windows 2K and XP but not on NT.

Previous MakeNSIS Version does not shows such a messagebox.

What am I doing wrong?

Does new version handle paths different as the previous version?

I did not found any flags to tell NSIS to ignore that, nor to specify the rigth path string.

Help will be appreciated. See attachment for scriptfile.

Adolfo

Comperio · 18th February 2006, 16:58

I didn't see any PAGE commands in your attached NSI file. How were you even getting a directory page? Are you sure this is the right NSI file?

Mr Inches · 19th February 2006, 04:54

According to my syntax highlighting editor, single quotes in the !define messes with the rest of the file.

Try replacing the following line

!define INSTALLPATH '$PROGRAMFILES\Controlware\Supervisor_${SV_VER}\'

with

!define INSTALLPATH "$PROGRAMFILES\Controlware\Supervisor_${SV_VER}\"

and see if that helps.

Takhir · 19th February 2006, 11:30

IMHO MessageBox in 4.7.2.1.10 .onVerifyInstDir is not good. It's MessageBox may look crazy. And $PROGRAMFILES in your default path includes blank spaces.

Luni · 21st February 2006, 07:40

At first, thanks for answers

!

@Mr Inches

What editor are you using?

I'm using HM NIS Editor http://hmne.sourceforge.net/ and its coloring is OK.

@Comperio

I agree, I do not know

way it is working without PAGE commands but it is. That script was written by other peoples not more here. I'm just trying to adapt it to work with the new version of NSIS. Till now it works fine, only the behavior problem with "browse" buttom is wrong.

@Takhir

I tried to print the $INSTDIR in the MessageBox and it is "C:\Dokumente und Einstellungen\alucha\desktop" (inglish: "C:\documents and settings\alucha\desktop") in the first box. It is "C:\Dokumente und Einstellungen\alucha\Eigene Dateien" in the other three message boxes. But I did not set it to that string. Where is it set to it? And why is it poping up four times, and with different path strings?

I tried to set $INSTDIR in followiung code

Function .onInit
StrCpy $INSTDIR "${INSTALLPATH}"
FunctionEnd

But it does not change the behavior.

Why is the behavior other under XP as under NT?

Luni · 21st February 2006, 09:52

I fixed it with a workaround. I check the Windows Version in the .onVerifyInstDir and allow spaces inside paths when XP.

Thanks again for all your answers.

Mr Inches · 21st February 2006, 20:04

Good to hear you managed to sort it out, or at least have the workaround.

I use UltraEdit-32 with the NSIS wordfile extension for my editor and your file was the first one I have seen in it that marked all of the file after that !define as a string, which I found odd.

NSIS seemed to compile it OK (except for the obvious missing files!), but it looked unusual enough for me to highlight it.

Brummelchen · 21st February 2006, 21:40

TextPad latest with nsis2 file - i code myself w/o help - only with wiki and chm help

21st February 2006, 21:40	#8
Brummelchen Major Dude Join Date: May 2003 Posts: 681	TextPad latest with nsis2 file - i code myself w/o help - only with wiki and chm help Greets, Brummelchen

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

18th February 2006, 16:58	#2
Comperio Major Dude Join Date: Jan 2005 Location: Oregon Coast Posts: 737	I didn't see any PAGE commands in your attached NSI file. How were you even getting a directory page? Are you sure this is the right NSI file?

19th February 2006, 04:54	#3
Mr Inches Member Join Date: Jan 2006 Location: Canberra, Australia Posts: 76	According to my syntax highlighting editor, single quotes in the !define messes with the rest of the file. Try replacing the following line !define INSTALLPATH '$PROGRAMFILES\Controlware\Supervisor_${SV_VER}\' with !define INSTALLPATH "$PROGRAMFILES\Controlware\Supervisor_${SV_VER}\" and see if that helps.

19th February 2006, 11:30	#4
Takhir Major Dude Join Date: Feb 2004 Location: Moscow, Russia Posts: 1,222	IMHO MessageBox in 4.7.2.1.10 .onVerifyInstDir is not good. It's MessageBox may look crazy. And $PROGRAMFILES in your default path includes blank spaces.

21st February 2006, 07:40	#5
Luni Junior Member Join Date: Feb 2006 Posts: 3	At first, thanks for answers ! @Mr Inches What editor are you using? I'm using HM NIS Editor http://hmne.sourceforge.net/ and its coloring is OK. @Comperio I agree, I do not know way it is working without PAGE commands but it is. That script was written by other peoples not more here. I'm just trying to adapt it to work with the new version of NSIS. Till now it works fine, only the behavior problem with "browse" buttom is wrong. @Takhir I tried to print the $INSTDIR in the MessageBox and it is "C:\Dokumente und Einstellungen\alucha\desktop" (inglish: "C:\documents and settings\alucha\desktop") in the first box. It is "C:\Dokumente und Einstellungen\alucha\Eigene Dateien" in the other three message boxes. But I did not set it to that string. Where is it set to it? And why is it poping up four times, and with different path strings? I tried to set $INSTDIR in followiung code Function .onInit StrCpy $INSTDIR "${INSTALLPATH}" FunctionEnd But it does not change the behavior. Why is the behavior other under XP as under NT?

21st February 2006, 09:52	#6
Luni Junior Member Join Date: Feb 2006 Posts: 3	I fixed it with a workaround. I check the Windows Version in the .onVerifyInstDir and allow spaces inside paths when XP. Thanks again for all your answers.

21st February 2006, 20:04	#7
Mr Inches Member Join Date: Jan 2006 Location: Canberra, Australia Posts: 76	Good to hear you managed to sort it out, or at least have the workaround. I use UltraEdit-32 with the NSIS wordfile extension for my editor and your file was the first one I have seen in it that marked all of the file after that !define as a string, which I found odd. NSIS seemed to compile it OK (except for the obvious missing files!), but it looked unusual enough for me to highlight it.