Grasky's Overclocking Guide seems to be withdrawn .. .

[BonzaiDuck]

What happened to the sticky we've all known and loved, dealing with the "OC ins and outs" of over-clocking for Nehalem and earlier cores?

 

[sangyup81]

i'm guessing it got automatically axed due to inactivity

 

[BonzaiDuck]

i'm guessing it got automatically axed due to inactivity

Surely, it's in an archive somewhere accessible to members!!

There was a lot of useful information in that sticky. the response comments -- we might do without, but the author's explanation of the i7 and other cores -- very useful . . .

 

[Ben90]

No offense to whoever wrote it, but the i7 guide was pretty crappy. Whenever I linked to one of the stickies, I always used the C2D, even if it was an i7 processor in question.

I feel like such a Negative Nancy, but I didn't really even like the C2D sticky that much. With about 4% more effort, it could have been easily made to accommodate ANY type of overclocking. I did appreciate how it put a lot of emphasis on the pre-reqs to overclocking.

 

[Gillbot]

It was unstuck. If there is merit in bringing it back, people will post in it and keep it up. Otherwise, it's an old guide for old tech and the activity wasn't there to justify it remaining stuck.

 

[BonzaiDuck]

It was unstuck. If there is merit in bringing it back, people will post in it and keep it up. Otherwise, it's an old guide for old tech and the activity wasn't there to justify it remaining stuck.

Well . . . "old tech" . . . . but not quite that old . . . . I suspect the same architecture will carry through the IB release and beyond for a while.

Of course, there's also the phenomenon of response posts. For the volume, one would have to do a lot of scanning for anything additional of insightful use. Which supports a suggestion to put the original guide in one thread and the responses in another . . . .

 

[Gillbot]

Well . . . "old tech" . . . . but not quite that old . . . . I suspect the same architecture will carry through the IB release and beyond for a while.

Of course, there's also the phenomenon of response posts. For the volume, one would have to do a lot of scanning for anything additional of insightful use. Which supports a suggestion to put the original guide in one thread and the responses in another . . . .

feel free to reply to it and suggest updates. as I said, if there is interest and merit, it can be restuck easily.

 

[BonzaiDuck]

feel free to reply to it and suggest updates. as I said, if there is interest and merit, it can be restuck easily.

Roger-Dodger . . . I'll make it a "must do." After I put away the latest batch of home-made pasta sauce, and fix the dough for tomorrow's pizza and the semi-monthly lunch of the seniors' "Gang of Four."

Soon . . .

 

[jvroig]

I unstuck it, but it wasn't my decision alone, of course. I gather that less stickies are always a good thing, and this one you are talking about was already very old (C2D), but there's really no problem to resticky it (or to sticky any thread) as long as the interest and activity are there. Otherwise, they just look like artifacts and take up vertical space we could all use.

Overclocking guides in particular are abundant and easily google-able, so it wasn't such a difficult decision to have them unstuck, given their age.

 

[Gillbot]

I unstuck it, but it wasn't my decision alone, of course. I gather that less stickies are always a good thing, and this one you are talking about was already very old (C2D), but there's really no problem to resticky it (or to sticky any thread) as long as the interest and activity are there. Otherwise, they just look like artifacts and take up vertical space we could all use.

Overclocking guides in particular are abundant and easily google-able, so it wasn't such a difficult decision to have them unstuck, given their age.

:thumbsup:

Wise words here folks!