From owner-freebsd-ports@FreeBSD.ORG Wed May 28 06:08:37 2003 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A64A237B401 for ; Wed, 28 May 2003 06:08:37 -0700 (PDT) Received: from mail.mdacc.tmc.edu (mail.mdanderson.org [143.111.251.38]) by mx1.FreeBSD.org (Postfix) with ESMTP id 10A1A43FB1 for ; Wed, 28 May 2003 06:08:35 -0700 (PDT) (envelope-from syjef@mail.mdanderson.org) Received: from ([143.111.64.231]) by mail.mdacc.tmc.edu (InterScan E-Mail VirusWall Unix); Wed, 28 May 2003 08:08:34 -0500 (CDT) Date: Wed, 28 May 2003 08:08:32 -0500 To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=iso-8859-15; format=flowed From: Jonathan Fosburgh MIME-Version: 1.0 Message-ID: User-Agent: Opera7.11/Linux M2 build 406 Subject: Wine, networking, and XFree86 4.3.0 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 May 2003 13:08:37 -0000 Is anyone able to use any wine applications that communicate over the network *and* are doing so with XFree86 4.3.0? I am running 5.1-BETA, updated from CVS late last week. Prior to that I was on 5.0-R and XFree86 4.2.1. At that time, I was able to use windows applications that communicated over the network, such as Lotus Notes. After upgrading to 5.1, I had some other breakage in wine, and over the course of trying to make wine work again, I upgraded to 4.3.0. Wine seems to be working up to the point where it tries to do any networking, but then the application either goes away or just hangs. For instance, in the case of Lotus Notes, I run the program and get the splash screen, and then it simply exits, leaving me with just the following on my console: fixme:console:SetConsoleCtrlHandler (0x0,0) - no error checking or testing yet fixme:console:SetConsoleCtrlHandler (0xecd6d0,1) - no error checking or testing yet I have seen others having problems with 4.3.0, but I have not discovered a solution. Should I just try to downgrade back to 4.2.1 and see if that helps any? -- Jonathan Fosburgh Software Systems Specialist IV AIX/SAN Administrator University of Texas MD Anderson Cancer Center Houston, TX