index | guide | tools | history
Last updated: 2006-11-23
(TCP) Share version EX2 = e3ebc4e73fb2ce8ed5e3904a82067715be0dd4fd : locale . hint . readme . info
(UDP) Share version NT5 = 3792d45b9bfd1a1cd00fa2b376296fc230932e50 : locale . hint . readme . info
This page list information from my personal experiences with Share. Guidelines of things you need not know or follow exactly, but might come useful one day ^_^;
Guidelines for upgrading Share
Here it's not a question of "how" (which was answered on the main page), but "when". Share has seen a history of frequent updates with lots of unstable versions in between, and it was very difficult to tell which versions were unstable. Village Chief generally responds very fast with same day updates when there is a serious problem, though sometimes the unstable version may have already done some damages by then. The good news is that Share is generally a lot more stable than before ^_^;
Generally, most people do not want to upgrade as soon as a new version comes out, a more stable version may be available few hours later. The more conservative people might even wait for the countdown timer to almost reach zero before upgrading. During that time, there are others (me included) who would have already tried out the new version and confirm whether the new version is stable or not.
If you keep Share running most of the time, you can know how old a new version is by checking the Log view, as it reports the time when a new version first connected.
Guidelines for starting Share
The first window to watch when Share is starting should be the "Log" view. During this time, you can observe Share's connection and database statuses. Nothing should be done with Share (including exiting the application) until Share has completed all its initialization tasks, when the disk activity has calmed down.
During Share's startup process:
If you exit Share before initialization is done, you will lose some cache files, so don't do that.
Guidelines for creating triggers
The way to automate Share for the best experience as it did for Winny. For those who never used it before, triggers lets you download things you haven't seen in search results, typically one of three types:
Note that Share is not completely automated under certain conditions:
Because of this, it's a good idea to avoid overlapping or conflicting triggers,
Hints on avoiding fake files:
Quirks about the query screen
Query screen does not refresh automatically, not even if you change the sort order of the columns, or switch to a different view. This is so that you can copy information from it without having to deal with the information changing under the cursor constantly.
Three ways to force the query screen to refresh:
Sometimes people wonder why they can't add a file to Download by double-clicking it (the file name doesn't turn blue). The most likely cause is that they are already downloading or uploading the same file, possibly under a different name. It's also possible that the user already has too many downloads/keys. Share doesn't say why though, unfortunately.
As of A77, the "cancel task" button and the corresponding "task cancel" menu item no longer cancels downloads (but still works on canceling file conversion). This seems to be aimed at people cutting off slow downloads, and attempts to distribute the traffic more evenly over the entire network.
If your main use of the "cancel" button was to cut off slow downloads then there isn't much more to say... but suppose there are files ready for download (with their order numbers approaching 1), and your download slots are already full, how do you cancel some tasks to yield the slot these files?
One way is to disconnect Share then restart the connections again, a better way is to delete the triggers that are currently downloading (from the Download view). This causes those connections to be cut off immediately, but leaves the other connections unaffected.
Note that the other downloads generally do not start immediately after the download slots are free. Also note that restarting download on the deleted trigger takes a while, even if you add it back immediately after deleting it.
In general, there is no merit to managing the download priorities manually this way, better to let Share handle it automatically.
List of files used by Share
List of files in Share's directory. The minimal set of files are in bold, Share can generate the other ones as needed. Once Share is up and running though, deleting any of them would be a bad idea and can lead to data loss.
Note that for text files, some are encoded in Shift_JIS, while others are in UCS-2LE, and still others in UTF-8. Most modern text editors can read them all without trouble, but some of them will not save the files in the original encoding, so be careful if you modify them. The list is current as of version EX2.
|cache.idx||binary||Index of files in cache directory, deleting this file will cause files in the cache directory to be deleted.|
|cluster.txt||text||List of active cluster keywords.|
|clusterlist.txt||text||List of all cluster keywords specified in the clusters list dialog box.|
|config.ini||text||Various operational settings. UI settings are in share.ini|
|diffuse.db||binary||Status of files currently being uploaded.|
|download.tmp||binary||State of keys for files currently being downloaded.|
|download.txt||text||List of hashes of files currently being downloaded.|
|filter.txt||text||List of files and keywords currently being ignored.|
|folder.ini||text||List of directories registered with Share.|
|hash.db||binary||State of file metadata.|
|hint.txt||text||Help messages, included in the original ZIP package.|
|history.txt||text||List of recent changes, included in the original ZIP package. Not essential to Share's operation.|
|info.txt||text||Additional developer-orientated notes from the author, included in the original ZIP package. Not essential to Share's operation.|
|keymgr.tmp||binary||State of keys and current search results.|
|locale.txt||text||Strings used in Share UI, included in the original ZIP package, including translations. Deleting this file will cause all widgets to be rendered with Share's internal names.|
|nodes.db||binary||List of existing nodes. Deleting this file usually makes Share unusable, until another node connects to you or until more nodes are added manually.|
|oldhistory.txt||text||Old change list documentation, included in the original ZIP package. Not essential to Share's operation.|
|plugin.ini||text||Plugin configuration. Plugin specific configurations are generally in their own private configuration files and not here.|
|point.db||binary||Karma of your peers, no longer in use as of a67c.|
|profile.id||binary||ID data for upload folders.|
|query.txt||text||List of keywords for queries dropdown list.|
|queryid.txt||text||List of IDs for ID dropdown list.|
|querytab.txt||text||List of keywords used in query tabs.|
|readme.txt||text||User documentation, included in the original ZIP package. Not essential to Share's operation.|
|Share.exe||binary||Main program, included in the original ZIP package.|
|trigger.txt||text||List of rules used as triggers.|
Guidelines for asking a question
Okay, so this doesn't have much to do with using Share itself, but I get a lot of questions similar to "I can't find this file, help?" or "how do I make my download go faster?"
Please try to resist asking these questions, I can't really be that much help in either case, especially if you have already read the rest of these pages. Ultimately it's luck and patience, mostly luck if you are trying to find a file, mostly patience if you are waiting for it to complete.
All I can say is... good luck, and be patient ^_^;
|Copyright (c) 2007 serika, under the GNU Free Documentation License.||uguu...|