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

text edit box not painting text ( on form startup )
by Doug Herbert March 9, 2005

March 9, 2005

( I have posted a similiar question in wine-users, don't flame me for doing so, just thinking about this some more, perhaps it may be more a developer question ) Ok, I have a windows app, that runs under wine fine - not quite. This app has a form, with many text field edit boxes on. Quite often these edit boxes already have text values, ie. they are not empty - there is a database behind the form. Anyway, the form shows on the screen, but the text within the edit fields is invisible, until you activate each edit box component. When you leave one edit box to the next, the text remains visible. It seems like the repainting is not working, on initial startup of the form. As a way to debug this database app ( I don't have the source code for it ) I wrote a real basic form app in Visual Studio, with two edit boxes, with data in each. Now this basic app shows the text values immediately on startup. So there must be something different that the database app is not doing. I then ran wine using 'wine --debugmsg +edit programname' for both app's. I see both logging 'Creating ANSI edit control, style = xxxxx' but the style reference is different between apps - I am not sure if this the cause or not. The problem app reports style = 54011104 and the basic app shows style = 50010080. Can somebody explain what this style reference means and how do I force an app to use a certain style of edit box ? What other wine class debugmsg types should I use to narrow down the source of this problem ? Is there anyway I can check to see how the database app is repainting text within the text edit components ? Regards Doug Herbert. __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free, easy-to-use web site design software http://sitebuilder.yahoo.com

3 4

Precompiled headers?
by Shachar Shemesh July 5, 2004

July 5, 2004

Hi, Is anyone considering putting precompiled headers support into the wine build system? http://gcc.gnu.org/onlinedocs/gcc/Precompiled-Headers.html#Precompiled%20He… -- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/

2 1

Re: Ukrainian translation
by Dmitry Timoshkov May 5, 2004

May 5, 2004

"Ylia K" <k_ilya(a)ukr.net> wrote: > * dlls/kernel/nls/ukr.nls, dlls/comctl32/rsrc.rc, dlls/commdlg/rsrc.rc, dlls/user/resources/user32.rc, dlls/shell32/shres.rc, > dlls/comctl32/comctl_Uk.rc, dlls/commdlg/cdlg_Uk.rc, dlls/shell32/shell32_Uk.rc, dlls/user/resources/user32_Uk.rc : > > Ilya Korniyko <k_ilya(a)ukr.net> > > Ukrainian translation: full translation of comclt32, commdlg, shel32, user dlls, fixes in ukr.nls You shouldn't touch ukr.nls since it has been auto generated. -- Dmitry.

2 4

Re: Using Windows ODBC drivers
by Brian Vincent (C) May 3, 2004

May 3, 2004

> 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

3 2

Printing problem; RHEL3U1 (CUPS) with 20031118
by Bill Medland May 3, 2004

May 3, 2004

(Yes, I know 20031118 is a little old) Anyone any ideas what is going on here or any simple tests I can do? I am trying to get our company's software running on Red Hat Enterprise Linux 3 Update 1. I am using the wine-20031118-1rh8winehq.i686.rpm I am printing to a SMB printer elsewhere on the computer. I can print the test page from the printconfgui I can print a text file from the command line (lp /etc/passwd) I cannot print from notepad; nothing seems to happen I cannot print from our application; I get the error: lpr: unable to print file: server-error-service-unavailable (I'll try the 20040408 when I can actually download it, but I don't expect it to change) (I would try changing to LPRng but of course RHEL3 doesn't seem to include it) Anyone any ideas? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

3 7

winelib application taking 100% of the CPU
by Scott W Gifford May 3, 2004

May 3, 2004

Hello, I recently ported a small application from Windows using winelib. The app uses a third-party DLL that I don't have source for (which is why I'm using winelib instead of just writing a Unix program). It seems to work fine, but it takes up 100% of the CPU all the time: 24916 activewv 25 0 1080 1080 920 R 50.2 0.2 44:06 0 wineserver 24938 activewv 16 0 0 0 0 Z 24.5 0.0 3:52 0 wine-pthread <defunct> 24913 activewv 15 0 0 0 0 Z 24.1 0.0 17:38 0 wine-pthread <defunct> Also Linux claims that the two threads of the program are zombies, and are taking up 25% of the CPU, which doesn't really make any sense. The app isn't CPU-intensive under Windows. The app is just sending a short request to the serial port every 5-10 seconds, and sometimes getting back a short response. When I strace wineserver, it's doing: 31132 poll([{fd=5, events=POLLIN}, {fd=4, events=POLLIN}, {fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=13, events=POLLIN}, {fd=15, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=16, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=17, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=28, events=POLLIN}, {fd=-1}, { fd=-1}, {fd=-1}, {fd=32, events=0, revents=POLLERR|POLLHUP}, {fd=33, events=POLLIN, revents=POLLIN}, {fd=-1}, {fd=-1}, {fd=36, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=18, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=44, events=0, revents=POLLERR|POLLHUP}, {fd=45, events=POLLIN, revents=POLLIN}, {fd=-1}, {fd=-1}, {fd=48, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=24, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=56, events=POLLIN}, {fd=57, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=60, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=63, events=POLLIN}, {fd=64, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {fd=-1}, {! fd=71, events=POLLIN}, {fd=72, events=POLLIN}, {fd=-1}, {fd=-1}, {fd=75, events=POLLIN}, {fd=-1}, {fd=-1}], 69, -1) = 4 31132 read(33, "&\0\0\0\0\0\0\0\0\0\0\0L\0\0\0\0\0\0@\0\0\0\0\0\0\0\0\0"..., 64) = 64 31132 write(34, "\0\0\0\0\0\0\0\0\t\0\0\0\1\0\0\0\1\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 31132 read(45, "\25\0\0\0\0\0\0\0\0\0\0\0l\0\0\0\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 31132 write(46, "\0\0\0\0\0\0\0\0\377\377\377\377\0\0\0\0\0\0\0\0\0\0\0"..., 64) = 64 Those file descriptors are all pipes according to lsof, and I'm not sure what they're connected to---although it seems likely they're connected to those two threads, especially since those are the only threads this copy of wineserver is servicing. I'm not really sure how to go about figuring this out; I'm about to port another similar application, and I'd prefer not to have both of them trying to get the CPU all the time. This is with Wine-20040309, compiled myself for a Fedora Core Release 1 (Yarrow) Linux. I'm not really sure what my next step is in figuring this out. Any ideas? Thanks! ----ScottG.

3 5

d3d8 CVS doesn't compile
by Ferenc Wagner May 2, 2004

May 2, 2004

Hi, this is with current CVS: ../../tools/winegcc/winegcc -B../../tools/winebuild -shared ../../../src/dlls/d3d8/d3d8.spec basetexture.o cubetexture.o d3d8_main.o device.o directx.o drawprim.o indexbuffer.o resource.o shader.o stateblock.o surface.o swapchain.o texture.o utils.o vertexbuffer.o volume.o volumetexture.o vshaderdeclaration.o d3d8.dll.dbg.o version.res -o d3d8.dll.so -L../../dlls -luser32 -lgdi32 -lkernel32 -ladvapi32 -L../../libs/wine -lwine -ldxguid -luuid -L/usr/X11R6/lib -lSM -lICE -lXxf86dga -lXxf86vm -lXv -lXext -lX11 -lGL -lGLU -L../../libs/port -lwine_port surface.o: In function `IDirect3DSurface8Impl_LoadTexture': /usr/local/src/wine/elf/dlls/d3d8/../../../src/dlls/d3d8/surface.c:577: undefined reference to `glCompressedTexImage2D' collect2: ld returned 1 exit status winegcc: gcc failed. make[2]: *** [d3d8.dll.so] Error 2 make[2]: Leaving directory `/usr/local/src/wine/elf/dlls/d3d8' I could only find glCompressedTexImage2DARB in my glext.h (SGI OpenGL 1.2.1). Any clues? -- Thanks, Feri.

5 6

Marlett Replacement Useful for Wine?
by Robert Shearman May 1, 2004

May 1, 2004

Hi all, I have several people interested in creating a replacement for the Marlett symbol font included in Windows (used for drawing of window decorations and some widgets). Would this be useful for inclusion in Wine? If so, would just the TTF file be ok, or would you need whatever propietary formatted file they will probably be working with (I think it will be some Adobe product)? Rob

5 4

Linking with 3rd party DLLs
by Scott W Gifford April 30, 2004

April 30, 2004

I'm working on two apps that link to 3rd party DLLs. For both DLLs, I have a .dll file and a .lib file, but no .def. For the first app, in order to get things working I had to load all of the functions myself with GetProcAddress. That worked fine, but was tedious to set up. I know there's a better way, but nothing I've tried has worked. I tried to create a .spec file, compile to a .def file, and link with that. If I copy ActiveWaveLib.dll to libActiveWaveLib.dll, create an ActiveWaveLib.spec file, compile that with winebuild to libActiveWaveLib.def, then compile with: wineg++ ... -lActiveWaveLib it compiles, but when I run it complains: err:module:import_dll No implementation for ActiveWaveLib.dll.rfCallTags imported from L"Z:\\home\\gifford\\prog\\activewave-test\\activewave.exe", setting to 0xdeadbeef If I instead use: wineg++ ... -iActiveWaveLib it won't compile: activewave.o(.text+0xce): In function `main': : warning: undefined reference to `rfRegisterReaderEvent' Any idea what I'm doing wrong, or what else I can try? Thanks! ----ScottG.

1 0

downloading binaries
by Bill Medland April 30, 2004

April 30, 2004

Am I being some sort of an idiot? I can't download binaries. Is it something I am doing, my network or have they messed things up? I am trying to download a RedHat 8.0 binary package from SourceForge I select the one I want It redirects to the page asking which mirror I want. It just sits there. In the very old days it would automatically start the download In the old days there would be a link to select if the download didn't start;I tended to use it. Now it doesn't start and there is no link any longer. Anyone any idea what is going on? -- Bill Medland mailto:billmedland(a)mercuryspeed.com http://webhome.idirect.com/~kbmed

2 2

wineserver not reading config files
by Saulius Krasuckas April 30, 2004

April 30, 2004

(Subject was: wineinstall problems at creation of config-files) Ok, today I got less lazy and found function of interest: /usr/src/wine-cvs/wine/server/registry.c:1114: fprintf( stderr, "Line %d: %s '%s'\n", info->line, err, info->buffer ); Function name seems to be "file_read_error". Plainly running /usr/local/bin/wineserver shows Line-errors, but killing it (via winserver -k) and running it via gdb stops emitting mentioned Line-errors to output: [s2(a)katleriai s2]$ gdb --quiet /usr/local/bin/wineserver (gdb) break file_read_error Breakpoint 1 at 0x805b91e: file registry.c, line 1114. (gdb) r Starting program: /usr/local/bin/wineserver Program exited with code 02. (gdb) Maybe there is some complex methods on debugging wineserver's binary? I am asking for help on that. PS I had refreshed src from the CVS and recompiled Wine before trying to debug it.

3 6

Segfault
by Kevin Koltzau April 30, 2004

April 30, 2004

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

2 7

RE: Fix toolbar get style
by Ge van Geldorp April 30, 2004

April 30, 2004

> From: Maxime Bellengé > > 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 It seems there is another problem with the toolbar styles. When you CreateToolbarEx() with the WS_VISIBLE bit turned on, TOOLBAR_Create() will call GetWindowLongW() to get the window style and store that as the dwStyle member of TOOLBAR_INFO. Unfortunately, when the WM_CREATE message is sent the WS_VISIBLE bit of the window style retrieved with GetWindowLongW() is always turned off. It is turned on a little bit later, but no WS_STYLECHANGED is sent for this. So, the dwStyle member of TOOLBAR_INFO doesn't always mimick the "true" window style, it is possible that the WS_VISIBLE bit is off in TOOLBAR_INFO but on in the window style. If your app does something like: SendMessage(hwndTB, TB_SETSTYLE, 0, SendMessage(hwndTB, TB_GETSTYLE, 0, 0) | TBSTYLE_FLAT ); this will make your toolbar invisible. Gé van Geldorp.

