April 2004 - Wine-Devel - list.winehq.org

Re: Fix toolbar get style

by Robert Shearman

>>> maxime.bellenge(a)laposte.net 04/29/04 22:59 PM >>> > When a toolbar receives a TB_GETSTYLE message with wParam=0, the > application expects to get the toolbar style and not the first button > style. This patch fixes eMule 0.42e, now the toolbar is visible. > > ChangeLog > * Fix TB_GETSTYLE to return the style of the toolbar when wParam is 0 Good catch, but I think the original author of the TB_GETSTYLE code got a bit confused. I think it should always return the style of the toolbar (according to MSDN) and should print an ERR or FIXME if wParam != 0, as it is reserved. Could you resubmit with that change? Rob

April 29, 2004

Segfault

by Kevin Koltzau

I'm getting segfaults with current cvs, I've tracked it down to this patch http://cvs.winehq.org/patch.py?id=12187 last few lines in a +relay are 0009:Call ntdll.NtCreateKey(bfffcd84,000f003f,bfffe190,00000000,00000000,00000000,00000000) ret=4051e47a 0009:Ret ntdll.NtCreateKey() retval=00000000 ret=4051e47a 0009:Call ntdll.RtlInitUnicodeString(bfffc52c,405d616e L"windows") ret=4051e27f 0009:Ret ntdll.RtlInitUnicodeString() retval=00000000 ret=4051e27f 0009:Call ntdll.NtQueryValueKey(00000010,bfffc52c,00000002,bfffc534,00000800,bfffc528) ret=4051e2be 0009:Ret ntdll.NtQueryValueKey() retval=00000000 ret=4051e2be 0009:Call ntdll.RtlDosPathNameToNtPathName_U(bfffc540 L"c:\\Windows",bfffc49c,00000000,00000000) ret=4053ecd2 Segmentation fault

April 29, 2004

Running NT PPC with wine

by emmanuel maillard

Hi all, I'm looking for people using wine on linuxPPC who want try my patches to run a NT PPC exe. (i plan to reinstall linux/ppc to make my tests but i need to rearrange my HDs before, and it will take times ) This doesn't work for me on MacOSX but this could be due to our port for darwin, this why i need to have feedback from linux/ppc users. PE headers are store in little endian even for an PPC file, so I test endiannes and swap PE infos if needed. For my test i use winimage 3.0 for NT PPC, available here : http://www.winimage.com/download.htm map_image seems good : trace:module:map_image mapped PE file at 0x4f000-0xe5000 Trying to load PE image for unsupported architecture (PowerPC) trace:module:map_image mapping section .text at 0x50000 off 400 size 6c600 flags 60000020 trace:module:map_image mapping section .rdata at 0xbd000 off 6ca00 size 1c00 flags 40000040 trace:module:map_image mapping section .data at 0xbf000 off 6e600 size 3600 flags c0000040 trace:module:map_image clearing 0xc2600 - 0xc3000 trace:module:map_image mapping section .pdata at 0xc8000 off 71c00 size 5c00 flags 40000040 trace:module:map_image mapping section .idata at 0xce000 off 77800 size 3000 flags c0000040 trace:module:map_image mapping section .reldata at 0xd1000 off 7a800 size 200 flags c0000040 trace:module:map_image mapping section .rsrc at 0xd2000 off 7aa00 size e000 flags 40000040 trace:module:map_image mapping section .reloc at 0xe0000 off 88a00 size 5000 flags 42000040 trace:module:do_relocations relocating from 0x400000-0x496000 to 0x4f000-0xe5000 trace:module:do_relocations 1848 relocations for page 6e000 trace:module:do_relocations 816 relocations for page 6f000 trace:module:do_relocations 80 relocations for page 70000 trace:module:do_relocations 40 relocations for page 71000 trace:module:do_relocations 80 relocations for page 72000 trace:module:do_relocations 32 relocations for page 73000 trace:module:do_relocations 1236 relocations for page 79000 trace:module:do_relocations 1240 relocations for page 7a000 trace:module:do_relocations 1240 relocations for page 7b000 trace:module:do_relocations 1236 relocations for page 7c000 trace:module:do_relocations 1240 relocations for page 7d000 trace:module:do_relocations 796 relocations for page 7e000 trace:module:do_relocations 1316 relocations for page 7f000 trace:module:do_relocations 704 relocations for page 80000 trace:module:do_relocations 184 relocations for page 82000 But when process start : .... trace:module:MODULE_InitDLL entry : 0x0(L"WINIMAGE.exe",0x1) - END 0009:Starting process L"F:\\Desktop\\wimapp30\\WINIMAGE.exe" (entryproc=0xbe750) wait few seconds ... wine: Unhandled exception (thread 0009), starting debugger... i test it with mosaic too but failed due to an undefined symbol in iphlpapi.dll "err:module:load_builtin_dll failed to load .so lib for builtin L"iphlpapi.dll": dlcompat: dyld: wine Undefined symbols: _res_9_init" If someone with a Linux/x86 want to launch winimage PPC with +module enable to send me the output to see if my changes give right values it will be helpfull to. Thanks in advance emmanuel the patches (kernel/process.c, ntdll/loader.c, ntdll/virtual.c, server/mapping.c and winedump/pe.c) : full winimage output with +module :

