goolasas.blogg.se

1. LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 FULL
2. LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 PRO
3. LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 SOFTWARE
4. LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 PC

RWilco RE: NIC card headaches.Why? Cyfu (TechnicalUser) 24 Jan 02 14:33 You can drop me a note at and I'll send you the program and source code. If anyone would like to run my test program to see if you get the same results (and give me a bit more ammunition to use with NetGear/National Semiconductor) let me know. I have been pursuing NetGear about this issue, but they haven't been very helpful. In WinME, despite I don't get a BSOD, the NIC stops functioning after the running my test program. The BSOD occurs on Windows 2000 (and maybe NT and/or XP - I haven't tried). I have been able to reproduce the problem with v1.30 and v1.80 of the NetGear drivers, and v5.0.119.0 and v5.0.124.0 of the National Semiconductor drivers. Analyzing the crash dump reveals that it is the FA-312 driver that is calling NDIS.SYS when the BSOD occurs. The NetGear FA-311 and FA-312 NICs both use the National Semiconductor DP83815 MacPhyter chipset. I have written a test program that reliably causes a BSOD in NDIS.SYS in my machine with a NetGear FA-312 NIC. RE: NIC card headaches.Why? Guest (visitor) 3 Dec 01 09:46 Check it out, it just might save ya a buck or two. This happens alot especially when people add new periphals to their computers. If your not running DHCP and you don't see an address and you know you put it in and bound the protocol chances are your NIC don't have an IRQ.

If your running DHCP you should see a IP address, if you don't chances are that your nic isn't getting it's IRQ and can't assign it to the NIC. I find that if you will go to the command prompt and type "ipconfig /all" you should see a nice information window telling you all about your IP configuration.

And lastly you can remove the dirver and reinstall it forcing the o/s to try to assign another IRQ. Try taking all extra cards out and leave video and nic and see if the problem goes away if it don't try moving the nic to another slot. NICs very rarely go bad (only seen one bad in 12 yrs and I've seen a bunch and this one was from a lightning strike), try instead of spending your hard earned money on another piece of equipment and hoping it will fix the problem, do some BASIC trouble shooting. When you see this error "DRIVER_IRQL_NOT_LESS_OR_EQUAL" there is a hint here, you have a IRQ problem hence computer crashes and reboots. Lets take a trip down A+ basics.IRQ,IRQ,IRQ. Or maybe it will end up ME here I come again! J TIA. All I can hope for now is for some kind soul to see this post on one of the forums I will post it to and maybe point me in the right direction. I’ve looked at a few of the knowledge bases on Microsoft and other places and find that though this error seems ‘popular’ there is no one definitive fix. I tried the games using a regular dial up connection with the internal 56k modem and the game loaded fine and played fine so I know the problem lies somewhere in this NIC card.

LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 FULL

The computer goes into full system reboot. I see the game screen start to appear and the ** POOF ** gone. I go through all the steps and it loads the game fine until the very last moment. The error also reports that the machine is BEGINNING DUMP OF PHYSICAL MEMORY.Īnother problem with the card I have found came when I tried to play Video poker through the Pogo games on. The error reports as happening in the file NDIS.SYS. Then, out of nowhere it seems that the card dies out on me with an error as follows: DRIVER_IRQL_NOT_LESS_OR_EQUAL. The card actually works fine for periods of time. The driver for the card (Downloaded right from Linksys) is the apparent latest one available. The card registers as active and as working properly with no conflicts. The card is a Linksys LNE100TX Fast Ethernet Adapter(LNE100TX v4) and on the surface all seems fine. Maybe someone can help save me from that drastic and gut wrenching ( J ) move. Seeing what was spent on 2K this really wouldn’t be what I want to do. I’ve encountered a big problem with the card that may actually force me to revert back to ME. All is not fine however, somewhere in my NIC card.

LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 SOFTWARE

The configurations of both hardware and software all look normal and properly set. The problems I have encountered have been the normal learning curve type of things. To further insure (or so I thought) that I would have minimal problems, I made sure that all the hardware in this Gateway Essential 933 was on the HCL and that it would work with the proper installation of needed drivers.įor the most part I’ve done okay.

LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 PC

I specifically waited until I bought a new PC to even truly think about buying Win2000.

LINKSYS LNE100TX V5.1 DRIVER WINDOWS 98 PRO

I knew when I bought Win 2000 Pro that it was possible I would run into some problems and incidents that I didn’t have in WinME.