Simon Smith wrote:
I'm now on the fresh 2.1 release, and the problem is as bad as ever. In particular, using a recent URL from the pull-down list, then selecting another recent URL /in the same window/ before the first page has loaded also seems to trigger it. So it's very easy by various means to accidentally get NetSurf in a state where the next aborted download will drop the socket count to zero. A nuisance.
This doesn't affect all NetSurf users, and it doesn't affect all Iyonix users, therefore there must be something you are running which is affecting the network stack.
Get a clean RISC OS 5 boot sequence and a clean NetSurf install, don't run anything else, and see if it still occurs.
Cheers ---David -- Email: dr...@druck.org.uk Phone: +44-(0)7974 108301
