Re: Starting .exe: DOS prompt OK, double-click not

2003-03-24 Thread Michael Pierce
On Mon, 2003-03-24 at 06:35, Kodaj Bence wrote: > > > "/cygdrive/c/OurAppFolder/OurScript.tcl": no such file or directory > >^^ > > This is a POSIX path. > > You can translate it to a Windows path using the Cygwin API call > > cygwin_conv_to_win32_path > >

RE: Starting .exe: DOS prompt OK, double-click not

2003-03-24 Thread Hannu E K Nevalainen (garbage mail)
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > Behalf Of Kodaj Bence --8<-- > = > Everything's fine when I start OurApp.exe from a DOS prompt. > = > > Now, OurApp.exe invokes wish like this: > > execlp

Re: Starting .exe: DOS prompt OK, double-click not

2003-03-24 Thread Igor Pechtchanski
On Mon, 24 Mar 2003, Kodaj Bence wrote: > > > "/cygdrive/c/OurAppFolder/OurScript.tcl": no such file or directory > >^^ > > This is a POSIX path. > > You can translate it to a Windows path using the Cygwin API call > > cygwin_conv_to_win32_path > > Thanks fo

Re: Starting .exe: DOS prompt OK, double-click not

2003-03-24 Thread Kodaj Bence
> > "/cygdrive/c/OurAppFolder/OurScript.tcl": no such file or directory >^^ > This is a POSIX path. > You can translate it to a Windows path using the Cygwin API call > cygwin_conv_to_win32_path Thanks for the tip, but I'm not sure this is the solution. The

Re: Starting .exe: DOS prompt OK, double-click not

2003-03-24 Thread Ronald Landheer-Cieslak
On Sat, 22 Mar 2003, Kodaj Bence wrote: [sbip] > (The actual Tcl/Tk installation on my machine is ActiveTcl 8.4., but > that's not really important.) Windows doesn't understand POSIX paths.. > Now, when I double-click on OurApp.exe in Windows Explorer, I get the > following error message from wis

Re: Starting .exe: DOS prompt OK, double-click not

2003-03-22 Thread Elfyn McBratney
> When OurApp.exe starts up, it invokes Tcl/Tk's "wish" shell, and passes > OurScript.tcl to it for interpretation. (The actual Tcl/Tk installation on my > machine is ActiveTcl 8.4., but that's not really important.) Well that depends. How does your application access the file "OurScript.tcl"? Wha