How to get ProxySwitchy working in Chrome again [Updated]

If you’re a fan of Chrome and you need to use a proxy to secure your traffic once in a while, you’ve probably been using ProxySwitchy to get things running. You’ve probably also noticed how it’s broken down in the last couple of weeks, suspiciously timed to the release of Google Chrome 12. Yep, it’s broken. Here’s how to fix it on Mac OSX.

Step 1: If you’re using a PAC file, go to your System Preferences > Network > Advanced > Proxies > Automatic Proxy Configuration and make sure the URL to your PAC file is correct. Because if you were using Auto Switch Rules, the URL might have been replaced with a weird Chrome extension path.

Step 2: Uninstall ProxySwitchy.

Step 3: Upgrade to Chrome 13. (Here’s the technical background)

Step 4: Install Proxy SwitchyPlus SwitchySharp.

Step 5: You should be taken to the SwitchySharp options page. Configure your proxy and switch rules like you did before. On the “Network” tab, make sure the “Revert proxy changes done by other apps” is checked.

Now your proxy switcher as well as switch rules should be working again.

I’m leaving the comments open in case you have additions or corrections to this.

OSX security tip: create a screensaver shortcut in your dock

If you need to secure your Macbook from prying eyes, you can enable the screensaver and require a password to unlock. The usual way to go about this is using a hot corner to activate the screensaver. But if you, like me, are all over the place with your mouse, you might want to create a screensaver shortcut in your dock. Here’s how:

  1. Open Finder, navigate to System/Library/Frameworks/ScreenSaver.framework/Versions/Resources/
  2. Note: System/Library/
  3. Drag ScreenSaverEngine to dock
  4. Profit

Use Microsofts official Internet Explorer Virtual PC testing images in VirtualBox on OSX

If you need to test Internet Explorer 6 on your Mac, but don’t want to resort to multibooting, you can download the free VirtualBox software, and grab one of Microsofts free VirtualPC testing images and get up and running.

  1. Download a VPC image of your choice.
  2. Rename the .exe file to .rar, then unpack using a RAR unpacker on the Mac
  3. Create a new Virtual Machine in Virtualbox. When you get the chance to select an existing disk, do that and point to the VPC image.
  4. Boot. The VPC image may require activation and/or a password (which resides inside the .txt file that came with the VPC image)

Yep. There’s the activation hassle. It’s Microsoft. What did you expect? It’s still easier than manually installing Windows XP.

Webdesigner #316: “Just Get A Mac” (Mac vs. PC Round 2, TwentyTen Edition)

Slowly, one by one, my colleagues are switching out their desktop PCs with portable Macs. Except for me. Consistently, I’m suggested to “just get a Mac already”, implying the OSXperience will change my life for the better.

Standard_Mac

Here’s where I think it will change my life for the better, and where it won’t.

Pros of getting a Mac

  • Coda becomes available to me.
  • The keyboard layout is great for PHP and Javascript with great locations for $, { } and [ ]. This is a big one.
  • Expose is great for switching between open apps.
  • Getting to the desktop, finding a file, dragging it to an app in the dock for it to open, works great. This doesn’t work nowhere near as nicely on Windows.

Cons of getting a Mac

  • The selection model is virtually useless. If you didn’t start your selection next to the right character, you might as well start over.
  • You can’t live with the dock, you can’t live without it. It pops in whenever you don’t need it, which is when you scale a window.
  • Scaling windows is a miserable pain, especially if you don’t have Cinch installed. Sure it’s “clean” that I can only scale in the bottom right corner of a window. But what the hell is up with that?
  • StrokeIt (systemwide mouse gestures) is not available to me.
  • Directory Opus (superb file manager) is not available to me (and Pathfinder is not an alternative).
  • Expose is horrible for switching to minimized apps, i.e. it can’t.
  • There’s no fullscreen feature, and maximize behavior is inconsistent.
  • Since there’s no fullscreen, there’s no inherent app background, so clicking the space between app panels invokes the desktop. Stupid stupid.
  • OSX creates .DS_Store files in every fricken folder everywhere, and I can only disable it for network drives.
  • OSX hides period-prepended filenames (as it should by default, but if I disable this feature so I can more easily edit a .htaccess file, my desktop becomes cluttered with other files I really don’t want to see).

For the record, I dislike both Windows and OSX now.

Microsoft, Apple, j’accuse!

Webdesigner #316: "Just Get A Mac" (Mac vs. PC Round 2, TwentyTen Edition)

Slowly, one by one, my colleagues are switching out their desktop PCs with portable Macs. Except for me. Consistently, I’m suggested to “just get a Mac already”, implying the OSXperience will change my life for the better.

Standard_Mac

Here’s where I think it will change my life for the better, and where it won’t.

