"Mark W. Knecht" wrote:
As for the kernel questions, Win4Lin works best if you're using a standard distribution kernel from one of the majors, such as RH or SuSE. In this case you just start using a new kernel instead from NeTraverse that simply replaces the one you have today. In case you've patched your own kernel, then you have to use their patches to rebuild your kernel with Win4Lin support. Right now some folks are having success with this for 3.0 and others are not.
I had some problems using the stock (kernel.org) 2.4.4 kernel patched with the Win4Lin patches, but I got past them. Using "make oldconfig" to set up the compilation configuration file, I got compilation errors from the kernel. So I tried using a clean config file and twiddling it as best I could to get back to where I was, and that worked. No problems now. One other hint: the patched kernel sources do need to be in a directory 2.4.4-Win4Lin (or something like that -- it sets it up for you). Same for the modules. In my case I had to recompile the alsa sound modules to get them to work because they were compiled under a 2.4.4 kernel, and the module loader (insmod, I think) rejected them because of the apparent difference. You can symlink from /usr/src/linux to /usr/src/linux-2.4.4-Win4Lin, and that will help some other programs find what they're looking for. Paul