March 2005 - Wine-devel - list.winehq.org

Re: Drive detection stuff
by Oliver Stieber 04 Mar '05

04 Mar '05

> Ah, so this means that the directory change > notification mechanism > applies to volume notification as well? Or is it > still a somewhat separate > API? > > Nevermind, at least you just told us that this API > exists, so we should > try to get the hal/hotplug/fam stuff integratedf > towards this API. > take a look at how ivman http://ivman.sourceforge.net/ does things. > Andreas Mohr > > Send instant messages to your online friends http://uk.messenger.yahoo.com

1 0

ESD sound support in Wine 20050111
by Kumaran Santhanam 04 Mar '05

04 Mar '05

I found a patch for ESD (Enlightenment Sound Daemon) support in Wine from July 2004. I modified this to work with Wine-20050111 and compiled the wineesd.drv.so driver. This driver works in both Wine and CrossOver 4.1. The patch and instructions are attached to this email. I have been using it for a few weeks and it seems to be working well. It would be great if it could be incorporated into the main Wine tree. Please let me know if you have any questions. Best Regards, Kumaran Wine Enlightenment Sound Daemon support --------------------------------------- [Jul 2004] Original driver code by Zhangrong Huang <hzhr(a)users.sourceforge.net> [Feb 2005] Ported to Wine 20050111 and CrossOver Office Professional 4.1 by Kumaran Santhanam <rhapsody(a)users.sourceforge.net> Instructions: 0) Make sure that esound-devel is installed. 1) Untar Wine-20050111.tar.gz 2) cd wine-20050111 3) patch -p1 <wineesd-20050111.patch 4) autoconf configure.ac >configure 5) ./configure 6) make depend 7) make Binary is built as dlls/winmm/wineesd/wineesd.drv.so

3 2

MSVCRT still hisshandling Exception
by Uwe Bonnes 04 Mar '05

04 Mar '05

Hallo, with a 2.6 kernel, _pn.exe from the Xilinx ISE suite crashes while loading the last process. With native MSVCRT, a message box pops up, reporting the error. With builtin msvcrt, the exception handling loops until a stack overflow happens. Find appended the beginning of the loop. With the second loop, trace:seh:EXC_CallHandler calling handler at 0x77ec1830 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 appears, with the third loop cointaining these lines doubled and so on. Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- fixme:msvcrt:_setmbcp Unreal codepages (e.g. -3) not implemented fixme:ole:CoRegisterMessageFilter stub fixme:process:CreateProcessA BON: App "(null)" cmd ""C:\\ise-6.3\\bin\\nt\\findmgsg.exe"" err:comm:GetCommState tcgetattr or ioctl error 'Invalid argument' err:ole:CoGetClassObject couldn't load InprocServer32 dll C:\windows\system\vbscript.dll fixme:ole:CoCreateInstance no classfactory created for CLSID {3f4daca4-160d-11d2-a8e9-00104b365c9f}, hres is 0x80040150 err:x11drv:X11DRV_CreateWindow invalid window width -19 err:x11drv:X11DRV_CreateWindow invalid window width -19 fixme:msvcrt:MSVCRT__sopen : pmode 0x01b6 ignored trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x76726151 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=44455359 trace:seh:EXC_RtlRaiseException eax=44455355 ebx=b7212480 ecx=b7542c88 edx=ffffffff esi=b7542ca4 edi=b7542c88 trace:seh:EXC_RtlRaiseException ebp=77428a70 esp=77aa09dc cs=0073 ds=007b es=007b fs=003b gs=0033 flags=00010206 trace:seh:EXC_CallHandler calling handler at 0x76774e9f code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x76ccdea5 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661d92b code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661d93d code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661bb36 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661f3e5 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661c926 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661ce51 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661c590 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x76618114 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x45bef5 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402ef3 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402e0a code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402d82 code=c0000005 flags=0 trace:seh:cxx_frame_handler handling C++ exception rec 0x77aa0984 frame 0x77aafce8 trylevel 0 descr 0x6c424f50 nested_frame (nil) exception type: flags 8508c483 destr 0x8a4275c0 handler 0x548d1a47 type info 0xe0831024 trace:seh:EXC_RtlRaiseException code=c0000005 flags=0 addr=0x7732567b trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=e0831024 trace:seh:EXC_RtlRaiseException eax=e0831024 ebx=77345620 ecx=00000000 edx=77eff031 esi=0a90274b edi=00000000 trace:seh:EXC_RtlRaiseException ebp=77aa0234 esp=77aa0198 cs=0073 ds=007b es=007b fs=003b gs=0033 flags=00010202 trace:seh:EXC_CallHandler calling handler at 0x77ec1830 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x76774e9f code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x76ccdea5 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661d92b code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661d93d code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661bb36 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661f3e5 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661c926 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661ce51 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x7661c590 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x76618114 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x45bef5 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402ef3 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402e0a code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 trace:seh:EXC_CallHandler calling handler at 0x6c402d82 code=c0000005 flags=10 trace:seh:cxx_frame_handler handling C++ exception rec 0x77aa0140 frame 0x77aafce8 trylevel 0 descr 0x6c424f50 nested_frame (nil) exception type: flags 5028 destr 0xb7fffb90 handler 0xb7ff49e0 type info 0xb7f38c90 0: code=c0000005 flags=0 addr=0x773256b1 trace:seh:EXC_RtlRaiseException info[0]=00000000 trace:seh:EXC_RtlRaiseException info[1]=244c8b14 trace:seh:EXC_RtlRaiseException eax=7734142d ebx=77345620 ecx=b7fd5140 edx=00000007 esi=244c8b10 edi=00000000 trace:seh:EXC_RtlRaiseException ebp=77a9f9f0 esp=77a9f954 cs=0073 ds=007b es=007b fs=003b gs=0033 flags=00010246 trace:seh:EXC_CallHandler calling handler at 0x77ec1830 code=c0000005 flags=0 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x77ec1830 code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 2 trace:seh:EXC_CallHandler calling handler at 0x76774e9f code=c0000005 flags=10 trace:seh:EXC_CallHandler handler returned 1 ... err:seh:setup_exception stack overflow 212 bytes in thread 0009 eip b7ec7425 esp 779b0f2c stack 0x779b0000-0x77ab0000

