I have a question about this. One thing I have noticed is that using something like WinAmp while using Win4Lin, for an extended period of time, has actually caused my Xwindows to just stop and go away. *blink*. Just like that, and back to a login screen. I don't see this when I'm using it on a different graphics chipset, like at home, which is NVidia there. At work, it's an 810C I believe. So it's not the best chipset. If I don't use winamp or XMMS..then it's all good and will stay up for a very long period of time. -- Austin Gonyou Systems Architect, CCNA Coremetrics, Inc. Phone: 512-796-9023 email: [EMAIL PROTECTED] > -----Original Message----- > From: Richard Bass [mailto:[EMAIL PROTECTED]] > Sent: Friday, July 06, 2001 11:24 AM > To: [EMAIL PROTECTED] > Subject: [Win4Lin-users] Win4Lin 3.0 performance on 2.4 - the > definitive > answer > > > > > > > I continue to wonder why > > it is that on my computer > > Win4Lin performs so much better > > in the context of Linux 2.2.16-22 > > than it does in the context of Linux 2.4.2-2 > > > > It turns out that the way win4lin hooks into the virtual memory > system for 2.4 had some undesirable side effects that were not > initially visible. This may be because things changed from 2.4.1 > (on which we based the first port) or because the problem just doesn't > always show up. The bottom line is that in some > circumstances the OS ends > up doing a whole heck of a lot of extra (unnecessary) disk > writes in the > name of trying to keep available (stealable) pages available. Don't > get me wrong: this was OUR bug and not a bug in 2.4.X. We have a > fix for this which we were able to put into the win4lin RPM itself > (as opposed to the kernel) and with the fix, performance is > pretty much > back to what it was with 2.2 kernels. > > The fix is in QA. It will be win4lin 3.0.5 (rpm > Win4Lin-5.2.5?). I am not > sure how long it will take for it to get through the QA > cycle, but the good > news is that there is light at the end of the tunnel! There > will be a message > posted to this mailing list as soon as the fix is made available. > > Thanks for everyone's patience. > > Richard <rwb> > -- > Richard W. Bass > Systems Software Architect > NeTraverse, Inc. > mailto: [EMAIL PROTECTED] > _______________________________________________ > Win4Lin-users mailing list > [EMAIL PROTECTED] > https://lists.netraverse.com/mailman/listinfo/win4lin-users > _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
