Marco Gaiarin schrieb: (...)
>> If it's enabled, everything will be launched in foreground - so that any >> logged on user could see it. > > Ok, but... if i restart service as a logged user i confirm that i see > the cscript command prompt windows and i can see also some 'flying > files' windows (also with /q:q some little copy windows appear...) > popping up for some fraction of second, but if i run on boot, nothing > appear. Because it did already run before you managed to log in? Try to start a command that never ends (like "notepad"), and you'll see the difference. > what you are saying is that if i put '5 minutes' on run time for the > 'lock logon' window, and 5 minutes passed without a complete > installation, a logged user can (eventually) interact with WPKG? If I understood you correctly, yes. > I think is an acceptable risk... or at least seems it is the only way > to install some package... ;((( > > > Can the foreground/background execution status moved on a per-package > basis? No. Right now, basically, WPKG*.exe and wpkg.js are independent. -- Tomasz Chmielewski http://wpkg.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ wpkg-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wpkg-users
