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.
Although unlikely (it was a long time ago that I spent a lot of precious time dealing with MS's bugs that introduce such ridiculous holes to expensive OS software) and am pretty sure I've taken measures against the sasser worm at least). However, I must admit I didn't think of it in the first place. Gonna run an antivirus check tomorrow at the office and come back with results. At home, the same combination of OS and TortoiseCVS does not cause any such problem, however a CVSNT server is installed and running there and consequently cvsnt' lock server instead of the one TortoiseCVS installs. Thanx "Tony Hoyle" <tmh at nodomain.org> wrote in message news:cpa2q8$jso$1 at paris.nodomain.org... > mada wrote: > > I installed TortoiseCVS on a winxp pro machine that _does_not_ have cvsnt > > installed and starting getting messages about lsass.exe crashing just after > > winxp completes booting and waits for you to login. > > > > However, the only info I found on the net with respect to this problem is > > related to cvsnt, there is also something writen about it at the cvsnt wiki. > > > > So, does TortoiseCVS install anything that has to do with cvsnt? > > > > If not, please forgive me for the off-topic, would you maybe know where to > > look for info on this problem? > > > This related to old server installs of CVSNT and was never associated > with client installs such as TortoiseCVS. It would also never affect an > idle server (since cvsnt wouldn't be invoked at that time). > > It sounds more likely you have the sasser virus which is known to cause > this. > > Tony