----- Original Message ----- From: "Dave Hooper" <[email protected]>
> Tried the most recent webinstaller for a laugh (it never worked particularly > well for me), and when it said "Execute: NodeConfig.exe" I noticed that it > didn't load NodeConfig at all, instead it launched freenet. I haven't seen this happen locally, so I don't have any ideas. The installer shouldn't be messing up like that though - afaik, it's not a common occurance. The only real way to make it better in this respect, imho, would be to generate the installer a new way which allows for easier use of external configuration program (meaning not nsis). > At this point the installer hung. > > So I right clicked that rabbit and shut down freenet, and the installer > continued, up until the point where it said "Execute: fservew --export > myOwn.ref" when I noticed that it launched freenet again. And hung, > naturally. > > So I closed freenet again. > > Ironically it then popped up a message saying "Congratulations, you have > finished the installation of Freenet successfully. Do you want to start > your Freenet node now?". > > This won't help new users any... Not least because the installer hangs, or > that they won't know how to resume the installation. Mainly because they > miss the entire configuration step when NodeConfig is not run. If it's reproducable in a new directory, I'd like information (like the install.log) > d -Mathew _______________________________________________ devl mailing list devl at freenetproject.org http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/devl
