[Bug 5597] New: Kiwi Cattools 3.0.6 crashes on startup

[Wine Bugs]

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

Summary: Kiwi Cattools 3.0.6 crashes on startup
           Product: Wine
           Version: CVS
          Platform: Other
               URL: http://www.kiwisyslog.com/software_downloads.htm#cattool
                    s
        OS/Version: other
            Status: NEW
          Keywords: download
          Severity: normal
          Priority: P2
         Component: wine-misc
        AssignedTo: [e-mail]
        ReportedBy: [e-mail]

Continued from bug 4232.
The current version of Kiwi Cattools installs fine
if you ask it to install as an app rather than a service,
but crashes on startup.

With winecfg set to win98, it opens all sorts of vxd's:
fixme:vxd:VXD_Open Unknown/unsupported VxD L"bcmdmccp.vxd". ...
fixme:vxd:VXD_Open Unknown/unsupported VxD L"smartvsd.vxd". ...
...
then dies with
err:seh:setup_exception stack overflow 56 bytes in thread 0009 eip 7ff8ffb6 esp
7fa90fc8 stack 0x7fa91000-0x7fba0000

With winecfg set to the default of win2k, it still dies with that last line.
+relay,+file shows it's trying to open a file that has the
same name as one of those vxd's, BCMDMCCP, and which is
commonly associated with a winmodem:

0009:Call kernel32.CreateFileA(00638630
"\\.\BCMDMCCP",00000000,00000003,00000000,00000003,00000080,00000000)
ret=00630822
trace:file:CreateFileW L"\\.\BCMDMCCP" QUERY_ACCESS FILE_SHARE_READ
FILE_SHARE_WRITE  creation 3 attributes 0x80
...
warn:file:CreateFileW Unable to create file L"\\.\BCMDMCCP" (status c0000034)
0009:Call ntdll.RtlNtStatusToDosError(c0000034) ret=7fc3284b
0009:Ret  ntdll.RtlNtStatusToDosError() retval=00000002 ret=7fc3284b
trace:file:CreateFileW returning 0xffffffff
0009:Ret  kernel32.CreateFileA() retval=ffffffff ret=00630822
0009:Call kernel32.GetVersion() ret=00634b60
0009:Ret  kernel32.GetVersion() retval=08930005 ret=00634b60
err:seh:setup_exception nested exception on signal stack in thread 0009 eip
7ffb559e esp 7fe45c60 stack 0x7fa91000-0x7fba0000

So it seems like the app is tripping over its own shoelaces somehow.
Maybe tracing the syscalls in winxp would show us what the
app is expecting...