Posts Tagged Twitter

Getting SATA and Windows XP Installs to Play Nice Together

Before the end of last year, I undertook an interesting project.  One of my coworkers—actually, one of my team members—wanted to downgrade his laptop from Windows Vista to Windows XP.  He had complained about the speed, even with SP1 installed.  I took a look, and I immediately thought the culprit was the onboard graphics and chipset—an Intel 945GM Chipset.  Of course, as the press discovered and class-action suit disclosed, emails sent within Microsoft complained about the performance of this chipset with Vista, but I digress. 

I had thought I blogged this topic, but I had only twittered my victory apparently.  I was contacted by David Bradley via Twitter asking if I was ever able to get this working.  Thus began an email conversation between the two of us concerning this.  I also admonished myself and promised to post my solution to this problem as I recollected it. 

Given the rebuild task, I did some research before starting to grab the drivers I needed and see if there were any other potential issues to be wary of.  I soon discovered a pretty big one.  Windows XP SP2 does not have native Serial ATA (SATA) hard drive support.  In other words, unless you have a floppy with the drivers or have a USB key handy, the installation disc does not contain the appropriate drivers. 

I initially tried to burn an integrated disc, but I was met by a BSOD when the machine rebooted.  I burned a new disc with Windows XP SP3 integrated, and that also resulted in the same “blue” results.  I opted to do a bit more Googling, and I turned up the following two articles concerning the “downgrade” of HP laptops to Windows XP from Windows Vista. 

An Up to Date Guide to Reinstalling WinXP to DV6000T

HP dv8000t Reinstallation Guide

The takeaway from both of these articles and what I learned when I rebuilt this machine—I got it right on the third attempt—is that there is a delicate dance required to get SATA support to work with a new Windows XP installation.  At a very high level, here is what is required to get this installation routine to work:

  1. Make sure to download the appropriate chipset drivers—in this case the Intel 945GM chipset. 
    (If you have any question as to what to install, download and run the Intel Chipset Identification Utility on the machine in question.  Be sure to install the version appropriate to your OS.) 
  2. Extract the SATA driver for your chipset.  This varies based upon the method you can get the storage driver, but in my case, it involved the use of a virtual floppy tool to trick the driver install into believing my PC had a floppy drive. 
  3. Disable Native SATA support in the BIOS. 
  4. Boot from your installation media and proceed with your operating system installation. 
  5. When the installation is complete and you boot into Windows, open Device Manager. 
  6. From Device Manager, select your IDE ATA/ATAPI Controller and select Primary IDE Channel
  7. Choose the “Update Driver” button, and be sure to not search for the driver and instead specify the Intel SATA driver. 
  8. Continue the installation of the drivers, clicking through any security prompts. 
  9. Reboot your machine once complete.  As the machine boots, enter the BIOS and re-enable Native SATA Support.  Save your BIOS changes and reboot. 
  10. Enjoy Native SATA support for your machine, and continue installing the other drivers on your machine as required. 

Now, this procedure will vary depending upon the hardware manufacturer.  Nonetheless, the way to get around the initial install problem is to disable native SATA support, install your OS, install the correct SATA driver for your hard drive interface, then reboot. 

, , , , , , ,

6 Comments

Twitter’s Failure and FriendFeed’s Shortcomings

Various bloggerati are up in arms about the ongoing instability of Twitter.  Information is slightly better than it has been before as the technical folks are communicating the status and their ongoing work to resolve the problems.  Various Twitter clients fail to work, and in some cases the site is completely unreachable.  The FailWhale image has become all too common.

Honestly, I have grown to enjoy Twitter.  Is it something you need to be on?  Not really, but it is incredibly simple to use.  Nonetheless, the downtime of this free product has been annoying–keeping in mind you get what you pay for.  Given this, the most recent exhortation to flock to FriendFeed really started to grind my gears.

I’m spending 80% of my time on FriendFeed instead of here. Move over there, slow adopters. ;-)

Sure, I have a FriendFeed account, and it does some interesting things I like.  Still, FriendFeed to me is just an aggregator.  It relies on folks posting items–links from Google Reader, links from del.icio.us, blog posts, flickr photos, LinkedIn, and other things–to build their FriendFeed content. You still need things like GoogleTalk, Twitter, Pownce, and your blog.  People: use common sense.  FriendFeed is an aggregator of your various points of presence on the Interwebs.  It is nothing more.

