Skip to main content

How to speed up your Windows Boot after iTunes upgrade.

A new version of iTunes 10.5 came out for Windows with compatibility for iOS 5. After upgrading my boot time jumped a huge amount of time. Here is how to tame the Windows Boot back into shape when you have installed iTunes.

1. First install Soluto (mentioned in my Windows utilities post). Then go to chop boot and look for these processes

  • Apple Application Support
  • Bonjour -- this one is optional
  • Mobile Devices (Apple Mobile Devices Support)

And set all three to "Delay." Unless you only use your computer for iTunes/iOS support from the minute you start the computer, there is no real reason for those to hold up the start-up of your computer.

2. Then open Run... and type 'msconfig' and go to the start up tab. On Windows 7 you can just type it on the Start search bar and it will fire right away. Don't ask me why but when things are set up here sometimes they conflict with Soluto.

Go to the Startup tab and look for any processes that shouldn't be a start up. A typical one is Sun's Java insisting on check for updates every time the computer starts up. If there are any Apple ones here make sure you mark them off. I tend to check everything off, since those services will start up when you call the application anyway. They'll just make your application launch slower (so iTunes launch will be way slower) but your boot way faster.

Occationally if you launch iTunes right after start-up some of the services like Bonjour may not be running yet, so you'll get a warning just wait a few seconds and restart iTunes.


Popular posts from this blog

How to configure Ubuntu's keyboard to work like a Mac's

Typing accents on a PC is a complicated Alt + three numbered code affair. One feels like a sorcerer casting a spell. "I summon thee accented é! I press the weird magical key Alt, and with 0191 get the flipped question mark!" For a bilingual person this meant that writing on the computer was a start-and-stop process. With Mac's it a whole lot easier, just Alt + e and the letter you wanted for accents and alt + ? for the question mark. No need to leave the keyboard for the number pad and no need to remember arcane number combinations or have a paper cheat sheet next to the keyboard, as I've seen in virtually every secretaries computer in Puerto Rico.

Linux has a interesting approach to foreign language characters: using a compose key. You hit this key which I typically map to Caps Lock and ' and the letter you want and voilá you get the accent. Kinda makes sense: single quotation mark is an accent, double gets you the ümalaut, works pretty well. Except for the ñ, wh…

Contrasting Styles of Writing: English vs. Spanish

There is interestingly enough a big difference between what's considered good writing in Spanish and English. V.S. Naipul winner of the 2001 Nobel prize for literature publish an article on writing. In it he emphasizes the use of short clear sentences and encourages the lack of adjectives and adverbs. Essentially he pushes the writer to abandon florid language and master spartan communication. This is a desired feature of English prose, where short clipped sentences are the norm and seamlessly flow into a paragraph. In English prose the paragraph is the unit the writer cares about the most.

This is not the case in Spanish where whole short stories (I'm thinking this was Gabriel Garcia Marquez but maybe it was Cortázar) are written in one sentence. Something so difficult to do in English that the expert translator could best manage to encapsulate the tale in two sentences. The florid language is what is considered good writing in Spanish but unfortunately this has lead to what …

Fixing Autocomplete in Github's Atom Text Editor for Ruby

I really like Github's Atom Text Editor. I really like that it's multi-platform allowing me to master one set of skills that is transferable to all platforms and all machines. 

On thing that just burns me of the default set-up in Atom is the Autocomplete feature that seems to change my words as a type them. Because Ruby uses the end of line as a terminus for a statement you usually finish a word with pressing the return button and you get really annoying changes to your finished typed word a la MS Word. I find myself yelling "No that's not what I wrote!" at the screen in busy coffee shops.

I disabled autocomplete for a while but it is a very useful function. Then I found out they changed the package that gave the autocomplete to a new one called "Autocomplete Plus" that gives you more options. All that I needed to change to make autocomplete sane again:

1. Open Atom's Preferences
2. Search the bundled packages for "Autocomplete Plus"

3. Go to t…