April 29, 2004

Re: Using Windows ODBC drivers

by Florian Wunderlich

Brian Vincent (C) wrote: > > > 5.14.2. Using Windows ODBC drivers > > Does anyone actually have any experience of this and anything to add? > > > > > > I do, with Microsoft Access and the JetProxy JDBC. If there's any > > interest, I can give you a quick summary on how to set things up. > > It looks like the stuff on WineHQ is a bit out of date. > A patch I submitted in March added some info that Boaz > put together. Now that section should read: > > <title>Using Windows ODBC drivers</title> > <para> > Native ODBC drivers have been reported to work for many types of > databases including MSSQL and Oracle. In fact, some like MSSQL > can > only be accessed on Linux through a Winelib app. Rather than > just copying DLL files, most ODBC drivers require a Windows-based > installer to run to properly configure things such as registry > keys. > </para> > <para> > In order to set up MSSQL support you will first need to download > and run the mdac_typ.exe installer from microsoft.com. In > order to > configure your ODBC connections you must then run CLICONFG.EXE and > ODBCAD32.EXE under Wine. You can find them in the windows\system > directory after mdac_typ runs. Compare the output of these > programs > with the output on a native Windows machine. Some things, such > as protocols, may be missing because they rely on being installed > along with the operating system. If so, you may be able to copy > missing functionality from an existing Windows installation as > well as any registry values required. A native Windows > installation > configured to be used by Wine should work the same way it did > when run natively. > > If you'd like to make any additions or corrections, please > work from the version in CVS. If you'd like me to do the > SGML markup, feel free to email me raw text to add. If so, > no rush - I'll be out of town till May 10th. > > Thanks! To be honest, I'm too lazy to get the CVS version, so here's my raw text, which you may want to edit anyway. First of all, I'm working with wine-20040309 from debian-unstable. Using the Microsoft Access ("Jet") ODBC driver from Office 2000 is pretty straight forward. You need the following DllOverrides: "oleaut32" = "native, builtin" "ole32" = "native, builtin" "odbc32" = "native, builtin" "vbajet32" = "native, builtin" "msjet35" = "native, builtin" "msjet40" = "native, builtin" "msjetoledb40" = "native, builtin" Run the control panel using wine windows/control.exe, and configure a new ODBC data source as usual. Done. Be aware that performance really suffers here. Queries run noticeably slower, but you would want this setup for a test system only anyway. Using the Advantage Database Driver (see http://www.extendedsystems.com) is a bit more complicated. I use the same DllOverrides, though obviously this driver does not need overrides for the msjet stuff. The installer works completely under Wine, except for creating the icons at the end - just answer no when asked wether icons should be created. Setting up a data source for the driver works with control.exe too. If you want to connect to a remote Advantage server, you should be done now. If you plan to use the "local server" (file database, like Access mdb files), you have to put the files in a root directory - for example, if you have your .add file and the various .adt and .adi in /var/lib/advantage/mydb, put something like this in your ~/.wine/config: [Drive I] "Path" = "/var/lib/advantage/mydb" "Type" = "hd" "Label" = "mydb" "Filesystem" = "win95" then start control.exe, add a data source for the Advantage driver, and check "Data Dictionary" and "Local Server", uncheck "Remote Server" and "Internet Server", and enter as Database "I:\mydb.add". Don't use just the directory name. Even though the .add file and its friends can be in any directory under Windows, this does not work with Wine. I don't know why - the ODBC driver just complains that you don't have the necessary permissions (even on a FAT filesystem). If you get errors about the collation order in an index not matching your settings then the database you use was created with a local server with a different charset. As there is no mention of the charset of the existing index you have to reinstall the ODBC driver and choose a different charset (first option in the options dialog after the files are copied) until you find the right one. You do not have to uninstall the ODBC driver each time, even though the setup program asks you wether you want to - just overwrite the existing installation and choose a new charset. The performance for this setup is ok. I didn't notice longer query times (yet). As the native Linux ODBC driver for Advantage does not seem to support the "local server", this is the only way to access a local Advantage database under Linux that I know of (JDBC doesn't implement the "local server" either) except using the proprietary API. Even accessing the databases via JDBC is possible, if you feel really adventurous. You can use the JetProxy <http://www.jetools.com/products/jetproxy> running from a JVM inside Wine. To get the j2re-1.4.1_01 java.exe running, you *have* to set "Windows"="winxp" inside you ~/.wine/config [Version] section. Then create a jetproxy.properties as described in the documentation using the jdbc-odbc-bridge (using a CONNECTION_URL like jdbc:odbc:mydb - the DRIVER_CLASS sun.jdbc.odbc.JdbcOdbcDriver picks up the right ODBC DSN automatically). Run the proxy like this: wine -- ../../Java/j2re1.4.1_01/bin/java.exe \ -classpath $LOCALCLASSPATH com.jet.jdbc.server.JETProxyServer \ -config $CONFIG_FILE where $CONFIG_FILE points to the properties file and $LOCALCLASSPATH includes all the jars in the jars directory of the JetProxy. Now you can use any ODBC database - I've tested this with Access and Advantage as described above - from your Java programs. Meaning you have access under Linux to a Microsoft Access database. Good stuff. BTW, the single most useful feature in Wine wouldn't be better support for win32, as most stuff works already anyway, but this [AppDefaults\\appname\\section] functionality universally for all sections. I'm aware that this is probably not such an easy task, but Microsoft Access for example runs fine with "Windows"="win98", but crashes with "winxp", while its the exact opposite with java.exe. Well, I guess you're working on this already anyway. Also, the "ttydrv" GraphicsDriver sucks.

