- Wine-Devel - list.winehq.org

gcov and wine?
by Dan Kegel Dec. 30, 2002

Dec. 30, 2002

Has anyone ever tried building wine with gcov, then running the conformance test suite to see how much of the wine code gets exercised? - Dan -- Dan Kegel Linux User #78045 http://www.kegel.com

2 1

Win98 Compliance Status
by Mathew McBride Dec. 30, 2002

Dec. 30, 2002

I downloaded and ran the Wine Comformance tests from http://fgouget.free.fr/wine/winetests.zip Windows 98 Second Edition, with all official updated installed. 1152x864 res, NVIDIA RIVA TNT 41.09 beta drives. Overclocked by Powerstrip. AMD Duron 800MHz. 3 gb VFAT partition Dr. Watson (drwatson.exe) was enabled advapi32_test.exe/registry crash DrWatson: The application overflowed its temporary memory area. Module Name: ADVAPI32_TEST.E Application Name: Advapi32_test.exe dsound_text.exe I don't have msvcrtd.dll (where can I get it) REQUEST: Is it possible to compile these tests using mingw32. gdi32_test.exe/generated 2786 tests executed, 0 marked as todo, 0 failures kernel32_test.exe/alloc alloc.c:208: Test failed: GlobalReAlloc failed to convert FIXED to MOVEABLE: err or=87 alloc.c:213: Test failed: Converting from FIXED to MOVEABLE didn't REALLY work alloc.c:238: Test failed: Discarded memory we shouldn't have alloc.c:239: Test failed: GlobalUnlock Failed. alloc: 58 tests executed, 0 marked as todo, 4 failures. kernel32_test.exe/atom atom.c:55:WARNING: Unicode atom APIs are not supported on this platform atom: 163850 tests executed, 0 marked as todo, 0 failures. kernel32_test.exe/codepage 2 tests executed, 0 marked as todo, 0 failures kernel32_test.exe/directory 25 tests executed, 0 todo, 0 failures kernel32_test.exe/drive 80 tests executed,0 todo, 0 failures kernel32_test.exe/environ 19 executed, 0 todo, 0 failures kernel32_test.exe/file file.c:631: Test failed: WriteFile error 183 file.c:632: Test failed: expected number of bytes written 0 file.c:633:Current offset = 0100 file.c:634: Test failed: expected file offset 21 file.c:639: Test failed: WriteFile error 87 file.c:640: Test failed: expected number of bytes written 0 file.c:642: Test failed: expected file offset 517 file.c:656: Test failed: ReadFile error 0 file.c:657: Test failed: expected number of bytes read 0 file.c:658:Current offset = 0000 file.c:659: Test failed: expected file offset 21 file.c:661: Test failed: pattern match failed file: 487224 tests executed, 0 marked as todo, 10 failures. kernel32_test.exe/format_msg 58 executed, 0 todo, 0 failures kernel32_test.exe/generated 609 executed, 0 marked as todo, 0 failures kernel32_test.exe/locale locale.c:499: Test failed: GetDateFormat check DATE_YEARMONTH with null format e xpected ERROR_INVALID_FLAGS got return of '10' and error of '0' /locale: 105 tests executed, 0 marked as todo, 1 failure. kernel32_test.exe/path path.c:881:TMP=C:\WINDOWS\TEMP path.c:892:TMP=C:\WINDOWS path.c:902:TMP=C:\ path.c:912:TMP=C: 1702 executed, 0 todo, 0 failures kernel32_test.exe/process tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. 116 executed, 0 todo, 0 failures kernel32_test.exe/thread thread.c:430: Test failed: SetThreadPriorityBoost Failed thread.c:432: Test failed: GetThreadPriorityBoost Failed thread.c:434: Test failed: SetThreadPriorityBoost Failed thread.c:436: Test failed: GetThreadPriorityBoost Failed 86 executed, 0 todo, 4 failures msvcrt_test.exe/file 2 executed, 0 todo, 4 failures msvcrt_test.exe/scanf 8 tests executed, 0 todo, 0 failures netapi32_test.exe access.c:174:It appears there is no netapi32 functionality on this platform same error reported by all netapi32 tests. ntdll_test.exe/error 813 executed, 0 todo, 0 failures ntdll_test.exe/generated 1279 executed, 0 todo, 0 failures ntdll_test.exe/rtlbitmap, ntdll_test.exe/rtlst, ntdll_test.exe/rtlstr 1 executed, 0 todo, 0 failures oleaut32_test.exe/safearray 348 executed, 0 todo, 0 failures oleaut32_test.exe/varest 2871 executed, 0 todo, 64 failures rpcrt4_test.exe/rpc 511 executed, 0 todo, 0 failures shell32_test.exe/generated 272 executed, 0 todo, 0 failurs shell32_test.exe/shlfileop shlfileop.c:177: Test failed: Can't rename many files shlfileop.c:185: Test failed: Can't rename many files shlfileop.c:286: Test failed: Files are copied to other directory shlfileop.c:287: Test failed: The file is copied 121 executed, 0 todo, 0 failures shlwapi_test.exe/clist clist.c:367: Test failed: allowed bad element size clist.c:372: Test failed: allowed adding a container 236 execited. 0 todo, 2 failures shlwapi_test.exe/generated 19 executed, 0 todo, 0 failures shlwapi_test.exe/shreg shreg.c:205: Test failed: (ImARatherLongButIndeedNeededString) shreg.c:206: Test failed: (ImARatherLongButIndeedNeededString) shreg.c:262: Test failed: didn't open copy Then Crashed Dr Watson: The application overflowed its temporary memory area. Module Name: SHLWAPI_TEST.EX Application Name: Shlwapi_test.exe urlmon_test.exe/generated 4 executed, 0 todo, 0 failures user32_test.exe/class nothing done user32_test.exe/generated 1524 executed, 0 todo, 0 failures user32_test.exe/sysparams bugger! this mucked up my system. Task Bar turned into a grey box. A massive border was around all the Windows. Reboot forced user32_test.exe/win win.c:132:main window 00000640 main2 00000644 desktop 00000080 child 00000648 win.c:148:created child 0000064C win.c:161:created child of desktop 00000650 win.c:171:created child of child 00000654 win.c:181:created top-level 00000658 win.c:191:created owned top-level 0000065C win.c:201:created popup 00000660 win.c:211:created owned popup 00000664 win.c:221:created top-level owned by child 00000668 win.c:227:created popup owned by desktop 0000066C win.c:233:created popup owned by child 00000670 win.c:239:created WS_CHILD popup 00000674 win.c:245:created owned WS_CHILD popup 00000678 win.c:250:testing parent changes Then Crashed. DrWatson: Windows User-interface core component accessed memory improperly or encountered some nonspecific error. Module Name: user.exe Description: Windows User-interface core component Version: 4.10.2227 Product: Microsoft(R) Windows(R) Operating System Manufacturer: Microsoft Corporation Application Name: User32_test.exe user32_test.exe/wsprintf 2 executed, 0 todo, 0 failures wininet_test.exe/generated 252 executed, 0 todo, 0 failures wininet_test.exe/http Too Much output to list here 22 executed, 0 todo, 1 failure winmm_test.exe/wave wave.c:182:found 1 WaveOut devices wave.c:206: 0: "C-Media Audio Playback (DC00)" 4.0 (1:15): channels=4 formats=0 fff support=002c wave.c:220:Testing invalid 2MHz format ws2_32_test.exe/sock 148 executed, 0 todo, 0 failures

