> OK, I did some work on the Windows installer to improve the silly Java
> detection.
>
> Although the freenet code is still 0..9.1, here is what I would like to
> put out as 0.3.9.2:
> http://sspaeth.de/Freenet/Freenet_setup0.3.9.2pre.exe
> Could the Win guys (David, I love you as tough tester and your Ghost
> partitions), give that thing a shot and feedback?
OK Guys - here's the report.
Since you're doing such a good job fixing up the problem areas, I've added a
constant to my test procedure:
'#define ANUS_DIAMETER ANUS_DIAMETER_HAMSTER'
;=)
----------------------------------------
TEST REPORT
FREENET 0.3.9.2pre INSTALLER
----------------------------------------
Windows 98 - virgin ghost partition
no java installed
----------------------------------------
Summary:
----------------------------------------
FAIL
Required remedial actions are detailed at
the end of this report.
------------------------------------------
DETAILED TEST DATA
------------------------------------------
1. Installation:
-------------
* before offering to show download page,
installer does not first check if user is
currently connected to internet.
BAD
* installer has a loop which repeatedly
checkins for java reg key, then offers
download page
GOOD
* seems to be only checking for Sun Javas
GOOD
2. Running Freenet.exe
(while not connected to Internet)
---------------------------------
* Freenet.exe does not check if user is
currently connected to internet
BAD
* Double-click on icon - Freenet.exe launches
the URL http://127.0.0.1:/
VERY BAD
* Java configurator launches successfully
GOOD
* FProxy port shows on configurator as 8080
BAD
* Changing FProxy port in configurator, then
double-clicking again, launches
'http://127.0.0.1:8081'. Gateway page
comes up.
GOOD
* After connecting to internet, I click on
Snarfoo link - apparently node has given
up - node doesn't connect to Freenet
BAD
* Stop and restart freenet (via tray popup)
is successful
GOOD
* Click on Snarfoo link, after initial
failure (from launching freenet without
active connection, then restarting freenet)
- successful
GOOD
* I closed down internet connection, then
tried another link - got a 404, and no other
sign of what was wrong
BAD
* I Re-connected to internet, then tried
surfing again - successful
GOOD
END OF TEST
----------------------------------------
REMEDIAL ACTION NEEDED
----------------------------------------
Installer:
----------
* If java interpreter reg key is not found,
then installer needs to first enter a
loop of prompting user to start up an
internet connection.
* This first loop should:
* Gain user's permission to test
internet connection, and assure
him/her that you are not 'phoning
home', sending any info, or
violating privacy in any other way
* Verify that there is an active
internet connection - a ping or
brief web hit to freenetproject.org
should suffice
* This loop should provide a 'cancel'
button to allow user to bail out
* Loop MUST complete successfully before
entering the body of the java
selection/detection loop
* Best to not use other ways of detecting the
presence of an active connection - such
measures work ok on 95/98/ME, but not
so well on win2k
Configuration
-------------
* Fix the bug of 'http://127.0.0.1:/'
(see below)
* Fix the bug of the Java config dialog
showing 8080 as FProxy port (below)
Freenet.exe
-----------
* First, check that an active internet
connection exists. If it doesn't exist,
then flash the tray icon, with the ALT
text "Please open an internet
connection". Freenet.exe should enter a
state - WAITING_FOR_INTERNET_CONNECTION
* check every 2 seconds for a connection
* When a connection comes up, then and
only then, launch the node.
* Once node is launched successfully, I'd advise
that you invisibly send a request to fproxy
(directly with sockets), to
ensure that you can load the gateway
page.
* If you can't get the gateway page in
this way, then flash the tray icon, with
the ALT text "cannot load gateway page".
* Every 30 seconds, check if user is still
connected to net. If not, then go into
the WAITING_FOR_INTERNET_CONNECTION state
* When all these problem areas have been rectified,
I strongly recommend reinstating the 'default TRUE' status
for the 'Launch Freenet Node Now' and 'Launch Freenet on
Startup' installer config options. With these problems fixed,
Freenet will be safe for inclusion in the startup folder, and safe
for immediate launch after installation.
Cheers
David
_______________________________________________
Devl mailing list
Devl at freenetproject.org
http://lists.freenetproject.org/mailman/listinfo/devl
