Jim,

Thanks for the help!  The RUBYOPT environment variable must be set
behind the scenes somewhere.  I did not have it set in my Windows
environment variables previously, but had just recently added it and
set it to "w" to get more detailed warning messages.  After changing
this to "rubygems" everything worked great again.

Joe