mnavarro
18th January 2005 10:13 UTC

Problems with nsExec::Exec
The installer of our procuct uses nsExec::Exec and it always have worked fine. But recently one of our clients is experiencing some problems with our installer: it hangs. We suspected the problem was related with nsExec and we made a little installer that just calls "nsExec:Exec notepad.exe". In our machines this installer works fine but in client's machine it also hangs.

Client's machine has a Windows 2000 Advanced Server in Chinese with SP4. We have tried it in a Windows 2000 Advanced Server in Spanish with SP4 and it works fine

Have you ever heard about nsExec problems like this?

Thanks

Takhir
18th January 2005 10:34 UTC

Do not use nsExec with window applications, this plug-in was written for DOS apps only. For Notepad and others use Exec, ExecWait, ExecShell.

mnavarro
18th January 2005 10:55 UTC

Our installer doesn't call notepad.exe. Our installer uses nsExec to call DOS apps. notepad.exe is called from a small installer we made to ensure that the problem was caused by nsExec. This installer has four sections: one section uses nsExec to call dcomperm.exe (the app of our installer), another one uses nsExec to call a DOS hello world app, another one uses nsExec to call notepad.exe and the last one calls dcomperm.exe with ExecWait.
In out client machine the installer hangs if he selects any of the first three sections (the nsExec ones) and works fine if he only selects the forth one. So the problem is not the dcomperm.exe app but the nsExec itself.

Yathosho
18th January 2005 11:34 UTC

maybe you should use $WINDIR\notepad.exe ?

kichik
18th January 2005 18:34 UTC

I have never heard about such problems with nsExec. Any chance you can open Contrib\nsExec\nsExec.c, insert some debug information (message boxes/OutputDebugString/log file) and post your findings?

Takhir
18th January 2005 18:56 UTC

2 days ago http://forums.winamp.com/showthread....hreadid=205043 :)
May be chinese string length (file path)? Or problems with ASCII and Unicode?

kichik
18th January 2005 18:58 UTC

That's not a similar problem.

mnavarro
19th January 2005 09:08 UTC

We haven't been able to reproduce the problem in our office, so it's not easy to find the problem modifying the nsExec.c. But I will take a look at it anyway I will let you know any progress.

Thanks