How to get network to work?

[cleanremote]

[copy]

Probably in a bug in ne2k.js.

[therealbrate]

wait how did you boot windows 7?

[hello-smile6]

How did you get Windows 7 to work, @cleanremote?

[ayunami2000]

can you send the 7.img file that you used? (upload it to google drive or mediafire or github)

[BelleNottelling]

AFAIK Vista and newer don't have support for the NE2K, buuuut there are two possible solutions that may or may not work:

1. Use the NE2K driver from a Windows Longhorn build: https://www.betaarchive.com/forum/viewtopic.php?t=38054
2. Use the NE2K driver from ReactOS. ReactOS NE2K.zip (Compiled today off of their current master branch)

I tried option #2 personally.

Needed to tell Windows to install the driver (not signed), but after quite a bit of thinking it did indeed install and it said that it was working, but I still didn't see a connection inside of Windows. Windows doesn't even seem to show it as a network adapter in control panel.

Another oddity is that Window seems to PCI devices are removable?
@copy Any idea what's going on with this?

I tried rebooting Windows after installing the driver, but it give a BSoD on the next boot, which I believe is actually caused by the many many device drivers it sets up for V86 and NOT the network driver.

Edit:
This is also a random Windows 7 image I created back in 2018 using Qemu, so it's entirely possible there is something weird with this image. It looks like I have an OEM ISO rip so I may do a fresh image and try it again sometime in the future

[copy]

Would probably good to try it with qemu with -nic user,model=ne2k_pci.

Another oddity is that Window seems to PCI devices are removable?

No idea.

[BelleNottelling]

So I wanted to follow up on this.
The BSoD I was getting was unrelated to the ReactOS driver being installed, it'll happen regardless because of Vista setting up new drivers. I tried safe mode, group policy, and a few tweaks to try and prevent vista from doing that, but I had no luck. Vista would either install the driver as usual or BSoD before the initial boot.

So, I instead installed the driver in qemu, but with both it and V86 Windows doesn't show any available connections, so it seems like the driver itself isn't causing a BSoD, but it also can't make a connection. I did not even attempt the other option, as reading the page again it looks like it only works with the longhorn releases at the newest, not anything Vista+

Also, this issue of getting networking to work isn't an actual bug with V86, but instead of newer OS's not coming with drivers for the NE2K network card. However, there are serous bugs that cause issues with Vista/7 in V86 so there are still bugs.

TLDR:

• The BSoD with Vista is a compatibility issue with V86, not the driver
• The drive does not work at all, even in qemu
• The other option doesn't seem to apply to the retail release of Vista

Note: I did all of my testing in Vista, but the info applies to 7 as well. Under the hood 7 is like Vista+ and the bit that I did use 7 for seemed to behave the same

[SuperMaxusa]

I tried running ne2k_pci on Windows 7 and i have some success.

As said @BelleNottelling, Windows Vista (and 7) don't have support for the NE2K, but I found this post about how to use this network card for Windows Vista RTM by installing the driver from Windows 2000.

This driver also was able to install via Device Manager, but there is one problem: after each reboot, Windows installs automatically its own driver (Ethernet Controller), which does not work correctly with rtl8029

[copy]

I'll close this issue, as everything seems to be working fine from v86's point of view.

Perhaps soon we'll get a virtio-net device, which should work in windows 7 (#1074).