1 0

Re: Documentation work -task list -man pages
by Tony Lambregts Dec. 30, 2002

Dec. 30, 2002

Tom Wickline wrote: We have decided to continue this discussion in public > I forgot to ask about sections 4-8 on Dimi's ToDo page. http://www.dssd.ca/wine/Wine-0.9-TODO.html > > > 4. Merge documentation/wine.texinfo into the Development Guide [TODO] > 5. Merge documentation/HOWTO-winelib into the Development Guide [TODO] > 6. Do something about > documentation/installation-und-konfiguration.german [TODO] > 7. Do something about documentation/shell32 [TODO] > 8. Do something about documentation/status [TODO] > > Are we going to be doing any work on these sections as well ? > Will your Task List take these sections into account ? I think that we should keep the documentation tasks togetther. If its OK with Dimi we can just use his page and give him diffs or we can split off the documentation section and he can link to it. > > > If our goal is to " Fix incomplete and/or out of date documentation." > Then we should do the Merge as well so everything will be complete. wine.texinfo is like a man page and it seems to be updated fairly well. I don't agree with trying to get rid of it but I am not about to be the one to maintain it either. The wine How-to should be part of wine users. Once it is merged we should get rid of it. I really dont know what to do about installation-und-konfiguration.german. I am inclined to leave it for now > > #7 and #8 I dont fully understand what needs to be done here. > Can you fill me in on what needs to be done with these two ?? From what I can tell these should be incorporated into the wine status page. This seems to be the logical place for them. Most of the files are a year or more old so I would tend to think that they are out of date. Whoever does this will probably need to ask some questions to the developers. In theory Each DLL should have a ToDo list inside the main .c file (or something like that (i can't fine the thread)) a little help here? Having these in documentation is doing neither the users or the developers any good. Again in "theory" someone could grep for "To Do" in wine and get a good idea of the status of that component. > > > Also are we going to be doing any work on man pages ? > If not does Dimi need to add them to this list ? I'm sure if > the web docs are out of date then the man pages need work > as well. > From what I can tell the man pages are the best of the lot. Right now we could use someone "New To Wine" to go through the users guide one chapter at a time and report to us *anything* they don't understand. Anyone is welcome to point out errors and offer any suggestions to help improve the documentation. Of course a patch is even better but if we do not know about a problem we can not fix it. -- Tony Lambregts

3 5

Problem with ShellExecute and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths
by Dan Kegel Dec. 29, 2002

Dec. 29, 2002

