Jenn's Support Shop

Q: I uninstalled WinPCap and installed a newer version, now I'm not able to boot my soft kernels anymore, and get this instead:
0.090 netw: Configuring INET.
win32eth: Failed to open adapter '???????????????r?????????????????????????????
?????????????????????}?????????????????????????', error 20
0.090 netw: Failed to open Ethernet device driver sfketh unit 0.

A: Manual -> OSE Getting Started -> Environment Preparation -> Network Access in Soft Kernels:
"OSE has been tested with versions 2.3 and 3.0 of WinPCap. Be careful when using alpha or beta versions of WinPCap, experience have shown that these are often unreliable or introduce interface changes (requiring an updated win32eth driver). A working version of WinPCap is included in the OSE release. "
Hint: You can also get around it temporarily by commenting out the lnh/udp in rtose4.conf (usually).

Q: Arrggh, I can't/won't use this WinPCap stuff, but I still need to boot soft kernels. Is there any hope?

A: There is a little-documented way to get around using WinPCap while still having networking on releases 5.1 and up. (Doesn't work as well with 4.x) Find your refsys/rtose/sfk-win32/rtose.mk file and comment out the lines for BSP_ETHERNET and win32eth.o, and add a USE_NETWORK line to include the inetapi network:

USE_NETWORK = inetapi
#DEFINE += -DBSP_ETHERNET
#OBJECTS += win32eth.o

Then "make clean cleanall cleanobj" and "make all" again and your network should be working without WinPCap.

Q: I'm trying to build refsys for OSE5.1 using Eclipse under Windows 2000, and it's not finding the REFSYSROOT properly and causing the builds to fail. They build okay outside of Eclipse, but in Eclipse when you build the target "all" they do this:

rtose.mk:41: /rtose/common_rtose.mk: No such file or directory
make[1]: *** No rule to make target > > > > `/rtose/common_rtose.mk'. Stop.

And editing refsys/environment.mk to point to REFSYSROOT properly as "../.." does not help.

A: In the manual: Eclipse for OSE User's guide -> Configuration -> Using Cygwin on Windows
"\cygwin\bin must be added to the PATH env-variable." The best way to do this is on a global system level, i.e. using My Computer->Properties->Advanced -> Environment Variables. There are other ways to work around this problem, which is specific to Windows 2000, but adding cygwin\bin in your $PATH is the easiest way.