Rainer Meier schrieb: (...) > No. I don't think this is the way to go. We are building up a > state-of-the-art software deployment environment and then we should > install one of the core components using a "hacky" cmd script? NO! > > Probably switching to NSIS could be an alternative too. Just make sure > the /S switch works properly ;-) > However currently it's clearly a resource problem. WPKG 1.0 is quite > stable, WPKG 1.1 is collecting new features and WPKG client suffers from > some upgrade problems and probably also the delayed logon feature needs > further investigation. So if somebody could provide some assistance here... Fair complaint. This is what's planned for WPKG Client 1.4: http://wpkg.org/TODO_list#WPKG_Client I made some categories there. Everything what's under important/*useful will be addressed. "Do we need this" will not necessarily be addressed. I need comments, comments, comments... -- Tomasz Chmielewski |