Archive for the ‘Vista’ Category

Another problem solved, but I don’t know why

Tuesday, May 5th, 2009

When trying to visit Microsoft’s connect.microsoft.com site earlier today, I was consistently getting the error message:

Internet Explorer cannot display the webpage

This was using IE8. Firefox and Opera both worked fine, so I was a bit perplexed. My impetus for using IE8 (I use Firefox whenever possible) was that a destination site was not working properly. So, I decided to try IE8 to see if it would work correctly. Ultimately, it did, verifying my guess that IE8 isn’t fully disposable quite yet. Along the way, however, I was hitting the “cannot display” roadblock.

I Googled the problem, got a lot of hits, and tried going through a whole shopping list of things to try to resolve the “cannot display” problem. Nothing worked.

Since Firefox and Opera were working, it didn’t occur to me that it might be some kind of DNS issue. Otherwise, those would have been having problems as well. So, I didn’t pursue that angle.

Ultimately, in a whim of desperation, I did an NSLOOKUP on connect.microsoft.com, and tried plugging the IP number into the address field in IE8… and bingo! It worked. I logged in and all looked normal after a detour through the live login site.

After closing and restarting IE, it now works using the name of the URL, as well.

Go figure.

Windows Security Center Lies

Wednesday, April 1st, 2009

Periodically, Windows Security Center lies to me, saying that AVG Anti-Virus Free reports that it is turned off. This is never true. Telling Security Center to turn AVG on—despite its not being off—never clears the bogus message.

For a while, however, I could fix the problem by toggling AVG’s resident shield off and then back on. Today, however, that no longer worked. I did find a solution, though.

What did work was to try to reinstall AVG 8.5, then choosing the Repair option. After running the repair, the problem went away (until next time, I guess).

An alternative would be to tell Windows not to monitor the antivirus status. Personally, I don’t like this option because—who knows—one of these times, Windows Security Center might eventually be correct. Besides, I don’t like sweeping things under the carpet. It leaves a little bulge, and even if it doesn’t, just knowing it’s there makes me uneasy. I don’t want to run the risk of tripping over unseen hazards.

Windows Sidebar Clock Can Steal CPU Cycles!

Saturday, March 21st, 2009

Last night, I noticed that programs were taking a while to start, and my computer was being sluggish in general. I right-clicked Windows Vista’s Taskbar and started the Task Manager to see if I could figure out why. In the Processes tab, I clicked CPU to reverse sort by CPU consumption.

In this picture, both instances of sidebar.exe were showing 0%. Last night, however, one of the sidebar.exe instances was showing 50% CPU usage! Note that there might be two instances of sidebar.exe running. I’m given to understand that the second process is used for managing Sidebar gadgets that do not come with Vista.

In any case, the question for me was WHY?

I closed Sidebar, and CPU usage for it dropped to 0% (although the two processes did not close). I restarted Sidebar, and the 50% problem returned after a short while, although not immediately.

Long story short… I traced the problem to the analog clock that comes with Vista’s Sidebar. I tried closing the gadgets one at a time, thinking that the problem would be with WeatherBug or one of the other add-on Gadgets. But, the problem went <POOF> (that’s techspeak for disappeared) when I right-clicked the clock and chose Close Gadget.

I checked on my laptop computer and the problem does not exist there, so I don’t know how widespread the issue is. However, if you’re noticing that the computer seems to be churning when you aren’t aware of any big programs running… do what I did—check the Processes list in the Task Manager. And, prepare for the unexpected!

In any case, my computer is running a good deal faster this morning. I temporarily replaced the clock that comes with Vista with something called Digital Dutch Clock. But, it exhibited the same problem as Vista’s built-in one. When I get around to installing Windows 7, I’ll have to see if it has the same clock issue. But, for now, I’ve placed an old wooden clock where I can see it.

Icons changed in Windows Explorer, Desktop, and Taskbar… in Vista

Thursday, March 20th, 2008

All of a sudden, a number of my icons changed from their specific normal Vista icons to a generic Windows 2000 icon. This happened to icons on the Desktop, in Windows Explorer, and in Windows’ Taskbar (including Quick Launch and the display of open programs).

I tried several things — including restoring to an earlier point from the same day. Nothing worked to fix the problem, until… I Googled about it and came up with this link:

http://www.vistaheads.com/forums/microsoft-public-windows-vista-general/38375-desktop-explorer-icons-changed.html

Don Varnau, an IE MS MVP, posted a solution that worked for me. I eliminated a step to avoid confusion:

Right-click the desktop and choose Personalize®Tasks (left side)®Change desktop icons®Restore default. When you click Personalize, the Personalization section of the Control Panel opens. Click on Change desktop icons to display the Desktop Icon Settings dialog. Finally, click Restore Default.

And, presto! I’m back in business.

