On Friday 08 May 2009 19:06:18 Zero3 wrote: > Matthew Toseland skrev: > > On Friday 08 May 2009 12:40:32 Zero3 wrote: > >> Matthew Toseland skrev: > >>> On Tuesday 20 January 2009 03:18:07 Juiceman wrote: > >>>>> On Fri, Jan 16, 2009 at 5:46 AM, Zero3 wrote: > >>>>>> Juiceman skrev: > >>>>>>> Here is a patch for a new version of the Windows update script. > >>>>>>> Please commit since that svn directory is restricted. I've tested it > >>>>>>> extensively on my XP machine. > >>>>>>> This should handle the new installer start/stop.exe while still being > >>>>>>> compatible with current installs. It will need to be made to handle > >>>>>>> the new node service ID the new installer creates. > >>>>>>> It also still needs some Vista functionality. > >>>> Here is a further revision of the update script. Mostly error > >>>> handling, beautification. Please commit. > >>> I have applied this for the new wininstaller. Is it 100% Vista compatible? > > In > >>> particular, will it RunAs itself in order to self-escalate on Vista? > >> Note that the update.cmd script doesn't need to (and wouldn't even be > >> able to) escalate itself. It should have write access to the files > >> already (inherited from the user running the script), and the start/stop > >> scripts handle escalation themselves. > > > > So it should just work? Unless the user runs it from a user other than the one > > they installed as? I thought we created a user for Freenet, are the files > > writable by both the installing user and the freenet user? > > I haven't had a chance to test it myself then. Juiceman knows best what > works and what doesn't (yet). (We discussed what things that needed to > change to support both types of installations a while ago.) > > You need admin privs to install Freenet. As any admin by default will > have readwrite access to program files, any admin (including the > installing one) should be able to use the update.cmd script. Normal > users will not have access to do that (which they shouldn't...) The > custom freenet user also has full access to the files to allow Freenet > to update itself (but the update.cmd script is run as the executing user!). > > Btw., did you remember to add the update.cmd to > src_freenetinstaller/FreenetInstaller_Include_Files.inc? It isn't > included in the .exe you linked to.
I have now. :| New prototype wininstaller released.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