1 0

Re: Make QueryServiceConfigW return an empty string for empty dependencies
by James Hawkins 03 Mar '05

03 Mar '05

On Fri, 4 Mar 2005 13:54:34 +1100, Troy Rollo <wine(a)troy.rollo.name> wrote: > QueryServiceConfigW currently returns a NULL pointer for lpDependencies when > there are no dependencies. The documentation states that an empty string has > the same meaning, and at least one application (an MSIEXEC.EXE from the > Office XP CD) will SEGV if this is NULL. Using the empty string avoids this. > > ChangeLog: > Return an empty string for service dependencies when there are no > dependencies, rather than a NULL pointer, which causes some apps > to SEGV. Can you write test cases for this behaviour? -- James Hawkins

1 0

Re: Make QueryServiceConfigW return an empty string for empty dependencies
by James Hawkins 03 Mar '05

03 Mar '05

On Fri, 4 Mar 2005 13:54:34 +1100, Troy Rollo <wine(a)troy.rollo.name> wrote: > QueryServiceConfigW currently returns a NULL pointer for lpDependencies when > there are no dependencies. The documentation states that an empty string has > the same meaning, and at least one application (an MSIEXEC.EXE from the > Office XP CD) will SEGV if this is NULL. Using the empty string avoids this. > > ChangeLog: > Return an empty string for service dependencies when there are no > dependencies, rather than a NULL pointer, which causes some apps > to SEGV. Can you write test cases for this behaviour? -- James Hawkins

1 0

wine-user.pdf feedback 2
by Dan W. 03 Mar '05

03 Mar '05

Okay, now I found what I think is a more serious missing piece of info in wine-user.pdf. In page 20, last paragraph, it says one can start off by modifying the sample config file, which "can be found in the directory 'documentation/samples'... Problem is, I did a file search for 'documentation', and I get like 10 pages of hits I did a file search for samples, and same thing, or worse. In both cases I went through all those instances visually scanning for 'wine' or 'config' and found nothing at all. I know I ought to have the sources somewhere, because when I installed fc2, I said "install everything", and that included sources; but I have no idea where to look for the wine documentation folder. I have to give up on it for now. Far past my bedtime by now, anyways.. ;-) Cheers!

3 2

Re: MSI: Radio Buttons
by Dmitry Timoshkov 03 Mar '05

03 Mar '05

