Why does it have to be so hard to simply install SQL Server 2005? Why can't I simply load a DVD into my computer, see a well designed and thought out install dashboard, make a few choices and click install?

The installation adventure for SQL Server 2005 is some kind of man versus machine epic battle. In one corner you have some poor soul who would like to get some work done today, in the other corner you have Legion. Legion is comprised of many souls including but most certainly not limited to the following: SQL Server Itanium, SQL Server x64, SQL Server x86, 32 bit, 64 bit, Developer Edition, SP1, and so on. Individually all of these things are great. Once you manage to extract the piece you are seeking all is good in the world.  But as long as they are combined into one mindless mob and you have trouble.

Why did the SQL Server 2005 setup application have to be written as a Web application? Was this the best choice for a setup application that runs off of a DVD? Were there any pros to a pseudo Web deployment package? Well, here are some cons:

Scary dialog, that warns me about potential security and privacy issues I should be aware of and avoid.

See, if this wasn't a Web page it could probably detect what Platform I was on and everything.

I'll go ahead and help it out, and choose SQL Server 2005 Developer Edition (English). Too bad I can't give any extra point for getting language right, since English was the only language on the DVD.

Now what should I do? Hmm, autorun.inf says run the HTML application "splash.hta", but this is Web application isn't it? so shouldn't I choose the HTML Document "default.htm"?
Is this background information I know fair to expect of all users? What about new developers? Does this create an artificial learning curve up front? Nobody can use it, until they figure out how to install it.

If you choose default.htm, which I still maintain is a reasonable choice, you will see the above, which reminds me of seeing "You Have Died of Dysentery" message in the old Oregon Trail game you may have played as a kid. At this point you can once again click and "Allow Blocked Content...". Well forcing me to confirm twice is okay because it is just Microsoft left hand watching out for Microsoft's right hand. I can understand that.

Hey where do you think you are going? Don't you know about allowing active content? Are you sure you want to let this file run active content?

Oh, you are. Well, too bad because you have an "Error on page." and nothing is going to happen. So ha. See what I mean about dying of dysentery? Sucks doesn't it?

Alright, some how or another you manage to recover from your dysentery, and make it back to the earlier step and choose "splash.hta". After realizing, that it followed that something named splash must be the installation executable.
Oh look, it needs us to tell it what Platform we are using, AGAIN. Not only can it not determine this on it own, which I'll admit maybe I do want to install the 32-bit (x86) version on my 64-bit OS, but at least remember once I tell you.

Oh boy, looks like we are getting close now. One problem I have with this screen is that nothing is selected by default. I would have one option, probably the "Install Server components, tools, Books Online, and samples" already selected in some manner, even if the text were only marked as bold.
Keep in mind all of the dialogs and forms are building up on our desktop. We now have at least three or four different active dialogs open right now.
If we were to choose an item in the above dialog it would open yet another dialog. One final usability treat is that once you pick a main option of this dialog, it will close itself and only itself. So if you wanted to do more than one thing it has listed, which it looks like it is encouraging then you can either sort through all the open dialogs you have already, or even more fun if you closed any of them, start all over again.
One more thing to note is this screen is labeled as SQL Server 2005 (Disc 1 of 2) is there another dialog for SQL Server (Disc 2 of 2)? One can only wonder considering this DVD is Disc 1 of 1.

Oh yeah! We are about half way through our adventure at this point, but the worst is behind us. From here most hardy adventurers make it to the promised land of our forefathers, and I have confidence you will too.

Take note, that it is after this point that Microsoft ask for your permission to log errors and issues, and track usage to help them improve Microsoft SQL Server, maybe it should be at the beginning of the setup application and not the end?

Gordon: And what about escalation?
Batman: Escalation?
Gordon: We start carrying semi-automatics, they buy automatics. We start wearing Kevlar...they buy armor-piercing rounds.
Batman: And?
Gordon: And you're wearing a mask… and jumping off rooftops. Now, take this new guy. Armed robbery, double homicide.
Got a taste for the theatrical. Like you. Leaves a calling card. [hands Batman a Joker playing card]

BioShock uses the latest version of SecureROM technology which includes an authentication technology similar to the activation process that is used in Windows XP and Windows Vista, with a very strict limitation. You may only install the software twice ever. It does appear they do allow you to install the game twice on two machines if you'd like. And I think you can play simultaneously.

