However, you can easily hide or move it.

Hide it

Launch Terminal.app and paste the following into there:

setfile -a V ~/Documents/Steam\ Content

The folder should disappear immediately. To make it visible again, use:

setfile -a v ~/Documents/Steam\ Content

To view it in Finder while it is invisible, use:

open ~/Documents/Steam\ Content

Move it

Alternatively, you can move it to another place (be that another folder or even another partition). After moving you would have to create a symlink (sort of a shortcut in Windows’ terms).

For example, you can move it to user’s Library folder (the first line moves it, the second line creates a symlink and the third line hides the symlink in Finder):

mv ~/Documents/Steam\ Content ~/Library/Steam\ Content
ln -s ~/Library/Steam\ Content ~/Documents/Steam\ Content
setfile -P -a V ~/Documents/Steam\ Content

It’s not necessary to move using the Terminal.app — you can as well just take and drag in Finder to wherever you want. In this case, disregard the mv ... command and use only:

ln -s NEW_LOCATION_OF_STEAM_CONTENT ~/Documents/Steam\ Content
setfile -P -a V ~/Documents/Steam\ Content

If you don’t know the exact new path, just drag and drop Steam Content (while it’s in the new location) to the Terminal.app window.

None of the solutions suggested by the Google search worked for me (including repairing and reinstalling Steam, just deleting some .blob files, etc), so having considered the installation of Kaspersky as the only possible influence factor, I checked Windows firewall configuration in the Control Panel, deleted Steam outta there and re-added it as a safe application.

This solved the problem. (It wasn’t too obvious: all other programs were working fine, Windows did not complain and Steam was a “trusted” program in built-in firewall settings).

To solve the problem, I decided to revert my system to a pre-Bootcamp state with Vista’s built in “System Restore” utility. At first I tried standard “Safe Mode” which didn’t work, but booting “Safe Mode with command-line” worked fine (to see those option hold F8 button on your keyboard while the computer is booting). To launch the “System Restore” utility, I typed rstrui.exe in the command-line. For some unknown reason it took several minutes to initialize, and launched in some sort of minimized state from which I retrieved it with a plain Alt+Tab.

After restoring, the system took a couple of reboots to sort things out, but everything worked fine afterwards.

Пример такого сайта — ВКонтакте. Отсутствующий у меня шрифт Tahoma зачем-то заменяется на более широкий Verdana, который заставляет отдельные элементы разъезжаться.

По умолчанию скрипт работает только с ВКонтакте, но вы всегда можете добавить новый сайт в настройках GreaseMonkey:

Установить скрипт «Override fonts with Helvetica Neue».
(перед установкой убедитесь, что у вас установлен и включен плагин GreaseMonkey).

To diagnose the problem, I booted in verbose mode (hold Cmd + V when it starts booting, later you may find the logs in Console.app) and noticed these lines:

Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer: Busy services :
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2 [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0 [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3 [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI/IOFireWireController [1]
Jun 21 03:02:15 Dae-MBP configd[36]: InterfaceNamer:   MacBookPro2,2/AppleACPIPlatformExpert/PCI0@0/AppleACPIPCI/PCIB@1E/IOPCI2PCIBridge/FRWR@3/AppleFWOHCI/IOFireWireController/IOFireWireLocalNode [1]
Jun 21 03:06:20 Dae-MBP /usr/libexec/hidd[27]: Timeout waiting for IOKit to be quiet

Obviously something was wrong with firewire. I checked my firewire 400 port and it appeared to be broken. Quick search revealed that the problem of dieing firewire ports is not uncommon for this generation of MacBook Pros, and the only way to repair it is to replace a logic board. I confirmed all of these by contacting a technician of local Apple reseller.

Since my MacBook was out of warranty and I didn’t want to spend 350€  on a new logic board for a quite old computer, I decided to minimize the consequences. The solution was easy: to move IOFireWireFamily.kext out of /System/Extensions. I as well have to repeat this operation after installing system updates. The sleep problem was gone as well.

At first I was trying to figure what’s a boot helper partition and where do I find it, but eventually I decided to take a look at com.apple.Boot.plist file, which appeared to be non-existent in it’s regular place.

So I created one by myself. In Terminal:

sudo nano /Library/Preferences/SystemConfiguration/com.apple.Boot.plist

There inserted the default code:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://
www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string></string>
</dict>
</plist>

(Cmd+X to save the file).

This solved the problem for me.