Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!rutgers!mcnc!ncsuvx!news
From: harris@hobbes.ncsu.edu (Michael Harris)
Newsgroups: comp.sys.amiga
Subject: Re: Things that should work on my 3000 but dont (heeelp!)
Message-ID: <1990Dec18.164723.25294@ncsuvx.ncsu.edu>
Date: 18 Dec 90 16:47:23 GMT
References: <16922@brahms.udel.edu>
Sender: news@ncsuvx.ncsu.edu (USENET News System)
Distribution: na
Organization: NCSU Computing Center
Lines: 29

don@brahms.udel.edu (Donald R Lloyd) writes:


>	I've had a number of strange problems getting some things _designed_
>for 2.0 to run.  I've been told by others that they run fine on their systems.
>
>	I've tried using both ToolManager and AddTools to customize my WB tools
>menu.  I know I've got them set up right, because if I run them from a shell
>after booting, they work fine.  However, in my startup-sequence or in the
>WBStartup drawer, they do absolutely nothing.  (in the SS I've tried 
>using runback and run <NIL: >NIL:, as well as just running them directly).

I too have discovered that ToolManager is picky.  I have the following in my
startup sequence and it works ok:

LoadWB
wait 2
runback >NIL: ClkPointer
runback >NIL: ToolManager

If you don't use ClkPointer, you may need to increase the time to 3 seconds.
I have tried using LoadWB -Delay and it doesn't wait long enough.  The key
is that Workbench must be completely loaded and initialized before 
ToolManager can install itself.
--
 __   _ ___ ___   Michael Harris - harris@catt.ncsu.edu      //        _    
|    / \  | |    Computer and Technologies Theme Program    // /||\/||/ _ /|
|__ / /_\ | |        North Carolina State University      \X/ /-||  ||\_|/-|