v62 is up

[Rolf]

Nope, the latest NV WHQL drivers for Windooze are 301.42.

[blandyuk]

Graph updated with v0.09b74 (see attached).

[atom]

Nope, the latest NV WHQL drivers for Windooze are 301.42.

what does that mean?

[atom]

b75 is up!

@mastercracker: i guess all passwords were found, right?
@Rolf : whats the problem with NV WHQL drivers for Windooze are 301.42?
@malik: pls update performance table
@malik: will try -m 3000 anomalies later
@proinside: did the driver update help?
@ati6990: WTH does that all mean. do i need to do any additional change to DES?

@all: are we good for release?

[Rolf]

If you release it, then windows users will need to install beta drivers to use pluscat, which kinda suck.

[mastercracker]

b75 is up!

@mastercracker: i guess all passwords were found, right?
@Rolf : whats the problem with NV WHQL drivers for Windooze are 301.42?
@malik: pls update performance table
@malik: will try -m 3000 anomalies later
@proinside: did the driver update help?
@ati6990: WTH does that all mean. do i need to do any additional change to DES?

@all: are we good for release?

I did not do a full recheck yet but I have checked if the bugs I reported were fixed and they were. Technically, all the passwords should be found now. For Nvidia, I will check with my GTX460. I remember when I tested earlier on it gave some bugs that were different from GTX470.

[atom]

If you release it, then windows users will need to install beta drivers to use pluscat, which kinda suck.

OK, but better this way than to distribute oclHashcat-plus binaries that base on CUDA 4.2.9. Problem with that is that when you have 304.x on Linux, they do not support < CUDA 5.0. That would force linux users to use an old driver. So my conclusion is better force windows users to use beta driver (and in some time whql driver) than to force linux users to use old drivers till next oclHashcat-plus update.

[Rolf]

I'd say hold your horses till NV releases WHQL, then make a shiny pluscat release, but you're the boss Atom.
I am not using pluscat because of those lousy beta drivers for a month or so, so I dont really care.

[M@LIK]

Re-tested after increasing --gpu-loops.

Code:

1 Million MD5s:
0.08:.............165.4M
0.09b75:..........171.1M
0.09b75(len_9):...171.2M
RESULT: 0.09 wins!

25k MD5s:
0.08:.............203.5M
0.09b75:..........203.6M
0.09b75(len_9):...203.5M
RESULT: 0.09... wins!

10 MD5s:
0.08:.............227.7M
0.09b75:..........267.8M
0.09b75(len_9):...228.3M
RESULT: 0.09 wins...
Command-line example: hc64p -n320 --gpu-loops=1024 -a3 --bf-min=9 --runtime=20 10fakemd5.hash ?a?a?a?a?a?a?a?a?a