Pros of getting a Mac

  • Coda becomes available to me.
  • The keyboard layout is great for PHP and Javascript with great locations for $, { } and [ ]. This is a big one.
  • Expose is great for switching between open apps.
  • Getting to the desktop, finding a file, dragging it to an app in the dock for it to open, works great. This doesn’t work nowhere near as nicely on Windows.

Cons of getting a Mac

  • The selection model is virtually useless. If you didn’t start your selection next to the right character, you might as well start over.
  • You can’t live with the dock, you can’t live without it. It pops in whenever you don’t need it, which is when you scale a window.
  • Scaling windows is a miserable pain, especially if you don’t have Cinch installed. Sure it’s “clean” that I can only scale in the bottom right corner of a window. But what the hell is up with that?
  • StrokeIt (systemwide mouse gestures) is not available to me.
  • Directory Opus (superb file manager) is not available to me (and Pathfinder is not an alternative).
  • Expose is horrible for switching to minimized apps, i.e. it can’t.
  • There’s no fullscreen feature, and maximize behavior is inconsistent.
  • Since there’s no fullscreen, there’s no inherent app background, so clicking the space between app panels invokes the desktop. Stupid stupid.
  • OSX creates .DS_Store files in every fricken folder everywhere, and I can only disable it for network drives.
  • OSX hides period-prepended filenames (as it should by default, but if I disable this feature so I can more easily edit a .htaccess file, my desktop becomes cluttered with other files I really don’t want to see).

For the record, I dislike both Windows and OSX now.

Microsoft, Apple, j’accuse!

Running Windows On The Mac: Did It Ever Work? [Update 3: Returning It]

Just last week, I bought myself a brand new unibody Macbook Pro 15, a rather expensive piece of hardware. I bought it, expecting it to run Windows natively via multi-boot; Apple advertises that their Boot Camp feature will do just this:

[Mac OSX] Leopard is the world’s most advanced operating system. So advanced, it even lets you run Windows if there’s a PC application you need to use. […] Setup is simple and straightforward – just as you’d expect with a Mac.

As it turns out, sure, setup is easy, but that’s pretty much where the trademark simple and straightforward ends. Windows, running on my late 2008 Macbook crashes, freezes and Blue Screen Of Deaths me constantly, as in at every 10 minutes of plain use. To preempt your question, “Why run Windows at all?”: gaming.

There are a number of problems:

  • Windows doesn’t seem to control the cooling fans at all, and so it overheats
  • Windows can’t switch between the two (fast or power friendly) graphics adapters
  • Windows freezes when simply browsing websites

So overall, Windows on the Mac is a consistently unpleasant experience, which brings me to the purpose of this post. I need to decide whether I should return the Mac for a full refund and buy a different laptop for half the price, or alternatively, establish whether it’s likely that Apple will address all of these issues given reasonable time. It would really be a pity to return the unit, as I have already grown quite fond of the hardware. Furthermore, despite prior gripes, I can actually now see myself switching to OSX for day to day work, only to boot Windows for the occasional game of Fallout, whereas I bought this Mac with the expectation to do both while in Windows.

Because I genuinely want to make this thing work, I have a number of questions I would love to hear your opinions on, and preferrably before thursday this week where my 14-day right of return expires:

  • Do you have a late 2008 Unibody 15 Macbook running Windows, and are you having similar troubles?
  • Do you have any other Mac running Windows, and if so, is that unit running perfectly?
  • Have you had problems like these on older Mac hardware, which Apple fixed with firmware and software updates?
  • If you are running Windows on a Mac, is it Vista or XP, and did switching from one to the other fix your troubles?

Please note again that I’m referring to Windows running in Boot Camp, not in emulation or virtualization like Parallels or VirtualBox.

While I have done some a lot of research on the topic and found that quite a few others are having the same troubles, and even articles on Apple supposedly working on a fix for these issues, I would love to hear updated feedback on this. As a point of note: OSX runs just fine, doesn’t crash and cools the machine aptly, which leads me to believe this is mainly a Boot Camp software / driver issue, rather than solely a hardware issue.

So there it is, the current state of my fling with The Mac. Please help me turn this into a love-affair. I’ll end this with a Steve Jobs quote:

Design is not just what it looks like and feels like. Design is how it works.

If you’re reading, Steve, right now it doesn’t work.

Update: I’m putting a signed print of your choice on the line for the author of the comment that fixes the problems I’ve been having—not that I think that’s possible without Apple actually getting involved, but it’s worth a shot.

Update 2: After reading an article on The Inquirer, I’m now finding it likely that this Macbook and many others are suffering from bad Nvidia hardware. Please help me decide whether I should return the unit, or request a repair.

Update 3: Returning it. More to follow.