2012-12-19 17:26 AEST by Arthur Barrett - CVSNT 'unicode' (utf8) can cause batch files to fail.

This is most evident with CVSNT 2.5.05 which switched to Unicode 'default'.

CVSNT 2.5.05 sets the output code page to 65001 (UTF-8) and does not set it back.
Unfortunately, Windows' handling of that code page is broken so bad things happen (including the 
inability to run batch files).

One workaround is to reset the code page (both input and output) to a known working one (437, 850, 
1252 or others) using CHCP, preferably on the same line as the CVS command. For example:

> cvs update & chcp 1252

More workarounds in the linked article.

2012-12-19 17:29 AEST by Arthur Barrett - It's odd that the codepage calls in CVSNT are changing the CODEPAGE of the calling shell.  Perhaps it's 
actually changing the codepage of the entire session?

It raises several issues:
* are we using the correct codepage calls in windows (to affect only our process)
* should info trigger reset the codepage back to the starting codepage?
* should we reset the codepage before exiting main()?