[cvsnt] CVSNT Build 63~66 with ViewCVS and Diff

Paul Russell paul_newsgroups at yahoo.ca
Wed Jan 22 01:03:14 GMT 2003

Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to sales@march-hare.com.

It ALL works (for me)!

I finally have CVSNT Build 66 working with ViewCVS, including rcsgraphs, and diffs. All on Win2k-SP3. Together with TortoiseCVS and PeggyPro IDE/Editor. Thank you to everyone who posted what they had to do to make their systems work - keeping the secrets to your success secret just ain't friendly.

Just for the history, here's some notes on what I had to do:

Note: IUSR and IWAM Internet accounts are NOT included in Everyone group. It might be cleaner to create a new group (Internet) for these accounts.

Note: RCS is used by ViewCVS. RCS57 (newest I've found) generates warnings about new fields in the repository files. These warnings are OK, but some changes are needed in the ViewCVS setup - see below. In ViewCVS_Diff, coloured diff hides the warnings and displays "No Changes", but by trying a different diff style in the listbox, you can see the warnings.

Note: Typing SET at a dos prompt will show the TMP/TEMP/PATH setting for the current user, which might be (probably is) different from that for the System account and IUSR/IWAM internet accounts used by IIS and ViewCVS. On a server you can probably have all (or at least most) environment variables defined under System instead of User, try to minimize the Environment variable differences between users.

1) at a dos prompt, type set. Check the PATH settings. After several installs/deinstalls/updates there were many duplicates. Clean it up. Ensure that correct versions of cvs.exe, diff.exe, rcs*.exe, cvsgraph, and other tools used by ViewCVS occur first in the path. Some packages include obsolete versions of the tools, and they might occur earlier in the PATH - check it. Try a search for each tool name to ensure none are hiding elsewhere.

2) Create a Share for the repository. Set the viewcvs.conf to reference this share directory (\\servername\sharename\wrk\) instead of (x:\cvs_server\cvsrepo\wrk\). It seems that the colon(:) can confuse the python or rcs mapping of the repo when warnings occur. 

Alternately (It works for some, but not me), you can specify the path as (\\servername\c$\cvs_server\cvsrepo\wrk). Ensure the priviledges are correct for IUSR/IWAM.

Copy and paste the path into Internet Explorer to ensure you have it correct. You may need to set the option for: Tools->Internet Options->Connections->LAN Settings-> [Check] Bypass Proxy Server for Local Addresses

3) Give IUSR and IWAM 

    -read/browse access to the share for the repository, 

    -execute access to the viewcvs_cgi directory, 

    -execute access to the util directory holding (rcs, diff.exe, cvsgraph.exe, enscript)

    -full access (r/w) to c:\winnt\temp

You can change the TMP and TEMP variables to point to c:\temp, but ensure you do it for the correct user accounts (IUSR/IWAM), or set the System environment setting. If you change the System environment setting, you'll probably have to reboot to restart the system programs using the new settings.

Note: I created a separate virtual folder for the ViewCVS scripts instead of copying them to the existing cgi script folder. This allows cgi to be set as python in this folder, and not conflict with other cgi languages installed. This is only necessary if you already have something like Perl installed and mapped as CGI, or wish to avoid possible future problems. 


I think that's it. Good Luck!

Paul Russell, Tottori Japan


Post your free ad now! Yahoo! Canada Personals

More information about the cvsnt mailing list
Download the latest CVSNT, TortosieCVS, WinCVS etc. for Windows 8 etc.
@CVSNT on Twitter   CVSNT on Facebook