CudaBiss 2.5
My computer is equipped with two video cards, gt730 + 1050ti. I want to run with 1050ti. Can I set the software?
Why is it so difficult
- Thread starter bh62549
- Start date
- Status
My computer is equipped with two video cards, gt730 + 1050ti. I want to run with 1050ti. Can I set the software?
I do not think cudabiss 2.5 was ever released,I think 2.0 was last public version and 2.2 last private version.
It was never open source to begin with,and development stopped over 10 years ago.
This from readme
********************""
Cudabiss user guide v 2.02
Cudabiss22464 and Cudabiss44864 are intended for GTX460/465/470
Cudabiss24064 and Cudabiss48064 are intended for GTX480/570
Cudabiss25664 and Cudabiss51264 are intended for the GTX560
(the different versions will work on all cards though)
Release history:
v2.02
-more modes
v2.01
-more speed in modes 1,7 & 9
********************************************************
v2.2 has added more search modes,so you have like 15 different ways to search for keys,if your version can do those extra modes then you have it,but it was private at some point.
Again,I might be outdated with this info,since some development was done and test versions were compiled and shared through private MIRC channels,and I was not always there.
The version 2.5 I see in youtube is a GUI that apparently do not have more than one ALL KEYS search more,but who knows,maybe you can edit the input.txt file to use different modes,and still you need the original README in order to understand how to use them.
It was never open source to begin with,and development stopped over 10 years ago.
This from readme
********************""
Cudabiss user guide v 2.02
Cudabiss22464 and Cudabiss44864 are intended for GTX460/465/470
Cudabiss24064 and Cudabiss48064 are intended for GTX480/570
Cudabiss25664 and Cudabiss51264 are intended for the GTX560
(the different versions will work on all cards though)
Release history:
v2.02
-more modes
v2.01
-more speed in modes 1,7 & 9
********************************************************
v2.2 has added more search modes,so you have like 15 different ways to search for keys,if your version can do those extra modes then you have it,but it was private at some point.
Again,I might be outdated with this info,since some development was done and test versions were compiled and shared through private MIRC channels,and I was not always there.
The version 2.5 I see in youtube is a GUI that apparently do not have more than one ALL KEYS search more,but who knows,maybe you can edit the input.txt file to use different modes,and still you need the original README in order to understand how to use them.
Last edited:
As I said before,after 2.0 I think there was not another public version,and after that is was private releases only.
While its been dead for 10 years,I chose not to release private versions given to me in confidence by the author.
I can't say any of the trusted people at the time might have made it public,no way to know.
I think 2.0 is latest made public,that one should be available.
The newer modes might not benefit much unless you are an expert searcher,and is clear most people today would not need those modes much.
And the latest cards optimized in cudabiss are not even close to what we are using today,so no real improvements.
vakula
Super VIP
- Messages
- 6,238
Stefan2k16
Registered
- Messages
- 44
To really effectively use Cudabiss, you needed multiple video cards, like maybe at least 4 or 8 cards. And to get that many cards in one system you needed some sort of PCIE expansion systems. By then your generating lots of heat and noise, so, it's best to have a small building out in your backyard to house the system. Basically, look at something like the cryptocurrency miners used to build, back in the days when cryptocurrency mining on GPUs was profitable. Even then, it could take several hours to find a key, sometimes even a day or 2.
If there was a particular feed you were familiar with and you noticed certain patterns to the key selection, you could sometimes use those "modes" to significantly reduce the time.
If there was a particular feed you were familiar with and you noticed certain patterns to the key selection, you could sometimes use those "modes" to significantly reduce the time.
100.5E UFC
100.5E It's very unlikely that the UFC signal on can find C8. I try to record it 2.5G Files can't find a valid C8, who has a better way?
TS file: D:\TS\100.5E 3915 V 05-17 07-49-36.ts
Using all PIDs
Using file limit: 4096 MByte
File length: 2541 MByte
UsingFileLen: 2665424896 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 65h B8h-Crypt8:11 4B 9C 94 62 8D 4A 80 [E] Count:3
PID: 65h B8h-Crypt8:24 0E 1D 29 BE 59 79 AE [E] Count:2
PID: 65h B8h-Crypt8:52 AB 74 C3 1A F6 F3 51 [E] Count:2
PID: 66h B8h-Crypt8:A8 B2 6E 21 E2 DA 1F 69 [E] Count:188
PID: 66h B8h-Crypt8
5 E5 A8 72 E8 B1 28 EF [E] Count:186
PID: 66h B8h-Crypt8:B6 15 5B 0C 84 72 DF 7B [E] Count:171
PID: 66h B8h-Crypt8:AA 09 F7 D2 AD A2 C2 9C [E] Count:164
PID: 66h B8h-Crypt8:5A 75 FD 58 2F 22 02 20 [E] Count:148
PID: 66h B8h-Crypt8:12 E4 13 6D DA 38 F3 DA [E] Count:144
PID: 66h B8h-Crypt8:20 71 E9 B7 CE 2D 83 2A [E] Count:125
PID: 66h B8h-Crypt8:1C E7 B2 87 69 F7 84 54 [E] Count:116
...
Time for searching Crypt8 = 8 sec.
Search CW Start
RBT file: G:\B8hxFFh V1\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 149931 possible chains (harddisk only search time = 239 sec.)
Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
CW not found
It seems you need a bigger RBT
Search CW done (366 sec.)
Search CW Start
RBT file: G:\B8hx030000h V1\CSA_B8hx030000h_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 149105 possible chains (harddisk only search time = 240 sec.)
Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
CW not found
It seems you need a bigger RBT
Search CW done (370 sec.)
100.5E It's very unlikely that the UFC signal on can find C8. I try to record it 2.5G Files can't find a valid C8, who has a better way?
TS file: D:\TS\100.5E 3915 V 05-17 07-49-36.ts
Using all PIDs
Using file limit: 4096 MByte
File length: 2541 MByte
UsingFileLen: 2665424896 bytes
Reading file ...
Searching ...
Using payload size: 184
PID: 65h B8h-Crypt8:11 4B 9C 94 62 8D 4A 80 [E] Count:3
PID: 65h B8h-Crypt8:24 0E 1D 29 BE 59 79 AE [E] Count:2
PID: 65h B8h-Crypt8:52 AB 74 C3 1A F6 F3 51 [E] Count:2
PID: 66h B8h-Crypt8:A8 B2 6E 21 E2 DA 1F 69 [E] Count:188
PID: 66h B8h-Crypt8
5 E5 A8 72 E8 B1 28 EF [E] Count:186PID: 66h B8h-Crypt8:B6 15 5B 0C 84 72 DF 7B [E] Count:171
PID: 66h B8h-Crypt8:AA 09 F7 D2 AD A2 C2 9C [E] Count:164
PID: 66h B8h-Crypt8:5A 75 FD 58 2F 22 02 20 [E] Count:148
PID: 66h B8h-Crypt8:12 E4 13 6D DA 38 F3 DA [E] Count:144
PID: 66h B8h-Crypt8:20 71 E9 B7 CE 2D 83 2A [E] Count:125
PID: 66h B8h-Crypt8:1C E7 B2 87 69 F7 84 54 [E] Count:116
...
Time for searching Crypt8 = 8 sec.
Search CW Start
RBT file: G:\B8hxFFh V1\CSA_B8hxFFh_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 149931 possible chains (harddisk only search time = 239 sec.)
Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
CW not found
It seems you need a bigger RBT
Search CW done (366 sec.)
Search CW Start
RBT file: G:\B8hx030000h V1\CSA_B8hx030000h_10000h.rbt
Calc all 10000h end values for this crypt ... (using file cache)
Search end values in RBT ...
Searching CW in RBT ...
Found 149105 possible chains (harddisk only search time = 240 sec.)
Analysing chains ... (will be 10 times slower if an other thread is keeping the GPU busy)
CW not found
It seems you need a bigger RBT
Search CW done (370 sec.)
Ratzvan
Feed Hunter
- Messages
- 22,693
I found your last umpteenth thread a bit redundant because you've already opened more similar threads in the past
So I collected more posts here.
I'm giving here a definitive answer, because it seems you can't understand problem.
Not always is possible to find CW with C8 methods and rainbow tables.
Feed can be arranged to give fake c8 (as the ones you posted) and you can save the bigger file you can, but untill that fake flux ends you couldn't find a good c8.
As already said luckly there are other methods.
1) CW LIST ATTACK
Many feeds have an known cw, already posted in the past. So just keeping a good old cw list updated can help finding a high number of cw by cw_list attack. Then many feeds have a same model pattern where only date inside change. I saw yesterday you posted feed/cw for Korea league, possibly found by C8 I guess
Well, it could "more easily" be found with a cw_list attack method if your list included the daily possible combination for Korea league fix pattern (ABCDMMDDAB01, where MM=month , DD=day
and last byte always increasing of one point if there are more matches during the day)2) Receiver method. As already said there are receivers that can do the same work for you (and I indicated already two methods: "so said "au biss" and dvbfinder ), where reference is always -> https://www.sat-universe.com/showthread.php?t=224549
3) BRUTE FORCE METHOD. This not particularly intended here as a complete brute force (where many time is requested), but a targeted one.
It needs knowledge about feeds and awareness if this one can be used in that particular situation. There are feeds that have many zero byte insideand only some numerical bytes and others where when feed appears only one/two bytes inside have changed since the last time
I think we've said everything about this stuff, so I'm closing this thread. For other more specific requests please relate to others already opened thread.
Thanks
- Status