NBCCCalc by money11465 - Page 3 - Overclock.net

pauldovi · 01-10-07

Quote:

Originally Posted by pauldovi

If there is a 800Mhz strap! All this is in theory. It has only been proven between the 1066Mhz strap and the 1333Mhz strap. Further testing on different motherboards and at different FSB must be done before we can generalize on straps at the 800Mhz, 1600Mhz, and beyond.

Quote:

Originally Posted by money11465

Once again, I am referring to the frequencies at which the straps occur rather than the sets of latencies themselves. So a DS3 user might be enjoying the set of latencies at 450FSB that a P5B user is stuck with at stock, or vice-versa. You can only compare straps on your board, and even so you must be careful as to which straps even exist.

Quote:

Originally Posted by money

You were saying that the straps are "in theory" and not yet proven, and I said I wasn't referring to the actual straps, only when they appeared. Close, but subtle.

But I guess we can agree pretty much.

I think you are a bit confused. We do not know when the FSB straps occur on all motherboards and at all frequencies. The only strap that we know exists is the 1066 and 1333Mhz strap on the P5B. And they only think we know about that is that it switches between the 1066Mhz and 1333Mhz strap at 400Mhz FSB. We also know that the 1066Mhz strap has lower latencies than the 1333Mhz strap, however, the 1333Mhz strap is more stable.

So you are referring to the frequencies at which they occur, but you do not know when they occur. You do not know what NBCC (FSB) triggers the change of strap on the DS3 or P5W. The only way to find that out is by testing memory bandwidth at different NBCC (FSB).

I was not referring to the latencies at all. It can be generalized that the latencies of a lower strap will always be less than the latencies of a higher strap.

Thus your NBCC Calculator cannot tell us what strap we are in. It can only tell us what NBCC value our overclock has. Experimental research can tell us where straps occur on different motherboards and you can add that into the program. Until then, your program cannot accurately determine straps.

money11465 · 01-10-07

Quote:

Originally Posted by pauldovi

I think you are a bit confused. We do not know when the FSB straps occur on all motherboards and at all frequencies. The only strap that we know exists is the 1066 and 1333Mhz strap on the P5B. And they only think we know about that is that it switches between the 1066Mhz and 1333Mhz strap at 400Mhz FSB. We also know that the 1066Mhz strap has lower latencies than the 1333Mhz strap, however, the 1333Mhz strap is more stable.

So you are referring to the frequencies at which they occur, but you do not know when they occur. You do not know what NBCC (FSB) triggers the change of strap on the DS3 or P5W. The only way to find that out is by testing memory bandwidth at different NBCC (FSB).

I was not referring to the latencies at all. It can be generalized that the latencies of a lower strap will always be less than the latencies of a higher strap.

Thus your NBCC Calculator cannot tell us what strap we are in. It can only tell us what NBCC value our overclock has. Experimental research can tell us where straps occur on different motherboards and you can add that into the program. Until then, your program cannot accurately determine straps.

Not when they occur, but the frequencies at which they occur if they even do. Straps do not necessarily change when my program say they do, but my program is able to tell you "There may have been a strap change. I recommend you do a mem. bandwidth test if you don't know if you have entered a new strap".

pauldovi · 01-10-07

Quote:

Originally Posted by money11465

Not when they occur, but the frequencies at which they occur if they even do. Straps do not necessarily change when my program say they do, but my program is able to tell you "There may have been a strap change. I recommend you do a mem. bandwidth test if you don't know if you have entered a new strap".

Quote:

Not when they occur, but the frequencies at which they occur if they even do.

You are saying the exact same thing. When they occur is the frequency at which they occur.

I never thought that your program changed NB straps. Estimation of strap change is okay, although somewhat foolish. However, you program does not label it as an estimation.

money11465 · 01-10-07

Quote:

Originally Posted by pauldovi

You are saying the exact same thing. When they occur is the frequency at which they occur.

I never thought that your program changed NB straps. Estimation of strap change is okay, although somewhat foolish. However, you program does not label it as an estimation.

Let me rephrase:
I am not claiming to know when the straps really occur, but when they would occur if they existed. And what's this whole thing about changing straps? Of course it can't change the straps.

pauldovi · 01-10-07

Quote:

Originally Posted by money11465

Let me rephrase:
I am not claiming to know when the straps really occur, but when they would occur if they existed. And what's this whole thing about changing straps? Of course it can't change the straps.

If they exist, how do you know what NBCC (FSB) they kick in at?

money11465 · 01-10-07

Quote:

Originally Posted by pauldovi

If they exist, how do you know what NBCC (FSB) they kick in at?

That's the point, I don't know, but common sense dictates (to me, maybe it's different for others) that there is a possible strap kicking in every 66FSB. So my program notifies you of a possible strap change.

EDIT:
I think it's natural that they kick in every 66FSB because that's what Intel set their CPUs to run at:
Some PDs: 133FSB
Better PDs: 200FSB
Conroes: 266FSB

pauldovi · 01-10-07

Quote:

Originally Posted by money11465

That's the point, I don't know, but common sense dictates (to me, maybe it's different for others) that there is a possible strap kicking in every 66FSB. So my program notifies you of a possible strap change.

There is a strap change on the P5B at 400Mhz but not at 466 or 333....

money11465 · 01-12-07

Quote:

Originally Posted by pauldovi

There is a strap change on the P5B at 400Mhz but not at 466 or 333....

Exactly, all boards are different. I am incorporating all frequencies at which it makes sense that a strap change MAY have happened. If the P5B doesn't have a strap change at 333 or 466, then ignore it. Other boards may. All my program is saying is: "Watch out, your strap may have changed".

pauldovi · 01-12-07

However, you information is highly misleading. The program does not say that. It says "You are on the following strap". Making a program that reports something that is inaccurate or wrong is not the best thing to do, and it can confuse a lot of people.

When I put 400Mhz FSB and a stock (9) multiplier in your calculator, it reports me as being on the 1600Mhz strap. This is untrue. I am on the 1066Mhz strap.

Quote:

My program refers to the straps by when they occur, not by the settings.

This makes little sense to me. What do you mean by when they occur, not by the setting. If the 266Mhz (1066Mhz) strap is moved to 400Mhz, then guess what. It is still the 1066Mhz strap. Your program is incorrect. It is plain and simple.

Quote:

You want to be on as low a strap as possible because higher straps mean higher latencies. However, FSB is still more important

This is not true either. 450Mhz FSB is slower than 400Mhz on a P5B.

money11465 · 01-12-07

Quote:

Originally Posted by pauldovi

However, you information is highly misleading. The program does not say that. It says "You are on the following strap". Making a program that reports something that is inaccurate or wrong is not the best thing to do, and it can confuse a lot of people.

When I put 400Mhz FSB and a stock (9) multiplier in your calculator, it reports me as being on the 1600Mhz strap. This is untrue. I am on the 1066Mhz strap.

Well, it might be nice if people read my post before downloading because it states:

Quote:

Also please note that most boards do not implement all of the straps yet, i.e. on the P5B-Deluxe only the 1066 and 1600 straps are in place, so any reported straps that are non-existent on your board are really the one below it (i.e. the 1333 strap is really still the 1066 on the P5B-Deluxe). Furthermore, you may notice that straps are "pushed forward" on some boards, for example the latency settings that should have occurred at 1333 occur at 1600.

		Overclock.net - Overclocking.net > Intel > Intel Motherboards
NBCCCalc by money11465

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)