
Last Update: 2-23-02
Welcome to the FAQ of alt.music.mp3.winmx, a newsgroup dedicated to the discussion of the software program WinMX, available at http://www.winmx.com
Currently there is no "Mini-FAQ". That will be pursued after we figure out this version.
Web Sources related to WinMX:
http://homepage.ntlworld.com/d-morris
http://http://www.trippymx.co.uk/whatiswinmx.html
Authors: Randy and roger - and the Entire WinMX newsgroup (we've just put a lot of this together from other's replies)...
WPNP stands for WinMX Peer Networking Protocol. WPNP is a protocol that creates zones (or groups) of servers and clients and allows other WinMX clients to share using this protocol.
A very brief explanation for a WPNP server is that your computer is acting as a server node and participates in searches for files and maintains lists of songs. It takes some bandwidth and processing resources to act as a server.
Peer redirect means that the computer does not participate, but draws results and share connections from the WPNP server nodes.
It is very important that if you have the processing resources, memory and bandwidth, that you configure your machine as a WPNP server. That's what makes WPNP work! If nobody participates as a server, it isn't possible to share using WPNP.
To participate as a server, you should have 128MBytes or more of memory a Pentium 350MHz or better, and an upstream bandwidth of more than 12 K/s (about 128kbits) is recommended. A server node requires bandwidth to share music lists and participate in song searches. Default installation options on WinMX v2.6 are to use peer-redirect if your computer's processor speed is less than 350MHz.
To act as a WPNP server, select the configure button that appears when you put your mouse over the "WinMX Peer Networking Protocol" in the Servers Window and uncheck the box next to "Only use redirects". To not act as a WPNP server, check the "Only use redirects" box. The rest of the options should be left at their defaults.
The server window consists of three sections: WPNP, High Capacity Network List and the Low Capacity Network list. Initially, Napster, before it went private and started blocking other applications, was the only high capacity server listed in the server window by default.
In WinMX the difference between High Capacity and Low Capacity servers is simply the method of connection. With servers in the Low Capacity category you can only connect one-at-a-time while with servers in the high-capacity category there is a Connect All selection. The concept of "High Capacity" servers was added to WinMX version 2.5 as a planned feature with the belief that more very high capacity Napster-like servers would become available, which due to the shutdown of Napster is no longer expected to occur.
Servers may be added either manually, by exporting a list from a program such as NapMX at http://napmx.darkservers.net, Napigator at http://www.napigator.com, or by replacing the server data file from a source such as TrippyMx at http://www.trippymx.co.uk.
There is no real preferred source since the validity of any particular server depends on the update frequency. Having said that, the current favorite appears to be NapMX.
For a list of potential OpenNap servers go to http://www.napigator.com and scroll down until you reach the "Servers" section. Also check when logging into a network, periodically right click and select "Review .
OpenNap servers can be added by clicking the [Servers] button, moving your mouse over the "OpenNap Protocol High Capacity Networks" (or Low CapacityNetworks) and click on the "Add" button that appears to the right. You need to know the IP address or domain name of the server, the Network it is on, and the Port of the server in order to add the server so that you can connect to it. Add this information to the "Add Server" dialogue box that appears. If adding a server to a Network that already exists, place mouse next to Network and click the "Add" button.
Some servers require that you register when first logging in, so it is usually a good idea to check this box in the "Add Server" dialogue box, and enter a valid (or valid looking) email address for a new network. The OPENNAP protocol does not appear to matter, so it is recommended to use the default.
For a list of potential OpenNap servers go to http://www.napigator.com and scroll down until you reach the "Servers" section.
There are a few different ways, three are detailed below…
NapMX is a new program that does a tremendous job of acquiring servers and will export the list directly to the WinMX servers list, or export to an external file. Recommended due to ease of use and retaining domain names of the servers.
Adds servers from a server database program called Napigator,http://www.napigator.com/
After you have downloaded and installed it, run the "Stand Alone" version and follow the steps below:
If that doesn't work, try dragging the .wsx file with your right mouse button and selecting "Open With" as you drag it over the WinMX icon. Or, start WinMX before doing this procedure, and drag the .wsx file onto the WinMX desktop icon while it is running.
You may want to edit your .wsx file in Notepad, and look for "N/A" next to the network name. This means "Not Affiliated" and are not really a network.
TrippyMX: offers news, information, help, assistance, and the popular TrippyMX server list.http://www.trippymx.co.uk/
Importing servers is a cumulative process (with the exception of TrippyMX which replaces the entire server file).
Obsolete servers are not removed nor are servers that change to other networks; just new entries are added. It is generally a good idea to delete a network if it fills up with too many entries that won't connect and re-import.
Napigator, http://www.napigator.com/, uses IP addresses, not Domain Names, and the IP addresses continuously change on the servers that use dynamic IP addresses. Therefore a server that uses a dynamic IP address will probably not connect when a Napigator server list is imported.
Some of the messages you may see when attempting to log into a server/network are "Banned", "Only Registered Users" and "Log In Here..." with a URL they want you to go click. Details of these are in this section below.
When attempting to connect to a server, you may receive the message: "Banned", or "WinMX Banned here", or even less pleasant messages. Put mouse over the server that displays the "banned" message, select the edit button, and change the reported client to something like "xnap" or "V2.0 Beta 10." A full list of potential clients is given at http://opennap.sourceforge.net/#clients. Note, some of the servers are better than others at detecting WinMX clients no matter what you report.
It is possible to change the client for an entire network by moving the mouse over the network, selecting Edit from the gray boxes that appear to the right, and then changing the client (to "xnap" or "V2.0 Beta 10"), and then selecting the tick box, selected by default, for the "Apply login parameters to all servers on this network."
Put mouse over server, select edit, enter a valid looking email address and click the "Attempt to Register on first use" box.
They want you to go to their website, download and use their client. You can try changing the client reported by WinMX and see if that helps bypass the message.
For firewall information, see the following: http://homepage.ntlworld.com/d-morris in section 5.1 and for XP at: http://www.sans.org/infosecFAQ/win/XP_firewall.htm.
You need to properly configure any firewall you use or nobody will be able to upload from you! By default, TCP port 6699 and UDP port 6257 need outbound permissions.
Some common ones are detailed below.
When you attempt to download a file and get a response of "Busy Queueable", this means you are attempting to download from another WinMX client that has no open transfer slots available and have the option to remotely queue the song for later transfer when a slot becomes available.
When a file is "Busy Queueable", you are able to enter the remote queue by right-clicking on the file in the transfer window and selecting "Enter Remote Queue".
A server will sometimes respond with "Busy Queuable" repeatedly. The exact reason for this error is not known, but it appears to a combination of the particular server and the number of files shared by the user being connected to and the server settings. In this case, right-click on the file(s) and select Auto-Retry, and "most" times, you will finally get into the remote queue.
If you have set your Download Queuing options to allow more than one download from a user, try to not do this with a whole group of songs since it is impolite to queue a group of songs and is hammering (see glossary) on the server. It may result in getting banned from the server.
The Queue number that appears by a potential download in the transfers window represents the total number of files queued for transfer from the user you are attempting to get files from. The Queue number does NOT represent your position in the queue. This number indicates your position in the queue only when you FIRST enter the queue. If the number is a low number, it also can give you an idea of your position in the queue.
As users add files to the queue the queuing number will increase. When others finish their downloads, cancel their downloads, time-out, or go off-line, this number will decrease.
The queuing number really just helps provide a guestimate of your chances of getting a file. In the worst case, enter the remote queue, right click the file, try to "Find Alternates" or "Find Similar," and look for greener pastures.
Busy usually means you are trying to download from a Non-WinMX client (section 4.4), but can also mean that you have tried to queue a file when the other user's server-settings have been exceeded (yet somehow you managed to "see" the user). Your only option is to right-click and select "Auto-Retry". You will be at the mercy of good timing in hoping a connection attempt occurs during a time period when there is an open transfer slot on the other client. See 4.3 for further information.
Auto-retry can be enabled by right-clicking an attempted download and clicking-on "Auto-retry". Auto-retry will then retry the download based on settings that you have set in "Settings/Connection" and "Download Auto-Retry Interval".
You can set-up WinMX to auto-retry every-so often, but if the user is offline (or has changed their name) then this is useless. Try to not "auto-retry" more than one song per server since "auto-retry" sends a request to the nap server and essentially is hammering the sever to fulfill the request. Tends to annoy server operators and they ban you.
This current version of WinMX doesn't support queuing into non-WinMX client software. Nor can Non-WinMX clients queue into WinMX. In fact, if no transfer slots are available, Non-WinMX clients won't even be seen as trying. This particularly annoys AudioGnome users who do at least see WinMX users trying. Try to avoid non-WinMX clients until this problem is fixed. Lopster appears to have a patch that addresses the queuing problem with non-WinMX clients. http://lopster.sourceforge.net/
The Whois command is found when you right-click on a user in the Search, Transfer or Hotlist window and select Whois. The Whois command gives a list of the user's statistics including things like time online and number of files shared. To date, most of the data appears meaningless with the exception of Shared Files, which most of the time pretty accurately shows the number of files the user shared when they logged into the network.
Pressing the HOTLIST button at the top of
the WinMX window accesses the Hotlist window. The Hotlist window
contains a list of users that you either have permanently added
to the list, or have temporarily added to the list during your
current session through the sending or receiving of messages
The Hotlist window is useful for tracking friends and
acquaintances, as well as somebody that has files that you want
and you would like to know when they are online. Only users on
the OpenNap networks (topic 2.0) can be permanently added to the
Hotlist. The Hotlist only supports one "nick" (handle,
user name) per a network.
There are numerous ways to add users to the Hotlist window; by right clicking on a search result in the Search window, a file transfer line in the Transfer window, through the Browse window, the Whois window, or through the Hotlist window manually, or right clicking on the temporary entry.
A WPNP user cannot be permanently added to the Hotlist. WPNP is by its nature "connectionless" and, as a result, a user can only be temporarily added to the Hotlist while users from OpenNap networks (topic 2.0) can be permanently added to the Hotlist. The users name is appended by a number sequence that continuously changes.
This setting is meant (and should be used) to keep others informed that you're not available for some reason. As you might realize it is not very nice to send a message to someone and never get an answer.
You can send a message to a user by right clicking on the user in the Hotlist, Search or Transfer windows and Select "Send a Message." In the Hotlist window, if open, and in the System Tray (that area where the time appears in Windows - the bottom right-hand corner) an envelope will start flashing on the person to whom you have sent the message, if they are running WinMX. It may take them a while to notice, if they are even at the machine to begin with. Other clients that are capable of receiving messages have different methods of notifying the user if they have a message. Not all clients support messaging.
When the person (or "if the person") to whom you sent a message replies, you will end up with an envelope flashing yourself. Double-click the envelope to see the message.
If the person is not currently in your Hotlist, they will be added to the Temporary section of the Hotlist window. You can add a person who is listed on an OpenNap server permanently to your Hotlist. WPNP users, however, can only be temporarily added due to the "disconnected" nature of the WPNP protocol. Right-click the user in the Hotlist and select "Perm add to list" to add the user to your Hotlist permanently.
Setting your privacy level to none will offer a better chance of messages getting through to you.
To reset the privacy level, click the burning small icon on the top left corner of the Hotlist to get a drop-down menu. Click Privacy Level... Click on the "Allow all messages" dialog. You may choose other options depending on your preferences (although don't complain that IM doesn't work!)...
The underlying mechanism is exactly the same. The only difference is that Send/Receive Message continually requires opening up little windows for the messages. Chat keeps a window up continuously. If you start doing more then three messages, open up a chat window instead. Also, selecting Chat will (usually) not continuously display Auto-Responses if one has been set
You can find Bandwidth Throttle by pressing the "Bandwidth" button in the Transfers window. Bandwidth throttle is the time period when WinMX attempts make adjustments to the bandwidth being used for downloads and uploads (if bandwidth limiting has been set as discussed in section 8.1.2). WinMX will attempt to equalize the transfer rates and make adjustments to any priority settings that may be in effect (as set by right-clicking the user and going to "Bandwidth Priority." It is recommended that the Bandwidth Throttle be left at the default of 250 milliseconds. Setting a higher rate consumes more CPU time and doesn't seem to do anything noticeable.
Bandwidth for both uploads and downloads can be limited using the "Bandwidth" button in the Transfers window. Though nobody has of yet had a reason to limit download bandwidth, limiting upload bandwidth turns out to be pretty important for users of Asymmetrical protocols, such as analog modems, ADSL and capped cable. See section 15.6 for how download speeds are affected by Bandwidth (or lack of) limiting.
You can set a "Bandwidth" priority for a user transferring from you by right clicking on the line in the download section of the window, and selecting the "bandwidth priority option" This only works if you have set a Bandwidth limit as discussed above.
Specifies the number of files you can download/upload at a time from a user and the maximum number of simultaneous downloads/uploads you will allow. You need to tailor this for your type of connection. See Netiquette section below for other considerations.
Click on the Settings button, select Share Settings, click on the Browse button, which is in the Download Folder section of the dialog box. Browse to the folder of your choice.
There are a couple of ways to capture a window that you want to save in WinMX since it does support a way to select and copy window selections.
Use the Windows Copy and Paste function. Hit ALT + PRINTSCREEN to copy the window into memory. Open up a paint program and select Edit->Paste (Paste Special) to copy the screenshot of the window into the program.
Use a program called SnagIt, http://www.techsmith.com/products/snagit/default.asp, which does a wonderful job of copying the window contents into various file formats.
There are several programs that do this. List Maker, http://www.nwlink.com/~koolguy/home.html, is a good one. You can find more by searching at http://google.com for mp3 list utility.
Ping is an old program developed for mainframes and workstations which was really designed to check for connectivity of a remote machine and for any unusual latencies due to configuration or router issues. Ping is available in the Search window.
What ping does is check to verify that a
connection to a remote machine is functioning.
Keep in mind that...
1> Pings can be blocked by a local firewall, such as
ZoneAlarm, yet file transfers can still take-place.
2> Ping times are a measure of latency, not speed. These two
things are not closely related.
What Ping does NOT do is necessarily indicate how fast a transfer will be. It can *kind* of indicate a good speed if you do repetitive pings and get very good response times, but it just may mean the machine is responsive and the route to it is very good.
Recommendation: Just try and transfer! If it is slow, look for another source.
As of the moment, the consensus seems to be that LAME makes the best MP3s. One of the easiest programs to use for extracting music from CDs and encoding them is Cdex, http://www.cdex.n3.net/, which uses the latest LAME codecs. DBPoweramp, http://admin.dbpoweramp.com/, is also highly recommended. EAC, http://www.exactaudiocopy.de/ or Exact Audio Copy, is considered by many to be the very best for Audio extraction, particularly if you have any problem CDs...ones you used as a frisbee playing catch with the dog, for instance. It is a bit tricky to set up but a good tutorial is available at http://www.ping.be/satcp/tutorials.htm.
With higher speeds, people are leaning more
towards 192 kbps as a minimum recommended encoding. Use Joint
Stereo or Stereo. Joint Stereo mode is only now considered to be
usable by LAME, but LAME still defaults to Stereo mode. Do NOT
use forced joint stereo! If you have keen ears and desire quality
over size, explore using VBR (variable bit rate) which is working
very well in LAME, or 256 kbps which is considered to be near
perfect CD Quality. The VBR encoding appears to have excellent
quality, does a great job retaining the dynamic ranges, and are
quite a bit smaller than 256kbits. Having said that, there is a
large contingent of people that do not like VBR. All this tends
to boil down to the ears of the ripper and desire of quality to
size (or accommodating both).
It maybe should be noted here that all this pertains to ripping
and encoding your own MP3s from your own source material. Once
encoded at a given rate an MP3 can not be improved and can only,
in fact, be degraded by decoding and recoding (also known as
resampling) of the file. If you want high quality MP3s you are
either going to have to find them that way to download or make
them yourself. You CAN NOT take a 128kbps MP3 and re-encode it to
192kbps and improve the sound. All you will do is degrade the
quality and then if you reshare that file...well, one thing leads
to another and the next thing the file sharing community will all
be trading a bunch of very bad quality but large sized MP3s.
Please do not contribute to this.
Although a 128kbps sampling-rate of a 44Khz range was at one time "touted" as "CD-Quality" there is a noticeable difference to most people's ears between a file recorded at 128Kbps sampling and one recorded at 192Kbps sampling. The "touted" 128Kbps rate was before broadband, and even 56k modems for that matter. Those users who are interested in balancing quality with size should consider using a minimum rate of 192Kbps or VBR. For lots more info and ideas about the whole mp3 question you might want to check out this FAQ http://webhome.idirect.com/~nuzhathl/mp3-faq.html from Xory, a one time regular in the alt.music.mp3 newsgroup. There is another FAQ here http://www.mp3-faq.org, from the folks at alt.binaries.sounds.mp3 that has much good information. Like most FAQs, and indeed probably this one on occassion, these may not have been updated as fast as the technology has advanced so if you really want to be on top of things it is best to check in on those newsgroups, as well as ours, as often as possible. You might also be interested in visiting the web site and bulletin boards of http://hydrogenaudio.org/. They have compiled some excellent versions of the Lame codecs with various presets and have much lively discussion going on about these topics.
This is something that can usually be done
with the software that came bundled with your CDRW. It is usually
just a drag and drop process, from a window in the Explorer like
interface of EZCD Creator of Nero for instance, into the CD
compilation window. Not too long ago you had to convert the MP3
to wav to burn the CD but, even though some folks insist this is
still the best way to do it, most burning programs will now do
this "on the fly" reducing the time involved. The
information still is changed from MP3 to wav to cdr format but
the process is done transparently - "in the
background".
Nero and EasyCD Creator are currently the favorites of most folks
but there are many other programs available, many on the web
either free or shareware.
Again there is lots more help available on line...for more details try this excellent CDR FAQ from Andy McFadden http://www.cdrfaq.org.
Create an empty mp3 file (open notepad, save to a file named "test.mp3" or whatever without anything in it), then on the song you want to download, right click and select "Resume from" and download the song you want into the empty mp3 file. This only works if you don't enter into a queue.
Setting Auto-Retry on resumes done this way does not change the filename. If you are fast enough, and get to the file in your transfers window BEFORE the "queueable" message comes up, the filename will not change from the one assigned by you to it.
Check the movie extension (after the dot in the filename). If the extension is .mov then you need Quicktime from Apple, http://www.quicktime.com, if the extension is "avi" then there are many different codecs (coder/decoders) available. Ensure that you have the latest from http://www.divx.com.
RealPlayer (make sure you get the basic player - it is always hard to find on the site) will sometimes play movies that don't work in other movie players. Make sure you do not install Comet Cursor (spyware) when installing realplayer. Use the Custom install and untick the comet cursor box. You also want to make sure you opt out of all the options they give you and be very careful about what files it associates with itself. All of the Real software can be very intrusive and extremely pesty.
Easy Solution: download and install WinAMP from http://www.winamp.com. This is the program that does it best.
Many of the "full featured" players out there are bloatware and your system will take a serious resource hit in order to play your music. It ain't necessary folks. WinAMP plays well, sounds good, has a built in equalizer, and can be extensively configured with a huge assortment of plug ins available at the WinAmp site. Most of which are free.
I only see xx files! Server boots me when I browse!
If you right click on a user in the Transfer, Search, or Hotlist windows, you have the option of "Browsing" the user. This will allow you to see what files the user is sharing.
Some servers will only allow you to see so many files. For example, you may get only 500 or 1000 results returned. Some servers will immediately boot you (disconnect you) if the person you are browsing has over 1000 shared since the server is not configured properly to handle that many files.
Almost all the servers will only allow browsing a limited number of files. In addition, most of the servers limit how many files you can share. A couple of servers always return 0 results. It is useless to say "which" servers since they can change without notice. Just be aware you may encounter these limitations.
With WPNP (WinMX's native protocol) it takes a while for the browse results to come in. If the user is sharing a large number of files, the browse will often stall out and never complete. This is a known issue in WinMX and we can only assume it is a limitation of the WPNP network portion of the program.
Tweak your TCP/IP Protocol adapters to get the most speed.
For information on how to do this see John Navas' Cable and DSL Tuning guide, http://cable-dsl.home.att.net/, and click on the "Quick and Easy" link. You might also want to check out http://dslreports.com...they have tests and tweaks and lots more.
Make sure that you have tweaked your MTU (Maximum Transmission Unit). For information on how to do this see John Navas's 56K Modem Tuning Guide, http://modemfaq.home.att.net/index.htm, and look for the link "Why does my Windows 95 Internet run at half-speed". You could also do a search at Google.com for "modem tweaking utility" and get enough hits to keep you tweaking well into the night.
A user has noted that setting an upload limited to 3250 B/s (when connected at 49kbps) was optimal. Increasing the upload limit slowly slowed down downloads, but at about 3500, download speeds plummet. With good modem connections the user was able to manage 4.5 kb/s down while doing 2.75-3 KB/s up.
Slowly increment and decrement the bandwidth and find where you make the best balance for upload and download speeds. Only allow one upload and perform one download at a time.
File transfers involve one side sending a packet of data and then waiting for an acknowledgement from the receiving side verifying they received the data ok. If all the upstream bandwidth is consumed sending large data packets, it becomes very difficult for your client to get its acknowledgement packets inserted with all the other upstream traffic. The following are recommendations based on type of service. In addition, there is a weakness in the basic TCP Internet Protocol that causes this.
Other than applying the tweaks referenced above, the other biggest factor for slow download speeds is failing to limit the upload bandwidth. Select the Bandwidth button on the Transfer Window, check the box for Limit Upload Bandwidth, and use the following guidelines:
Set to just below your provider's cap. If you have a 128kbps capped connection try setting the total bandwidth to something like 12000Bytes/s (12000 bytes is approximately 94Kbits/s). Slowly increment/decrement to maximize your speed. The more downloads you have going, and the higher the download rates, the lower you need to adjust the upload bandwidth limit.
An Incomplete Download from WinMX's point of view is a file transfer that has not reached the file-size recorded in "incomplete downloads.txt" -you can find this file in your Uploads folder (see section 11.0). If you manually delete such files (using Windows Explorer for example) then WinMX will get a bit confused since it is tracking these files.
In the Transfers window there is a button the says either "Show Incomplete" or "Clear Incomplete" depending on whether or not there are incomplete transfers in your Transfer window. If the button reads "Clear Incomplete" and it is pressed, all incomplete files will disappear and the button will change to read "Show Incomplete." Pressing the "Show Incomplete" button will result in all incomplete files appearing (Incomplete downloads from WinMX's point of view - NOT from your point of view!).
You can (and should) use WinMX to delete these files if you wish to remove them. Right click each file and select delete. If you have a bunch of files you can hold the <CTRL> key down and click on each file to select the bunch. Right click on any "grayed" file and select the "Delete file" option.
WinMX does not seem to have too many installation issues on the Win9x platforms. For Version 2.6 simply run the executable (after scanning for viruses) you downloaded. Disable any virus scanning software before installation. WinMX requires internet explorer to properly run.
Right click on the short cut to the program and click on "run as" and remove the check that protects WinMX from other users.
To enable or disable Internet Connection Firewall
The following article on how to manually open ports in the XP firewall may help resolve some issues. Add WinMX port 6699. The document is located at:
http://support.microsoft.com/support/kb/articles/Q308/1/27.ASP
WinMX needs Internet Explorer (IE) 4 or
later to run since it uses files from IE. Install the most recent
version of IE to overcome this issue.
NOTE: it is possible to run WinMX without IE, however you need
the appropriate DLLs from IE to run WinMX. If someone knows what
they are (Micas?), please let us know!
MP3 files in and of themselves are not executable files and do not contain viruses. Movies and programs however often have viruses planted in them. ALWAYS! use a good anti-virus program (particularly when connected to the net), and keep it updated (McAfee has been updating almost every week). It's worth its price in gold and will save you from more nasty & painful problems.
ALWAYS! suspect the worst from everything that can get to your computer (files, disks, diskettes, dlls, emails); Even from your friends (they usually spread viruses without even knowing it). Scan files and disks PRIOR to using ANY files off them.
Don't allow unknown files with suspicious extensions (i.e. programs.exe .com & some others...) to download to your computer unless you're absolutely sure of what you're doing.
ALWAYS! suspect ALL emails with attachments from unknown sources (and even known if they're programs or have multiple extensions like:file.txt.exe / file.jpg.exe) and you haven't asked for it previously.
ALWAYS! Suspect from those emails with no subject and body-text leading you to the attachment or with subject and no body-text but attachment. Watch out for those worms that work (run) with an "on mouse over" command (html email). Don't even open email/attachments whose sources are not well known. Delete them without even opening!
Basically: if you suspect a file or Email, don't open/run it and delete it immediately. Play it safe. If it was from a friend and deleted by mistake you can always ask your friend to send it again. All these warnings apply doubly if you are using Microsoft email clients. They are the most widely used and thus the most frequently targeted points of attack. Be very very careful with Outlook or Outlook Express.
Spyware is software that tracks your
internet usage and sends files to various companies about your
use of the internet. For a great explanation of spyware see Steve
Gibson's site at
http://grc.com/downloaders.htm
Another good resource is
http://www.spychecker.com/ If you are not sure if something
you have is actually spyware or just adware (a pain but not as
intrusive) they would be the ones to ask. As a service to you we
are providing this search box (ain't we grand?) If you have a
program or are considering downloading one you are not sure
about, put the name in the box below and search the database to
see if it really is spyware.
Spyware does stuff to your registry, uses cpu cycles and violates your privacy. Often, if you have spyware on your system it runs slower, crashes more often and is generally less stable.
RealNetworks Realdownload, Netscape/AOL Smart Download, and NetZip Download Demon all contain spyware when you install them in their default configuration. Comet Cursor, Godzilla, Cute FTP (older versions) contain spyware. You should remove them. They are intrusive and capable of tracking and logging a lot more of your computer activity than they ever need to or should be able to.
To obtain a spyware remover you can visit: http://www.lavasoftusa.com or http://www.lavasoft.de/aaw/ and download LavaSoft's Ad-Aware product.
WinMX has received a bad reputation and is banned on some servers because of its ability to connect to multiple servers. It is recommended that you do not use the connect to all servers button (after servers have been added to the "High Capacity Networks" in the servers window - see section 2.0) with the "Connect All" option that is available. Instead manually connect (mouse-over the network name and press connect) to five or six different networks that have shared lists that meet your interest areas. It will take some exploration to narrow down your favorites.
Why is it bad to connect to so many servers?
Ninety-nine percent of the time, 5-6 good servers will have what you need. So what point is there in being connected to 40 servers?
People on those networks will obviously be trying to download from you. How many people can you sustain uploading? Want to piss off a server operator, let them see they that have a ton of users waiting to download from you but can't because you are so over subscribed and have so many people queued in already you can't possible serve them all.
You are just tying up limited resources and preventing other people from using the servers.
If you are searching for some hard to find stuff, start dropping servers and connecting to new ones to expand your search; just don't keep connecting to more and more networks.
Queuing is set in the Transfers window, Queuing button. You can set the maximum number of files you can download at one time, the maximum number of downloads per user, the maximum number of files that other users can upload at one time, and the maximum number of uploads per user.
It is best to set yourself to receive only one download per user, unless you can get permission from the user you are downloading from before hand. Set your maximum downloads per user by pressing the "Queuing" button in the transfer window. You can then queue a number of files for the user and files not currently being downloaded will appear as "locally queued." If you receive permission to download more than one download per user you can always right-click a locally queued file and "Start Transfer." Trying to download a bunch of files at the same time off of another user just pisses them off and you will usually find your downloads cancelled, and if you repeat queuing a large number of files you will be ignored.
Recommended settings are a "Max Total Downloads" of 10 and "Max downloads per user" of 1
Try and get your upload settings so that you can sustain a minimum of 4k or better between transfers. It does not make sense trying to be over-accommodating and have 12 people downloading at 0.8k/s and sitting around for hours hoping the transfer will finish. For modem users, this means one upload and one download per a user. For 128kbs capped DSL and Cable services, this means 3-4 uploads total. If a user that is trying to download a file is queued and there is bandwidth still available, you can always right-click the queued file and "Start Transfer."
This is an area of debate. On the one hand, people feel that remotely queuing up an albums worth of music at a time is fine. On the other, many feel it is very unfair and rude and that you should only remotely queue one song and set the rest to Auto-Retry, which will automatically place the next song in the queue after the transfer of the first one is complete.
Recommendation: Follow the latter policy and attempt to contact the other person to check their policy. The general consensus is to follow the "Remotely Queue one song at a time" rule. It is NOT recommended that you try more than one album at a time without permission, as that is considered very rude, selfish and greedy.
You should periodically view the server messages. While logging into a network, right click on the network name and select “View Server Messages”. You can get system announcements, rules, and often a website of the network where you can gain other information, as available servers for the network, status, etc.
The WinMX newsgroup is not a flame throwing area. There are many users who will make an effort to answer your questions, and HOT topics regarding WinMX (such as leeching) are discussed. Discussion of other products in the WinMX newsgroup should be limited to comparison with WinMX. Questions regarding the implementation and operation of other products should be discussed in their own forums.
The usual standards of human decency are expected in the newsgroup (courtesy and respect for others opinions).
A discussion of netiquette for newsgroups,
and questions related to netiquette can be posted in the
newsgroup: Microsoft.public.netiquette
A short article on the basics of using usenet politely and
efficiently can be found at
http://unix1.sncc.lsu.edu/internet/usenet/usenet-etiquette.html
- Hammering: Hammering means to repeatedly attempt to connect to a server or send a command to a server time after time with little interval between. Explanation in a nutshell: Pisses off server operators who will ban you.
- IMing: Instant messaging. The ability to send messages directly to another user without having a server intervene. The other user must be online.
- Leech: Somebody that purposefully does not share any files. This is not a nice person.
- Nick, Nym or Handle: The username or nickname a user gives to themselves.
- WPNP: WinMX Peer Networking Protocol. The protocol that is used by WinMXto allow peer-to-peer based file-sharing (as opposed to server based file-sharing).
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"If you want 100% accurate songs of the highest quality and no time spent in wondering if what you get is going to be good or not, buy the CD."
Randy
"Just because you CAN do it, doesn't mean that you SHOULD do it."
roger
Last revised: March 1, 2002