>Q.1 How can we personally utilize the file downloads.bak to help us?

LimeWire will automatically utilize it. There's no need to do anything yourself. (And, in fact if you try to do things yourself it likely will confuse LimeWire.)

>Q.2 It sounds from your description that my assumption about links was correct. Otherwise how else can a file become a PFS. A simple deviation from what is hoped for is not a major issue to admit to so long as you are still looking into solutions for it.

Hmm. After thinking about it a bit, I haven't stated the truth in its entirety. A red incomplete file means the file isn't eligable for PFS, but it doesn't necessarily mean LimeWire doesn't recognize the file as incomplete. There are rare cases where LimeWire can detect that a download has become corrupted, and in those cases it will unshare the partial file (making it turn red in the library), but the file will still be correctly listed in the downloads.dat, and LimeWire will remember what it has downloaded for the file.

I'm not positive what you're referring to when you say "still looking into solutions for it".

>Q.3 How can we finish/complete the downloads of PFS files. As suggested, force resume doesn't work. Although I'm still exploring this option.

PFS is an optimization to sharing & utilizes incomplete files. The files aren't really "PFS" files -- they're incomplete files, used by PFS. That aside, the only way to resume them is to click 'resume' on the file from the library. I have some ideas to add a progress column to the incomplete table so that you can easily see how far incomplete files have progressed (or how much of the progress LimeWire recognizes).

>Q.4 The issue of prefs becoming corrupted in some way, be it due to a conflict with another app or whatever, is there anythig we should do to help safeguard ourselves from this.

If the properties are corrupted, LimeWire should display a message letting you know that it detected corrupt properties and is reverting to the default ones. We'll likely add a warning box to clicking 'revert to default' so that people don't do it accidentally. I'm not sure what else could cause properties to revert, other than the operating system itself preventing you from writing the properties file (or reverting it every so often).