BootCamp drive inside OS X

[KiwiLee]

Hi

I finally got rid of my old G4 Emac, and splashed out on a swanky 24" Imac (damn its a hell of an upgrade from 700mhz emac!).

Anyway i installed bootcamp and put XP on it after the great hal.dll mess. But its all good now.

But in Mac OS i am kind of paranoid about the bootcamp HD sitting there on my desktop with essential windows files not locked etc, they can easliy be deleted etc. I know its a bit paranoid as only could delete them and break windows! But i would just feel happier if they was locked away from being edited or deleted at all.

Can this be done at all? Or even better just stop the winows/bootcamp HD from mounting with Mac OS. I dont feel the need to transfer files between the two so it doesn't need to be involved in Mac OS at all..

Thanks all

 

[Guiyon]

Is the drive formatted as FAT32 or NTFS? If the drive is NTFS formatted you cannot write to the drive in MacOS X unless you install third-party software.

 

[KiwiLee]

Fat32

I know ntfs is better choice, but i go so annoyed with the hal.dll error trying to install windows. It worked straight away when changed to Fat32, so i am happy with that.

 

[sickmacdoc]

Well, not exactly what you are looking for I will admit, but making the BC drive icon invisible might help out in your situation. For all intents itself is still there and operates totally normally, but the icon itself is simply invisible. I saw no reason to have it on my Mac desktop, so stumbled onto this solution a while back.

To do that you can enter the following line in Terminal, substituting your BC drive's name where indicated and the icon itself will vanish:

SetFile -a V "/Volumes/Drive Name Goes Here"

To restore the visibility of the icon later if desired, you can enter:

SetFile -a v "/Volumes/Drive Name Goes Here"

the only difference being in the second case the "v" is capitalized.

One note- I believe you have to have installed the Developer's Tools to use SetFile, but I am not sure as I always keep the latest Developer's tool loaded (since they have the quite useful Icon Composer app and several other useful utilities), so if you try it in Terminal and it tells you "Command not found" you will at least know why!