Napster-related quirks
----------------------
Napster has some quirks in it, that are unrelated to this program.
Some of the more common ones are:
 - The Napster login server sometimes tells you to log in to your local host
   (127.0.0.1).  Solution: wait a bit (while their server updates) and try
   again.
 - Search and Login can be *very* slow at peak traffic times.

A tip:  The Napster servers aren't linked.  This means, if you don't find a
particular file you want, you can log out and log in again (to a different
server), and try your search again.  This is a common enough need (for me) to
have implemented the "Relog" menu item.


Bugs in gnome-napster
---------------------
I'm certain that this is horribly buggy.  On top of issues such as thread
synchronization and strange queuing logic, a lot of design ideas are still in
flux.  Right now, it Works For Me, and I don't think it is magic.

Bug reports are only useful (in most cases) if I can reproduce the bug, unless
you can fix it yourself.

Bug reports are very welcome now.  Of particular interest is the download queue.
But first: RTFM.  Please read this entire file before sending me bug reports.
I have recieved mail about questions already answered in this document!

To send a bug report: run the program 
	$ ./genbugreport
included with this archive and read the directions it displays.

If someone could explain to me how to operate memprof, I might start analyzing
for memory leaks.  While I'm on the topic of memory consumption: while it may
look like gnome-napster consumes a large amount of memory on Linuxes, it's
actually caused by the implementation of pthreads.  Each thread is a separate
process, but they share memory.  Some programs (such as 'ps') make it seem like
each thread is using an additional 6MB of RAM or so.

Known Problems that aren't bugs
-------------------------------
Old GNOME libs cause the following problem:
	Gdk-CRITICAL **: file gdkwindow.c: line 945 (gdk_window_clear_area):
	assertion `window != NULL' failed.
	Gdk-CRITICAL **: file gdkwindow.c: line 945 (gdk_window_clear_area):
	assertion `window != NULL' failed.
Don't mail me about this anymore, please.  Upgrade your GNOME libs.

Known Problems
----------
 - Some items in the configuration dialog aren't implemented yet.



