Thanks bigjme. Is this Compute 3.5? I tried using your compile with my same old groestl bat file. The performance was worse. From 3100+ kh/s down to ~2450kh/s. You experiencing any difference?
on Windows this should now be built in four flavours, when done correctly

Compute 2.0 with #define MAXWELL_OR_FERMI 1 <-- Fermi
Compute 3.0 with #define MAXWELL_OR_FERMI 0 <-- old Kepler
Compute 3.5 with #define MAXWELL_OR_FERMI 0 <-- highend Kepler and GT630/640 with compute 3.5
Compute 3.5 with #define MAXWELL_OR_FERMI 1 <-- for Maxwell
the flag must be set in both .cu modules with "groestl" in its name. It affects
the speed optimization of the Groestl code.
at some point I will code a runtime selection of the MAXWELL_OR_FERMI flag.
Christian
I'm guessing the build bigjme made was for maxwell and that's why my 670 in the system is reporting crazy high hashrate, but is there a chance it's actually hashing between 1-2Mhash? lol (I normally run separate bat files but I just left it since it looks like I've missed the train on this one anyways)