April 29, 2004

Re: RFH: winetest testing

by Eric Pouech

>>It may work if the app would close 0,1,2 and reopen them >>on standard handles > > > Do you mean StdHandles a la Windows? I'm not sure a GUI app > has them. Even if it had, there's no way to convert them > into libc handles or streams AFAIK. a GUI app gets the std-handles its parent requires it to have. then msvcrt on startup will only initialize 0,1,2 to the std-handle if the app is a CUI app (from the PE flag) check out in msvcrt _open_osfhandle to open a msvcrt file descriptor from a kernel32 handle http://msdn.microsoft.com/library/default.asp?url=/library/en-us/vclib/html… >>>In short, I've got the impression that things are working >>>out now (by using some black magic -- ie. winetest being a >>>CUI -- which I don't understand), so maybe we could simply >>>leave it for now. Or do I miss serious issues? >> >>the only point is that we don't have a consistent basis >>across platforms were we start the tests from: >>- all tests programs are CUI exec >>- but, we don't know if it's attached to a console or not > > > A CLI program is attached to a console unless created with > fancy flags, isn't it? it's attached to the parent console, if the parent has a console, and if you don't pass DETACH_CONSOLE as a flag in CreateProcess >Presently I only ask for the window > to be hidden, nothing else. > > >>- if attached to a console, we don't know whether other >>processes are outputting to the same console (which could >>impact the tests...) > > > I never thought of this. If this really can be a problem, > we must solve it, thanks for bringing it up. However I seem > to recall that the console test pops up a separate console, no, they create a console if the process doesn't have one. don't forget that on unix, the test will output to stdout/stderr using the unix streams, even without a console is created, which is rather different from windows were normally the program will output its info on the same console it's run from A+

April 29, 2004

Re: Using Windows ODBC drivers

by Dimitrie O. Paun

On Thu, 29 Apr 2004, Florian Wunderlich wrote: > 5.14.2. Using Windows ODBC drivers > Does anyone actually have any experience of this and anything to add? > > > I do, with Microsoft Access and the JetProxy JDBC. If there's any > interest, I can give you a quick summary on how to set things up. Yes, there is -- if you could provide a patch for section 5.14.2 it would be great. In the past, others have inquired about this issue, so having some documentation on it would be perfect. -- Dimi.

April 29, 2004

