Comments by "Jovet" (@jovetj) on "Why Doesn’t Microsoft Dump the Registry?" video.

  1.  @The_Penguin_City  The exact meaning of "{042D8A51-5878-4000-9C10-C04AFF122A1F}" is a 128-bit number. The point isn't what the value of that number actually is, but that number represents something unique subset of the system.
    2
  2. If I remember correctly, Creative made "total uninstallers" available on their website for just such situations. Lame that it wouldn't come with the software for the hardware, but it still was available.
    2
  3.  @The_Penguin_City  “that number represents something unique subset of the system.”
    1
  4. I believe that you don't actually understand The Registry. It's a mythical thing to most people, it seems. Like a Unicorn that most people have never actually experienced.
    1
  5. Asinine.
    1
  6.  @loupasternak  You haven't had a problem because most "Registry problems" are minor at best, and as stated in the video, it's not the Registry itself that is the problem. It's "garbage in, garbage out" that is the problem.
    1
  7.  @loupasternak  You're preaching to the choir.
    1
  8. Like what?
    1
  9. THE Registry.
    1
  10. It is documented. Not all of it is well documented, but some of Windows's internal data Registry structures don't matter to user programs.
    1
  11.  @JanPBtest  The power supply in your computer is a terrible idea: it's a single point of failure!
    1
  12.  @JanPBtest  You say different, I say not. There are many different possible designs of power supplies. I've seen them fail many more times than "the Registry"
    1
  13. You have no idea what you're talking about. "Registry problems" discussed in this video have little to do with applications remembering their settings. They have to do with applications extending or changing windows or its shell (Explorer) and those extensions being improperly setup (in the registry) or ending-up missing entirely. It doesn't matter how nice or expensive your car is: if you don't know how to drive it properly, you will wreck it.
    1
  14. How about this? Your car is only as good as your mechanic.
    1
  15. Good video!
    1
  16. Cannot into... ? Your "4 kB" statement is also wrong.
    1
  17.  @deniskhafizov6827  That number is approximate, but that's a lot closer than the 4 KB you stated earlier. (It can vary by file, based on how many other NTFS file attributes the file also has stored.) If the Master File Table (MFT) is corrupted, your entire drive is toast anyways, so worrying about tiny files is the least of your problems. But it's actually a very efficient manner of storing such data. It SAVES disk data clusters that can be used for other files. It also saves unnecessary writes, which means less wear on the drive (not more). Now, I've been using NT-based operating systems for over 25 years, and I've never had a corrupted NTFS MFT. Your "problem" is a non-problem.
    1
  18. It kinda already does that, at least between 32-bit and 64-bit applications on 64-bit Windows.
    1
  19. None of that is a problem if you have any semblance of what you're doing.
    1
  20.  @xpusostomos  You mean like incremental partition backups? Those are pretty common.
    1
  21.  @xpusostomos  That depends upon your backup solution. Not too difficult if your backup solution provides for selective restore. Why are you making a mountain out of a mole hill? You seem to be trying to complain about a problem that isn't.
    1
  22. Bingo!
    1
  23. He means that any security policy would have to apply to an entire .ini file. You can't have one section of an .ini file be read-only to a normal user, and the rest be read-write. You would need two separate files for that.
    1
  24.  @skilletpan5674  You can back it up yourself. Regedit, Export everything. Saved to a text file. You can pull things out of it later if you need to.
    1