Using a vanilla kernel, this would have worked. I've helped 6 people here at
work do temporary installs so they can evaluate W4L, and it's not been a
problem yet. 

-- 
Austin Gonyou
Systems Architect, CCNA
Coremetrics, Inc.
Phone: 512-796-9023
email: [EMAIL PROTECTED] 

> -----Original Message-----
> From: Justin L Gaither [mailto:[EMAIL PROTECTED]]
> Sent: Thursday, June 21, 2001 12:22 AM
> To: win4lin
> Subject: [Win4Lin-users] I finally fix my W4L3 and RH7.1 
> install here is
> how.
> 
> 
> Well after a nasty battle with RH 7.1 and W4L 3.0  I have finally beat
> them into submission and they are playing to gether nicely.  Here are
> the things I found out.
> 
> 1.  Probably the most interesting on is a kernel config problem.  
>       1. I took the stock 2.4.2 kernel that RH installs and 
> applied the patch
> for W4L.  
>       2. I did make xconfig.  Set Virtual Memory to 1G. and 
> HIMEM off, set
> all other options I needed.
>       3. I look at .config and Virtual Memory is still set to 
> 3G!  What? 
> Why?  Well it seems to have a bug in it that does not set this up
> properly.  
>       4. So I edited autoconf.h  for the option manually, did 
> make dep.
>       5. Made the kernel, and installed.
> 2.  I dont know whose idea it was to make W4L allocate 16MB 
> by default,
> but it was stupid.  Windows by itself cant work with 16Mb.  I was an
> idiot for not checking it sooner, but its at 64MB now.
> 3.  After following the thread about the kernel VM problem, I added
> another swapfile  to make sure I have 2x RAMsize for swap.
> 
> I think all is well now.(Knock on wood!)
> 
> justin
> -- 
> Justin Gaither                       Phone: 512-306-7292  x529
> RocketChips a Division of Xilinx     Fax:   512-306-7293
> 500 N. Capital of TX Hwy.
> Bldg 3                         email: [EMAIL PROTECTED]
> Austin, TX 78746               WWW:   www.rocketchips.com
> 
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users

Reply via email to