Had some good riding with some friends.  Probably the last ride of the season.

Ride with Rob stats:

Ride with Rob Vert Profile:

Google Maps track of the ride with Rob.  Google Earth track of the same.

---

Riding with everyone

Ride with everyone stats:

Ride with everyone vert profile:

Google Maps track of the ride with everyone.  And the Google Earth track of the same.

Here are the details:

The track is here.  And here is the Google earth view.

Here is the track from 9-24-2006.  Some great challenges for the beginner I was with.

The Google Maps GPS track (without track splits)

A view from Google Earth.

The elevation profile:

Went out both days this weekend and had a lot of fun riding. 

The overall stats:

 Heres a set of tracks.

Here is the Google Earth view. (save to disk first)

Here is the elevation profile:

 

I have fixed a couple of annoying bugs with this version.  Now it works cleanly.  Download here.

Nice ride with a co-worker.  (its Google Map, so you can zoom in on the track via the control)

Dryer_Road_8-26-2006.htm (106.36 KB)

    The new netsh in Vista is simly updated with a new section for outbound filtering.  I took some time and made a few example rules for those struggling with the syntax.  The rules below are linked here (Vista-Outbound-Firewall-Rules.bat.txt (1.23 KB)).

Pretty nice.  Finding some processes trying to access the internet such as Windows Error Reporting.  More a pain to translate the event log entries generated then anything.


netsh advfirewall firewall add rule name="IE (TCP)" dir=out program="c:\program files\internet explorer\iexplore.exe" protocol=TCP localip=any localport=any remoteip=any remoteport=80,443 action=allow
netsh advfirewall firewall add rule name="IE (UDP)" dir=out program="c:\program files\internet explorer\iexplore.exe" protocol=UDP localip=any localport=any remoteip=any remoteport=80,443 action=allow


netsh advfirewall firewall add rule name="Firefox (TCP)" dir=out program="C:\Program Files\Mozilla Firefox\firefox.exe" protocol=TCP localip=any localport=any remoteip=any remoteport=80,443 action=allow
netsh advfirewall firewall add rule name="Firefox (UDP)" dir=out program="C:\Program Files\Mozilla Firefox\firefox.exe" protocol=UDP localip=any localport=any remoteip=any remoteport=80,443 action=allow


netsh advfirewall firewall add rule name="Windows Messenger (TCP)" dir=out program="c:\program files\msn messenger\msnmsgr.exe" protocol=TCP localip=any localport=any remoteip=any remoteport=80,443,1863 action=allow
netsh advfirewall firewall add rule name="Windows Messenger (UDP)" dir=out program="c:\program files\msn messenger\msnmsgr.exe" protocol=UDP localip=any localport=any remoteip=any remoteport=80,443,1863 action=allow

Yikes, read this post on a Microsoft forum and it has scared me a little bit about Vista's BitLocker feature.

http://windowshelp.microsoft.com/communities/newsgroups/en-us/default.mspx?dg=microsoft.public.windows.vista.security&tid=9550eb1d-edd7-4905-8e8a-fcaa997faa99&lang=en&cr=US&sloc=en-us&p=1

This essentially means that your system "may" have a significant failure because of a single bit error on a drive.  Now I know I'm sounding a little brazen here, but this is a legitimate concern for users, especially corporate users - the ones most likely to implement this feature.

The only workarounds to this problem are:

1. Don't use BitLocker - Less security is safer?
2. Perform regular backups of your system - this may help but a typical user won't be capable of restoring their system without administrative intervention.  So you end up taking a user down for a day to get their system restored or rebuilt from image - great, just great.

I guess we'll just have to wait for a RAID-able solution.  or some type of parity option.