Roman Thilenius

while i am testing old OS 9 programs of mine on window and OSX i found out that a copy of the free runtime v 460 on my OSX machine chrashes wherever 

what could cause t hat surprising annoyance?

i need a working free runtime as the patches are to be given to non maxers.

while i am testing old OS 9 programs of mine on window and OSX i found out that a copy of the free runtime v 460 on my OSX machine chrashes wherever 
pak
is loaded, and also whenever
coll
gets anything.

i need a working free runtime as  the patches are to be given to non maxers.

max-runtime-460-faulty-objects

On 19 janv. 09, at 16:18, Roman Thilenius wrote:

> while i am testing old OS 9 programs of mine on window and OSX i 

> found out that a copy of the free runtime v 460 on my OSX machine 

> what could cause t hat surprising annoyance?

> i need a working free runtime as the patches are to be given to non 

Is it a collective? You might want to download the latest runtime 

> time to ask a silly question.
>
> while i am testing old OS 9 programs of mine on window and OSX i  
> found out that a copy of the free runtime v 460 on my OSX machine  
> chrashes wherever
> pak
> is loaded, and also whenever
> coll
> gets anything.
>
> what could cause t hat surprising annoyance?
>
> i need a working free runtime as  the patches are to be given to non  
> maxers.

Is it a collective? You might want to download the latest runtime  
(4.6.3).

no its bpatchers. first when it happoend with col i thought it might be the object but when pak chrashed i new it must be either the distribution or more likely my installation.

yet i hoped its a known issue or something :)

no its bpatchers. first when it happoend with col i thought it might be the object but when pak chrashed i new it must be either the distribution or more likely my installation.
yet i hoped its a known issue or something :)


On 19 janv. 09, at 16:39, Roman Thilenius wrote:

> no its bpatchers. first when it happoend with col i thought it 

> might be the object but when pak chrashed i new it must be either 

> the distribution or more likely my installation.

> yet i hoped its a known issue or something :)

Not that I'm aware of. I would recommend doing a clean installation, 

and making sure that you have a clean search path to start with.

> no its bpatchers. first when it happoend with col i thought it  
> might be the object but when pak chrashed i new it must be either  
> the distribution or more likely my installation.
> yet i hoped its a known issue or something :)

Not that I'm aware of. I would recommend doing a clean installation,  
and making sure that you have a clean search path to start with.

max runtime 460: faulty objects?