Just a short, simple blog for Bob to share his thoughts.
23 January 2011 • by Bob • Military
In part 2 of my series on the 511th MI Company, we'll take a look at some of the nicknames from the 511th that I managed to write down; although I need to stick to my disclaimer that I did not come up with these nicknames - I just took the time to write them down. ;-]
And my personal favorite:
There is one nickname that I wrote down that I didn't post here, and that was for Bill McCollum. I didn't add his nickname to this list because it might not be fit for the public. If you remember his nickname, you can smile about it now. If you don't, that'll remain a secret between the rest of us.
Who did I miss?
10/21/2014 Update - Bullseye Babbs was a 1LT who took over one of the EW platoons. He earned his nickname on one of the M-60 ranges when he failed to understand how his weapon's scopes worked, so instead of throwing rounds 1km downrange like everyone else, he was thoroughly pulverizing the ground about 5-10 feet in front of us; huge amounts of debris were being thrown into the air as everyone was screaming at him to cease fire. (It probably would have been funny if it hadn't been so dangerous.)
03/14/2018 Update - Terry Knaul dropped me a line to let me know that I had his name listed incorrectly; my apologies, and that has been fixed.
22 January 2011 • by Bob • Military
Over the 3.5 years that I spent in the Fulda Gap with the 511th MI Company, I collected and saved a lot of the stories and lists that the EW and TCAE teams put together. All of this nostalgic trivia is twenty years old now, but it still makes me laugh when I think about the people and times that it represents. Of course, this is mostly a collection of inside jokes with the people that were there.
So this will be part one of a series, and I should point out that I did not create this information - I just took the time to write it down. ;-]
UPDATE: While these were not entirely unique, we often used the following color-coded generic callsigns when we were on recon assignments where only one radio entity was present from each of the different platoons:
07 January 2011 • by Bob • Humor
For those of you who thought that the killer rabbit in Monty Python's "Holy Grail" was a work of fiction, I suggest that you see the top center pane in this stained glass detail from the West Rose Window of Notre Dame in Paris. Apparently brutal bunnies must have been an issue when the French built this cathedral, or perhaps the French will run away from anything.
(Note: Giving credit where it is due, this image is originally from the web page at La Cathédrale Notre Dame de Paris.)
04 January 2011 • by Bob • Humor, Military
Many years ago - more years than I would care to admit - I spent eight years in the Army as a 98G Voice Intercept Operator, which is a long title for someone that spends a lot of time listening to what other people are saying, taking notes, and then telling someone else what was being said. I won't go into any more details about what I did for a living, but for several years I was stationed in Fulda, Germany, where I was a member of the 511th Military Intelligence Company, which was attached to the 11th Armored Cavalry Regiment.
My fellow soldiers and I spent a lot of time hiding in the forests along what was then the border between East and West Germany, which is where the conditions were generally the best for our line of work. During the day we used an AN/TRQ-32(V) Radio Receiving Set, which we affectionately called the "Turkey 32."
The Turkey 32 was my favorite piece of equipment, and it's primarily used for direction finding operations. (Which means "locating the bad guys.") The only trouble with the Turkey 32 was - it used a great deal of fuel, and its generator was horribly loud, so at night we would shut down the Turkey 32 and use our AN/TRQ-30 Manpack Radio Receiving Set to continue our listening activities... which we called the "Turkey 30."
These radios were left over from a bygone era in the distant past - like the Korean War, or maybe the Civil War - so they were really starting to show their age. One of our radios was falling apart - literally. The knobs on the face panel kept falling off, the reception was terrible, the tuner barely moved, etc. I knew that my Turkey 30 was on its last legs and was in dire need of some kind of emergency maintenance, so one day I hauled my Turkey 30 to our Circuits & Electronics (C&E) office to see what my options were. (I was secretly hoping that C&E would replace the radio, but I was almost certain that it would simply spend a few weeks in the shop for repairs.) I had a good friend who was working in C&E that day, SP4 Villarreal, and he replied that as long as the radio was working, there was nothing that he could do about it.
So I started to pack up the radio, and I was probably muttering something about the fact that I had no idea how long it would take for the radio to eventually die, when Villarreal stopped me and said, "Perhaps you weren't paying attention, so listen to me very closely this time - we can't fix it, but if it doesn't work then we can replace it."
And suddenly - the light bulb turned on.
I blissfully carried the Turkey 30 back to our platoon office in the 511th building and announced to everyone, "Gentlemen, this radio has to die - today." So we spent the next hour or so having a contest to see who could throw the Turkey 30 the furthest from the 2nd-story window where our platoon office was located. After everyone had made their share of attempts at breaking the previous distance record, we declared the contest winners with the usual pomp and circumstance that is called for in such occasions - which means that several people were undoubtedly punched a few times before heading back to work.
Once that was taken care of, I packed up the Turkey 30 and strolled back to the C&E office, where I announced to Villarreal that, "For some reason my Turkey 30 has stopped working." Villarreal didn't blink as he overlooked the massive dents and broken glass and replied, "Well, we'll just have to order you a replacement."
It's times like that when it's great to have friends in the right places.
28 December 2010 • by Bob • IIS
Many years ago I wrote Microsoft KB article 203064 about using Server-Side-Include (SSI) files with IIS 4 and IIS 5, but that KB has long since vanished from Microsoft's support website because it was never updated for IIS 6 or IIS 7. I eventually turned the information from that KB article into a blog post, but that being said, I still see questions about SSI showing up in the IIS forums every once in a while. There was a great deal of useful information in that KB article about general SSI syntax and several practical examples for SSI directives, so I thought that it would make a good blog post if I updated the information from that KB for later versions of IIS.
This blog post details some features that are available in the Microsoft implementation of Server-Side Include (SSI) files for Internet Information Server (IIS) and provides general syntax and examples for SSI directives.
SSI files are most commonly used with IIS to allow content authors to include the contents of one file inside another file, allowing the easy creation of script libraries or page headers and footers to standardize the look and feel of your web content. SSI consists of very simple commands that are contained within HTML comment tokens, and are limited in functionality. Higher-level programming languages like ASP, ASP.NET, PHP, etc. make the need for SSI considerably less necessary than in previous years. In addition, programming features such as ASP.NET's Master Pages and Dynamic Web Template (DWT) files that are used by Dreamweaver, Expression Web, and FrontPage have replaced much of the need for SSI. Because of this, SSI is an outdated technology by today's standards. With that in mind, web developers are highly encouraged to migrate their SSI content to another technology, such as ASP.NET or PHP.
SSI files are mapped by file extension to a preprocessor or handler dynamic-link library (DLL), in the same way that file like ASP, ASP.NET, PHP, etc. are mapped to their requisite handlers. In the case of SSI, the specific handler is ssiinc.dll for IIS 4 through IIS 6 and iis_ssi.dll for IIS 7. SSI files on Windows are often named with .stm file extensions, although extensions of .shtm and .shtml are also supported.
cmd
directive for #exec
is disabled by default in IIS 5 and IIS 6. To enable the cmd
directive, see Microsoft KB article 233969.cmd
directive for #exec
is now disabled for SSI files in IIS 7; you can only use the cgi
directive.SSI is employed by the use of special preprocessing directives in SSI documents that are contained within HTML comment tokens; these directives are parsed by the SSI DLL and processed into HTML that is returned to a web client. All SSI directives take the following general form:
<!--#<DIRECTIVE> [<PARAMETER> = <VALUE>]-->
IIS supports a small set of SSI directives, and each directive has different parameters that configure the output for the directive. Other web servers may support a different set of SSI directives and parameters, so SSI files are not 100% compatible across different technologies.
The following directives are supported in the IIS implementation of SSI:
<!-- #CONFIG <ERRMSG/TIMEFMT/SIZEFMT>="<format>" -->
<html> <body> <!-- #CONFIG TIMEFMT="%m/%d/%y" --> <p>Today's Date = <!--#ECHO VAR = "DATE_LOCAL" --></p> <!-- #CONFIG TIMEFMT="%A, %B %d, %Y" --> <p>Today's Date = <!--#ECHO VAR = "DATE_LOCAL" --></p> </body> </html>
<!--#ECHO VAR = "<CGI_VARIABLE_NAME>"-->
<html> <body> <p>Server Name = <!--#ECHO VAR = "SERVER_NAME"--></p> <p>Date = <!--#ECHO VAR = "DATE_LOCAL" --></p> <p>Page URL = <!--#ECHO VAR = "URL" --></p> </body> </html>
<!-- #EXEC <CGI/CMD>="<command>" -->
<html> <body> <p>Root Directory of C:</p> <pre><!--#EXEC CGI = "/cgi-bin/HelloWorld.exe" --></pre> </body> </html>
233969 SSIEnableCmdDirective is set to FALSE by default
<!--#FLASTMOD <FILE/VIRTUAL> = "filename.ext"-->
<html> <body> <!-- #CONFIG TIMEFMT="%m/%d/%y" --> <p>Modified Date = <!--#FLASTMOD FILE="filename.ext"--></p> <!-- #CONFIG TIMEFMT="%B %d, %Y" --> <p>Modified Date = <!--#FLASTMOD FILE="filename.ext"--></p> </body> </html>
<!--#FSIZE <FILE/VIRTUAL> = "filename.ext"-->
<html> <body> <!-- #CONFIG SIZEFMT="BYTES" --> <p>File Size = <!--#FSIZE FILE="filename.ext"--> bytes</p> <!-- #CONFIG SIZEFMT="ABBREV" --> <p>File Size = <!--#FSIZE FILE="filename.ext"--> KB</p> </body> </html>
<!--#INCLUDE <FILE/VIRTUAL> = "filename.ext"-->
<html> <body> <!--#INCLUDE FILE = "header.inc"--> <p>Hello World!</p> <!--#INCLUDE VIRTUAL = "/includes/footer.inc"--> </body> </html>
The #config directive supports a large array of possible parameter values, which are listed in the following table. Note: All of these values are case-sensitive.
Value | Description | Example |
---|---|---|
%A |
Full Weekday Name | Tuesday |
%a |
Short Weekday Name | Tue |
%B |
Full Month Name | December |
%b |
Short Month Name | Dec |
%c |
Full Date & Time | 12/28/10 19:52:19 |
%d |
Day of Month as a Number | 28 |
%H |
Hours as a Number on a 24-Hour Clock | 19 |
%I |
Hours as a Number on a 12-Hour Clock | 07 |
%j |
Julian Date (Offset from Start of Year) | 362 |
%M |
Minutes as a Number | 52 |
%m |
Month as a Number | 12 |
%p |
AM or PM Indicator | PM |
%S |
Seconds as a Number | 19 |
%U |
Week Number (Offset from Start of Year) | 52 |
%W |
Week Number (Offset from Start of Year) | 52 |
%w |
Day of the Week as a Number | 2 |
%X |
Short Time | 19:52:19 |
%x |
Short Date | 12/28/10 |
%Y |
Four-Digit Year as a Number | 2010 |
%y |
Two-Digit Year as a Number | 10 |
%Z |
Time Zone Name | Pacific Standard Time |
%z |
Time Zone Name | Pacific Standard Time |
Note: The following Windows Script Host (WSH) code will create a sample SSI page that you can use to test the parameter values for the #config directive:
Option Explicit
Dim objFSO, objFile, intCount
Set objFSO = WScript.CreateObject("Scripting.Filesystemobject")
Set objFile = objFSO.CreateTextFile("ssitest.stm")
objFile.WriteLine("<html>")
objFile.WriteLine("<body>")
For intCount = Asc("A") To Asc("Z")
objFile.WriteLine("<!-- #CONFIG TIMEFMT=""%" & _
UCase(Chr(intCount)) & """ --><p>%" & _
UCase(Chr(intCount)) & _
" = <!--#ECHO VAR = ""DATE_LOCAL"" --></p>")
objFile.WriteLine("<!-- #CONFIG TIMEFMT=""%" & _
LCase(Chr(intCount)) & """ --><p>%" & _
LCase(Chr(intCount)) & _
" = <!--#ECHO VAR = ""DATE_LOCAL"" --></p>")
Next
objFile.WriteLine("</body>")
objFile.WriteLine("</html>")
SSI directives that use file paths can reference files by using a file or virtual path.
<!--#include file="myfile.txt"-->
<!--#include virtual="/scripts/myfile.txt"-->
For additional information on using SSI with IIS, click the following article numbers to view the articles in the Microsoft Knowledge Base:
For more Microsoft Knowledge Base articles about using SSI with IIS, click here.
Note: This blog was originally posted at http://blogs.msdn.com/robert_mcmurray/
28 December 2010 • by Bob • Guitar, Rants
There was a time long ago in a galaxy far, far away where Rolling Stone Magazine (RSM) had an ounce or two of actual journalistic and editorial credibility. Sadly, that time and place is long gone. Each time RSM puts out another list of the "100 Greatest This" or "50 Greatest That," RSM continues to show just how out of date and out of touch its editors really are.
This leads me to my current rant, which is the following article by RSM:
100 Greatest Guitarists of All Time
http://www.rollingstone.com/music/lists/100-greatest-guitarists-of-all-time-19691231
I realize that these types of lists are highly subjective, and as such no single person will ever be 100% happy with the results - with the notable exception of the guy that made the list. But just the same, here's how I would measure any guitarist's legacy - I use the TOAD elements to gauge their level of impact:
With this in mind, I took a long look at the RSM list, and it's really quite pathetic. Most of the guitarists in their list simply don't belong on anybody's list of guitar greats, while many others are badly slighted or given way more credit than they are due.
Here's a few of my thoughts on the top ten, in the order that they appear on the list:
That wraps up my tirade for the top ten, so here are some assorted thoughts for the rest of the list:
So who got missed? A lot of truly great guitarists. Here are just a few:
I am, of course, leaving out the incredible number of great classical, fingerstyle, and country guitar players; people like Chet Atkins, Andres Segovia, Leo Kottke, Julian Bream, Doc Watson, Christopher Parkening, etc. Each of these guitarists have talent, originality, influence, and durability way beyond most of the guitar players that made the list. Leaving them out is just as dim-witted as the omission of the other guitarists that I had already mentioned.
So there you have it - Rolling Stone Magazine put out another worthless list, and once again they demonstrated that their editorial staff is so out of touch with musical reality that their journalistic credibility is probably beyond reconciliation with their readers. Perhaps someone should explain to them what a guitar is and how it's played, and then build on that foundation until these idiots people understand what it means to be a truly great guitarist.
17 December 2010 • by Bob • IIS, Windows
I've run into this situation more times that I can count: I set up a new web server and no matter what I do, I cannot log into websites on the server that require authentication while I am browsing to them from the console. I used to pull my hair out over this problem until I discovered the problem is in the Windows Local Security Authority (LSA) and it can be easily remedied.
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
in the registry editor.Several years later someone wrote the following KB article that includes this fix with a description of the problem, as well as an alternate workaround:
http://support.microsoft.com/kb/896861
HTH
08 December 2010 • by Bob • BlogEngine.NET, IIS, Windows Phone 7
I love BlogEngine.NET, and I love my Windows Phone 7 mobile phone, so it goes without saying that I would want the two technologies to work together. I'm currently using BlogEngine.NET 1.6.1, but Windows Phone 7 is not supported by default. That being said, it's really easy to add support for Windows Phone 7 by modifying your BlogEngine.NET settings. To do so, open your Web.config file and locate the following section:
<appSettings>
<add key="BlogEngine.FileExtension" value=".aspx" />
<!-- You can e.g. use "~/blog/" if BlogEngine.NET is not located in the root of the application -->
<add key="BlogEngine.VirtualPath" value="~/" />
<!-- The regex used to identify mobile devices so a different theme can be shown -->
<add key="BlogEngine.MobileDevices" value="(nokia|sonyericsson|blackberry|samsung|sec\-|windows ce|motorola|mot\-|up.b|midp\-)" />
<!-- The name of the role with administrator permissions -->
<add key="BlogEngine.AdminRole" value="Administrators" />
<!--This value is to provide an alterantive location for storing data.-->
<add key="StorageLocation" value="~/App_Data/" />
<!--A comma separated list of script names to hard minify. It's case-sensitive. -->
<add key="BlogEngine.HardMinify" value="blog.js,widget.js,WebResource.axd" />
</appSettings>
The line that you need to modify is the BlogEngine.MobileDevices
line, and all that you need to do is add iemobile
to the list. When you finish, it should look like the following:
<add key="BlogEngine.MobileDevices" value="(iemobile|nokia|sonyericsson|blackberry|samsung|sec\-|windows ce|motorola|mot\-|up.b|midp\-)" />
You could also add support for Apple products by using the following syntax:
<add key="BlogEngine.MobileDevices" value="(iemobile|iphone|ipod|nokia|sonyericsson|blackberry|samsung|sec\-|windows ce|motorola|mot\-|up.b|midp\-)" />
That's all there is to it. ;-]
Note: This blog was originally posted at http://blogs.msdn.com/robert_mcmurray/
05 December 2010 • by Bob • Humor
I spent the weekend in Leavenworth, Washington, with my wife, our kids, and my future son-in-law. It was a fun-filled weekend of bright lights, snow-capped mountains, hot apple cider, chestnuts roasting on open fires, and Christmas carols sung by choirs. But the more that I listened to Christmas carols, the more I started to get an interesting picture of Santa Claus.
Like many other people, I grew up with the concept of Santa Claus as a kindly old gentleman that brought gifts at Christmas to all the good children of the world. Santa was like the ultimate grandfather - with a bright red suit, a cheery disposition, a full beard of whiskers, and a sleigh that flew through the air by magic reindeer.
But this year the words to some of the traditional Christmas carols began to really sink in, and I started to see a different Santa. A darker Santa. A scary Santa. Let me give you just a few examples:
My childhood illusion is finally shattered - this Christmas Eve Santa isn't filling STOCKINGS hung by the chimney with care, he's STALKING you by the chimney with care. That's why he's sneaking into your house like a burglar, and why he has so many aliases around the globe - even James Bond doesn't use as many pseudonyms: Saint Nicholas, Father Christmas, Kris Kringle, Grandfather Frost, Yule Man, Sinterklaas, Дед Мороз, etc.
So this Christmas Eve I suggest that you heed the wise advice found in the "Here Comes Santa Claus" Christmas carol: "Jump in bed and cover up your head, Because Santa Claus comes tonight."
11 November 2010 • by Bob • Military
It is the soldier, not the reporter,
who has given us freedom of the press.
It is the soldier, not the poet,
who has given us freedom of speech.
It is the soldier, not the campus organizer,
who has given us the freedom to demonstrate.
It is the soldier, not the lawyer,
who has given us the right to a fair trial.
It is the soldier,
who salutes the flag,
who serves under the flag,
and whose coffin is draped by the flag,
who allows the protester to burn the flag.
--By Father Dennis Edward O'Brien, USMC