Testing V 7.00

[coolstream]

I think you are right, Fred. I think it most likely that (the lack of) UDMF is the elephant in the room.

The offer of a remote Vista machine still stands if you wish to do any pre-beta testing.

[fred]

I tested the new 7.002 on an XP 32 machine and it installed properly.
This version now has a separate  XP and W7 driver, 4 drivers actually

[idahofisherman]

7.002 now works on my vista machine.  Thanks.

[coolstream]

Good job on the second update.

I have been busy over weekend and have only just tried the new version. For some strange reason, I still can't get it to work on a Vista machine. I'll try again when I have more free time.

I have noticed a few minor points whilst testing the install:

typo. Installer says

This will install TThrottle (32/64 Bit): Temperature Throttle by eFMer V 7.0.0.1 on your computer

should be V 7.0.0.2

also shows as 7.0.0.1 | in Control Panel | Programs |

In Remove Driver dialog, msg reads

Driver removed! (If you see any errors the driver way already removed or not running)

'way' should be 'was'

'Install Driver' dialog still reports that driver cannot be installed because INF file is missing

Microsoft Windows Vista Ultimate Edition Service Pack 2 (build 6002), 64-bit
-------------------------------------------------------------------------
Installer 64 Bit V1.40
StartService failure! Error = 127 (start driver)
Unable to install driver. (is the .inf file present?)
ControlService failed!  Error = 1062
ERROR: Driver not installed properly. (LoadDriver Dlg)

[fred]

Good job on the second update.

I have been busy over weekend and have only just tried the new version. For some strange reason, I still can't get it to work on a Vista machine. I'll try again when I have more free time.

I corrected the installer version.
Download it again to be absolutely sure you got version 2.
While installing check for the message XP driver.

[coolstream]

I corrected the installer version.
Download it again to be absolutely sure you got version 2.

v7.0.0.1 for comparison with the 7.0.0.2 versions:
CRC32: CF511F19
MD5: E03D9B466B355D516F5E0C2F9470D393
SHA-1: 6519166C22BCBA42B6B1B640BE64471F28878951

v7.0.0.2 downloaded previously:
CRC32: 86FE7714
MD5: DF2DEA9F77748910297B617DA4647CD6
SHA-1: A58D2F732CCDD47E5B5F5E1882C3CB119231284D

v7.0.0.2 downloaded from Europe server:
CRC32: DDAFE44F
MD5: 843EE7DE0B7D2223D5A9A337CBB3000A
SHA-1: 6285B590FF09F3AC0C1C94F85361F13576517259

v7.0.0.2 downloaded from America server:
CRC32: DDAFE44F
MD5: 843EE7DE0B7D2223D5A9A337CBB3000A
SHA-1: 6285B590FF09F3AC0C1C94F85361F13576517259

file hashes created with hashtab

The 7.0.0.2 version I had downloaded previously appears to be different to the ones I now have, but comparing it with 7.0.0.1, it would appear that you have indeed uploaded a new version with the same name!
REQUEST: It might be a useful addition to include a file hash on the download page 

Now for the bad news, I have tried installing 7.0.0.2 over 7.0.0.1 (and over 6.5.0) and also have done a complete uninstall before reinstalling 7.0.02. No matter whatever method I have used, I still can't get 7.0.0.2 to perform. The log always says that driver is not properly installed. ⁽¹⁾

I have also tried your earlier suggestion of using InstallDriver64.exe to uninstall and reinstall driver but the reinstall process always reports that a required INF file is missing.

Mixed good and bad news:Over the past few days, I have been building two new systems (one Vistax64 sp2 and one Win7x64 sp1).  Both systems are fully up to date with all Microsoft recommended updates and are running Norton Internet Security 2013 (fully updated). I have also deployed an XP machine (with all updates made). The Win7 and XP machines both work with 7.0.0.2, however this new Vista machine does not.

It's strange that idahofisherman reports that 7.0.0.2 works on Vista whilst neither of my Vista systems can get it to report core temps whilst they are happy running v6.5.

⁽¹⁾ Vista machine running TThrottle 7.0.0.2:

27 June 2013 - 16:03:11 Driver not loaded (yet?), retry in 10 seconds
27 June 2013 - 16:03:21 Driver not loaded (yet?), retry in 10 seconds. (2)
27 June 2013 - 16:03:31 OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
27 June 2013 - 16:03:31 (L01) ERROR: Driver NOT installed properly27 June 2013 - 16:03:31 Program version: 7.00,64Bit
Microsoft Windows Vista Ultimate Edition Service Pack 2 (build 6002), 64-bit
Language: User: 2057 (ENG), System: 2057 (ENG), Selected: 0 () Used: 1033 (ENU)
Amd/Ati: found 1 devices
Amd/Ati: AMD Radeon HD 7900 Series Present (Pos: 0, Valid adapter: 0)
27 June 2013 - 16:03:31 AdapterInfo: Pos: 0, Valid adapter: 0, Index: 0, AMD Radeon HD 7900 Series
Pos: 0, Temperature: 40

