-new: added a new script header flag "initialize=1" which will trigger the code section labeled [initialize] to be processed before beginning the search. &nbsp;-new: this allows the ability to modify any of the search variables, including new @search, @profile and also use the read-only @descriptions (1 if turned on and 0 if turned off).-fixed: the redirect '//' bug for toggling same HTTP or HTTPS protocol as the referrer-fixed: 'Locate' button in the script debugger for 'find() and extract()'-fixed: properly urlencode the @search (uses Win32 API.. so for example " " is converted to "%20" instead of "+"... also takes care of all the other characters)-improved: some language translation widths and heights based on feedback from gojko and Exoskeletor (thanks guys!)

sorry.. no installer right now. put the bit_che.exe in your usual place and extract 'external' folder to your bit che %appdir% if you want to open torrents in external programs. i have provided a few demo config files for you to test with (if you want).

I recently moved from my XP box to a new system I built with win7 x64 installed. Right now, I am mostly seeding and don't download too much but some software i wanted offered a torrent download so I figured I'd avoid using their WWW bandwidth.

I think I was using 1.0.60 on my XP system.. but when I tried using BC on my win7 box it was 2.0.60.

Right off the bat it was acting up. It wouldn't update scripts. Then it did. after that I got a good search result. The second time I tried a search, it flashed and reported "done", with no results. I tried with a simple word that has to have thousands of matches and again, 0 and done.

I started reading here and saw the newer versions, so DL build 70 which I think is the latest beta?

I got a couple excellent search results with it, selected a few torrents, they triggered my tixati dialog and started just fine. no problem.

I opened BC again today, tried a simple search and 'poof', 0 results and done.

I'd be most happy to assist with any other testing or details, but wouldn't know where to start with this. damn intermittent problems!

strange.. BC was (mostly) developed on Win7 x64 and never had intermittent issues except for people with anti-virus/firewall issues. I would start there -- which are you using? Have you tried with everything turned off (just for testing purposes)?

yes, my ignorance. New to win7 and the sample norton's security that got added on..

I had added BC as "trusted" but no difference. and i could not see where any exceptions were added. Once i researched it, I found the list of programs and sure enough, nortons had auto-blocked BC. Since it worked at first, I suspect nortons was monitoring it as strange activity, with a burst of connections and all. A custom rule for BC fixed the 0 results issue.

new: added a new script header flag "initialize=1" which will trigger the code section labeled [initialize] to be processed before beginning the search. new: this allows the ability to modify any of the search variables, including new @search, @profile and also use the read-only $descriptions (1 if turned on and 0 if turned off). improved: some language translation widths and heights based on feedback from gojko and Exoskeletor (thanks guys!)fixed: the redirect '//' bug for toggling same HTTP or HTTPS protocol as the referrerfixed: 'Locate' button in the script debugger for 'find() and extract()'fixed: properly urlencode the @search (uses Win32 API.. so for example " " is converted to "%20" instead of "+"... also takes care of all the other characters)