I did find out that if you uninstall BioShock, then you are credited back for the installation. That means as long as your hardware doesn't crash, you don't replace any hard drives with out first uninstalling BioShock while connected to the Internet, then you will be able to continue using BioShock.

You are allowed to contact SecureROM in the event you were unlucky and explain to the powers that be why you deserve another chance.

I believe Office 2007 has this "feature" as well, when it comes to handling volume licence users. If you had 10 licenses, as long as you remembered to uninstall before you formatted, and as long as you knew you needed to, you weren't using up licenses. When did we find out, on our eleventh install, after we called Microsoft up to explain there were only like 8 of us using the software.

My biggest complaint is, it takes a long time to install and setup up a machine, soon it will take just as long to uninstall and clean a machine just to be able to safely format it and start over and keep your software.

Over all it's not a real issue that I think will hinder me, but I don't feel that it helps me either. In the past I've waited until a PC was on its last leg before formatting it, now I may be taking a risk on losing my software long term. And I'm not sure one Mulligan is enough.

It's seems like everyone is in love with this game. If you can get it to run on your system it's a good bet you will be too.

Source: GameStats.com

BioShock is one of the very few Direct X 10 Games that are available now, or anytime soon.

Think you got what it takes to play BioShock? Read 'em and weep.

Operating Systems: Windows XP (with Service Pack 2) or Windows Vista

Minimum System Requirements:
CPU: Pentium 4 2.4GHz Single Core processor
System RAM: 1GB
Video Card: Direct X 9.0c compliant video card with 128MB RAM (NVIDIA 6600 or better/ATI X1300 or better, excluding ATI X1550).
Sound Card: 100% direct X 9.0c compatible sound card
Hard disk space: 8GB free space

Recommended System Requirements:
CPU: Intel Core 2 Duo processor
System RAM: 2GB
Video card:
DX9: Direct X 9.0c compliant video card with 512MB RAM (NVIDIA GeForce 7900 GT or better)
DX10: NVIDIA GeForce 8600 or better
Sound Card: Sound Blaster® X-Fi™ series (Optimized for use with Creative Labs EAX ADVANCED HD 4.0 or EAX ADVANCED HD 5.0 compatible sound cards)

Vista Experience Score:
Processor: 5.0
Memory (RAM): 5.2
Aero Graphics: 5.3
Gaming Graphics: 5.4
Primary Hard Disk: 5.4

Important Note: Game requires Internet connection for activation

The demo for BioShock is 1888 MB alone! So right there you have a hurdle to overcome. You can try downloading it from one of the gaming sites, but most are overwhelmed right now. It is available on Bittorrent from what I read. I wanted to download it from Steam, but even they were maxed out. I ended up using GW Channel's PowerGrid application to stream it down at speeds averaging 3,912 Kbps. Whoo, hoo!

Last year, Friday November 24, 2006 to be exact, Best Buy had Microsoft Flight Simulator X on sale for I want to say for a little over $18. Well, I couldn't resist so I picked up a copy for myself, only to find there was absolutely no way my machine at the time was going to even load this game, much less play it at anything close to acceptable levels.

So I put FSX away, for the time being, until I could see fit to invest into an adequate machine, in case you are curious anything on level of Cybertron or above should do just fine for this game. This game recommends a Windows Vista Experience score of 5.0 or greater. Basically Microsoft FSX already hates your machine, even before you bought FSX. You could by a new machine today, or tomorrow for that matter, and it could be too old for FSX.

Fortunately for me, and thanks to advice I got from Ars Technica's Hot Rod System Guide and Scott Hanselman's Ultimate Developer Rig guides, I was able to build myself a machine that is actually capable of running FSX. Well, at least after I downloaded the patch for Vista that fixes a problem with FSX and multi-monitor systems.

I told you that story, so I could tell you this story...

One of the things I noticed when I was first trying out FSX on my new system, was that you could fly FSX using the Xbox 360 Controller for Windows. You think FSX hates you and your PC, just try using it with either a mouse or a keyboard. I actually have an old Saitek X45 Flight Stick and throttle, but haven't wanted to set it up yet due to two reasons. One it uses a serial RS-232 port to connect to a PC. And two it is HUGE, and needs a whole desk of its own to hold it.

So the idea of reusing my Xbox 360 controller with FSX is perfect. It fits in my hand, and uses our friend USB.

First Attempt:

I have two Xbox 360 wireless controllers and I also have a Xbox 360 Play & Charge Kit. Basically you get a USB charge cable and a NiMH rechargeable battery pack. I know the regular Xbox 360 controller, the non-wireless version, works with Windows XP and Windows Vista out of the box. What about the wireless controllers?

