From time to time I find myself building Boost on Windows. There's a number of small things that need to be done to make that happen. Having had to "rediscover" the build process each time, I recently decided to create a small Windows command script to automate most of the process.
As I find the build script extremely useful, I figured it would be worth posting it here to inspire others in similar circumstances.
I recently posted an AWK script for combining GPX and HRM files into TCX format. This script is really handy when you have GPX files with or without matching HRM files, but what if you have HRM files without GPX files?
It did not immediately occur to me that there'd be any value in converting lone HRM files to TCX, since I think of TCX as being geographic location focused (which is not strictly true). However, prompted by Conrad, it became apparent that I could indeed convert HRM files (without GPX files) to TCX, and indeed, I already had 30 or so such HRM files that I'd been entering into Strava manually (stationary trainer sessions, and weights workouts).
I've previously presented a GPX + HRM to TCX AWK script (see this post). And while this script can be very useful on its own, I've also written a Windows batch file, and a Bash script to make use of that AWK script a little easier. In this quick post, I'll be presenting the former of the two - ie the Windows batch file.
Now, there are no official binary PIAs for Exchange Server 2000 / 2003. However, Microsoft does provide such PIAs in "source" form (not really source code as such... but we'll get to that) that you can download and compile yourself. There is an MSDN article that explains how to use the Exchange Server PIA wrappers, however I strongly recommend you download the code and read the included "Writing Managed Sinks for SMTP and Transport Events.doc" file instead - it is far more up to date than the MSDN article in areas that are quite significant (such as the actual build process).
Now, the back of the Family Pack box says:
This version of Windows 7 is designed as an upgrade for Windows Vista®. If you are upgrading from Windows® XP, you will need to back up your files and settings and perform a clean install and then re-install your existing files, settings, and programs.
Visit windows.microsoft.com/upgrade for important information.
Which is completely fine with me, because I always do a fresh install anyway, for performance reasons. So, with all my important data backed up, I formated the disk and proceeded to install.
The initial stages of the installation were pleasantly slick - feeling much more refined than good old XP, but the pleasantries were put on hold when it came time to enter my product key, which was consistently rejected! :(
Ok, so I found the registry key responsible for Telstra Bigpond's irritating re-branding of Internet Explorer's window title. This key:
HKEY_USERS\S-1-5-21-682003330-789336058-839522115-1004\Software\Microsoft\Internet Explorer\Main\Window Title
get set to:
"Telstra BigPond Home Internet Explorer"
So I just used the registry editor to change it back to "Microsoft Internet Explorer". Actually, I then experimented a little... I removed the value entirely, and in response, IE's title became "Windows Internet Explorer" - interesting.