The CDT and copywaza lab

I knew the parts were bad but trying got me no where. The system does not oc anymore, any clock/latency change from BIOS results in no change. It defaults to this now no matter what I do: http://valid.x86-secret.com/show_oc.php?id=268661

SetFSB gives me this now:
http://img57.imageshack.us/img57/8018/setle4.png

Sorry fellas. :(

This is what I meant by no or hardly any 1M change with major timings:

3600/540/5-4-4-5 39-7-13-12: http://img214.imageshack.us/img214/9...board06cp9.png
3600/540/5-4-4-4 39-7-13-12: http://img211.imageshack.us/img211/1...board07xu1.png
3600/540/4-4-4-4 42-6-16-12: http://img210.imageshack.us/img210/7...board08qu6.png / http://valid.x86-secret.com/show_oc.php?id=268660

All 3 times were 14.094s. Many others I saved are lost during system messup I just found out now when searching, even ran 4-4-4-3 and tRFC 35 and got the same time. Got a 14.000s with 450x8 1:1 4-4-4-4 funnily enough.

WHen did this turn into a RAM timings thread?
As ML said, just choose some settings that work on your system, then compare no tweak/CDT/CW which is what we are all interested in.

Anyhow, ive had Gigabyte boards doing that 'locked FSB' before, just pull out the battery and clear CMOS and you'll be back up and running.

Quote:

---

Originally Posted by KTE

Yeah, that's why I posted the initial results so someone can notice that the timing/sub-timing change is not giving me any difference in results. Negligble difference which is not what I expected and not what others I saw were getting, incl yourself. There's nothing wrong I'm doing other than what everyone does, it's a standard simple procedure, all things are constant, but I think it's hardware related...

Massman what CPU MHz/DDR MHz/latencies did you run those tests at? (so I can try them) I don't get those differences at all, no where near. :shakes:

---

MSI P35 motherboard, E2160 @ 360x9, 1GB 4:5. Booted at 5-5-5-15

Quote:

---

Originally Posted by T_M

WHen did this turn into a RAM timings thread?

---

When dinos said the times were quite slow and I showed I don't know how on earth guys say 4-4-4-4 PL6 gives you better times than 5-5-5-5 PF7 w/P35 because it doesn't on my setup, not even a millisecond.

Quote:

---

As ML said, just choose some settings that work on your system, then compare no tweak/CDT/CW which is what we are all interested in.

Anyhow, ive had Gigabyte boards doing that 'locked FSB' before, just pull out the battery and clear CMOS and you'll be back up and running.

---

Tried it long ago mate. No go. I think you can carry on the testings yourselves now.

Can someone post a 32M Pi score ran on XP Pro at 3550-3600/500-550 with or without LSC/Maxmem but definitely without any Copywaza or CDT please. Make it as good as you can without the above two tweaks if possible. It should be easy to replicate these high subtimings exactly.

http://img216.imageshack.us/img216/2833/settingsfk7.png


Just so that I know if its my software optimizations that are screwed or the tweak working.
BTW, ATi flacking drivers suck like crap! 35 too many BSODs has finally screwed my RAM over on the last BSOD:
http://img221.imageshack.us/img221/8...oard015cr9.png
http://img211.imageshack.us/img211/2440/memtest2ms1.jpg

After the last of ATi BSOD, memeory now gives massive errors. 4 days and new memory is dead. Worst of all its not even mine. :shakes: :censored: :cussing:

driver BSOD wont kill your memory.

Dead memory will be due to too much voltage or poor filter/regulation hardware on the board itself causing spikes on power-on/load(transient).

Power variations won't be the problem, the Seasonic is stable as hell 195W/550W max draw, DC primary and secondary filtering is excellent and neither will DIMM voltage since I ran 1.85V for 400/450, 2.1 for 500/550 and 2.3-2.35V for 600+ and the heatsink temp was 8C on average which is more than 15C cooler than stock in a case. I run Memtest every day at the end of use, and only on the day after repeated ATi CCC caused BSODs at 500/550 2.1V did it start giving memory/32M errors. Replacement will take a while now but funnily everything else but 32M Pi/Memtest works fine, even stress tests and intensive gaming.

Well......After ALL these pages AGAIN, do we have any news on this or not yet?...... :rolleyes:

Quote:

---

Originally Posted by hipro5

Well......After ALL these pages AGAIN, do we have any news on this or not yet?...... :rolleyes:

---

Read post #205, run that, but just for you, DO your best copywaza/tweaked time at those settings and post the 32M time. I'll reply to show if I have some CDT gains over copywaza or not. Otherwise there's a billion other who can be testing instead.

Quote:

---

Originally Posted by KTE

Read post #205, run that, but just for you, DO your best copywaza/tweaked time at those settings and post the 32M time. I'll reply to show if I have some CDT gains over copywaza or not. Otherwise there's a billion other who can be testing instead.

---

I'm NOT talking about YOU in personal if you took it that way...... :D
I'm talking in general about this thread..... ;) :)

Quote:

---

Originally Posted by hipro5

Well......After ALL these pages AGAIN, do we have any news on this or not yet?...... :rolleyes:

---

Nope, not yet :rolleyes:

hey guys, as i said i didnt have much time to follow this thread.
im really glad at how this thread stayed on topic, at least 90% of the time :)