I have a windows-free installation of current CVS wine, with wordpad.exe and the needed DLLs pulled in from a Windows ME installation. wordpad works great. However, ShellExecute(... "wordpad.exe", ".\\stl\\readme.wri" ...) is failing to find wordpad.exe for me. (The call in question is issued by the msvc4.0 setup.exe. The current directory when I run this is /mnt/cdrom, and stl/readme.wri is indeed there.) To get some insight on how this is supposed to work, I went to a real Windows Me system, searched the registry for references to "wordpad.exe", and removed them, one by one, testing after each deletion. The reference that mattered was [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\WORDPAD.EXE] @="C:\\Progra~1\\Access~1\\WORDPAD.EXE" So I ran "regedit foo.reg" to import the above registry key, and made sure it does show up in ~/.wine/system.reg. Still didn't work. I then ran wine --debugmsg +exec,+file,+reg setup.exe to see whether Wine was properly searching that registry key. Sure enough, Wine is trying to search that key, and it's not finding it. So... what's wrong? Best I can figure is there's something fishy about what registry file is being loaded. Here are the interesting bits of the log (word wrapped, unfortunately): --------------------- ... trace:reg:NtQueryValueKey (0x24,L"LoadWindowsRegistryFiles",2,0xbfffe7fc,1024) trace:reg:_w31_loadreg (void) trace:file:FILE_DoOpenFile reg.dat OF_READ OF_SHARE_COMPAT trace:file:FILE_DoOpenFile reg.dat 0000 trace:reg:NtOpenKey ((nil),L"Machine\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths",f003f,0xbfffbb08) trace:reg:NtOpenKey <- (nil) warn:file:FILE_DoOpenFile 'reg.dat' not found or sharing violation warn:file:FILE_DoOpenFile (reg.dat): return = HFILE_ERROR error= 2 trace:reg:NtQueryValueKey (0x24,L"LoadGlobalRegistryFiles",2,0xbfffe7fc,1024) trace:reg:NtQueryValueKey (0x24,L"GlobalRegistryDir",2,0xbfffe7fc,1024) trace:reg:SHELL_LoadRegistry GlobalRegistryDir is '/usr/local/etc'. warn:reg:_get_wine_registry_file_format_version Couldn't open /usr/local/etc/wine.userreg for reading: No such file or directory warn:reg:_get_wine_registry_file_format_version Couldn't open /usr/local/etc/wine.systemreg for reading: No such file or directory ... [snip] ... trace:exec:ShellExecuteA trace:exec:ShellExecuteExA32 mask=0x00000000 hwnd=0x10023 verb=(null) file="wordpad.exe" parm=".\\stl\\readme.wri" dir="." show=0x00000001 class=not used trace:exec:ShellExecuteExA32 execute:'wordpad.exe','.\stl\readme.wri' trace:exec:SHELL_ExecuteA Execute wordpad.exe .\stl\readme.wri from directory . trace:reg:NtOpenKey ((nil),L"Machine\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths",f003f,0x4078ebcc) trace:reg:NtOpenKey <- (nil) trace:reg:NtOpenKey ((nil),L"Machine\\Software\\Wine\\Wine\\Config\\AppDefaults",f003f,0x40790040) trace:reg:NtOpenKey <- (nil) trace:reg:NtQueryValueKey (0x14,L"wordpad.exe",2,0x40790134,80) trace:reg:NtQueryValueKey (0x14,L"*wordpad.exe",2,0x40790134,80) trace:reg:NtQueryValueKey (0x14,L"*",2,0x40790134,80) trace:file:CreateFileW L"C:\\WINDOWS\\SYSTEM\\wordpad.exe" GENERIC_READ FILE_SHARE_READ OPEN_EXISTING attributes 0x0 warn:file:CreateFileW Unable to get full filename from L"C:\\WINDOWS\\SYSTEM\\wordpad.exe" (GLE 2) trace:exec:SHELL_FindExecutable wordpad.exe trace:exec:SHELL_FindExecutable xlpFile=,extension=(null) warn:exec:SHELL_FindExecutable Returning 31 - No association trace:exec:ShellExecuteA trace:exec:ShellExecuteExA32 mask=0x00000000 hwnd=0x10023 verb=(null) file=".wordpad.exe" parm=".\\stl\\readme.wri" dir="." show=0x00000001 class=not used trace:exec:ShellExecuteExA32 execute:'.wordpad.exe','.\stl\readme.wri' trace:exec:SHELL_ExecuteA Execute .wordpad.exe .\stl\readme.wri from directory . trace:reg:NtOpenKey ((nil),L"Machine\\Software\\Microsoft\\Windows\\CurrentVersion\\App Paths",f003f,0x4078ebcc) trace:reg:NtOpenKey <- (nil) trace:reg:NtOpenKey ((nil),L"Machine\\Software\\Wine\\Wine\\Config\\AppDefaults",f003f,0x40790040) trace:reg:NtOpenKey <- (nil) trace:reg:NtQueryValueKey (0x14,L".wordpad.exe",2,0x40790134,80) trace:reg:NtQueryValueKey (0x14,L"*.wordpad.exe",2,0x40790134,80) trace:reg:NtQueryValueKey (0x14,L"*",2,0x40790134,80) trace:file:CreateFileW L"C:\\WINDOWS\\SYSTEM\\.wordpad.exe" GENERIC_READ FILE_SHARE_READ OPEN_EXISTING attributes 0x0 warn:file:CreateFileW Unable to get full filename from L"C:\\WINDOWS\\SYSTEM\\.wordpad.exe" (GLE 2) trace:exec:SHELL_FindExecutable .wordpad.exe trace:exec:SHELL_FindExecutable xlpFile=,extension=(null) warn:exec:SHELL_FindExecutable Returning 31 - No association trace:file:GetFileInformationByHandle 0xffffffff --------------------- OK, so then I copied my system.reg to /usr/local/etc/wine.systemreg. Now it finds that key (!) but unfortunately, the only change is that the line warn:reg:_get_wine_registry_file_format_version Couldn't open /usr/local/etc/wine.systemreg for reading: No such file or directory no longer shows up in the log. I'm pretty sure this is supposed to work, but I'm having trouble untangling it. Help would be greatly appreciated. If anyone's interested, I can send an executable that does the ShellExecute call in question so they can reproduce it themselves... Thanks, Dan -- Dan Kegel Linux User #78045 http://www.kegel.com

