🚀 go-pugleaf

In article <1gqgtrINNs9h@stephen.cs.ubc.ca> sritchie@cs.ubc.ca (Stuart  
Ritchie) writes:
> This is the second day in a row that my Workspace.app has died
> (panel pops up saying Workspace Manager Error).  25MHz monostation,
> 32MB RAM.
> 
> Today I investigated further, the console.log reports the following:
> 
> Dec 17 09:36:03 Workspace[140]: Cannot fork for  
/usr/lib/NextStep/Workspace.app/WM.app/AppFinder.tool
> Dec 17 09:36:03 Workspace[140]: No tool for launch notice on pid : 155
> Dec 17 09:36:08 bowen syslog: NXMiniApp: Cannot receive init message :  
-203
> Dec 17 10:20:06 Workspace: Controller exited.
> 
> The Workspace error panel popped up when I tried to launch  
IconBuilder.app
> as a regular user.  However, checking the console.log times, it appears
> that things went haywire well before I tried launching IconBuilder.

I had something similar a couple of days ago.  T _think_ that it could be  
associated with a very flakey SCSI chain that I had at the time.

If in doubt, check that all of your SCSI devices are properly connected,  
with appropriate termination, and that the chain isn't too long.  I have  
also found that having some devices in a chain powered off after the NeXT  
has recognised them at boot time will cause lots of problems.  Always  
leave all devices installed in your chain powered up to prevent hassles.

Paul
-- 
Paul Lynch
P & L Systems                   (NeXTmail) paul@seer.demon.co.uk
Tel: (0494)671501                      paull@cix.compulink.co.uk
Fax: (0494)680228                       76711.451@compuserve.com