Hi,
That log (300KB) is not "quite big"... nor it is the main log! The main installer log, called "VSMsiLog(...)" is about 50 MBytes (VS2003Pro). But nevermind.
The problem you experience is rare but was reported by a few other users. May have different causes:
- previous VS beta or release candidate versions; see
http://support.microsoft.com/?id=312383
- need to reboot after installing Windows component update CD; only then proceed with VS CD1 install.
- antivirus (or script block software) trouble maker; disable before running setup.
- Windows Installer service corrupted or wrong version; for other versions of Windows you could reinstall Windows Installer 2.0; for XP is part of the OS, see next.
- Windows components missing or corrupted somehow; try reinstalling XP Service Pack 1 (one user reported that as solving this problem); only way to be sure is to perform another clean install (if you had disk images (Norton Ghost, etc.) that would be no problem, just one click away and 5 minutes).
Beside that, I see no reason for installing VS.NET 2002 when VS.NET 2003 is available. The upgrade is only $29! You have the Enterprise Architect version, so $29 is absolutly nothing. VS.NET 2002 is full of bugs... corrected on VS.NET 2003.
Only reason I can think for someone to install VS.NET 2002 today is not being a legal copy. If that is the case you need to check if that copy is ok (not fukked, ripped, or corrupted). To do that, try to install it on another computer.
If you own a licensed Enterprise Architect version, you will have no trouble getting specific help from Microsoft (some free incidents are usually included; if not paid support):
http://support.microsoft.com/