I had read Scott Hanselman's article: "Xbox 360 Controller Wireless Receiver Adapter for Windows". So I know I could buy either an adapter, or a combo pack with both the wireless controller and the adapter, to get my controllers to work with Vista. Or I could just buy a standard non-wireless controller. But I didn't know if my controllers would work by using the USB charge cable. And why spend $20 to $60 if you don't have to?

So I plugged the USB charge cable into my controller, and then again into my PC and waited... Found New Hardware... hmm, this is promising... maybe... Locate and install driver software... Windows couldn't find driver software for your device... Uh, oh... Check for a solution... Contact Microsoft Corporation for support... hmm, not good... but wait there's a link... Download Gaming Software... Controllers, Xbox 360 Controller for Windows, Windows Vista (32-bit), English (US)... Download Xbox 360 Accessories Software 1.1 32-bit for Windows Vista... cross fingers...

Round Two:

...After much wailing and gnashing of teeth, I finally had to face the stark realization that something wasn't right. The question was what? Was it Vista? Was it my new PC? What could it be?

Well, I knew I was wishing and hoping from the start. I mean the Xbox 360 Wireless controller had to have a RF transmitter in it, and the Xbox 360 had to have a matching receiver in it, which was something my PC doesn't have. But did that mean that Xbox 360 wireless controllers don't have the required guts needed to send data out over USB like the standard controllers could do so effortlessly? I had to know.

Final Lap:

Google Search on "Play & Charge Kit PC Support" -> results: Scenyx Entertainment Community: PC Tools and Utilities (Xbox 360 related).

There definitely seems to be some difference of opinion on the matter, even at Microsoft, but in the end I accepted defeat.  It does NOT appear that the Xbox 360 wireless controllers will send any real controller data over the USB charge cable. This had better be due to cost constraints, and not simply an over site or profit decision.

Conclusion:

So I went to my local Game Stop store today and bought a Xbox 360 Controller Wireless Receiver Adapter for Windows today for $20, and took my first flight, in a Bombardier Learjet 45, from KFLO - Florence Regional Airport to somewhere over the Atlantic Ocean. Um yeah, I'm still working on the landings.

"First Flight" Microsoft Flight Simulator: $18 Adequate PC: $1600+ Xbox 360 controller adapter: $20   Getting to join the friendly skies: priceless

Note:

Once you do actually get your Xbox 360 Controller to work with Windows Vista you have a lot of cool opportunities to take advantage of the synergy.

Vista Games - you can use the controller to play any of the games that ship with Vista.

Virtual Earth 3D - this is a great way to explore maps. Very intuitive, responsive, and useful, and not to mention fun.

Games for Windows - any game that get Games for Windows certification is required to have Xbox 360 Controller support

Scott Hanselman's blog, at ComputerZen.com, is one of my favorites. He seems to always have the best answers to the worst problems.

Recently I had purchased a Western Digital MyBook 500GB External Hard Drive. (I managed to find them at a local Sam's Club for only $120, which was a steal at the time.)

I installed and setup the external hard drive and collected at least 200GB worth of data on it before I noticed something. "This hard drive came formatted as FAT32, which doesn't support files larger than 4 gigs."

This was a problem for me for two reasons. I wanted to use the external hard drive for both Virtual PC images and PC backup images, both of which can be larger than 4 gigs.

I knew I could copy off all my data and then format the drive as NTFS, but this meant finding over 200GB of free space on my network, which I could do but would be a hassle to do and the undo again.

Fortunately for me I remembered an article I had read on Scott's blog: "The Duh Files - The file is too large for the destination file system".

C:\Users\CJCraft>convert /?
Converts a FAT volume to NTFS.

CONVERT volume /FS:NTFS [/V] [/CvtArea:filename] [/NoSecurity] [/X]

  volume      Specifies the drive letter (followed by a colon),
              mount point, or volume name.
  /FS:NTFS    Specifies that the volume will be converted to NTFS.
  /V          Specifies that Convert will be run in verbose mode.
  /CvtArea:filename
              Specifies a contiguous file in the root directory
              that will be the place holder for NTFS system files.
  /NoSecurity Specifies that the security settings on the converted
              files and directories allow access by all users.
  /X          Forces the volume to dismount first if necessary.
              All open handles to the volume will not be valid.

Brilliant, simply brilliant. Thanks again, Scott.