Re: Using Windows ODBC drivers

by Brian Vincent (C)

> 5.14.2. Using Windows ODBC drivers > Does anyone actually have any experience of this and anything to add? > > > I do, with Microsoft Access and the JetProxy JDBC. If there's any > interest, I can give you a quick summary on how to set things up. It looks like the stuff on WineHQ is a bit out of date. A patch I submitted in March added some info that Boaz put together. Now that section should read: <title>Using Windows ODBC drivers</title> <para> Native ODBC drivers have been reported to work for many types of databases including MSSQL and Oracle. In fact, some like MSSQL can only be accessed on Linux through a Winelib app. Rather than just copying DLL files, most ODBC drivers require a Windows-based installer to run to properly configure things such as registry keys. </para> <para> In order to set up MSSQL support you will first need to download and run the mdac_typ.exe installer from microsoft.com. In order to configure your ODBC connections you must then run CLICONFG.EXE and ODBCAD32.EXE under Wine. You can find them in the windows\system directory after mdac_typ runs. Compare the output of these programs with the output on a native Windows machine. Some things, such as protocols, may be missing because they rely on being installed along with the operating system. If so, you may be able to copy missing functionality from an existing Windows installation as well as any registry values required. A native Windows installation configured to be used by Wine should work the same way it did when run natively. If you'd like to make any additions or corrections, please work from the version in CVS. If you'd like me to do the SGML markup, feel free to email me raw text to add. If so, no rush - I'll be out of town till May 10th. Thanks! --------------- Brian Vincent Copper Mountain Telecom vincentb(a)coppercolorado.com

April 29, 2004

Re: RegEdit problems

by Krzysztof Foltman

Dimitrie O. Paun wrote: > I was working on it a bit, but I got sidetracked. I have a patch in > the tree for a while now, but I haven't had time to clean it up and > submit. Well, I can try to clean the patch up for you, I guess it could save me a lot of work anyway. Krzysztof

April 29, 2004

Re: wineinstall problems at creatconfig-file

by Saulius Krasuckas

ooph, typo in the subject. was meant to be: wineinstall problems at creation of config-files

April 29, 2004

wineinstall problems at creatconfig-file

by Saulius Krasuckas

