https://bugs.winehq.org/show_bug.cgi?id=52131
--- Comment #24 from Eric eric.wheez@gmail.com --- I found out that the culprit is indeed the dvoa.dll library erroring and then wine-mono not knowing how to handle the error. It seems that dotNET has a way of skirting around the condition where no data comes back from the library, but wine-mono doesn't yet.
I downloaded all the files in the https://github.com/VE3NEA/DVOACAP/tree/master/DVoaDllTestCmd directory and ran the exe from DOS. An output.txt file with a table in it was created containing tables that look like this: ---snip--- 35.80 N 5.90 W - 44.90 N 20.50 E
1.0 16.2 6.1 7.2 9.7 11.9 13.7 15.4 17.7 21.6 25.9 0.0 0.0 FREQ 1F2 1F2 1F2 1F2 1F2 1F2 1F2 1F2 1F2 1F2 - - MODE 13.7 7.8 7.8 8.1 8.7 9.5 10.9 14.7 14.7 14.7 - - TANGLE 8.9 8.5 8.5 8.6 8.6 8.6 8.7 9.0 9.0 9.0 - - DELAY 440 295 296 304 317 337 371 466 466 466 - - V HITE ....keeps going ---snip---
I then changed `"Freqs":` in the `input.json` file to `[0.01]` and ran the exe from DOS again. No output.txt was created this time, but this error message appeared:
---snip--- C:\Users\AnthonyBistodeau\Desktop\Edu\dvoa>DVoaDllTestCmd.exe Exception500: Error computing prediction: Assertion failure (C:\Proj\VCL\AlProp\DVOA\DVoaClass\Reflx.pas, line 355) ---snip---
One solution might be to edit the github file to not have crashes on small frequency calculations. Another solution might be to implement an SEH exception for this kind of situation into wine-mono. A third solution might be to ask the RMS Express authors if they can make a workaround for cases when no output.txt is created from dvoa.dll.