2 1

Running NT PPC with wine
by emmanuel maillard April 30, 2004

April 30, 2004

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 :

1 1

Re: Fix toolbar get style
by maxime.bellenge＠laposte.net April 30, 2004

April 30, 2004

> >>> 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 > Hello I will perform some tests under win xp to check this behaviour because even if the author may have been confused. I think it is worth testing that. I will then send another patch. a+ Max Accédez au courrier électronique de La Poste : www.laposte.net ; 3615 LAPOSTENET (0,34/mn) ; tél : 08 92 68 13 50 (0,34/mn)

1 0

wineinstall problems at creatconfig-file
by Saulius Krasuckas April 29, 2004

April 29, 2004

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

1 2

Re: Fix toolbar get style
by Robert Shearman April 29, 2004

April 29, 2004

>>> 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

1 0

RFH: winetest testing
by Dimitrie O. Paun April 29, 2004

April 29, 2004

Folks, Can you please run this .exe on your Windows box: http://afavant.elte.hu/~wferi/wine/winetest.exe We are trying to test the winetest infrastructure. TIA! -- Dimi.

15 47

Re: Using Windows ODBC drivers
by Dimitrie O. Paun April 29, 2004

April 29, 2004

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.

1 0

RegEdit problems
by Krzysztof Foltman April 29, 2004

April 29, 2004

During deployment of some Linux desktop setup I had a major problem with WINE's regedit. First, I don't seem to be able to edit the (default) values of the keys (if they don't exist already ?). Second, the Modify dialog has Cancel as its default button. Third, there is no Find function. There are also some weird error messages in unexpected places. Is anybody working on it, or should I try it ? Using native regedit is not an option, as our goal is to avoid being a BSA victim completely. Krzysztof (who can't continue the RichEdit before getting the damn desktop to work)

3 3

Re: Re: CVS Invalid path for c:\\Windows
by brettholcomb＠charter.net April 29, 2004

April 29, 2004

Arrghh! I'll do that. Thank you. Can the message be updated to tell us to look at the dosdevices directory. > > From: Alexandre Julliard <julliard(a)winehq.org> > Date: 2004/04/29 Thu AM 02:02:21 GMT > To: "Brett I. Holcomb" <brettholcomb(a)charter.net> > CC: wine-devel(a)winehq.com > Subject: Re: CVS Invalid path for c:\\Windows > > "Brett I. Holcomb" <brettholcomb(a)charter.net> writes: > > > Yes. I just did again and it doesn't work. Same error. Something got > > broken again I guess. > > Path entries from the config file are no longer used. Check the > contents of your ~/.wine/dosdevices directory. > > -- > Alexandre Julliard > julliard(a)winehq.org >

1 0

Conversion between Clipboard Formats
by Santosh Siddheshwar April 29, 2004

April 29, 2004

Hi, Does WINE support automatic type conversion between certain kinds of clipboard formats? For e.g. between CF_TEXT and CF_UNICODETEXT and similar types of conversions? Any inputs would be appreciated Regards Santosh Siddheshwar ********************************************************************* Disclaimer: The information in this e-mail and any attachments is confidential / privileged. It is intended solely for the addressee or addressees. If you are not the addressee indicated in this message, you may not copy or deliver this message to anyone. In such case, you should destroy this message and kindly notify the sender by reply email. Please advise immediately if you or your employer does not consent to Internet email for messages of this kind. *********************************************************************

2 1

Re: SetCalendarInfoA and SetCalendarInfoW implementations
by Stefan Leichter April 29, 2004

April 29, 2004

Am Mittwoch, 28. April 2004 22:38 schrieb Wililam: > I have implemented the SetCalendarInfoA and SetCalendarInfoW API > functions in dlls/kernel/time.c. I am aware that you generally do not like > it when more than 1 thing is changed, but SetCalendarInfoA is not much more > than a > call to SetCalendarInfoW. I am also curious as to why both functions were > listed > as stdcalls rather than stubs when they were both stubs in the source file. > > I have enclosed the patch for the file against the latest source package. > > Here is the ChangeLog entry (I didn't patch the ChangeLog file): > > * dlls/kernel/time.c > William Lahti <computerman413(a)ezrs.com> > > - Implemented the SetCalendarInfoA and SetCalendarInfoW APIs. > > Sincerely yours, > > William Lahti Hello, for my limited understanding you need to convert lpCalData from ascii to unixode in SetCalendarInfoA before calling SetCalendarInfoW Bye Stefan

1 0

how can i solve this problem???
by Falcifer April 28, 2004

April 28, 2004

fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,2)-stub! fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,3)-stub! fixme:hook:NotifyWinEvent (32774,0x20049,-4,1)-stub! X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 73 (X_GetImage) Serial number of failed request: 21212 Current serial number in output stream: 21212 fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,2)-stub! fixme:nls:CompareStringW Ignoring unknown style 0x10000000 fixme:hook:NotifyWinEvent (32768,0x20049,-4,3)-stub! fixme:hook:NotifyWinEvent (32774,0x20049,-4,1)-stub! X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 73 (X_GetImage) Serial number of failed request: 21212 Current serial number in output stream: 21212 ----------------------------------------------------------------------------------- Any clue?? Its very important cause if i can run this corporative application in Linux all the firm will migrate gradually to Linux. Thanks

1 0

CVS Invalid path for c:\\Windows
by Brett I. Holcomb April 28, 2004

April 28, 2004

I installed from CVS today and when I start wine I get the error below. This happens even with the standard config file that it creates. I've check both my and the config file and can't find any errors. I'm including the c drive part of the config file. Any ideas why this is telling me this? Thanks. Error: Invalid path L"c:\\Windows" for L"windows" directory: does not exist. Perhaps you have not properly edited your Wine configuration file (/home/brett/.wine-cvs/config) Config file excerptL [Drive C] "Path" = "fake_windows" "Type" = "hd" "Label" = "MS-DOS" "Filesystem" = "win95" -- Brett I. Holcomb

3 4

[PATCH] Exception c0000005 opening JPEG files in FoxPro
by Sergio López April 28, 2004

April 28, 2004

Hello, When Visual FoxPro (tested with versions 6 and 7, wine-20040408) tries to open a JPEG file, it crash showing a c0000005 exception. The backtrace of winedbg shows the following API calls: 0 0x407c0e1d (CURSORICON_SimulateLoadingFromResourceW+0x8d(filename=0x403e63b0, fCursor=0x1, res=0x4074a208, ptr=0x4074a20c) [cursoricon.c:512] in USER32.DLL) (ebp=4074a1d0) 1 0x407c1d0d (CURSORICON_Load+0x28d(hInstance=0x0, name=0x403e63b0, width=0x20, height=0x20, colors=0x1, fCursor=0x1, loadflags=0x50) [cursoricon.c:799] in USER32.DLL) (ebp=4074a21c) 2 0x407c4ba0 (LoadImageW+0xb0(hinst=0x0, name=0x403e63b0, type=0x2, desiredx=0x20, desiredy=0x20, loadflags=0x50) [cursoricon.c:2133] in USER32.DLL) (ebp=4074a258) 3 0x407c4a8f (LoadImageA+0x14f(hinst=0x0, name=0x4074a370, type=0x2, desiredx=0x0, desiredy=0x0, loadflags=0x50) [cursoricon.c:2074] in USER32.DLL) (ebp=4074a334) 4 0x407c39b5 (LoadCursorFromFileA+0x45(name=0x4074a370) [cursoricon.c:1649] in USER32.DLL) (ebp=4074a358) 5 0x0053b8c5 (vfp7.exe.EntryPoint+0x13a8c5 in vfp7.exe) (ebp=4074a5e8) 6 0x00490d4b (vfp7.exe.EntryPoint+0x8fd4b in vfp7.exe) (ebp=4074a78c) 7 0x004abd03 (vfp7.exe.EntryPoint+0xaad03 in vfp7.exe) (ebp=4074a928) 8 0x00436a8d (vfp7.exe.EntryPoint+0x35a8d in vfp7.exe) (ebp=0000002b) The last function (CURSORICON_Simulate...) has a bug that makes the exception when the opened file isn't in RIFF format. Returning with fail when the file is in other format avoids the exception, and Visual FoxPro continue the execution loading correctly the image. Best regards, -- Sergio López koro(a)menteslibres.org

1 0

Re: SetCalendarInfoA and SetCalendarInfoW implementations
by Vincent Béron April 28, 2004

April 28, 2004

Le mer 28/04/2004 à 16:38, Wililam a écrit : > I have implemented the SetCalendarInfoA and SetCalendarInfoW API > functions in dlls/kernel/time.c. I am aware that you generally do not like it > when more than 1 thing is changed, but SetCalendarInfoA is not much more than > a > call to SetCalendarInfoW. I am also curious as to why both functions were > listed > as stdcalls rather than stubs when they were both stubs in the source file. There are two levels of stubs: "real stubs", and dummy functions. stub is used in a spec file when there's no implementation whatsoever of a given function, not even a dummy one. If an app tries to use that function, it results in a segmentation fault (and usually a crash to the debugger). In the case of SetCalendarInfo{A,W}, some dummy function existed, so they were callable by an app without it crashing (hence the stdcall declaration). Of course it wouldn't actually do much, that's what your implementation is for. The "stub" in the FIXME is to remind people that some function is not really there, although it's been called. The line is difficult to draw between the two types of stub: some apps will crash with a real stub and need a dummy one, some other ones will crash with a dummy one and will route around real stubs. Usually it's done on a case by case basis. > > I have enclosed the patch for the file against the latest source package. > > Here is the ChangeLog entry (I didn't patch the ChangeLog file): Alexandre commits all the changelog entries to the ChangeLog file when there's a release. Your way to specify the changelog is the correct one. Vincent

1 0

Re: [Darwine] compiling wine on Darwin/MacOS X 4/10
by Pierre d'Herbemont April 28, 2004

April 28, 2004

Emmanuel, I know that I did this hack, but it is not really a good one. Since it corrupts the stack (you get a stack frame error at every signal caught). So this issue would need to be a bit more investigated. But it is required for now, without it you can't launch an App. Pierre PS: its good to see that someone takes time to send those patches and work ;) So thanks for that. On 15 avr. 04, at 23:36, emmanuel maillard wrote: > Hi, > > an other patch for darwin/ppc > > changelog > Add darwin/ppc support in THREAD_InitStack > > emmanuel > > <kernel_thread.diff>

2 1

Re: [D3D8] Many Improvements
by Duane Clark April 28, 2004

April 28, 2004

This commit to CVS doesn't compile for me: http://www.winehq.org/hypermail/wine-cvs/2004/04/0346.html The part the doesn't compile is the replacement of glCompressedTexImage2DARB() - glCompressedTexImage2DARB(gl_target, - ... + glCompressedTexImage2D(gl_target, + ... The old name compiled fine for me; changing it back fixes the compile. This is on RH7.3.

2 1

Re: exec-shield patch take 6
by Mike Hearn April 28, 2004

April 28, 2004

Go Mike! Good to see this work finally turn into a patch against CVS :) On Wed, 2004-04-28 at 19:02 +0900, Mike McCormack wrote: > Description: > > This patch allows platforms using exec-shield patch against the Linux > kernel (eg. Fedora Core) to run Wine without disabling exec-shield. It also fixes the prelink case, right? :) > + vars.pe_size = 0x01000000; 0x1000000? Are you sure you didn't drop a zero somewhere? That's only 16mb.... we probably want something like 0x40000000 which reserves a gig of address space. Some very large game installers can in fact get close to this level, and as it's just non-backed address space we're reserving (for a shor time) there's no real reason to be stingy. > +/* > + * The _start function is the entry and exit point of this program > + * > + * It calls wld_start, passing a pointer to the args it receives > + * then jumps to the address wld_start returns after removing the > + * first argv[] value, and decrementing argc > + */ > +void _start(void); > +__asm ( > + ".align 4\n" > + "\t.global _start\n" > + "\t.type _start,@function\n" > +"_start:\n" > + "\tcall wld_start\n" > + "\tpush %eax\n" > + "\txor %eax,%eax\n" > + "\txor %ebx,%ebx\n" > + "\txor %ecx,%ecx\n" > + "\txor %edx,%edx\n" > + "\tret\n" > +); You know, I wonder if we couldn't make this simpler ... well, shorter, by assuming the stack is already set up and the main binary is mapped correctly, then being careful not to disturb the linker entry stack just reserve the areas we need with a few mmap syscalls, map in the real dynamic linker and do a jump. In effect, rather than repeat the work the kernel already did for everything but the real dynamic linker, insert a small shim between them. Thoughts? thanks -mike

