http://bugs.winehq.org/show_bug.cgi?id=36492
Anastasius Focht focht@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |focht@gmx.net Component|mountmgr.sys |-unknown Summary|mountmgr:harddisk_ioctl |32-bit Dragon |Unsupported |NaturallySpeaking 12.x | |fails to start in 64-bit | |WINEPREFIX
--- Comment #3 from Anastasius Focht focht@gmx.net --- Hello Susan,
I assume you attempted the installation in clean (new) 64-bit WINEPREFIX. Did you install any native components/changes overrides (winetricks recipes)?
--- snip --- WINEDBG=+all --- snip ---
The environment variable is named 'WINEDEBUG'. 'winedbg' is a debugger (application).
Also passing 'all' is not very useful (omits call site info) so don't do that unless explicitly requested by a developer.
There is no reason to believe that the problem is in 'mountmgr' component. FIXME messages are not bugs in most cases.
Installing in 64-bit WINEPREFIX isn't really useful for pure 32-bit app. You are using the 32-bit edition of DNS (see 'Program Files (x86)' path).
There are still some problems with 64-bit prefixes and installing in one will just harm yourself:
* DNS 12 can't be installed in default 64-bit WINEPREFIX which is reported as 'Windows XP 64-bit'
See: https://nuance.custhelp.com/app/answers/detail/a_id/6925/~/system-requiremen...
'Windows Vista' would be the first version that supports 64-bit. You didn't mention that you've changed the Windows version for the prefix so I wonder how you managed to install that thing if the installer refuses 'Windows XP'?
* broken .NET 4.0 installation (known)
* InstallShield 32-bit stub and 64-bit server doesn't work well (despite some bugs fixed) -> ISBEW64.exe crashes
In the end you're better off with a 32-bit prefix (WINEARCH=win32).
Anyway, please provide the exact steps you've done to install that thing in 64-bit prefix (my tests show it doesn't install in 64-bit WINEPREFIX at all).
Regards