create new tag
, view all tags
I have just started on the WikiThing and having a partially working Dec2000 TWiki working on Windows 2000 (I can't get the RCS and version stuff working) I decided maybe I should try out the beta. I can't find any tips on how to install it though.. I tried to do something like what had to be done with the Dec2000 release but have had no luck. Any help would be great!

-- MichaelCodanti - 30 Jul 2001

How about more details about what works and what does not?

Have you read the TWikiOnWindows topic?

-- DavidLeBlanc - 30 Jul 2001

Yes I have read it. I have done everything it lists and the Dec2000 version still doesn't work correctly. I decided to try and setup the current beta, and tried to follow the same guide but it appears to be too different and without a little help I can't get it to do anything. There is a new directory called lib, should it be a web side directory or not? Does it need to be added to @INC? Really any clues would be helpful... If this is supposed to be released soon, it would be good to get something done so it would be available.

-- MichaelCodanti - 31 Jul 2001

I think if you are having this kind of difficulty, your question would probably get more attention in the Support web. Codev and TWikiDevQuestion are for developing TWiki code, not figuring out install problems.

In the meantime, it would be helpful to know:

  • What OS are you running?
  • What Web server are you running?
  • What version of Perl?
  • Do all Perl CGI scripts run correctly on your webserver now?
  • Which aspects of TWiki are working and which are not?

I myself am using Windows NT 4.0sp6a, Apache 1.3.20, ActiveState Perl 5.6, build 626, and I have the TWiki distribution installed under /apache/htdocs. I have set the /apache/htdocs/twiki/bin directory to be able to execute cgi scripts, and the rest of the twiki/* directory hierarchy is as it comes out of the zip file (so the lib dir is at /apache/htdocs/twiki/lib). Nothing was added to the @INC directory.

-- DavidLeBlanc - 01 Aug 2001

I am running Win2000SP1 with IIS, ActiveState Perl5.6.1 build 628

I got everything but RCS working with the DEC2000 release but can't get anything to work with the July2001 release. I think I got things running better but I am getting this error:

D:\Web\RCSBin\rcs -x,v -q -u D:/Web/BTWiki/Data/Main/WebHome.txt 2>&1 1>NUL
Access is denied.
If I run it from a CMD prompt and take the >NUL off I get this:
rcs: RCS/1,v: No such file or directory
I have traced it down to the store.pm file, but I can't figure out what they are trying to do. You can't redirect STDOUT to two different places, at least not in Windoze. It looks like they are trying to unlock the file, but what is the "2>&1 1" on the end for?

-- MichaelCodanti - 01 Aug 2001

Sorry, am really busy.

I made code changes to get TWiki to work for me on Windows. I suggested that some of these went in but decided to wait until the next beta before I reapply those changes to a public release.

So, I don't whether this is related, but search for 2>&1 in http://twiki.org/pub/Codev/TWikiOnWindows/diffoutput.txt - you will see that I made this "join stderr to stdoutput" directive only used on NT/2000 as Win95 does not allow it. Seems your 2000 box doesn't allow it.

Must go. (PS. Thanks for the reminder Micheal, I am sorry that I cannot give more time to TWiki right now, allocated to other things at work and very long working days.)

-- MartinCleaver - 02 Aug 2001

Actually, the NUL redirection does work on Windows (NT/2k/XP). They just have their own flavor:

foo 1>NUL 2>&1
instead of
foo 2>&1 >NUL

Note that the "1" in the first example is actually optional.

-- JasonPierce - 13 Apr 2005

Edit | Attach | Watch | Print version | History: r8 < r7 < r6 < r5 < r4 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r8 - 2005-04-14 - JasonPierce
  • Learn about TWiki  
  • Download TWiki
This site is powered by the TWiki collaboration platform Powered by Perl Hosted by OICcam.com Ideas, requests, problems regarding TWiki? Send feedback. Ask community in the support forum.
Copyright © 1999-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.