If you want something "not dependent on network access or a central server," then centralized SCMs from your list should be sent (Subversion, CVS, p4).
If you need a cross platform, I think Visual Source Safe will have to go.
Also, you mentioned Open Source, which produces p4 and Visual Source Safe.
CVS is pretty old, and if you plan to use it, it is best to ignore it and use SVN instead.
Git is something you can add to the list, but it does not support windows as well as bzr and mercurial.
I use git myself, but I develop exclusively on Gnu / Linux and therefore cannot comment on Windows support. Itβs also a little freaky, but once you get used to it, it can be very powerful. There is a problem with the training curve, so you may have to spend some time training your team on the instrument.
Bzr, I do not know. The last time I touched it, it had problems with the repository format and it was terribly slow. Now it is much better, but I was amazed at my first exposure.
Hg is sweet and works fine on windows and Gnu / Linux, but since I used git quite heavily, I skip some of them on hg.
source share