Windows Mail main window font too small in Vista?

Sunday, January 13th, 2008

Do you find the default font in Windows Mail’s main window (see below — shown after resizing to 12 points) too tiny to read? What? You say the default 9 points isn’t big enough? It’s not big enough for me, either.

Fortunately, it’s not cast in stone. It’s controlled by Icon text size, accessible in Windows’ Appearance Settings.

To change it, right-click on Vista’s desktop and choose Personalize. In the Personalization settings, click on Window Color and Appearance. From there, click on the link to Open classic appearance properties for more color options. Then click on the Advanced button to display the Advanced Appearance dialog box, shown below.

Click the dropdown arrow next to Item, and choose Icon. Set the Font: Size: control to the desired font size, then click OK. Back in Appearance Settings, click either on OK or Apply (the latter if you think you might want to experiment a little before settling).

This setting will also make any text on the desktop itself larger, as well. Now, for me personally, that’s that a bad thing, but you might want to experiment with Item Size: if the larger text results in text being clipped on the desktop or in other place controlled by the Icon Font Size setting.

Outlook 2007, Vista, Firefox, and General Failure

Wednesday, December 26th, 2007

Should we salute General Failure?

For some reason, over the past few days, many Firefox users have encountered the General Failure error message when clicking links in Outlook. I haven’t yet tracked down the why in each case (one why occurs when you install the beta of Firefox 3, then remove it and revert to a still-installed Firefox 2.x), but several solutions seem to be floating around:

  • Remove and reinstall Firefox;
  • Change the default browser to Internet Explorer, then change it back to Firefox;
  • Delete the (Default) REG_SZ registry value found at:HKEY_CLASSES_ROOT\FirefoxURL\shell\open\ddeexec

    i.e., replace what’s stored for (Default) with nothing; double-click (Default), select and delete what’s stored for Value data.

Caveat: editing the registry incorrectly can result in your computer not working anymore. It also is a major cause of global warming. Edit the registry at your own risk.

Very Nasty Vista Bug

Tuesday, August 21st, 2007

