Joel, Did you read the release notes on the Fedora kernal? Here there are: Product : Fedora Core 2 Name : kernel Version : 2.6.8 Release : 1.521 Summary : The Linux kernel (the core of the Linux operating system) Description : The kernel package contains the Linux kernel (vmlinuz), the core of any Linux operating system. The kernel handles the basic functions of the operating system: memory allocation, process allocation, device input and output, etc. --------------------------------------------------------------------- Update Information: This update kernel updates the Fedora Core 2 kernel to version 2.6.8. Included in this new upstream kernel are several fixes on the networking front, including traffic shaping and window scaling fixes. Note: This kernel includes several Execshield cleanups and changes, and as a result programs that make certain restrictive assumptions about the virtual address space (such as Wine) need a different workaround than before. The applications can get the old (legacy) VA layout via the setarch -L option when a recent enough serarch application is in use, in addition there now is a global switch to go to the legacy VA layout: echo 1 > /proc/sys/vm/legacy_va_layout I would recommend disabling exec-shield or following the recommendations from RedHat. Kevin On Sunday 22 August 2004 12:26 pm, Joel Uckelman wrote: > Hi, > > Yesterday I upgraded to kernel 2.6.8 on my Fedora Core 2 system. This > caused a problem with the version of wine I'd been using (20040505), > so I upgraded wine to the current version (20040813). > > The remaining problem is as follows: > > I'm calling wine like this: > > wine start.exe vcbuild.bat > > and vcbuild.bat contains the following: > > set QMAKESPEC=win32-msvc.net > set QTDIR=F:\wine\qt\3.2.1-nc\msvc.net > set PATH=%PATH%;%QTDIR%\bin > > set PATH=F:\wine\msvc++tk2003\bin;%PATH% > set > INCLUDE=F:\wine\msvc++tk2003\include;F:\wine\OpenSSL\include;%INCLUDE% set > LIB=F:\wine\msvc++tk2003\lib;F:\wine\OpenSSL\lib\VC;%LIB% > > qmake > nmake > > This worked fine before, but now runs successfully only as root, and gives > this error for non-root users: > > <snipped> > fixme:exec:ShellExecuteExW32 flags ignored: 0x00000500 > fixme:exec:SHELL_ExecuteW Strange error set by CreateProcess: 203 > fixme:exec:SHELL_ExecuteW Strange error set by CreateProcess: 203 > Application could not be started, or no application associated with the > specifi ed file. > ShellExecuteEx failed: Environment variable not found > > > The fact that it works for root but not for a normal user makes me think > that it's a permissions problem, but I don't see what the relevant > permissions are. Google turns up nothing useful which contains any of these > error strings, so I'm stumped. Any suggestions would be appreciated. > > _______________________________________________ > wine-users mailing list > wine-users@xxxxxxxxxx > http://www.winehq.org/mailman/listinfo/wine-users _______________________________________________ wine-users mailing list wine-users@xxxxxxxxxx http://www.winehq.org/mailman/listinfo/wine-users
