This is unfortunate. The official 2.2.19 has been released and I'm
running it on my workstations. I wonder if 2.2.19 has the newer 2.4-style
vm architecture changes merged into it. Well, now it seems win4lin no
longer runs on linux 2.2.x at all. (Even win4lin 2.0). I guess I'll just
eat the cost and get win4lin 3.0. It sounds like a great product. If it
can maintain the speed of win4lin 2.0, it will give vmware express a run
for its money. I expect win4lin to last for a good portion of the 2.4.x
kernel series, though. There are bound to be further vm changes. The
hazards of supporting a disjointed open-sourced hacker os. ;) (No flame
bait intended.)
By the way, I've been referring to netraverse wrong. Netraverse is a
company and is referred to in the singular, gender-neutral, it. Not them.
Them is they that work at netraverse. ;) Some day I'll be able to speak
properly.
Michael
On Fri, 6 Apr 2001, Tim Bell wrote:
> On Thu 05 Apr 2001 at 18:35:41 +1000, I wrote:
> > On Thu 29 Mar 2001 at 17:57:00 +0200, Rein Klazes wrote:
> >
> > > Did any one succeed to get win4lin working with kernel 2.2.19?
> >
> > No, it didn't work for me either. It broke somewhere in the 2.2.19pre
> > cycle, although I don't know where.
>
> I've just confirmed that win4lin doesn't work with either 2.2.19pre1 or
> 2.2.19pre2. My guess is that it's something to do with Andrea
> Arcangeli's VM-global patch, which went into 2.2.19pre2. (2.2.19pre1
> had some different VM changes, which were backed out in 2.2.19pre1, and
> I suppose those broke win4lin as well.)
>
> Tim.
>
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
