I see from using wpiview on GenMU_INTEL_WIFI-0-4-6.wpi that the 8086:0891 also uses the netw4x32.reg and netw4x32.sys files.
It actually uses completely different file names in windows. Those files also seem to work, as well as the netw4x32.* files do. the number "4" indicates the version of the windows driver netw5x32.* is newer, but also requires more resources. I have also tried older ones, with the same results, and they are actually more likely to work, until the device needs something that they don't support. Choosing netw4x32.* was a compromise, and some of the packaged (TEST) drivers have multiple copies in them, but only one is configured. They can e selected by editing PROTOCOL.INI.
GENMAC2.WPI from the eCS2.2beta2 dvd/iso will also need to be installed as v2.20 releases seem to fail to load drivers they do not "know" about.
Not true. The only difference between GENMAC 2.20 and 2.21, is that in 2.21, they left out some of the windows drivers that they couldn't get permission to include. ArcaOS did the same thing, but they also pulled the GENMAC drivers for devices that are now supported by the MultiMac project. Unsupported devices are supported in exactly the same way in both cases. Sometimes they work, and often they don't. System loading seems to have a large effect on whether it works, or not, but that seems to be something in GENMAC, and we don't have the source to be able to fix it. It is known that one of the problems is that the windows driver sometimes overwrites the GENMAC configuration. A couple of people tried to fix that, but it didn't work.
On my Intel (Dell) 5100 laptop the wireless led comes on just after genmac reports the driver as loaded.
As i said, mine works perfectly, as if there was no cable attached to a wired NIC (I can assign an IP address, and ping it). There is no way to turn on the radio, which effectively attaches the wire. From what I found out, Linux had a program to do that (using ACPI), but it got replaced by something in the Linux kernel, and I can't find the source any more. It is also obvious that windows uses an add on driver to control the radio. About the only thing I didn't try, was to hard wire a switch to the adapter. Since I already had an external WiFi device, that connects to the wired NIC, and AN was working on a proper driver, I didn't bother trying any more.