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.
Tony, > 3M is nothing for an installer these days, really... I don't mind 3M installers, but if you can have 2M and you get 3M instead something is not quite right. > If you don't allow MSI on your machine how do you use python? I don't use Python at work, but last time I was installing it they seemed to use Wise installer? Anyway, I am currently testing new CVSNT at home only, where I do allow all sort of things since I can afford the time to rebuild the system if neccessary. So far the testing is going pretty badly :( > It's easy enough to create one... the source for the installers is > there, or you can just edit the MSI directly with orca. I don't intend to build CVSNT on my own at this point in time, but if I do get around to it I won't be using MSI for sure. It may actually come to that since I am not quite happy with the direction that CVSNT development seems to be taking. I don't mean an installer only but also the exclusive edits command operations and return to dynamic linking which increases the size. > Just send the crashdump (or let it send it automatically). Any command, even just calling "cvs.exe" produces the message box telling me this: "The procedure entry point MiniDumpWriteDump could not be located in the dynamic link library dbghelp.dll. " 2.0.58d works perfectly. CVSNT 2.0.59 craches with the same message too, but at least I am able to select my own installation folder by using the Browse button. Best Regards, Jerzy ----- Original Message ----- From: "Tony Hoyle" <tmh at nodomain.org> Newsgroups: support.cvsnt To: <cvsnt at cvsnt.org cvsnt downloads at march-hare.com @CVSNT on Twitter CVSNT on Facebook> Sent: Friday, November 12, 2004 23:01 Subject: Re: [cvsnt] Latest updates > Jerzy Kaczorowski wrote: > > I don't see how nearly 1MB difference (increase by 50% from 2M to 3M) is a > > minor difference. Additionally I don't like installers to screw up my dlls, > > and in case of MSI (which is not only buggy but also both stupid and ugly) > > it means that the latest CVSNT is not allowed on my work PC. > > 3M is nothing for an installer these days, really... > > MSI doesn't screw up anything - it's built into the OS and has very > specific rules about what can be installed where. It has some major > limitations (sucks pretty hard in some places actually) but does in fact > work. > > If you don't allow MSI on your machine how do you use python? > > > While we are at it - I would really like to also have a client-only > > installer which contains cvs.exe that doesn't have the server-specific code > > in it. It should be much smaller that way and I think it would not have MFC > > dependency since most of MFC is involved in server support code I guess. > > It's easy enough to create one... the source for the installers is > there, or you can just edit the MSI directly with orca. > > > On another note - latest cvs.exe is crashing on me like hell, can't get it > > to even display version or anything. No problem with 51d or any other > > previous version. > > Just send the crashdump (or let it send it automatically). Almost > nothing has changed, really, except some backend stuff for file > access... seems pretty stable at the moment. > > 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