- Wine-Devel - list.winehq.org

Messages from 2030 (Laxdragon please read)
by Ivan Leo Puoti Sept. 6, 2005

Sept. 6, 2005

http://www.winehq.com/pipermail/wine-devel/2030-March/000355.html Well, now we all know wineserver will still be around in 2030... Seriously, this should be fixed (not wineserver, the list archive) Ivan.

1 0

ntoskrnl patch, reviews/comments/suggestions wanted
by Ivan Leo Puoti Sept. 6, 2005

Sept. 6, 2005

As Dmitry rightly pointed out, wine-devel is a good place to post stuff for help/comments/review, so here is an (almost) full diff of my tree against cvs. Without going as far as making wineserver a user mode ntoskrnl like mike_m suggested, this code allows kernel mode drivers to work decently in wine, naturally not many have been tested but it's a start. Alexadre's main complaint is that it's ugly to pass handles to ntoskrnl because it's a client process, currently we pass a pointer to a DEVICE_OBJECT, that obviously won't do but we're not sure what would do, suggestions are welcome. secdrv.sys from safedisc 1 works. Some code used to work around the anti debugger checks has been removed, so you can't run safedisc in winedbg with this patch. Running tools/make_requests and a full ./config.status && make depend && make is needed to build this patch. Ivan.

1 0

Some troubles with InstallShield
by Vitaly Lipatov Sept. 6, 2005

Sept. 6, 2005

Can anyone test PHP Expert Editor for install? It uses InstallShield and install loop at message "File access denied." http://www.ankord.com/download/phpxedit_33.zip -- Vitaly Lipatov, ALT Linux Team Russia, Saint-Petersburg, www.etersoft.ru

2 1

fake higher directx version
by Christoph Frick Sept. 5, 2005

Sept. 5, 2005

hiho, i am currently trying rFactor with WINE. the config programm wants dx9C - the current version with the last release version of wine is dx9B. where would i find this so i can fake a higher version? a naïve grep found nothing in my source. -- cu

3 2

Re: kernel32: get ExitProcess to call NtTerminateProcess
by Eric Pouech Sept. 5, 2005

Sept. 5, 2005

Ivan Leo Puoti a écrit : > As NtTerminateProcess alredy exists in ntdll, there's no reason to call > wineserver directly. > > Ivan. I don't see why you need to return something. If NtTerminateProcess() fails, then just call exit(status). A+ -- Eric Pouech

2 1

Some troubles with InstallShield:solved
by Robbert Xerox Sept. 5, 2005

Sept. 5, 2005

Hahaha, Wine is just great, patch that just came in : http://www.winehq.org/pipermail/wine-patches/2005-September/020456.html seems to fix the problem.... ___________________________________________________________ To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. http://uk.security.yahoo.com

1 0

Some troubles with InstallShield
by Robbert Xerox Sept. 5, 2005

Sept. 5, 2005

Using native comctl32 makes the installer proceed; is this also caused by theming patches that got in? See for example http://bugs.winehq.org/show_bug.cgi?id=3241 ___________________________________________________________ How much free photo storage do you get? Store your holiday snaps for FREE with Yahoo! Photos http://uk.photos.yahoo.com

1 0

Re: dinput force feedback header detection
by Daniel Remenak Sept. 5, 2005

Sept. 5, 2005

The patch to fix that error is at http://www.winehq.org/pipermail/wine-patches/attachments/20050903/636b08f6/… The headers are correctly detected but the use of the constants was not protected. --Daniel Remenak On 9/5/05, Jesse Allen <the3dfxdude(a)gmail.com> wrote: > Hi I got this compile error from current cvs: > > make[2]: Entering directory `/home/jesse/.local/build/wine/dlls/dinput' > gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ > -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 > -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o > joystick_linuxinput.o joystick_linuxinput.c > joystick_linuxinput.c: In function `alloc_device': > joystick_linuxinput.c:305: error: `FF_STATUS_STOPPED' undeclared > (first use in this function) > joystick_linuxinput.c:305: error: (Each undeclared identifier is > reported only once > joystick_linuxinput.c:305: error: for each function it appears in.) > joystick_linuxinput.c: In function `joy_polldev': > joystick_linuxinput.c:726: error: `EV_FF_STATUS' undeclared (first use > in this function) > joystick_linuxinput.c: In function `JoystickAImpl_EnumEffects': > joystick_linuxinput.c:1182: warning: unused variable `dei' > joystick_linuxinput.c: In function `JoystickWImpl_EnumEffects': > joystick_linuxinput.c:1266: warning: unused variable `dei' > make[2]: *** [joystick_linuxinput.o] Error 1 > make[2]: Leaving directory `/home/jesse/.local/build/wine/dlls/dinput' > make[1]: *** [dinput] Error 2 > make[1]: Leaving directory `/home/jesse/.local/build/wine/dlls' > make: *** [dlls] Error 2 > > > Apparently the linux/input.h version 2.4.31 does not have support for > force feedback. I've installed headers for 2.6.12.5 and now have it > compiled. So something might need to be done to improve detection, > else others still running 2.4 will get this error. > > Jesse > > >

