Upgraded to WordPress 3.0

As you can tell from the Template, I’ve upgraded to WordPress 3.0 RC. It’s rather simple to do this automatically. Just following these instructions to automatically upgrade WordPress from 2 to 3.

http://wordpress.org/download/nightly

Access NTFS (Windows) Disk from OSX using MacFuse

I know, its nothing new, however not many people know about it. Personally I don’t have that many NTFS external drives, mostly because I knew it would cause issues with Mac and Linux/Unix. So instead I use to format most of my external drives as Fat32. However I would have to make  a couple of partitions manually because Windows 2000/XP actually limited you from creating partitions large than 32/64GB. You can get the specifics because this covers more than this article at WikiPedia:

http://en.wikipedia.org/wiki/File_Allocation_Table

Don’t worry about Fat32, partition your drives as NTFS and make them as large as you want. You can now using them on Mac OSX using MacFuse and NTFS-3g from Tuxera.

Macfuse –  http://code.google.com/p/macfuse/
NTFS-3G from Tuxera – http://macntfs-3g.blogspot.com/

Install both and enjoy!

Enable MultiSite on WordPress 3.0 RC1

I was searching around on how to Enable Multisite on WordPress 3.0 RC1 and I couldn’t find anything, and some sites were incorrectly telling you how.

Here is the official instruction’s from WordPress on their Codex site.

http://codex.wordpress.org/User:Andrea/Create_A_Network

All you need to do is add the following code into your wp-config.php

define(‘WP_ALLOW_MULTISITE’, true);

Exchange 2007: Finding out what version and service pack you’re running.

First  you will need to find out some information about Exchange, and the only way to do that is to open up the Exchange Management Shell and run the following:

Get-ExchangeServer | fl name,edition,admindisplayversion

Then you will be shown the following:


[PS] C:\Documents and Settings\Administrator.BCRICWH\Desktop>Get-ExchangeServer
| fl name,edition,admindisplayversion

Name                : EXCH01A
Edition             : Standard
AdminDisplayVersion : Version 8.1 (Build 240.6)

Name                : EXCH02A
Edition             : Standard
AdminDisplayVersion : Version 8.1 (Build 240.6)

Name                : EXCHMBX01
Edition             : Enterprise
AdminDisplayVersion : Version 8.1 (Build 240.6)

Name                : mx4
Edition             : Standard
AdminDisplayVersion : Version 8.1 (Build 240.6)

Name                : mx3
Edition             : Standard
AdminDisplayVersion : Version 8.1 (Build 240.6)

As you can see the Version isn’t really all that informative. But its rather simple, the 8 stands for Exchange 2007 and the 1 stands for Service Pack 1. The build will also confirm that this is SP1, however I’m assuming it only changes when there are hotfixes or rollup updates.
Anyways, you can get all the version and build numbers from Microsoft at the following URL.
I am also going to copy and paste them here for historical purposes.
Exchange Server 4.0 4.0.837 April 1996
Microsoft Exchange Server 4.0 (a) 4.0.993 August 1996
Microsoft Exchange Server 4.0 SP1 4.0.838 May 1996
Microsoft Exchange Server 4.0 SP2 4.0.993 August 1996
Microsoft Exchange Server 4.0 SP3 4.0.994 November 1996
Microsoft Exchange Server 4.0 SP4 4.0.995 April 1997
Microsoft Exchange Server 4.0 SP5 4.0.996 May 1998
Microsoft Exchange Server 5.0 5.0.1457 March 1997
Microsoft Exchange Server 5.0 SP1 5.0.1458 June 1997
Microsoft Exchange Server 5.0 SP2 5.0.1460 February 1998
Microsoft Exchange Server 5.5 5.5.1960 November 1997
Microsoft Exchange Server 5.5 SP1 5.5.2232 July 1998
Microsoft Exchange Server 5.5 SP2 5.5.2448 December 1998
Microsoft Exchange Server 5.5 SP3 5.5.2650 September 1999
Microsoft Exchange Server 5.5 SP4 5.5.2653 November 2000
Microsoft Exchange 2000 Server 6.0.4417 October 2000
Microsoft Exchange 2000 Server (a) 6.0.4417 January 2001
Microsoft Exchange 2000 Server SP1 6.0.4712 July 2001
Microsoft Exchange 2000 Server SP2 6.0.5762 December 2001
Microsoft Exchange 2000 Server SP3 6.0.6249 August 2002
Microsoft Exchange 2000 Server post-SP3 6.0.6487 September 2003
Microsoft Exchange 2000 Server post-SP3 6.0.6556 April 2004
Microsoft Exchange 2000 Server post-SP3 6.0.6603 August 2004
Microsoft Exchange 2000 Server post-SP3 6.0.6620.5 March 2008
Microsoft Exchange 2000 Server post-SP3 6.0.6620.7 August 2008
Microsoft Exchange Server 2003 6.5.6944 October 2003 Microsoft Exchange Server 2003 SP1 6.5.7226 May 2004
Microsoft Exchange Server 2003 SP2 6.5.7638 October 2005
Microsoft Exchange Server 2003 post-SP2 6.5.7653.33 March 2008
Microsoft Exchange Server 2003 post-SP2 6.5.7654.4 August 2008
Microsoft Exchange Server 2007 8.0.685.24 or 8.0.685.25 December 2006
Microsoft Exchange Server 2007 SP1 8.1.0240.006 November 2007
Microsoft Exchange Server 2007 SP2 8.2.0176.002 August 2009
Microsoft Exchange Server 2010 14.00.0639.021 October 2009

