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.
Wendy, > After I upgraded the CVSNT 2.5.05, the problem of the > fileattr.xml is still there. Did you upgrade the server and the client or just the server? Check that there is no old cvs.exe in the WinCVS directory. You may have to 'delete' the 'broken' fileattr.xml from the server. > > Upgrade the client and the server and the problem will go away, or > > upgrade the server to 2.5.05 and set the options as described in bug > > 5555. > > And also I cannot get the 'assumed > character set' for each type of client (CVSNT, non-CVSNT, etc). in > the 'compatibility options' tab. My mistake - 2.5.05 does NOT have bug fix 5555 - that fix is only in CVS Suite 2008. The bug does say that, but my comments in the e-mail misled you. If you upgrade the client then it should work OK - the problem is that the 'old' client does not send the codepage to the server - so the server make some assumptions which can easily be wrong in a multi-character set environment. You should: 1) run 2.5.x server in 'unicode' mode and 2.5.x clients Or 2) run 2.0.x server and clients in the identical character set *may* work Or 3) run 2.5.x server and 2.0.x clients with the server and client configured for the same character set *may* work Either way you will almost certainly need to 'delete' the old fileattr.xml from the server. This *may* cause some things like renamed files and watch/edit to misbehave in the short term. Let the group know if you need more clarification. Regards, Arthur Barrett