February 2003 - Wine-Bugs - list.winehq.org

[Bug 1283] - bsd -automount'ed drives ignored (e.g. "A:" on /vol/a via autofs master.vol)
by wine-bugs＠winehq.com Feb. 16, 2003

Feb. 16, 2003

http://bugs.winehq.com/show_bug.cgi?id=1283 tony_lambregts(a)telusplanet.net changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|wine-bugs(a)winehq.com |tony_lambregts(a)telusplanet.n | |et ------- Additional Comments From tony_lambregts(a)telusplanet.net 2003-02-16 12:41 ------- Excellent bug report. It seems that the cause of the problem is that the mount point for your floppy does not exist untill autofs mounts it. So another fix for your problem is to define a mount point (create that directory). That however seems to be defeating the way that autofs works. I am fairly familiar with this portion of wine and how it behaves on linux. I would also like it changed but for different reasons. let me explain. In general a mount point has to exist in order to mount a device. That mount point has a st_ino number. When a device is mounted that number is different from when no device is mounted. The current (ASCII) code for returning the drive letter fails when the ino number changed. All this however is (almost) irrelevant to your patch. What is missing from this patch is the documentation. The sample config and users guide need to be updated to do this properly. documentation/samples/config documentation/configuring.sgml Are the relevant files. If you need help with this aspect please tell me. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1283>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1283] - bsd -automount'ed drives ignored (e.g. "A:" on /vol/a via autofs master.vol)
by wine-bugs＠winehq.com Feb. 16, 2003

Feb. 16, 2003

http://bugs.winehq.com/show_bug.cgi?id=1283 ------- Additional Comments From guidod-2003-(a)gmx.de 2003-02-16 09:56 ------- Created an attachment (id=402) add .wine/config AutoMount option to be checked in DRIVE_Init DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1283>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1283] New: - bsd -automount'ed drives ignored (e.g. "A:" on /vol/a via autofs master.vol)
by wine-bugs＠winehq.com Feb. 16, 2003

Feb. 16, 2003

http://bugs.winehq.com/show_bug.cgi?id=1283 Summary: bsd -automount'ed drives ignored (e.g. "A:" on /vol/a via autofs master.vol) Product: Wine Version: CVS Platform: PC URL: http://freespace.sf.net/guidod/wine-vol-a/ OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-winelib AssignedTo: wine-bugs(a)winehq.com ReportedBy: guidod-2003-(a)gmx.de The following text is a shortened description of the bug - a long description, screenshots and patches can be found at http://freespace.sf.net/guidod/wine-vol-a/ The problem: If there is no medium in a autofs mounted floppy drive at startup of wine, then files on the floppy are inaccessible even when a medium is inserted later. The diagnosis: The DRIVE_Init will throw away any mount-point that does not exist at startup time - it does not make it to the internal drive. It will not check later whether the mount-point came into existance somewhen in between - you need to restart The real way: There is no need to keep this behaviour, the wine's drive access method can handle it that a mount-point is removed somewhere in between: it prints warning messages and continues to work properly. This is partly the windowish way: just say the drive is inaccessible as warning during runtime, do not kill it beforehand. The patch: A .wine/config boolean option "AutoMount" is introduced that will default to the old behavior. When being enabled then a warning-message logged but the drive is kept in the internal drivelist and can be seen in the file-open dialog-box. At the moment, applications work properly with wine cvs but we still need to patch the sources like that to make it useable for us. cheers, guido counter.li.org #81555 DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1283>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1282] New: - excessive MDI slowdowns (app: IDA Pro >= 4.30)
by wine-bugs＠winehq.com Feb. 16, 2003

Feb. 16, 2003

http://bugs.winehq.com/show_bug.cgi?id=1282 Summary: excessive MDI slowdowns (app: IDA Pro >= 4.30) Product: Wine Version: 20030115 Platform: PC OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.com ReportedBy: scut(a)nb.in-berlin.de Using the latest version of IDA Pro (Interactive Disassembler, http://www.datarescue.com/idabase/) version 4.30, the now MDI based GUI turns out to be unusable. While the GUI is displayed correctly, all GUI actions are very slow and every simple action, such as a click on an MDI document window is taking > 20 seconds to process. The program behaves correctly though after the "blocking" has passed, which happens on every GUI action. Sorry for the vague bug description, you may want to reproduce the bug yourself using an evaluation version available from http://www.datarescue.com/idabase/ida4down.htm by email request. Versions < 4.30 are non-MDI based and behave almost right under wine, 4.30 is unusable due to the slowdowns. I use the Debian/sid wine packages, version 20030115. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1282>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1281] New: - Wine core dumps very often on FreeBSD
by wine-bugs＠winehq.com Feb. 14, 2003

