This is a query regarding installation of Office 2007 in XP SP2. The system is Acer Aspire One with 1GB RAM.
First thing is that the default user that was created after installation of the OS on the machine was "UserXP" and it was l8r renamed. Now in Task manager all user processes show UserXP as the user who's process it is. It doesn't shows the new name. Is it going to be a cause of any trouble later on?
Now the main query. The Office is being loaded in a different partition, not the system partition and while installation it gives the error "Windows Installer is unable to update a protected system file. Aborting installation" It doesn't shows the name of the file but I haven't checked the log file either, yet.
Now on MS site it is said that
Source
Now it implies 2 things. either update to SP3 or the installer I'm using might be corrupted. I've used this same installation package earlier also and never faced such issue. Any Ideas?
First thing is that the default user that was created after installation of the OS on the machine was "UserXP" and it was l8r renamed. Now in Task manager all user processes show UserXP as the user who's process it is. It doesn't shows the new name. Is it going to be a cause of any trouble later on?
Now the main query. The Office is being loaded in a different partition, not the system partition and while installation it gives the error "Windows Installer is unable to update a protected system file. Aborting installation" It doesn't shows the name of the file but I haven't checked the log file either, yet.
Now on MS site it is said that
Windows Installer never attempts to install or replace a protected file. When the InstallFiles action or any other action scheduled before InstallFiles attempts to install a file protected on Windows Server 2003, Windows XP or Windows 2000, the installer calls WFP with a request to install or replace the protected file. The installer requests the file installation from WFP immediately after executing the InstallFiles action. WFP installs or replaces the file on the user's system with a cached version of the protected file. Note that this does not guarantee that the version of the file installed from the cache is the version required by the application. After WFP has installed the file, the installer determines whether this version matches the version in the package. If the file version in the package is greater than the installed version, the installer informs the user that it cannot update the system and that an update of the operating system may be required for the application.
Source
Now it implies 2 things. either update to SP3 or the installer I'm using might be corrupted. I've used this same installation package earlier also and never faced such issue. Any Ideas?