This evening I began rebuilding my laptop with Windows 2008 R2, while the install went swimmingly I did run into an issue once my machine was up and running, I couldn’t connect to my wireless network. The now the obvious issue would be that the drivers for my wireless adapter were missing but further investigation cleared that up. My adapter was there but no wireless networks were detected.
So off to the fabled internet I went in search of answers. Turns out the Wireless Auto Configuration service is not installed on the server products by default. Open up the server feature manager and low and behold all the way at the bottom is the option to install the Wireless Auto Configuration Manager. Five minutes later I was connected again.
Now to finish my rebuild before tomorrow morning :os
I’ve been running windows 7 for a while now on both my home and work PC’s and all in all I’ve been pretty impressed. However, today I found one feature/bug that I can see will cause no end of pain.
Today I decided to download the R2 of Windows 2008, so after firing up the Microsoft Transfer Manager selecting the C drive as my download location and then waiting for the next couple of hours my transfer was complete.
The problem, the file I had supposedly stored on my C Drive was no where to be seen. I did some checking in the FTM to be sure the transfer hadn’t failed, but still no file to be found.
So after some much heated clicking around I noticed the following button
Turns out that the file I told FTM to stored in c:\ was placed in “c:\Users\<UserName>\AppData\Local\VirtualStore”
Not very intuitive place to put things Microsoft
Tonight a friend and I headed out to see the new Star Trek film at Hoyts in Melbourne. While we waited for the film to start we got to talking/reminiscing about some of the games we spent our youth playing. Some where between our recount of Grim Fandango and X-Wing Alliance we came to the conclusion that there is a lot of IP out there in the games industry that is ripe to be ported to Xbox Live Arcade.
For example Lucas Arts has around 7 titles that I can think of off the top of my head that were great hits back in the 90’s that would be accepted with wide open loving arms if released to XBLA. As mentioned above Grim Fandango and X-Wing Alliance are a great start. But why stop there when Lucas Arts has some great content in games like Day of the Tentacle, Full Throttle, Rebel Assault and of course the original space flight sim that I’m sure we all sunk more than a few hours into X-Wing vs Tie Fighter
Of course Lucas Arts isn’t the only studio out there that I can see is resting on it’s laurels when it comes to classy game IP from yester year. Take Activision or as they were known in the day Sierra, they had a great series of games in the Space Quest, Kings Quest and Gabriel Knight franchises, while these were probably not amazing graphically they had great storylines and humour that gave them a special charm,
Now I can understand people like Activision and Lucas Arts are probably more focused on your big budget games, but it surprises me that Microsoft hasn’t made an attempt to re-release some of it’s older titles and breath some new life into them. Two I can think of that got a lot of my attention gaming wise was Starlancer and Freelancer both games that have some great co-op and multiplayer prospects, and in theory would not be difficult to move across to the Xbox Architecture.
What I’ve listed above is by no means an exhaustive, and I’m sure there are more you could probably think of but the above are a few that I enjoyed completing more than once.
So this is my official call out to each of these developers/publishers time to look at some of those games that made you great and see if you can’t help us gamers in our mid-20’s relive our youth :o)
Last week I had my first official deployment of SharePoint SP2 in the field. While most of the install succeeded with out any issues I did run into a problem while I was attempting to run the configuration wizard. The error I received indicated that the Timer service failed to start. My first idea was to start the Timer service manually and then re run the configuration wizard.
This approach soon came to a halt, when I started the timer service the service began attempting to run the scheduled update jobs in the background. This caused issues as the configuration wizard would not start as it believed there was an update already in progress.
So now I was stuck with a server that was apparently updating but I had no idea if this was actually happening or not. So after doing some hunting I found I could force the upgrade using STSADM. However I still had the issue that SharePoint thought an upgrade was already in progress.
After a little more hunting I found the following command to reset the Upgrade running status;
STSADM –o setproperty –pn command-line-upgrade-running –pv no
then I ran this command to execute the upgrade using the command line
PSCONFIG –cmd upgrade –inplace b2b –wait –force
10-15 minutes later I was up and running.