I was just about to say that, sorry I missed the post at the time as I dont check her daily yet (i'm just an ocassional demo user atm at least until after xmas).
I found copying over network to the Mac also set the permissions up badly. In fact today I found copying another Mac users hard disk to a temporary folder on my system messed up all of my permissions on my route structure, for no reason at all, and I had to reinstall completely.
OSX is absolutely aweful and very definately the worst thing Apple ever did, it's trying too hard to be Windows now.
Do you realise that executables files you see are actually folders, the Mac .exe is in reality folder structure but it's hidden from you (you get "show package contents" from the gear icon in Finder).
The whole permissions thing is aweful because if any folder starts with a period symbol it's invisible to the OS, this effects BMax programs when you copy folders from PC to Mac so make sure you dont copy over your .bmax folder over from the PC because of course the permissions will not be set up correctly and it's a totally invisible folder, you wont be able to change the permissions because you cannot see and click on the folder to edit it, and consequently BMax wont compile (and sadly the error message is obscure).
The only solution when you make this error is to make a new folder and delete the original one you copied over, and dont use "select all" from the copy menu because I think that selects the invisible folder to copy, you want to drag select the visible contents to the new folder and compile from there. (dont forget to close and reopen the source code file in BMAX).
I think the "correct" PC-esque solution would be to open Darwin up (the Mac CLI [version of MS-DOS]) but as it's Unix based I havn't a clue of the commands.
Bloody aweful machine.
I found copying over network to the Mac also set the permissions up badly. In fact today I found copying another Mac users hard disk to a temporary folder on my system messed up all of my permissions on my route structure, for no reason at all, and I had to reinstall completely.
OSX is absolutely aweful and very definately the worst thing Apple ever did, it's trying too hard to be Windows now.
Do you realise that executables files you see are actually folders, the Mac .exe is in reality folder structure but it's hidden from you (you get "show package contents" from the gear icon in Finder).
The whole permissions thing is aweful because if any folder starts with a period symbol it's invisible to the OS, this effects BMax programs when you copy folders from PC to Mac so make sure you dont copy over your .bmax folder over from the PC because of course the permissions will not be set up correctly and it's a totally invisible folder, you wont be able to change the permissions because you cannot see and click on the folder to edit it, and consequently BMax wont compile (and sadly the error message is obscure).
The only solution when you make this error is to make a new folder and delete the original one you copied over, and dont use "select all" from the copy menu because I think that selects the invisible folder to copy, you want to drag select the visible contents to the new folder and compile from there. (dont forget to close and reopen the source code file in BMAX).
I think the "correct" PC-esque solution would be to open Darwin up (the Mac CLI [version of MS-DOS]) but as it's Unix based I havn't a clue of the commands.
Bloody aweful machine.