Contents tagged with Windows Vista
Two new sound schemes (glass and pearl)...c'mon you could do better than this in a year and a half...
And a whole bunch of language packs. This time not announced as an extra but the details still tags them as Vista Ultimate content (but just not extra...)
Recently my laptop (DELL XPS m1210) has been really sluggish and I have had several BSOD's when I have been working with it. I try to keep it pretty optimized and up to date so it will behave nice. I think I've read most of the optimize Vista articles and posts and I always keep track on which processes and services running and how much memory is used etc etc.
So I was somewhat confused since the machine has started to behave like this and degenerate over the last few months. Yesterday I went through all the optimization routine once again to find out that nothing helped me out.
The laptop behaved worse when running heavy applications or when the machine has been running for a while, and it felt like there was syrup in the CPU for a few minutes until it was back on track.
I fired up the Windows Vista Resource Monitor, which I think is better than the Task Manager when looking at performance. When I looked at the CPU graph I could see that the CPU Maximum Frequency was dropping from 100% down to 20 or 30% more than often, and especially when running heavy applications! What! The blue line in the CPU graph shows you the maximum frequency used of the CPU.
Modern machines lowers the maximum CPU usage to conserve batteries and power when not needed, but I had my machine running in High Performance and plugged in and I have configured it so that it should always use 100% COU in this mode.
There must be some hardware error I thought and shut the machine down and screwed it open to find out that there were tons of dust in the laptop. I took a deep breath and blew all the dust off. After a real cough-attack I assembled it together and fired it up again.
And WOW, what a difference. Now it runs at 100% all the time!!!
The reason must have been that the CPU and/or the passively cooled graphics card got to warm so the machine lowered the maximum frequency.
So, open up your machines and dust 'em off.
I have several time stumbled upon clients who complain that their hyper linked Office documents (Word, Excel, PowerPoint) opens up in the web browser, Internet Explorer, instead of in their respectively Office application.
Three KB articles focuses on this one (wonder why I have missed them before?).
- KB927009 - A new window opens when you try to view a 2007 Microsoft Office program document in Windows Internet Explorer 7
- KB162059 - How to configure Internet Explorer to open Office documents in the appropriate Office program instead of in Internet Explorer
- KB254918 - How to change Internet Explorer to open linked files in Word 2000 instead of in the browser
There are mainly two methods to make the documents open up in their Office applications; one is to do some registry hacking and the other one is to edit a property in the Registered file types. I think the easiest way is using a registry script.
This script (from KB927009) fixes the issue, just create an empty document with notepad and save the file using a .reg file extension and then double-click the file and accept to import the changes to the registry.
If you don't have Office 2007, then you can remove all references to ????.12, for example Word.Document.12.
Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.Document.8] "BrowserFlags"=dword:80000024 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.RTF.8] "BrowserFlags"=dword:80000024 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.Document.12] "BrowserFlags"=dword:80000024 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Word.DocumentMacroEnabled.12] "BrowserFlags"=dword:80000024 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Excel.Sheet.8] "BrowserFlags"=dword:80000A00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Excel.Sheet.12] "BrowserFlags"=dword:80000A00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Excel.SheetMacroEnabled.12] "BrowserFlags"=dword:80000A00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Excel.SheetBinaryMacroEnabled.12] "BrowserFlags"=dword:80000A00 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.Show.8] "BrowserFlags"=dword:800000A0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.Show.12] "BrowserFlags"=dword:800000A0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.ShowMacroEnabled.12] "BrowserFlags"=dword:800000A0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.SlideShow.8] "BrowserFlags"=dword:800000A0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.SlideShow.12] "BrowserFlags"=dword:800000A0 [HKEY_LOCAL_MACHINE\SOFTWARE\Classes\PowerPoint.SlideShowMacroEnabled.12] "BrowserFlags"=dword:800000A0
Standard registry hack disclaimer: only do this if you are sure what you are doing....
The Release Notes for Windows Vista Service Pack 1 just appeared on the Microsoft Downloads Site. And just after this Microsoft posted a Media Alert: Microsoft Releases Windows Vista Service Pack 1, Windows Server 2008 to Manufacturing.
Vista Service Pack 1 will be available "to customers in March" and Windows Server 2008 will "be available [...] on March 1".
When will it be available on Microsoft Downloads or for MSDN/TechNet Subscribers?
Update 2: Windows Server 2008 is available for MSDN and TechNet Subscribers
Let the fun begin...
Let's see how the download servers will handle this...
Update (later this day): No need for any download servers...we will have to wait a month and a half before it will be available. Sigh...
Finally there is a possible workaround for the missing icons in the Vista Notification Area, see my post from march 2007. The workaround is documented in KB945011 - "System icons may not appear in the notification area on a Windows Vista-based computer until you restart the computer".
It's the network, power and volume icons in the notification area that suffers from this problem. The KB article pins down the cause due to heavy processing on a Vista based machine during the first startup and that it typically not reoccur after the first reboot. This is because of the "welcome sequence" in Vista that initializes services and applications for the first time.
My post on this is one of the most visited posts I've had the last year so I think it's more common than the KB article states...
But I'm sad to say that this one does not always work, it worked when the explorer process was started again, but after a reboot I had my problems once again.
Anyway I have had little of these problems the last few months, so I guess my machine is now "initialized" - only took about eight months...
Thanks to Jack that hinted me to the KB article.
The year of 2007 is about to come to an end, and it has been a really exciting year.
First of all I've had a great year with my family; my daughters turned four and one years old during 2007 and it's so wonderful having them around giving me energy. My wife has been home with them the whole year and next year I will take a few months of parental leave and give them my full attention.
During 2007 we sold our company, iBizkit, which we started in 2000 to a larger company, Pdb DataSystem. This is something we wanted to do for some time. iBizkit forms a new team focusing on portals and SharePoint within Pdb which I think will be great. I can now focus more on doing stuff that I'm good on rather than spending time on administration. After just a few months we have seen a great increase in business opportunities and I hope I can share some of them during next year.
I have been spending a lot of time this year with the new Microsoft Office System 2007 releases; SharePoint Server, Office desktop applications and the standardization of Office Open XML. During the last few months this market has exploded here in Sweden, I'm not sure if we are late or early up here? I have heard through Microsoft channels that the product sales of the Office desktop applications have experienced increased sales numbers during the same period. I look forward to continuing with this during 2008.
The heavily discussed OOXML standardization has of course affected me and I look forward to see what will happen during the BRM in the beginning of 2008. I really hope it will get an approval, which will hopefully result in that ECMA International will submit the XPS (XML Paper Specification), which I think is one really interesting standard.
Summing up 2007 and not mentioning Windows Vista, would feel very odd for me, so here it comes. I had great expectations for Windows Vista during the beta phase and when it was released. Beta testing is nothing compared to working with it eight hours a day. I currently uses Vista as my primary OS for my business laptop and as a Media Center at home. As a Media Center machine, and occasionally playing some games on, is great - except for the d**n lack of graphic driver support from Nvidia. As a primary workstation, I would like to say that it really sucks, if you are doing anything else but using Office 2007! I have been struggling with it for a year now, far to long I think. My rescue has been Virtual PC with a couple of different machines. But I'm positive and have big hopes for Vista Service Pack 1.
And I'm still wondering what will happen to the Ultimate Extras - will it ever be worth the money!
Blogging has been fun, I have not had the time I wished for it but I think I have had some interesting post during the last year. Here are the top five posts of 2007 (written during 2007):
- NVIDIA drivers for Windows Vista with overscan available in march - that did not happen!
- Dissecting XPS, part 1 - The basics - first part of the Dissecting XPS series.
- Customize the Favorite Links in Windows Vista common dialogs
- Using Windows Vista ReadyBoost on an SD-card
- Windows DreamScene Content Pack available - I was not the only one looking forward to this...and got disappointed!
All time favorite post is Watch DVDs in VIDEO_TS folders on Vista Media Center - wonder why :-)
I'm really looking forward to 2008 and this is my whish list for the next year:
- A working version of Windows Vista with Service Pack 1
- That OOXML gets approval from the national bodies
- That XPS is submitted to ISO
- Getting at least a few of our customers to upgrade to Windows Server 2008 and SQL Server 2008
- Having a nice parental leave
- Getting some time over so I can finish msfeedicon version 3
- Testing out the new Media Center for Vista, codename Fiji
- Internet Explorer 8
What are your whishes for 2008?
The list can grow longer, but these are the ones currently on my mind. I will keep blogging about them and other stuff that I find interesting for the moment.
I hope that this blog will continue to grow in number of subscribers, and I would be glad if you give me some feedback on my posts and recommend it to friends and colleagues.
A Happy New Year to all of you!
This shot was taken the day before Christmas eve at our weekend cottage. It was a great scenery with one centimeters of hoarfrost.
Remote Debugging is a great feature to use, especially when you work with virtual machines. It allows you to develop and debug locally but have the code running on another machine, virtual or physical. Microsoft SharePoint can't be installed on a Windows Vista or XP workstation, but needs to be installed on Windows Server 2003 or 2008, so the general recommendations has been for developers to have either Windows Server as their main OS or have a virtual machine with Windows Server. None of these work that well; either you have problems debugging your components and you have to rely on traces or message boxes or you have to have a virtual machine with a full development environment, which will not resemble a production machine.
So, Remote Debugging, is my primary way when working with SharePoint development. It allows you to have a smaller virtual machine, and it will allow you to develop in your main OS. But, Remote Debugging has been quite problematic to set up and configure, so here is a guide that you can follow to get it work in a few minutes.
This guide uses Microsoft Visual Studio 2008 and Windows Vista with UAC on the client and a Windows Server 2003 with WSS 3.0 running in a Virtual PC on the client.
Prepare your remote host
First of all you need to prepare your remote host for accepting incoming debugging requests, this is done by running the Visual Studio Remote Debugging Monitor on the remote machine, which is found under C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger\. Copy that folder to your remote host and place a shortcut to the msvsmon.exe on the desktop, so you have fast access to it whenever you need to debug.
The Remote Debugging Monitor is the one accepting your debug calls and the talking back to Visual Studio on your client, so to get these things to work you have to start the client as the user running Visual Studio (or have administrative permissions on the client). You can either log in to the remote host using that user or, as I prefer, right-click on the msvsmon.exe and choose Run As... Make sure that the user you are using to run the monitor with is member of the local Administrators group.
Now the Remote Debugging Monitor has started to waiting for new debugging connections. The debugging server was named with the username that is running the application and the server name, separated with an @-character. You can rename it using Tools->Options.
Prepare your client
Now it's time to prepare your client. First of all you have to run the Visual Studio 2008 Remote Debugger Configuration Wizard, which will open up the correct ports in your firewall. You will find the wizard under the Visual Studio Tools in your start menu. The wizard also allows you to run the Remote Debugger as a service on the machine which the wizard is run on, skip this step for this guide. When the wizard asks you for how you would like to configure your firewall, choose the Allow only computers on the local network... option and the finish the wizard.
Now it's time to start Visual Studio 2008 and load up your solution and hook up the debugger to the remote machine. Prior to this you need to deploy the application to be debugged on the remote machine, including the .pdb files.
In Visual Studio choose Debug->Attach to process. In the Qualifier you have to enter the name that was given to the Remote Debugger Monitor and hit Enter, then all you need to do is attach to the process you would like to debug and set some break points!
That wasn't to hard?
Here are some problems that I have stumbled upon when trying to get these things to work.
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'XXX. The Visual Studio Remote Debugger on the target computer cannot connect back to this computer. Authentication failed. Please see Help for assistance.
This one is due to the fact that the user running the debugging monitor are not allowed to access the client machine, make sure that the user running the monitor is either the same user running Visual Studio or the member of the Administrators group on your client.
You only see a few processes in the Attach to Process dialog.
First of all make sure you have checked the Show processes from all users check box, then make sure that the user running the monitor has access to the process on the machine, that is you have to make the user member of the local Administrators group. After adding the account to the Administrators group you have to restart the monitor.
Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named 'ibvsretail'. Logon Failure: The target account name is incorrect.
This one is pretty uncommon, but still I have had it. Somehow the server account in Active Directory had gone wrong so I hade to remove the machine from the domain and add it back.
For the last year I have had really annoying security troubles when working with documents in SharePoint (2003 or 2007, WSS or MOSS) on my Windows Vista machine with Office 2007. Every time I have opened up a document for editing the Office applications have asked me to log in to access the document. I have been able to press Cancel three times, but then the document is opened up in read-only mode. The problem has not occurred on any Windows XP installations. I have seen this problem on several computers with Vista. There have been several reported workarounds, of which none has worked for me.
But now Microsoft has released a number of hotfixes, which will be included in the soon to come Vista Service Pack 1, and there are two interesting hotfixes that currently focuses on this problem.
I installed this one first, but it did not fix my problems after rebooting.
But this one did (don't know if it was the combination or if this one did the whole job...)! Sweet!
To get your hands on these hotfixes, before Service Pack 1, you have to call the Microsoft support who will send you the update packages. Last night the Release Candidate of SP1 was released, so I guess these fixes are included in that one. If you have had this problem and are testing the RC of SP1, please inform me on the results.
Neowin.net has posted a picture of suggestions of features for future versions of Windows, gathered from the Windows Early Feedback program. The list contains the top 61 suggestions which is to be presented to the Windows 7 team.
I think it's great that Microsoft tries to listen to the community, but a lot of these suggestions should have been in Windows by now or earlier!
Just take a look at these few examples:
Desktop icons arrangement - allow me to save (247142) This one has been bugging me for years, it should be included in Vista not in Windows 7 that is light years away!
Auto clean up of Temp folders (296526) Cleaning the temp folders is one of the annoying tasks that you manually have to do to often to keep your machine working ok.
IE should have a close button on each tab (250961) The tabs in IE is a great feature but using them efficient is a mess. I would also like a close button on each tab, so you don't have to activate the tab to close it (or right-click). I also would like to have the possibility to configure ctrl-tab to switch to the last used tab instead of always switch to the next. I posted an article a long time ago, that Microsoft should look over all of their tab-designs, read it.
Then you have some interesting suggestions which makes me think where's that focus (remember this is the top 61 suggestions): Include Pinball into next version of Windows...
Some day I will write my own list of future Windows suggestions - I got quite a few!