Jeremy

The ever-vigilant Mike Z noticed that I totally neglected to do 

anything about byte-swapping for Intel Macs when I posted the 4.6 

version of filetype. This has been fixed, as well as another bug 

which made setting all 3 characteristics of the file (type, creator, 

I've not updated the OS9 or 4.5 versions, though (which could benefit 

from the bug fix, but will have to wait).

https://cycling74.com/twiki/bin/view/Share/JeremyBernstein

The ever-vigilant Mike Z noticed that I totally neglected to do  
anything about byte-swapping for Intel Macs when I posted the 4.6  
version of filetype. This has been fixed, as well as another bug  
which made setting all 3 characteristics of the file (type, creator,  
extension) at the same time impossible.

I've not updated the OS9 or 4.5 versions, though (which could benefit  
from the bug fix, but will have to wait).

https://cycling74.com/twiki/bin/view/Share/JeremyBernstein


filetype-object-updated-for-intel-mac

I downloaded the 'curtains' UB this morning, and can't seem to get it to authorize to enable mode 1, either though the standard authorization dialog, or by sending the 'auth' message to the object. Mode 0 works as expected. Any ideas?

- I am using the correct login and passcode

- short name and full name on the account are identical

Details:
- Max 4.6.2
- MacBook Pro 2.33 duo, 10.4.8
- I am using an admin account
- I am using the correct login and passcode
- short name and full name on the account are identical


I just got it to work on my Mac Mini. However, this might have 

something to do with the issue reported in relation to the "shell" 

object (do a forum search on "shell" for more info), which also never 

affected my Mini. The curtains object is more or less calling /sbin/ 

reboot or /sbin/halt to do its work, so it's probably the same 

problem. The next Max update will include a fix for this issue.

> I downloaded the 'curtains' UB this morning, and can't seem to get 

> it to authorize to enable mode 1, either though the standard 

> authorization dialog, or by sending the 'auth' message to the 

> object. Mode 0 works as expected. Any ideas?

> - I am using the correct login and passcode

> - short name and full name on the account are identical

I just got it to work on my Mac Mini. However, this might have  
something to do with the issue reported in relation to the "shell"  
object (do a forum search on "shell" for more info), which also never  
affected my Mini. The curtains object is more or less calling /sbin/ 
reboot or /sbin/halt to do its work, so it's probably the same  
problem. The next Max update will include a fix for this issue.

>
> Dear Jeremy,
>
> I downloaded the 'curtains' UB this morning, and can't seem to get  
> it to authorize to enable mode 1, either though the standard  
> authorization dialog, or by sending the 'auth' message to the  
> object. Mode 0 works as expected. Any ideas?
>
> Thanks,
> Ben
>
> Details:
> - Max 4.6.2
> - MacBook Pro 2.33 duo, 10.4.8
> - I am using an admin account
> - I am using the correct login and passcode
> - short name and full name on the account are identical


Just for your records... I tested it on a mac mini, 1.66Ghz Core Duo, 10.4.8, and am experiencing the same issue.

Hm, that's the same one i have, and it was working fine. Possibly 

because I'm running a beta of the next minor upgrade to MaxMSP? ;)

> Just for your records... I tested it on a mac mini, 1.66Ghz Core 

> Duo, 10.4.8, and am experiencing the same issue.

Hm, that's the same one i have, and it was working fine. Possibly  
because I'm running a beta of the next minor upgrade to MaxMSP? ;)

>
> Hi Jeremy,
>
> Thanks for the update.
>
> Just for your records... I tested it on a mac mini, 1.66Ghz Core  
> Duo, 10.4.8, and am experiencing the same issue.
>
> Thanks,
> Ben


filetype object updated for Intel mac