why? all my stuff i have in my computer is in my sig and I also have a modem in my system too. i think i have enough free IRQs... the NIC is a D-Link, i just got it the other day.
I put my NIC in, and windows takes forever to load now
- Thread starter aUt0eXebat
- Start date
which windows and where does it freeze, boot up, after windows screen, booting into window and detecting card and freeze ?
I have had the same problem with my Linksys 10/100TX It won't work in any slot but slot 2 for some reason. I would try that frist if not check the d-link website faq and get the latest drivers.
I have the latest drivers. and I only tried it in one slot... Ill try moving it around in diff slots..
I had the same problem with a Linksys nic,tried all slots, downloaded new drivers, same crap.
Bought a Netgear nic and the problem was solved on the first boot!
Bought a Netgear nic and the problem was solved on the first boot!
well, its in a different slot now, and it loads, but right after the Windows 98 splash, in goes to load my Desktop, but it sits and waits for about 15 secs, and then loads the password screen.
Why does it take so long to load now? Is there anything I can do to fix this? Oh yea I have a modem in there too. Here are my settings in the network props... anything else i need to add/remove in there? I am just setting up a little P-P network.
Why does it take so long to load now? Is there anything I can do to fix this? Oh yea I have a modem in there too. Here are my settings in the network props... anything else i need to add/remove in there? I am just setting up a little P-P network.
Are IPs assigned on your boxes, or are they set to DHCP? I assume that you have 2 of them since you said it was P2P; you're using a xover cable, correct?
What IRQs are currently assigned to your NIC and video card? Does your BIOS give you the option to check/set IRQs?
What IRQs are currently assigned to your NIC and video card? Does your BIOS give you the option to check/set IRQs?
Unbind TCP/IP from NetBIOS. You probably don't need it anyway. Your system will load much faster as a result. More importantly, it will close up a few open ports and secure you computer even further.
nope, no cross over cable, I have a 5 link hub, i am planning on adding another computer sometime. how would I unbind Rudee?
You mean unbind TCP/IP from Client for M$ Networks & F&P sharing for M$ Networks, and/or uncheck "enable NetBIOS over TCP/IP?" 
Edit: The above tips might help secure his shares, but looking at his network properties he doesn't have sharing installed. I'm not sure how it would help his hanging issue, though.
Edit: The above tips might help secure his shares, but looking at his network properties he doesn't have sharing installed. I'm not sure how it would help his hanging issue, though.
Hi. I think what's happening is you have no network connection. I have DSL, which uses a NIC, and everytime I boot-up my computer, Windows searches for a connection. If my DSL is down for whatever reason, Windows takes a long time to load up as it searches for a good connection. In your case, you're setting up a local network, but the idea is the same. Check the integrity of your network chain.
Hope this helps.
Antonio
Hope this helps.
Antonio
Hi. I think what's happening is you have no network connection. I have DSL, which uses a NIC, and everytime I boot-up my computer, Windows searches for a connection. If my DSL is down for whatever reason, Windows takes a long time to load up as it searches for a good connection. In your case, you're setting up a local network, but the idea is the same. Check the integrity of your network chain.
Hope this helps.
Antonio
Hope this helps.
Antonio
Are you connected to any server? 'cause some drivers "look" for something to connect to during boot.
If your IPs are set to DHCP you can try setting them manually. Maybe the one is choking because it can't get a number. Who knows? Also, I've found that static IPs often speed up the boot process a little.
Have you assigned an IP addy to the TCP/IP->D-link NIC properties?
The reason it's taking long to boot is that Windows is trying to assign an IP address upon Winboot. Specify them w/ an IP of 192.168.0.1 or something with a Subnet of 255.255.255.0.
The reason it's taking long to boot is that Windows is trying to assign an IP address upon Winboot. Specify them w/ an IP of 192.168.0.1 or something with a Subnet of 255.255.255.0.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 24K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes Discussion Threads
- Started by Tigerick
- Replies: 19K
-
-
-
Facebook
Twitter