Recent content by Tetedeiench

Indeed, that's what i'm going to do. Changing screen causes a few frames to be half-rendered, and thus OCCT counts that as errors. I have a few updates to the FAQ i need to do, i'll include it today. Thanks for the report ! EDIT : FAQ was updated a few seconds ago.

Still going through 1.1.1 betas... I don't have alot of time to program these days. And there's something big that just started cooking... I'm sure you're going to like it. It's going to take a while to program though !

Thanks :) b01 had a problem with everest monitoring, so i released b02 yesterday. It also fixes a problem when loading the settings with Core Temp enabled, and removes extra spaces in CPU names, motherboard, and such... http://www.ocbase.com/OpenBeta/OCCTPT1.1.1.b02.zip

:D :D

I can give it a shot. There's however a problem with those softwares that doesn't provide a shared memory : i have to scan the whole window, getting all the strings out of it, and then select the right ones and make them into OCCT. Asus probe support was relly really tricky. in fact, with...

Ah yes :D The message you have seen is as follows : "OCCT detected that you closed Speedfan. You shouldn't do it. OCCT will now terminate. Bye. Never do it again while OCCT is running. It's a weird idea anyway. It's because of such silly ideas that we, programmers, have such hard work trying...

OCCT with advertisements ? What do you mean ? OCCT doesn't come with ads of any sort... As for the bug, i can't reproduce it here... what exactly were you doing ? If you did close coretemp, this message is normal (i just forgot to replace "speedfan" by "CoreTemp").

It's possible, but OCCT and orthos are not designed to be real-tough CPU heaters... they DO load the cpu, make it generate heat more than alot of programs out there, but as there's error checking, it will never be as tough as others like Intel TAT, for instance.

I promised it, there it is :) OCCT PT 1.1.1.b01 : Core temp support (make sure it is running before selecting it in OCCT) and chinese support : http://www.ocbase.com/OpenBeta/OCCTPT1.1.1.b01.zip

IMHO, yeah, you're pretty set here ;) I do think 8 hours of OCCT is more demanding than 8 hours of Orthos.

As it is random, it is really hard to say... it doesn't multiply or add at all... So i really can't tell you... One test showed OCCT being 10times faster (yeah, 10 times), another showed OCCT being twice faster, another showed OCCT equal to orthos, ... and so on.

Having a program stating that your CPU is 100% stable will never exist. As i said, those errors are random, and thus, even if you ran OCRTorthosPrimeSuperPI2010 for 10 days you could not be 100% sure your CPU is stable. There are just, as previously said, levels of stability, and OCCT is...

Error generation is random, that's why. What i do is just make those errors likely to happen... however, sometimes it will fail sometimes not. But as soon as one error is detected, you can be 100% sure there had been a problem :D

I'm pretty sure (even if not 100% sure), that running both tests at the same pretty much going to hinder OCCT's capability to detect computing errors... I do not really recommend it ;) I don't have enough test data to be 100% sure about that, but it's a enlightened guess i am doing :)

i'm sure OCCT would have detected something in 1hour or so ;) Remember you can customize OCCT to run for much longer. The 30 min test is usually good for almost all cases, to get a quick idea, but having orthos fail after one hour and a half means a "on the edge of stability" overclock, and...