For anyone considering running Win4Lin on Mandrake, here is a post that mentions a few problems to lookOut for. Ralph --- Date: Mon, 31 Jul 2000 13:25:22 -0700 From: David Peet <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Win4Lin-users] Outlook 2000 and Win4Lin Problem "Zaleski, Matthew (M.E.)" wrote: > Well, I bought win4lin last week and got it installed over the weekend. I > fought my way through the incompatibilities between Mandrake 7.1 and win4lin > (the win4lin patch puts src files in the wrong location). I then discovered > that win4lin doesn't like ReiserFS at all. I tried symbolic links from the > win4lin dirs in /opt and /var to a ext2 partition. No go. I reinstalled > LM7.1 with only ext2, patched the kernel, moved the src files to the correct > location. The most critical part is that the $HOME/win directory cannot be on a Reiser FS. And /var/win4lin also should not be on a Reiser FS. /opt/win4lin should not matter. So all you should have needed was to do symbolic links for $HOME/win and /var/win4lin into an ext2 partitiostn. The problem with the ReiserFS is that win4lin does a "statfs" on the filesystem to make sure there is space to create some critical files, and statfs reports that there is no more free space or there are no more free inodes. Typically this only happens on a read-only filesystem or one that is truely out of space. The Win4Lin code takes this at face value and aborts the session startup. The ReiserFS developer(s) need to fix this. > Now, at least, I could install win4lin and create the initial Windows image > on the Linux box. I used my MSDN subscription copy of Win98se. The next > problem is that win4lin strips the burned-in serial # that the MSDN CD had. > I got lucky and found the correct serial # in a previous MSDN Windows > install. Win4Lin uses it's own msbatch.inf file to install Windows. On the MSDN the product ID is in a msbatch.inf file. So it is not so much "stripped", as it is just 'not used'. You can look on the MSDN CD and read the msbatch.inf file to find out the "ProductKey". > After that I had very god luck getting a pile of development software > installed plus Office 2000. The hiccup came with Outlook 2000. We run MS > Exchange NT servers here for all our email and calendaring requirements. > Under VMWare, Outlook (while starting) would display a NT domain logon box > requiring userid, domain, and password. Under win4lin, Outlook hangs. It > appears packets are flying across the network (hard to prove unless there is > a diagnostic mode in win4lin I can check). But the appropriate response > never comes. > > Any ideas on what the problem might be? I was assuming it would work since > I DON'T do a domain login during my VMWare bootup. What could the Outlook > domain login need that isn't provided in winsock.dll? > > Matthew Zaleski Using Outlook with an MS Exchange server *currently* does not work. It apparently does not use winsock for some of it's communication, or uses secret protocol extentions. Hopefully this will be fixed in a later version of Win4Lin. Note: Outlook can be used with a normal POP or IMAP mail server. -David Peet _______________________________________________ Win4Lin-users mailing list [EMAIL PROTECTED] http://lists.trelos.com/mailman/listinfo/win4lin-users
