Best Buy [still] sucks

April 1, 2010 at 1:12 PMJoshua Harley

Best Buy

It has been a long, long time since I last set foot in a Best Buy store. Ever since I was able to purchase products from sites like Amazon and Newegg I hardly ever set foot in a brick and mortar store. In fact, the only time I would even think of visiting a store was in the case of an emergency: hard drive failure, power supply failure, and the like. Since I started to notice that may laptop’s current hard drive, a Samsung HM160HI, is starting to overheat I have been looking for a replacement laptop hard drive. Unfortunately, I made quite a mistake....

I had spent the last couple of days researching different laptop hard drives, looking for a drive that has a good balance between capacity, speed, and heat. I had entertained the thought of using this as an excuse to purchase a Solid State Drive but quickly abandoned that thought as 64GB drives currently run between $200 and $300. Of course, I’m currently using about 90GB on my current 160GB drive so I would have to purchase the next viable size up: a 128GB drive, which runs about $400. Forget that!

Having previously upgraded a laptop hard drive in my old laptop I knew that having a 7200 RPM drive over a 5400 RPM drive really does make a world of difference in speed. Of course, a faster speed means higher power consumption and rotational speed (duh), which leads to a higher operating temperature. So with that, I had a target drive type I was looking for:

  1. Must be at least 120GB. (Easy!)
  2. Must run at 7200RPM. (Narrows it down a bit)
  3. Must support SATA II and NCQ. (Pretty much weeds the cheap ones out right there)
  4. Must have positive user reviews. (Narrows it down even more)
  5. Must run cooler than my current one. (Any drive can hit that with no effort!)

Power consumption is actually not on the list since my battery is already 49% worn (meaning it currently operates at 51% of its designed capacity) and I hardly use my laptop away from a power outlet. After much searching and reading I decided to settle on the Western Digital Scorpio Black 320GB 7200RPM drive (Model: WD3200KTRTL). After researching that model I found that it did not have the freefall sensor to park the heads when it was dropped. This was OK actually since I am hardly on the road with it and I *starts knocking on wood* haven’t dropped my laptop yet *stops knocking*.

After checking online prices for the drive through various vendors, I stumbled on the fact that the drive sold at Best Buy for the same price as other online retailers! Not only that but it is in stock!

Best Buy product listing

See? It’s available AND only for $79.99! Well, happy as I am, I finish off the work day and head down to the Greeley Best Buy, expecting to walk out with a hard drive. Of course, I should have known better.

When I finally got in to the store it took me a bit to find their hard drive … shelf. I say shelf because all of the drives they have are on the bottom shelf in the store. They have a few portable ones hanging up in the corner but that doesn’t count. After searching all of the tags on the shelf for about 10 minutes I finally found it. Or rather, where it should be and with a higher price! It was marked at $94.98! (I wish I had taken a picture of it!) $15 markup for going to the store... wonderful! At that point, I pulled the website up on my phone to make sure it was "still in stock" and being sold for $79.99. Yup, it was. A Geek Squad member came over and asked if I needed any help. I directed them to the empty spot on the shelf and asked if it was in stock. What a mistake that was, it took him about 10 minutes to come back and say "Nope, the website must be out of date." Thanks, geek squad, really!

As I was walking towards the door I spotted a normal Best Buy employee. Naturally they asked if there was anything they could do so I figured I'd try again. I asked if they had the drive and about 5 minutes later he came back with it in hand. The exact model I was wanting too (impressive)! Rather than inquire why the previous employee took longer and couldn't find it, I took the drive to the checkout counter.

Checkout Lady (CL): Did you find everything you need?
Me: Eventually.
CL: That's great.
- The price rings up as $94.99. I expected this. -
Me: I noticed online that the price was $79.99. Any chance I can get it at that price?
CL: No it doesn't.
Me: I'm sorry?
CL: The website wouldn't have a different price.
- I pull out my phone and load the website -
Me: See? Here's the site, the model matches, and it's for $79.99.
CL: I can't trust your phone, how do I know you didn't make that up?
Me: *sigh* You can pull it up here if you want.
- The Checkout Lady calls the manager -
Manager (MG): Is there something wrong?
Me: Not really, I was just wanting to purchase this at the advertised price.
MG: The website doesn't have the right price.
Me: Really? That would be bad if the price is wrong then.
MG: It is wrong. We don't have to match what the website says anyway.
Me: All right. Have a nice day. Thanks anyway.
- I walk out. I heard them calling after me but I really didn't want to deal with them anymore. -

