top of page
chlorderodersflava

Realtek 8029as Driver: How to Troubleshoot and Fix Common Issues



If the driver listed is not the right version or operating system, search our driver archive for the correct version. Enter RealTek 8029(AS) into the search box above and then submit. In the results, choose the best match for your PC and operating system.




Realtek 8029as Driver



Once you have downloaded your new driver, you'll need to install it. In Windows, use a built-in utility called Device Manager, which allows you to see all of the devices recognized by your system, and the drivers associated with them.


Windows'Unix (Linux)'DOS'Novell'OEM'OthersThis product is covered by one or more of the following patents:US5,307,459, US5,434,872, US5,732,094, US6,570,884, US6,115,776, and US6,327,625.If there is any further detailed information required, please contact This email address is being protected from spambots. You need JavaScript enabled to view it.document.getElementById('cloak8c9a15feec483db2deb32efd92ba3214').innerHTML = '';var prefix = 'ma' + 'il' + 'to';var path = 'hr' + 'ef' + '=';var addy8c9a15feec483db2deb32efd92ba3214 = 'nicfae' + '@';addy8c9a15feec483db2deb32efd92ba3214 = addy8c9a15feec483db2deb32efd92ba3214 + 'realtek' + '.' + 'com';var addy_text8c9a15feec483db2deb32efd92ba3214 = 'nicfae' + '@' + 'realtek' + '.' + 'com';document.getElementById('cloak8c9a15feec483db2deb32efd92ba3214').innerHTML += ''+addy_text8c9a15feec483db2deb32efd92ba3214+'';


Drivers for Cirrus GD-5446 video adapterDOS DriversOS/2 DriversWindows 3.1, Windows NT and Windows 9x DriversDrivers for X.Org and X11 are inside "cirrus" module.QNX includes the driver.


Drivers for Realtek 8029AS network adapter (for other OSes try NE2000 compatible driver)BeOS R4 and R4.5 instructions (Use NE2000 PCI)BeOS R5 instructions (Use NE2000 PCI)DOS driver for NDIS2LANtastic 4 driverLANtastic 5 driverWindows NT 3.51 driverWindows NT 4.0 driverNovell NetWare Client32 driverNovell NetWare Client for DOS ODI driverNovell NetWare Client for OS/2 ODI driverNovell NetWare Server driverOS/2 driver for NDIS2SCO UNIX driverUNIXWare driverWindows for Workgroups driver (3.1 and 3.11)Windows 95 driverWindows 98 driverWindows 2000 driverWindows XP includes driverWindows Vista stopped supportLinux driver is in ne2k-pci.c


Drivers for Realtek 8139 network adapterBeOS R4 and R4.5 driverBeOS R5 driverDOS driver for NDIS2FreeBSD driver (for versions that do not include it in kernel repository)JavaOS driverMacOS 8.5, 8.6, 9.0 and 9.1 driverNovell NetWare Client32 driverNovell NetWare Client for DOS ODI driverNovell NetWare Client for OS/2 ODI driverNovell NetWare Server (from 3.12 onward)SCO UNIX driverSlackware Linux 8 driverSolaris 7, 8, 9, and 10 driverUNIXWare driverVXWorks for x86 driverWindows NT 3.51 driverWindows NT 4.0 driverEmbedded Windows NT 4.0 driverWindows for Workgroups driver (3.1 and 3.11)Windows 95 driverWindows 98 driverWindows 98 Second Edition, Windows Me and Windows 2000 driverWindows XP and Windows XP Professional x64 Edition driverWindows CE 2.0 for x86 driverWindows CE 3.0 for x86 driverMac OS X 10.0.4 and Darwin/PPC 1.3.1 driverMac OS X 10.1, Darwin/PPC 1.4.1 and Darwin/PPC 5 driverMac OS X 10.2 and Darwin/PPC 6 driverLinux driver is in 8139too.c or 8139cp.cWindows Vista, Windows 2003 and Windows CE.NET include drivers


Drivers for Sound Blaster 16 adapterDOS driverWindows NT 4.0 driverWindows 95 and Windows 98 driverOSS and ALSA have drivers.Windows 98 SE, Windows Me, Windows 2000, Windows XP and Windows 2003 include drivers.Windows Vista dropped support.


