DNSB on CrossOver (Commercial WINE) asks to use microphone

[Scott]

Codeweavers is the primary sponsor for the WINE project, and their product CrossOver is the commercial version of WINE. It's WINE plus many customizations, primarily easier configuration and an easy way to download preconfigured bottles.

The current version of CrossOver, 25.1.1, is based on WINE 10.0. I setup a bottle to run DNSB V2R3, and it had one anomaly - on first run, it popped up a permissions dialog stating that DNSBench would like to access the microphone! I clicked on "Don't Allow" and the benchmark continued. Subsequent runs did not ask for this permission, presumably because CrossOver remembered my answer.

System config: Intel Mac running MacOS Sonoma 14.8.3, CrossOver 25.1.1, DNSB V2R3

To recreate:

1. Install CrossOver
2. Create Bottle Type Windows 10 32-bit
3. Set Run Command to the DNSBench.exe, and Save Command as Launcher
4. Launch DNSBench from CrossOver Home window
5. Let verification of servers finish
6. Click "Run Benchmark"
7. Leave default of 5X and "Continue"
8. Select which types of resolvers to benchmark; as previously noted for WINE, DoT Resolvers button is greyed out. Click "Test ALL Resolvers"
9. Benchmark starts running, and after about a second the Microphone dialog box pops up. Note that the benchmark continues running behind this permissions dialog box.
10. Whether you click "Don't Allow" or "Allow", the benchmark will continue running.
11. Subsequent runs will not ask permission and just run.

Steve, if there's anything you want me to log to investigate, let me know. Else, as it seems harmless, maybe just document in a "How to run under WINE / Crossover" section.

 

[Calvin]

I used an open source version of WineHQ on MacOS on Apple Silicon and it too asked to access the microphone. I don’t recall at which point it asked.

 

[PHolder]

The app makes a "click" (like a photo shutter) sound effect. Perhaps, because it plays sounds, it expands the access request to the entire audio device?

 

[Steve]

Good thought, Paul. That's the only explanation I can imagine. I'm certainly not "asking" for access to any microphone. In order to get access to play that "click.wav" file, I'm linking to the WINMM (Windows Multi-Media) library. So it be the initialization of that library that's raising the alarm about "microphone access".