3 2

Re: Add stub function HWND GetConsoleWindow()
by Dmitry Timoshkov April 28, 2004

April 28, 2004

"Ylia K" <k_ilya(a)ukr.net> wrote: > * dlls/kernel/kernel32.spec, dlls/kernel/console.c, include/wincon.h > Ilya Korniyko <k_ilya(a)ukr.net> > Add stub function HWND GetConsoleWindow() > > It is for excelent file manager FAR Manager (www.rarlab.com) > FAR Manager doesn't run without this patch. > With patch it runs - good on winXP, very bad on winME. I'm wondering how your patch works at all, the call should smash the stack since it misses WINAPI modifier. -- Dmitry.

3 3

Re: SetFocus
by Alexandre Julliard April 27, 2004

April 27, 2004

Ulrich Czekalla <ulrich.czekalla(a)utoronto.ca> writes: > ChangeLog: > Ulrich Czekalla <ulrich(a)codeweavers.com> > Trying to set focus to an invisible window should fail I don't think that's correct, setting focus to an invisible window seems to work fine on Windows. -- Alexandre Julliard julliard(a)winehq.org

2 2

Re: RPCRT4: reimplement UuidCreate() with Win32 APIs (resubmit)
by Juan Lang April 27, 2004

April 27, 2004

Alexandre wrote: > I don't think rpcrt4 should depend on iphlpapi, it > doesn't on Windows AFAICS. Right, rpcrt4 precedes iphlpapi. However, iphlpapi was created to allow you to do things that were platform-specific and often undocumented. In this case, rpcrt4 is trying to get the MAC address. On Windows 9x, you used to use WsControl for this, and this calls the appropriate VxD. Wine's WsControl forwards to iphlpapi instead (on Win9x iphlpapi calls WsControl). On Windows NT, you use a DeviceIoControl on the network device driver. Wine doesn't implement any of these. Wine could use ioctl on a UNIX fd, but I doubt this is what Hans wants to do, since he's trying to implement this using Win32. It appears to me that this is the most straightforward way to get the MAC address in Wine (but since I wrote iphlapi, you could count on me saying that ;) ) --Juan __________________________________ Do you Yahoo!? Win a $20,000 Career Makeover at Yahoo! HotJobs http://hotjobs.sweepstakes.yahoo.com/careermakeover

1 0

Re: RPCRT4: reimplement UuidCreate() with Win32 APIs (resubmit)
by Alexandre Julliard April 27, 2004

April 27, 2004

Hans Leidekker <hans(a)it.vu.nl> writes: > Anything wrong with this one? > > Changelog: > Reimplement UuidCreate() with Win32 APIs. I don't think rpcrt4 should depend on iphlpapi, it doesn't on Windows AFAICS. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: 2 Fatal Problems With Winesetuptk-0.73 (BOTH Sourceforge Release Formats)
by Ivan Leo Murray-Smith April 27, 2004

April 27, 2004

If you build a binary for older versions of Linux, let me know and I'll put your binary on the sourceforge page. AFAIK winesetuptk will only work correctly with the itcl/tck libs shiped in the tarball. Ivan.

1 0

Winsock help...
by António Serra April 27, 2004

April 27, 2004

Hi all! I'm porting a windows application to Linux using the winelib. I created a project with KDevelop and include all ( at least I think all ) the .dll.so needed by my project. After compiling a linker error message appears, saying that /windows/D/ HICOD2000/j2kserver/j2kserver/kdu_server.cpp:2894: undefined reference to `WSAWaitForMultipleEvents' . It happens that I included the ws2_32.dll.so in my project. Am I missing something? TIA -- ______________________ António Serra aserra.wine(a)iol.pt ______________________

2 1

Re: GetTimeZoneInformation patch
by Rein Klazes April 27, 2004

April 27, 2004

