[[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.
Windows machines are smaller than enterprise Unix machines, but Windows applications are often “bulkier”.
Surprise! [[art of unix programming]] P71 gave some reasons.
Confession — I’m a laggard on adopting new applications. Ascii text files are my default choice.
- I use spreadsheets when I must.
- I use MSWord only for equations.
- I use Outlook tasks/drafts to capture screenshots for record keeping.
- 😦 OneNote is too bulky to back up
- 😦 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.
I hit this stubborn blocker twice. Outlook would refuse to receive or send mails.
I believe each time I had to reinstall Office 2010 to get rid of it. The online suggestions didn’t work.
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.
Control panel -> Local sec policy -> grant AllowLogonThroughTerminalService to that user
MyComputer -> Property -> Remote -> add to RemoteUsers
The Desktop.ini file is a standard text file used to customize the appearance and behavior of the enclosing folder.
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.:
Nevertheless, it is possible to redirect:
\Documents and Settings
\Program Files (x86)