I have been beta testing for Microsoft since Windows 98 and it has been a very worthwhile endeavor. However, this is my first experience doing beta testing while being connected to WildBlue Satellite Internet. This added a whole new dimension to the testing process because I wanted to test the stability and compatibility of Microsoft’s beta releases.
I am very happy to report that the switch over was seamless. WildBlue performed at the same level of excellence as it does on my
current operating system. At first I was completely unaware that I was testing in a new environment due to having DSL in previous testing.
I have two hard drives on that machine. One is on the ‘C’ drive and the other is running on a totally different drive, the ‘D’ drive. I am dual booting the system. For those not familiar with this term, at start up I have a choice of booting into both operating systems. Each operating system runs independently of the other and all hardware is installed twice.
This gives me a real world environment in which to see the performance of WildBlue Satellite Internet Service without any crossover from the other operating system. As I stated above, there were no added steps involved and WildBlue ran flawlessly.
I have yet to run the ‘Windows Optimizer’, supplied by WildBlue, on the beta releases. This is the utility that puts the icon for the Portal, Help and Web Mail used by WildBlue Satellite Internet Service. This is the next test I will be performing. I expect it to work as it has in the past, but stay tuned to this spot for an update within the next few days.
Any of you testing for Microsoft while using WildBlue? I would be interested in any feedback you may have. The more we test and debug, the better the user experience will be when Microsoft releases its products. I am very pleased with the results I have had using WildBlue Internet Service. I also welcome any and all questions having to do with WildBlue and issues you may be having using it with your particular operating system. So, let’s talk!