Matthew Toseland skrev: > One theory for this is that icacls.exe is 64-bit on win64 and therefore isn't > a valid win32 app when called from 32-bit wrapper or AHK code. However, why > do we need to call icacls.exe at all in the new installer, given that we > don't create a user? And even if it fails, so what, why should that break > anything else?
Yes, that is most likely the reason. IIRC NetworkService (the user account we now use) doesn't by default have read-write access to our files. Can someone verify on XP/Vista/Win7? If icacls fails, the installer will continue anyway. However, since the node didn't work, chances are that we did indeed need to apply the permissions. > Another theory is that there is difficulty in detecting the JVM on win64. One > solution is to let it pick it up from the registry, see my other mail - it > will only pick up the 32-bit version, but that is okay, the 64-bit version > isn't autoupdated and may not be terribly reliable... However, in the below > log, it was attempted to hard-code the path to the 64-bit java exe (which > works for other people). I'm not so sure: [22:46:01] <qwebirc20693> It only has one line: STATUS | wrapper | 2010/01/03 15:03:54 | Freenet background service installed. This means that the service installation succeeded (or at least the wrapper thinks so), but it was never attempted started. This means that the Windows start.exe fails, which the mentioned "didn't respond to signal" errors confirm. This means that Service_Start() in src_freenethelpers/FreenetStart.ahk fails to start the service before the 120 second timeout kicks in and throws that error. It would be interesting to know if the service actually has been created, as the wrapper claims. If it has, I need to look into why Service_Start() fails. Of course this could be caused by the lack of proper permissions because icacls failed... We should figure that out first. > Thoughts? This is a blocker: Freenet must install reliably on 80% of win64 > systems before releasing 0.8.0! We need a 64-bit tester then... It's kind of hard to develop something for a system you neither own nor has access to in one way or another. > Also, Freenet must install reliably on Windows 7 before releasing 0.8.0. > Right now the installer doesn't support it. It's true that it's not officially supported, but I've seen both successful and failed Win7 installs. Again, I need a tester before I can start tracking down bugs. - Zero3
