NIC card Slow/30 sec. boot into Windows ME or 98.. Netgear FA310TX..Serious help needed!

[Wizzah]

Hello!

I know you guys are the best at what you do, so I am hoping you can easily help me with this.

When I first purchased my Netgear card a while ago and installed it into my first PC, There was discussion here on how to change a setting in Network Neighborhood in order to stop the slow slow slow bootup when the NIC card is installed and enabled.

I can no longer remember which setting it is... I believe it is the WINS, Gateway or similar..

I am using Road Runner and have to use DHCP to connect... I do not have a static IP with them... so I don't believe it was the DHCP setting....

Please help, it's taking about 30 secs to boot into WinME because of this issue.

I appreciate all your help, Thanks Guys and Gals!

 

[GT1999]

The reason it takes so long is because with DHCP the computer is sitting there looking for a DHCP server, but there isn't one. At least for my DSL (which is PPPoE, however), just because you have a dynamic IP that changes doesn't mean you have to have DHCP enabled for your NIC.

Just go to your NIC and specify a LAN only IP, such as 192.168.0.1 or something. Then see if your cable modem grabs the dynamic IP like it's supposed to, still.

If not, then I guess you will need to have DHCP enabled.

 

[Wizzah]

Thank you for your response...

I updated the information in the cards TCP/IP settings tab..

What should I specify for the Subnet Mask?

Thanks again!

 

[GT1999]

Probably 255.255.255.0

 

[Wizzah]

I tried the above and it still hangs upon bootup... I can tell it's definitely still this same NIC problem as 2 years ago.. As soon as my Cable modem lights start flashing, it goes right into the main WINME screen... Are there any other settings that could possibly effect this?

Wins?

Gateway?


DNS?


I know it was one of these, but I can't remember and I didn't take good notes

🙁

Thanks agai Guys and Gals

 

[GT1999]

You shouldn't need a WINS, that's for a domain server and the like.

You might need a gateway in there, do you have any info (on a sheet or anything) from your ISP?

 

[John]

<< Please help, it's taking about 30 secs to boot into WinME because of this issue. >>



30sec from the time you turn on the system to get to the desktop? If so that it not too terribly long. You should not have to mess with the network properties by specifying IP's and making other changes within your nic tcp/ip settings. If anything, remove the protocols you aren't using.

 

[ToBeMe]

Ibelieve there is an updated driver which addresses this issue..............saw an identical post about this problem somewhere a while back and there was a link to a new driver. Can't recall where the thread was though..........🙁

 

[Wizzah]

No, 30 seconds from the time it shows the initial WinME splash screen until the time it enters the desktop.

I had this same problem when I installed the card a year ago on my Windows 98 SE system.

At the time there was a lot of talk on here and how to get by this long 30 second load time..

I applied the change from what I read on here, and it worked flawlessly... The 30 second splash time never happened again...

I just can't remember what change it was.. it was in the Network Neighborhood...

 

[KGB1]

Had that same card for 1 year. I formatted my drive sometimes and I couldnt believe how fast i started in Windows 2000. Once I popped in that Netgear FA310TX and the system slowed down and could not connect to my own LAN. It died on me.. good riddance.
But do they still sell that model?? Man unless you paid 5 dollars you got jipped. I never found out what the issue was, but it worked fine as a Crossover NIC card. Dude give it back or get rid of it. Either get a good Intel/Lynksis/DLink/3Com card and dont be bothered with that thing( itll make your hair fall)

 

[John]

Do you have another NIC to swap with? Pick up a 5.00 Realtek 8139C chip model.