Core OS

Anyone catch the Foo Fighters reference?

Commonly referred to as Desktop Aurora or Aurora Desktop, this long forgotten early Vista eye candy can be "hacked up" to work in the newer builds. It is not quite like the earlier builds but it sure it nice being able to run screen savers as your background. It was one of the things I always loved about xscreensaver under unix.

Read more about it here and make sure to grab a copy of the AnimatedDesktop.zip program to automate the process for you.

You can also get it to work under XP although I haven't tried it personally. If you want to see some eye candy inside Vista without grabbing any files or programs, just open up a 'Run' prompt and type 'winsat aurora', hit [Enter] and enjoy.

The AnimatedDesktop.zip method is much more elegant though.

I guess Minesweeper was an unpopular game outside of the US due to problems with land mines. Apparently, this short lived version of Minesweeper, called Mimesweeper, caused an even bigger uproar.

It is too bad people are so easily offended these days or maybe I have a twisted sense of humor.
Read about Mimesweeper and other goodies left out of Vista, here.

Brought to you by the MS Hardware group and others - scripts and information on saving power in your datacenter and/or server room with Windows 2003. It is the framework that the newer Vista power management support was built off of and fleshed out more. By the way, if you have an AMD CPU running under Windows 2003, I highly recommend downloading the updated CPU drivers for much better support overall. This is especially true on the dual core CPUs due to the dual TSC-out-of-sync problem you can run into without proper drivers.

Read more about it here.

Getting familiar with powercfg.exe is worth looking into, also. You can read about it more here.

This seems to show up from time to time in the newer Windows Live Messenger builds but I also suspect due to the bug in the earlier builds of Adobe Flash Player that other applications will also have issues from time to time.

Again, the perils of running betas on betas, but at least this one is an easy fix with a download from here.

I haven't drilled through the dumps from the earlier Adobe builds but I suspect, if you are "lucky", you might get DEP errors under XP, also.

From what I can tell, this is a protocol much like Rendezvous to discover machines and people that are on your local subnet/etc. I know there is much more involved than that but it looks like a bit of a framework to extend applications like Windows Meeting Place and others.

The best reference I can find about the protocol at the moment is here.

Specifically this section:

Windows Vista includes version 2 of the Peer Name Resolution Protocol (PNRP) that is more scalable and uses less network bandwidth. For PNRP v2 in Windows Vista, Windows Peer-to-Peer Networking applications can access PNRP name publication and resolution functions through a simplified PNRP API. For highly simplified PNRP name resolution in Windows Vista, PNRP names are now integrated into the getaddrinfo() Windows Sockets function. To use PNRP to resolve a name to an IPv6 address, applications can use the getaddrinfo() function to resolve the Fully Qualified Domain Name (FQDN) name.prnp.net, in which name is peer name being resolved. The pnrp.net domain is a reserved domain in Windows Vista for PNRP name resolution. The PNRP v2 protocol is incompatible with the PNRP protocol used by computers running Windows XP. Microsoft is investigating the development and release of an update to the Windows Peer-to-Peer Networking components in Windows XP to support PNRP v2.

It looks like the part that I highlighted in bold finally happened.

You can grab the update for Windows XP here.

I've been tinkering with Longhorn quite a bit after hours when I get pockets of free time. If you do it right, you can almost convince people you are running Vista on your XP laptop due to how seemless the windows applications look.

If I really wanted to go all out, of course, I could install Vista on the laptop but I'd much rather do it this way for now. Vista sound drivers are still in development due to the API/engine overhaul (for the good) that happened in Vista. It was always one of my biggest pet peeves that there wasn't a decent way for applications to have different volume levels.

I used to "sort-of" get around it way back when with 2 different Sound Blaster 16 cards in one machine, with one output going into the input of the other one, like the old Adlib or Gravis Ultrasound cards. Unfortunately, back then, many programs did not know how to handle the fact that there were multiple mixers and output devices available under Windows.

OS/2 would handle it fine but by the time OS/2 4.0 came out, there were a whopping 10 applications native to OS/2 (just kidding). OS/2 was a great operating system to run a DOS based BBS on if you only had one machine overall. Running a multiline Renegade BBS became possible and tolerable with that OS.

Back on topic though, Longhorn really is looking like it will be a Citrix killer.

I have an older than dirt Kensington USB Bluetooth dongle that is actually a rebranded / relabeled MSI Bluetooth dongle. Due to the way WIDCOMM originally did licensing and firmware, it is easier getting an organ from the organ donation list than it is to get updated drivers and firmware for most Bluetooth devices.

For whatever reason that I haven't looked into yet, the dongle isn't automatically discovered correctly like most newer BT dongles with the default XP SP2/Vista BT support.

In an effort to get something working under Vista, I ended up pointing Vista to my original XP inf directory for initial BT support of the actual dongle to get rid of the 'Unknown device'. To avoid 30 or 40 'unsigned driver' warnings, I edited the local group policy to 'ignore' the fact that the drivers might be unsigned. Sure, not best practice, but I don't mind bending the rules on my home desktop machine. If I break it, I'm the one that has to fix it anyway.

