tain

As a matter of fact the point is exactly that (with all due exceptions ) most people here are not "fans" of one Os or the other, they are (largely) "simple" users of it, more or less desperately trying to have the stupid thingy work as it should, in some cases (please read as "often") notwithstanding the efforts of the good MS guys to make Windows (you choose) either Android or an X-Box. Microsoft is in the name and has certainly been our historical strength...but I've always thought of our community as one of general hackers (tinkerers). We want to make our OS do things we like even if the developer didn't intend for that. There's certainly a place for us Linux types here

Thanks!

Welcome!

Oh wow, it is Kiki! Your attachment didn't attach...

Looks pretty handy!

Did the software detect the drives? Often this sort of software needs to wait for Windows to properly ID the drives and load appropriate drivers first. Don't break any enclosures open yet. Disconnect both drives and reboot. Just plug in one drive and wait for Windows to get it all ready for you. Once you can access the drive via Windows, then try your software. I've seen some instances where different types of USB ports are finicky for this sort of operation so you can try this procedure with different ports.

What is your theory?

Welcome! I think I like it better that way

Why do modern TVs with internal QAM tuners properly display channel data (ie, "4-1 WCBS" versus "74-76473 RANDOM LETTERS") while external stand-alone QAM tuners only display the other "74-76473 RANDOM LETTERS" data? TVs seem to have some additional feature. I've seen this phenomenon several times in different settings. The general environment is an unencrypted QAM signal for local TV broadcasts via FIOS TV or other provider.

Hi! We generally speak English so I'm unsure how many people can understand you.

Most of the discussion about Telemetry leading up to Win 10 is in other subforums so here is a post with some links for the Win 7 crowd. A single script that worked well for me. It uninstalls the KBs, hides them, disables tasks and kills services. It is not my script: https://github.com/WindowsLies/BlockWindows/blob/master/BlockWindows.bat A set of scripts, some of which I used successfully but are not mine: https://github.com/WindowsLies/BlockWindows Guide from the Win 10 subforum: http://www.msfn.org/board/topic/172856-guideway-to-disable-keylogger-telemetry-v21/ Relevant from the Win 8 subforum: http://www.msfn.org/board/topic/173752-how-to-avoid-being-upgraded-to-win-10-against-your-will We do currently have a sticky that points to the Win 8 thread: http://www.msfn.org/board/topic/173753-how-to-avoid-being-upgraded-to-win-10-against-your-will/

Oh and I just saw that our old buddy Claus has been compiling some relevant resources: http://grandstreamdreams.blogspot.com/2015/09/windows-telemetry-and-tracking-linkpost.html

Here is a relevant set of scripts on github. Haven't tried them, can't vouch for them. https://github.com/WindowsLies/BlockWindows Found via slashdot http://tech.slashdot.org/story/15/09/01/1951235/microsofts-telemetry-additions-to-windows-7-and-8-raise-privacy-concerns The semi-manual method that alacran cross-linked is more straightforward.

@alacran: Thanks for the cross-post