Feb. 14, 2003

http://bugs.winehq.com/show_bug.cgi?id=1281 Summary: Wine core dumps very often on FreeBSD Product: Wine Version: 20030115 Platform: PC OS/Version: FreeBSD Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-debug AssignedTo: wine-bugs(a)winehq.com ReportedBy: q(a)galgenberg.net I already described the problems I have with Wine on FreeBSD in Bug #803. Here is a quick overview: wine + VirtualDub + Win98SE: fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo not yet supported on this system fixme:mmsys:WMMMidiRunOnce16 (), stub! err:winmm:MMDRV_InitPerType Strange: mapper with 8 > 1 devices err:thunk:_loadthunk (USER.EXE, UsrMpr_ThunkData16, MPR.DLL): Bad magic fUh (should be SL01) err:thunk:_loadthunk (USER.EXE, UsrMpr_ThunkData16, MPR.DLL): Bad magic fUh (should be SL01) (Exit Code 133) With builtin MPR.DLL (whatever that is): fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo not yet supported on this system fixme:mmsys:WMMMidiRunOnce16 (), stub! err:winmm:MMDRV_InitPerType Strange: mapper with 8 > 1 devices fixme:file:DeviceIo_MMDEVLDR (5,0x0,0,0x283b2bdc,4,0x28622e18,0x0): stub fixme:gdi:Escape16 unknown/unsupported 16-bit escape c03 (56,0x28632f3e,0x28632f86 fixme:gdi:Escape16 unknown/unsupported 16-bit escape c03 (56,0x28632f3e,0x28632f86 fixme:x11drv:X11DRV_GetDeviceCaps (0xafc): CAPS1 is unimplemented, will return 0 fixme:hook:NotifyWinEvent (32780,0x30029,-4,1)-stub! fixme:process:CreateProcessA (C:\windows\SYSTEM\DDHELP.EXE,...): NORMAL_PRIORITY_CLASS ignored fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:cdrom:CDROM_GetIdeInterface not implemented for BSD fixme:reg:GetSystemInfo not yet supported on this system fixme:x11drv:X11DRV_GetDeviceCaps (0xafc): CAPS1 is unimplemented, will return 0 fixme:mmsys:WMMMidiRunOnce16 (), stub! err:winmm:MMDRV_InitPerType Strange: mapper with 8 > 1 devices fixme:x11drv:X11DRV_GetDeviceCaps (0x74): CAPS1 is unimplemented, will return 0 GetModuleHandleA succeed LoadLibrary returns baaa0000 fixme:system:EnumDisplayDevicesA (0x0,0,0x286226e8,0x00000000), stub! wine: Unhandled exception, starting debugger... Warning: L"/usr/bin/winedbg.exe" not accessible from a configured DOS drive Warning: L"/usr/bin/winedbg" not accessible from a configured DOS drive Warning: L"/usr/bin/winedbg 134705408.exe" not accessible from a configured DOS drive Warning: L"/usr/bin/winedbg 134705408" not accessible from a configured DOS drive Warning: L"/usr/bin/winedbg 134705408 152.exe" not accessible from a configured DOS drive Warning: L"/usr/bin/winedbg 134705408 152" not accessible from a configured DOS drive err:seh:start_debugger Couldn't start debugger ("/usr/bin/winedbg 134705408 152") (2) Read the Wine Developers Guide on how to set up winedbg or another debugger err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x28e9990e err:seh:EXC_DefaultHandling Unhandled exception code c0000005 flags 0 addr 0x28e9990e [1000 more lines of the same error] zsh: 30788 illegal hardware instruction (core dumped) wine --dll mpr=b virtualdub (Why is Wine looking for winedbg in /usr/bin? Wine got installed to /usr/local/bin!) Here is one backtrace I did with gdb: err:module:BUILTIN32_dlopen failed to load .so lib for builtin vdoenc32.dll: Cannot open "/usr/local/lib/wine/vdoenc32.dll.so" Program received signal SIGBUS, Bus error. 0x280ebd80 in IsBadWritePtr (ptr=0x29a50000, size=40) at ../../memory/virtual.c:568 568 p[0] |= 0; (gdb) bt #0 0x280ebd80 in IsBadWritePtr (ptr=0x29a50000, size=40) at ../../memory/virtual.c:568 #1 0x29a542af in ?? () #2 0x29a53359 in ?? () #3 0x79a9199a in ?? () #4 0x41b57e in ?? () #5 0x2d0 in ?? () Error accessing memory address 0x28: Bad address. (gdb) "Error accessing memory: Bad address"??? This sounds like serious breakage to me. I got enough core dumps when trying to get Starcraft/Diablo to work and I guess it's because there are tons of functions not (yet) implemented for non-linux system. I myself am right now trying to implement CDROM_GetIdeInterface for BSD systems, but my C skills are ... lacking :( DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1281>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1280] - edit control bug - EM_LIMITTEXT does not work
by wine-bugs＠winehq.com Feb. 14, 2003

