On Thu, 25 Jan 2001 21:26:12 +0900, Jan Matejka <Jan.Matejka / koncept.cz> wrote:
> Strange thing happened: both ruby162-0.exe and 
> ruby162-1.exe are identicall; 
> look at  MD5 checksums
> 
> 9ceb0e750210ff139243aa3f6a4557a9 ruby162-0.exe
> 9ceb0e750210ff139243aa3f6a4557a9 ruby162-1.exe
> 
> MaT

There are actually both ruby162-1.exe, there is no ruby162-0.exe
anymore -- we stuck that there as a placeholder while having
the web server problems.

I am seeing these reports of many problems with the RubyWin
executable -- I've dropped a note to the maintainer, but
I guess that he's out of town or bust just at the moment.

Do you think we should keep RubyWin in the Windows distribution?
I would hate to scare off new users with a face-full of bugs
right out of the gate.

As far as the installer itself goes, I will look into problems
when using spaces in the target directory path -- in the meantime,
stick to c:\ruby :-)

/\ndy