Guess which version?

Posted by Mike Brittain on January 26, 2010
Microsoft / Comments Off on Guess which version?

Just what do you suppose I should make of this user-agent string?  It’s real.  I found it in my logs today.

Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; Trident/4.0; GTB6.3; Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1) ; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)

Seriously.  We see “MSIE 7.0” in there, which you would initially think of as Internet Explorer 7.  But of course, since we also see “Trident/4.0”, we can deduce that this is Internet Explorer 8 running in Compatibility View.  So what the hell is “MSIE 6.0” still doing in here?

P.S. Thanks for including the version of .NET CLR… 6 different ways. That certainly is helpful.

Tags: , ,

Microsoft’s Lost Vision

Posted by Mike Brittain on July 26, 2009
Microsoft / Comments Off on Microsoft’s Lost Vision

John Dvorak has a great piece on MarketWatch right now about how Microsoft has lost sight of its core business.  He points out a number of great examples of how the company has chased after others in publishing, online networks, search, and music, while none of these areas have anything to do with Microsoft’s history and what it used to do best.  The Xbox isn’t mentioned, and while it might look like a separate business (gaming) I think it probably is pretty close to the idea of building an OS and tools for other developers to build for.  Not a far stretch from building Windows when you think about it.

Dvorak hits on all of the points that bother me about Microsoft.  Personally, I’ve felt that over the years I’ve poured a bundle of money into Windows and Office licenses (for personal and business use) and I can fathom that much of the profit that Microsoft has made on these purchases has been sunk into losing propositions.  And that makes me angry.


Automatic Time Sync in Parallels Virtual Machines

Posted by Mike Brittain on July 29, 2006
Apple, Microsoft / 4 Comments

I’ve been running Parallels on my MacBook so I can boot up a few of the Windows applications I still rely on… which I can tell you is a dwindling number. I noticed a few weeks ago that the clock in Windows XP had gone out of sync on the machine. Basically, if the virtual machine was not running, the Windows clock was completely asleep.

For the first few weeks of running Parallels, I solved this by writing a very simple .bat file that would execute at startup of Windows XP. It ran the Windows time manager and told it to check one of the time servers on the Internet and reset the time on my laptop. I don’t run on a domain or any fancy network at home, so I don’t have a local server I can use for syncing the time.

Anyway, here’s how to set that up:

  1. Open a new text file in Notepad
  2. Paste the following command (without the quotes) into the file: “w32tm /resync /rediscover”
  3. Save the file as synctime.bat. You may find that Notepad automatically helps you by adding on the default .txt extension. If that happens, just rename the file and take off that extension.
  4. Put the file somewhere in your path, maybe c:Windowssystem32.
  5. Create a shortcut to the synctime.bat file and put it into your Startup folder.

When the operating system is restarted, a command prompt will briefly appear showing the w32tm process running, and then it should go away after your clock has been updated.


Well… not exactly. After running this for a few weeks with no trouble, I found that the clock was no longer updating. I opened the command prompt today and entered the w32tm command manually and found the following error:

The computer did not resync because the required time change was too big.

A quick Google search landed me at Microsoft’s TechNet article for Windows Time Service Tools and Settings, which provides in-depth detail on the switches and parameters for using the w32tm utility. Since I’m not running my own time server, most of it was irrelevant to me. I found a couple of registry settings that would correct the issue. These are MaxNegPhaseCorrection and MaxPosPhaseCorrection, and they are found in the registry at:


The default (decimal) value for both of these keys was 54,000, which is 15 hours. This means that if your local clock and the Internet clock that you are syncing to are within 15 hours of each other, the time on your PC will be updated. If they are more than 15 hours apart, forget it.

The TechNet article highlighted a special case for this setting: “0xFFFFFFFF means always make time correction.” So fixing this issue is just a matter of editing a couple of Registry keys.

  1. Open up the Registry Editor. (From your Start Menu, select “run” and enter “regedit”.)
  2. Browse down to the “config” key to find the phase correction settings.
  3. Double-click on MaxNegPhaseCorrection to edit the value. It will read “d2f0” in the hexidecimal value, or 54000 in the decimal value. Select “hexidecimal” and enter “ffffffff” in the field.
  4. Click “OK”.
  5. Make the same change for MaxPosPhaseCorrection.
  6. Close the Registry Editor

Re-run the synctime.bat file and you should fine that the time in Windows has been updated.

If there is a better way to do this, or a different setting that should be used, I’m happy to hear about it. This seems to have fixed my problem with time syncing in Windows, but I’m also pretty new to how Windows manages time syncing on a local network or on a managed domain.

If you have a better suggestion, please post it in the comments area below.

Microsoft’s Anti-Virus Business Will Hurt the Global Network

Posted by Mike Brittain on July 24, 2006
Microsoft / Comments Off on Microsoft’s Anti-Virus Business Will Hurt the Global Network

There is an article on ZDNet today about Microsoft’s security get-together with security and anti-virus companies. The gist is that Microsoft is now a competitor in the space for anti-virus products and will be less likely to reveal some product secrets that they used to share. My guess is that this is true.

It’s unfortunate that Microsoft can’t keep their focus straight. The company’s job, with respect to Windows, is to put forth a secure operating system that is immune, so-to-speak, from computer viruses. The goal shouldn’t be to build some junky security scheme and build another process to guard it. Instead, build the security policy well and maintain an upgrade program that fights problems that arise.

Norton, McAffe, and others have a very valid place in the industry. They play the role of third-party watch guards over the Windows (and Macintosh) operating systems. The product that watches for security problems and viruses really shouldn’t be built by the same people who build the OS and the security policy. That leaves the company (Microsoft) open to compromised decision making on what is and is not a flaw.

Sadly, I believe that companies in the anti-virus industry are going to be hurt by Microsoft’s new tools in Vista. Consumers will tend toward using the tool that comes along for free with Vista. This will inevitably spell trouble for the global network (the majority of consumers and businesses who use the Windows OS) as third-party anti-virus tools, which are now common place, begin to disappear. I suspect that exploits, viruses, and worms will be on the rise.

The watched becomes the watcher.