jaclaz

Talking of updates/upgrades, in Redmond : http://blog.win-fu.com/2016/11/every-windows-10-in-place-upgrade-is.html meanwhile in Cupertino : https://onemoreadmin.wordpress.com/2016/11/27/the-untouchables-apples-new-os-activation-for-touch-bar-macbook-pros/ jaclaz

Subinacl OS support may depend on version , I believe "last" version is however very "old". Have you tried Regini.exe? (if available in Windows 10) BUT - hard as it may be to suggest this - most probably you should use Powershell (examples): http://superuser.com/questions/914377/setting-registry-permissions-with-powershell https://gallery.technet.microsoft.com/scriptcenter/How-to-Manage-Permissions-e5b32b49 jaclaz

Right before the AARD code thing came out, JFYI: https://en.wikipedia.org/wiki/AARD_code jaclaz

Well, to be fair, 99% of first reply when asking about *any* problem with *any* OS in a lot of places is "re-format and re-install OS", the fact that it is popular (and often effective ) doesn't really mean that it is a good idea or that is an appropriate answer to the specific problem at hand. jaclaz

Let's say that IF I were a Windows 10 user I would keep under close watch the new "protocols" such as “ms-windows-store“ or "microsoft-edge": https://www.brokenbrowser.com/abusing-of-protocols/ jaclaz

JFYI : jaclaz

If you never used command line tools, you can remove them. Remember, tomorrow morning, to remove the spare wheel, jack and tools from your car, you also never used them. Truecrypt is no more (since 2014). http://truecrypt.sourceforge.net/ It has been "replaced" by VeraCrypt (JFYI): https://veracrypt.codeplex.com/ Help subsystem can be replaced (with some little caveats) with xchm: http://xchm.sourceforge.net/ https://sourceforge.net/projects/xchm/files/xCHM for Win32/ jaclaz

In other words, by making your add-ons for Photoshop, you are an accomplice, facilitating and supporting this flawed market model and somehow justifying it. A Court would probably give you a lighter sentence because of your state of need, still ... jaclaz

Only to add some FUD , a nice POC (if you think that NOT having a microphone would do): https://techcrunch.com/2016/11/23/security-researchers-can-turn-headphones-into-microphones/ jaclaz

https://tools.ietf.org/html/rfc3330 All in all I find it normal that pinging any address on 127.x.x.x loops back (the /8 is "class A" and corresponds to 255.0.0.0 netmask). The source of your 127.0.0.84 port use is something that needs to be investigated, but should be unrelated. jaclaz

Sure, and still that has no relevance whatever when talking of formatting or partitioning (or both), the concepts don't change with size. jaclaz

Introduction/presentation (if needed): https://m.signalvnoise.com/microsoft-reboots-war-on-sleep-a90da0396fb5 Actual Microsoft (Surface) commercial video: https://www.youtube.com/watch?v=Yjs2uiKPo2c Quote of the day: No comment actually needed. jaclaz

Which is good , it means you are "modern", once upon a time people used to get to know things before making opinions on them, even wrong ones. Here are some possibly interesting resources to back up your thesis: http://reboot.pro/topic/21074-windows-10-is-now-shipping-with-linux-command-line/?p=198581 Anyway the issue is only about the actual attempt to "convert" existing usersbase to migration from cmd.exe. The ps.exe as an option? Good, lots of people actually deserve that. The ps.exe forced down everyone's throats? Advanced users will be able to revert that in no time, the less advanced users will be stuck in there and have all kinds of issues attempting to (wrongly) run cmd.exe commands in the new shell, a perfect way to have BOTH dislike the new shell. Yep, and these senseless (partial/wrong) aliases already made their victims, JFYI: https://github.com/PowerShell/PowerShell/pull/1901 jaclaz

It's not about caveats, the given article doesn't say anything different from what you just reported. Whether you call it "votes" or not the essence is the same, if the "integrity" of a file is checked, *something* must be there to compromise it in case of hardware change, and whether the new (not fully known) set of triggers is "morally correct" or "to be expected" (or not), or whether the used method is "forgiving" and "fairly easy to reactivate" doesn't really answer the OP question. Both slmgr.vbs -dlv and MGADiag do not AFAIK actually give any useful information on what is the situation, more or less we have a "black box" that *sometimes* will issue a request for reactivation, and most probably each of the zillion versions and licence types have different "black boxes". jaclaz