2 9

Re: PATCH: dlls/cabinet/cabextract.c and off_t
by Greg Turner Dec. 29, 2002

Dec. 29, 2002

On Thursday 26 December 2002 02:48 pm, Gerald Pfeifer wrote: > If we really want to use off_t in this file (instead of cab_off_t) > we need to #include sys/types.h, or we'll break non-Linux systems. > > Gerald > > > ChangeLog: > #include <sys/types.h> to obtain off_t. actually I don't think we really want to use off_t. The relationship to off_t is historical: cabextract (the unix executable, which I ported) used off_t because it used the fopen/fseek/fgetpos/etc family of functions. Wanting to depend only on kernel32, I ported these to use windowsy api's like CreateFile/SetFilePointer/etc, which take LONG arguments, IIRC. My memory on this is already a bit hazy, but I think I created cab_off_t to save myself keystrokes -- I basically was able to go through much of the code and just turn "off_t"'s into "cab_off_t"'s. Initially I tried to support huge (64 bit offset) files -- cab_off_t was going to be a struct with two LONGS -- but later I decided I was too lazy, since this would have required a substantial reworking of the logic, some of which I didn't even take the time to fully understand. There's a fair amount of math in there and in some places off_t's got passed around, converted to other types, etc.... so I decided I should bang out the port first and worry about the finer details later. The easy version of the right fix is probably just to rename "cab_off_t" to something less confusing (i.e., cab_file_offset). The fancy fix would be to support huge files, which might be a bit of a project. -- gmt "It does not take a majority to prevail ... but rather an irate, tireless minority, keen on setting brushfires of freedom in the minds of men." --Samuel Adams, Patriot

2 5

Another Wine OSS hang-at-end-of-playback bug
by Matt Chapman Dec. 29, 2002

Dec. 29, 2002

Hi, I'm seeing some apps hang after playing an audio sample (even after the latest fix from Eric Pouech/Dan Kegel). I've tracked it down to the following. dwBufferSize is calculated from info->fragstotal * info->fragsize: wwo->dwBufferSize = info.fragstotal * info.fragsize; whereas dwPlayedTotal is calculated using info->bytes: wwo->dwPlayedTotal = wwo->dwWrittenTotal - (wwo->dwBufferSize - info->bytes); Thus the assumption is that, at beginning and end of playback, info->fragstotal * info->fragsize == info->bytes, so that wwo->dwPlayedTotal == wwo->dwWrittenTotal. But, for my soundcard (ymfpci driver), after asking for 15 frags * 1024 bytes the situation is: fragments = 15, fragstotal = 18, fragsize = 1024, bytes = 15612 i.e. info->fragstotal * info->fragsize = 18432, info->bytes = 15612 Thus dwPlayedTotal never reaches dwWrittenTotal and the last buffer never gets marked as done. Using info->bytes for wwo->dwBufferSize does fix my problem, not sure if there's a better solution. Matt [Looking at the driver, it looks like the difference is a safety margin to stop the DSP when it reaches the end. Arguably the driver should just report 15 in fragstotal and not bother applications with the detail that its buffer is actually 18 frags in size...] Index: dlls/winmm/wineoss/audio.c =================================================================== RCS file: /home/wine/wine/dlls/winmm/wineoss/audio.c,v retrieving revision 1.68 diff -u -r1.68 audio.c --- dlls/winmm/wineoss/audio.c 15 Dec 2002 02:59:13 -0000 1.68 +++ dlls/winmm/wineoss/audio.c 28 Dec 2002 09:56:46 -0000 @@ -1357,7 +1357,7 @@ /* Remember fragsize and total buffer size for future use */ wwo->dwFragmentSize = info.fragsize; - wwo->dwBufferSize = info.fragstotal * info.fragsize; + wwo->dwBufferSize = info.bytes; wwo->dwPlayedTotal = 0; wwo->dwWrittenTotal = 0; wwo->bNeedPost = TRUE;

