I did not create this but I have used it and can confirm it is fully working on XP SP2. It may require .NET Framework 2.0. I am not sure

What’s included:
The Office 2007 package file (contains all the th!nstalled files)
Access 2007
Excel 2007
InfoPath 2007
OneNote 2007
Outlook 2007
PowerPoint 2007
Publisher 2007
Word 2007
Project Professional 2007
Visio Professional 2007
Office Document Imaging
Office Document Scanning
Office Diagnostics
Picture Manager
Clip Organizer
Save as PDF/XPS integrated

This is a complete installation, minus Groove. It is activated. MSOCache has been removed, and there do not appear to be any errors related to this (I have been using this for a while now, and so far so good). It has been fully tested on a clean Windows XP SP2 install in VMWare under Administrator, Limited, and Guest accounts with no problems (make sure your file permissions are set correctly, otherwise you may get errors when opening files). The biggest problem was with Outlook. This was due to the Outlook data file being in a shell folder, such that if the “Program Files” folder was on a different partition Outlook would throw an error and sometimes refuse to open. To work around this, I put the default Outlook data file in a directory named “Outlook” under the C drive of the th!nstall build, with isolation set to “Full”. Thus, the Outlook data file in a fixed location, no matter what environment it’s run in, and it is fully sandboxed.

One more problem I encountered was that most of the Office apps would start services but not end them when exited. This would cause problems if you were running on a USB stick, because it would refuse to eject until those services were terminated (which you sometimes can’t do on a locked-down computer). As a result, I added an executable called “pskill” to the build. This is a command-line utility written by SysInternals that kills processes. I made use of the scripting utility in th!nstall to insert the following script into each executable:
Code:
Function OnFirstParentExit
ExecuteVirtualProcess “c:\utils\pskill -accepteula mdm.exe”
ExecuteVirtualProcess “c:\utils\pskill -accepteula ctfmon.exe”
End Function

This script calls pskill in the virtualized environment and directs it to kill the processes mdm.exe and ctfmon.exe once you exit any of the office apps, thus enabling you to eject your USB key without problems. Please note, when you exit any of the applications, you will very briefly see two command windows appear. This is normal and is merely pskill being called.

I also tested on a clean Vista Ultimate VMWare machine. This testing was not as extensive as what I did under XP, simply because I don’t use Vista. A couple of points:
1. The services called by th!nstalled Office (mdm and ctfmon) don’t seem to work properly in Vista and close with an error, but it doesn’t affect the running application.
2. pskill also closes with an error, but also does not affect the running application. Basically, you have to dismiss a few error windows, but the applications work in Vista
3. I did not notice any missing dll errors in Vista
4. There is a known bug in th!nstall, such that if a File>Open dialog is called by a th!nstalled application the application will crash. This severely limits the usefulness of this version in Vista, but it may be able to be worked around given time and patience.
link check ok

__________________