Tag Archives: Solutions

Windows live writer’s "Invalid response document" error

In my previous post, I outlined my unsuccessful attempt to use windows live writer (WLW) to connect to the XmlRpc server of PhpWebsite‘s article manager module. I experimented using both the Metaweblog API and the Movable Type API but with no success. When attempting to post an entry, WLW always returned the following error message “The response to the metaWeblog.newPost method received from the weblog server was invalid: Invalid response document returned from XmlRpc server.” However, the entry did get posted. Republishing the same entry would create a new post instead of replacing the one posted earlier. And each time, WLW gave the same error. 

I searched the Internet for possible solutions. I found out that the problem is quite common and not unique to PhpWebsite (PWS).  The same problem has also been observed in other blogging platforms such as wordpress. Luckily for wordpress users, there are already solutions posted in several blogs for some of the problems with WLW. Unfortunately for me, the solutions were not applicable for PWS. I could not even find other sites or blogs talking about PWS and WLW except this one. It seems I am the only soul trying to do this in the entire world wide web.

Since most of the websites I’m maintaining are powered by PWS, I thought it is worth the time and effort to figure out the cause of the problem. I am also in need of a good editing application that I can use with PWS. The provided text editor is only good for basic editing and not for more advanced formatting. For instance, using tables in entries can really take a lot of time. Anyway, since I am using WLW in my other blogs, I thought it would be great if I could also use it in my PWS-based websites.

Finding IP and MAC addresses on Windows XP

According to Wikipedia, an IP (Internet Protocol) address is a unique address that certain electronic devices, such as computers, use in order to identify and communicate with each other on a network utilizing the Internet Protocol standard. In simple terms, it is the address of a computer in the network, which you need in order to reach that computer. On the other hand, a MAC (Media Access Control) address is a unique identifier attached to most network adapters. It is like a name for a particular network adapter.

To get these information in Windows XP, you will need to open a Command Prompt. To do this, click the Start button on the Windows taskbar, then choose All Programs. Choose the Accessory folder, then click Command Prompt. Alternatively, you can also click the Start button, then choose Run. Type cmd in the text box that appears. In either approach, a Command Prompt window will be launched on the desktop. In this command window, type

ipconfig /all

This will display the Windows IP configuration. Locate the appropriate Ethernet adapter. The entry for the IP address is your IP address. This is usually a series of numbers separated by dots (eg., The entry for the Physical Address is your MAC address. This is usually a series of hexadecimal numbers separated by dashes (e.g., 00-04-00-AB-23-CC).

In summary, to know your current IP configuration, launch the Command Prompt window (Start > All Programs > Accessory > Command Prompt), then type ipconfig /all.

Problem running GTK applications remotely

This entry was originally posted in my old 360.yahoo.com blog.

I encountered this problem while testing a gtk application I developed. The application was installed in a remote machine, which could be accessed via ssh. Every time I ran the program, I got this error message "… BadWindow (invalid Window parameter) …".

I initially thought that the problem was related to the X window system. After searching the Internet, I found out that the problem is an ssh issue, or more precisely, X11 and TCP forwarding in ssh. There are two possible solutions to resolve this problem:

  1. using the -Y option in ssh. The -Y option enables trusted X11 forwarding. Note that the -X option also doesn’t work. You can run ssh as follows:
    [user] $ ssh -Y hostname
  2. put "ForwardX11Trusted=yes" option in the ssh configuration file. The personal configuration for ssh can be placed in .ssh/config in your home directory ($HOME/.ssh/config)

With this, the problem was solved!