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
Whereas Win4Lin performance under Linux 2.2.16-22
on my computer calls to my mind words like "snappy",
"smooth", and "fast", Win4Lin performance under
Linux 2.4.2-2 on my computer calls to mind words
like "clumsy", "lurching", and "slow"
This prompts me to speculate that there must be
something specific about Win4Lin that singles it out
for poor treatment in relation to Linux 2.4.2-2
but that does not have such an effect in relation
to Linux 2.2.16-22.
After spending a few hours browsing
a few kernel-related usenet newsgroups,
I have the impression that the transition
from 2.2.x to 2.4.x brought with it
a radically new if not altogether well-defined
and well-understood approach to
how "virtual memory" is implemented.
This suggests to me that something about
the way Win4Lin handles win386.swp might
might have something to do with the
difference in Win4Lin performance
as between 2.2.16-22 and 2.4.2-2 kernels
that I see on my computer, but when I went
to look for that file I could not find it.
This makes me wonder what would happen
if I told Win98 that I wanted to manage my own
virtual memory using a file of my choice
(a) in my ~/win directory,
(b) on a device mounted under Linux as vfat, or
(c) on a device mounted under Linux as ext2?
Would this be courting disaster?
BillH
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