Fix for Windows XP not able to Remote Desktop to Windows 2008 Server

It’s a simple registry fix, you can read the KB Article 951608 from Microsoft.

http://support.microsoft.com/kb/951608

This will then allow you to connect to Windows 2008 Server computers as well as Windows 7 computers.

UPDATE: This won’t work for mRemote or mRemote-NG, for some reason you can only use for instance “mstsc” or Remote Desktop Client directly.

Fixes for WordPress Twitter Updater by Ingoal

I’ve fixed up the WordPress Plugin Twitter Updater by Ingoal and a number of others (Eric Austin Lee, Victoria Chan). Here’s my changed to the plugin.

Edited by
Jordan Trask (April 17th 2010 – http://geektank.net (v2.09)
– ZZ.gd broke with 403 forbidden error, fixed with setting different user agent.
– Move menu to “Settings”.
– Added option under configuration to choose ZZ.gd or TinyURL. Added 1 function.
– Re-worked the code for url shortening services, change in one place instead of three. Created a function instead.
which makes it easier to add more services if necessary. Bit.ly support in the future?

Edited byJordan Trask (April 17th 2010 – http://geektank.net (v2.09)- ZZ.gd broke with 403 forbidden error, fixed with setting different user agent.- Move menu to “Settings”.- Added option under configuration to choose ZZ.gd or TinyURL. Added 1 function.- Re-worked the code for url shortening services, change in one place instead of three. Created a function instead.  which makes it easier to add more services if necessary. Bit.ly support in the future?

You can download the new version, I’ve renumbered the version number and hope to have bit.ly setup as well.

I’ve removed the download and placed all relevant information on the Twitter Updater page.

Twitter App for Facebook is Broken! But Twitter Support is Non-Existant!

I have had time to blog that much, but since I’ve got some time today. I thought I might talk about how I’ve stumbled upon my own issues with Twitter. I’ve talked to https://twitter.com/fabbrunette about her issues with her password reset problems and Twitters phone verification not working at all. And then the on going issue of actually trying to get help without a login.

But lets cover my problems, because its all about me today. Ha.

The problem, I can’t add the Twitter application to my Facebook account. I know, I know, applications are the suck. But I thought I would have my twitter followers and facebook friends enjoy the comfort of my ramblings equally. Instead of favouring one platform, I can get the attention of my IRL (In Real Life) friends and my Twitter “followers”.

When I try to add the application, it asks for my login. I input my login and then am greeted with a “Wrong username or password”. So I decided to be smart about it, and use my email address, same outcome. So I change my password, same outcome. So I create a new Twitter account to see if that works. First try, same outcome, second try it works.

I don’t understand. Like seriously, I know I might sound a little annoying and bitchy, but it gets better.

So who do I talk to about this issue? Well Twitter of course, so I decided to click the “Help” and see what I might get out of this. To my surprise there is already a topic on the issue.

http://help.twitter.com/entries/87314-i-can-t-add-twitter-to-my-facebook-account

It might not be the issue im experiencing exactly, but its the right topic. But the comments are closed, so what to do now?

VirtualBox Default Intel Network Card Not Recognized by Windows XP

I did a fresh install of VirtualBox on my Mac Book Pro and then install Windows XP. Once installed I noticed that there was no network card showing up under “Network Connections”. I checked out the Device Manager and found that the network card was showing up with now driver. After searching around, I figured out that the AMD PCNET III driver seems to work out of the box. If you power down the machine and change the adapter, it should detect and install properly and you’re good to go.