Got 3.2.1 running on Windows 7 Enterprise x86 last night. As soon as the Blade connected to BFG, BFG just quit/disappeared. Upon reopening BFG everything worked perfectly. Connected the second Blade, and again BFG quits. I've rebooted etc several times, and BFG is happy now.
To me, it seems BFG quits on the very first instance on a Blade connecting to the HTTP port (perhaps something craps out creating the virtual device?).
3.2.1 works OK on Linux, on the same machine (Intel NUC DCCP847DYE) with 4GB RAM and 30GB Kingston SSD).
Scratch that. First time the Blade connects at each reboot, BFG quits. It runs perfectly every time until the next reboot.
Blades aren't being restarted, just using the Switch Server function (the backup server are to a stratum_proxy running on my WHS.
I'll likely need the crash report (printed to standard error, or log file if one is configured) to do anything.
BFGminer is not really a Windows program, it is a DOS program.
No, BFGMiner is a fully native Win32 and Win64 application.
I don't think it's even possible to build it for DOS.