the cnet build was replaced though.. with the new build.

Basically... xolox has learned a new lesson with this latest update. First a corrupt file being served on cnet which was a disaster, then a bug thought to have been cleared in bad/unresponsive gwebcache's xolox used showed up.

build 384 is very close to what will be released in a few days? or so on cnet.

check what build you're using ( help > about) + just remove the bad gwebcache's.....
follow these directions.

www.xolox.nl/client/support/howtogwebcache.html


good luck