zipb

I've found another weird problem in my museum installation. Every 

once in a while (in fact quite often, maybe 1 out of 5 times) after a 

reboot, the two G5's that generate sound will boot, try to 

automatically launch their Max patches(via Startup Items and now via 

Keep-It-Up X, thanks for the link, Peter!) and then Max will stall. 

The empty Max(play) Status Window will appear and then nothing, not 

even the Jitter splash screen that normally follows before the 

To make matters worse, the Keep-It-Up program will not automatically 

restart Max or reboot the machine, as everything looks healthy when 

checking TOP(the UNIX table of running processes). Max is running, 

but not doing anything useful, and meanwhile the desktop is exposed 

so visitors can do what they like with the G5, which often means 

Any ideas what is causing this? Should I delay the automatic launch 

Another problem: although all my Max patchers are fullscreen, 

sometimes a part of the Apple menubar is still visible, enabling 

people to switch to the finder, quit Max, try to surf the Internet, 

How can I avoid this? Is there a way to disable everything except the 

Any tips most welcome. What I find really unnerving is that the 

installation will work fine one day, and refuse to boot properly of 

I've found another weird problem in my museum installation. Every  
once in a while (in fact quite often, maybe 1 out of 5 times) after a  
reboot, the two G5's that generate sound will boot, try to  
automatically launch their Max patches(via Startup Items and now via  
Keep-It-Up X, thanks for the link, Peter!) and then Max will stall.  
The empty Max(play) Status Window will appear and then nothing, not  
even the Jitter splash screen that normally follows before the  
fullscreen patch is supposed to load.
To make matters worse, the Keep-It-Up program will not automatically  
restart Max or reboot the machine, as everything looks healthy when  
checking TOP(the UNIX table of running processes). Max is running,  
but not doing anything useful, and meanwhile the desktop is exposed  
so visitors can do what they like with the G5, which often means  
completely messing up the system.

Any ideas what is causing this? Should I delay the automatic launch  
of Max?

Another problem: although all my Max patchers are fullscreen,  
sometimes a part of the Apple menubar is still visible, enabling  
people to switch to the finder, quit Max, try to surf the Internet,  
destroy the system etc.

How can I avoid this? Is there a way to disable everything except the  
max patch that is/should be  running?

Any tips most welcome. What I find really unnerving is that the  
installation will work fine one  day, and refuse to boot properly of  
crash like crazy the next.

Media Mechanics
Zwaluwstraat 54
2025 VR  Haarlem
The Netherlands
+31627014758
zip@knoware.nl


stall-on-launch-more-permanent-installation-problems

On 8-Feb-2007, at 22:09, Zip Boterbloem wrote:

> Should I delay the automatic launch of Max?

Possibly a good idea. I can't remember... does KIU let you do this?

John Dekron and I had a similar problem once with one incarnation of 

realiTV. We never found a real solution and in the meantime our 

hardware has evolved. So we have different problems:-

Peter Castine +--> Litter Power & Litter Bundle for Jitter

Interface Building for |home | chez nous|

Max/MSP Extremely cool |bei uns | i nostri|

John Dekron and I had a similar problem once with one incarnation of  
realiTV. We never found a real solution and in the meantime our  
hardware has evolved. So we have different problems:-

--------------    http://www.bek.no/~pcastine/Litter/    -------------
Peter Castine             +--> Litter Power & Litter Bundle for Jitter
                                Universal Binaries on the way
iCE:  Sequencing,  Recording &
       Interface  Building  for                   |home    | chez nous|
       Max/MSP   Extremely cool                   |bei uns |  i nostri|
       http://www.dspaudio.com/                   http://www.castine.de

I'm trying to include a 3rd-party external (Kosma's great 

windowmanager.mxo), and I'm having trouble getting it included. Scanning 

1. copied the windomanager.mxo/ bundle into my app/Contents/MacOS/

2. inside that windowmanager.mxo/Contents/ I put a file "PkgInfo"

    (note: the Info.plist there has this entry

I'm trying to include a 3rd-party external (Kosma's great 
windowmanager.mxo), and I'm having trouble getting it included.  Scanning 
the archives, here's what I've done:

1.  copied the windomanager.mxo/ bundle into my app/Contents/MacOS/
2.  inside that windowmanager.mxo/Contents/ I put a file "PkgInfo"
 	with the single entry "iLaX????"
 	(note: the Info.plist there has this entry

> I'm trying to include a 3rd-party external (Kosma's great 

> windowmanager.mxo), and I'm having trouble getting it included. 

> Scanning the archives, here's what I've done:

cosmas window manager will crash my Max 4.6.2 reliably, maybe the 

And as Peter pointed out usually there is nothing to do to include an 

Bradford Garton wrote:
> I'm trying to include a 3rd-party external (Kosma's great 
> windowmanager.mxo), and I'm having trouble getting it included.  
> Scanning the archives, here's what I've done:

cosmas window manager will crash my Max 4.6.2 reliably, maybe the 
problem isn't the inclusion...
And as Peter pointed out usually there is nothing to do to include an 
external...

-- 
Stefan Tiedje------------x-------
--_____-----------|--------------
--(_|_ ----|-----|-----()-------
-- _|_)----|-----()--------------
----------()--------www.ccmix.com


I'm beginnging to think it might indeed be the external -- lucky me. I 

futzed a bit with the bundle contents, but I get conflicting reports with 

the build -- in the max window it first says "error: can't open 

windomanager.mxo" but then the next line it says "Copying External 

windowmanager". And after trying various ways of situating the bundle in 

the finished app bundle, it still can't locate it. One thing I notice is 

tha the actual executable down in the windowmanager.mxo bundle is named 

"windmanager27". Even though the Info.plist lists the CFBundleExecutable 

I'm also still in max/msp 4.5.7-land, maybe that's also a factor.

>> I'm trying to include a 3rd-party external (Kosma's great 

>> windowmanager.mxo), and I'm having trouble getting it included. Scanning 

> cosmas window manager will crash my Max 4.6.2 reliably, maybe the problem 

> And as Peter pointed out usually there is nothing to do to include an 

I'm beginnging to think it might indeed be the external -- lucky me.  I 
futzed a bit with the bundle contents, but I get conflicting reports with 
the build -- in the max window it first says "error: can't open 
windomanager.mxo" but then the next line it says "Copying External 
windowmanager".  And after trying various ways of situating the bundle in 
the finished app bundle, it still can't locate it.  One thing I notice is 
tha the actual executable down in the windowmanager.mxo bundle is named 
"windmanager27".  Even though the Info.plist lists the CFBundleExecutable 
as that, I wonder...

I'm also still in  max/msp 4.5.7-land, maybe that's also a factor.

> Bradford Garton wrote:
>> I'm trying to include a 3rd-party external (Kosma's great 
>> windowmanager.mxo), and I'm having trouble getting it included.  Scanning 
>> the archives, here's what I've done:
>
> cosmas window manager will crash my Max 4.6.2 reliably, maybe the problem 
> isn't the inclusion...
> And as Peter pointed out usually there is nothing to do to include an 
> external...
>
> Stefan
>
> -- 
> Stefan Tiedje------------x-------
> --_____-----------|--------------
> --(_|_ ----|-----|-----()-------
> -- _|_)----|-----()--------------
> ----------()--------www.ccmix.com
>
>


stall on launch; more permanent installation problems