See the Technet article on installing Windows SP3. Note that they recommend having WinXP SP2 installed before installing SP3.

From the TechNet Forum:

“Today we are happy to announce that Windows XP Service Pack 3 (SP3) has released to manufacturing (RTM). Windows XP SP3 bits are now working their way through our manufacturing channels to be available to OEM and Enterprise customers.

We are also in the final stages of preparing for release to the web (i.e. you!) on April 29th, via Windows Update and the Microsoft Download Center. Online documentation for Windows XP SP3, such as Microsoft Knowledge Base articles and the Microsoft TechNet Windows XP TechCenter, will be updated then. For customers who use Windows XP at home, Windows XP SP3 Automatic Update distribution for users at home will begin in early summer.

Thanks to everyone here who installed the public betas – you not only gave us detailed feedback but also helped each other out with timely troubleshooting. Through the beta program we found several important issues and were able to confirm some essential fixes. We couldn’t have done this without you.

We will still be monitoring this forum during the next few weeks in case you have more feedback about the release of Windows XP SP3.

On behalf of myself, Shashank Bansal and Windows Serviceability, many thanks.

Chris Keroack
Release Manager, Windows XP Service Pack 3
Windows Serviceability”

Techmixer has links to WinXP SP3 for different languages, German, Japanese, French, Russian and Chinese.

Having had the pleasure of meeting Hiroko, and two of the other competitors, Kana Anan and Yoshimi Sato, at the Emerald Ball in March, I can honestly say that the photos do not do them justice. The girls are much more beautiful in real life, and after putting up with 20 drunken Irish young lads at the Westin Hotel, they are great sports too.

More photos after the link

I wish her the best of luck in the competition in July. I for one will be cheering for her.

But when I rebooted my PC today it displayed the following error:

INF file txtsetup.sif is corrupt or missing, status 14.
Setup cannot continue. Press any key to exit.

I rebooted a couple of times and tried to hit F8 to get to a boot menu, but no luck. Normally if you time it right, hitting F8 before Windows XP starts loading will let you select Last Known Good Configuration or Safe Mode.

I booted from an XP installation CD and tried to get to the Microsoft Windows Recovery Console, but it simply said that it could not detect any hard disks and the only option was to press F3 to restart. That recovery console really sucks.

Next I tried the trusty Ubuntu live CD. For some reason it wouldnt boot into the normal Ubuntu, the graphics would go haywire, so I booted into the safe graphics mode. With Ubuntu I was able to see the Windows XP partitions and verified that all the files were there.
I did notice that the aborted XP installation had managed to add a line in BOOT.INI on the primary partition so I realise the boot files had been overwritten. With Ubuntu its easy to edit it, but rebooting into XP still gave the same “txtsetup.sif is corrupt or missing” error.

Next I tried a Windows 98 boot CD, but it couldnt see the NTFS partition with the XP installation.
I was about to try an fdisk /mbr but decided to try one more option with Ubuntu.

Heres what worked…

If you dont already have a Ubuntu live CD, download and burn one.
Download an Ubuntu ISO.
Use a CD ROM burning application like CDBurnerXP to burn the ISO to a DVD.

On a working Windows XP PC, copy BOOT.INI, ntldr and NTDETECT.COM from the C: drive to a USB stick.
If you dont see these files in your C: drive then start Windows Explorer. In the Tools menu, click Folder Options. Click the View tabb. Click to select “Show hidden files and folders” is selected, and remove the check from “Hide protected operating system files”.
Now copy the three files to an easily recognisable folder on your USB stick, if your stick is drive H:, copy the files into H:\Recover

Boot Ubuntu on the crashed PC. Boot into safe graphics mode.
Insert the USB stick. Ubuntu should recognize it.
Now copy those three files from the USB stick to your disk.
Reboot and hopefully your Windows XP is running again.
You may get warnings that some files are the wrong version.

I still have a feeling that booting from a Win98 CD and running fdisk /mbr from a DOS prompt work also have worked, but I’m not going to try it until the next time I get the same error.

If your PC has a floppy drive, you could make a boot floppy.
Insert a blank floppy disk into drive A:
Select Start > All Programs > Accessories > Command Prompt (or just press Windows Key+R and type CMD<code>).
Type <code>format a: and press Enter.
xcopy c:\boot.ini a: /h
xcopy c:\ntdetect.com a: /h
xcopy c:\ntldr a: /h
exit
The window will close when you type exit. Now remove the floppy disk and label it “Windows XP Boot Floppy”
Put this in your corrupted PC and boot up.
If you are luck, Windows should start.
Now open a Command Prompt and enter the following commands to overwrite your corrupted boot files with the files from the floppy.
xcopy a:\*.* c:\ /h

