Unsurprisingly, this has turned many users away from Daemon Tools even if they have now made this option more transparent.
Although it has been clarified now, there was a distinct lack of any information about this at the time in either the Daemon Tools or Mountspace privacy policies which in many people’s eyes was unacceptable. There was also rumor that it was sending IP addresses too, but that was strongly denied. This essentially collects usages statistics on all ISO’s you mount in the software like image hash, image file name, disk label, number of mount occurrences and sends it to to be logged. That’s why there was quite a controversy in 2012 when the well known virtual drive software Daemon Tools decided to include a service called Mountspace starting in version 4.40.1. And rightly so too, with so many privacy issues to watch out for these days, the last thing you want is software you perhaps trusted do it as well. I think I might be willing/able to fix this one day if i can wrap my head around exactly what's causing it.A lot of PC users get very annoyed when a piece of software access’s the internet without their knowledge and does things like phoning home without consent. I was creeping around the msfn forum where people were working on updates for kernelex, its extensions and it's per application settings/definitions the other night. Daemon tools and kernelEX are working together with it set to 'disable extensions by default' instead of the default 'always on' (recommended) setting.
I'll try it the other way around and see how it goes.Įdit** yeah, that error just disappeared and daemon tools 3.47 started working again just fine the moment i uninstalled kernelEXĮdit2** Yup, that was it. I've never installed it this time round, however Daemon tools broke in exactly the same way the moment i installed & updated kernelex (i guess that's installed as part of UnofficialSP3 too?) Anyway, I presume this error's because i choose "Enable KernelEX extensions for all applications" during its installation. I don't believe it's the unofficial service packs fault. For anyone else googling, i just bumped into this issue myself today.
0 kommentar(er)
