NBCCCalc by money11465 - Page 4 - Overclock.net

pauldovi · 01-12-07

Quote:

Originally Posted by money11465

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

But you are wrong! You are wrong in your example, and you are wrong in general.

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.

This is not true. It is the 1066Mhz and the 1333Mhz straps that is known to exist. Not the 1600Mhz strap.

I think straps need to be explained in another way to you. The speed that we refer to the strap as (i.e. 1066Mhz or 1333Mhz) is a name which is attached to a series of latencies. The NBCC (or FSB) that the strap occurs in has nothing to do with the name.

I am looking for a explanation on XS to show you... But their forum is down.

money11465 · 01-12-07

Quote:

Originally Posted by pauldovi

But you are wrong! You are wrong in your example, and you are wrong in general.

This is not true. It is the 1066Mhz and the 1333Mhz straps that is known to exist. Not the 1600Mhz strap.

I think straps need to be explained in another way to you. The speed that we refer to the strap as (i.e. 1066Mhz or 1333Mhz) is a name which is attached to a series of latencies. The NBCC (or FSB) that the strap occurs in has nothing to do with the name.

I am looking for a explanation on XS to show you... But their forum is down.

That's my point. I am NOT trying to explain straps according to the latencies they are attached to. I am calling them by when they kick in, and if they don't happen to exist on your board (or in general) then ignore them. I also said in my first post that all boards are different, so the strap that kicks in AT 1600 on the P5B may have different latencies than one that kicks in AT 1600 on the P5W DH. Now I am not claiming to know the strap arrangement on the P5W, I am just using it as an example.

Intervention · 01-12-07

[QUOTE=pauldovi;1632871]But you are wrong! You are wrong in your example, and you are wrong in general.
QUOTE]

Thats a nice way to say it Paul, try not to sugar coat it like that next time. Lol

My understanding of it is that Asus pushed back the 1333 strap to 400fsb / 1600mhz speed, am I correct? Therefore sort of eliminating the 1333 strapm, leaving you with proven straps of 1066 and 1333@1600. I wonder if there is a 1600 strap, were it ends at, maybe 2000Mhz????

pauldovi · 01-12-07

Quote:

Originally Posted by money11465

That's my point. I am NOT trying to explain straps according to the latencies they are attached to.

What is the point of it then. Why are you going to describe something, and ignore their purpose? Why are you going to tell people something that is wrong and make it seem correct?

Quote:

so the strap that kicks in AT 1600 on the P5B may have different latencies than one that kicks in AT 1600 on the P5W DH.

I never once asked you to report what the latencies values were, or how there latencies relate to other boards.

Quote:

I am calling them by when they kick in

You are still missing the point. You are reporting every 66Mhz of FSB as being a change in NB strap. This is wrong, this is incorrect, this is misleading. Every 66Mhz of FSB does not result in a NB strap change. This is not where they kick in.

Quote:

and if they don't happen to exist on your board (or in general) then ignore them.

No, I think you have that backwards. If something doesn't happen in general, they you get rid of it in your program.

Quote:

I also said in my first post that all boards are different

This is the exact reason that you cannot use your program to report straps. Because they are different on all motherboards!

Quote:

Originally Posted by Intervention

Thats a nice way to say it Paul, try not to sugar coat it like that next time. Lol

My understanding of it is that Asus pushed back the 1333 strap to 400fsb / 1600mhz speed, am I correct? Therefore sort of eliminating the 1333 strapm, leaving you with proven straps of 1066 and 1333@1600. I wonder if there is a 1600 strap, were it ends at, maybe 2000Mhz????

Sorry Intervention, I do not sugar coat anything. I will give you the straight facts. Euphemisms are for politicians. I don't know how else you want me to work it.

money11465 · 01-12-07

Quote:

Originally Posted by pauldovi

What is the point of it then. Why are you going to describe something, and ignore their purpose? Why are you going to tell people something that is wrong and make it seem correct?

I am NOT trying to explain straps according to the latencies they are attached to. I am explaining them according to where one may kick in. And about the purpose, while it is true that they were made to keep the NB stable, we (as a community) try to make sure they don't hinder our performance. So we need to know when we should watch our Pi times to see if a strap did kick in.

