You need sqlite3.dll installed:
http://blog.mmediasys.com/2009/07/06/getting-started-with-rails-and-sqlite3/
(Getting SQLite3 step)
--
Luis Lavena
AREA 17
-
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
It is a newer version? or older?
I'm using 3.6.14.1 without issues.
I've tried version 3.6.23.1 too without issues.
Please check in the PATH if any other, old version, of sqlite3.dll
could be interfering.
Also, a recommendation: using RubyInstaller releases as seems you're
using the 1.9.1 releases from garbagecollect.
It can't be right.
You installed RubyInstaller, which is x86-mingw32 platform, yet still
the backtrace of the error you reported indicates x86-mswin32-60
version of the gem installed.
This means you manually indicated the platform when installed? Why?
Please remove the gem and install the appropriate one: "gem install
sqlite3-ruby" should download x86-mingw32 one.
Also, are you sure that D:\Ruby191\bin appears before any other PATH,
including system32? in some cases ppl recommended install sqlite3.dll
into system32, which is plain wrong (it is not Windows 3.1)
Can you not use PowerShell?
C:\Users\Luis>ruby -v
ruby 1.9.1p378 (2010-01-10 revision 26273) [i386-mingw32]
C:\Users\Luis>gem list sqlite3
*** LOCAL GEMS ***
sqlite3-ruby (1.3.0 x86-mingw32)
C:\Users\Luis>where sqlite3.dll
C:\Users\Luis\Tools\bin\sqlite3.dll
C:\Users\Luis>irb
irb(main):001:0> require 'sqlite3'
=> true
irb(main):002:0>
Can you *not* use PowerShell?
We need to determine which DLL is being used by your system, normally,
use the command prompt.
Oh, Windows XP then, sorry. we should have started by that.
I understood that PowerSheel did not understood it, and since I don't
use it, didn't now how to proceed and say to you except "don't use it"
Please provide me the output of:
SET PATH
SET HOME
gem env
gem list sqlite3-ruby -d
Also, try as mentioned by Brandon: download latest binaries and put
them in Ruby bin folder.
It might be a corrupt binary?
> Do you still want to see the info you asked for or should we just
> leave it?
>
I think if the issue is solve, let's keep the other questions for the
next time ;-)
> Anyway, thanks a lot for all your help.
>
You're welcome. Glad you solved it.