Lets take the readme.txt file and see what we can find out about it.
If there is more than one developer that can change the files, or if you are just monitoring the CVS as a non-developer, then over time there will be differences between the version of a file you have stored locally and the ones on the server. You can review those differences also.
Select Query > Diff selection
Click on OK
But heay, nothing happened, no messages, nothing, that can't be right ?
Well if you followed this HOWTO step by step that is what should have happened, and you did get a messages BTW, it said:
cvs -q update -p readme.txt (in directory D:\cvsroot\Version_4\) *****CVS exited normally with code 0*****These two lines were the confirmation that the command got executed and the the result was empty, if everything goes as expected CVS exits wit code 0 (code 1 means that there has been an error).
And of course you weren't really expecting differences between your copy of the file and the one on the server with the same revision, since it was only a couple of minutes ago that you downloaded a fresh copy and you hadn't changed it yet.
If you had changed the file in those couple of minutes, then both the copy on the server and your local copy would have been opened in CsDifft so you could look at the changes.