Ok, can you try passing "c:\home\chicken-trunk\bin\csi.exe" to the Windows system(3) call? Perhaps it needs the full path to the executable.
-Ivan "felix winkelmann" <bunny...@gmail.com> writes: > The handling of backslashes as escaping characters is not the problem, > it seems. If I pass this string (verbatim, just like it is printed here) to > system(3): > > "c:\home\chicken-trunk\bin\csi" -bnq -e "(require-library setup-api)" > -e "(import setup-api)" "c:\...some...path...\defstruct.setup" > > I get an error message that tells me that the program > > "c:\home\chicken-trunk\bin\csi" -bnq -e "" _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