2 1

Mac OS X Port of WineLib
by ATMRD＠aol.com Dec. 29, 2002

Dec. 29, 2002

Hi, I dont recall how I stumbled upon Wine and its existance, however I am intersted in recent, if any, devlopments with the porting of Wine to OS X. I checked the Wine site and most of the articles are dated with the lastest date of Nov 2000. A lot has changed in OS X since that time and it appears that a leats a couple of the main issues have been addressed during this time. The main issues which seemed to be posted are as follows: Current list of possible issues: ================================ -> Endianness. Since we are using WineLib, could have resources written in native (big) endian format with wrc. Any external data files such as cursors, bitmaps, sound would have to be converted. The PUT_WORD/GET_WORD macros need byte swapping turned off. (Did I miss anything?) -> Exception handling, Signal handling code -> Memory alignment issues -> According to "Inside MacOS X: Kernel Environment" (<A HREF="http://developer.apple.com/techpubs/macosx/Kernel/KernelEnvironment.pdf">http://developer.apple.com/techpubs/macosx/Kernel/KernelEnvironment.pdf</A>) pg. 34, Darwin supports Pthreads, "many of the POSIX APIs" I haven't been able to find any lists of incompatibilities yet, but I am afraid of the word "many". -> According to the "MacOS X Kernel Environment" book, pg. 37, Mac OSX does not support memory mapped devices through the mmap API. This would affects at least streaming sound playback. -> WSControl / WSAIoctl need to be adapted to MacOS X. (ioctl() calls can be platform dependent, /proc/net/dev on linux is probably different on OSX) -> Sound Support. Currently done with WineOSS (ties into Linux OSS drivers) Doesn't seem to be a port of OSS to MacOSX. Maybe need to do another layer specific to the Mac(?) -> Must ensure that behaviour of lower level UNIX resources like sockets, threads, files are the way WINE expects it. -> Presence of Assembly language in code will have to be written in C or translated to PowerPC assembly. (assembly is generated in spec.c files, as well as other places like in the server) -> Debugger seems tied completely to Intel architecture. (Since we will be using WineLib, we probably don't need winedbg, can use gdb?) -> Need a X11 server or need to make a x11drv replacement that is Quartz specific. (There is a XFree86 port to MacOS X, but it only runs seperately from Quartz at this time. Making the X server a rootless client of Quartz is on the TODO list of Darwin but there is no mention of its current status. There is a commercial server, at: <A HREF="http://www.tenon.com/products/xtools/"> http://www.tenon.com/products/xtools/</A> which already implements this) -- the XFree86 port to MacOS X now includes a rootless clinet of Quartz so this should be a big jump having the window manager avialable. -> Need to be able to build Windows app using gcc (might be issues such as using MS specific keywords/language constructs, etc.) Does ATL build properly with gcc? in addition James Hatheway wrote on Nov 10 2000 "To test these concerns, I made four test apps and compiled and ran them on Mac OS X. I used the "Mac OS X Public Beta Developer Tools CD" which is downloadable from<A HREF="http://connect.apple.com"> http://connect.apple.com </A> The first test app used mmap and MAP_SHARED option, the second sent messages between two programs using sendto over a socket, the third used file I/O functions (like read,write) to send messages over a socket, the fourth sent an FD over a socket to another process using sendmsg/recvmsg. I have good news, each of these programs compiled without modification on MacOS X with the standard cc, and ran perfectly!! So, I don't think there are any show stoppers that would keep us from being able to port WineLib to MacOS X. Of course there would be work to do, but at least it is definitely possible. " I dont no what has happend to the WineLib port to MacOSX if anything. However, I am willing with what time I have to begin a port, since it does seem like it can be done now, hopefully with a group of people. In addition apple has posted some information regarding win32 porting that may be a little help at "http://developer.apple.com/macosx/win32porting/". Hope you had the best of holidays. Thanks ~Sanjay Connare

3 2

Re: Changing FS type reported by Wine
by Tony Lambregts Dec. 29, 2002

Dec. 29, 2002

Duane Clark wrote: > Stephen Mollett wrote: > >> >> I'm using ReiserFS. I've also tried on a 40GB ext3 filesystem on a >> spare drive. The error comes from VirtualDub, which believes that >> it's running on a FAT32 filesystem (obviously that's what Wine >> reports to any program that asks what FS type a drive is). I've tried >> working around it by using vdub's 'segmented AVI' feature (which >> creates multiple AVIs <= 2GB) but I can't use these successfully >> under Linux. > > > In the file wine/files/drive.c, in the function > GetVolumeInformationW() (down around line 1965), is this: > > > if (fsname && fsname_len) > { > /* Diablo checks that return code ... */ > if (DOSDrives[drive].type == DRIVE_CDROM) > { > static const WCHAR cdfsW[] = {'C','D','F','S',0}; > strncpyW( fsname, cdfsW, fsname_len ); > } > else > { > static const WCHAR fatW[] = {'F','A','T',0}; > strncpyW( fsname, fatW, fsname_len ); > } > fsname[fsname_len - 1] = 0; /* ensure 0 termination */ > } > > That appears to hardcode the filesystem "name" to FAT. You might try > changing that to NTFS. That assumes that this is the call your app is > using to determine filesystem type. > > I assume you have already determined that ReiserFS supports files > larger than 2GB? > Well thats a patch that shouldn't go into cvs. <g> If it does "fix" the application though then there should be some way for wine to do it the "right way". The way I see it there are two ways to do this. 1.) wine should try to set the fsname to NTFS if underlying file system can support files sizes > 4GB. 2.)There should be a conf file option for NTFS along with MSDOS, unix and win95. The difficulty with wine trying to do this automaticly is that it would need to find the file system type of the current directory and not the root. This is of course because of the way the unix file system works. The current directory could very well be an MSDOS drive while the root drive is an ext3 and this function is only aware of the root drive. AFAICS Having it as a config option is easier to implement and removes the problem from the developers hands.<g> For myself I (think I) could implement it as a config option but Iwould prefer that wine could deal with it automaticly. If anyone has any suggestions I would appreciate it. -- Tony Lambregts

