----- Original Message ----- From: "Mathew Ryden" <[EMAIL PROTECTED]>
> I'm sure everyone's getting sick of me telling them this, but there is a new > windows installer up. > I changed the noderef file to the one on sourceforge, as well as tried to > update the updater. I still can't get it to work here, but I have no way of > telling what is causing that - be it my internet connection or a but in the > updater (i'm leaning towards the latter) > > Could someone else test the updater to see if it works properly? I've fixed it on my computer - does the updater still work for everyone? > New in this release is a bug which causes the node's default port to be set > to 8812. I'm pretty sure where it is occuring but most likely won't be able > to fix it until ~3 hours from now. Are other people even getting this? > Anyone who finds a new bug in the windows installer or brings my attention > back to a real bug will get $5 or my thanks, whichever I happen to have more > of (probably the thanks :) > > -Mathew Is there anything else I should have on my todo list for the windows installer? - make it so that nodeconf can change every option - have nodeconf just edit the config in place (effectively, have it treat %'s and not have to be manually rewritten) - build in search for fproxy.* and nodeinfo.* so that we can save those options if any [won't build in msvc6] - fix import/export ref on bunny - popup window when # of threads is changed to equal 0 - make windows installer using windows installer. - have pathfind buttons on nodeconfig/normal work - fix weird 8812 bug only I seem to manifest - get rid of fproxy and maininfo checkboxes - change text for mainport.class on fproxy screen (split mainport into it's own page with perhaps nodeinfo on the same page) -Mathew _______________________________________________ chat mailing list [EMAIL PROTECTED] http://hawk.freenetproject.org/cgi-bin/mailman/listinfo/chat