It's an RTL8139C card. I found the drivers online (from Realtek), since I don't have an install CD myself. I ran the diagnostics program in pure DOS mode and it seemed to work. (It didn't work when running the same program inside Win95 though.)


I really don't know what to do, even after installing the TCP/IP protocol and restarting, winipcfg tells me it can't do anything and the hardware properties says it's got "error code 2" and tells me to install different drivers.


I'm pretty sure it's a 10/100mbit card, since I bought it a couple of years ago. Still, you're probably right and I'll go searching for some other drivers. If anyone knows a good place where I can find them, that would be useful. Somehow it's harder than I thought to find them.


Ive recently been through the same thing as you ...Its really a pain to get those NICs to work under old windows. Under win 3.11 I tried pretty much every combinations with 3 different drivers for the RTL8139 with two different cards. It would not work. I ended up digging up a RTL8029as from another machine and found a driver that worked with it in windows 3.1.


Hmm, I never had such problems. The main point is, that for Win98SE and newer you can use the WDM architecture drivers, for Win95 you have to use the older/other drivers. But it is written in the readme.


Thanks for the drivers, but unfortunately it doesn't seem to work yet. It's strange because I'm positive these are the correct drivers for my card. It's now properly installed as a 10MB/100MB PCI Fast Ethernet Card (and I actually remember using it with this name under Windows 98 before, though that was with a completely different machine).


Some progress, though. I removed the USB PCI card and put the network card in its slot, just to see if that would make a difference. Not really. But with these new drivers, at least I'm getting a positive I/O test with the card:


This version of the driver can be identified by usingsin ver -- it should be reported as4.25F. Note also that the hardware is supported only in PCII/O access mode on the PCI bus -- memory-mapping isn'tsupported at this time.


Be aware that this driver should only be used for devices not yet supported by the in-kernel driver r8169. Installation of the r8168-dkms package will disable the in-kernel r8169module. To re-enable r8169, the r8168-dkms package must be purged.


This package installs an updated version of the Microsoft Windows 7, Vista and XP device driver for the Realtek Ethernet that comes preinstalled in your computer.This package requires approximately 10MB of space on your hard drive.


Navigation: Linux Kernel Driver DataBase - web LKDDB: Main index - N index CONFIG_NE2K_PCI: PCI NE2000 and clones support (see help)(adsbygoogle = window.adsbygoogle []).push();General informationsThe Linux kernel configuration item CONFIG_NE2K_PCI has multiple definitions:PCI NE2000 and clones support (see help) found in drivers/net/ethernet/8390/KconfigThe configuration item CONFIG_NE2K_PCI:


This driver is for NE2000 compatible PCI cards. It will not workwith ISA NE2000 cards (they have their own driver, "NE2000/NE1000support" below). If you have a PCI NE2000 network (Ethernet) card,say Y here.


This driver is for NE2000 compatible PCI cards. It will not workwith ISA NE2000 cards (they have their own driver, "NE2000/NE1000support" below). If you have a PCI NE2000 network (Ethernet) card,say Y and read the Ethernet-HOWTO, available from


RealTek RTL8029AS drivers will help to eliminate failures and correct errors in your device's operation. Download RealTek RTL8029AS drivers for different OS Windows versions (32 and 64 bit). After you have downloaded the archive with RealTek RTL8029AS driver, unpack the file in any folder and run it.


*1 - Not sure if this driver works.*2 - Use when booting the disk via a PXE remote boot image*3 - This works for some motherboards (eg ASUS A7N-266), but not for others.*4 - Also works for some D-LINK 530 cards*5 - Not the original driver's filename!


Some network cards uunfortunately have the same name or very similar names, yet use a totally different driver. This sometimes adds a lot of confusion to the process of selecting the right driver. (not to mention putting the correct driver on the disk in the first place!


There are a number of reasons why you could be encountering issues with rtux64w10.sys. Most of the issues concerning SYS files involve Blue Screen of Death (BSOD) errors. These types of rtux64w10.sys errors can be cause by hardware problems, outdated firmware, corrupt drivers, or other software-related (eg. 3DP Net update) issues. Some of these errors include:


Commodore 2065 (requires user supplied driver to be placed in DEVS:networks)Zeus ConneXion (C= 2065 clone) (requires user supplied driver to be placed in DEVS:networks)VillageTronic Ariadne II (requires user supplied driver to be placed in DEVS:networks)X-Surf (needs a patched Ariadne driver). The on-board IDE does not work. 2ff7e9595c


0 views0 comments

Recent Posts

See All

Comments


bottom of page