From: vs_tv AT aat-f DOT aeg-f DOT de (Thomas Vetter) Subject: problems starting gnu commands remotely 27 Jun 1997 02:12:17 -0700 Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <199706270820.KAA03482.cygnus.gnu-win32@frss27.aat-f.aeg-f.de> Original-To: gnu-win32 AT cygnus DOT com Original-Cc: vetter AT aat-f DOT aeg-f DOT de X-Sun-Charset: US-ASCII Original-Sender: owner-gnu-win32 AT cygnus DOT com Hi, I have just installed gnuwin32 on a winnt 4.0 system to port my unix sources to nt. My sources are located on a unix system (sun solaris). To access the sources from nt I use samba. I created links on nt to get the same directory structure as in our Unix environment To administrate my sources I have an own development kit based on a lot of csh scripts using sccs and gcc. To compile a source a script will be created on the unix system which will be started on the destination system (nt) using rsh. Therefore I use a rshd for nt. The compiling sequence works for about 3-5 times ok. But then the remote on the nt system started script aborts and the following error message appears in a window on the screen of the nt system: The Application can't be initialized correct (0x0000022). Press 'OK' to finish the Application In the DOS-Window where I had started the rshd by hand the following message appeared : fork_helper: child died before initialisation with win32 error 128 This happens for every gnu-application started remotely by a batch-job (gcc,ar,mv,...). Starting standard programs and commands from nt (cd,dir,...) by a batch-job via rsh the error doesn't occure. So I think the problem isn't the rshd (... I tested several ones). The problem seems to be the gnu commands or the workaround where they are started. Reading the mailing list archives I didn't find a description for this problem. Is there anybody who can help me solving this problem ? Thomas Thomas Vetter (vetter AT aat-f DOT aeg-f DOT de or http://thomasvetter.aat-f.aeg-f.de) - For help on using this list (especially unsubscribing), send a message to "gnu-win32-request AT cygnus DOT com" with one line of text: "help".