If you were able to get to a Recovery Console from your Windows XP CD, you ould try the following commands. Try one, reboot without the CD to see if it worked, then try the next.
fixmbr
fixboot
The diskpart command runs a tool that lets you play with your partitions. Recommended only for those who know what they are doing.

I decided to give it a go. Installing it and getting a simple application running on the emulator was a breeze. The installation instructions on the Android site were relatively straightforward, and the videos helped getting the application to work.

1. Install the Android SDK
   1. Download the Android SDK and unpack it to a suitable installation folder (eg. C:\Program Files\Android SDK)
   2. Optionally, you can add the path to the SDK tools directory to your path.
      1. On Windows, right click on My Computer, and select Properties.
      2. Under the Advanced tab, hit the Environment Variables button, and in the dialog that comes up, double-click on Path under System Variables.
      3. Add the full path to the tools/ directory to the path.
2. Download and install JDK 6 Update 3 from Sun. Updating the PATH variable is optional.
3. Install Eclipse
   1. If you dont have Eclipse yet, download the Eclipse IDE for Java Developers package and simply uncompress the Eclipse folder to where you want it installed (eg C:\Program Files\Eclipse).
   2. Make a shortcut to Eclipse.exe on your Desktop, in your All Programs, or in your QuickLaunch.
   3. Run Eclipse and select a folder to store your Workspaces.
4. Install the Android SDK plugin in Eclipse
   1. Start Eclipse, then select Help > Software Updates > Find and Install.
   2. In the dialog that appears, select Search for new features to install and press Next.
   3. Press New Remote Site.
   4. In the resulting dialog box, enter a name for the remote site (e.g. Android Plugin) and enter this as its URL:
      https://dl-ssl.google.com/android/eclipse/
      Press OK.
   5. You should now see the new site added to the search list (and checked). Press Finish.
   6. In the subsequent Search Results dialog box, select the checkbox for Android Plugin > Eclipse Integration > Android Development Tools and press Next.
   7. Read the license agreement and then select Accept terms of the license agreement, if appropriate. Press Next.
   8. Press Finish.
   9. The ADT plugin is not signed; you can accept the installation anyway by pressing Install All.
   10. Restart Eclipse.
   11. After restart, update your Eclipse preferences to point to the SDK directory:
       1. Select Window > Preferences to open the Preferences panel.
       2. Select Android from the left panel.
       3. For the SDK Location in the main panel, press Browse and locate the SDK directory (eg C:\Program Files\Android SDK).
       4. Press Apply, then OK.
5. Create an Android Project
   1. Select File > New > Project
   2. Select Android > Android Project, and press Next
   3. Select the contents for the project:
      1. Select Create new project in workspace to start a project for new code.
         Enter the project name, the base package name, the name of a single Activity class to create as a stub .java file, and a name to use for your application.
         The base package name should be in the format com.yourdomain.android.yourpackagename (for example com.google.android.hello)
      2. Select Create project from existing source to start a project from existing code. Use this option if you want to build and run any of the sample applications included with the SDK. The sample applications are located in the samples/ directory in the SDK.
         Browse to the directory containing the existing source code and click OK. If the directory contains a valid Android manifest file, the ADT plugin fills in the package, activity, and application names for you.
   4. Press Finish.
6. Create a Launch Configuration
   Before you can run and debug your application in Eclipse, you must create a launch configuration for it. A launch configuration specifies the project to launch, the Activity to start, the emulator options to use, and so on. To create a launch configuration for the application, follow these steps:
   1. Select Run > Open Run Dialog or Run > Open Debug Dialog as appropriate.
   2. In the project type list on the left, right-click Android Application and select New.
   3. Enter a name for your configuration.
   4. On the Android tab, browse for the project and Activity to start.
   5. On the Emulator tab, set the desired screen and network properties, as well as any other emulator startup options.
   6. You can set additional options on the Common tab as desired.
   7. Press Apply to save the launch configuration, or press Run or Debug (as appropriate).
7. When you launch your application, the first time you will be asked if you agree to send usage statistics to Google.
   
8. Then your application should start in the emulator. Or at least in my case, it displayed an error (I fixed it by adding a new contact name and number)
9. The emulator is very cool. Clicking on the Home key lets you select from a couple of preinstalled applications such as a Browser, Contacts, and Google Maps

