Thanks for the response.
-
Never, ever it is allowed to user to write/execute to/from Q: Always, it can execute from C: (writing to it is disposable anyway).
-
When I want to write and execute, it hast to be on/from external storage and in template based AppVM. I’m not hiding, and sys-firewall is default VM. I don’t execute from C: This is when I use win app which has no alternative in a Linux world and why I waited for 4.1 for four years. When jevank fixes at-the-moment-a-must-attaching via --persist (if this is about him at all), this appVM will basically look useless to the one who starts it and doesn’t know that it has to attach external storage cause everything happens there. As of now, qvm-block detach after each use…
-
When I don’t want to write, I use dvm, and execute only from C: I’m hiding there behind sys-whonix. But I indeed have no special need for Windows dvm. If I need dvm, it’s the Linux one. But I’d like to set proper unggogled-chromium as I have under Windows, and so far still couldn’t customize it satisfactory under Whonix. I’ll try with other distros, it’s on my to-do list. I’ll be happy to get a recommendation.
-
When jevank fixes choppy sound for win qubes, one app goes offline as multimedia. And that would be all from Windows.
Basically no browsing except always contacting several same specific sites for the win app stated under 1. Everything else - Linux.