Unable to install KB923275 and KB923272 - Windows Update to Office

Recently, Windows update was having trouble updating my Office 2003 installation. There was one OneNote update that was failing and 4 Office updates (Specifically KB923275 and KB923272). Though I am sure this problem might affect other office updates as well. After a lot of searching and performing tasks that I saw on other websites, of which none worked, I was almost ready to uninstall and reinstall Office (which I did not want to do as it just takes too long!). And then I happened on a website that had the steps that worked for me: Check to see that the OSE (office source engine) service is running. 1. Goto Start->Control Panel->Administrative Tools->Services. 2. Run through the list and find Office Source Engine service. 3. In the column status, if it says "Started", then you are out of luck and this fix will not help you. 4. If there column is blank or has some other text, then double click on the service. 5. Click the button Start. 6. Now try and update your system. (My system was successfully updated at this point) 7. Windows update should be able to update your Office installation. If not look up other websites to see if there are other reasons for this problem. (this page may help : http://forums.techarena.in/showthread.php?t=605338) 8. If all else fails - reinstall Office. The one weird thing about this step is that my other computer does not have OSE service running and I have never had a failed office update. Which is why I believe this might not solve everybody's problem.

Schneier on Security: Choosing Secure Passwords

Schneier on Security: Choosing Secure Passwords: "Choosing Secure Passwords" An interesting essay that will give you insights into how to choose a better password by understanding how some of the password recovery programs work.

InfoQ: How to Design a Good API & Why it Matters

InfoQ: How to Design a Good API & Why it Matters Here is a video on good API design by Joshua Bloch (Joshua Bloch is a Principal Engineer at Google) The crux: 1. Easy to learn 2. Easy to use, even without documentation 3. Hard to misuse 4. Easy to read and maintain code that uses it 5. Sufficiently powerful to satisfy requirements 6. Easy to extend 7. Appropriate to audience

UNDERSTANDING NanoTechnology

UNDERSTANDING NanoTechnology: "This site is dedicated to clearly explaining the concepts behind nanotechnology applications in areas such as energy, medicine, and consumer goods. It attempts to make the concepts of nanotechnology understandable by anyone." An interesting read.

Kristoffer's tidbits : Debugging memory usage in managed code using Windbg

Kristoffer's tidbits : Debugging memory usage in managed code using Windbg Another page about debugging memory in managed code. Some very cool techniques are discussed here.

Rico Mariani's Performance Tidbits : Memory leaks 101: Objects anchored by event generators

Rico Mariani's Performance Tidbits : Memory leaks 101: Objects anchored by event generators Some good information about managed memory leaks occuring due to objects having a root at an event generator.

Parse-O-Matic - Welcome

Parse-O-Matic Here is a really useful tool that allows you to reformat a text file using scripts. There is a free version of the tool, that you can use to take the software for a spin. The easiest method is to open one of the sample files and tweak it to do something you need it to do. Still looking for other tools which might be simpler that P-o-matic. Untill then this will safetly be tucked into my toolbox.

Windows Installer Error Messages

Windows Installer Error Messages on MSDN and some useful information about deciphering the error codes and messages in MSI logs: http://blogs.msdn.com/heaths/archive/2006/01/18/514641.aspx

Windows Installer Error Code Reference

Recently, I was trying to debug an installer problem for one of our customers. The MSI log file came back with a list of error codes, but I could not find out what they meant, until I happened on the following site: Its an invaluable reference : Windows Installer Error Code Reference Also, if you dont know how to enable logging, here is an easy way through the registry: Add the following keys and values [HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer] "Logging"="voicewarmup" "Debug"=dword:00000007

Textron commerative coins

In April of 2006, the company that I work for, Visual Learning Systems, got acquired by Overwatch Systems. Then in November of 2006, we got bought out by Textron Systems, a division of Textron, which is a Fortune 500 company. This coin was given to us as a commeration of this event (which I think is a testament to the great work done by us at this company).