On 3 Aug, 11:58, Erik Veenstra <erikv... / gmail.com> wrote:
> [Note:  ¨Âáòôó ïæ ôèéó íåóóáç÷åòå òåíïöåôï íáëå éô ìåçáðïóô®Ý
>
> > Is there a work-around for getting rubyscript2exe to work in
> > the meantime?
>
> Add "require 'rubygems'" _in_ your application and temporarily
> remove rubygems from RUBYOPT before compiling:
>
>  RUBYOPT= ruby rubyscript2exe.rb test.rb
>
> Or:
>
>  ¨ÂºÜõîóåÒÕÂÙÏÐ>  ¨ÂºÜòõâù òõâùóãòéðô²åøå®òôåóô®ò>
> That seems to work. At least, on my machine...
>
> gegroet,
> Erik V. -http://www.erikveen.dds.nl/

This doesn't work on  my XP machine with newest oneclick rubyinstall
and rubygems 1.2 (same Gem::Exception error as usual)
I've tried with both rubyscript2exe and rubyscript2exe.rb. Do you have
any other workaround ideas until something is made about rubygems?