"Ulrich Czekalla" <ulrich.czekalla(a)utoronto.ca> wrote: > + if (control->hwnd) > + { > + WNDPROC oldproc = (WNDPROC) SetWindowLongPtrW(control->hwnd, GWLP_WNDPROC, > + (LONG)MSIRadioGroup_WndProc); Then it's better to cast to LONG_PTR instead of LONG. -- Dmitry.

1 0

Re: [ADVAPI] SetSecurityInfo
by Robert Shearman 03 Mar '05

03 Mar '05

Raphael wrote: >Hi, > > Changelog: > - simple implementation of SetSecurityInfo > >(seems to be needed by War3 frozen throne, cf >http://forums.gentoo.org/viewtopic-t-303306.html?sid=3f962c702ae58ad8902ca8…) > > I have made a few comments on the implementation below: > SRCDIR = @srcdir@ > VPATH = @srcdir@ > MODULE = advapi32.dll >-IMPORTS = kernel32 ntdll >+IMPORTS = winspool kernel32 ntdll > > Should be in DELAYIMPORTS. We don't want to slow down the loading of all applications because of this one uncommon case. >@@ -1418,6 +1422,87 @@ > { > FIXME("(%s) : stub\n", debugstr_w(lpFileName) ); > return TRUE; >+} >+ >+/****************************************************************************** >+ * SetSecurityInfo [ADVAPI32.@] >+ */ >+BOOL WINAPI SetSecurityInfo(HANDLE handle, >+ SE_OBJECT_TYPE ObjectType, >+ SECURITY_INFORMATION SecurityInfo, >+ PSID psidOwner, >+ PSID psidGroup, >+ PACL pDacl, >+ PACL pSacl) >+{ >+ SECURITY_DESCRIPTOR sd; >+ BOOL test; >+ >+ TRACE("(%p, %x, %x, %p, %p, %p, %p) : alomst stub\n", handle, ObjectType, SecurityInfo, psidOwner, psidGroup, pDacl, pSacl); > > Remove the "almost stub" part of it and just print FIXME's for the parts that aren't implemented, otherwise the next person that comes along to this function will spend hours trying to work out what isn't implemented, if they even realise this function is to blame. >+ >+ test = InitializeSecurityDescriptor(&sd, SECURITY_DESCRIPTOR_REVISION); >+ if (!test) return FALSE; >+ >+ if (SecurityInfo & DACL_SECURITY_INFORMATION) { >+ test = SetSecurityDescriptorDacl(&sd, TRUE, pDacl, TRUE); >+ } >+ if (SecurityInfo & SACL_SECURITY_INFORMATION) { >+ test = SetSecurityDescriptorSacl(&sd, TRUE, pSacl, TRUE); >+ } >+ if (SecurityInfo & GROUP_SECURITY_INFORMATION) { >+ if (NULL == psidGroup) { >+ SetLastError( ERROR_INVALID_PARAMETER ); >+ return FALSE; >+ } >+ test = SetSecurityDescriptorGroup(&sd, psidGroup, TRUE); >+ } >+ if (SecurityInfo & OWNER_SECURITY_INFORMATION) { >+ if (NULL == psidOwner) { >+ SetLastError( ERROR_INVALID_PARAMETER ); >+ return FALSE; >+ } >+ test = SetSecurityDescriptorOwner(&sd, psidOwner, TRUE); >+ } >+ >+ switch (ObjectType) { >+ case SE_KERNEL_OBJECT: >+ test = SetKernelObjectSecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_SERVICE: >+ test = SetServiceObjectSecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_REGISTRY_WOW64_32KEY: >+ case SE_REGISTRY_KEY: >+ test = RegSetKeySecurity(handle, SecurityInfo, &sd); >+ break; >+ case SE_LMSHARE: >+ /*test = NetShareSetInfo(handle, SecurityInfo, &sd); TODO: don't exit on netapi */ >+ break; >+ case SE_PRINTER: >+ { >+ PRINTER_INFO_2A pr_info; >+ memset(&pr_info, 0, sizeof(pr_info)); >+ /** maybe we should do GetPrinter before SetSecurityDesc* ? */ >+ test = GetPrinterA(handle, 2, (LPBYTE) &pr_info, 0, NULL); >+ pr_info.pSecurityDescriptor = &sd; >+ test = SetPrinterA(handle, 2, (LPBYTE) &pr_info, PRINTER_CONTROL_SET_STATUS); >+ break; >+ } >+ >+ case SE_FILE_OBJECT: >+ /*SetFileSecurity ? */ >+ case SE_WINDOW_OBJECT: > > Call SetUserObjectSecurity. >+ case SE_DS_OBJECT: >+ case SE_DS_OBJECT_ALL: >+ case SE_PROVIDER_DEFINED_OBJECT: >+ case SE_WMIGUID_OBJECT: >+ case SE_UNKNOWN_OBJECT_TYPE: >+ default: >+ WARN("unsupported ObjectType %d\n", ObjectType); > > Change this to a FIXME. >+ test = TRUE; >+ } >+ >+ return test; > > This function returns a DWORD error code, not a BOOL. > } > > /****************************************************************************** > > Rob

1 0

Re: ntdll: Add NtCreateKey tests
by Alexandre Julliard 03 Mar '05

03 Mar '05

James Hawkins <truiken(a)gmail.com> writes: > What are the steps I need to take to break registry initialisation? I > did wonder how anything in the real win32 registry could be created > though if you can't create a key directly under HKLM or HKU. If this > really does break initialisation, can we implement a different > create_key that has little restrictions and would only be used > internally, or would this just be scrapped entirely? I don't think there's any point in replicating that behavior. I doubt there's any such check on Windows either, it's most likely just a side effect of the way the registry files are "mounted" at different places in the tree. Once we have a proper implementation of RegLoadKey/RegUnloadKey we should get the same behavior automatically. -- Alexandre Julliard julliard(a)winehq.org

1 0

any way to unlink the symbolic link, not its target?
by Kuba Ober 03 Mar '05

03 Mar '05

Hi, I'm using wine to cross compile projects using vc7.1 from a software configuration tool called aegis (http://aegis.sf.net) I'm maintaining a symlinked baseline with source and derived (.obj, .exe, .pdb) files in it. A change only has copies of changed files. So, when the compiler tries to output something, it first tries to unlink the file. But that won't work as wine tries to unlink target of the symlink, instead of the symlink itself. Is there any switch somewhere to revert to deleting the symbolic links, or if not -- what source file should I look into to patch that? Thanks a lot, Kuba Ober

1 0