[Bug 1945] New: MYOB v11, strange dialog box on load, crashes after short period of time

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=1945

Summary: MYOB v11, strange dialog box on load, crashes after
                    short period of time
           Product: Wine
           Version: 20031212
          Platform: Other
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: wine-binary
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

MYOB version 12 (from www.myob.co.nz) displays dialog box (sic) "FALT is needs
that bit cleared. [OK]" Click [OK], dialog appears 36 times before MYOB starts.
Seems to run okay for about 2-3 minutes before hanging.

Each time initial dialog is clicked, console log shows:

fixme:accel:CreateAcceleratorTableA should check that the accelerator
descriptions are valid, return NULL and SetLastError() if not.

When trying to open it's data file (standard Windows File Open dialog appears)
console log shows:

fixme:commdlg:GetFileName95 Flags 0x00002000 not yet implemented
err:dosfs:DRIVE_ReadSuperblock Couldn't open device '' for drive F: ! (not
available or symlink not valid ?)
err:dosfs:DRIVE_ReadSuperblock Can't read drive volume info ! Either pre-set it
or make sure the device to read it from is accessible !
err:dosfs:DRIVE_GetLabel Invalid or unreadable superblock on  (F:).
fixme:dosfs:DRIVE_GetSerialNumber Serial number reading from file system on
drive F: not supported yet.

During program execution, this message appears numerous (40+) times, whenever
the mouse pointer hovers over a link or button in the MYOB gui:

fixme:font:SetMapperFlags (0x730, 0x00000000): stub - harmless

After a period of time (2-3 minutes) or after opening a few child windows, MYOB
hangs. Console shows:

fixme:msvcrt:_XcptFilter (-1073741819,0x406cf63c)semi-stub
wine: Unhandled exception (thread 001f), starting debugger...
WineDbg starting on pid 1e
Loaded debug information from ELF 'wine' ((nil))
No debug information in 32bit DLL 'C:\myob12\Myob.exe' (0x400000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NTDLL.DLL' (0x40200000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\KERNEL32.DLL' (0x40490000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\ADVAPI32.DLL' (0x40a50000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\GDI32.DLL' (0x408a0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\USER32.DLL' (0x40720000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\IPHLPAPI.DLL' (0x40aa0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WS2_32.DLL' (0x40ac0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\NETAPI32.DLL' (0x40a80000)
No debug information in 32bit DLL 'C:\MYOB12\CTMYOB32.DLL' (0x10000000)
No debug information in 32bit DLL 'C:\MYOB12\MYOBSP32.DLL' (0x406d0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\RPCRT4.DLL' (0x40c40000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\OLE32.DLL' (0x40bc0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHLWAPI.DLL' (0x40c90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMCTL32.DLL' (0x40ce0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\SHELL32.DLL' (0x40b30000)
No debug information in 32bit DLL 'C:\MYOB12\CPDF.DLL' (0x40add000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\LZ32.DLL' (0x40d90000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\MSVCRT.DLL' (0x40dc0000)
No debug information in 32bit DLL 'C:\MYOB12\XERCES.DLL' (0x12000000)
No debug information in 32bit DLL 'C:\MYOB12\MFC42.DLL' (0x73dd0000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\WINSPOOL.DRV' (0x40e80000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\COMDLG32.DLL' (0x40e00000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\X11DRV.DLL' (0x40f60000)
No debug information in 32bit DLL 'C:\WINDOWS\SYSTEM\VERSION.DLL' (0x43290000)
No debug information in 32bit DLL 'C:\MYOB12\CFX2032.DLL' (0x4322d000)
Unhandled exception: page fault on read access to 0x40430000 in 32-bit code
(0x4010574c).
In 32-bit mode.
0x4010574c (NTDLL.DLL.memcpy+0x1c): repe movsl  (%esi),%es:(%edi)
Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>Wine-dbg>syntax
error
Wine-dbg>syntax error
Wine-dbg>syntax error
Wine-dbg>syntax error

The last line repeats for quite some time, sometimes the only way to get out of
it is to kill the terminal session. If Ctrl-C is pressed in the debugger (if it
stops prompting) then this message appears:

err:seh:setup_exception nested exception on signal stack in thread 001f eip
400466c6 esp 40016bac stack 0x405d0000-0x406d0000

But more often than not even if debugger is stopped and control is returned to
the bash prompt the last line starts scrolling all over the screen (no line feed
beterrn messages) and the terminal must then be killed.

Application Details:
MYOB version 12 (New Zealand Customised version) from http://www.myob.co.nz)
Running on Mandrake 9.2 Linux 2.4.22-10mdk
Wine 20031212