Vendor ID: GenuineIntel
Vendor ID: INTEL
HighestIntegerValue: 0000000B - Processor Signature: 000206C2
Misc. info: 02200800
Feature Flags1 029AE3BF
Feature Flags2 BFEBFBFF

Processor: Intel(R) Core(TM) i7 CPU         970  @ 3.20GHz               
Processor: Family: 6h, Model: 2C, Stepping: 2

TJunction using: 100  °C


BOINC:
www.worldcommunitygrid.org

You can help by reading www.efmer.eu/boinc/faq.html How can I help!
Select the send EMail button,or copy everything in this logging window and mail it to me!
boinc[At]efmer[Dot]eu. We use this information to improve this product.

27 June 2013 - 16:03:42 Number of matching Programs (Processes): 12
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 20576, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 5740, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 25560, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 24508, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 13036, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 23212, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 11868, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 21812, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 9984, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 24656, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 24244, Threads: 3
CPU: wcgrid_faah_7.15_windows_x86_64, PID: 8404, Threads: 3
---------------------------------------------------------------------------------------------------------------------   12 0 0 0
27 June 2013 - 16:03:42 Connected with BOINC client
27 June 2013 - 16:03:42 Number of matching Programs (Processes): 12

Vista machine running TThrottle 7.0.0.2:

[fred]

Vista machine running TThrottle 7.0.0.2:

XP 32 bit working. XP 64?
Vista 32 bit working. 64 bit inconclusive.
Win 7 32/64 working.

I will setup a test machine with Vista 64 bit, to see if this a reproducible problem.

[fred]

REQUEST: It might be a useful addition to include a file hash on the download page 

As I made a too quick test build.... The exe itself is protected by a certificate, so if the version in the setup read correct, you have the right file.

[coolstream]

I see your reply to my unedited version. I was in the midst of correcting typos, so I hope it is clearer now.

I will setup a test machine with Vista 64 bit, to see if this a reproducible problem

I look forward to your findings. To save time, the offer of remotely running one of my Vista boxes still stands.

[fred]

You can help by looking here: C:\Windows\inf

Search for cputemperature in:

setupapi.app.log
and
setupapi.dev.xxxxxxxxxxxxxx.log the xxxxx are a number.

[coolstream]

You can help by looking here: C:\Windows\inf

Search for cputemperature in:

setupapi.app.log
and
setupapi.dev.xxxxxxxxxxxxxx.log the xxxxx are a number.

setupapi.app.log: Cannot find "cputemperature"
there is no setupapi.dev.xxxxxxxxxxxxxx.log file, but there are 3 setupapi.ev files

setupapi.ev1, setupapi.ev2 and setupapi.ev3 apart from having incomplete names all appear to be corrupted when compared to the same file on a working Win7 system.

Would you like to see them anyway?

[coolstream]

I have uploaded the three files to my skydrive but the fact that there are 3 'corrupted' files seems sinister to me.

To clarify:
My previous post related to a Vista system with v7.0.0.2 installed but not working.
On the other Vista system with attempted install and then subsequently 6.5 installed, the 3 .ev(x) files exist but there are also the two files you asked about (but from the subsequent install of 6.5)

[fred]

Go here: C:\Program Files\eFMer\TThrottle
And delete *.inf and *.sys.

And here: C:\Windows\System32\drivers
Delete: cputemperature.sys

Install everything again.

[coolstream]

OK. TThrottle stopped and the inf and sys files removed as per your instructions. TThrottle 7.0.0.2 reinstalled as Administrator. Temps still not being captured with the following log:

29 June 2013 - 07:09:40 Driver not loaded (yet?), retry in 10 seconds
29 June 2013 - 07:09:50 Driver not loaded (yet?), retry in 10 seconds. (2)
29 June 2013 - 07:10:00 OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)

Have you been able to replicate this?

[fred]

OK. TThrottle stopped and the inf and sys files removed as per your instructions. TThrottle 7.0.0.2 reinstalled as Administrator. Temps still not being captured with the following log:

29 June 2013 - 07:09:40 Driver not loaded (yet?), retry in 10 seconds
29 June 2013 - 07:09:50 Driver not loaded (yet?), retry in 10 seconds. (2)
29 June 2013 - 07:10:00 OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)
OpenService failed!  Error = 1060 (start driver)
Unable to start driver. (is the driver installed?)

Have you been able to replicate this?

Yep. My guess it's a bug in Vista 64.
But the problem is resolved by using the older 2.4 driver.
2.5 only has one item for W7 and up, for better core detection.

This is probably the best test version on this side.

This probably means that 2.4 is the last < W7 driver.