So I'm going on vacation next week and being the connected person I am my laptop will be by my side.  I stumbled across a good deal on a second 1GB stick for only $25 after rebate.  Installing the ram was easy as pie in my T60, just unscrew the four screws that have a little ram chip picture next to them and then lift up the touch pad area.  I popped in the ram and turned the system back on.  BIOS shows 2GB so all is good right?

Unfortunately it wasn't that easy.  Vista now wants me reactive.  I tried the online activation with no luck.  I called the 800 number, read the IVR system nine sets of six numbers and of course it couldn't activate me either.  I finally got a person on the phone, definably an overseas individual but their English was great and he was very helpful.  I only had to give him the first set of six and let him know the only thing I did was install ram he promptly gave me the necessary code to reactivate.

While the process wasn't very painful I shouldn't have ever had to do it.  I would assume that adding RAM is one of the most common hardware changes and its someone ridiculous that it would require re-activation.

While I respect Microsoft right to protect their software it is really the guy that follows the rules that gets hurt.  I could have downloaded a hacked version of vista using an OEM bios and never had the problem but instead I followed the rules and had to jump through hoops because I want to follow the rules.

Posted at 7/18/2007 10:16 PM
Comments [1] - Permalink

While working on a dasBlog bug report I found an interesting "feature" in ASP.Net 2.0.   There are a few controls on the configuration page that can be enabled on the client side via JavaScript.  This worked fine and dandy in asp.net 1.1 but in 2.0 it stopped working.  The controls that were enabled on the client side never had any value after postback (in this case it was a CheckboxList). 

After first thinking it had something to do with how dasBlog dynamically loads the configuration usercontrol dynamically it was time to dig into the toolbox for the trusty reflector.  It turns out that asp.net 2.0 won't load the postback data of a checkbox list (or a listbox or dropdownlist) if the control is not enabled. In asp.net 1.1 the control's postback data was always loaded.  Since the controls were being enabled on the client side and not on the server side the postback data was never loaded.

The easiest way to solve the problem is to enable the checkbox list before the postback data is loaded (OnInit or Page_Load).  If needed you can still disable the control later in the page lifecycle.

Posted at 7/16/2007 10:37 PM
Comments [2] - Permalink