Feb. 14, 2003

http://bugs.winehq.com/show_bug.cgi?id=1280 ------- Additional Comments From felipewd(a)elipse.com.br 2003-02-14 09:44 ------- Created an attachment (id=401) .tar.gz source program which sets (in the "about" dialog) the maximum input to 10 characters DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1280>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1280] New: - edit control bug - EM_LIMITTEXT does not work
by wine-bugs＠winehq.com Feb. 14, 2003

Feb. 14, 2003

http://bugs.winehq.com/show_bug.cgi?id=1280 Summary: edit control bug - EM_LIMITTEXT does not work Product: Wine Version: 20030115 Platform: PC OS/Version: other Status: UNCONFIRMED Severity: major Priority: P2 Component: wine-gui AssignedTo: wine-bugs(a)winehq.com ReportedBy: felipewd(a)elipse.com.br When you try to limit the maximum chars accepted in an edit control by doing something like this: SendMessage(hwndEdit, EM_LIMITTEXT, 10, 0); Wine simply ignores it, and let the user type more than 10 (in this example) characters. This looks bad, because the user could eventually overflow the allocated memory for the dialog, making the program crash. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1280>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1279] New: - Dialog scrolling visual bug
by wine-bugs＠winehq.com Feb. 13, 2003

Feb. 13, 2003

http://bugs.winehq.com/show_bug.cgi?id=1279 Summary: Dialog scrolling visual bug Product: Wine Version: 20030115 Platform: PC OS/Version: Windows 2000 Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-gdi AssignedTo: wine-bugs(a)winehq.com ReportedBy: snoopy97(a)mail.ru The bug with ChessNet application http://www.chess.net/cnfw/download/cnfw254.exe When I open game dailog it looks like this http://olegpro.netfirms.com/bug-free.png during scrolling dialog there's visual glitches, and the dialog can llok like this http://olegpro.netfirms.com/bug.png (some portions of it became cleared) DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1279>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1278] - 3DSMax registry crash
by wine-bugs＠winehq.com Feb. 13, 2003

Feb. 13, 2003

http://bugs.winehq.com/show_bug.cgi?id=1278 ------- Additional Comments From tony_lambregts(a)telusplanet.net 2003-02-13 11:39 ------- Thankyou for the bug report. Just a comment on the attached log(s) usually only the last 3000 lines before "starting debugger..." are required (unless we are debugging the debugger<g>) the lines after that are calls made by the debugger to set up and run. trace:reg:NtCreateKey (0x114,L"ShellNew",L"",0,f003f,0x40762900) trace:reg:NtCreateKey <- 0x118 00000034:Ret ntdll.NtCreateKey() retval=00000000 ret=40a2bb76 00000034:Call ntdll.RtlFreeUnicodeString(407627ac) ret=40a2bb83 00000034:Ret ntdll.RtlFreeUnicodeString() retval=00000001 ret=40a2bb83 00000034:Call ntdll.RtlNtStatusToDosError(00000000) ret=40a2bb0f 00000034:Ret ntdll.RtlNtStatusToDosError() retval=00000000 ret=40a2bb0f 00000034:Ret advapi32.RegCreateKeyExA() retval=00000000 ret=300b123a 00000034:Call advapi32.RegSetValueExA(00000118,300b40d8 "NullFile",00000000,00000001,00000000,00000000) ret=300b108b 00000034:Call kernel32.GetVersion() ret=40a2d683 00000034:Ret kernel32.GetVersion() retval=c0000004 ret=40a2d683 wine: Unhandled exception, starting debugger... Trim after this. What is program is this? Is there a demo/download available? Thanks. DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1278>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0

[Bug 1278] - 3DSMax registry crash
by wine-bugs＠winehq.com Feb. 13, 2003

Feb. 13, 2003

http://bugs.winehq.com/show_bug.cgi?id=1278 ------- Additional Comments From mgf(a)taktile.com 2003-02-13 06:22 ------- Created an attachment (id=400) please ignore the previous log file. it is irrelevant DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://bugs.winehq.com/show_bug.cgi?id=1278>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.

1 0