One faulty driver no longer hides every radio on the machine. FoxSDR looks for radios in a separate process, so a driver that crashes while it is looking cannot take the application down with it. Until now, when that probe crashed, FoxSDR tried once more and then gave up — which works when the crash is occasional, but not when a driver on that machine crashes every single time. A user with a radio plugged in was told there were no radios at all.
Now, when the whole scan has died on every attempt, FoxSDR asks each driver separately, one at a time, in its own process. The drivers that work still list their radios; the one that crashes is skipped and named in the log, so you know which driver on your machine to update or remove. Machines where the scan works normally are untouched: none of this runs unless the scan has already failed.
What has been checked. 138 tests pass on Windows and on a clean Linux clone. The new test fakes exactly this machine — a probe that dies every time for the whole bus, two drivers, one of which faults — and requires the working radio to be listed, the faulting driver to be named, and the counts to be right. It fails without the fix.
Not checked: no machine here reproduces the original fault, so the fix is verified against the faked helper and the report's own log, not against the driver that caused it.
The Linux files are still in development. The Android alpha stays at 0.98.1-android.1.
SHA-256 of foxsdr-setup-0.99.7.exe:
74aa6253e879243008b8dcceb8c0c5499d93c02c8de9df823a1feb72c5f62203
SHA-256 of FoxSDR-0.99.7-x86_64.AppImage:
d05728cfaa75a73e95f2ec13e47b2c294e98249f0c10eb05219114591da5ab24
SHA-256 of foxsdr-0.99.7-linux-x64.tar.gz:
b4f3246c7fa00398105926e8f78c34bcb327ed6dd3d8a9a713653f44e2acaf8c