i hope somebody can get the tweak working, atm it looks like only massmann, kte and t_m are trying to reproduce copy waza. so kte you got copy waza working but on a much older system? since your having problems with your new system, why dont you use skype or a webcam chat to guido somebody else through the cdt process?

Quote:

---

Originally Posted by KTE

Rather than keeping it hidden he spoke openly and tried to help everyone

---

i didnt see that yet but i hope we are getting there :)

Well, I don't think we need much more unsuccessful reports as there have been already plenty of them :( ... but if ya want, here's another one which I've compiled after literally days spent on all this... still can't wait for detailed reports from those who have been at least partially successful with CDT and compare them with my experience :)

System:

• CPU: E6600 B2 stepping
• Mobo: Asus P5K-E unmodded
• RAM: 2x1Gb Corsair 6400C3 (spd 3-4-3-9)
• Video: Asus X850XT (no drivers installed :D)
• HDD: WD 20Gb IDE for system, Samsung T166 500Gb for pagefile/Superpi
• Cooling: all air
• OS: WinXP SP2

Tweaks:

• OPB registry stuff (LSC, Prefetcher, Throttledualcore etc)
• Maxmem=600
• Pagefile=512Mb fixed
• no ERAM
• Services: all disabled/manual except RPC, Plug&Play & Themes (for Luna Silver)
• Priority=high from task manager
• Copywaza=CDT file (3x632Mb rared, have this from CDT testing :)) 3x times copy on itself in Superpi folder (you'll see it later in the pictures)...

The system layout is 2 partitions: C:\ (system) and F:\, pagefile of 512Mb exactly on F:\, Superpi folder on F:\ and copywaza (CDT) folder on F:\ as well, nothing more there.

Most of the services disabled:

http://img401.imageshack.us/img401/8...icesqh2.th.jpg

Taskmanager at fresh boot:

http://img98.imageshack.us/img98/654...bootsj2.th.jpg

Taskmanager processes on fresh boot:

http://img232.imageshack.us/img232/4...ocesac8.th.jpg

How the CDT file does look like (exactly 3x632Mb):

http://img239.imageshack.us/img239/4...fileyg7.th.jpg

Before running stock 32M:

http://img221.imageshack.us/img221/8...tockoj0.th.jpg

Stock 32M : 13m20.047s (default boot subtimings :) ):

http://img403.imageshack.us/img403/3...tockub9.th.jpg

