@ 27.5°w bbc one hd / bbc hd / itv hd / 4 hd / 301 bbc sport hd

Status
Not open for further replies.
OK, I have started my analysis of the keys between 20 00 00 [] 00 00 00 [] and 2F FF FF [] FF FF FF []

How is everyone else getting on?

Any volunteers for other ranges?
 
I'll start from 300000000000 to 3fffffffffff. But I don't know if it's correct.
 
I'll start from 300000000000 to 3fffffffffff. But I don't know if it's correct.
I think it sounds right. Not sure how long it is going to take though, the "Remaining Time" counter in CW Finder doesn't make much sense to me :Dunce:
 
I think it sounds right. Not sure how long it is going to take though, the "Remaining Time" counter in CW Finder doesn't make much sense to me :Dunce:

The problem with cw finder is it is old and takes forever (realistically looking at many days even for the small ranges we are using). Cudabiss is far faster but obviously needs an nvidia card capable of cuda (knew i should have got nvidia at last upgrade instead of radeon). Did read somewhere that a large 4Gb ts file (bigger is better apparently) can be potentially cracked in days rather than weeks with cudabiss. Still hopefully there will be others getting together who have cudabiss and will beat us to it....the more the merrier as far as cracking goes.

Do not watch bbc etc much but want it because it can be got if you know what i mean.

Also silly question but do you need to enter the [] as I just put in the 6 hex digits ie start 100000000000 end 1fffffffffff
 
Last edited:
I feel that I know what I am doing now. My range has been running overnight and the remaining time has reduced by about a day (in less than a day!). I am going to set up CW Finder on a second PC and run another range there too. So now we have ...

fourthwisemonkey - 11 11 11 11 11 11 to 1F FF FF FF FF FF
blueplatinum ----- 21 11 11 11 11 11 to 2F FF FF FF FF FF
Madison ---------- 31 11 11 11 11 11 to 3F FF FF FF FF FF
blueplatinum ----- 41 11 11 11 11 11 to 4F FF FF FF FF FF


Desperately need more volunteers to speed things up. There must be someone else out there who requires this key and therefore needs to participate.
 
:new update:

So now we have ...

fourthwisemonkey - 11 11 11 11 11 11 to 1F FF FF FF FF FF
blueplatinum ----- 21 11 11 11 11 11 to 2F FF FF FF FF FF
Madison ---------- 31 11 11 11 11 11 to 3F FF FF FF FF FF
blueplatinum ----- 41 11 11 11 11 11 to 4F FF FF FF FF FF
darkart ---------- 51 11 11 11 11 11 to 5F FF FF FF FF FF


There must be someone else out there who requires this key and therefore needs to participate. There are only 9 opportunities remaining (we seem to have overlooked X0 00 00 00 00 00 to X1 11 11 11 11 1E in each range). The next range should be 60 00 00 00 00 00 to 6F FF FF FF FF FF. If we don't find the key, I suggest we address the missing ranges in the existing scans at the end.
 
Sorry .. above should read

"
(we seem to have overlooked X0 00 00 00 00 00 to X1 11 11 11 11 10 in each range)
"
 
I run 2 apps. In addition to 30 00 00 00 00 00 - 3f ff ff ff ff ff I'll take 60 00 00 00 00 00 - 6f ff ff ff ff ff.
We talked about 10, 20, 30 yesterday. Why do you use 11, 21, 31 etc.?
 
I run 2 apps. In addition to 30 00 00 00 00 00 - 3f ff ff ff ff ff I'll take 60 00 00 00 00 00 - 6f ff ff ff ff ff.
We talked about 10, 20, 30 yesterday. Why do you use 11, 21, 31 etc.?
Sorry, it was because I cut and pasted from fourthwisemonkey's original post. I'll re-post for clarity.
 
blueplatinum, I would like to participate, but I'm afraid my HW is not powerful enough to finish one range within some realistic time. What is the rate (keys/s) you achieve?
I've done some tests using cudabiss this weekend and with nvidia ion 2 (has 16 CUDA cores) it went too slow...
 
:new update:

So now we have ...

fourthwisemonkey - 11 11 11 11 11 11 to 1F FF FF FF FF FF
blueplatinum ----- 20 00 00 00 00 00 to 2F FF FF FF FF FF
Madison ---------- 30 00 00 00 00 00 to 3F FF FF FF FF FF
blueplatinum ----- 40 00 00 00 00 00 to 4F FF FF FF FF FF
darkart ---------- 50 00 00 00 00 00 to 5F FF FF FF FF FF
Madison ---------- 60 00 00 00 00 00 to 6F FF FF FF FF FF


fourthwisemonkey : can you confirm if you started at 10 00 00 00 00 00 or 11 11 11 11 11 11 please?

We need more testers - There must be someone else out there who requires this key and therefore needs to participate. There are only 8 opportunities remaining.
 
blueplatinum, I would like to participate, but I'm afraid my HW is not powerful enough to finish one range within some realistic time. What is the rate (keys/s) you achieve?
I've done some tests using cudabiss this weekend and with nvidia ion 2 (has 16 CUDA cores) it went too slow...
My system indicates it is going to take just under seven days more to complete my first range. I don't know what stats other testers are getting. I have no objection to people taking a smaller range within reason. What does everyone else think?
 
You're way ahead of me. I've got 999277 CWs and I haven't even managed to get the second PC to run the program yet !
 
I suppose we also need to test 00 00 00 00 00 00 to 0F FF FF FF FF FF so that means there are 9 more ranges still to be allocated.
 
I just started range 70 00 00 00 00 00 to 7F FF FF FF FF FF with CWFinder 0.9 (BETA)

I'm still little bit skeptic about the timeframe.... Each range consists of 44 bits. 2^44 = 17 592 186 044 416 possible CWs. Say, you have rate 2 000 000 CWs/sec, that'ss 8 796 093 seconds or 146 601 minutes or 2443 hours or 101,8 days :-(
 
I just started range 70 00 00 00 00 00 to 7F FF FF FF FF FF with CWFinder 0.9 (BETA)

I'm still little bit skeptic about the timeframe.... Each range consists of 44 bits. 2^44 = 17 592 186 044 416 possible CWs. Say, you have rate 2 000 000 CWs/sec, that'ss 8 796 093 seconds or 146 601 minutes or 2443 hours or 101,8 days :-(
Don't worry. We'll deal with the slack at the end if we haven't found the key.
 
Status
Not open for further replies.
Back
Top