Friday, May 02, 2008

I received my new Laptop on Wednesday (30/04/08). A brand spanking new Dell Vostro 1310. I chose it because I wanted something powerful, cheap and professional looking.
Specs as follows:
Processor: T9300 2.5GHz 6MB cache
Ram: 3GB
HD: 320 GB
Screen: 13.3" Widescreen WXGA
Graphics: NVidia GeForce 8400M GS

After a week's wait (the Dell website estimated a 2 week lead time) my laptop arrived. Not a lot in the box:
1 Laptop
1 Power Pack
5 Restore CDs
1 Useless pamphlet
Great, everything worked, the screen is nice and bright, I'm getting fingerprints all over the metallic shiney case but that's inevitable, then... while I'm trying to type a couple of things I realise somethings wrong. It takes a while to dawn on me what it is.. I'm mis-spelling everything I type. This sometimes happens with a new keyboard especially if you touch type as I do but not to this extent. And it's always the same keys. Hang on... this isn't a QWERTY keyboard at all!

If you look carefully at the picture above you see the Z is below the S and D. Now look at your keyboard and (it it's QWERTY) the Z should be below the A and S. The whole bottom register is shifted to the right making touch typing impossible.

My keyboard is also different to all the pictures of Vostro 1310's online.

So I posed the problem at Dell's forums here and was told to contact Dell to get a replacement. After being bounced around Dell customer service for a while a nice Hardware Support guy in India agreed that this isn't a QWERTY keyboard and contacted Customer Care to arrange a replacement. He then came back on the line and told me that this IS the keyboard for the Vostro 1310 and Vostro 1510 line up and I can either stick with it or get a refund.

WTF! I like this laptop, all Dell have to do is sort out the keyboard and I'm a happy customer. I don't want to go through the time and effort of finding, ordering and waiting for delivery of another laptop.
DELL HELP

EDIT:
Just found this on the Engadget website. Sounds like Dell have acknowledged the problem but I haven't been contacted yet!

Friday, April 11, 2008

I'm trying to make my blog searchable from the internet so I'll put in a few reasonably unique words. They will be random and inappropriate and the first words that pop into my head.
Chopin, antithetical, circumlocution.

That should do it.

Monday, March 17, 2008

I needed my treeview only to show a link if a user was in a role that could view that page.

Easy, SecurityTrimming, you may think. However, I use the same ASP.NET page to cover several links in my treeview, some of which may be viewable to the user and some of which may not. SecurityTrimming (if I understand it correctly) would mean I would have to either grant access to the ASP.NET page or deny it; no inbetween.

Fortunately I found and hacked (it didn't work for me without a few changes) some code that removes a link if a user is not in an appropriate role. When a treeview node is databound the sitemapnode is checked for roles and matched to the users roles.


protected void TreeView1_TreeNodeDataBound(object sender, TreeNodeEventArgs e)
{
SiteMapNode myNode = (SiteMapNode)e.Node.DataItem;
foreach (string myRole in myNode.Roles)
{
if (!Roles.IsUserInRole(myRole.Trim()) && Roles.RoleExists(myRole.Trim()))
{
e.Node.Parent.ChildNodes.Remove(e.Node);
}
}
}

Monday, March 03, 2008

A quick test post