6 8

WinXP conformance test update
by Dave Miller Dec. 28, 2002

Dec. 28, 2002

These tests were run on Windows XP Professional using the latest precompiled binaries. The results of any tests not listed on or not matching http://fgouget.free.fr/wine/tests-en.shtml C:\winetests>dsound_test.exe dsound dsound: 63 tests executed, 0 marked as todo, 0 failures. C:\winetests>gdi32_test.exe generated generated: 2786 tests executed, 0 marked as todo, 0 failures. C:\winetests>kernel32_test.exe locale locale.c:154: Test failed: GetTimeFormat got '' instead of '4' locale.c:155: Test failed: GetTimeFormat: got 1 instead of 2 locale.c:181: Test failed: GetTimeFormat got '8.@:56AM' instead of '8.@:56.@:AM' locale.c:182: Test failed: GetTimeFormat: got 9 instead of 12 locale.c:190: Test failed: GetTimeFormat got '' instead of '3' locale.c:191: Test failed: GetTimeFormat: got 1 instead of 2 locale.c:474: Test failed: GetDateFormat got '5/4/2002' instead of '5/4/02' locale.c:475: Test failed: GetDateFormat: got 9 instead of 7 locale.c:499: Test failed: GetDateFormat check DATE_YEARMONTH with null format expected ERROR_INVALID_FLAGS got return of '10' and error of '0' locale: 109 tests executed, 0 marked as todo, 9 failures. C:\winetests>kernel32_test.exe path path.c:514: Test failed: GetLongPathNameA: wrong return code, 105 instead of 45 path.c:881:TMP=C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp path.c:892:TMP=C:\WINDOWS path.c:902:TMP=C:\ path.c:912:TMP=C: path: 1730 tests executed, 0 marked as todo, 1 failure. C:\winetests>kernel32_test.exe process tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process.c:378: Test failed: StartupInfoA:lpTitle expected kernel32_test.exe process, got C:\winetests\kernel32_test.exe tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process.c:530: Test failed: StartupInfoA:lpTitle expected kernel32_test.exe process, got C:\winetests\kernel32_test.exe tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. tests/process.c: 1 tests executed, 0 marked as todo, 0 failures. process: 116 tests executed, 0 marked as todo, 2 failures. C:\winetests>msvcrt_test.exe file file: 2 tests executed, 0 marked as todo, 0 failures. C:\winetests>msvcrt_test.exe scanf scanf: 8 tests executed, 0 marked as todo, 0 failures. C:\winetests>ntdll_test.exe error error: 813 tests executed, 0 marked as todo, 0 failures. C:\winetests>ntdll_test.exe generated generated: 1279 tests executed, 0 marked as todo, 0 failures. C:\winetests>ntdll_test.exe rtlbitmap rtlbitmap: 224 tests executed, 0 marked as todo, 0 failures. C:\winetests>ntdll_test.exe rtlstr rtlstr: 38 tests executed, 0 marked as todo, 0 failures. C:\winetests>oleaut32_test.exe safearray safearray.c:131: Test failed: SAC(20,1,[1,0]), result 8, expected 0 safearray.c:131: Test failed: SAC(21,1,[1,0]), result 8, expected 0 safearray.c:131: Test failed: SAC(37,1,[1,0]), result 4, expected 0 safearray.c:131: Test failed: SAC(38,1,[1,0]), result 4, expected 0 safearray: 348 tests executed, 0 marked as todo, 4 failures. C:\winetests>oleaut32_test.exe vartest vartest.c:1707: ======== Testing VarUI1FromXXX ======== vartest.c:1713:VarUI1FromI2: passing in NULL as return val makes it crash, needto write proper test. vartest.c:1797: ======== Testing VarUI2FromXXX ======== vartest.c:1802:VarUI2FromI2: passing in NULL as return val makes it crash, needs to be fixed. vartest.c:1874: ======== Testing VarUI4FromXXX ======== vartest.c:1877:VarUI4FromI2: passing in NULL as return val makes it crash, implement me. vartest.c:1952: ======== Testing VarI1FromXXX ======== vartest.c:2005: ======== Testing VarI2FromXXX ======== vartest.c:2048: ======== Testing VarI4FromXXX ======== vartest.c:2092: ======== Testing VarR4FromXXX ======== vartest.c:2139: ======== Testing VarR8FromXXX ======== vartest.c:2159: ======== Testing VarDateFromXXX ======== vartest.c:2209: Test failed: VarDateFromStr([7]="0.49") got 0.0340278 instead of 0.034028 vartest.c:2209: Test failed: VarDateFromStr([8]="0.5") got 0.00347222 instead of 0.003472 vartest.c:2209: Test failed: VarDateFromStr([9]="0.51") got 0.0354167 instead of 0.035417 vartest.c:2209: Test failed: VarDateFromStr([34]=" 1 2 ") got 37258 instead of 35797 vartest.c:2209: Test failed: VarDateFromStr([39]="1.2.3") got 0.0430903 instead of 0.04309 vartest.c:2209: Test failed: VarDateFromStr([69]=" 1999/ 11/21 11 :11:11am") got 36485.5 instead of 36485.5 vartest.c:2209: Test failed: VarDateFromStr([70]="11/11/1999 11:11:11Am") got 36475.5 instead of 36475.5 vartest.c:2209: Test failed: VarDateFromStr([71]="11/11/1999 11:11:11PM") got 36476 instead of 36476 vartest.c:2209: Test failed: VarDateFromStr([73]="11/11/1999 0:0:11am") got 36475 instead of 36475 vartest.c:2209: Test failed: VarDateFromStr([75]="11/11/1999 11:11:11am") got 36475.5 instead of 36475.5 vartest.c:2209: Test failed: VarDateFromStr([77]="11/11/1999 11:11AM") got 36475.5 instead of 36475.5 vartest.c:2209: Test failed: VarDateFromStr([78]="11/11/1999 1AM") got 36475 instead of 36475 vartest.c:2209: Test failed: VarDateFromStr([80]="11/11/1999 11:11:11") got 36475.5 instead of 36475.5 vartest.c:2209: Test failed: VarDateFromStr([89]="1 January 1999 11AM") got 36161.5 instead of 36161.5 vartest.c:2209: Test failed: VarDateFromStr([90]="4AM 11/11/1999") got 36475.2 instead of 36475.2 vartest.c:2209: Test failed: VarDateFromStr([109]="1.5") got 0.0451389 instead of 0.045139 vartest.c:2209: Test failed: VarDateFromStr([110]="2.5") got 0.0868056 instead of 0.086806 vartest.c:2209: Test failed: VarDateFromStr([111]="3.5") got 0.128472 instead of 0.128472 vartest.c:2209: Test failed: VarDateFromStr([112]="4.5") got 0.170139 instead of 0.170139 vartest.c:2224: ======== Testing VarBoolFromXXX ======== vartest.c:2284: ======== Testing VarBSTRFromXXX ======== vartest.c:2309: Test failed: d is 7.65432e+015, should be cvt. to 7.65432198765432e+15, but return val is "7.65432198765432E+15" vartest.c:2316: Test failed: d is -7.65432e+015, should be cvt. to -7.65432198765432e+15, but return val is "-7.65432198765432E+15" vartest.c:2309: Test failed: d is 8.76543e+016, should be cvt. to 8.76543219876543e+16, but return val is "8.76543219876543E+16" vartest.c:2316: Test failed: d is -8.76543e+016, should be cvt. to -8.76543219876543e+16, but return val is "-8.76543219876543E+16" vartest.c:2309: Test failed: d is 9.87654e+017, should be cvt. to 9.87654321987654e+17, but return val is "9.87654321987654E+17" vartest.c:2316: Test failed: d is -9.87654e+017, should be cvt. to -9.87654321987654e+17, but return val is "-9.87654321987654E+17" vartest.c:2309: Test failed: d is 1.98765e+018, should be cvt. to 1.98765432198765e+18, but return val is "1.98765432198765E+18" vartest.c:2316: Test failed: d is -1.98765e+018, should be cvt. to -1.98765432198765e+18, but return val is "-1.98765432198765E+18" vartest.c:2309: Test failed: d is 2.19877e+019, should be cvt. to 2.19876543219877e+19, but return val is "2.19876543219877E+19" vartest.c:2316: Test failed: d is -2.19877e+019, should be cvt. to -2.19876543219877e+19, but return val is "-2.19876543219877E+19" vartest.c:2360: Test failed: d is 7.65432e+015, should be cvt. to 7.65432198765432e+15, but return val is "7.65432198765432E+15" vartest.c:2366: Test failed: d is -7.65432e+015, should be cvt. to -7.65432198765432e+15, but return val is "-7.65432198765432E+15" vartest.c:2360: Test failed: d is 8.76543e+016, should be cvt. to 8.76543219876543e+16, but return val is "8.76543219876543E+16" vartest.c:2366: Test failed: d is -8.76543e+016, should be cvt. to -8.76543219876543e+16, but return val is "-8.76543219876543E+16" vartest.c:2360: Test failed: d is 9.87654e+017, should be cvt. to 9.87654321987654e+17, but return val is "9.87654321987654E+17" vartest.c:2366: Test failed: d is -9.87654e+017, should be cvt. to -9.87654321987654e+17, but return val is "-9.87654321987654E+17" vartest.c:2360: Test failed: d is 1.98765e+018, should be cvt. to 1.98765432198765e+18, but return val is "1.98765432198765E+18" vartest.c:2366: Test failed: d is -1.98765e+018, should be cvt. to -1.98765432198765e+18, but return val is "-1.98765432198765E+18" vartest.c:2360: Test failed: d is 2.19877e+019, should be cvt. to 2.19876543219877e+19, but return val is "2.19876543219877E+19" vartest.c:2366: Test failed: d is -2.19877e+019, should be cvt. to -2.19876543219877e+19, but return val is "-2.19876543219877E+19" vartest.c:2383: Test failed: d is 8.76543e+007, should be cvt. to 8.765432e+07, but return val is "8.765432E+07" vartest.c:2389: Test failed: d is -8.76543e+007, should be cvt. to -8.765432e+07, but return val is "-8.765432E+07" vartest.c:2383: Test failed: d is 9.87654e+008, should be cvt. to 9.876543e+08, but return val is "9.876543E+08" vartest.c:2389: Test failed: d is -9.87654e+008, should be cvt. to -9.876543e+08, but return val is "-9.876543E+08" vartest.c:2383: Test failed: d is 1.98765e+009, should be cvt. to 1.987654e+09,but return val is "1.987654E+09" vartest.c:2389: Test failed: d is -1.98765e+009, should be cvt. to -1.987654e+09, but return val is "-1.987654E+09" vartest.c:2409: Test failed: d is 0.2345, should be cvt. to 0.2345001, but return val is "0.2345" vartest.c:2433: Test failed: d is 654322, should be cvt. to 654322.2, but return val is "654322.3" vartest.c:2439: Test failed: d is -654322, should be cvt. to -654322.2, but return val is "-654322.3" vartest.c:2433: Test failed: d is 8.76543e+007, should be cvt. to 8.765432e+07, but return val is "8.765432E+07" vartest.c:2439: Test failed: d is -8.76543e+007, should be cvt. to -8.765432e+07, but return val is "-8.765432E+07" vartest.c:2433: Test failed: d is 9.87654e+008, should be cvt. to 9.876543e+08, but return val is "9.876543E+08" vartest.c:2439: Test failed: d is -9.87654e+008, should be cvt. to -9.876543e+08 , but return val is "-9.876543E+08" vartest.c:2433: Test failed: d is 1.98765e+009, should be cvt. to 1.987654e+09, but return val is "1.987654E+09" vartest.c:2439: Test failed: d is -1.98765e+009, should be cvt. to -1.987654e+09 , but return val is "-1.987654E+09" vartest.c:2494: ======== Testing Hi-Level Variant API ======== vartest.c:2561: Test failed: should be 5/11/94 7:58:42 AM vartest.c:2579:-------------- Testing different VARTYPES ---------------- vartest: 2281 tests executed, 0 marked as todo, 55 failures. C:\winetests>shell32_test.exe generated generated: 272 tests executed, 0 marked as todo, 0 failures. C:\winetests>shlwapi_test.exe generated generated: 19 tests executed, 0 marked as todo, 0 failures. C:\winetests>urlmon_test.exe generated generated: 4 tests executed, 0 marked as todo, 0 failures. C:\winetests>user32_test.exe generated generated: 1524 tests executed, 0 marked as todo, 0 failures. C:\winetests>wininet_test.exe generated generated: 252 tests executed, 0 marked as todo, 0 failures. wininet/http passes now. Lots of output http: 24 tests executed, 0 marked as todo, 0 failures.

2 1

Re: Make RECT identical to RECTL, fix compile warnings (resending)
by Dimitrie O. Paun Dec. 28, 2002

Dec. 28, 2002

On December 27, 2002 01:29 pm, Dan Kegel wrote: > I think this patch touches every single TRACE > statement that prints out a RECT. Many different > formats are used... might be nice to standardize them > sometime. (See my related post about maybe using > macros for that.) Now that you've identified all these places, it seems to me the perfect oportunity to standardise them. At the very least, we should convert them all to a common format (say (x0,y0)-(x1,y1), or anything you fancy) so we can more easily grep/sed for them later. But I'd certainly prefer the debugrect() approach, provided Alexandre accepts it. -- Dimi.

2 1