Scott Hanselman's ComputerZen.com

Recently I needed to inspect a bunch of Visual Basic 6 DLLs (binary) that I [gulp] didn't have the source for. I wanted to see if they were marked in Project Properties when they were compiled as "Retain in Memory" and "Unattended Execution" (Note KBs Q264957 and Q241896) At any rate, a friend pointed me at this COMPLETELY UNSUPPORTED TOOL that you can run from the command-line and it will tell you if your VB6 Binaries are marked appropriately for use in COM+.

KeithBa. KeithBa.com. Keith Ballinger who has dropped off the weblog radar for sometime now seems to have lost his domain [kilic.net] Keith told me last week that he's moving to www.keithba.net although it doesn't appear to be up yet. [Simon Fell]

In reading about Keith losing his Domain Name (I should gone to the PADNUG meeting and asked him about it) it made me want to take some inventory of my domain names.  In the process, I found an one I'd forgotten about - http://www.computerzen.com.  It was just laying fallow, so I pointed it to this weblog with a Response.Redirect just for giggles.

Outlook News Aggregator.
Good news! Version 0.1 of the Outlook News Aggregator is now available for download.  It requires Outlook 2002 (aka Outlook XP).
[Greg Reinacker's Weblog]

This is a FANTASTIC Concept.  I like my applications like I like my women - stylish, elegant, and sitting in the System Tray next to the clock.

Trying to figure out installed versions/service packs of various things on your NT4 / 2000 / XP System?

I use:

• PSInfo from SysInternals (freeware)
  PsInfo is a command-line tool that gathers key information about the local or remote Windows NT/2000 system, including the type of installation, kernel build, registered organization and owner, number of processors and their type, amount of physical memory, the install date of the system, and if its a trial version, the expiration date.
• MDAC Component Checker
  Component Checker is a customizable tool that performs the following tasks - Identifies the current MDAC installation on a computer, Creates a series of reports about the files identified for the current MDAC installation, Removes the current MDAC installation after listing .dll conflicts and identifying programs that reference a given .dll.
• Shavlik's HFNetChkLT for patch management and yummy security goodness
• The MDAC Installation FAQ with version numbers and a compability matrix for all the Windows OSs (95, 98, ME, 2000, NT4, XP) and the MDACs (2.0, 2.1, 2.5, 2.6, 2.7)

Also, for finding the version of the the MDAC manually via regedit (from Network Simplicity)

Summary:
How to determine which version of MDAC is installed on a Windows machine?
Explanation:
Run regedit and search for the following key:

HKEY_LOCAL_MACHINE
      \Software 
          \Microsoft 
               \DataAccess 
                    \Version

Overhead on the 'Net/Quote of the Day:

"Our management style is largely one of deception..."