The cause of the problem is libxml2 version 2.7.0 and newer, which for some reason changes the way that some bits of text are stripped. Libxml2 is used by PHP to handle XML parsing.

There are a few ways to fix this, wait for the new version of PHP (it’s fixed in 5.2.9), downgrade your copy of libxml2 to a version before 2.7.0, or hack WordPress so it won’t get libxml2 to parse angle brackets. The third option is the easiest.

This patch will fix your XMLRPC issues. The only thing is you will need to update the code to check for libxml version 2.7.3 as well. This can be done by adding || to the end of the lines ending with 2.7.2 and adding a line underneath, "LIBXML_DOTTED_VERSION == ‘2.7.3′ ". Re-upload the new class-ixr.php and rss.php and you’ll be good to go.

–Ben

An interesting fact about the cliTrackPoint: initially it was integrated into some IBM desktop keyboards, before they realised it would be excellent in a notebook. IBM stopped making desktop keyboards with nipTrackPoints, but they later reappeared when UniComp bought out the keyboard manufacturing part of IBM (well, Lexmark at that time, since IBM spun off its peripherals business to Lexmark). They still make the excellent Model M-style clacky keyboards. I’m considering getting one, because they are really nice to type on. Anyway, their EnduraPro model is an old-school clacky keyboard .. PLUS a TrackPoint. It could very well be the best keyboard ever made. If all goes well I could be getting one for Christmas … but I’m still trying to decide whether to go for the Das Keyboard instead. Meh, i’ll figure it out.   

–Ben

After a bit of research I found a better way to do this: install Windows from the hard disk it’s installing onto. I tried this a few times*, and found that after refining my process, it works really well. Even if you have a CD drive in your new computer, installing from the hard disk will be faster, and since we will be automating the installer, you can leave it to install while you go and do other things.

You Will Need:

1. Your new computer
2. A computer already running Windows
3. A Windows XP/2003 CD (whichever OS you want to install on your new machine)
4. A USB-IDE or USB-SATA adapter, depending on the hard disk in the new computer. For this an external HDD enclosure is fine. Personally I use a USB-IDE+SATA adapter, which works brilliantly.
5. A copy of the latest service pack for your copy of Windows, if it isn’t already slipstreamed into your CD.

Partitioning

Firstly we need to partition the hard disk. Take the hard disk out of the new computer, and connect it to your USB-SATA/IDE adapter. Windows should detect your hard disk.

Right-click My Computer, click Manage, then open the Disk Management snapin. Then select the drive you connected (it should contain all unallocated/free space). We need to create two partitions: a partition that will become the system partition, and a partition which will hold the setup files (which can later be a data partition, or you can delete it).

WARNING!  Partitioning your hard disk using Disk Management means you will LOSE all your DATA. Just so you know.

The first partition we will create will be the system partition. This will be a FAT32 partition (it will be converted to NTFS later). Make sure this is a Primary partition. Most importantly, do not assign it a drive letter. This is so during Windows Setup you don’t end up with a drive letter like F: as your system drive. Make sure this partition is at least about 20GB, or however much you estimate that a install of Windows will be when all of your applications are installed.

Now we need to create a partition for the setup files. Create a Primary NTFS partition, and assign it a drive letter. It doesn’t matter what this drive letter is, you can change it later. Make this partition at least 2GB.

Now right-click the setup partition, and select Mark Partition as Active.

Copying the setup files

The second NTFS partition you created should show up in Windows Explorer after it has finished formatting. Create a new folder on this partition called "install". Now copy the entire contents of your Windows XP/Server 2003 CD to this folder.

Slipstreaming the latest service pack

If your Windows install CD doesn’t contain the latest service pack, you really should slipstream the latest service pack into the install files. This will save you time as you won’t have to install the service pack after you have installed Windows. Obtain the full (network) install packages of either Windows XP SP2 (note: this will be replaced by SP3 in a few days!) or Windows Server 2003 SP2. Now open up a command prompt and run the EXE you just downloaded, with the Integrate parameter like this:

WindowsXP-KB835935-SP2-ENU.exe /integrate:X:\install

(where X is the setup partition)

After a few minutes, your install files will contain the latest service pack.

Unattended Install

We will be automating the install by entering in all of the data. This is mainly to save time, but also because we need to create an unattended install script anyway to tell the installer to convert the first partition to NTFS. In the SUPPORT\TOOLS folder in the Install folder, there is a file called deploy.cab. Extract the contents of this to a folder, and run SetupMgr.exe. This is Windows’ unattended install script generator. You could also use nLite, which is actually a whole lot nicer, but this is sufficient. Make sure you select Fully Automated as the install method, otherwise you will need to click through the install, which defeats the purpose. Enter in all of your details such as your timezone, product key, etc, and save the unattended script as Unattend.txt in the Install folder on the setup partition.

Now open up Unattend.txt in Notepad, and under the [Unattended] heading, add the following line:

FileSystem = ConvertNTFS

This will ensure that the FAT32 partition is converted to NTFS during the text-mode phase of setup.

Copying the setup files

We now need to run the Windows Installer, and tell it to copy the installer boot files to the setup partition. Open up a command prompt to the i386 folder in the Install folder on the setup partition. Now type the following:

winnt32 /unattend:..\unattend.txt /dudisable
/syspart:X /tempdrive:X /makelocalsource /noreboot

(where X is the setup partition. This should be all on one line.)

When you run this command, Windows Setup will run, and create $WIN_NT$.BT and $WIN_NT$.LS folders on the Setup partition. The next time a computer boots from this partition, Windows Setup will run and install Windows automatically.

Interesting Sidenote: What do the switches mean?

/unattend: Tells the Windows Setup program to use the unattended install script in the folder above the i386 folder

