I run a RedHat 7.1 kernel-2.4.2-2 patched with the latest LVM (logical
volume manager). I was happy to note that Win4Lin 3.0 not only works
perfectly with reiserfs as expected, but also on logical partitions in
LVM. This may be no surprise to others, but I had doubts because I
remember reading that previous versions of Win4Lin didn't work even with
reiserfs.
I use the ALSA sound driver to enable full duplex with Speak Freely. I
haven't found an RPM installer for it, so it had to be compiled and
installed from the source tar.gz.
I re-patched my LVM-enabled kernel with the win4lin patch successfully
by carefully following the win4lin pdf documentation. That was a smooth
and easy job. Then I proceeded to install win4lin, which was a success
as well. I selected the VNET method.
Upon completion, the win4lin user installation automatically started a
fresh Win98 session for me. Here comes my first observation that might
be helpful for others.
The IP Problem
I ran winipcfg and noticed that win4lin had acquired a fresh IP address
from my cable internet provider. I could ping it from linux. On linux
ipconfig I still saw my old dynamic IP. If I recall correctly, I was
also able to ping that IP from win4lin. I also successfully pinged
another host out there on the internet from win4lin. However, outside
world had become unreachable from linux.
I opened Win98 network settings and set my IP to 192.168.1.3 (on my home
network, my linux is 192.168.1.1 and my other workstation is
192.168.1.2) and rebooted win4lin. It shut down and never came back. The
console window on which I had started the user installation was hung. As
root, I did a "killall -9 dosexec" and an "ifdown eth0; ifup eth0" which
I had to repeat to successfully reconnect to the internet.
So it seems like win4lin "stole" the cable internet connection from
linux. Should I have used the Winsock method?
The ALSA Problem
The reason for the second issue I had isn't in win4lin itself. The
patched kernel uses its own module tree in /lib/modules/2.4.2-2win4lin,
and the ALSA modules need to be installed there. There were a couple of
glitches here.
The ALSA Makefile.conf needs to know about the new kernel. Change
"moddir" and "kaversion" to "2.4.2-2win4lin" before re-installing ALSA.
If you compiled the kernel in its own directory (e.g.
/usr/src/patched-linux like the manual suggests), do not set
CONFIG_SND_KERNELDIR to point there. Fix the symlink /usr/src/linux
instead. I wonder why RedHat 7.1 doesn't create this link by default.
You can now do a "make clean; make install", follow the rest of the ALSA
installation instructions and have a working sound subsystem again.
The Resolution Problem
I like to use win4lin in 1024x710 resolution. However, if I shut down
Win98 and start it again, the resolution is reset to 800x600. But if I
just restart (Start->Shut Down->Restart with or without pressing shift),
the resolution remains at whatever I chose. So it seems that it's not
Win98 itself changing the setting, it must be win4lin.
This problem I have not solved. Anyone?
I hope this "log" helps somebody. Lots of what I've read on the win4lin
mailing list have helped me.
Cheers,
Antti Kaihola
Ambitone Oy
Helsinki, Finland
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