On Tue, 27 Apr 2004 10:03:13 -0400, you wrote: > I was looking through the source code and noticed a FIXME for the > GetTimeZoneInformation API in dlls/kernel/time.c saying that the function > needed to return a different value if Daylight Savings Time was in effect. I > implemented that feature, and also made the function return the proper value > if DST was not in effect for the version being simulated. > > I have enclosed the patch for the file against the latest source package. > > Here is the ChangeLog entry (I didn't patch the ChangeLog file): > > * dlls/kernel/time.c > William Lahti <computerman413(a)ezrs.com> > > - Fixed return values in GetTimeZoneInformation Three remarks: - you are using ftime() of which my man page says: | These days the contents of the timezone and dstflag fields are undefined. and | This function is obsolete. Don't use it. Have a look at the implementation of GetDaylightFlag() or use it directly. - You state that on NT, 2K and XP the return code is TIME_ZONE_ID_UNKNOWN when the daylight saving time is not in effect. This is only true if the transition dates are undefined. This is true in the current implementation, but those transition dates are a bigger FIXME then the correct return value. - I am not sure if it is worth the trouble to be so correct for windows 9x. The NT return value is not impossible under win9x and unless there is an application that depends on it, Wine defaults to the NT behavior. Rein. -- Rein Klazes rklazes(a)xs4all.nl

1 0

Re: MDI fix attempt
by Dmitry Timoshkov April 27, 2004

April 27, 2004

"Krzysztof Foltman" <kfoltman(a)portal.onet.pl> wrote: > Applying this patch makes MDI Window menu behave as follows: > > - if no child windows are present, no separator is added (or it is > removed if it was present before) > - if any child windows are present (and visible), a separator is added > after last item of the original Window menu (unless it was already there) Is there a real bug you are trying to fix? When I last time worked with MDI code including Window menu handling I did a lot of tests under Windows. Did you? -- Dmitry.

2 6

Re: Winetest: outstanding issues (USING)
by Dimitrie O. Paun April 27, 2004

April 27, 2004

Now for the second installment: USING (Feri) ----------------------- A. winetest Winetest will have to support a new option -B <filename> This will add a new section to the report, just before the test results, called "Build Info". The body of this section will be read from <filename>, with each time indented (say 4 spaces), and a blank line to end it (for neatness). B. Dissect & gather Need only recognize the "Build Info" section as optional, and ignore it for now. Maybe dissect should do that as a rule, ignore sections it doesn't understand. This way we can easily add more data in the future, without needing to constantly patch dissect. Such sections would have all lines indented, and would end with a blank line. BTW Feri, can we indent the body of our current sections? Would that break stuff? It would be nice to, would make the report more readable. We should be more forgiving with the parsing, like HTML is. The idea would be: "we should look only for stuff that we need for the report, additional stuff should be ignored. Moreover, non-essential stuff should be optional, and if not present/parsed, don't display". -- Dimi.

4 8

Fwd: Re:SpecOpS Labs
by Ivan Leo Murray-Smith April 27, 2004

April 27, 2004

I asked project davied if they know what use of LGPL code involves, and if the're using wine code, I got the following answer. The impression I have is that they are using major parts of wine. They claim they will fully comply with the LGPL. Here is the full email they sent me. > Good Evening Mr. Smith > > > Thanks for your email; We appreciate your taking the time to delve into > Project David. We feel certain that the closer that you look at the project > the more comfortable you will be with it. > > Our overall purpose of the project is to encourage consumers to use Linux. > Our David Linux/Win Bridge software is simply a product to facilitate the > transition to Linux. Our Linux/Win Bridge software is one of multiple > components, which comprise our OS platform. In the future we will release > another component, which is a set of tools that will encourage developers to > write native Linux applications. > > The David software is a joint development effort between De La Salle > University and SpecOpS Labs. Our Chief Technical Officer is Mr. Peter > Valdez. As you may know Mr. Valdez is the founder of Tivoli Systems, which > is now a multi billion-dollar flagship product of IBM. > > The code for our Windows/Linux Bridge is a hybrid of code, including our own > proprietary code, and code from several open source projects. For now we > are keeping the exact nature of our code under wraps until our first release > of David. We are not using pirated or stolen code from Microsoft or any > other source. As stated we are not disclosing the nature of our code or our > exact methodology for running Windows Apps on Linux, this is for competitive > and other reasons. However, a good deal of our success is attributed to our > innovative methodology in assembling together open source code, proprietary > code that we have written/purchased, and freeware. In the future, once we > disclose how we have done this, then Im sure a number of developers will be > kicking themselves in the rear end for not having thought of this > themselves. > > We do encourage the open source movement and we will comply with the GNU > LESSER GENERAL PUBLIC LICENSE. > > Our website is currently under construction, the data (*especially the > technical data) on the website for the most part is not current and in some > cases is up to 20+ months old. We are now in the process of doing a major > overhaul of the site, which we expect to be completed in a few weeks. *The > technical data on our web site concerning David, is outdated and in some > cases a competitive smoke screen. We appreciate your comments on the WINE > Project and we have no intention of misrepresenting the WINE. Therefore, we > are now consulting our English-technical writers and the Filipino - > designers/developers of David to ensure that there are no mistakes in the > translation. Until we can update the website we have disabled the links to > both our technical and competitive data. Hopefully, the development > community wont get wrapped around the axle about David, and will withhold > judgment until David is released. > > So far as our product goes we just completed our prototype, which has been > in the making for quite some time. Our first release will be issued before > the end of 2004; we expect to start Beta Testing in about 4-5 months. On 22 > April we held a press conference at De La Salle University. During the press > conference we demonstrated our prototype to more than 30 members of the > local and international media. During the demo we ran Macromedia Flash, and > MS Office on our Windows/Linux Bridge without a hitch. What you read in the > media was primarily the result of the press conference/demo. David is not a > hoax or vaporware, but we're not going to make any further claims about > David at this point, We prefer to let our software do our talking for us. > > > FYI: We are now a publicly traded company, our ticker symbol is SPLMF, you > can view it on any major financial website such as Merrill Lynch: > http://askmerrill.ml.com/markets_chart/1,2260,,00.html?q=SPLMF > > > > Thanks > > > > > Customer Service > SpecOpS Labs > Summit One Office Tower > Unit 23-H, 530 Shaw Blvd > Mandaluyong City, Metro Manila, Philippines > > Office 63 2 532-7854 > Fax 63 2 532-5875 >

7 10

winealsa fails the winmm test
by Francois Gouget April 27, 2004

April 27, 2004

I'm not having much luck with sound this week-end :-( First there was the crash in ALSA_WaveInit() (an old bug apparently), but now the winmm test either gets stuck or crashes. When it gets stuck it's because I get: trace:wave:wodUpdatePlayedTotal dwPlayedTotal=21987 dwWrittenTotal=22050 delay=63 trace:wave:wodPlayer_NotifyCompletions still playing 0x4069fd1c (22050/21987) trace:wave:wodPlayer waiting 2ms (7,2) trace:wave:wodUpdatePlayedTotal dwPlayedTotal=21987 dwWrittenTotal=22050 delay=63 ... So the problem is that everything has been played but because snd_pcm_delay() keeps returning 63, dwPlayedTotal never reaches the 22050 that would signal the completion of the first tone. Now it seems like snd_pcm_delay() should return 0 after a while so this looks like an Alsa bug (0.9.6). Is this a known bug? Is there a way to work around it? (besides commenting out the call to snd_pcm_delay()) And when I don't get into the above infinite loop it's because I've crashed before with an Alsa assertion: trace:wave:wodPlayer waiting 7ms (7,4294967295) trace:wave:wodUpdatePlayedTotal dwPlayedTotal=11781 dwWrittenTotal=17184 delay=5403 trace:wave:wodPlayer_WriteMaxFrags Writing wavehdr 0x4069fd1c.17184[22050] trace:wave:wodPlayer_WriteMaxFrags 1065 dwLength=2433 toWrite=110 0010:Call ntdll.RtlAcquireResourceShared(4037c168,00000001) ret=404e0751 0010:Ret ntdll.RtlAcquireResourceShared() retval=00000001 ret=404e0751 0010:Call ntdll.RtlReleaseResource(4037c168) ret=404e08ae 0010:Ret ntdll.RtlReleaseResource() retval=00000000 ret=404e08ae 0010:Call ntdll.RtlTryEnterCriticalSection(40340098) ret=404e0519 0010:Ret ntdll.RtlTryEnterCriticalSection() retval=00000001 ret=404e0519 0010:Call ntdll.RtlTryEnterCriticalSection(40340098) ret=404e0519 0010:Ret ntdll.RtlTryEnterCriticalSection() retval=00000001 ret=404e0519 0010:Call ntdll.RtlTryEnterCriticalSection(40340098) ret=404e0519 0010:Ret ntdll.RtlTryEnterCriticalSection() retval=00000001 ret=404e0519 wine-kthread: pcm.c:5899: snd_pcm_mmap_commit: Assertion `frames <= snd_pcm_mmap_avail(pcm)' failed. The interesting things are that wwo->write points to snd_pcm_mmap_writei(). This assertion would seem to imply that we are writing too much stuff at once? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ The greatest programming project of all took six days; on the seventh day the programmer rested. We've been trying to debug the *&^%$#@ thing ever since. Moral: design before you implement.

2 1

2 Fatal Problems With Winesetuptk-0.73 (BOTH Sourceforge Release Formats)
by Kenny Love April 27, 2004

April 27, 2004

In the Bugzilla system, including the search page, there is no mention of Winesetuptk, so I can't tell whether the following bugs are new to you. These two problems are of considerable import to aspiring Wine users, particularly if they are running Red Hat Linux 6.2 or equivalent or older (for the first item, Red Hat Linux 7.x or equivalent might also be affected). 1. The rpm'ed Winesetuptk binary currently posted on the Sourceforge site, winesetuptk-0-73.i586.rpm, aborts on startup on a Red Hat Linux 6.2 system with the message "winesetuptk: /lib/libc.so.6: version `GLIBC_2.3' not found (required by winesetuptk)". I suspect this means that the binary (maybe the Tcl/Tk/ITcl) is dynamically linked to glibc 2.3, but Red Hat Linux 6.2 can only be easily upgraded to glibc 2.1.3-21; even Red Hat Linux 7.3 easily upgrades only to glibc 2.2.5-44, so this might prohibit most Red Hat Linux installations older than 8.0 from running this binary. 2. The scripts in the Winesetuptk tarball currently posted on the Sourceforge site, /winesetuptk-0-73.tar.bz2, hang. When run "as scripts directly" on a Red Hat Linux 6.2 system with Tcl 8.0.5-35 and ITcl 3.0.1-35 installed, after the program opens a window stating "Autodetection in Progress", an error notice appears stating that map is not a legal argument to the string function ("Error: bad option "map": must be compare, first, index,"...). After the notice's "Ok" button is pressed, the error notice box disappears, but the program quietly hangs, ignoring attempts to close the remaining windows. Bash's kill command, probably unknown to the novice, is required to exit the comatose program. Also, on the launching shell window appears the message "CBase::AutoConf:GetWinInstalls: unable to grep /dos/c/msdos.sys: child process exited abnormally ". My /dos/c/ directory contains my dual-boot Windows 3.1 system. In the tcl8.3.2 subdirectory, the "changes" file lists, between the "8.1 final" and "8.1.1" headers, a "new features" entry dated 5/3/99 mentioning adding Jeff Hobbs' patches introducing, among others, a map argument to the string function. The Sourceforge Winesetuptk-0.73 release note states that at version 0.34b, all was successfully converted from requiring Tcl 8.4 to using Tcl 8.0, so this map call appears to be a small overlooked mouse with a show-stopping roar. I lack Tcl programming experience, but the stack trace (see below) and 'grep'-ing the source tree for potential "string_ map" calls seems to implicate "winesetuptk-0.73/Enable8.0Compatibility.tcl", line 42 as the culprit; it looks like there's no if-clause to handle $aCmd == "map". Here's the stack trace: bad option "map": must be compare, first, index, last, length, match, range, tolower, toupper, trim, trimleft, trimright, wordend, or wordstart while executing "string_ map {{${WinDir}} windows} {${WinDir}/system}" ("eval" body line 1) invoked from within "eval string_ $aCmd [list $aStr] $args" (procedure "string" line 26) invoked from within "string map [list {${WinDir}} $WinDir] $SystemDir" (object "::ObjBase" method "::CBase::AutoConf:GetWinInstalls" body line 74) invoked from within "AutoConf:GetWinInstalls $Drives" (object "::ObjBase" method "::CBase::AutoConf" body line 39) invoked from within "$pObjBase AutoConf" ("GEN_NEW" arm line 6) invoked from within "switch [$pObjBase AccessCfgData GET_KEY_VALUE_BY_NAME Cfg WhatToDo] { GEN_NEW { CMsgDialog ObjWaitMsg . .wait_msg "WineSetup" "Autodetection..." (object "::ObjScrFileLoc" method "::CScrFileLoc::SetWineData" body line 2) invoked from within "SetWineData" (object "::ObjScrFileLoc" method "::CScrFileLoc::SetResult" body line 58) invoked from within "::ObjScrFileLoc SetResult NEXT" (in namespace inscope "::CBaseScr" script line 1) invoked from within "namespace inscope ::CBaseScr {::ObjScrFileLoc SetResult NEXT}" invoked from within ".f_scr.b_next invoke" ("uplevel" body line 1) invoked from within "uplevel #0 [list $w invoke]" (procedure "tkButtonUp" line 8) invoked from within "tkButtonUp .f_scr.b_next" (command bound to event) I'm going to try compiling the Winesetuptk-0.73 source from the tarball on my system; hopefully that will produce a >working< binary dynamically linked to glibc 2.1.3-21. Considering that most aspiring Wine users, (Remember: Many, perhaps most of those are new to Linux itself.), are currently steered by the Wine documentation to use the Winesetuptk program with its nice, friendly GUI, those who took the time-honored route of putting a Linux installation from second-hand CD's on an older, expendable PC (which often limits one to a 6.2/7.0 version or less because 2.4 kernels can thrash too much on old hardware to be useful) may be in for a big suprise when they try to graphically configure their wine.conf file. To summarize, the rpm binary release as-is probably won't start for Linux versions older than Red Hat Linux 8.0 or equivalent and the tarball release as-is hangs deviously when run "as scripts directly" on systems with Tcl 8.0, possibly 8.1.0. By the way, that rpm should have refused to install because the program required a higher version glibc than my Linux system possesses, shouldn't it? Thanks! Kenny A life spent making mistakes is not only more honorable, but more useful than a life spent doing nothing. G. B. Shaw

1 0

Alignment testing
by Hans Leidekker April 26, 2004

April 26, 2004

Hi, kernel/tests/generated.c currently shows one failure when the executable is compiled with MinGW. Investigation shows that MinGW and GCC differ when it comes to alignment of doubles (i.e. a 64 bit wide type). I have constructed the test below that shows the difference between MinGW and GCC. My question is, could someone compile this with MSVC >= 6, run it, and report the outcome here? Thanks, -Hans

3 4

GetDriveTypeW crash
by Robert Reif April 26, 2004

April 26, 2004

I'm having problems with several programs crashing in GetDriveTypeW. I recently did a fresh install from source with tools/wineinstall so it may be a config problem. Any ideas where to start? Unhandled exception: page fault on read access to 0x00000000 in 32-bit code (0x404944b0). In 32-bit mode. 0x404944b0 (GetDriveTypeW+0xac [volume.c:110] in KERNEL32.DLL): movw 0x0(%edi),%ax 111 { Wine-dbg>bt Backtrace: =>0 0x404944b0 (GetDriveTypeW+0xac(root=0x0) [volume.c:110] in KERNEL32.DLL) (ebp=4081e8b8) 1 0x40493294 (GetVolumeInformationW+0x300(root=0x0, label=0x0, label_len=0x0, serial=0x0, filename_len=0x4081fb34, flags=0x4081fb38, fsname=0x0, fsname_len=0x0) [volume.c:683] in KERNEL32.DLL) (ebp=4081f7b8) 2 0x40493551 (GetVolumeInformationA+0x91(root=0x0, label=0x0, label_len=0x0, serial=0x0, filename_len=0x4081fb34, flags=0x4081fb38, fsname=0x0, fsname_len=0x0) [volume.c:780] in KERNEL32.DLL) (ebp=4081f7fc) 3 0x01004012 (PPView97.exe..text+0x3012 in PPView97.exe) (ebp=4081fb48) 4 0x01004c0c (PPView97.exe..text+0x3c0c in PPView97.exe) (ebp=4081fc8c) 5 0x0100577f (PPView97.exe..text+0x477f in PPView97.exe) (ebp=4081fdb0) 6 0x01005970 (PPView97.exe..text+0x4970 in PPView97.exe) (ebp=4081fec4) 7 0x01005aa8 (PPView97.exe..text+0x4aa8 in PPView97.exe) (ebp=4081ff2c) 8 0x404773ca (start_process+0xf2(arg=0x0) [process.c:785] in KERNEL32.DLL) (ebp=4081fff4) 9 0x4002921d (wine_switch_to_stack+0x11 in libwine.so.1) (ebp=00000000)

2 1

Re: Make dlls-kernel-tests-file.c work on Windows 95 and XP.
by Alexandre Julliard April 26, 2004

April 26, 2004

Jakob Eriksson <jakov(a)vmlinux.org> writes: > +static int test_win9x_based() > +{ > + OSVERSIONINFOEX ver; > + > + ver.dwOSVersionInfoSize = sizeof(OSVERSIONINFO); > + ok( GetVersionEx ((OSVERSIONINFO *) &ver), " --- Can't get OS version.\n" ); > + if ((4 == ver.dwMajorVersion && 0 == ver.dwMinorVersion && 1381 == ver.dwBuildNumber) > + || ver.dwMajorVersion >= 5) > + { > + return 0; > + } > + > + return 1; You should not do version checks in tests, the checks should be based on the features we are testing. Otherwise the results are going to depend on the Windows version that Wine is configured for, which is the wrong thing to do since the behavior of the Wine code in that case does not depend on the version. -- Alexandre Julliard julliard(a)winehq.org

2 3

Hmm.. something strange in winetest reporting
by Jakob Eriksson April 26, 2004

April 26, 2004

Check out http://test.winehq.org/data/20040425-1000/ OSR2 shell32:string. It says "0", but if you click, there seems to be some kind of error. Is it the test output somehow erratic, or is the log parser doing something bad? regards, Jakob

2 1

Re: msvcrt: compatibility fixes
by Alexandre Julliard April 26, 2004

April 26, 2004

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > ChangeLog > Fix the _WCHAR_T_DEFINED/_WCHAR_T_DEFINED sentries for > compatibility with the MSVCRT ones. Unfortunately _WCHAR_T_DEFINED is also used by gcc in stddef.h. -- Alexandre Julliard julliard(a)winehq.org

2 3

Re: String constification
by Dmitry Timoshkov April 26, 2004

April 26, 2004

"Francois Gouget" <fgouget(a)free.fr> wrote: > We find the same issues with an added twist: now that we can use > literals we can write things like: > > const char* str = "String literal"; > > However this is slightly different from: > > static const char* str[] = "String literal"; > > The difference is that in the first case sizeof(str) returns 4 (on 32 > bit machines<g>) while in the latter we get 15. Some of our code relies > on this so care must be taken when converting the latter to the former. My understanding of this is that in the first case you declare a const pointer and hope that a compiler is smart enough to place a pointed by it object into a read only section, while in the second case you explicitly say to a compiler to place the whole object into a read only section. I prefer to not rely on a compiler's good will. -- Dmitry.

4 5

Re: RPCRT4: make the on-wire protocol Windows compatible
by Steven Edwards April 26, 2004

April 26, 2004

Hiya Filip, You should leave this part out. I dont think Alexandre will remove it for you. +#ifndef __REACTOS__ __TRY { - if (func) func(&msg); + if (func) func(msg); } __EXCEPT(rpc_filter) { /* failure packet was created in rpc_filter */ } __ENDTRY +#else + if (func) func(msg); +#endif Thanks Steven __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25� http://photos.yahoo.com/ph/print_splash

1 0

Re: Remove debugmsg from guides
by Ivan Leo Murray-Smith April 26, 2004

April 26, 2004

> Please don't do that, we've been over this a thousand times, > let's not rehash it. Do either or, otherwise you end up > confusing Alexandre's script, etc. Inlining is prefered > for a lot of reasons, so if you're using a decent mail client > (and you seem to be), just inline it and don't look back :) I'm not using an email client, my ESP only allows that if I connect via their dial-up service. That's why I can't have text/plain attachments. Ivan.

1 0

Re: Remove debugmsg from guides
by Dimitrie O. Paun April 26, 2004

April 26, 2004

On Mon, 26 Apr 2004, Ivan Leo Murray-Smith wrote: > attaching as text/plain can't be done for various reasons, so I'll both attach > and inline. Please don't do that, we've been over this a thousand times, let's not rehash it. Do either or, otherwise you end up confusing Alexandre's script, etc. Inlining is prefered for a lot of reasons, so if you're using a decent mail client (and you seem to be), just inline it and don't look back :) -- Dimi.

