When booting to Win4Lin, Network Device Control now refuses to open from the desktop. This was the initial problem that caused me to break off installation when I tried using the Netraverse-enabled kernel rpm for my single-processor Athlon configuration. I now have Win4Lin Workstation 5.0 working, but I can't dialup.

When Network Device Control is invoked from the desktop after booting to the stock FC2 kernel, it just opens. (at ordinary user level)

After Network Device Control refused to open, I set up kppp within the Linux part of the Win4Lin environment... it disls up fine, goes to opening pppd, the window with the ISP name and Details/Disconnect buttons shows, and when Details is selected, it shows local and remote IP addresses. Nothing else happens, I can't even ping with it. However, it also does the same thing with the stock FC2 kernel.

This is what happened when I tried opening system-control-network (Network Device Control ) from a terminal window:
[alizard@terrarium alizard]$ /usr/bin/system-control-network
Traceback (most recent call last):
File "/usr/bin/system-control-network", line 52, in ? from netconfpkg import *
File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/__init__.py", line 61, in ?
File "<string>", line 1, in ?
File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/Control.py", line 28, in ?
File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/NC_functions.py", line 78, in ?
File "/usr/src/build/377922-noarch/install/usr/share/system-config-network/netconfpkg/NC_functions.py", line 54, in kernel_version
ValueError: unpack list of wrong size
[alizard@terrarium alizard]$