1 0

dinput force feedback header detection
by Jesse Allen Sept. 5, 2005

Sept. 5, 2005

Hi I got this compile error from current cvs: make[2]: Entering directory `/home/jesse/.local/build/wine/dlls/dinput' gcc -c -I. -I. -I../../include -I../../include -D__WINESRC__ -D_REENTRANT -fPIC -Wall -pipe -mpreferred-stack-boundary=2 -fno-strict-aliasing -gstabs+ -Wpointer-arith -g -O2 -o joystick_linuxinput.o joystick_linuxinput.c joystick_linuxinput.c: In function `alloc_device': joystick_linuxinput.c:305: error: `FF_STATUS_STOPPED' undeclared (first use in this function) joystick_linuxinput.c:305: error: (Each undeclared identifier is reported only once joystick_linuxinput.c:305: error: for each function it appears in.) joystick_linuxinput.c: In function `joy_polldev': joystick_linuxinput.c:726: error: `EV_FF_STATUS' undeclared (first use in this function) joystick_linuxinput.c: In function `JoystickAImpl_EnumEffects': joystick_linuxinput.c:1182: warning: unused variable `dei' joystick_linuxinput.c: In function `JoystickWImpl_EnumEffects': joystick_linuxinput.c:1266: warning: unused variable `dei' make[2]: *** [joystick_linuxinput.o] Error 1 make[2]: Leaving directory `/home/jesse/.local/build/wine/dlls/dinput' make[1]: *** [dinput] Error 2 make[1]: Leaving directory `/home/jesse/.local/build/wine/dlls' make: *** [dlls] Error 2 Apparently the linux/input.h version 2.4.31 does not have support for force feedback. I've installed headers for 2.6.12.5 and now have it compiled. So something might need to be done to improve detection, else others still running 2.4 will get this error. Jesse

1 0

Delphi edit control created in Unicode instead of ANSI mode
by Michael Kaufmann Sept. 5, 2005

Sept. 5, 2005

Hi Frank, One of your theming patches ( http://www.winehq.org/hypermail/wine-cvs/2005/08/0313.html ) has caused a problem in many Delphi applications. The edit controls of Delphi applications are now created in Unicode mode. I hope you have an idea why this happens... Of course Delphi applications are ANSI and expect ANSI controls in their windows. If you believe that this is a real problem, you won't need to read the rest of this email :-) Because the Delphi edit controls are now in Unicode mode, the messages sent to them have to be translated from ANSI to Unicode and back. When a program reads the "Text" property of a TEdit control, Delphi sends a WM_GETTEXTLENGTH message. Wine doubles the return value when translating back from Unicode to ANSI because of double-byte character sets. (dlls/user/winproc.c) Now Delphi gets the doubled text size (should be no problem because WM_GETTEXTLENGTH only returns an upper limit of the text size, but Delphi doesn't regard this fact). Because Delphi does NOT use zero-terminated strings, Delphi will return a string that has twice the size of the text in the edit control and contains a '\0' character. If the application then concatenates this string with another string and passes the result to a Windows API function, the API function will only see the first string because of the '\0' character. I've discovered the problem because installers created by InnoSetup ( http://www.innosetup.com/ ) are now failing. You may use my simple Delphi demo program to test the bug: http://www.michael-kaufmann.ch/WINE/DelphiEdit.zip Regards Michael

2 6