Copywaza my way (copy of the big cdt file on itself in superpi folder, you can see the *.bat file used for that)

Taskmanager before the run:

http://img405.imageshack.us/img405/6...aza1na0.th.jpg

Result: 13m12.312s

http://img211.imageshack.us/img211/7...2mcwvn2.th.jpg

Now on to the CDT how it was described (like elmor & KTE @ XS were doing, again, I'm using a *.bat file for that, check it to see the copy sequence):
How the taskmanager looks after the tweak:

http://img231.imageshack.us/img231/7...cdt1wg5.th.jpg

The result, though, is slower than the copywaza I did :( 13m13.859s

http://img252.imageshack.us/img252/3...inalgk7.th.jpg

Now I tried a little different thing as well (from the pictures of applying the CDT tweak which were posted at the beginning of this thread), and managed to achieve very close balance :

http://img142.imageshack.us/img142/4...mentwf4.th.jpg

The result is half a second better than previously (which indicates that memory balance has to do something with 32M times, indeed ;) ), however, it still is a second slower than my copywaza run 13m13.484s :

http://img152.imageshack.us/img152/4...red1ms2.th.jpg

What can I add... running the original CDT 5times in a row raises the available memory and system cache by additional 10 Mb for me (can even achieve 569/571 balance in my case), however, for me this never translated to better 32M times.

KTE, I just switched my bench HDD to a faster one, hope I'll be able to give you a run with the timings you asked soon :)

I'll continue my testings when I've finished the P35 roundup review :)

Quote:

---

Originally Posted by hipro5

I'm NOT talking about YOU in personal if you took it that way...... :D
I'm talking in general about this thread..... ;) :)

---

I understood George. :D Just asking for some comparison times. CW does work on my C2D though. I tried it many times but hardware error and limits so can't do more yet.

Quote:

---

Originally Posted by saaya

so kte you got copy waza working but on a much older system?

---

Can get it working on the E6750, pretty well.

Quote:

---

since your having problems with your new system, why dont you use skype or a webcam chat to guido somebody else through the cdt process?

---

Don't use them where I'm staying. I hardly ever use MSN bro, let alone those. You won't find me that free to, I usually post from work after finishing all my tasks for the day, time is a major issue. Try doing two years of a science degree in one year and working 7 days a week along with it and you'll know why :p: :shakes:

Quote:

---

Originally Posted by mrlobber

KTE, I just switched my bench HDD to a faster one, hope I'll be able to give you a run with the timings you asked soon :)

---

Thank you mate. Look forward to it. :up:

Your CW/CDT difference looks the same as mine (mine was at lower clocks though) but that was a fudged run by me. If you don't have it done well through my experience you will get a 32M time 1-3 seconds slower than a 4GB copywazza. However, if you did it well, then it will be quicker than a very good CW by at least 2 seconds by my C2D experience.

ML, maybe you require some extensive pauses between the file copy processes in your .bat?
Like maybe 1 minute to be sure.

What would the .bat code be to do a pause?

Quote:

---

Originally Posted by T_M

ML, maybe you require some extensive pauses between the file copy processes in your .bat?
Like maybe 1 minute to be sure.

---

I don't think so... the CDT process states you need to wait those around 45 seconds only after all the CDT copying has been done, not between the steps. As far as I've gone with my testing, letting the system to be idle between the CDT steps turns the CDT into an ordinary not-so-good copywaza. If I'm not correct on this, feel free to turn my attention to it :)

Btw, yesterday it just became more mysterious... I switched to 2 identical HDD's (Seagate 160Gb SATA 8Mb, previously it was 20Gb IDE for system and 500Gb 2nd HDD), and guess what... the CDT 32M time improved by ~0.6 secs (first time I got below 13m13s with CDT and the configuration I described above) while my copywaza time - only by 0.2 seconds :shrug: This means additional testing again :cool:

