Driver realtek RTL 8139

[GMan]

Right click on the 0008 and delete it. Then merge my attachment to the registry after you extract it. Reboot.

(I custom made it for you based on my key. It took some time, but it's all good.)

Yours is missing a whole bunch of stuff, if you compare your screenshot to mine.

 

[prateek3651]

how to merge the registry .. ? please .. tell me Gman .. thnx very much for helping .. i guess this it will work ..

 

[GMan]

Delete your 0008 key, then just extract my download from the rar, then double click on the .reg file. Reboot.

 

[prateek3651]

okay i did but now it's showing code 31 ..

 

[GMan]

Extract the driver file attached below to C:\Windows\System32\drivers

Reboot.


--------

If that doesn't work, extract the attachment from this post to a folder:

http://www.eightforums.com/hardware-drivers/4791-driver-realtek-rtl-8139-a.html#post73003

Then install using the device manager. Right click Realtek, update driver software, browse my computer, let me pick, have disk. Find and double click on the extracted .inf. Hit ok then next. Reboot.

 

[prateek3651]

not working ..

 

[GMan]

not working ..

Which error code do you get after doing the second part of my previous post?

Did you ever tweak or disable any Windows services like "Plug and Play" or "Shell Hardware Detection" or "Device Setup Manager"?

 

[prateek3651]

rtnicxp .. only contain .. one sys file .. whic i have pasted in systems 32 /drivers .. but still not working .. same code 31 ... i do not understand what is the matter.. with this relatek thing ..

 

[GMan]

rtnicxp .. only contain .. one sys file .. whic i have pasted in systems 32 /drivers .. but still not working .. same code 31 ... i do not understand what is the matter.. with this relatek thing ..

Dunno. Try pasting the .dll and the .cat file to C:\Windows\System32

Then rename the .inf file to oem4.inf and paste it over the one at C:\Windows\Inf

Reboot.

Other than that, unless Calico has something to add, I recommend clean installing Windows.

 

[prateek3651]

okay let me clean install the window again ,, which i have done before also .. but nothing helped .. i am doing it again .. may be this time it will help me ..

 

[Calico]

I think a fresh install is probably best, but one question, is the realtek the only network adapter in the system?

 

[GMan]

Could try to install using the device manager and this extraction below. I added your hardware id specifically to it. That shouldn't be necessary here but who knows...

 

[prateek3651]

yes it is the only adapter in the system i installed new copy of windows then i updated the registry .. .. still sthen same issue .. code 10

 

[GMan]

Tried the driver from my previous post yet?

It should show up as "SURECOM EP-320X-R 100/10M PCI Adapter" when done, in the device manager.

 

[prateek3651]

nope ..

 

[prateek3651]

i did tried that also .. , it show surecom .. adapter .. but it's not working too .. i think we should .. register this problem to microsoft may be they can figure it out and help us

 

[GMan]

i did tried that also .. , it show surecom .. adapter .. but it's not working too .. i think we should .. register this problem to microsoft may be they can figure it out and help us

Unfortunately, I don't think they'd be interested in repairing one machine having an issue for an unpaid beta OS.

Windows can't bind the IP protocol because as a guess, something is weird with your bios and/or hardware address.

Your best bet is to revisit or do further research on how to clear the DMI pool. (Or clear configuration data.)

If unsuccessful with that, as stated before, you can purchase a PCI adapter for extremely cheap.

 

[prateek3651]

okay i will buy ..... pci adapter now tell me which will be suitable for windows eight ?

 

[Calico]

Something very odd going on here. The original error was a code 10, more often than not Device manager will display this when it doesn't know the exact cause of the problem. usually it's a driver issue, but it may also be a something indirectly related or even a hardware event. The interesting part, is the lack of information in the registry key, after you performed the tasks listed. I'm not really sure what happened there but my guess would be the driver failed to install correctly, perhaps they were the wrong drivers.

Moving on, after you merged the data GMan gave you, the code change to 31. This code is telling us Windows couldn't load the drivers, which may mean they're the wrong drivers.

Going back to an earlier post of mine, I had a feeling Windows simply wasn't detecting your network card correctly, the question is, why?

Out of interest, is this an onboard - integral motherboard chip - or a separate network card?

 

[prateek3651]

it's a onboard network card ... and funny thing is that it's working perfectly with windows 7 but not with 8 .... so i guess something .. with the operating system ....