Chris R's Profile

The reason for not officially supporting these models has not yet been officially stated. Because of how Boot Camp works, the only reason specific Mac models would not be supported is because compatible drivers are not available. This would not prevent Windows 7 from being installed on these machines, but could result in certain devices not working as expected while running Windows.

Third party drivers for the unsupported devices (if they exist) could solve any issues, and Windows 7 may offer to install drivers for devices it recognizes but does not have built in support for; it may even identify and download the drivers automatically.

Of the unsupported machines in the supplied list, the Early 2006 iMacs and MacBook Pro models have 32-bit Core Duo CPUs, but the other models specified feature 64-bit Core 2 Duos or Xeon processors, and no other 32-bit Macs (MacBooks, mini) are excluded. Apple has yet to release any comments about providing support for the 64-bit edition of Windows 7 only, so the support issue does not appear to have anything to do with these models’ CPU or firmware.

The only other common thread between these machines is that they all originally shipped with either no or disabled support for 802.11n wireless networking. However, late 2006 MacBooks also shipped with disabled support for 802.11n, and no Mac minis supported 802.11n until 2009, so this does not appear to be a factor either.

• Open Disk Utility (/Applications/Utilities/).
• Mac OS X 10.4, 10.5 or later: Click the New Image button, or choose New > Blank Disk Image from the Disk Utility File menu.
  
  Mac OS X 10.3 through 10.3.9: Choose New from the Disk Utility Image menu.
  
   
• Enter a name in the Save As field. This name is used for the disk image (.dmg) file.
• Change the save destination if you wish to.
• Select a size for the image file from the Volume Size pop-up menu (Size in Mac OS X 10.3) .
• Choose a volume format if you don't want to use the default Mac OS X Extended (Journaled).
• Choose an image format. You can use "sparse disk image" for a disk image that only uses as much space as it needs, rather than a set amount of space. If you're not sure, use "read/write disk image" choice.
• Choose 128-bit AES (and/or 256-bit AES in Mac OS X 10.5 or later) from the Encryption pop-up menu to encrypt the image's contents with a password. If you don't choose an encryption, your new image won't be encrypted.
• Click the Create button.
• Enter and verify a good password in the dialog window that appears. This password will be saved in your keychain by default, or you can deselect "Remember password (add to keychain)" if you don't want that. You can store the password in the keychain both for convenience and for reducing risk of password loss.
• Click OK.

hat's Mac Screen Sharing connecting to a TightVNC server
on my wife's Windows XP machine (click it for a larger image). I'm looking at QuickBooks and wondering
why I haven't made any money so far this month.. oh, yeah, I've been
goofing off this week - that'll do it!

To make that connection from Finder, I just clicked "Go->Connect to Server" and typed in "vnc://10.10.1.2" (that machine's IP address). That's it,
and of course if ports were open, I could have just as easily done
that across the Internet.

The important thing to remember is this: the subfolders are not actually stored in the library. They are just made to seem as though they are. Each library has some default contents, but you can change these, and also create new libraries if you wish.

sually, you can just kill the firefox process to solve this problem. For example, on Linux the command “ps auxwww | grep firefox” will find the process number and then “kill [processnumber]” will work fine. But sometimes things are more horked than usual. That happened to me today, surprise surprise Here’s how to fix the deeper problem:

Step 1. Find your profile. This page tells you how to find the location of your Firefox profile. Under Linux (e.g. Ubuntu), it will be at ~/.mozilla/firefox/[Profile name]/ .

Step 2. Remove the lock files. This page tells you what the lock files are for Firefox on Windows/Linux/Mac. Under Unix/Linux, you’ll need to remove two files “lock” and “.parentlock” .

I haven’t had this happen before today, but it can happen if (for example) someone turns your computer off while Firefox is running.