Here’s how to find “Options”:

• Click on the orb up at the top left.
• Down at the bottom right click “Word Options”.
• Continue on to find “About”.
• Now pick “Resources”.
• Over on the right you can see an About button.

There you go.

Oh and by the way, Microsoft Office 2010 brings back the familiar “File Edit View…” toolbar (albeit in a fancy new design). Still, hooray!

I tried downloading the Mac ARF player, which supposedly has options to convert the file to WMV and SWF.

http://www.webex.com/downloadplayer.html

After installing and opening my video in the player, I didn’t have File > Convert options that everyone talks about.

There are lot of tools on the Support / Downloads page for Webex:

http://support.webex.com/support/downloads.html

Maybe the nbr2mp4 utility would work (http://support.webex.com/supportutilities/nbr2mp4.tar):

A Linux-based conversion utility that allows you to convert your Cisco WebEx network-based recording files, which are in WebEx Advanced Recording Format File (.arf), and which were created with WBS 26 or higher to an MPEG-4 (.mp4) format.

It converts in realtime, though, so I didn’t try that path, especially since I’m not sure if all of the linux libraries would be support on Mac.

Since I already had a virtual machine with Windows, I grabbed the ARF viewer for Windows and it had the conversion options.

So, this rake task will reset all of them, presuming you have something to set them to. In my case, I found the latest comment date and used that, but you could figure it out some other way.

For reference, I was trying to pull from a remote branch and got the error message:

Pull is not possible because you have unmerged files.

A google search revealed this commit (d38a30df7dd54c5c6883) to the git source on January 12, 2010.

The error messages have been updated to be much clearer. Before, you’d get “needs merge” or “error building trees” errors, which didn’t really mean much.

In this case, I was pulling in many commits and had a conflict partway through. I just needed to resolve the files, add/delete them, commit the result and then continue with the pull.

We’ll be sending updates on what we’re doing as well as giving valuable tips to make your computing lifestyle a little easier.

Jammit Warning: Asset compression disabled -- Java unavailable

I checked out Java:

> java -version
java version "1.5.0_22"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_22-b03-333-9M3125)
Java HotSpot(TM) Client VM (build 1.5.0_22-147, mixed mode, sharing)

Odd.  Poking into the jammit source, I saw that java 1.4 is required to use the YUI javascript compressor, but I had selected the google closure compiler which requires java 1.6, hence the [unclear] error message.

On Leopard, if you’ve run all your System Updates, you probably have java 1.6, but you have to select it as the default:  Applications > Utilities > Java Preferences > drag new version to top

Also, Luke is helping to organize the Ruby Midwest conference, so you should check that out.

Kansas City Ruby Users Group | March 2010 | Luke Pillow | Jeweler for Rubygems | kcrug.org from Wes Garrison on Vimeo.

Kansas City Ruby Users Group | March 2010 | Ryan Smith | Heroku | kcrug.org from Wes Garrison on Vimeo.

First, some helpful information:

OEM Dell installation CDs depend on the SLP code in the Dell BIOS for activation.  If the installation program can’t see the real bios, it can’t activate.  With a commercially purchased installation CD this is not a problem as you have a COA that can be activated on line or by phone.  OEM installation CDs cannot be activated on line, and since Dell is responsible for support of an OEM disk that was issued by Dell, Microsoft will not normally give you an activation key if you call them.  You can try the phone method, of course, since so far as I can tell you are running only Windows XP Pro rather than both Vista and Windows XP.  Once you explain what you are doing they might grant you an activation code.

If you are installing an OEM version onto a virtual machine, it will not activate as it cannot see the BIOS String of the real Dell machine. It is only seeing the Virtual BIOS which doesn’t have the SLP String to activate.

How to resolve this:

1. Boot up XP Pro VM installation, and select the Telephone activation option for the XP activation.
2. Call MS. Try to go on to speak to a representative to explain further.
3. Here it’s important to explain exactly what you’re doing to the rep — Explain that you simply want to activate this one XP license, on the Dell with which it was purchased, but you are doing so in a virtual machine. They can quickly confirm why it’s not working, due to not seeing the real BIOS.
4. You should end up transferred to the Product Key Team.
5. Once connected with the Product Key Team, they should provide you with a new product key (after confirming you are installing XP on the Dell that it came with and installing just one instance) there are a couple more steps — after entering the new product key, give the new activation code to the rep, get the confirmation to enter in the activation screen; and with luck, success!

$ git push origin master
...
warning: updating the current branch
warning: Updating the currently checked out branch may cause confusion,
warning: as the index and work tree do not reflect changes that are in HEAD.
warning: As a result, you may see the changes you just pushed into it
warning: reverted when you run 'git diff' over there, and you may want
warning: to run 'git reset --hard' before starting to work to recover.
warning:
warning: You can set 'receive.denyCurrentBranch' configuration variable to
warning: 'refuse' in the remote repository to forbid pushing into its
warning: current branch.
warning: To allow pushing into the current branch, you can set it to 'ignore';
warning: but this is not recommended unless you arranged to update its work
warning: tree to match what you pushed in some other way.
warning:
warning: To squelch this message, you can set it to 'warn'.
warning:
warning: Note that the default will change in a future version of git
warning: to refuse updating the current branch unless you have the
warning: configuration variable set to either 'ignore' or 'warn'.

Woah! After some research, this is because I didn’t set up my remote folder as “bare”. A non-bare repository has a working copy attached to it, and this warning is telling you that said working copy exists and is currently checked out to the branch you’re trying to push to.

This is bad, because if you were pushing to a co-worker’s machine, then when they go to commit or run a diff, things will go awry. In this case, I just didn’t set up the repository correctly (it was the first one I’d done!) so I wasn’t in danger of losing anything.

The fix is to use --bare:
git init --bare or git clone --bare