[ruby-talk:6058] Re: Cygwin conflicts

Following up on:

> Andy writes:
>
> #     >Andrew Hunt <[e-mail]> wrote:
> #     >> What do you do if you are running an incompatible version of
> #     >> the Cygnus utilities?
> #     >
> #     >It's my impression that as long as you install the .dll in the same
>
> #     >directory as the executables, that they will be found there before
> #     >looking in some more global location.  So I just put the .dll in
> #     >the \bin\ directory of Ruby and haven't seen any problems.
> #
> # Which is, in fact, where I put the dll in the InstallShield version.
> # The problem is, I also put that bin directory in the PATH, so the cygnus
> # stuff stumbles across it and dies.
> #
> # Now, at the moment (and contrary to my usual Unix philosophy), I am
> # putting Ruby at the head of the PATH.  If I put it at the end, and you
> # are right, then Ruby should look for it's dll first next to it's bin,
> # and cyguns will find their own dll's as usual before stumbling on to
> ours,
> # and everybody is happy.

<previous response snipped>

Well, my first thought upon reading that was "Why didn't I have the presence
of mind to think of that?". But I just tried the same thing again on my
*other* NT4 machine (service pack 5, Cygnus B20) and ran into the same
problem running under the bash shell:

================================================
/Programming/tmp> echo $PATH
/cygnus/CYGWIN~1/H-I586~1/bin:/IBMVJava/eab/bin://C/WINNT/system32://C/WINNT
:/cy
gnus/cygwin-b20/H-i586-cygwin32/bin://c/usr/local/bin/:/bin://C/Perl/5.00502
/bin
/MSWin32-x86-object://C/Perl/5.00502/bin:/program files 2/MS Partial
Resource Ki
t:/usr/local/bin:/IMNnq_NT:/Program_Files_3/Tcl/bin:/Program_Files_3/ruby/bi
n://
c/msdev/bin:/Program Files 2/Java2.0/jdk1.2.1/bin:.:/Program Files
2/Python:/Pro
gram Files 2/Tcl/bin
/Programming/tmp> ruby -v
d:\Program_Files_3\ruby\bin\ruby.exe: *** conflicting versions of
cygwin1.dll de
tected.  Use only the most recent version.

      0 [unknown (0xD2)] ? 0 lock_pinfo_for_update: rc 0, pinfo_mutex
0xFFFFFFFF
, Win32 error 6
/Programming/tmp> type cygwin1.dll
cygwin1.dll is /cygnus/CYGWIN~1/H-I586~1/bin/cygwin1.dll
/Programming/tmp> type ruby
ruby is hashed (/Program_Files_3/ruby/bin/ruby)
/Programming/tmp>
================================================

Now on to some other observations.

After starting the Ruby installer, I got the following message (which didn't
happen on my other NT machine):

================================================
"Setup has completed configuring the Windows Installer on your system. The
system need to be restarted in order to continue with the installation.
Please click Restart to reboot the system."
================================================

I did as requested.

It would be nice if Readme Information subwindow were 10-20 columns wider to
prevent so many line wraps, if this is something under your control.

I got this item again (with different corresponding applications being
involved this time), which still puzzles me:

================================================
"The following applications are using files that need to be updated by this
setup. Close these applications and click Retry to continue."

    Quick
    VIM - d:\tmp\x.ruby_install.vim
================================================

In case it makes any difference, on both NT machines, I had selected the
custom install option (and kept the suboptions).

If one opts not to have the Ruby Installer update the environment settings,
I think the cancel option on the corresponding panel should say that you
will write out this information to <whatever> for you to refer to after the
installation is complete.

After the reboot following installation, I started getting this error when
logging in (which did not occur on my other NT machine):

================================================
[Rough transcription]: MSTips Engine Services: tips.exe - Application Error.
(Some instruction trying to write memory at 0x00000000.)
================================================

By the way, has anyone else tried installing twice on the same machine? That
should eventually become a common occurrance (although usually with
subsequent versions of Ruby). I didn't want to try this until these problems
were resolved.

---------------------------------------------

Finally, I forgot to mention last time that despite these problems, the Ruby
Installer and your great Ruby Logo look very cool and quite professional.

Conrad