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?
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). Thoughts? This is a blocker: Freenet must install reliably on 80% of win64 systems before releasing 0.8.0! Also, Freenet must install reliably on Windows 7 before releasing 0.8.0. Right now the installer doesn't support it. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20100104/0be35b5b/attachment.pgp>