KTE, I did a run with your timings, but haven't taken the screenshot with me. The stock time (with tweaked Windows, no copywaza, no CDT) was, if I remember properly, around 13m33s.

Quote:

---

Originally Posted by mrlobber

Btw, yesterday it just became more mysterious... I switched to 2 identical HDD's (Seagate 160Gb SATA 8Mb, previously it was 20Gb IDE for system and 500Gb 2nd HDD), and guess what... the CDT 32M time improved by ~0.6 secs (first time I got below 13m13s with CDT and the configuration I described above) while my copywaza time - only by 0.2 seconds :shrug: This means additional testing again :cool:

---

Having two HDDs, new, same ones made a gain to my results too! :)

Quote:

---

KTE, I did a run with your timings, but haven't taken the screenshot with me. The stock time (with tweaked Windows, no copywaza, no CDT) was, if I remember properly, around 13m33s.

---

Cheers. Try doing a CW run now please and let me know the time and frequencies used. :up:

mrlobber: forgot to throw in one major edit. Use 8 multi please because my setup can't do that FSB at 1:1. :)

KTE: I can post that time but please be more specific. I can run for example LSC=1, 9x400, PL=6 or 7 if you wish, RAM @ 500 and your timings

Quote:

---

Originally Posted by kiwi

KTE: I can post that time but please be more specific. I can run for example LSC=1, 9x400, PL=6 or 7 if you wish, RAM @ 500 and your timings

---

Yep, these settings exactly. I would prefer if you could replicate 450x8 DDR:540 if you can and you can use Maxmem/LSC/CW and so on... but not CDT, so that I can differentiate. Thanks. :)

Quote:

---

Originally Posted by mrlobber

I don't think so... the CDT process states you need to wait those around 45 seconds only after all the CDT copying has been done, not between the steps. As far as I've gone with my testing, letting the system to be idle between the CDT steps turns the CDT into an ordinary not-so-good copywaza. If I'm not correct on this, feel free to turn my attention to it :)

Btw, yesterday it just became more mysterious... I switched to 2 identical HDD's (Seagate 160Gb SATA 8Mb, previously it was 20Gb IDE for system and 500Gb 2nd HDD), and guess what... the CDT 32M time improved by ~0.6 secs (first time I got below 13m13s with CDT and the configuration I described above) while my copywaza time - only by 0.2 seconds :shrug: This means additional testing again :cool:

KTE, I did a run with your timings, but haven't taken the screenshot with me. The stock time (with tweaked Windows, no copywaza, no CDT) was, if I remember properly, around 13m33s.

---

M8......ACCORDING to this "CDT Tweak" you HAVE to see MORE than 10sec dropping out of it.....;):p:

I mean that IF you have - for example - 13.13m with the Copy Waza, when you apply the "CDT Tweak", you MUST SEE 13.03m......THAT'S the time difference you SHOULD see according to OPB..... ;)
.......and you are talking about 0.6sec.....!........Give me a break...... :D :p:

Quote:

---

Originally Posted by hipro5

M8......ACCORDING to this "CDT Tweak" you HAVE to see MORE than 10sec dropping out of it.....;):p:

---

People can't get upstairs without taking the first steps, so let's consider these small differences being those steps ;) :D

Quote:

---

Originally Posted by mrlobber

People can't get upstairs without taking the first steps, so let's consider these small differences being those steps ;) :D

---

OK......At least give us ONE step at a time....for example ~ 3sec difference and then the rest 10sec difference.....
DON'T just move your feet a bit upwards coz you'll never reach the next step..... :D

There's certainly more to this CDT tweaking than has been described in this thread. Thats for certain after having spent time on MSN with OPB.

Quote:

---

Originally Posted by hipro5

OK......At least give us ONE step at a time....for example ~ 3sec difference and then the rest 10sec difference.....
DON'T just move your feet a bit upwards coz you'll never reach the next step..... :D

---

Now what happens if you or any other members here dont get a 10sec improvement?