|
I'm sure I'm not the only person in the middle of a long, partially
completed, download or two, and worried about the launch of
1.5.0 preventing me from completing. I understand that the extra md5
function in 1.5.0 is an important addition, but that it will "kill" all
existing shares and make it impossible to resume any existing
partials.
I, for one, need about another 72 hours to finish a couple of biggies
that I'm over halfway through, and at 'phone modem speeds I'd hate to have
to start again, assuming the sets get reshared under the new band-name
lockdown restriction, which will be another new feature of v1.5.0.
I presume that users of v1.4.0 and below who do not upgrade
immediately will still be able to connect to each other through the
Furthur network after the launch of v1.5.0, and I therefore suggest that
if you are unable to complete your downloads in time, if you wait to
upgrade for a day or two and carry on using your existing version, and
(hopefully) the people sharing these same sets also hold off upgrading for
a day or two, we can all finish what's in hand before taking the Great
Leap Forward.
Indeed, it has occurred to me that by keeping the old version in
reserve as well as downloading the new one, we could have the best of
both worlds here - those people who want to continue sharing sets blocked
by the new restrictions on approved band-names could merely continue
sharing and downloading using v1.4.0 or below.
Whenever I upgrade, I always first copy the old contents of the
Furthur folder (apart from the Downloads & Temp folders) into a
reserve directory which I name with the old version, and I can then use
the old one if I have problems with the new one. If we do this before
upgrading to v1.5.0, I guess we can carry on using both versions.
I'm certainly gonna give it a try!
Al
PS I love the new download windows with all the extra info, but I do
miss the "time remaining" feature from the old window, even though it's
only an approximation based on the current (variable) d/l speed. It'd be
nice if we could have that feature restored. |