|
Check to see if the nic was disabled in the bios. Then reset settings for the bios and check that. After that check to see if there is a bios settings reset jumper on the motherboard. Also, you might want to test it with a minimum of extra cards plugged in.
Another common culprit is windows update "upgrading" drivers.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
I shall check out the bios and give what you've said a try. I dont think it would be WU though as it hasnt downlaoded anything in a about week and the NIC was working this morning.
|
|
|
|
|
I tried everything you suggested, and played with a couple mroe settings I found, but nothing seemed to help. I installed a PCI NIC in place of the PCI WiFi card for the time being.
|
|
|
|
|
That's the problem with the integrated devices. If they do fail, they are part of the motherboard.
Another possibility is that you have a network cable that is close to tolerence. In that situation you will get ittermitent connection, some NICs will work some won't and the ones that do work will have outages, but it sounds like the NIC probably failed.
Most "hardware" problems are really driver/software problems so you typically have to go much further out of your way to elminate software problems. Some of NIC companies had diagnostic applications that ran under DOS that might be able to give a more definite result, but like I said it's probably let out the magic smoke. At least they make motherboards with dual NICs these days.
I can imagine the sinking feeling one would have after ordering my book,
only to find a laughably ridiculous theory with demented logic once the book arrives - Mark McCutcheon
|
|
|
|
|
I've spent so much time trying to get it working over this past week that now I'm prepared to just let it be. In the not too distant future the whole machine will need rebuilding anyway so I will cycle the motherboard round to a testing machine and then see if I can find some diagnostics software to run on it.
|
|
|
|
|
David Wulff wrote:
I would rather not have to replace the whole damned motherboard for a $1 component.
If it is dead, you can get USB network adapters, so if you have a spare USB port, you're back in business.
|
|
|
|
|
anyone has done such job?please give me some hint!Thanks a lot
please contact:
max_xiayi@hotmail.com
|
|
|
|
|
max_xiayi wrote:
anyone has done such job?please give me some hint!Thanks a lot
why would you want to? Same sound file two cards, are you trying to reach 14.2 sound or something? You can go up to 7.1 sound easily now so the question seems rather bizarre.
_________________________
Asu no koto o ieba, tenjo de nezumi ga warau.
Talk about things of tomorrow and the mice in the ceiling laugh. (Japanese Proverb)
|
|
|
|
|
It is possible, but the application has to support it.
Don't try it, just do it! 
|
|
|
|
|
I need to write a little app that can detect when the system clock
gets adjusted. (within limits) In a perfect world, I guess Id like to
know what process does the adjustments, but that may be the subject to
some follow-on post.
Can anyone direct me to some thread here in TheCodeProject?
Basically, I need to access the system's TIMECLOCK (the one that is adjustable,
and shows me the time in the lower right corner). I also figure I need access
to the systems UPTIME CLOCK (that just humms along - regardless of whatever
time the TIMECLOCK says).
I *think* that what I want to do, is just do an infinite loop where I read
the SYSTEMCLOCK, compare it to the previous reading.
If its within the limits of time I *expect* to elapse, then all is good. I
just sleep another 1000ms or some such, and test again.
If I detect that somehow the clock has gone backwards, or jumped forward more
than say 1500 ms, then I want to append to some logfile that a time-adjustment
has occurred...
Can anyone give me some guidance on this? Is this a workable strategy?
(I ask because I dont really know what my 'sleep 1000ms' step will do if
the clock is adjusted during my sleep... basically, WILL I KNOW if a
time adjustment has taken place? (even if its a slight nudge forward or
backward). How does this work behind the curtain?
Free candy-bar to the guy (or gal) that puts me on the path to elightenment.
Thanks,
-Newbie Dave
AIM: KewlBean36
|
|
|
|
|
|
Hi all, Just wanna ask this.. I used Norton Utilities 2005 (Disk Doctor) and it keeps saying my Security Descriptors are not fixed. It tells me to Click the 'Fix Errors' and to enable Surface testing, which I did and restarted the system for it to fix it...
After half an hour plus of waiting, it gets done and when back in windows, using norton disk doctor again, it reports that the security descriptors are still not fixed... Anyone have any ideas..?
Why I did Disk doctor in the first place is my system tend to randomly reboot itself lately? Could this be the cause? thanz all..
|
|
|
|
|
Ever tried chkdsk/scandisk?
Don't try it, just do it!
|
|
|
|
|
Tried it, doesn't work.. read this from symantec's own site but the problem still there... hehe.. any idea what kind of errors this problem may or may not cause... thanz..
|
|
|
|
|
XP does the complete shutdown sequence and at the moment the computer should power down, the hard disk light goes on and remains on even though I don’t hear disk head movement. Using the power switch is no help, the computer remains on unless I unplug it. When I plug it back, the hard disk light goes on again and remains on. The computer starts normally when I hit the power switch.
Any idea?
Thanks
Hugo Migneron
|
|
|
|
|
If it's been doing this since you bought it, my thought would be that the indicator might've been connected to the mobo backwards. ALso in this case the HD light would be going out when in use instead of turning on. Beyond this I'm stumpted.
|
|
|
|
|
dan neely wrote:
If it's been doing this since you bought it
It started doing it a while after the computer was bought, so I guess it cannot be the HD indicator.
Thanks for your reply anyway!
Hugo Migneron
|
|
|
|
|
|
Yes I did scan for viruses and spywares and there were none. Just out of curiosity though, could a virus/spyware cause such a thing even if XP is closed at this point?
Hugo Migneron
|
|
|
|
|
i think so...
some viruses (not a spyware at this point) can update the bios, or change the sector 0 with their own code to be loaded at the very begining when the hard dirk is read...
however, what happens when you keep the power button of your computer pressed longer than 5 seconds ?
TOXCCT >>> GEII power
[toxcct][VisualCalc]
|
|
|
|
|
toxcct wrote:
however, what happens when you keep the power button of your computer pressed longer than 5 seconds ?
It doesn't power down the computer like it is supposed to. The only way to make it stop is to unplug it.
I spent quite some time looking for a solution over the web and didn't find anything related and I don't really see what could cause this. I would guess it's a hardware problem since it is such a low level issue, but I tested the HD in another computer and it is not defective.
I am starting to think that exorcism might be the only solution 
Thanks!
Hugo Migneron
|
|
|
|
|
My fist thought was that the HD power light was connected wrongly to the MB but it seems that is not the case. I would check the HD light cable anyway as it looks like there could be a short or something. Normally there are more lights on a case than you need for a christmas tree so i would try connecting one of these to the HD light connectors or swap some over to give you a better idea of where the problem is.
EDIT: Assuming you are happy laying with the insides of your PC
Jon
|
|
|
|
|
I said in my original post that I didn't hear disk head movement. I didn't say that the disk was spinning though. I don't think it's just a question of lights.
jonathan15 wrote:
i would try connecting one of these to the HD light connectors or swap some over to give you a better idea of where the problem is.
I don't really understand how this could help me. I am not too used to hardware problems so maybe you can point out to me what you meant.
Thanks for you help!
Hugo Migneron
|
|
|
|
|
Bought me one of these[^] the other day for AUD$22.10.
Fired it up today for the first time testing a couple power supplies I had in the garage. After seeing that it has a couple of contact points for testing voltages I dug out my brand new, never been used 11 or 12 year old multimeter I bought all those years ago thinking I might need it one day (See ladies, it wasn't a waste of money. I did need it and at a time when no shops were open, so lucky I did buy it back then). Funny thing is when I connected it all up none of the voltages were all that close. The readings were
PSU 1 PSU 2
+3.3V 3.35V 3.36V
+5V 5.22V 5.20V
+12V 11.81V 11.90VIs it normal for voltage to be off by 4% like that.
I used to short pins 13 and 14 or 14 and 15 on the power supply as told by Roger Wright. But a couple of weeks ago I found a machine where the power supply ran for hours when shorted this way with no load. But when connected to the computer sporadically turned itself off or wouldn't start at all. When I heard of this little toy (with built in load) I ran out to get one to throw in my toolkit.
Michael Martin
Australia
"I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So i had to leave the place as soon as possible."
- Mr.Prakash 24/04/2004
|
|
|
|
|
Yes. The atx standard specifies a 5% variance is allowable.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
