Paul A. Rubin wrote: >> The first would imply that either sh.exe or the configure script can't >> be found by the OS. The second would mean that something is going >> wrong in its execution. > > The first is more consistent with the symptoms. Is the installer > running the same copy of the configuration script that's installed in > the Resources folder tree? If so, maybe I can hack the script to pause > right at the top, so that (maybe) I could see what if anything was > painted in the DOS window that spawned (and died).
It is. Try adding something like: $ cat trial.sh #! /bin/sh while true do echo "Hello!" done -- Angus
