Zero3 skrev: > Your main problem (nothing happening for 20 secs, then an error) is > actually located in the launcher (new browse.cmd) executed after the > install (As checked off, in the installer. The desktop shortcut points > to the same thing). Before launching fproxy in your browser, it checks > the status of the service. If it's not running, it will be started. > However, if this process takes more than 20 seconds, the launcher will > assume that the node is stuck and report back with the error you got. > I'll think add some kind of progress bar (similar to the one in the > uninstaller) so the user knows that something is going on in the background. > >
I managed to get a hold of a Vista machine and made a test install. It appears that the service installed by the wrapper is un-startable, even from the Windows service manager, which is odd. I'll have to figure out why it returns "-2" without anything in wrapper.log, and what the heck that means... So Vista users will have to wait until I figure out what that is all about. - Zero3 _______________________________________________ Devl mailing list [email protected] http://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
