![]() |
|
Technology Computing, programming, science, electronics, telecommunications, etc. |
![]() |
|
Thread Tools | Display Modes |
|
![]() |
#1 |
Why, you're a regular Alfred E Einstein, ain't ya?
Join Date: Jun 2006
Posts: 21,206
|
I was having trouble again last night. Tonight I will look around some more. I may call one of my old IT buddies. Any of them would do it for a couple drinks, but I would like to offer a little better than going rate for a housecall. Just to make sure everything is good. What is the going rate?
__________________
A word to the wise ain't necessary - it's the stupid ones who need the advice. --Bill Cosby |
![]() |
![]() |
![]() |
#2 | |
Read? I only know how to write.
Join Date: Jan 2001
Posts: 11,933
|
Quote:
Not to fix it. Long before fixing anything, first the problem must be identified. Currently nobody even knows yet what your problem is. So, you did all those "PINGs" when it worked fine. Then when it was not working, you did those "PING" programs again. Those are critically essential facts. Same with "IPCONFIG /ALL". What did the anti-virus scan report some hour plus later when it finished working? Where is the information from system logs and Device manager? Those also were not idle questions. They were critically important facts that reported your system was still completely failed when you thought it was working. What were the lights doing on the wireless router both during good and failed operations? What is your OS? What is the computer? You probably have access to talent far superior to anything that the Geek Squad or you friend can provide. But you are stifling it by not answering all questions and doing everything requested - regardless of whether the machine is working or not. Are the wireless drivers current? That also was not a question to avoid because you did not understand it. What did www.windowsupdate.com report? What does the manufacturer report as the latest drivers? Again, not to fix anything (even though it might). To identify a problem that still exists even the machine appears to be working. What exactly did "netsh winsock reset" report? Nobody can be helpful if you filter out facts. Command prompt provides an easy way to cut and past every numeric detail from that window. Right click on the C:\ icon in the top left corner. In Edit, Select Mark. Then select everything on the screen to copy. Right click on the icon again to select Copy. Now the critical numbers that mean nothing to you can be pasted in a post. Those unanswered questions and every fact that means nothing to you is probably the critical fact that says what is wrong. Therefore you have stifled your help. Numerous questions and requests for information were posted. Most were not answered. Answers them all. Otherwise spend money on a less knowledgeable repairman. What's the going rate? $70 per hour? Either you can do the labor or pay someone else to do these same things. |
|
![]() |
![]() |
![]() |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Display Modes | |
|
|