From: Luis Lavena Date: 2010-12-16T05:15:26+09:00 Subject: Re: Instiki failing to run - msvcrt-ruby18.dll not found On Dec 15, 9:10 am, John Smth wrote: > > Your English is perfect, and I'm grateful for your support, but would > appreciate some respect for someone who doesn't have your background. > Apologies, but I assume you have certain knowledge of programming. > > 1) Download and install RubyInstaller DevKit: > >http://rubyinstaller.org/downloads > >http://github.com/oneclick/rubyinstaller/wiki/Deve... > > Looking at the installation instructions these are still assuming some > background - how do I remove artifacts from previous installations - is > this as simple as deleting a gem folder somewhere or just as you say > lower down? > > > 2) Uninstalll existing json gem > > gem uninstall json --all > > 3) Install and compile json gem: > > gem install json --platform=ruby > > 4) Start instiki. > > That should solve the issue you're having. > > Unfortunately not (see attachment). Possibly something I've missed with > the Devkit (see my comments above). I was installing the devkit into the > ruby192 folder as this seemed to be 'seen' better (some kind of path > issue) but perhaps this isn't the thing to do. > https://github.com/oneclick/rubyinstaller/wiki/Development-Kit In the wiki instructions it says, unders Step 3: "Left double-click the self-extracting executable downloaded from Step 2 and choose a directory (without spaces) to install the DevKit artifacts into. For example, C:\DevKit. In the instructions that follow, the directory that you selected is identified as ." That clearly indicates where to put (as suggestion) the DevKit > A lot of the stuff I've read just says 'download this' and 'install > this' and 'run this' without actually being detailed about the correct > foldernames or telling you where you should be when running files > (C:ruby192, C:\instiki... etc or what to do if files are not being seen > by the installation. Hence my implied comments about needing the process > KISS. > In the same wiki page: "cd from Step 3 above." That assumes you know how to use the command prompt. "ruby dk.rb init to generate the config.yml file to be used later in this Step. Your installed Rubies will be listed there (only those installed by a RubyInstaller package are detected at present)." If you pay attention to the wiki, will notice the formatting difference between "ruby dk.rb init" and the other text, THAT is a command to be executed (I assume you got this from the Instiki page too) You can't expect a full detail of instructions like "install in C: \FooBar" because it might be the chances your system lacks C: drive (and I have seen those cases) > Please let me know if there are any other 'info' commands I can run that > might localise the issue (apart from layer 8 which is a given). > Please provide me the following 9and cut in your reply all the above but just this information) 1) full output of "gem env" command 2) full output of "bundle show" from inside your instiki folder: * CD C:\where\you\installed\instiki * bundle show 3) Full output that you're getting when executed instiki and get the popup (that is stored in the log folder or shown at the console) === Once you do that, please do: 1) gem uninstall json --all 2) gem install json --platform=ruby Please note the command, needs to be exact, In your previous message you tried "gem install json gem" which was not like the command I showed to you (I used colon to indicate the instruction and a clean new line to show you the exact command that needed to be entered) While I understand your background is not the same, I assume certain criteria from your side to follow these instructions. I have no problem in provide more instructions, but I expect you follow them exactly as I provided. If none of this work, I can go through the installation process and provide you the exact, line by line, installation instructions even with screenshots but that will not solve your problem, as every computer and configuration is different, other things my be interfering in your setup. -- Luis Lavena