1 0

Re: RFH: RPC patch
by Ivan Leo Murray-Smith April 26, 2004

April 26, 2004

Running server and client with wine CVS current returns Hello Implicit RPC World! but I can't test with your patch because it doesn't cleanly apply against the current CVS code. Ivan.

1 0

service.cgi: script generation
by Dimitrie O. Paun April 26, 2004

April 26, 2004

Currenly we send a script to run and execute all published versions that we have. This is currently problematic, because an error in one causes the abort the entire script. Moreover, releases may no arrive at the server at the same time, and if we're going to receive the poll event in between them, we'll miss some of them. What we need to do is to ask the client to execute one thing at a time. Problem is that we need to keep track of what the client did execute already. Here's a way to do it without storing state on the server side, which is problematic. We need to introduce three new cookies: build_id: the current build ID that we execute. It's going to be something like '200405031000' current: the name of the test that was just executed history: a comma separated list of filenames that where already executed by the client for this current build. It's going to look like so: 'wine-200405031000-paul-mingw.zip,wine-200405031000-kevin-mingw.zip' The algorithm is simple: if $build_id != $current_build_id $build_id = $current_build_id $history = "" else $history = $history . "," . $current $current = pick_next_test($history) # send script to run $current, and to set the values of the # three cookies to the values in our variables where: pick_next_test picks the next test to run from the pool of tests avaiable for our current build, so that it doesn't appear in $history Comments? -- Dimi.

1 0

Re: Font selection - please review
by Shachar Shemesh April 26, 2004

April 26, 2004

Hi Dirk, First of all, thank you for the reference. Regarding the missing flag to TranslateCharsetInfo - My VisualStudio 6 MSDN DVD (Latest that came up for that version - dated October 2001) does not have this flag mentioned. This means either that the flag was not present at that time, or that it was present but they forgot to mention it (has happened to me before). The latest MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unico…) does mention it, and claims it's available on Windows 2000 (like you said). I guess this is anyone's guess what this means as far as when you can use it. Fortunetly for Wine, we don't care when it was introduced. If Wine has it, we can use it. At least for code written by us, that rule is fine. So, thank you very much for the good advice. Are you a wine user that needs this flag, or did you just happen to see my email when you were investigating a Win32 problem? Shachar Dirk Luetjens wrote: > Hello Shachar Shemesh, > > sorry for the lost context. Your mail I replyed to, is available at > > http://www.winehq.com/hypermail/wine-patches/2002/11/0221.html > > I know, that the wine project is totally unrelated to any windows dll. > I thought it would be better to mention, that this additonal flag for > TranslateCharsetInfo is not available in a specific windows version, > since the wine project tries to implement the WIN32 interface, and it > should behave as close as possible to the original one. Judging from > the code in > > http://source.winehq.org/source/objects/font.c#L1849 > > this additional flag is not yet implemented in wine. I can not tell > you when it was introduced into WIN32 itself. The MSDN says something > about WIN2000, but it isn't available on my WIN2k installation. > > Dirk > > > Shachar Shemesh wrote: > >> Hi Dirk, >> >> Judging from the email address you used to send me this email, we are >> talking about a fairly old post. Can you please direct me to the some >> context regarding what was my post exactly? A link with the post in >> question would be very helpful. >> >> Also, I hope you do realize that my post was on a Wine mailing list, >> which means that the functions there are totally disjointed from any >> particular Microsoft version or DLL. >> >> Many thanks, >> Shachar >> >> Dirk Luetjens wrote: >> >>> Hi Shachar Shemesh, >>> >>> I came across your post while researching a problem I had during >>> application development under windows. >>> >>> While digging in the MSDN I found another function that deals with >>> this problem: TranslateCharsetInfo >>> >>> --- >>> TranslateCharsetInfo function translates based on the specified >>> character set, code page, or font signature value, setting all >>> members of the destination structure to appropriate values. >>> --- >>> >>> and for the flag parameter: >>> >>> --- >>> TCI_SRCLOCALE Windows 2000: Source (that is, lpSrc) is the LCID or >>> LANGID of the keyboard layout. If it is a LANGID, the value is in >>> the low word. >>> --- >>> >>> The destination of the translation is a CHARSETINFO structure, where >>> one entry is the charset. >>> >>> I had problems using this parameter, since it isn't implemented in >>> the gdi version I use (VS6, gdi32.dll 5.00.2195.6898). I can only >>> find the definition in the newer .NET studio headers. But perhaps >>> this is a possible inclusion point for your function. >>> >>> Best regards >>> Dirk Luetjens >>> >> >> > > -- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/

1 0

Re: winmm wave test
by Robert Reif April 26, 2004

April 26, 2004

Francois Gouget wrote: > Some Windows sound drivers allow wild frequencies such as the 2MHz > one. > Is this a windows driver bug? Is the test really valid and it's just finding a real bug in the windows driver for that specific sound card? I know it makes the test fail on bad windows drivers but is that bad?

2 4

email add
by kosta April 26, 2004

April 26, 2004

1 0

Re: Add some functions to msvcrt.dll
by Dmitry Timoshkov April 25, 2004

April 25, 2004

"kata 198" <kata198(a)hotmail.com> wrote: > Changelog: > Add some functions to msvcrt.dll If you could make your patch behave according to current locale that would be really nice. Otherwise it's not acceptable. Also, please make sure that your formatting style is at least consistent, and even better conforms to the formatting style of the file you are editing. -- Dmitry.

1 0

Window management protocol extensions
by Mike Hearn April 25, 2004

April 25, 2004

The latest WM problems caused by Metacity preventing windows from being moved offscreen prompted to raise the issue of having a Wine specific extension to the NETWM (EWMH) protocol into which we can easily add whatever semantics we need to map win32 windowing to X windowing more easily. The idea would be that we have a new property/set of properties we can mark windows with, _NET_WM_WINDOWS_EMULATION for instance, and standards compliant window managers will take note and not do things that break us. Short of actually doing all our own window management, this is probably the best way to fix the obscure bugs caused by different interpretations WMs have of what various hints mean. The current NETWM border hints are semantic not presentational, so we cannot rely on particular intepretations. The MWM hints are even worse - they are apparently undocumented, and most modern WM authors consider them deprecated. Thanks to their undocumentedness, WMs vary in their interpretation of these too: http://bugs.kde.org/show_bug.cgi?id=73294 So, I'd like to start gathering ideas on what sort of things we'd like to have in the NETWM spec, seeing as how many WMs conform to it these days. First up is a way to ensure the WM doesn't attempt to keep the window onscreen of course :) Other things we probably want are related to border styles, an absolutely crystal-clear no-wriggling-possible equivalent to PPosition as apparently the wording of the ICCCM allows WM authors to ignore this if they want. We might also want to look at where we use unmanaged windows and see if we can replace them with the use of managed windows+hints. We can probably hack around the lack of these things for now, but being able to use these hints where possible will probably keep a lot of us from going grey-haired early :) thanks -mike

2 2

RFH: MDI Window menu fix
by Krzysztof Foltman April 25, 2004

April 25, 2004

I've just finished fixing the behaviour of Window menu in MDI applications. However, I'm not sure if it won't cause some other MDI applications to work incorrectly. So, if you have some time and MDI apps to play with (regardless if they worked correctly before or not), check this out and tell me if I've fixed or broken the Window menu. http://www.winehq.org/hypermail/wine-patches/2004/04/0414.html Krzysztof

1 0

Re: abnt2 keyboard patch
by Mauro Carvalho Chehab April 25, 2004

April 25, 2004

Rafael, With your patch, the '\' key on the main keyboard will stop to work on the ABNT2 Keyboard, at least on the ABNT2 keyboards I've tested (some low valued keyboards and also Compaq keyboard). On ABNT2 keyboards, before the 'z' key there is the '\' key and the layout has to reflect that. That was the situation before 200303xx version. That changes was required in order to support that key. Had you tested it? If it works on your keyboard, may be you has some ABNT2 variant. I think it would be better to find another solution for the numeric keyboard that doesn't break the main keyboard. Mauro Chehab > Date: Fri, 16 Apr 2004 10:52:01 -0300 > From: Rafael Ávila de Espíndola <rafael.espindola(a)ic.unicamp.br> > To: wine-devel(a)winehq.org > Subject: Re: abnt2 keyboard patch > > > That's why I said that it's an X11 bug and we can do nothing about it. > > > > Please resubmit the patch without that part. > Attached. I will contact xfree and try to fix the rest of the problem. > > Thanks. > > > Dmitry. > Rafael >

2 1

RFH: RPC patch
by Filip Navara April 25, 2004

April 25, 2004

Hi, for about week and half I was working on a patch that makes Wine RPC runtime communicating with the Windows one. Now I'm almost done with the work and I need help from someone who can test the patch under Wine. (I was doing all my testing under regular Windows.) If someone will be willing to help me testing it, the patch is at www.volny.cz/xnavara/rpc/ along with a test programs. Regards, Filip

1 0

Wine bug with MFC/C++?
by greensh＠knology.net April 25, 2004

April 25, 2004