The output you posted seems to come from Powershell allright (note the "length" instead of "Size"), the dir is a "standard" Alias, as well as ls, list and gci, of Get Child-Item, you can check the Aliases via Powershell, it is simple and easy to remember : get-alias | where-object {$_.Definition -eq 'Get-Childitem'} jaclaz

There must be a communication problem of some kind. If you use the HP USB format tool, it will make a PARTITIONED USB stick (unlike the "normal" Windows XP, where you CANNOT partition a "removable" device), so if you used that tool, you did partition the USB stick (evidently without knowing that you did so). cfadisk.sys is a THIRD PARTY filter driver and it doesn't exist in XP, or in Server 2003. What (the heck) is an "expandable" HDD? Does it expand (and possibly shrink)? Anyway what is the relevance of it being 80 Gb (and old) ? jaclaz

Replace WHAT? With WHICH version? It seems like you are not very familiar with the concepts of partitioning and formatting (USB) devices and with the ideas behind the mentioned filter drivers. jaclaz

Yep , but I was asking if this happened on a non-partitioned device (a "Normal" USB stick which normally comes from factory as "removable") i.e. a device which first sector is the PBR or it it happened with USB hard disks (that are always a "fixed" device) i.e. a device that has one or more partition created and that has the MBR as first sector and the PBR at a given offset (typically 63 sectors) or if it happened with a "removable" but partitioned device. The reference by Dybia to the HP USB Format utility is "queer" as that tool does not do the same things as the built-in Windows XP tools. By default in Windows XP: 1) if the device is "removable", the USB device is given "directly" a drive letter and is formatted (by format.com) as "superfloppy". 2) if the device is "fixed", the USB device needs to be partitioned (by diskpart or disk manager) then format.com is used on the partition(s) The HP USB format tool creates (often with wrong, unbalanced CHS/LBA data) a partition on the ("removable") device, then formats it, the result is DIFFERENT from what you can do with built-in tools. If you prefer, maybe using a filter driver like cfadisk.sys or dummydisk.sys or diskmod.sys would change something (or maybe it won't) . Anyway, I failed to understand that once USBPORT.SYS from Windows 2003 is used the problem is solved . jaclaz

I would be curious to know something more about this "formatting" problem. What it is related to exactly? 1) formatting a volume on a USB partitioned device 2) formatting a USB "removable" device 3) partitioning a USB device What is the error/problem? Using disk manager or diskpart or format.com? Does it affect all USB ports or just USB3 ones? jaclaz

So, the given article is just rubbish? http://searchitchannel.techtarget.com/feature/How-Windows-7-hardware-upgrades-affect-licensing jaclaz

The XP "votes" mechanism was detailed here (just for the record): http://aumha.org/win5/a/wpa.htm and the XPINFO (and related papers) are here: http://www.licenturion.com/xp/ The Windows 7 mechanism (not as detailed as in the above): http://searchitchannel.techtarget.com/feature/How-Windows-7-hardware-upgrades-affect-licensing I don't know if anyone already tried doing something like xpinfo for 7. jaclaz

And now, if you think that Windows 10 is bad, meet Finch which is what the good Google guys can use to change your chrome (or Chromium) remotely (separate from the "normal" upgrade/update engine): https://sslmate.com/blog/post/ct_redaction_in_chrome_53 in a nutshell: https://news.ycombinator.com/item?id=12953172 jaclaz

The decimal separator is a convention, but, unfortunately for you (US and for some other English speaking countries), the international ISO standards use the comma. though *like* 99.99% of the people (please note the comma as decimal mark) simply ignore that, it is a requirement for international standards: http://www.iso.org/sites/directives/2016/part2/index.xhtml#_idTextAnchor098 As Oracle puts it: https://docs.oracle.com/cd/E19455-01/806-0169/overview-9/index.html But in practice scientists tend to be smart enough to understand which is which : https://web.archive.org/web/20130228062258/http://www.councilscienceeditors.org/files/scienceeditor/v31n2p042-043.pdf jaclaz

What about the remaining 90,000%? jaclaz

I think in my simplicity that a good idea would be to set a couple of conventions: 1) NOT promise any date <- for the developer 2) NOT ask for delivery <- for the final user When (and if) it will be released it will be released, no need to promise, no need to ask or press for release, no need to provide justifications for non-matched dates. jaclaz