Okay, with further investigation ... The user in question appears to have installed a clean copy of XP and is reusing the already-installed Firefox. Therefore App Paths in the registry is empty, and doesn't include firefox.exe. Therefore, we are not detecting Firefox.
However, this doesn't explain why we open a command line called welcome.html instead of IE/Firefox (there was a copy of FF running...) pointing to the welcome.html ... Further testing shows start http://127.0.0.1:8888 launches a new firefox window pointing to the freenet homepage. We should check popular locations for Firefox to deal with this eventuality. Obviously this won't work on some languages, but if it works on some it will significantly increase our chances of success (in an admittedly pathological but probably somewhat common scenario). It is a pain that our fallbacks don't work, and I have no idea how to fix it, it looks like a windows bug, unless anyone has an alternative explanation. :( On Monday 05 May 2008 23:49, Matthew Toseland wrote: > Did another usability test. Problems: > - The installer is signed by nextgens. We should change this. But this wasn't > reported by the user, it's just my view. > - Freenet not only didn't find Firefox (2.0.0.14, english, custom theme), it > didn't find any web browser of any kind: it opened a command line with the > title "welcome.html" !! I told the user to go back to the download page, and > he followed the instruction to open http://127.0.0.1:8888/wizard/ , and from > then it was somewhat smooth... > http://amphibian.dyndns.org/screenshot-freenet-command-line.bmp > http://amphibian.dyndns.org/screenshot-freenet-bratnet.bmp > - Freenet is slooooooooow, especially in this case where it had an untweaked > browser. After a long delay, two sites loaded, after a longer delay, several > sites loaded at once; this strongly suggests imho that the problem is caused > by not finding the browser. User reports significant improvement in speed > after a few minutes. > - Connection limit is definitely a problem: many images which should be in the > same container not loading; same for the Potentially Dangerous Content > warning. > - Freenet Activelink Index causing problems... in an untweaked browser, this > site is an utter disaster. Even in a tweaked browser it will DoS the rest for > a while. Maybe we shouldn't bundle it? > > Solutions? > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20080506/d0d6dc2a/attachment.pgp>