Quote:

I never once asked you to report what the latencies values were, or how there latencies relate to other boards.

And that's why I didn't. BTW, it's their, not there.

Quote:

You are still missing the point. You are reporting every 66Mhz of FSB as being a change in NB strap. This is wrong, this is incorrect, this is misleading. Every 66Mhz of FSB does not result in a NB strap change. This is not where they kick in.

Once again, I am NOT saying that every 66FSB will result in a strap change. I a saying that it is possible, and you should watch your bandwidth when it is possible.

Quote:

No, I think you have that backwards. If something doesn't happen in general, they you get rid of it in your program.

When processors (namely FSB) get faster, for example with DDR3, more straps will be implemented. This is a relatively new issue whose specifics are not known about very well.

Quote:

This is the exact reason that you cannot use your program to report straps. Because they are different on all motherboards!

I am not asking you to compare motherboards. I will say this again:
Straps may be different on different motherboards, the only thing that is the same across all boards is when there is a possibility of a strap kicking in. Notice I said a strap, not the so-and-so strap.

And finally, if you don't like my feature you can either write your own NBCC calculator and use that or I can make a Pauldovi version without strap reporting. Go ahead and choose.

pauldovi · 01-12-07

Quote:

So we need to know when we should watch our Pi times to see if a strap did kick in.

Quote:

I a saying that it is possible

Quote:

Straps may be different on different motherboards, the only thing that is the same across all boards is when there is a possibility of a strap kicking in.

The problem with your program is that it is not doing what you are saying it is doing. You keep on referring to possibilities. However, you program suggests certainty:

I don't know if you noticed, however, your program says:

Quote:

You are on the following strap

That implies certainty. You said "You are". Know someone who downloads this program, typed in their info and gets a readout that says "You are" on this strap, guess what. They are going to take your little program for granted and think that they are ON that strap. However, they are not.

Your program reports incorrectly in terms of the P5B for all values between
1Mhz FSB through 266Mhz FSB and 333Mhz FSB through 625Mhz FSB.

You are supplying a program with incorrect information. It is very plain.

money11465 · 01-12-07

Quote:

Originally Posted by pauldovi

The problem with your program is that it is not doing what you are saying it is doing. You keep on referring to possibilities. However, you program suggests certainty:

I don't know if you noticed, however, your program says:

That implies certainty. You said "You are". Know someone who downloads this program, typed in their info and gets a readout that says "You are" on this strap, guess what. They are going to take your little program for granted and think that they are ON that strap. However, they are not.

Your program reports incorrectly in terms of the P5B for all values between
1Mhz FSB through 266Mhz FSB and 333Mhz FSB through 625Mhz FSB.

You are supplying a program with incorrect information. It is very plain.

Sounds like you need a special version just for you.

pauldovi · 01-12-07

Quote:

Originally Posted by money11465

Sounds like you need a special version just for you.

No, it sounds like anyone using this program between 1 and 266Mhz FSB and 333Mhz through 650Mhz FSB needs a special version. Because the only people this program works for, are the between 266Mhz and 333Mhz FSB on a P5B.

*DigitalPhreak* · 03-05-07

I just read through that whole pointless argument... (No Offense... really.) Get over it paul. Its a nifty little program that makes some quick calculations. Anybody that is that worried about straps will know if enough about straps to decipher any flaws. I for one am not so worried about the strap that I am on. I downloaded it for its ability to quickly tell me at what frequency I will be at x FSB.

Kudos Money... you did a great job! And better yet.. It was free.

pauldovi · 03-05-07

Quote:

Originally Posted by DigitalPhreak

I just read through that whole pointless argument... (No Offense... really.) Get over it paul. Its a nifty little program that makes some quick calculations. Anybody that is that worried about straps will know if enough about straps to decipher any flaws. I for one am not so worried about the strap that I am on. I downloaded it for its ability to quickly tell me at what frequency I will be at x FSB.

Kudos Money... you did a great job! And better yet.. It was free.

That is just a little rude. It is not pointless. The core of this program is to tell you what NB strap you are on. And it is wrong almost all the time. That not being anal like you are suggesting.

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

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