After upgrading to 4.9.10, I don't notice the Disk Problem problem any more. But it's not mentioned in the 4.9.10 changelog, and it was only introduced in 4.9.9, so it looks like someone forgot to mention this in the changelog?

Anyway, everyone complaining in this thread about the problem, upgrading to 4.9.10 seems to fix it without breaking anything else, even though the 4.9.10 change list just mentions splash screens and translations.

Normally LW 4.8 should resume 4.9 downloads. Also the disk error prob fix is in the 4.9.9 changelog...
- Reverted change to VerifyingFile.

As for dling .exe, you can, really, if you have a good antivirus or trust the file. I do on my xp box. But yeah I mostly use a Mac, so viruses don't bother me

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

Here's a bug -- if you select something other than All Types (i.e. videos, music, images, documents, or programs) with the Library tab hidden, then use the view menu to show the library tab, the selection in the search tab moves back to All Types all by itself. It should only move in response to user input.

Also, Limewire 4.9.10 still sometimes randomly drops a connection (goes from all green bars to one or more red bars) while the network connection is stable and it's not starting up or shutting down. Limewire should only drop connections in response to user input.

I confirm the library resetting the file type bug.

Spud Tosser: can you make a stack trace (thread stickied in the beta forum) of LW when it drops connections and post it here?

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

That could also be due to the other side going offline.

Just wondering, when I am running in leaf mode sometimes Limewire will drop all but 1 connection if I touch the mouse. What apears to be happening is if I am leaving LW idel and it is just UL to others for a while with the connection page open and I come back when I come back I can look at the connections it will show 5 and turbo charged but as soon as I touch the mouse it wil drop 4 and then imedatley re connect to 4 new host. I have not noticed any decline in LW preformance, is this somthing that has been writen into LW so that there ar more ultrappers available for others to use when others have a demand for them and I do not. I have just noticed this in the last few versions currentley running 4.9.10. By the way I was able to make LW freeze 1 time I started 22 DL one right after the other and LW froze but only for about 20 sec. Tried several more times to get it to freeze but could not and not thinking I did'nt have Debug running so no stacktrace.


Latter Grandpa

Another question while running Pro 4.9.10 Leaf mode 5 connections, I had a file than needed more sources but could not find any. I left 4.9.10 running and started 4.9.10 Pro DeBug connected in leaf mode 5 connections so now have 2 versions of LW running the DeBug immedatley found a source for the file and started DL it. I manualy searched for the file on the other verson several times and still need more sources. I am asumeing this is due to the Ultrappers I am connected to but don't all people have acess to the same files.

Latter Grandpa

your two instances had different network horizons, because they were connected to different sets of ultrapeers. Think of the earth's northern hemisphere and the hemisphere east from the greenwich meridian to the date line -- there's a large chunk of overlap, plus some areas in only one hemisphere or the other, plus a chunk in neither. North America and much of the Pacific is in both; Asia is in only one; South America is in the other; Australia isn't in either. Europe and Antarctica are divided east-west, the Atlantic is divided north-south, etc...

Recent betas have a troubling regression: once again, "resume" is useless as Limewire refuses to connect to known sources for a file. In 4.8.1, for most files hitting "resume" produced an honest attempt to connect to the file's sources; in early 4.9 betas it did nothing. In later 4.9 betas (around 4.9.10) it worked again, and in 4.9.14 it's broken again.

On top of that, it is becoming increasingly obvious that it is becoming increasingly urgent that ways be found of identifying and dynamically working around "bad actors" on the network. The ipod spammer, for example, but the ipod spammer is only the tip of the iceberg. There are a lot of just plain broken clients out there -- "indian giver" clients that result in things like "downloading 1% ... 2% ... 3% ... 4% ... 5% ... Waiting for busy hosts" and then it just sits there forever saying it's busy and won't resume, and similar clients that offer juicy search results but then refuse to actually upload them to anybody (you know the type -- usually they come in bunches, and every one of them immediately "needs more sources" so, of course, you hit "find sources" and now mysteriously the files are suddenly impossible to find judging by Limewire's complete failure to find any more sources...even though they were easy enough to find when you initially did a search...) ... and then there's the broken Shareaza versions that will give six different uploads queue position 1, and then refuse to serve any of them; the downloaders just see, alternately, "Shareaza -- waiting in line, position 1" and "waiting for busy hosts" and, of course, never "downloading".

All of these misbehaving clients need to be routed around, ostracised from the network; if the people running these rudely-behaving and broken clients can't find or download anything they will switch to clients that work properly, or upgrade to versions that have fixed the bugs, or whatever. Currently users don't have any incentive to upgrade to fix bugs with *uploading*, and such bugs have proliferated in several popular network clients until just seeing their names in the Vendor/Version comment makes me sigh and give up on any likelihood of ever downloading the file. So let's give them one, and also weed out the spammers and spoofers while we're at it.

By the way, Limewire is still prone to be schizophrenic about whether a given host is online or not. Often a batch of co-hosted files will end up in a mixture of states that includes several or even all of "waiting in line", "waiting for busy hosts", "downloading", "connecting", and "awaiting sources". The last one doesn't belong -- if a source for the file is online the file should be at worst "waiting for busy hosts". "Awaiting sources" means -- or is *supposed* to mean, anyway -- that there are no known sources for the file currently connected to the network. The list of known sources is a bunch of iport pairs all of which have nothing listening at the other end at the time, in other words. If any of them respond, even with a busy signal or some other such "buzz off" message, it should show "busy hosts" and periodically retry until the host is not busy (or does go offline).

(And with "resume" no longer working, hosts in yo-yo mode are also a massive pain to download from. The downloads all end up "awaiting sources" and in 4.8.1 you'd just hit "resume" and half of them would start downloading. Now if the source has a flaky network connection or keeps rebooting or restarting their client, they all end up "awaiting sources" and you have to ... keep restarting your client! And that, of course, makes a bunch of people uploading off you with a Limewire beta restart theirs, and so on, and so on, in a chain reaction. I thought we were supposed to be encouraged to keep our clients running 24/7, not shut them down when not in use or frequently restart them, but the gone-again, back-again "resume not working" problem encourages the latter and the continuing bloat problem -- not even just ram use, but it's a CPU hog too, and that's damned strange for an event-driven application -- encourages the former.)

OK, who'se the wise guy that mutilated my previous post? I thought these forums were supposed to show "edited by" if someone alters something, but it doesn't -- yet it definitely was edited, since someone mangled a phrase and inserted an icon in there and it wasn't me. At least, I didn't insert an icon into the text, or an image tag; I'd have remembered doing that.

I suppose the lack of an "edited by..." note means it was the system administrator, or some dumbarse bot with equivalent privileges...