A reader reports that this no longer occurs in Vista–it was probably fixed by a service pack or another windows update. The problem does not occur in the 64-bit version of Windows 7 (I presume it doesn’t happen in the 32-bit version either, but I cannot verify that since I don’t currently have the 32-bit version running.

Even so… unless you’re sure it’s fixed in the version you’re running, do not try this on any files you want to keep. Best to try it on a test copy of files.

  • In Vista, select a group of files you want to rename.
  • Press F2 (Rename), and type a new name. The files are all renamed using that name, but each file after the first has a number added a la (1), (2), etc.
  • Click Edit->Undo Rename. The file are restored to their original names. So far, so good.
  • Click Edit->Redo Rename. All but one of the files disappear – they are permanently and irrevocably gone. History. Poof. All she wrote.

This is exceedingly nasty.

Note: If you don’t have but want the menu bar in Vista’s Windows Explorer click Organize->Layout->Menu Bar.

Language bar context menu problem

Monday, June 11th, 2007

When I right-click the language bar, the context menu is mostly obscured by the Taskbar. When I right-click other parts of the Taskbar, this does not happen.

Creating New Word 12 Files from Windows Explorer

Sunday, April 15th, 2007

A few days ago, in one of the public newsgroups, someone posted about a problem when creating new Word files in Windows Explorer. First, set your default font in Word to something other than Calibri 11 point. To do this, press Ctrl+D, select a different font and/or point size, then click Default. Click Yes to changing the default. If prompted later, say Yes to saving the changes in Normal.dotm.

Next, try the following:

  1. In Windows Explorer, right click in the files area and choose New->Microsoft Office Word Document.
  2. Type a name for the file, the double-click to open it.
  3. Regardless of your own default font and point size, Word will have created a file that uses Calibri 11 point as the default font.

Now, try it again, only this time choose New->Microsoft Office Word 97-2003 Document. This time, Word will correctly use your defaults, rather than its own hard-coded Calibri 11.

CAUTION: Editing the registry can damage windows and prevent your computer, office, and word from starting. It can also put out an eye. Edit your registry at your own risk.

The behavior for Word 97-2003 documents is controlled by the registry’s settings for what it does when you create a new .doc file in the “shell” (Windows Explorer). This is controlled by the following registry location:

HKEY_CLASSES_ROOT\.doc\Word.Document.8\ShellNew

In particular, it’s controlled by the FileName variable, which tells the system to look for WINWORD8.DOC, contained in the \windows\ShellNew folder.

If you look down a little later, however at:

HKEY_CLASSES_ROOT\.docx\Word.Document.12\ShellNew

there is no FileName variable. So, when you create a new .docx file this way, Word sees that there is no reference template or file, and it uses its own internal default Calibri 11 rather than the user’s default font settings.

A partial fix for this behavior is to create a new FileName variable in the docx registry location, pointing to a file that contains the desired default fonts, such as a file you might name WINWORD12.DOCX (you would need to create that file, too, not just a pointer to it). Then, when you create a new file using the NewðMicrosoft Office Word Document method from Windows Explorer, it will use the defaults contained in that file (WINWORD12.DOCX, for example).

This does not solve the whole problem, however. That’s because when you change the default font in Word 12, it stores the new default in Normal.dotm and in WINWORD8.DOC. The change doesn’t get communicated to your WINWORD12.DOCX.

The obvious solution is to point the .docx\Word.Document.12\ShellNew FileName variable at WINWORD8.DOC, right? Well, that is what logic dictates. However, when you do that and create a new file, the resulting file cannot be opened by Word. So, FileName has to point to a different file.

You might be tempted to point FileName at Normal.dotm in its default location. This, too, doesn’t work. It tells you that the folder is in use, creates two new files (instead of one), and both use Calibri 11 regardless of your default settings. So, unless someone else discovers a different work-around, we’re left with half a solution.

Of course, if you create new files from within Word 12/2007 itself, then you don’t need this solution. You need this solution only if you’re addicted to the Windows Explorer method. In a later article, I’ll look at other solutions.

Repost from 3/8/2007

Sunday, April 15th, 2007

March 8, 2007

Dian Chapman, my technical editor for the Word 2007 Bible, tells me that her two copies of the book arrived yesterday. I still haven’t seen any yet. I emailed Jim Minatel (my AE) to find out why not, and he tells me that the first printing is already out of stock! They’ve ordered a second printing, which will be ready next week. Amazon, Barnes & Noble, Wal-Mart, and other online booksellers seem to have it in stock. So, Wiley’s warehouse loss is their gain. If you order the book now, there should be no delay in its shipping to you.

On the computer front, I ultimately determined that either the motherboard or the GeForce 7300GT was defective. I exchanged the T470 for a different one, and this one has been working like gangbusters. I sure wish I hadn’t invested five days trying to get it to work. But, at least I now have a better idea about how to recognize defective hardware… as opposed to defective Vista drivers. Even so, I’m still gun-shy about installing new versions of the driver.

My most recently solved Vista mystery—apparently—was the presence of an error in my events log:

The following boot-start or system-start driver(s) failed to load: i8042prt

I searched the internet, and didn’t find much specific having to do with Vista. However, in an old Windows 2000 discussion—in Spanish, no less—someone indicated that you see that error message when your mouse and/or keyboard are connected using USB rather than the PS/2 connectors. So, apparently, it’s nothing to worry about. I’m blogging about it here so it might be useful to someone else when they search for the error message.

Another pending mystery—and I hope it doesn’t recur—is why my computer suddenly started saying that my Documents folder was off-limits this morning. This morning while editing an Excel spreadsheet, I suddenly got an error message that the file I was editing was in use and that I couldn’t save to it.

Because I didn’t want to lose what I was doing, I decided to take a quick screen shot. When I tried to save the screen shot, I was informed that I didn’t have permission to access my Documents folder. So, I grabbed the camera, and took a picture of the data onscreen as a last resort.

During this time, the computer was responding extremely slowly, but I didn’t see anything grabbing the CPU in the Task Manager.

I closed everything and rebooted, and the problem has not [yet] recurred. I studied the event logs, but I don’t see anything that happened during that time.

I have two suspicions so far, neither of which are based on anything solid:

  1. My first suspicion is that it has something to do with having installed NOD32 last night — always suspect the new guy, right? — but, that’s just a desperate grasp.
  2. My second suspicion–this is a new computer with an Intel Core2Duo 6300–is that the CPU developed schizophrenia, and that possession of everything disk-based resided in one of the cores and was claiming ownership of my user files and folders, while the other core had suddenly assumed control of the program memory space, and wouldn’t let me access anything because the other core “owned” it.

In months and months of beta testing Vista and running RTM, I never had anything like this happen. But, all my testing/running until this past Tuesday was with a single core Pentium 4, and my A/V software was AVG, not NOD32.

Anybody seen anything similar?

My next adventure is to decide whether to replace Vista Home Premium with Vista Ultimate. Actually, I already know that I’m going to do that. But, I think I’ll install my large SATA, first, and install Vista Ultimate on it. Now, I’ll need to decide whether to install the 32 bit or 64 bit version… or both—maybe one to my X partition and other to my Z partition.

I also want to boost my RAM to 4 GB. It turns out that the 7300GT actually uses shared memory—robbing almost 500MB from main memory—in addition to its own 256MB. Greedy little sucker. I could try to turn off this sharing, but when I did that on the defective T470, my graphics index score went from 4.3 down to 1.0! So, I think I’ll try the upping-the-memory solution, instead.