Hi, all My intention is to add a user mode system tray client too in the future, yes. The system is now that the wpkg-gp.dll running as a GPE will contact a service and ask it to execute wpkg.js. This scales to adding a client running in the system tray that could do the same, and even running a centralized service that contacts all clients and ask them to execute wpkg, giving control over the upgrade process. I am also investigating how to do "update on shutdown" as well. I am not sure on how to communicate that to the user, as I have not (yet) found the interface Windows uses for generating messages on shutdown (Like "please wait, installing update 1 of 10") but I know that a service can delay shutdown indefinitely, even on Windows >= Vista, but userspace programs cannot. But this is all in the future, what I have for now is the reimplementation of old features (I hope) :) I'll come back pretty soon with more. -CL 2010/12/10 Brent A Nelson <brent at phys.ufl.edu> > Either of these approaches could be interesting, but it would be nice to > give the users a measure of control. The second approach sounds like it > will do that, although still not quite as convenient or familiar as the > Windows Update behavior. It seems as if wpkg-gp is making good progress in > this direction... > > > On Fri, 10 Dec 2010, Troy Hamilton wrote: > > Brent, >> >> On Fri, Dec 10, 2010 at 1:20 PM, Brent A Nelson <brent at phys.ufl.edu> >> wrote: >> >>> As things stand now, we've been reluctant to upgrade large packages (say, >>> Office 2007->2010), as this would be applied when they turn on their >>> computers, and they might have to wait an hour before they can use their >>> machines. But if the user got a notice that the update was ready, they >>> could choose to apply it or be aware that it will install on the next >>> reboot. >>> >> >> Have you considered running wpkg.js outside of business hours (either >> with a scheduled task or cron job) to install such large packages? >> You may also have other reasons for not doing that, but I thought I'd >> ask. >> >> >> Once you have those features, will you be adding support where a >>> non-privileged user could potentially launch a wpkg upgrade while logged >>> in? >>> Perhaps much like Windows/Microsoft updates, where it could check to see >>> if >>> there are any changes every so often, and then let the user know what >>> changes would be applied and give them the option to proceed? That would >>> be >>> very cool. >>> >> >> At some point in the past, I had an unofficial (custom) wpkg service >> installed, and I used setacl.exe to change the permissions on the >> service so that non-admin users could start it. I'm not sure if this >> would work with Windows 7 or not, but it might solve half of your >> problem. I'm pretty sure that services can't interact with the >> desktop in Vista and Win7, so that still leaves the task of notifying >> the user of the update(s). >> >> This might not be exactly what you're looking for, but I thought I >> throw it out there anyway. >> >> >> Cheers, >> >> Troy >> ------------------------------------------------------------------------- >> wpkg-users mailing list archives >> >> http://lists.wpkg.org/pipermail/wpkg-users/ >> _______________________________________________ >> wpkg-users mailing list >> wpkg-users at lists.wpkg.org >> http://lists.wpkg.org/mailman/listinfo/wpkg-users >> > > ------------------------------------------------------------------------- > wpkg-users mailing list archives >> > http://lists.wpkg.org/pipermail/wpkg-users/ > _______________________________________________ > wpkg-users mailing list > wpkg-users at lists.wpkg.org > http://lists.wpkg.org/mailman/listinfo/wpkg-users > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.wpkg.org/pipermail/wpkg-users/attachments/20101211/18258b64/attachment.html> |