On Sep 27, 9:07 am, Eric Hodel <drbr... / segment7.net> wrote:
> On Sep 27, 2007, at 07:06 , Trans wrote:
>
>
>
> > On Sep 26, 4:35 pm, Eric Hodel <drbr... / segment7.net> wrote:
> >> On Sep 26, 2007, at 09:05 , Trans wrote:
> >>> Is there anything you have to do after installing the Windows
> >>> OneClickInstaller? I did so and then tried to use RubyGems with now
> >>> success. First I tried:
>
> >>>   gem install rubyscript2exe
>
> >>> but got
>
> >>>   getaddrinfo: no address associated with hostname.(SocketError)
>
> >> This tells me that you weren't attached to the internet, or were
> >> having problems with DNS.
>
> >> While there could be a corner I've missed, I don't believe that
> >> RubyGems prints out just an exception message and nothing else.
> >> Please paste the full command output.
>
> >>> So I download the latest 0.9.4 version of RubyGems
>
> >> Last I checked the one click installer shipped with 0.9.4.  gem env
> >> will give you the version of RubyGems you have installed.
>
> > I downloaded what was on ruby-lang.org and it install RubyGems 0.9.2;
> > I was able to upgrade to 0.9.4 manually --I ran setup.rb a second time
> > and somehow it resolved the problem there. However, I still get the
> > same errors trying to use RubyGems. This is the exact CLI text:
>
> > C:\Documents and Settings\Milton\My Documents\Tom>gem install
> > rubyscript2exe ERROR:  While executing gem ...
> > (Gem::RemoteFetcher::FetchError)
> >     getaddrinfo: no address associated with hostname.(SocketError)
>
> Check `gem sources` to see what hosts you are attempting to attach  
> to.  If you are having problems with DNS, no changes to RubyGems are  
> going to fix your DNS.
>
> > C:\Documents and Settings\Milton\My Documents\Tom>gem install
> > rubyscript2exe -n
> > o-http-proxy
> > ERROR:  While executing gem ... (NoMethodError)
> >     undefined method `[]=' for #<Gem::ConfigFile:0x2e2ebc0>
>
> This is a bug that has been fixed.
>
> Are you using a proxy server?  If you are and you set --no-http-
> proxy, you probably won't be able to connect.

No.

However, I deactivated the Firewalls (turns out there were two on this
machine Microsoft's and Norton's) and then it worked. So it's
definitely a Firewall issue.

T.