Well, this is turning into an all night project, sadly. I uninstalled ruby1.8.2 on my WinXP OS, which did a scorced earth uninstall, wiping clean my c:\ruby directory an taking my instiki 0.10.2 install with it. Completely gone. Guess I won''t be having any worry about migration, eh? ruby 1.8.4 is now running. My distress about the Instiki 0.11.0 README file remains. For me, the 2-step install doesn''t work. I have now placed the instiki files in a location outside of the ruby directory. Executing instiki.rb gets me exactly what I had before with ruby 1.8.2: a blank page in all three of the browsers I use. I really really need some help on this one. I''ve NO idea what to do next. My Windows command window ruby output remains as I have previously reported -- t. ===============================================Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd at bestmindhealth.com >> ===============================================-- ===============================================Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd at bestmindhealth.com >> ================================================
Try install.cmd Tom Cloyd wrote:> Well, this is turning into an all night project, sadly. > > I uninstalled ruby1.8.2 on my WinXP OS, which did a scorced earth > uninstall, wiping clean my c:\ruby directory an taking my instiki 0.10.2 > install with it. Completely gone. Guess I won''t be having any worry about > migration, eh? > > ruby 1.8.4 is now running. > > My distress about the Instiki 0.11.0 README file remains. For me, the > 2-step install doesn''t work. I have now placed the instiki files in a > location outside of the ruby directory. Executing instiki.rb gets me > exactly what I had before with ruby 1.8.2: a blank page in all three of > the browsers I use. > > I really really need some help on this one. I''ve NO idea what to do next. > My Windows command window ruby output remains as I have previously reported > > -- t. > > ===============================================> Tom Cloyd, MS MA, LMHC > Private practice Psychotherapist > Bellingham, Washington, U.S.A: (360) 920-1226 > << TC.BestMindHealth.com / BestMindHealth.com >> > << tomcloyd at bestmindhealth.com >> > ===============================================>
Philip, On Mon, 27 Mar 2006 09:24:18 -0800, Philip Thompson <philip at electricvisions.com> wrote:> Try install.cmdI don''t see why this should do anything. And it doesn''t. The OS says this "is not recognized". You don''t say where it might be. I tried it from within my Instiki 0.11.00 directory, then from system root, then from root of my ruby subdir. All were desperate moves, as I didn''t see where this install.cmd module was in the first place, and so didn''t really expect anything to happen. I really need more information than this, since I don''t know how to get this suggestion to actually move things forward. Sorry! Tom> > Tom Cloyd wrote: >> Well, this is turning into an all night project, sadly. >> >> I uninstalled ruby1.8.2 on my WinXP OS, which did a scorced earth >> uninstall, wiping clean my c:\ruby directory an taking my instiki >> 0.10.2 install with it. Completely gone. Guess I won''t be having any >> worry about migration, eh? >> >> ruby 1.8.4 is now running. >> >> My distress about the Instiki 0.11.0 README file remains. For me, the >> 2-step install doesn''t work. I have now placed the instiki files in a >> location outside of the ruby directory. Executing instiki.rb gets me >> exactly what I had before with ruby 1.8.2: a blank page in all three >> of the browsers I use. >> >> I really really need some help on this one. I''ve NO idea what to do >> next. My Windows command window ruby output remains as I have >> previously reported >> >> -- t. >> >> ===============================================>> Tom Cloyd, MS MA, LMHC >> Private practice Psychotherapist >> Bellingham, Washington, U.S.A: (360) 920-1226 >> << TC.BestMindHealth.com / BestMindHealth.com >> >> << tomcloyd at bestmindhealth.com >> >> ===============================================>> >-- ===============================================Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd at bestmindhealth.com >> ================================================
There is a file named instiki.cmd. Just double click on it. -----Original Message----- From: instiki-users-bounces at rubyforge.org [mailto:instiki-users-bounces at rubyforge.org] On Behalf Of Tom Cloyd Sent: Monday, March 27, 2006 5:18 PM To: Instiki users (rubyforge) Subject: Re: [Instiki] Instiki > blank page still Philip, On Mon, 27 Mar 2006 09:24:18 -0800, Philip Thompson <philip at electricvisions.com> wrote:> Try install.cmdI don''t see why this should do anything. And it doesn''t. The OS says this "is not recognized". You don''t say where it might be. I tried it from within my Instiki 0.11.00 directory, then from system root, then from root of my ruby subdir. All were desperate moves, as I didn''t see where this install.cmd module was in the first place, and so didn''t really expect anything to happen. I really need more information than this, since I don''t know how to get this suggestion to actually move things forward. Sorry! Tom> > Tom Cloyd wrote: >> Well, this is turning into an all night project, sadly. >> >> I uninstalled ruby1.8.2 on my WinXP OS, which did a scorced earth >> uninstall, wiping clean my c:\ruby directory an taking my instiki >> 0.10.2 install with it. Completely gone. Guess I won''t be having any >> worry about migration, eh? >> >> ruby 1.8.4 is now running. >> >> My distress about the Instiki 0.11.0 README file remains. For me, the >> 2-step install doesn''t work. I have now placed the instiki files in a >> location outside of the ruby directory. Executing instiki.rb gets me >> exactly what I had before with ruby 1.8.2: a blank page in all three >> of the browsers I use. >> >> I really really need some help on this one. I''ve NO idea what to do >> next. My Windows command window ruby output remains as I have >> previously reported >> >> -- t. >> >> ===============================================>> Tom Cloyd, MS MA, LMHC >> Private practice Psychotherapist >> Bellingham, Washington, U.S.A: (360) 920-1226 >> << TC.BestMindHealth.com / BestMindHealth.com >> >> << tomcloyd at bestmindhealth.com >> >> ===============================================>> >-- ===============================================Tom Cloyd, MS MA, LMHC Private practice Psychotherapist Bellingham, Washington, U.S.A: (360) 920-1226 << TC.BestMindHealth.com / BestMindHealth.com >> << tomcloyd at bestmindhealth.com >> ===============================================_______________________________________________ Instiki-users mailing list Instiki-users at rubyforge.org http://rubyforge.org/mailman/listinfo/instiki-users
Tom Cloyd wrote:>I don''t see why this should do anything. And it doesn''t. >It does something interesting, nevertheless. Instiki, as packaged, uses SQLite3 for database. This requires a precompiled SQLite library. instiki.cmd is a shell script that adds the directory containing the SQLite library to the system path, so that Instiki (or, to be more accurate, DBI driver for SQLite) can find it there. Then it calls ''ruby instiki''. You might also copy contents of instiki\lib\native\win32\ to some place that''s already on the PATH, such as C:\WINNT\System32\ By the way, that shell script is, indeed, too simple. Double click on it works, but try calling it from another working directory, or passing arguments into it. Not supported. So, if you wants to help this project, here is one thing you can do - a decent launcher script for Win and/or Linux. As far as Windows is concerned, launcher script from Ant is probably a good starting point, it is very comprehensive, as far as I remember.>The OS says this "is not recognized". >Hmm... Any Windows starting from Win NT should recognize it. An older Windows, something like Win 98, wouldn''t know what a .cmd file is, but 2000, XP and 2003 all support the .cmd. Alex