abe@mace.cc.purdue.edu (Vic Abell) (02/22/89)
I have been unable to run almost any IB application before I run the WS manager - /bootdisk/NeXT/Apps/Printer is the only exception I have found. I first found this problem while trying to get my own application to run right after the login dialog has been completed. My application is called by a special loginwindow program that forks a shell script that calls my application, then forks the WS manager. If I remove the call to my application from the script, the WS manager starts OK. If I replace my application with a call to some other application - e. g., Terminal - the application runs OK, but the following WS won't. Other, non-IB programs run fine from the shell script. My application runs fine when launched by the WS manager or from a Terminal/Shell window. (Actually, it runs fine before the WS manager, but the WS manager won't follow it.) The sick WS manager paints the dock, the black hole and the browser and exits. The console file, /tmp/console.log says: Home is /bootdisk/Homes/tst Path is .:~/Apps:/bootdisk/Apps:/bootdisk/NeXT/Apps:/bootdisk/Programming/Demos exception raised 1000 What's an "exception 1000" and why won't the WS manager run after some other