[Bug 57783] New: Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

Bug ID: 57783
           Summary: Approach will not run in a virgin 10.0 wineprefix
           Product: Wine
           Version: 10.0
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: -unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ---

Created attachment 77980
  --> https://bugs.winehq.org/attachment.cgi?id=77980
debugg message on crash

What a disaster!  Please correct. I need my accounting system back.

SmartSuite-N99.8.0208.0800
Fedora 41
wine-stable-10.0.0-1.1.x86_64
winehq-stable-10.0.0-1.1.x86_64

Lotus Approach will not run in a fresh WINEPREFIX under WineHQ Stable 10.0,
unless you have leftover stuff from a prior wine install.  But that would not
be a fresh WINEPREFIX.

Both Approach and WordPro were selected on a customer install and a fulkl
install too after wiping the .wine directory and starting fresh

The following error occurs at the end of installation from the smart suite ISO.
    regedit: Unable to open the registry key
'HKEY_CURRENT_USER\Software\Lotus\SmartSuite'.
and
    regedit: Unable to open the registry key
'HKEY_CURRENT_USER\Software\Lotus\ScreenCam'.

Only Approach and WordPro were selected on a customer install.

When starting Approach:
      $ cd /home/todd/.wine/drive_c/lotus/approach
      $ wine ./approach.exe

The following pop occurs
      "Lotus Approach: Couldn't load Lotus Dialog DynaLink"

Pressing okay, opens a Program Error box and presents this error in the command
line:
     wine: Unhandled exception 0xe06d7363 in thread 24 at address 7B5F7448
(thread 0024), starting debugger...

I will attach the full debug message message.

I have one for one checked a qemu-kvm Windows 10 install of Approach against my
wine registry and they are identical

Many thanks
-T

[Bug 57783] Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

--- Comment #1 from Rafał Mużyło  ---
...attach whole output, not just the backtrace,

[Bug 57783] Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

--- Comment #2 from Todd Chester  ---
(In reply to Rafał Mużyło from comment #1)
> ...attach whole output, not just the backtrace,

What do you mean?

[Bug 57783] Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

--- Comment #3 from Todd Chester  ---
Is this what you want?  It is 84 meg tar gz'ed up.  Limit 10 meg on the
attachments

WINEDEBUG=+all wine approach.exe > /home/temp/Wine.IconBar/full.trace.txt 2>&1

[Bug 57783] Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

--- Comment #4 from Todd Chester  ---
How about this?

WINEDEBUG=+err wine approach.exe > /home/temp/Wine.IconBar/full.trace.txt 2>&1

0080:err:environ:init_peb starting L"C:\windows\syswow64\winedevice.exe" in
experimental wow64 mode
00d4:fixme:wineusb:query_id Unhandled ID query type 0x5.
0024:err:environ:init_peb starting L"C:\lotus\approach\approach.exe" in
experimental wow64 mode
wine: Unhandled exception 0xe06d7363 in thread 24 at address 7B5F7448 (thread
0024), starting debugger...
0140:err:environ:init_peb starting L"C:\windows\syswow64\winedbg.exe" in
experimental wow64 mode

[Bug 57783] Approach will not run in a virgin 10.0 wineprefix

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57783

--- Comment #5 from Todd Chester  ---
This is not an issue in wine-devel-10.1-1.1.x86_64