March 2021 - Wine-Bugs - list.winehq.org

[Bug 44837] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing ' ntoskrnl.exe.PsAcquireProcessExitSynchronization'
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=44837 Bug ID: 44837 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing 'ntoskrnl.exe.PsAcquireProcessExitSynchronization' Product: Wine Version: 3.4 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44811 --- snip --- ... 0052:Call KERNEL32.GetModuleHandleW(7ec246fc L"ntoskrnl.exe") ret=7ec1a2f6 0052:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec1a2f6 0052:Call KERNEL32.GetProcAddress(7ec00000,0011d4b8 "PsAcquireProcessExitSynchronization") ret=7ec1a30b 0052:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1a30b 0052:Call KERNEL32.GetModuleHandleW(7ec24718 L"hal.dll") ret=7ec1a324 0052:Ret KERNEL32.GetModuleHandleW() retval=f7ac0000 ret=7ec1a324 0052:Call KERNEL32.GetProcAddress(f7ac0000,0011d4b8 "PsAcquireProcessExitSynchronization") ret=7ec1a33f 0052:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1a33f 0052:Call ntdll.RtlFreeAnsiString(0065eb30) ret=7ec1a351 0052:Ret ntdll.RtlFreeAnsiString() retval=0065eb30 ret=7ec1a351 0052:fixme:ntoskrnl:MmGetSystemRoutineAddress L"PsAcquireProcessExitSynchronization" not found 0052:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=007da46e 0052:Ret driver init 0x78d000 (obj=0x11caa0,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000001 0052:trace:winedevice:init_driver init done for L"BEDaisy" obj 0x11caa0 ... 0052:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000001 ret=7effb786 0052:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000001 ... --- snip --- Discussion of this API (potential use) here https://forum.sysinternals.com/discussion-howto-enumerate-handles_topic1940… https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/windows-ke… https://docs.microsoft.com/en-us/windows-hardware/drivers/kernel/run-down-p… https://www.geoffchappell.com/studies/windows/km/ntoskrnl/api/index.htm (PsAcquireProcessExitSynchronization 6.0 and higher ) $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.4-192-gd7430abd40 Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 9

[Bug 44906] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing ' ntoskrnl.exe.ExfUnblockPushLock'
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=44906 Bug ID: 44906 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to missing 'ntoskrnl.exe.ExfUnblockPushLock' Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, ticket dedicated to: https://github.com/wine-staging/wine-staging/blob/master/patches/ntoskrnl-S… Prerequisite: * bug 44837 --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1 ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "PsAcquireProcessExitSynchronization") ret=7ec18527 0035:Ret KERNEL32.GetProcAddress() retval=7ec0e468 ret=7ec18527 ... 0035:trace:ntoskrnl:MmGetSystemRoutineAddress L"PsAcquireProcessExitSynchronization" -> 0x7ec0e468 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=7ec0e468 ret=007da46e 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ecac) ret=00868d6d ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "PsReleaseProcessExitSynchronization") ret=7ec18527 ... 0035:trace:ntoskrnl:MmGetSystemRoutineAddress L"PsReleaseProcessExitSynchronization" -> 0x7ec0e540 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=7ec0e540 ret=00868d6d 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ecac) ret=0084d372 ... 0035:Call KERNEL32.GetModuleHandleW(7ec229dc L"ntoskrnl.exe") ret=7ec18512 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18512 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d630 "ExfUnblockPushLock") ret=7ec18527 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec18527 0035:Call KERNEL32.GetModuleHandleW(7ec229f8 L"hal.dll") ret=7ec18540 0035:Ret KERNEL32.GetModuleHandleW() retval=f79f0000 ret=7ec18540 0035:Call KERNEL32.GetProcAddress(f79f0000,0011d630 "ExfUnblockPushLock") ret=7ec1855b 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec1855b ... 0035:fixme:ntoskrnl:MmGetSystemRoutineAddress L"ExfUnblockPushLock" not found 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=0084d372 0035:Ret driver init 0x78d000 (obj=0x11cc00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000001 ... 0035:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000001 ret=7effb832 0035:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000001 --- snip --- $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 44910] New: BattlEye 'BEDaisy' kernel service fails in driver entry point due to ' ntoskrnl.exe.ObReferenceObjectByHandle' stub (needs STATUS_SUCCESS)
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=44910 Bug ID: 44910 Summary: BattlEye 'BEDaisy' kernel service fails in driver entry point due to 'ntoskrnl.exe.ObReferenceObjectByHandle' stub (needs STATUS_SUCCESS) Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 44907 Prerequisite: * bug 44837 -> missing 'ntoskrnl.exe.Ps{Acquire,Release}ProcessExitSynchronization' * bug 44906 -> missing 'ntoskrnl.exe.ExfUnblockPushLock' * bug 44907 -> missing 'fltmgr.sys.FltGetRoutineAddress' Unlike the other bug reports, I added +server debug channel to show which handle is being dereferenced. --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl,+server wine net start BEDaisy >>log.txt 2>&1 ... 0033:Call driver init 0x78d000 (obj=0x11cb00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") ... 0033:Call ntoskrnl.exe.PsCreateSystemThread(0065ec4c,001fffff,0065ec50,00000000,00000000,0078308e,00000000) ret=0080858c 0033:Call ntdll.RtlCreateUserThread(ffffffff,00000000,00000000,00000000,00000000,00000000,0078308e,00000000,0065ec4c,00000000) ret=7ec1823e 0033: *fd* 21 <- 145 0033: new_thread( access=001fffff, attributes=00000000, suspend=0, request_fd=21 ) 0033: new_thread() = 0 { tid=0035, handle=0040 } 0033:Ret ntdll.RtlCreateUserThread() retval=00000000 ret=7ec1823e 0033:Ret ntoskrnl.exe.PsCreateSystemThread() retval=00000000 ret=0080858c 0033:Call ntoskrnl.exe.ObReferenceObjectByHandle(00000040,001fffff,00000000,00000000,0078b55c,00000000) ret=007840d4 0033:fixme:ntoskrnl:ObReferenceObjectByHandle stub: 0x40 1fffff (nil) 0 0x78b55c (nil) 0033:Ret ntoskrnl.exe.ObReferenceObjectByHandle() retval=c0000002 ret=007840d4 0033:Call ntoskrnl.exe.KeSetEvent(0078b3f4,00000000,00000000) ret=00790914 0033:fixme:ntoskrnl:KeSetEvent (0x78b3f4, 0, 0): stub 0033:Ret ntoskrnl.exe.KeSetEvent() retval=00000000 ret=00790914 0033:Call ntoskrnl.exe.ZwClose(00000040) ret=007f2c73 0033:Call ntdll.NtClose(00000040) ret=7bc803ab 0033: close_handle( handle=0040 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7bc803ab 0033:Ret ntoskrnl.exe.ZwClose() retval=00000000 ret=007f2c73 0033:Call fltmgr.sys.FltUnregisterFilter(deadbeaf) ret=007fd488 0033:fixme:fltmgr:FltUnregisterFilter (0xdeadbeaf): stub 0033:Ret fltmgr.sys.FltUnregisterFilter() retval=00000039 ret=007fd488 0033:Call ntoskrnl.exe.PsRemoveCreateThreadNotifyRoutine(0078130c) ret=0082f2bc 0033:fixme:ntoskrnl:PsRemoveCreateThreadNotifyRoutine stub: 0x78130c 0033:Ret ntoskrnl.exe.PsRemoveCreateThreadNotifyRoutine() retval=00000000 ret=0082f2bc 0033:Call ntoskrnl.exe.PsRemoveLoadImageNotifyRoutine(00781dc6) ret=008242ab 0033:fixme:ntoskrnl:PsRemoveLoadImageNotifyRoutine stub: 0x781dc6 0033:Ret ntoskrnl.exe.PsRemoveLoadImageNotifyRoutine() retval=00000000 ret=008242ab 0033:Call ntoskrnl.exe.KeWaitForSingleObject(0078b530,00000000,00000000,00000000,00000000) ret=0080b669 0033:fixme:ntoskrnl:KeWaitForSingleObject stub: 0x78b530, 0, 0, 0, (nil) 0033:Ret ntoskrnl.exe.KeWaitForSingleObject() retval=c0000002 ret=0080b669 0033:Call ntoskrnl.exe.ObUnRegisterCallbacks(deadbeaf) ret=007ac56b 0033:fixme:ntoskrnl:ObUnRegisterCallbacks stub: 0xdeadbeaf 0033:Ret ntoskrnl.exe.ObUnRegisterCallbacks() retval=0000003b ret=007ac56b 0033:Call ntoskrnl.exe.KeReleaseMutex(0078b530,00000000) ret=00839822 0033:fixme:ntoskrnl:KeReleaseMutex stub: 0x78b530, 0 0033:Ret ntoskrnl.exe.KeReleaseMutex() retval=c0000002 ret=00839822 0033:Call ntoskrnl.exe.IoDeleteSymbolicLink(0065ec74) ret=0080d6dc 0033:Call ntdll.NtOpenSymbolicLinkObject(0065eb40,00000000,0065eb28) ret=7ec158ab 0033: open_symlink( access=00000000, attributes=00000040, rootdir=0000, name=L"\\DosDevices\\BattlEye" ) 0033: open_symlink() = 0 { handle=0044 } 0033:Ret ntdll.NtOpenSymbolicLinkObject() retval=00000000 ret=7ec158ab 0033: unlink_object( handle=0044 ) 0033: unlink_object() = 0 0033:Call ntdll.NtClose(00000044) ret=7ec15924 0033: close_handle( handle=0044 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7ec15924 0033:Ret ntoskrnl.exe.IoDeleteSymbolicLink() retval=00000000 ret=0080d6dc 0033:Call ntoskrnl.exe.IoDeleteDevice(0011cce0) ret=00867fef 0033:trace:ntoskrnl:IoDeleteDevice 0x11cce0 0033: delete_device( handle=0038 ) 0033: delete_device() = 0 0033:Call ntdll.NtClose(00000038) ret=7ec15773 0033: close_handle( handle=0038 ) 0033: close_handle() = 0 0033:Ret ntdll.NtClose() retval=00000000 ret=7ec15773 ... 0033:Ret ntoskrnl.exe.IoDeleteDevice() retval=00000001 ret=00867fef 0033:Ret driver init 0x78d000 (obj=0x11cb00,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000002 ... 0033:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000002 ret=7effb832 0033:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000002 --- snip --- MSDN: https://docs.microsoft.com/en-us/windows-hardware/drivers/ddi/content/wdm/n… One of MS official kernel driver examples, illustrating how the API is meant to be used here (general pattern for getting thread object pointer): https://github.com/Microsoft/Windows-driver-samples/blob/master/general/can… --- snip --- ... status = PsCreateSystemThread(&threadHandle, (ACCESS_MASK)0, NULL, (HANDLE) 0, NULL, CsampPollingThread, deviceObject ); if ( !NT_SUCCESS( status )) { IoDeleteSymbolicLink( &unicodeDosDeviceName ); IoDeleteDevice( deviceObject ); return status; } // // Convert the Thread object handle into a pointer to the Thread object // itself. Then close the handle. // ObReferenceObjectByHandle(threadHandle, THREAD_ALL_ACCESS, NULL, KernelMode, &devExtension->ThreadObject, NULL ); ZwClose(threadHandle); ... --- snip --- NOTE: Unlike the snippet shown above, 'BEDaisy' driver checks the return value of 'ObReferenceObjectByHandle' and initiates teardown on failure. For testing I simply returned 'STATUS_SUCCESS' but also set the object pointer to a magic value (if ptr is non-NULL). The idea is when the driver tries to access/dereference the pointer we can easily see that a "poor" man's "succeed" stub is not enough. It seems it doesn't need a real thread object for now and runs much further. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.5-107-gf4573adb0f Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 5

[Bug 44908] New: BattlEye 'BEDaisy' kernel service wants ' ntoskrnl.exe.ObGetObjectType'
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=44908 Bug ID: 44908 Summary: BattlEye 'BEDaisy' kernel service wants 'ntoskrnl.exe.ObGetObjectType' Product: Wine Version: 3.5 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: ntoskrnl Assignee: wine-bugs(a)winehq.org Reporter: focht(a)gmx.net Distribution: --- Hello folks, continuation of bug 4907 Prerequisite: * bug 44837 -> missing 'ntoskrnl.exe.Ps{Acquire,Release}ProcessExitSynchronization' * bug 44906 -> missing 'ntoskrnl.exe.ExfUnblockPushLock' * bug 44907 -> missing 'fltmgr.sys.FltGetRoutineAddress' --- snip --- $ WINEDEBUG=+seh,+relay,+ntoskrnl wine net start BEDaisy >>log.txt 2>&1 ... 0035:Call driver init 0x78d000 (obj=0x11cbf8,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") ... 0035:Call ntoskrnl.exe.RtlGetVersion(0078b270) ret=0080750a 0035:Call ntdll.RtlGetVersion(0078b270) ret=7bc803ab 0035:Ret ntdll.RtlGetVersion() retval=00000000 ret=7bc803ab 0035:Ret ntoskrnl.exe.RtlGetVersion() retval=00000000 ret=0080750a 0035:Call ntoskrnl.exe.MmGetSystemRoutineAddress(0065ec68) ret=007a8561 0035:Call ntdll.RtlUnicodeStringToAnsiString(0065eb30,0065ec68,00000001) ret=7ec1855e 0035:Ret ntdll.RtlUnicodeStringToAnsiString() retval=00000000 ret=7ec1855e 0035:Call KERNEL32.GetModuleHandleW(7ec22a9c L"ntoskrnl.exe") ret=7ec18572 0035:Ret KERNEL32.GetModuleHandleW() retval=7ec00000 ret=7ec18572 0035:Call KERNEL32.GetProcAddress(7ec00000,0011d610 "ObGetObjectType") ret=7ec18587 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec18587 0035:Call KERNEL32.GetModuleHandleW(7ec22ab8 L"hal.dll") ret=7ec185a0 0035:Ret KERNEL32.GetModuleHandleW() retval=f7b10000 ret=7ec185a0 0035:Call KERNEL32.GetProcAddress(f7b10000,0011d610 "ObGetObjectType") ret=7ec185bb 0035:Ret KERNEL32.GetProcAddress() retval=00000000 ret=7ec185bb 0035:Call ntdll.RtlFreeAnsiString(0065eb30) ret=7ec185cd 0035:Ret ntdll.RtlFreeAnsiString() retval=0065eb30 ret=7ec185cd 0035:fixme:ntoskrnl:MmGetSystemRoutineAddress L"ObGetObjectType" not found 0035:Ret ntoskrnl.exe.MmGetSystemRoutineAddress() retval=00000000 ret=007a8561 ... 0035:Ret driver init 0x78d000 (obj=0x11cbf8,str=L"\\Registry\\Machine\\System\\CurrentControlSet\\Services\\BEDaisy") retval=c0000002 ... 0035:Ret ntoskrnl.exe.IoCreateDriver() retval=c0000002 ret=7effb832 0035:err:winedevice:async_create_driver failed to create driver L"BEDaisy": c0000002 --- snip --- NOTE: I didn't mention "crashes" or "fails in entry point" in this ticket summary on purpose. The failure from the log snippet is actually a different problem. $ sha1sum Tibia_Setup.exe 50951008ccc402cc32407bfc56a88da873e3e9bd Tibia_Setup.exe $ du -sh Tibia_Setup.exe 5.2M Tibia_Setup.exe $ wine --version wine-3.5-107-gf4573adb0f Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

2 4

[Bug 5149] Ebase 1.03 (FileMaker Pro 5 runtime): 'Find' button does nothing
by WineHQ Bugzilla March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=5149 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|ebase 1.03 buttons "do |Ebase 1.03 (FileMaker Pro 5 |nothing" (FileMaker Pro) |runtime): 'Find' button | |does nothing URL|http://www.mediafire.com/?b | |a32udh1dr2 | --- Comment #16 from Anastasius Focht <focht(a)gmx.net> --- Hello folks, removing broken (fileshare) download link. There are multiple Internet Archive snapshots from the app author's website "Clif Graves Consulting": https://web.archive.org/web/20070223161029/http://www.clifgraves.com/eBase/… Unfortunately none of the linked app zip archives were ever captured on archive.org Regards -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11990] New: Script and Field Lists in FileMaker Pro are blank
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=11990 Summary: Script and Field Lists in FileMaker Pro are blank Product: Wine Version: 0.9.57. Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: dempsey(a)weirdfish.net Created an attachment (id=11316) --> (http://bugs.winehq.org/attachment.cgi?id=11316) Manage Databases Comparison I've installed FileMaker Advanced 9 fine using the latest Wine but when trying to view both fields and scripts it shows all the lines, but doesn't show the text which should be showing the name. I guess the problem occurs in all three places as they use the same control for : Field Listing in Manage Database Script Listing in Manage Scripts Script Steps in Edit Script http://magicbadger.com/dump/images/wine/FM_Manage_Database.png http://magicbadger.com/dump/images/wine/FM_Manage_Scripts.png http://magicbadger.com/dump/images/wine/FM_Edit_Script.png -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 7

[Bug 2423] FileMaker Pro 4.0 installer freezes when using scroll button
by WineHQ Bugzilla March 18, 2021

March 18, 2021

1 0

[Bug 6375] FileMaker 5.x/6.x doesn't show contents of fields computed from the entries of other fields
by WineHQ Bugzilla March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=6375 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL| |https://archive.org/details | |/FileMaker_Pro_5.5_U01073-0 | |01A_FileMaker_2001 Keywords| |download Summary|Computations in filemaker |FileMaker 5.x/6.x doesn't | |show contents of fields | |computed from the entries | |of other fields CC| |focht(a)gmx.net -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 26600] New: Filemaker Pro2 under Wine
by wine-bugs＠winehq.org March 18, 2021

March 18, 2021

http://bugs.winehq.org/show_bug.cgi?id=26600 Summary: Filemaker Pro2 under Wine Product: Wine Version: unspecified Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs(a)winehq.org ReportedBy: gilles.l.auger(a)gmail.com The program winevdm.exe has encountered a serious problem and must be closed. We are sorry for this situation. This may be caused by an error in the program or a default in Wine. This problem does not occur under Windows. Le programme winevdm.exe a rencontré un problème sérieux et doit être fermé. Nous sommes désolés pour le désagrément subi. Cela peut être causé par une erreur dans le programme ou un défaut dans Wine. Se problème ne se produit pas sous Windows. -- Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email Do not reply to this email, post in Bugzilla using the above URL to reply. ------- You are receiving this mail because: ------- You are watching all bug changes.

2 6

[Bug 1776] FileMaker Pro 2.x/3.x fails to install
by WineHQ Bugzilla March 18, 2021

March 18, 2021

https://bugs.winehq.org/show_bug.cgi?id=1776 Anastasius Focht <focht(a)gmx.net> changed: What |Removed |Added ---------------------------------------------------------------------------- URL|http://appdb.winehq.org/app |https://archive.org/details |view.php?appId=337 |/FileMaker_Pro_U95073-055D_ | |Claris_Corporation_1996 CC| |focht(a)gmx.net Keywords| |download, Installer Summary|Wine and FileMaker Pro |FileMaker Pro 2.x/3.x fails | |to install -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.

1 0