just wondered if anyone encountered this behaviour before: when i invoke shake (release 3) from within the desktop or a shell, it starts up, prints the startup output messages to the console and hangs my entire desktop (mouse, keyboard, everything) for a few seconds, then it finally comes up.
it's like windows hardware detection on drugs - worst thing is that *sometimes* when shake is lauchend via wacom tablet and i lift the pen in the apparently wrong moment, then the pen will be unavailable during the rest of the session, totally annoying.
any clues as to what shake is looking for during startup? maybe some config stuff that can be ticked off to speed up start up. this does not seem to be a problem on different architectures.
this is shake 3 on dual-cpu octane2 running irix 6.5.12.