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.
Thanks for the reply. /3GB actually partially solved the problem. The cvsnt server can handle the 300MB file now, but failed on a 600MB file. So this at least proves that you are correct in assuming the 32bit memory limit is the problem. On the other hand, the linux cvs server, which should be 32bit too, appears to do fine with these big files. Can I assume that this memory problem is a limitation of the windows OS? Daben Tony Hoyle wrote: > Daben Liu wrote: > >> 6. The physical memory on the cvsnt server is 2GB with a 4GB virtual >> memory. >> So memory availability should not be the issue. > > > The 32bit memory limit will bite you long before you get to 2GB, let > alone 4GB. Memory fragmentation will mean that even getting 1GB usage > is going to be hit and miss. > > Try booting the windows machine with the /3GB switch.. it changes the > memory layout and might give you more space (or it might not if lots > of yout 2GB is already used up by system stuff/other processes). > > If you're routinely dealing with files this big a 64bit linux server > would be worth investing in (64bit cvsnt for windows isn't working yet). > > Tony > _______________________________________________ > cvsnt mailing list > cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook > http://www.cvsnt.org/cgi-bin/mailman/listinfo/cvsnt https://www.march-hare.com/cvspro/en.asp#downcvs