Wow I think I'm sold on eboostr! Thanks much for the insight!

Your results will vary depending on the type of drive you have. I have a 2GB drive that reads at 20,000 KB/sec while my cousin has one that only reads at half that speed. He has R2 installed on his machine and his boot times didn't go down nearly as well as mine did, but thats to be expected since I have a faster access flash drive. Even if your boot time doesn't go down tremendously you will definitely notice a difference in application responsiveness.

For me the answer is much simpler then some of the others given here; if it doesn't work I can't use it and get work done -- so fault tolerance and stability seal the deal for me.

Among other things I do Sound Design for games, film, theater, and television -- and I have several applications and that will consistently BSOD Windows 7.

Moreover on some chip sets even with its newer kernel architecture and HAL Windows 7 has some of the same audio reproduction issues as Windows XP where you'll get drop-outs and popping -- and while these issues have been blamed on some chip sets, the issues don't prevail on the Windows Server OS's...

In a professional audio production environment, as I'm sure is the case in any other professional production environment where time is money; these short-comings just aren't tolerable, and Microsoft and the staffs of large sound and film studios have made no headway to resolving them on Windows 7...

I also agree with yumeyao's remarks about all the ridiculous automation in Windows 7, which is well and fine for a Consumer 'User Land' OS, but in professional production environment can work across purposes of what you need the OS to do, and be a time consuming pain in the ass to reconcile...

Interesting... Out of pure interest, which applications are BSOD-ing your machine? I'm only asking because I'm into audio recording/production myself, and have considered upgrading my current XP-based setup to Win7, so I'm interested in any potential compatibility issues.

Re audio pops/dropouts, in my experience those are usually caused by underpowered hardware or suboptimal drivers, but then you've probably researched this issue thoroughly already. Did you attempt to pin the problem to any specific component of Windows 7 (eg. by disabling potential suspects, to have Win7's list of running processes/services/etc. match that of Windows Server)?

If you ask me, Indrek was just mearly stating his opinion about your idea of a separate forum. You calling him a troll is a personal attack against him and it needs to stop.

There you go. Problem solved.