why is this thread closed when there is clearly no difinitive answer given?

[Clzwldsconfusion]

Intel Dual Band Wireless AC 7260 Problem

 

[Wolfshadw]

What thread? Link?

Wolfshadw
Moderator

 

[Clzwldsconfusion]

Sorry I thought I had hperlinked it but I see it's not showing.
"Intel Dual Band Wireless AC 7260 Problem"
"Tom's HardwareForumWireless NetworkingIntel Dual Band Wireless AC 7260 Problem"
Started by
bmarkjones49
January 9, 2014 11:58:27 AM
Now I'm really not sure how to link the thread?
Appreciate you at least questioning what's up.

 

[Clzwldsconfusion]

http://www.tomshardware.com/answers/id-1972291/intel-dual-band-wireless-7260-problem.html
I spent part of the afternoon with centurylink trying to figure out more info on this problem.

 

[ex_bubblehead]

That thread is approaching 2 years old and was closed by a moderator in order to prevent further necroposting. Rather than hijacking old threads it's preferred that you start a new one.

 

[Wolfshadw]

Thanks for the assist, ex_bubblehead!

-Wolf sends

 

[Clzwldsconfusion]

"necroposting" I'm looking up what that means rt now."necroposting. On a message board, posting something irrelevent on a really old topic to bring it to the top of the list topics"
So we start a new thread to rehash the same info as the first thread so as to ? save ?
Information is what I'm looking for. It just seems that this process obfuscates existing information. and we might ask?Why?
And the answer to that is a new thread.
So I look for the answer and I get buy a different devise as the chosen answer. And don't be necroposting on the site.
My take away is books of information are old so don't open em. Reinvent the wheel. It's good for job creation.
I have spent 3 dayishs on trying to resolve this issue.
I am closer now.
Can anybody else help me waist more time?

 

[Pooneil]

Please don't whine about the moderation. If you need help, just ask a direct question in its own thread.

 

[ex_bubblehead]

This thread has now run its course. Closing.