It appears that Wine cannot use tmpfs... so far my testing only works using swap :o( which I do have enabled at home and it crashes. At work I have a 500MB swap space and the same exact program does not crash there. It's not convenient for me to run swap at home, so does anyone know a fix for this? The code seems to require approx 500MB free memory. Since I only have 500MB RAM, I setup tmpfs on /tmp. But wine doesn't seem to use any of it. Shaun

1 0

winetest.exe output from Windows 95
by Jakob Eriksson April 25, 2004

April 25, 2004

By killing processes left and right, I managed to get a 50 - megabyte log. Maybe in the future we should link in bzip2 in winetest.exe to compress logs before submitting? regards, Jakob

2 2

Re: Remove debugmsg from guides
by Dimitrie O. Paun April 25, 2004

April 25, 2004

On Sun, 25 Apr 2004, Ivan Leo Murray-Smith wrote: > Please let me know if something isn't OK. A few points: -- I find the change confusing. There's no WINEDEBUG channel. I think most should just change from debugmsg -> debug -- Please provide only one .diff file. Multiple diffs are not necessary, and makes reviewing and applying so much more difficult. -- It would be nice if the diff would be either inlined or attached as text/plain. Inlining is prefered, this way people can quote easily when replying. -- Dimi.

1 0

Re: Remove debugmsg from guides
by Eric Pouech April 25, 2004

April 25, 2004

Ivan Leo Murray-Smith a écrit : > With this all unneeded references to debugmsg should be gone. Just one note, in > debugger.sgml I found this > [MACHINE\\Software\\Microsoft\\Windows NT\\CurrentVersion\\AeDebug] 957636538 > "Auto"=dword:00000001 > "Debugger"="winedbg --debugmsg -all %ld %ld" > As I don't know what it's meant to be now, I've left it, if it should change, > let me know. > Please let me know if something isn't OK. > > Ivan. this should be changed into "Debugger"="winedbg %ld %ld" (the issue is that the debugger will be inheriting the parent's debug channel, while this setting was turning off all debugging channels from debugger itself). A+

1 0

Re: PATCH: silence strict aliasing in dlls/opengl32
by Lionel Ulmer April 25, 2004

April 25, 2004

> Not sure how to regenerate the opemngl_ext.c file. You need the extension registry CVS (you can find it here http://oss.sgi.com/projects/ogl-sample/ - no idea where the exact CVS informations are). After, do 'make_opengl PATH_TO_EXTENSION_DIR 1.2' where PATH_TO_EXTENSION_DIR points to the '<OGL-SAMPLE-ROOT>/main/doc/registry/specs/' directory). Anyway, if it can wait, it will be updated the next time I generate the file. Lionel -- Lionel Ulmer - http://www.bbrox.org/

1 0

dlls/d3d8/shader.c
by Marcus Meissner April 25, 2004

April 25, 2004

Hi, I was just fixing this code, but I wonder why floorf(s0->w) is overwritten right next with tmp_f = powf(2.0f, s0->w); What is the right version? Ciao, Marcus void vshader_expp(D3DSHADERVECTOR* d, D3DSHADERVECTOR* s0) { float tmp_f = floorf(s0->w); DWORD tmp_d = 0; tmp_f = powf(2.0f, s0->w); tmp_d = *((DWORD*) &tmp_f) & 0xFFFFFF00;

2 1

Bad string handling in PRINTDLG_UpdatePrintDlg?
by Francois Gouget April 24, 2004

April 24, 2004

In PRINTDLG_UpdatePrintDlgA() in dlls/commdlg/printdlg.c we do: ... LPPRINTER_INFO_2A pi = PrintStructures->lpPrinterInfo; ... pi->pPortName = "FILE:"; And in PRINTDLG_UpdatePrintDlgW() we do: ... LPPRINTER_INFO_2W pi = PrintStructures->lpPrinterInfo; ... static WCHAR file[] = {'F','I','L','E',':',0}; pi->pPortName = file; ... Now in gcc all string literals are read-only, even if you declare them as char* foo="bar", *foo='\0' will cause a segfault. So in the Ansi version we point pPortName to a read-only string. But if the application gets hold of that pointer we have no garantee that it won't expect to be able to modify that string: pPortName is an LPSTR. (this is a case where -Wwrite-strings will complain) And in the Unicode case we point pPortName to a static writable buffer. But in this case if the application writes in our buffer its contents is going to be messed up forever. However I don't know this code at all. So I'm asking, shoudln't we make a copy of these strings? Which also raises the ugly issue of later freeing the corresponding memory buffer... -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Any sufficiently advanced Operating System is indistinguishable from Linux

1 0

Idea to fight spam
by Ivan Leo Murray-Smith April 24, 2004

April 24, 2004

What about having a link to this page somewhere on winehq? Maybe on the mailing lists page? http://www.hostedscripts.com/scripts/antispam.html Ivan.

2 1

Re: Docu: mention piping for debugmsgs
by Ferenc Wagner April 24, 2004

April 24, 2004

Andreas Mohr <andi(a)rhlx01.fht-esslingen.de> writes: > Make people know how to reduce log size, using pipes. Hi Andi! Two notes: 1. The --debugmsg option is deprecated, people should use the WINEDEBUG environmental variable instead. 2. Won't the pipe block until you read from it, then give you all the data ever written? -- Feri.

1 0

winetest: build & publishing
by Dimitrie O. Paun April 24, 2004

April 24, 2004

Hi folks, I've checked the build this morning on SF, and it looks beautiful! So let's review the possible problems still outstanding: 1. Build Info Feri want to move that in the resources, with good reason. This will probably affect you very little, but needs to be done. We can still keep it in the .zip file (it is tiny) as it's a lot easier accessible for others. However, if we do that, the file will need to use DOS line ends, as this file will probably be viewed by folks on Windows boxes. Anyway, from your point of view it will probably mean a 'unix2dos' and a 'cp' before the build. 2. Uploading to SF This works nice now, but I'm afraid it may not when we have more than one person doing it. Namely, a release needs to be created, will that not fail if it already exists? Can we check that? If that's a problem, how are we going to deal with it? Kevin, can you please try to see if what happens if you upload two files (with differents sfutils invocations) into the same release? 3. Downloading from SF I just realized there is a time delay for the uploads to be propagated to the mirrors. What URL are we going to use for downloading? How long are we going to allow for the propagation to happen? Anyone has experience with this? 4. Release lifetime It would be nice to have the "WineTest Files" package visible on SF. I have made it so for testing purposes now. However, it will become ugly soon, because we don't hide the old releases. We can hide the entire package, and that would solve the ugliness problem, but it would be much nicer to have an automatic way of hiding old releases, and having just the latest releases visible. Can we maybe modify the sfutils to do this for us? We are very close on this front. I'm very happy with the state of things right now, I hope we can resolve these in a few days. -- Dimi.

5 6

Re: FILEDLG_MapOfnStructA bug?
by Dmitry Timoshkov April 24, 2004

April 24, 2004

"Francois Gouget" <fgouget(a)free.fr> wrote: > -static char defaultopen[]="Open File"; > -static char defaultsave[]="Save as"; > > /*********************************************************************** > * FileDlg_Init [internal] > @@ -970,9 +968,13 @@ > if (ofnA->lpstrTitle) > str = ofnA->lpstrTitle; > else > + { > /* Allocates default title (FIXME : get it from resource) */ > + static const char* defaultopen="Open File"; > + static const char* defaultsave="Save as"; Don't you really want to leave it as a static const array of characters as before and not a static const pointer? Same for your next patch. -- Dmitry.

1 0

Re: Fix for test of CreateFileMapping in dlls/kernel/tests/file.c
by Stefan Leichter April 24, 2004

April 24, 2004

Am Samstag, 24. April 2004 00:54 schrieb Jakob Eriksson: > From a run of winetest 20040423 on Windows XP: > > file.c:1075: Test failed: mapping should succeed > file.c:1077: Test failed: can't close mapping handle > file: 487696 tests executed, 0 marked as todo, 2 failures. > > > > Seems CreateFileMapping has some seriously strange behaviour. > I tested some more how XP behaves and produced a patch based on that. > > > regards, > Jakob Hello Jakob, + *handle = CreateFile(filename, GENERIC_READ|GENERIC_WRITE, 0, 0, + CREATE_ALWAYS, FILE_ATTRIBUTE_NORMAL, NULL); + if (handle != INVALID_HANDLE_VALUE) { do you have to test the pointer not the value ? Bye Stefan

2 1

Re: Fix for test of CreateFileMapping in dlls/kernel/tests/file.c
by Jakob Eriksson April 24, 2004

April 24, 2004

Jakob Eriksson wrote: > > From a run of winetest 20040423 on Windows XP: > > file.c:1075: Test failed: mapping should succeed > file.c:1077: Test failed: can't close mapping handle > file: 487696 tests executed, 0 marked as todo, 2 failures. > > > > Seems CreateFileMapping has some seriously strange behaviour. > I tested some more how XP behaves and produced a patch based on that. But I just installed Windows 95 and it fails very much under that platform: will have to think more about that... file.c:58: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:105: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:180: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:204: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:319: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:354: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:394: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:441: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:683: Test failed: DeleteFileA("nul") returned ret=0 error=5 file.c:893: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:982: Test failed: couldn't create file "testfile.xxx" (err=32) file.c:1077: Test failed: Map is already created, for some reason we should be able to remap now... file.c:1081: Test failed: can't close mapping handle file.c:1086: Test failed: We should still be able to map! file.c:1087: Test failed: can't close mapping handle file.c:1088: Test failed: can't close file handle file.c:1097: Test failed: not ERROR_FILE_INVALID file.c:1108: Test failed: mapping should fail file.c:1110: Test failed: can't close file handle file.c:1111: Test failed: DeleteFile failed after map file.c:1118: Test failed: open testfile.xxx failed file.c:1120: Test failed: expected type disk got 0 file: 76 tests executed, 0 marked as todo, 22 failures.

1 0

graphical Linux
by Lonnie Cumberland April 24, 2004

April 24, 2004

Hello All, I am going to work on a project that will rely heavily on OpenGL and Wine. I wanted to get some of your opinions on which Linux distribution has the easiest setup and install for dealing with OpenGL and Wine. I will make a fresh install of the best latest version and build on it. did try Mandrake once but the OpenGL did not seem to work with my NVIDIA GeForce FX 5200 Any suggestions would be greatly appreciated. Lonnie __________________________________ Do you Yahoo!? Yahoo! Photos: High-quality 4x6 digital prints for 25� http://photos.yahoo.com/ph/print_splash

4 3

DirectPlay
by Ryan Underwood April 24, 2004

April 24, 2004

I have seen some mentions of work on DirectPlay. Who is currently working on this, and what are the implementation plans? I am mainly curious if it is planned to be network compatible with the same programs running on Windows. There could be some drawback to this, because the old versions of DirectPlay are not NAT friendly. So in the case of Wine, if the user is running a program that uses an old version of DirectPlay (i.e. the DX6 version), perhaps we could give them the choice to maintain compatibility with Windows clients (and thus be subject to NAT issues), or to use a more robust WINE-only version instead, perhaps an identical protocol to the one that would be implemented to support the later more robust versions of DirectPlay. -- Ryan Underwood, <nemesis(a)icequake.net>

3 2

winetest: dissect & gather
by Dimitrie O. Paun April 23, 2004

April 23, 2004

Hi Feri, Here is a list of things that I see as potential problems: (I haven't checked the code, so they may already be handled) 1. Multiple builds For a given BUILD_ID, we can have reports comming from different builds now, that is from different winetest-*.exe. That means a much of URLs, etc. 2. Multiple reports For a given BUILD_ID, we may get multiple reports from the same client (same Tag). This is because of (1), we can ask each client to run not one, but a bunch of the available tests (this is very useful, say we have each client run a mingw build, and a msvc build). 3. Build Info This is a minor issue, and we can safely ignore it for now, but maybe we can provide a little icon beside each URL that we list in (1), that would popup a window and display the Build Info. 4. Template Not a biggie, but maybe we can transform the generated report into a template so that it integrates nicely with the rest of the site (menu to the left, etc). Jer, what do we need to do to achive that? I think it should be very easy, but... -- Dimi.

4 8

Re: Winetest: outstanding issues (SERVING)
by Dimitrie O. Paun April 23, 2004

April 23, 2004

And the thrist and last installment: SERVING (Brian) --------------- What we need to support: -- multiple publishers -- multiple files for the same build for each publisher -- various distribution policies What we need to do: -- maintain a pool of releases as described in my previous mail. This is a map/hastable keyd by the published filename. -- persist this to disk, in case of server crash, load it from disk on startup. -- currently we use <program>/url.mask to get to the url mask. We need to add the publisher info in there, so this will need to change to: <publisher>/<program>/url.mask Similar for the other files. -- the rest remains unchanaged, as Brian correctly mentioned. We can have different distribution policies: pick a random file, send all files, etc. Given that we have few published files, and tests are short, I suggest we send them all. So what we have to do is to add a loop around most of the script generation: for file in pool: generate script commands to download it and run it It looks like there aren't that many changes after all. -- Dimi.

3 3

Re: winetest: build & publishing
by Jakob Eriksson April 23, 2004

April 23, 2004

Okay, but am I missing the point? winetest.exe is already self-extracting in itself... regards, Jakob chmorgan(a)charter.net wrote: > Lately I've been doing a lot of installer building with the NSIS > installer(http://nsis.sf.net). We could easily package winetest as a > self-extracting and executing installer that was transparent to the > user. The installer would simply extract the actual winetest.exe to > windows/temp, start it up and wait until it completed before exiting. > This should be transparent to winrash as well. > > Chris > > > > >> From: Jakob Eriksson <jakov(a)vmlinux.org> >> >> Can you also upload the exe? >> >> Ferenc touched this issue slightly - if we want to point (maybe very >> novice) users >> to a way to contribute to Wine - commandline option may be hard to >> understand. >> A zipped file can also be an obstacle. >> It's very neat just to click "open" on an exe compared to unpacking a >> zip. >> >> >

1 0

Re: Re: winetest: build & publishing
by chmorgan＠charter.net April 23, 2004

April 23, 2004

Lately I've been doing a lot of installer building with the NSIS installer(http://nsis.sf.net). We could easily package winetest as a self-extracting and executing installer that was transparent to the user. The installer would simply extract the actual winetest.exe to windows/temp, start it up and wait until it completed before exiting. This should be transparent to winrash as well. Chris > > From: Jakob Eriksson <jakov(a)vmlinux.org> > Date: 2004/04/23 Fri PM 02:24:17 EDT > To: "Dimitrie O. Paun" <dimi(a)intelliware.ca> > CC: Wine Development <wine-devel(a)winehq.org>, > Paul Millar <paulm(a)astro.gla.ac.uk>, Kevin Koltzau <kevin(a)plop.org>, > Ferenc Wagner <wferi(a)afavant.elte.hu> > Subject: Re: winetest: build & publishing > > Dimitrie O. Paun wrote: > > > 2. Uploading to SF > > This works nice now, but I'm afraid it may not when we > > have more than one person doing it. Namely, a release > > needs to be created, will that not fail if it already > > exists? Can we check that? If that's a problem, how are > > we going to deal with it? Kevin, can you please try to > > see if what happens if you upload two files (with > > differents sfutils invocations) into the same release? > > > > > > Can you also upload the exe? > > Ferenc touched this issue slightly - if we want to point (maybe very > novice) users > to a way to contribute to Wine - commandline option may be hard to > understand. > A zipped file can also be an obstacle. > It's very neat just to click "open" on an exe compared to unpacking a zip. > > regards, > Jakob > > > >

1 0

project David?
by Rein Klazes April 23, 2004

April 23, 2004

Hi, Somehow, we are doing something far to complicated: http://www.specopslabs.com/david.htm Rein. -- Rein Klazes rklazes(a)xs4all.nl

13 18

Google's cachze link update
by PETREOLLE Sylvain April 23, 2004

April 23, 2004

Hello, The following change makes the google page unavailable here. why would you change it since it still works ? Patch: http://cvs.winehq.org/patch.py?id=12121 Old revision New revision Changes Path 1.2 1.3 +1 -1 lostwages/news/2004040701.xml - (23 April 2004 - <a href="http://66.102.7.104/search?q=cache:sDglkGiMh7sJ:www-106.ibm.com/develo perworks/linux/library/l-wine/%3Fca%3Ddgr-lnxw11FineWine">Google's cache</a> still has a copy, but it's been removed from IBM's website.) + (23 April 2004 - <a href="http://www.google.com/search?q=cache:sDglkGiMh7sJ:www-106.ibm.com/deve loperworks/linux/library/l-wine/%3Fca%3Ddgr-lnxw11FineWine Cordialement, PETREOLLE Sylvain #DMIT/DATO/PSI/OPS (exploit at gefco dot fr ) +33 (0)1 49 05 29 29 "1+1=3" Bernard Werber ---------------------------------------------------------------------------- Ce message ainsi que toutes pièces jointes (le "message") sont confidentiels et sont exclusivement destinés à l'usage de la personne à laquelle ils sont adressés. Tout point de vue ou toute opinion contenus dans ce message expriment la pensée personnelle de leur auteur et ne représentent pas nécessairement la position des sociétés du Groupe GEFCO. Si vous n'êtes pas la personne à laquelle ce message est destiné, veuillez noter que vous avez reçu cet e-mail par erreur et qu'il vous est strictement interdit d'utiliser, de diffuser, de transférer, d'imprimer ou de copier ce message. Si vous avez reçu ce message par erreur, merci de contacter la personne qui vous l'a adressé et de l'effacer immédiatement. Les sociétés du Groupe GEFCO déclinent toute responsabilité en cas d'altération, de modification, d'édition, de diffusion sans autorisation de ce message ou en cas d'affection de ce message par un virus. This message and any attachments (the "message") are confidential and intended solely for the use of the individual to whom they are addressed. Any views or opinions presented are solely those of the author and do not necessarily represent those of the GEFCO Group of Companies. If you are not the intended recipient, be advised that you have received this email in error and that any use, dissemination, forwarding, printing, or copying of this message is strictly prohibited. If you have received this message in error please contact the sender and delete the message immediately. The GEFCO Group of Companies shall not be liable for the message if altered, changed, falsified, edited, diffused without authorization or affected by any virus. ----------------------------------------------------------------------------

1 0

Problem with GetVolumeInformation
by Chris McKenzie April 23, 2004

April 23, 2004

The refers to the 2004-03-09 ChangeLog, specifically: * dlls/kernel/Makefile.in, dlls/kernel/volume.c, dlls/ntdll/file.c, documentation/samples/config, documentation/wine.conf.man, files/drive.c, include/drive.h, include/winnt.h: Reimplemented GetVolumeInformation and SetVolumeLabel; volume label and serial number are now stored in the filesystem instead of in the config file (partly based on a patch by Eric Pouech). GetVolumeInformation's new implementation has 2 problems: 1. For software that was previously registered with a "made up" serial number via the "serial=" directive in the config file, the software (for me Altera MaxPlus) will no refuse to run claiming a change in serial. 2. If the function fails to claim a serial number (What actually _did_ happen with me) it will fall back on *serial=0. In my opinion this does not seem reasonable. I propose two options for wineconfig. First, one that says UseConfigSerial = [Y/N] Which will use the serial number in the config file and ignore the one on disk (This is useful for people that registered their software before the new function implementation) And the second option will be to reinstate the serial= for the drive descriptions. This should be the fallback serial number if the function fails, instead of the value *serial=0. I made a quick hack to return the value that I needed - however, I have not dealt with the kernel or the wine code extensively so I cannot put for a patch that does this at this time. However, I think this is a much more sensible design decision. Thank you. Sincerely, Christopher J. McKenzie cjm(a)ucdavis.edu

2 1

MinGW --mno-align-double
by Dimitrie O. Paun April 23, 2004

April 23, 2004

======= From: Hans Leidekker <hans(a)it.vu.nl> To: wine-devel(a)winehq.com <wine-devel(a)winehq.com> On Saturday 27 March 2004 02:20, Dmitry Timoshkov wrote: > generated.c:542: Test failed: TYPE_ALIGNMENT(*(LPWIN32_STREAM_ID)0) == 8 > (expected 4) generated: 842 tests executed, 0 marked as todo, 1 failure. > * NOTE: the same test compiled by cl.exe (MS compiler) works as expected, > * so that's most likely a gcc bug. (gcc version 3.3.1 (cygming special)) Same here (GCC 3.2.3 (mingw special 20030504-1)). It appears that this compiler defaults to --malign-double. When I specify --mno-align-double the test succeeds. ======= Alexandre, can we add this flag to our makefiles? If so, I can produce a patch... -- Dimi.

3 2

Re: Winetest: outstanding issues (BUILDING)
by Dimitrie O. Paun April 23, 2004

April 23, 2004

> From: Paul Millar <paulm(a)astro.gla.ac.uk> > One way this could work is if the general format for the BUILD_ID is > YYYYMMDDhhmm [ "-" <tag> [ "-" <tag> ] ...] > where <tag> is any metadata keyword that must not include a "-" Right, I have reached the exact same conclusion over lunch myself. So here is a fresh round of specifications: BUILDING (Paul & Kevin) ----------------------- A.The build process will produce 2 files: <name> <name>.sig where: <name>: the file being published <name>.sig: the GPG signature B. Naming <program>-<build>-<publisher>-<tools>[-<misc>].<ext> where: <program>: program name (i.e. "winetest", "winrash") <build>: build ID (for winetest, it's YYYYMMDDhhmm) <publisher>: publisher ID (i.e. "paul", "kevin") <tools>: tool chain used (i.e. "mingw", "msvc") <mic>: any other information the publisher wishes this can be used to support different builds for the same <build>, say with different flags, patches, etc. <ext>: appropriate extension (i.e. "zip", "exe") C. Publishing After the files have been successfully uploaded to the server (for winetest, this will be sf.net) a publish event will be sent to WineHQ, with the following form: http://test.winehq.org/service?publish=true&url=<url> where: <url>: is the URL to the <name> D. Winetest specific information - <program> = "winetest" - <publisher> = "paul" or "kevin" - <tools> = "mingw" (but a msvc would be good too) - <ext> = "zip" - nightly build will use sources as of 5AM EST - the <build> will use same time converted to UTC so it will mosty be YYYYMMDD1000, but it may be different when daylight-savings is in effect - you should use cvs co -D "YYYY-MM-DD 5:00 EST" to check out the code, and use date -u +%Y%m%d%H%D -d "YYYY-MM-DD 5:00 EST" to generate the <build> (I may have the format wrong, I don't have a reference handy) - the .zip file contains two files: winetest.exe: the object of this exercise winetest.info: metadata information about the build, as the tools that where used, special flags, mentions any special patches, etc. The information in here will not be automatically parsed, but rather is intended to help the developers debug problems. NOTE: should we include all the metadata present in <name> is the names of the .exe and .info? I would personally like to, in order to avoid any possible confusion on the tester's box. OK, did I miss anything? I will shotly send emails describing the other stages, I did not include them here, since this email is getting a bit long. The good thing is that there are no changes to Chris' winrash, there are a few changes (trivial) to winetest.exe, and dissect&gather, and some to service.cgi. But I'll cover those in my next emails. -- Dimi.

4 4

Microsoft: "We'd have been dead a long time ago without the Windows APIs"
by Mike Hearn April 23, 2004

April 23, 2004

http://news.zdnet.co.uk/0,39020330,39152686,00.htm At least they're honest about it - I especially love this quote: In the commission's report, Contorer's email was also blunt about Microsoft's shortcomings. "It is this switching cost that has given the customers the patience to stick with Windows through all our mistakes, our buggy drivers, our high TCO [total cost of ownership], our lack of a sexy vision at times, and many other difficulties ... Customers constantly evaluate other desktop platforms, [but] it would be so much work to move over that they hope we just improve Windows rather than force them to move. In short, without this exclusive franchise called the Windows API, we would have been dead a long time ago." Higher TCO huh? D'oh! thanks -mike

1 0

Re: project David? (Rein Klazes)
by Kevin F. Quinn April 23, 2004

April 23, 2004

A couple of statements on their web site: "One of the problems of the MS Windows OS is that it is subject to crash applications and itself. While studying the Microsoft Windows OS, we found the design flaw that causes this problem." _the_ design flaw? Marketing hype. It seems from later statements that they're talking about Microsoft's decision to relocate large sections of previously user-land code into the kernel (in particular, GDI), much commented on when NT went from 3.51 to 4.0. Later on, when comparing themselves to WINE, they state: "SpecOpS Labs believes, that [WINE] suffers from a major architectural flaw, which requires a major rewrite of the WINE code. The WINE project had been too faithful in reverse engineering the Windows Environment Subsystem, that it also inherited the architectural flaws in Windows. Among these flaws is when a problem is experienced by an application running in a Window, it can crash the whole operating system, causing it to either hang or reboot. " I think I'm right in saying an application using WINE _cannot_ crash the kernel, any more than any other user-land app. Also, from what I understand, it is _not_ WINE policy to re-implement Win32 bug-for-bug (since Microsoft do fix bugs, this is sensible). It looks like their project is on the search for large-scale funding. Assuming they can't distribute WINE code (good ol' GPL), they have a lot of work to do. Their "architecture" basically means full Win32 API implementation, with what looks like a priviledged kernel component ("WACS Driver") to interface to priviledged objects in the kernel. Incidentally, that kernel component better be rock-solid or they _will_ be able to kill the kernel from Windows apps in their subsystem... They do claim to have a "prototype" - I would guess that's either a modified WINE, or if newly written only implements a very small subset of the Win32 API. It will be interesting to see how quickly they get product to market, and when they do to see how much WINE code is used (which will need object-code comparisons, of course). One of their headline comments is: "David is not a reinvention of the wheel. It takes the best of breed pieces from previous attempts to simulate the Windows Subsystem, and integrates them into a single product." We shall see. There's a lot of "validation" garbage on the site, which to my mind isn't worth the paper it isn't printed on. It could well be they'll just raise loads of cash, then later crash and burn when they realise quite how much effort they need to spend to reimplement everything - or maybe when they realise they'll be violating the GPL if they lift WINE code. Kev.

1 0

Re: Re: i810 audio fixes 1/2
by chmorgan＠charter.net April 22, 2004

April 22, 2004

>like "play this wave file". The major remaining drawback >is latency; >click on button in app, hear sound 2 seconds later when >scheduler This is why we have sound servers like jack. Any delay is likely due to not having a fully callback based architecture in the app. >Maybe a better thing to do is rewrite arts/esd library >interfaces to >omit the daemons altogether. That way the daemons can go >away, but the >existing applications can be trivially migrated. I've heard that arts is being phased out from kde use in the near future. I'm not sure what might replace it though. Chris

6 7

Re: wine/include winternl.h
by Lionel Ulmer April 22, 2004

April 22, 2004

On Wed, Apr 21, 2004 at 05:21:36PM -0500, Alexandre Julliard wrote: > ChangeSet ID: 12085 > CVSROOT: /opt/cvs-commit > Module name: wine > Changes by: julliard(a)wine.codeweavers.com 2004/04/21 17:21:36 > > Modified files: > include : winternl.h > > Log message: > Mike McCormack <mike(a)codeweavers.com> > * add some values to the SYSTEM_INFORMATION_CLASS enumeration > > *************** > wint-sys-debug.diff (text/plain) > > Index: include/winternl.h > =================================================================== > RCS file: /home/wine/wine/include/winternl.h,v > retrieving revision 1.74 > diff -u -r1.74 winternl.h > --- include/winternl.h 16 Apr 2004 05:00:46 -0000 1.74 > +++ include/winternl.h 19 Apr 2004 06:57:43 -0000 > @@ -442,9 +442,36 @@ > SystemCacheInformation, (...) > > Patch: http://cvs.winehq.org/patch.py?id=12085 > > Old revision New revision Changes Path > 1.77 1.78 +33 -1 wine/include/winternl.h > Is this a VERY verbose Changelog or the new way to see the patch in the commit log :-) ? Lionel -- Lionel Ulmer - http://www.bbrox.org/

2 1

Winetest publishers
by Dimitrie O. Paun April 22, 2004

April 22, 2004

Hi Brian, A few more thoughts on the multiple publisher idea, and what we need to do on the server side. So, let's assume we have a number publishers out there. On server side we need to: 1. Maintain a pool of published winetest.exe's 2. Implement policy to serve from that pool (on a poll even) 1. The pool The pool will have to be maintained in a persistent manner to survive server reboots. It needs to get saved in a file. It should be managed as such: When a publish event happen we do: - check that the publisher id exists in publishers.txt file (1) - reject the event if not - check that it's really the publisher who publishes (2) - reject if not - check that the new BUILD_ID is >= than the current BUILD_ID - reject if not - if greater, reset the pool - add the published test to the pool - return 'OK' NOTES: (1) I suggest this format for publishers.txt <publisher-id>:<publisher-base-url> (2) We need to check that someone doesn't want to polute the pool. I suggest checking for the existance of: <publisher-base-url>/<published-file> 2. The Policy The sky's the limit. For now, we can just pick one at random from the pool. -- Dimi.

2 1

Invalid curdrive and curdir
by jeffl April 22, 2004

April 22, 2004

All, I am tracking a problem where an install program with an exception trying to access 0x00000000 memory. I have tracked the problem down to files/drive.c in DRIVE_GetCurrentDirectory where dos_cwd contains 0 and is used in ret = strlenW(dos_cwd) + 3; /* length of WHOLE current directory */ It seems that DRIVE_GetCurrentDrive returns a value greater than MAX_DOS_DRIVES (25) and then return DOSDrives[drive].dos_cwd; where dos_cwd=0; pTask->curdrive and pTask->curdir appear not to be set or invalid. Now it seems that a check for null ptr in DRIVE_GetCurrentDirectory is order ie. UINT ret; LPCWSTR dos_cwd = DRIVE_GetDosCwd( DRIVE_GetCurrentDrive() ); static const WCHAR driveA_rootW[] = {'A',':','\\',0}; if (dos_cwd == 0) { ERR("dos_cwd returned 0 instead of pointer to current working directory\n"); dos_cwd = "\0"; /* make a valid string for strlenW */ } ret = strlenW(dos_cwd) + 3; /* length of WHOLE current directory */ if (ret >= buflen) return ret + 1; but what would be a good value for dos_cwd? I am interested in what causes the pTask->curdrive to be greater than 25 and curdir to be set to ???????? as shown below. Wine-dbg>p *pTask {hNext=0, ss_sp=0, nEvents=0, priority=0, unused1=0, hSelf=4143, hPrevInstance=0, unused2=0, ctrlword8087=0, flags=16, error_mode=0, version=1024, hInstance=0, hModule=0, hQueue=4199, hParent=0, signal_flags=0, sighandler=0x00000000, userhandler=0x00000000, discardhandler=0x00000000, int0=0x00000000, int2=0x00000000, int4=0x00000000, int6=0x00000000, int7=0x00000000, int3e=0x00000000, int75=0x00000000, compat_flags=0, unused4="", teb=0x4002f000, unused5="", hPDB=4151, dta=272040064, curdrive=254, curdir="????????", nCmdShow=1, hYieldTo=0, dlls_to_init=0, hCSAlias=4167, thunks={0, 21584, 0, 8, 16, 0, 0, 0, 24, 0, 0, 0, 32, 0, 0, 0, 40, 0, 0, 0, 48, 0, 0, 0, 56, 0, 0, 0, 0, 0, 0, 0}, module_name="", magic=17492, hEvent=0x0000000c, pdb={int20=8397, nextParagraph=0, reserved1=0, dispatcher="?", savedint22=0x00000000, savedint23=0x00000000, savedint24=0x00000000, parentPSP=0, fileHandles="????????????????????", environment=4159, saveStack=0, nbFiles=20, fileHandlesPtr=272039960, hFileHandles=0, reserved3={0, 0, 0, ...}, ...}...} Wine-dbg> Jeff Latimer

1 0

Anyone working on WSALookupServiceBegin() and WSALookupServiceNext?
by Robbert Xerox April 22, 2004

April 22, 2004

Simple question : is anyone working on WSALookupServiceBegin() and WSALookupServiceNext() in winsock? ____________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html

1 0

richedit - anybody trying to do it ?
by Krzysztof Foltman April 22, 2004

April 22, 2004

Hi, Just out of curiosity: is anyone already actively developing a (supposedly) fully featured richedit control ? The current version looks like a plain editor combined with RTF reader... -- Chris

5 5

speed up oleaut32: vartest
by Chris Morgan April 21, 2004

April 21, 2004

*dlls/oleaut32/tests/vartest.c: Chris Morgan<cmorgan(a)alum.wpi.edu> Skip over most of the unused variant types to speed up the variant tests. This look like a reasonable way to speed up the variant tests without losing testing functionality? Chris

1 1

RE: Fix for GetFileTime API - Incorrect Modified/Last access Time .
by Krishna Murthy April 21, 2004

April 21, 2004

We have Team Developer Product for MS Windows which has its own language and in the process of verifying on Wine. Few of test cases working on Windows are failing in Wine. Hence I have submitted this patch. Yes, since Pre-1970 times are not going to work on Unix anyway we could release note this in our product. Thanks for your input on this. Krishna -----Original Message----- From: Alexandre Julliard [mailto:julliard(a)winehq.org] Sent: Wednesday, April 21, 2004 6:16 PM To: Krishna Murthy Cc: wine-devel(a)winehq.org Subject: Re: Fix for GetFileTime API - Incorrect Modified/Last access Time. Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > Change of argument type DWORD to LONGLONG of function > RtlSecondsSince1970ToTime() and RtlSecondsSince1980ToTime() to accept > negative values. These are Windows APIs, you cannot simply change their arguments, we have to be compatible. Pre-1970 times are not going to work right on Unix anyway; what do you need them for? -- Alexandre Julliard julliard(a)winehq.org

1 0

winetest oddity - oleaut32: VarTest
by Chris Morgan April 21, 2004

April 21, 2004

I've been looking at vartest, specifically to speed it up since the tests I added for VarMod() are the cause of its current excessive length. Something appears to be a bit different with mingw compiled tests vs. MSVC compiled tests. Under wine these tests run just fine, three fixmes popup. I get two failures when running the oleaut32 vartest on my XP machine. This is compiled with vc6sp5+processor pack. Running the mingw compiled test from Paul Millar, http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/winetest-20040421-100…, there are thousands of failures for the same test. Anyone have a clue what might be causing this? One thing that came to mind was that there are int64's used in the ole code, the test won't compile cleanly under vc6 without the processor pack. Maybe mingw is messing up the int64's? Chris

1 0

Re: Fix for GetFileTime API - Incorrect Modified/Last access Time.
by Alexandre Julliard April 21, 2004

April 21, 2004

Krishna Murthy <Krishna.Murthy(a)guptaworldwide.com> writes: > Change of argument type DWORD to LONGLONG of function > RtlSecondsSince1970ToTime() and RtlSecondsSince1980ToTime() to accept > negative values. These are Windows APIs, you cannot simply change their arguments, we have to be compatible. Pre-1970 times are not going to work right on Unix anyway; what do you need them for? -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Wine detect patch (ignore previous whitespace patch)
by Ferenc Wagner April 21, 2004

April 21, 2004

Jakob Eriksson <jakov(a)vmlinux.org> writes: > (Sorry about the linespace noise after print_version(), > emacs seems to change stuff behind my back when I save.) Hi Jakob, You'd better educate Emacs about your ways, otherwise all your patches will be full of whitespace changes making them very hard to review. The indentation isn't consistent, but if you want to fix this, do so in a separate patch, please! > + static const TCHAR wine[128] = {"Wine"}; I think we could use static const char wine[] = "Wine"; instead. No wide characters in winetest for now. But see below! > + if (running_on_wine ()) { /* Make a an obvious signature for Wine */ > + ext = 1; > + > + ver.dwMajorVersion = 1; > + ver.dwMinorVersion = 1; > + ver.dwBuildNumber = 1; > + ver.dwPlatformId = 1; > + strncpy (ver.szCSDVersion, wine, sizeof (wine)); > + } > + I think we can do better. A single line like xprintf (" bRunningUnderWine=%d\n", running_under_wine ()); as the first line of print_version() would do a perfect job without masking anything else. -- Feri.

2 1

Re: Winetest results uploaded... where?
by Ivan Leo Murray-Smith April 21, 2004

April 21, 2004

On http://test.winehq.org/data/200404192305/ the "next build" and "previous build" buttons are broken. I get a error message, saying "You don't have permission to access /site on this server." Ivan.

4 12

Re: White-space patch for programs/winetest/main.c
by Alexandre Julliard April 21, 2004

April 21, 2004

Jakob Eriksson <jakov(a)vmlinux.org> writes: > This is also an example of how the file can store its indent > preference in a comment. > > I will run this when I'm done editing the file: > FILENAME=main.c && `grep indent $FILENAME` $FILENAME I don't think that's a good idea at all. It would require everybody to do that every time they make a change to that file, otherwise there will be plenty of spurious whitespace changes and conflicts. Please don't do that. -- Alexandre Julliard julliard(a)winehq.org

2 2