Hello all, I installed Win4Lin v3 yesterday and overall I am very pleased with the product. However, I would like to address a few small issues and perhaps someone can point me in the right direction with these items. I installed the kernel that the installer provided me, and I was pleased that it worked well, but I was very displeased to see that the supposed transparent replacement kernel for my stock RedHat 7.1 2.4.2-2 kernel did not have smbfs support, while the original RedHat provided kernel did have said support built in. So I have found this to be rather lacking and would like to see a 2.4.2-2 kernel that provides smbfs support as soon as possible. It seems that RedHat 7.1 comes with some strict security settings that I am not aware of how to repair, specifically when I try to run Win4Lin in a seperate fullscreen session in VT 8, I get an error stating that a connection to the requested terminal could not be established. I understand that there is a way to rectify this on a session by session basis, but for automation purposes, I would like to be able to do so on a system wide basis. Could someone point me in the right direction on this? Perhaps it is something that should be included in the Win4Lin documentation. It seems that when I am using the VNET option, heavy network activity both on the Linux AND Win4Lin sides of the network adapter causes the Win4Lin side to give up and stall indefinitely. I have not yet been able to track down specifically what situations can / have caused this, but I will look into it more in the coming days and provide more information as it becomes available. Thanks, I look forward to hearing back soon! -- Kevin Murphy Sargon Consulting (609) 688-1711 (Office) (866) 205-4921 (Pager) (908) 468-8703 (Cell Phone) [EMAIL PROTECTED] _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] https://lists.netraverse.com/mailman/listinfo/win4lin-users
