This may have been mentioned before but I have not seen it, so here is the situation. I am running W4L 3.05 under RedHat 7.1. The W4L install was done from a stock RH 7.1 load w/ a 2.4.2-2 kernel. The install went great and everything works. W4L is a really great program. The problem shows up when I boot from the RH 7.1 stock kernel, not the W4L kernel, and allow the /etc/rc.d/init.d/Win4Lin initialization program to run at startup which it does by default. After the system comes up and is running the first 2 or 3 program starts under KDE go fine then program initialization bogs down. It may take 60-90 seconds to open a kvt window. Once the window opens all the tasks internal to the window run fine unless they require another KDE program to start up. I have looked at cpu, memory and swap and all looks good, cpu load <=10%, memory ~120 meg out of 128 meg, and only about 136K of swap used out of 256 meg available. If I prevent the Win4Lin initialization program from running then everything is ok. The same problem occurs if I boot with the win4lin kernel and run Win4Lin initialization even if I don't start Win4Lin. Any suggestions? Jim Blackshear Blackshear Consulting _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
