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.
> CVSNT Release 2.5.03.2382 (03-07-2006) writes > zero-byte files to the user's Temp directory on > a Windows XP Home machine when TortoiseCVS > In D:\COBOLWB\SRC\NT\BV: > "cvs.exe" "-q" "update" "-p" "-r" "1.64" > "BVZUG2.CBL" > CVSROOT=:local:D:\CVSNT\Rep It is not typical (or recommended) to checkout a particular physical version number, you would usually use a tag. It is also not typical (or recommended) to use :local:. Also I do not understand from your description if there is anything wrong with the action behaviour other than what is left in TEMP? Is the file updated OK? Does this only occur when you update first to 1.63 then to 1.64 or does it happen in other situation, eg: a "plain" checkout? Does this only occur with :local:, or does it occur in client/server mode as well (:sspi: or :pserver:)? If so is the temp file left on the server or on the client? Can you submit a trace of the command that actually gives the "error", eg: CVSROOT=:local:D:\CVSNT\Rep In D:\COBOLWB\SRC\NT\BV: cvs -ttt update -r 1.64 BVZUG2.CBL 2> trace.log Regards, Arthur Barrett