hey guys,

i downloaded the max/msp runtime package and am trying to install it on
my old g3 iBook. it gets most of the way through the installation and
then quits, telling me there were errors and to try installtion again.
i've tried rebooting and installing a few times but the same error comes
up every time.

i have:

500 mhz g3
640 megs of ram
2.5 gigs free drive space
os x 10.3.9
max/msp runtime 4.6.3

any ideas?
thanks!
`greg

do you have enough disk space?
are you installing to the default location?

i'd suggest posting this error on cycling74's forum. never tried such a 
new version on a g3.

i have two and a half gigs free on my disk. i'm assuming that should be 
enough considering the installer is 10 megs.

yes, installing to the default location.

i posted on cycling74's forum as well. no response yet.

again, any help would be greatly appreciated. on the other hand i might 
just have to chalk this up as another reason to /finally/ upgrade to 
that macbook i've had my eye on. may as well get an iphone too while i'm 
at it...

i digress,
`greg

i have no suggestions other than you're going to be much happier with os 
x 10.4 because monomeserial probably won't work with 10.3.9

sorry for the bad news.

running 10.4 on a g3 is really really sluggish though. maybe not too bad 
with 640 ram, but there was an old g3 tower at this place i worked a 
couple of summers ago that had 10.4 on it, and it was dismal for even 
browsing the internet.

fwiw, i cant get monomeserial to work on my wife's emac G4 running 
10.3.9.

the guys at cycling74 got back to me yesterday with plenty of advice on 
installing max/msp on my system.

...but you're right. monomeserial doesn't seem to load on 10.3.9.

shoot.

i think joe used some 10.4 specific API's or something.  its kind of 
wierd that it doesnt give any errors, though (at least on my wifes 
machine).  this is always an issue in software developing it seems, 
balancing between backwards compatibility and utilizing newer and better 
features.  i have to say that this is one thing that MS seem to spend 
alot of time on, making sure that old apps dont break in new versions. 
and, while they often do succeed, it leads to other problems where newer 
parts arnt as elegant as they should be.