How to re-install the .NET Framework 1.1

1. Remove the .NET Framework 1.1
   1. Download the Microsoft Windows Installer Cleanup Utility and install it.
   2. Run it from Start > All Programs > Windows Installer Clean Up
   3. Select .NET Framework 1.1 from the list and click Remove
2. Download and install the .NET Framework 1.1 Redistributable
3. Download and install .NET Framework 1.1 Service Pack 1. Ignore the message saying it is already installed, go ahead and reinstall it.
4. Download and install .NET Framework 1.1 SP1 Security Update (KB928366). Reboot when asked to.

If this doesn’t work for you, here are additional instructions for repairing .NET version 1.1, 2.0 and 3.0.

Repair .NET Framework 1.1 (method 2)

• Try the knowledgebase article How to troubleshoot Microsoft .NET Framework 1.1 installation issues http://support.microsoft.com/kb/824643
• The msizap.exe utility in step 4 of the article is included in the Windows Installer Software Development Kit for XP and Vista. During installation, select not to install the documentation and samples to avoid downloading 1GB of unnecessary files. (I selected only Visual C++ Compilers and Win32 and .NET Development Tools which came to 32MB)
• Unregister and then reregister Windows Installer (See article)
• Download/install/use:
  http://www.microsoft.com/downloads/details.aspx?FamilyId=7A4EFC33-0343-4EE4-B0C4-97BD16967A09&displaylang=en
• Manually remove and then reinstall the .NET Framework 1.1 (See Article)
  For the articles below, follow the “IT professionals” link and find the download for your OS.
  - Download/Install http://support.microsoft.com/kb/867460/
  - Download/Install http://support.microsoft.com/kb/886903/
  - Download/Install http://support.microsoft.com/kb/928366/
• Reboot as needed and at the end.

Repair .NET Framework 2.0

• How to troubleshoot Microsoft .NET Framework 2.0 installation issues
  http://support.microsoft.com/kb/908077/
• Unregister and then reregister Windows Installer (See article)
• Manually remove and then reinstall the .NET Framework 2.0 (See Article)
  For the articles below, follow the “IT professionals” link and find the download for your OS.
  - Download/Install http://support.microsoft.com/kb/917283/
  - Download/Install http://support.microsoft.com/kb/922770/
  - Download/Install http://support.microsoft.com/kb/928365/
• Reboot as needed and at the end.

Repair .NET Framework 3.0

• Unfortunately there does not appear to be any particular article pertaining to .NET Framework 3.0. I have not had issues with this version, however just going into the Control Panel > Add or Remove Programs and locating and removing it and its patches should be enough to get rid of it. I suggest you do the same and then reboot…
• Download and re-install using this distributable package:
  http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
• Reboot as needed.

Cleanup your updates system…

• Get Dial-a-Fix from http://wiki.djlizard.net/Dial-a-fix
• Use its options to fix:
  - Windows Installer
  - Windows Update
  - All the Registration Center options
• Turn off the “Empty System32\Catroot 2″
  Do NOT do “Flush SoftwareDistribution”.
• Then click “GO”… May take a while.
• Reboot when it is done…

Install Updates

• Visit http://windowsupdate.microsoft.com/ and scan for updates.
• Choose the critical updates you need and install them. Do not bother getting hardware updates (unless you happen to have some Microsoft hardware installed) and “Optional Updates” are *usually* just what the name infers - but feel free to see if you want any of the “Optional” ones.
• Come back here and let us know how you came out…

Imagine trying to buy new ink cartridges for this thing.

Note the flashing lights to warn folks that this is a MASSIVE printer.

Yes, thats a PC monitor on the right hand side.

Best-Quality mode: 600 dpi (apparent)
High Quality mode: 448 dpi
Production mode: 336 dpi

* Up to 400sqm/hr at 336 dpi.
* Up to 200 sqm/hr in true 448 dpi.
* Up to 100sqm/hr in apparent 600dpi.

* Prints 140 posters 1.5m X 1.8m per hour
* 100 billboards per eight hour shift
* 6-color printing.

Size (HWD): 3.25 x 9 x 10m (10.5 x 25 x 62ft)
Weight: 2,700kg (5,952lb)
Power Consumption: 41 KVA max.

Download this StatTraq Calendar Patch. Extract calendar.php from the file and copy it into your \wp-stattraq folder, replacing the file that already exists there.

Now when you check your StatTraq statistics, you will be able to select time periods by Year or Month correctly.