/dudisable: Tells the Windows Setup program to not check the internet for updates

/syspart:X Tells the Windows Setup program to copy the setup files to the specified partition instead of the partition that the system is currently running from (usually C). If you don’t include this, then next time you reboot your old computer, it will boot into setup.

/tempdrive:X Tells the Windows Setup program to place temporary files on the setup partition.

/makelocalsource: Tells the Windows Setup program to create a copy of all of the setup files in the $WIN_NT$.LS folder. This is the most crucial step, as this means that setup will not look for files on the CD drive.

/noreboot: Tells Windows Setup to not reboot after it copies the files. Since usually when winnt32 is run, it is performing an install on the computer it is running on, it will reboot to start the text-mode phase of setup.

Installing Windows

Safely remove the new computer’s hard disk and connect it to the new computer. Boot the new computer. Provided that it doesn’t try to boot to the network or a USB device, the system should boot straight into Windows Setup. It will continue without needing any user intervention, unless something goes wrong. It will also be considerably faster than a normal Windows install, as installing from a hard disk is a lot faster than installing from a CD.

In about 20 minutes, you should be faced with a Windows logon screen, or the annoying Windows Out-Of-Box-Experience (Let’s Activate Windows!) screen.

Copying the boot loader

Windows is ready to go, however the setup program will have most likely put the boot files on the second partition. To make everything self-contained, it is better if these are on the system partition.

Open up Windows Explorer to the system partition. Go to Tools -> Folder Options -> View, and select Show hidden files and folders and untick Hide protected operating system files (Recommended).

As well as the Install folder we created, you will notice that there are three files, ntldr, ntdetect.com and boot.ini. Copy these three files to the root of the C:\ drive.

Now right-click My Computer, click Manage, then open the Disk Management snapin. Right-click the C: partition, and select Mark Partition as Active. Close Disk Management, and reboot. Your computer should boot as normal.

Now you can change the drive letter on the second partition, or delete the second partition if you want. You do not need to keep the install files that are on this partition. If you want to extend the C: partition to fill the drive, you could use either Windows’ built-in Diskpart tool, or the excellent GParted+ Linux livecd (though in this case if you have no CD drive, you would probably boot it from a USB drive).

Other nice things to try

You can slipstream the latest service pack and set up the unattended install using nLite. nLite will also give you a lot more options with regards to tweaking the system, and it also allows you to slipstream all of your drivers and software into the install, so you don’t have to install them later. If you do it using nLite, make sure you don’t create an ISO file on the final setup. You don’t need it, unless you want to burn your new nLited install to a CD.

Why not use Ghost/Sysprep/RIS/USB/Floppy?

Ghosting/imaging a SysPrepped copy of Windows requires you to have a somewhat-similar PC already set up with Windows to clone onto the new drive. RIS achieves the same thing as we did here, but you have to have a Windows Server 2003 machine handy. You can install Windows XP from a USB drive, but I didn’t have a USB2.0 device with enough space on it available. You cannot feasibly install Windows from a USB1.1 device, because it is too small. You cannot feasibly install Windows from a floppy disk either.

–Ben

* A few times is more like about 10 times … I reinstalled Server 2003 quite a few times on my machine, trying to figure out why it would bluescreen at random points during and after setup. Then I realised that one of the sticks of RAM I had was bad. *smacks head*.

Note: Before you start this program, make sure you have downloaded Synapse and placed it where FreePascal can find it. Also add the following to the top of your program: uses StrUtils, SysUtils, blcksock;

The Packet

The “Magic Packet” consists of six FF bytes, followed by the MAC (hardware) address of the computer, repeated 16 times. To do this first we loop through the string containing the address, then use StrToInt plus a dollar sign to convert the hexadecimal number to a decimal. Then we pass that to the Chr function, which gives the actual byte. After the address string is generated, we use DupeString to repeat it 16 times.

function BuildWOLPacket(wolAddress : string) : string;
var
	i : integer;
	addressByte, address : string;
begin
	// This function will work with a MAC address formatted like this:
	// "01-23-45-67-89-0A" ie. delimited by a character.
	// So if the address isn't 17 chars long, we will quit.
	if length(wolAddress) <> 17 then exit;
 
	for i := 0 to 5 do
	begin
		addressByte := UpperCase(MidStr(wolAddress, 3*i+1,2));
		address := address + Chr(StrToInt('$' + addressByte));
	end;
 
	// Repeat #255 6 times, then repeat the address 16 times.
	result := DupeString(#255,6) + DupeString(address,16);
end;

This function will return a string which contains a WoL “Magic Packet.”

Sending the packet

To send this packet, we need to use the Synapse socket library. The Synapse library has a component called TUDPBlockSocket which we will use to send the packet to the broadcast address (255.255.255.255) on port 0 (some other ports can be used, eg. 9 and 7, however 0 seems to work).

procedure SendWOLPacket(wolPacket : string);
var
	sock : TUDPBlockSocket;
begin
	// Create the socket
	sock := TUDPBlockSocket.Create();
 
	// Enable broadcast support (this is important)
	sock.EnableBroadcast(True);
 
	sock.Connect('255.255.255.255','0')
 
	// Send the string.
	sock.SendString(wolPacket);
 
	// Close the socket.
	sock.CloseSocket();
end;

Now that you have these two functions, it is easy to wake up a computer:

wolPacket := BuildWOLPacket('00:13:37:BA:DA:55');
SendWOLPacket(wolPacket);

If it doesn’t work…

You might want to try changing the port number from 0 to 9 or 7. There doesn’t seem to be a standard for which port is used for Wake On LAN (it actually doesn’t really matter on a LAN).

Also since this uses the Delphi syntax you will need to compile with the -Sd option if you’re using the FreePascal compiler.

–Ben