FreeDB Never Working

[scruffytwigg]

I have suddenly stopped been able to add albums via the FreeDB system. I have tried many ways and always get the an error warning saying NO MATCH FOUND ON SERVER.
This is for any band, album or track I can think of that is Popular, stones, madonna, chilli peppers, rush, seal. You name it, always the above error message.
Have I unticked somethng?, or can you give any suggestion.
Thanks in anticipation

[andrei_c]

This is a know problem. The fix is ready and will be included in the next update. Until then, you can work around this problem by downloading and running the following reg file once:

http://www.firetongue.com/support/DirectFreeDBQuery.reg

Alternatively, you can manually add the following registry key:

[HKEY_CURRENT_USER\Software\Firetongue\Organizer\Fr eeDBSearch]
"DirectFreeDBQuery"=dword:00000000

Andrei

[bull666]

Andrei,

I had the same problem this morning, I added 1 cd and it worked fine and then all of sudden there is no way I can add anything. The weird thing is that stuff like cd-ex appears to connect perfectly to freedb. I clicked on the link you provided and apparently it did something but OrangeCD still does not work and I still have the same message: "No match found on server".

PLEASE HELP !!! :'(

(I'm running 5.9.9 build 9321)

[scruffytwigg]

Thanks Andrei
I have gone into the registery key via reg edit and got to FreeDB part.
Do not know how to add.
Or how to apply the link as it seems like a thread.
Any Help???

[pheisholt]

Hi scruffytwigg

All you have to do is:

1. Right-click the link in Andrei's posting
2. Save the .reg-file to your hard drive
3. Locate the .reg file, and then double click it

The appropriate registry key will then be added/updated. And you're done.

[wlb1006]

I have installed the following: reg file:

http://www.firetongue.com/support/DirectFreeD...y.reg
from Andrei as described with no success.

I now recieve the following when I search:

Bad HTTP status code

What can be done to fix this so I can use the data base?

Please provide detailed steps to correct this.

Running ver 5.2.0 build 7523