My other complaint is how everyone is crowing about “the discussion is happening over on FriendFeed.”  Better yet, I am moving from Twitter to FriendFeed since I can have a discussion.”  If I wanted to have a discussion with people, I would send them an instant message, send them an email, or, for chrissake, pick up the phone and call them.

We have comments in blogs, and that is, quite frankly, where most normal folks who actually have things to do will engage in their “conversations.”  Most normal folks do not have hours on end to comment on someone’s blog post on yet another aggregator.  Call me myopic, but I do not see how FriendFeed is the technical equivalent of the second coming of Christ.

Great, people can comment on my blog, my flickr photos, and my various tweets.  .  Are they commenting on my blog?  On a photo on Flickr?  On Twitter?  No.  They are commenting on someting in FriendFeed.  You know what I call that: FAIL.

At the end of the day, FriendFeed allows me to catch up on things when Twitter’s infrastructure is a smoking mess of plastic and silicon.  Nonetheless, it is just that.  To borrow from William Shatner in a classic SNL sketch:

GET A LIFE, will you people!

, , , ,

6 Comments

Virtual Housecleaning

Last night, I spent some time taking care of some housecleaning on my blog. Here's a brief summary of what I did last night.

  • Installed Bad Behavior Plugin
    I was getting annoyed at the occasional trackback spammer linking to a post--either merely trackbacking to certain posts or completely taking my content to use as a post on an obvious ad-site.  I now have what I consider a pretty good perimeter to protect against comment and tracback spam: Akismet, Spam Karma 2, and Bad Behavior.
  • Corrected a Strange WordPress Error
    I discovered this problem when I was transitioning from Categories to Tags after settling in with WordPress 2.3.1.  WP 2.3.1 transitions from categories to tags, and the database tables that held categories were removed.  When I was removing categories after I had moved to tags, I kept getting a strange error.  The same error would appear when I was updating links in my blogroll and their categories.  The error below (or some variation) was what I would see:

    CODE:
    1. WordPress database error: [Table 'foo_db1.wp_post2cat' doesn't exist]

    I knew that I did not have any plugins referencing categories, and most of my plugins and themes were up-to-date.  I stripped everything down on my blog, but the problem still existed.  Based on a thread here, I decided to upload the WP 2.3.1 base files.  Once I re-uploaded the wp-includes directory, the problem stopped.  It was then that I was reminded of a problem I experienced with FileZilla at the time I updated my blog.  I had thought I had corrected it by performing the upload via scp, but apparently I did not completely upload everything.  I should have been tipped off by another problem I fixed.

  • Corrected a Problem with Windows Live Writer
    When I was using Windows Live Writer, I was getting an error when I would try to have it update the list of categories to select when editing or creating a post.  The error pointed to an error coming from what Windows Live Writer uses to communicate to WordPress blogs, XML-RPC. On a hunch, I looked at the xmlrpc.php file in the root of my blog installation.  I compared it to the standard WP 2.3.1 installation, and I noticed the one on my blog install was older.  I updated that file, and my error in getting categories in Windows Live Writer went away.
  • Cleaned the Blogroll
    I started cleaning up my blogroll.  If you don't see your blog there, do not get offended.  I decided to pare it down to those blogs I read that are updated with some degree of frequency.  I am pondering moving the blogroll to another page just to reduce the clutter on the left margin of my blog, but that is a project for another day.
  • Updated Other Plugins
    I updated a couple of plugins to their latest version.  I have re-added Twitter Tools, and I updated the Subscribe Me plugin as well.  I also added Simple Tags as an easier way to manage tags in WP 2.3.1, as the native tools suck badly.

, , ,

10 Comments

Twitter Updates for 2007-07-26

  • Heading home. #

Powered by Twitter Tools.

No Comments

Twitter Updates for 2007-07-25

  • Paying bills online #
  • Up and at them and hitting the showers after a workout and breakfast. After that, time for coffee. #
  • Off to Evelyn's for coffee in 5 minutes. #
  • Back at the home office with coffee in hand. Need to edit an important document. #
  • @i_heart_pigtown Sorry about my glaring omission. Obviously, it is served with much cheer and no sarcasm as well. ;-) #
  • Off to begin traveling. #
  • Off to Reston. #
  • @bosconet I will be taking your advice depending on when I ultimately leave Reston. #
  • Arrived in Reston. #

Powered by Twitter Tools.

No Comments