As I was walking out of the store I wondered why I even went there in the first place. I didn't really need it right away and the online price was competitive. I suppose I could have ordered it online and picked the "in-store" option, but I am glad I didn't. After getting home, taking a nap, and looking online again. I found the model with the freefall sensor (the WD3200BJKT) available on Amazon for $89.98. So for $5 less I can get a higher model than Best Buy offered as well as free two-day shipping from Amazon! It should be here on April 2nd! Wee!

OK, as I was writing this, something really funny and irritating happened. As I loaded the Amazon page for the WD3200BJKT I noticed something odd... the price dropped! To $79.99! Go figure. Amazon may or may not refund the difference (they don't offer a post-purchase price match guarantee) but I'm not going to worry about it. It's not worth the hassle.

So what did I learn? Best Buy still sucks, the employees are a pain, and I don't plan on ever going to one again. Their prices may be (somewhat) competitive online, but it seems like you still have to buy online and forget about the store.... Oh well, I'll be happy when my drive comes in on the 2nd!

Posted in: Rant

Tags: , , ,

Comment Amusement

March 23, 2010 at 2:38 PMJoshua Harley

As I was upgrading the site, changing themes, and cleaning up spam comments, I came across something amusing. This is a spam script (obviously) from the same computer, but what amused me is that a day after the first (top) comment was posed the second comment was posted as a response (somewhat anyway).

Posted in: General

Tags: ,

1992 meet 2009. 2009 say hello to 1992

August 25, 2009 at 11:51 PMJoshua Harley

I can still remember when I got my first computer. It was a Leading Edge computer running an Intel 8086 with a whopping 512 KB of RAM and an internal hard drive of 10MB! Now that was a kicking system! I quickly learned that HIMEM.SYS and EMM386.EXE only worked with Extended Memory (XMS) and Expanded Memory (EMS).

I quickly learned what things broke the system and which things don’t. format c: /y? Bad! Deletes the drive data! command.com? It’s ok, though it nests a shell.

Well, after installing the latest Windows 7, I started to feel a little nostalgic. I kind of miss those days, back where the operating system didn’t take care of you and you actually had to have an idea of what you were doing.

It got the better of me, so I managed to get Windows 3.11 online and running inside of Windows 7. They got to say hello over the network! It’s amazing that technology from 1992 can still operate in today’s world!

Without further ado, say hello again to Windows for Workgroups 3.11!

Windows for Workgroups 3.11

Posted in: Windows 7

Tags: ,

Explorer still limited by MAX_PATH

August 23, 2009 at 1:41 AMJoshua Harley

With the upcoming release of Windows 7 by Microsoft I am still surprised at a limitation of Explorer that has been around since explorer was first introduced with Windows 95. When Microsoft first introduced Windows 95 they included long filename support. This long filename support allowed Windows to store a filename of “up to 255 characters” while still maintaining compatibility with DOS and previous versions of Windows.

Remember filenames like LETTER~1.DOC and directories like PROGRA~1? Well, believe it or not they still exist by default in Windows 7! You can confirm this yourself by opening a command prompt and running the dir /x command. This will display files in the current directory with both their long filenames and DOS compatible filenames. Of course you can turn this filename generation off by setting the appropriate registry keys.

Back with Windows 95 the Windows API generally provided only ANSI functions. ANSI strings were either single-byte or a variable-width multi-byte arrays. When Windows NT came along with its new kernel, all of the internal strings were represented in Unicode (double-width) character arrays.

The string "HELLO" in ANSI:
Byte: 1 2 3 4 5 6
Data: H E L L O \0
The string "HELLO" in Unicode:
Byte: 1 2 3 4 5 6 7 8 9 10 11 12
Data: H \0 E \0 L \0 L \0 O \0 \0 \0

Along with the Unicode kernel, Windows NT also included updated APIs that used the new Unicode strings. So for every CreateFileA you now had a CreateFileW. To maintain backwards compatibility the original CreateFileA still had the limitation on the length of the path that Windows 95 did. Otherwise known by the macro of MAX_PATH which is defined as 260. Since CreateFileW was a new function, there was no backwards compatibility to maintain, so Microsoft provided a way to provide a path up to 32,676 characters. You can read more about the maximum path length on MSDN.

The drawback of still providing both APIs is that as applications pick and choose they can run into issues with the length of the path. Microsoft Word uses the CreateFileW function which allows them to create longer filenames than explorer can handle. I was hoping that in Windows 7 Explorer would finally be updated to use the Unicode CreateFile function… since Windows 95 was released over 14 years ago.

Unfortunately I ran into Explorer’s 260 character limitation just the other day. One of the deleted files resulted in a path of 273 characters long and the following dialog popped up:

The folder contains items whose names are too long for the Recycle Bin.