windows registry: criticized

[[art of unix programming]] points out that Windows registry are sometimes corrupted. ( Remember the standard advice to always back up the registry before editing it? ) When corrupted, the registry “frequently” breaks the entire system and requires a completely reinstall, as the book claims.

  • weakness — the registry is a centralized hierarchical config data store shared in RW mode by all (dozens of) applications.
  • weakness — single point of failure

In contrast, Unix config data is decentralized, but I won’t elaborate.

Centralized hierarchical configuration sounds plausible but isn’t impressive in practice.

Advertisements

MSOffice one-note for note-taking

Confession — I’m a laggard on adopting new applications. Ascii text files are my default choice.

  1. I use spreadsheets when I must.
  2. I use MSWord only for equations.
  3. I use Outlook tasks/drafts to capture screenshots for record keeping.
  4. 😦 OneNote is too bulky to back up
  5. 😦 OneNote is hard to share with computers without MSOffice

I think OneNote is suitable for office use —

🙂 save screenshots, but I can do the same in outlook
🙂 add notes anywhere on the doc, to make more visual presentation/documentations. However, for personal note taking I won’t need this feature.

ms-outlook personal-folders — 2 instances running

There’s no workaround — having 2 instances (ie on 2 machines) of outlook running will inevitably mess up your personal folders.

Symptoms? all email-rules using personal folders will lose the folder names.

What can users do? Not much. If you must run 2 instances, then try to disable the rules that use personal folders.

Location of the personal folders doesn’t matter, even if located on a shared drive.

pitfalls with NTFS junction point

http://www.techrepublic.com/article/manually-creating-junction-points-in-windows-xp/5388706 and
http://en.wikipedia.org/wiki/NTFS_junction_point warn —

^^Junction point target must be a local file system directory. Target can’t be a file.
^^Most delete operations are junction-unfriendly. Can damage the target i.e. the real files !
^^DOS command dir can report odd free-space statistics on drives that contain folders acting as junction points.
^^Junction points can cause havoc with certain backup programs, that aren’t junction-point aware.
^^if a target folder C:\a\b\T contains some kind of link (symlink? hard link? shortcut?) then I find it troublesome to move the folder content somewhere and replace C:\a\b\T with a junction point

^^Junction points do not work at boot, so it’s impossible to “redirect” i.e. substitute a hardlink for e.g.:
\Windows
\Windows\System32
\Windows\Config

Nevertheless, it is possible to redirect:
\Users
\Documents and Settings
\Program Files
\Program Files (x86)