CVS Wine of today compiles OK, but at the end of wineinstall script I get some strange output (put below). After that it seems Wine is unable to read ~/.wine/config file. Thus it switches to default Desktop mode ("Desktop" = "640x480") while running any win32|wine app. That makes me feel quiet disappointed. Should I regress-test Wine or have I missed something? There are about 70 MBs of free disk space available for Wine in my box. [s2(a)katleriai wine]$ sh -x tools/wineinstall <skipped /> + echo 'Preparing to install default Wine registry entries...' Preparing to install default Wine registry entries... + '[' '!' -d /home/s2/.wine/dosdevices ']' + echo 'Installing default Wine registry entries...' Installing default Wine registry entries... + echo + programs/rundll32/rundll32 setupapi.dll,InstallHinfSection DefaultInstall 128 tools/wine.inf Line 8: Malformed key '[wine]' Line 8: Error creating key '[wine]' Line 9: Value without key '"Windows" = "c:\\windows"' Line 10: Value without key '"System" = "c:\\windows\\system"' Line 11: Value without key '"Temp" = "e:\\"' Line 12: Value without key '"Path" = "c:\\windows;c:\\windows\\system;e:\\;e:\\test;f:\\"' Line 13: Value without key '"Profile" = "c:\\windows\\Profiles\\Administrator"' Line 14: Value without key '"GraphicsDriver" = "x11drv"' Line 17: Value without key '"ShellLinker" = "wineshelllink"' Line 21: Malformed key '[Version]' Line 21: Error creating key '[Version]' Line 29: Malformed key '[DllOverrides]' Line 29: Error creating key '[DllOverrides]' Line 31: Value without key '"oleaut32" = "builtin, native"' Line 32: Value without key '"ole32" = "builtin, native"' Line 33: Value without key '"comdlg32" = "builtin, native"' Line 34: Value without key '"shell32" = "builtin, native"' Line 35: Value without key '"shfolder" = "builtin, native"' Line 36: Value without key '"shlwapi" = "builtin, native"' Line 37: Value without key '"shdocvw" = "builtin, native"' Line 38: Value without key '"advapi32" = "builtin, native"' Line 39: Value without key '"msvcrt" = "native, builtin"' Line 40: Value without key '"mciavi.drv" = "native, builtin"' Line 41: Value without key '"mcianim.drv" = "native, builtin"' Line 42: Value without key '"msi" = "native, builtin"' Line 49: Value without key '"*" = "builtin, native"' Line 51: Malformed key '[x11drv]' Line 51: Error creating key '[x11drv]' Line 53: Value without key '"AllocSystemColors" = "100"' Line 55: Value without key '"PrivateColorMap" = "N"' Line 57: Value without key '"PerfectGraphics" = "N"' Line 61: Value without key '"Managed" = "Y"' Line 66: Value without key '"UseDGA" = "Y"' Line 68: Value without key '"UseXVidMode" = "Y"' Line 70: Value without key '"UseXRandR" = "Y"' Line 72: Value without key '"UseTakeFocus" = "Y"' Line 74: Value without key '"DXGrab" = "N"' Line 77: Value without key '"DesktopDoubleBuffered" = "N"' Line 93: Malformed key '[fonts]' Line 93: Error creating key '[fonts]' Line 96: Value without key '"Resolution" = "96"' Line 97: Value without key '"Default" = "-adobe-helvetica-"' Line 98: Value without key '"DefaultFixed" = "fixed"' Line 99: Value without key '"DefaultSerif" = "-adobe-times-"' Line 100: Value without key '"DefaultSansSerif" = "-adobe-helvetica-"' Line 114: Malformed key '[FontDirs]' Line 114: Error creating key '[FontDirs]' Line 120: Malformed key '[ppdev]' Line 120: Error creating key '[ppdev]' Line 128: Malformed key '[spooler]' Line 128: Error creating key '[spooler]' Line 129: Value without key '"FILE:" = "tmp.ps"' Line 130: Value without key '"LPT1:" = "|lpr"' Line 131: Value without key '"LPT2:" = "|gs -sDEVICE=bj200 -sOutputFile=/tmp/fred -q -"' Line 132: Value without key '"LPT3:" = "/dev/lp3"' Line 134: Malformed key '[ports]' Line 134: Error creating key '[ports]' Line 138: Malformed key '[Debug]' Line 138: Error creating key '[Debug]' Line 146: Malformed key '[registry]' Line 146: Error creating key '[registry]' Line 152: Value without key '"LoadGlobalRegistryFiles" = "Y"' Line 154: Value without key '"LoadHomeRegistryFiles" = "Y"' Line 156: Value without key '"LoadWindowsRegistryFiles" = "Y"' Line 158: Value without key '"WritetoHomeRegistryFiles" = "Y"' Line 162: Value without key '"SaveOnlyUpdatedKeys" = "Y"' Line 164: Malformed key '[Clipboard]' Line 164: Error creating key '[Clipboard]' Line 165: Value without key '"ClearAllSelections" = "0"' Line 166: Value without key '"PersistentSelection" = "1"' Line 167: Value without key '"UsePrimary" = "0"' Line 170: Malformed key '[afmdirs]' Line 170: Error creating key '[afmdirs]' Line 171: Value without key '"1" = "/usr/share/ghostscript/fonts"' Line 172: Value without key '"2" = "/usr/share/a2ps/afm"' Line 173: Value without key '"3" = "/usr/share/enscript"' Line 174: Value without key '"4" = "/usr/X11R6/lib/X11/fonts/Type1"' Line 176: Malformed key '[WinMM]' Line 176: Error creating key '[WinMM]' Line 179: Value without key '"Drivers" = "wineoss.drv" ; default for most common configurations' Line 186: Value without key '"WaveMapper" = "msacm.drv"' Line 187: Value without key '"MidiMapper" = "midimap.drv"' Line 189: Malformed key '[dsound]' Line 189: Error creating key '[dsound]' Line 209: Malformed key '[Network]' Line 209: Error creating key '[Network]' + echo + echo 'Registry entries successfully installed.' Registry entries successfully installed. + '[' yes = auto ']' ++ whoami + '[' s2 = root ']' + '[' -f /tmp/wineinstall.conf ']' + rm -f /tmp/wineinstall.conf + echo + echo 'Installation complete for now. Good luck (this is still alpha software).' Installation complete for now. Good luck (this is still alpha software). + echo 'If you have problems with WINE, please read the documentation first,' If you have problems with WINE, please read the documentation first, + echo 'as many kinds of potential problems are explained there.' as many kinds of potential problems are explained there. + exit 0

April 29, 2004