I ran the WIDCOMM setup in XP SP2 compatibility mode and it installed everything correctly as far as I can tell. There are a few sections of the programs that have quirky display problems, but I just wanted some base functionality with this old dongle until I decide to get a newer USB 2.0 Class 1 Bluetooth dongle.

At least I don't have to suffer with the Toshiba Bluetooth stack that installs 40 COM devices on initial install, even if you are only going to use one COM port. A lot of programs still don't handle anything above COM8 correctly.

An unpatched Toshiba BT stack is also easy to crash if you have your system discoverable and in range of someone with exploit code. Sure, not very common in the real world, but given how difficult it is to get updated Bluetooth stacks from vendors, I am sure most people are still running the older versions.

I am hoping Broadcom, who bought WIDCOMM, will do something like what Agere did with their software modems. They released a 'generic' driver for their chips that might not have all the features of the original OEM drivers, but you can at least download and get basic functionality if you lose your original CDs.

There is a recommended hotfix KB article for Windows 2003 RTM that was published before SP1 came out, located here

It looks like there is a more recent KB article that is specific for Windows 2003 SP1, located here.

You will want to use the right KB for the right service pack level, which most likely is SP1.

Programs, such as decoders and CD burning software, sometimes register ‘filters’ that load either before or after the cd-rom subsystem in Windows.

Sometimes when uninstalling software, they will remove the filter that was registered but leave behind the reference to the filter in the registry.

End result: Yellow exclamation point on every CD and DVD-ROM on the system.

Brute force fix:
Run regedit and drill down to this location:
[HKLM\SYSTEM\CurrentControlSet\Control\Class\
{4D36E965-E325-11CE-BFC1-08002BE10318}]
Export the contents of this location to a registry file backup (right click entry->Export), if you want a backup.
Delete the keys “UpperFilters” and “LowerFilters”

You might have to reinstall CD burning software or DVD decoders, but it is better than a non working drive.

You can also delete the “0000”, “0001”, “0002”, “0003” subtrees if you want Windows to rescan/reload the related CD-ROM drivers. You might have to re-enable digital audio on the CD/DVD-ROM afterwards.

More elegant fix:
Go to the same location and if you know what filter file is missing, just remove the reference to it from either ‘UpperFilters’ or ‘LowerFilters’.

MS’s documentation on this problem:
KB 314060

Sometimes it is specifically related to a filter called GearAspiWDM by Gear Software. It usually comes bundled with software, like iTunes. It has also been known to blue screen 64-bit versions of Windows from time to time too. There are trojans out that register themselves as GearAspiWDM, unfortunately.

Here is Gear software's guide to removing GearAspiWDM if you suspect that filter is the cause of your CD-ROM/DVD problem.

Subject line says it all. If you have an invalid copy and have a valid license to apply to a currently installed OS, go to this website and download KeyUpdateTool.exe.

Previously you had to do some scripting and/or use 3rd party applications to re-register Product Keys.

This is a bit of a strange problem. If you have a group policy set that gives users elevated rights to Windows Installer, the JRE 5.0 installer, when run from an update prompt in the tray, will complain that the administrator has disabled installation.

In fact, the opposite is true, the Group Policy in question gives elevated rights, not a denial of rights.

Another strange fact about this error - JRE 6.0 Beta 2 doesn't seem to have this bug with regards to group policies. If you have the group policy applied for elevated rights, JRE 6.0 will install just fine.

Just curious if anyone else has run into the same bug or not - it looks like it was/is a known issue because JRE 6 doesn't have the logic reversed.

This utility modifies the way IE 7 behaves, primarily by mangling the User Agent string to report that it is actually IE 6.0.

User Agent Changer for IE 7.0

KB 924050 - Telephony API-based applications stop responding and you cannot disconnect telephone calls on a Windows Server 2003-based telephony server

KB 919009 - An incoming fax call may stop responding and not finish in Windows Server 2003

I originally spotted the reference to KB 919009 here.

I'm having some serious deja vu because a few months ago I was fighting with a server that had multiple CPUs that was used as a fax server. About once a day, the TAPI service and Fax service would hang as if it were stuck inside of a kernel call. I suspected there might have been a race condition or a deadlock somewhere, because when I "crippled" the machine to only use one CPU overall, the hangs decreased by a good 95%. Every once in a great while under heavy load, the fax service would quit.

I am going to work on getting both of these KB articles installed on that server and see if it makes the problem go away.

It looks like it was originally created for use by Microsoft.

The 'secret' link to put into IE is:
hcp://CN=Microsoft%20Corporation,L=Redmond,S=Washington,
C=US/Remote%20Assistance/Escalation/unsolicited/unsolicitedrcui.htm

Read more about it here.

Earlier it was mentioned that it would come out on October 5th, but it looks like it came out last night.

http://www.vmware.com/download/vi/