I assume you have tried simply inserting the Windows XP reinstallation CD that came with your system and it did not work.
I was able to add IIS on my system (which came with Windows XP and no service packs) without difficulty. You might try duplicating the setup I have on my system. Copy all the files from the i386 folder on your reinstallation CD to an i386 folder on your C:\ drive. After doing this, open regedit and navigate to HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\Setup and change the value of SourcePath to
C:\. (Make sure the i386 folder is on the root of the C:\ partition.)
This should allow you to add Windows components (and will also eliminate the requirement to insert the Windows XP reinstallation CD to add components or to run system file checker).
The difference between your setup and mine is that my i386 folder has not been slipstreamed with SP2 so that the add component wizard is apparently accessing either the C:\i386 folder or the C:\Windows\Service Pack Files folder for the files it needs.
The SP2 CD is available free from
here. Despite the stated time requirement, I received my copy in about a week.
the i386 directory is already on my computer and is slipstreamed with sp2. I have no problem installing iis on other computers that I have built from scratch using both the standard non service pack installation of XP Pro or slipstreamed sp2 installations.
The strange thing is that even when I unpack and expand all of the relevant files (i.e: the ones that the add component wizard is asking for) from the network installation version of the service pack and point the installer to them it comes back with the same message asking for the original sp2 cd which as far as I can tell, I have to pay for from microsoft, only a nominal fee but annoying none-the-less.
The problem displayed by my default dell build is not something I have come across before and I have to re-build my machines on a regular basis because the work I'm involved in which is why I'm stumped. Maybe there is a missing cab file? or a corrupt registry entry?
Thanks for the help, any more ideas will be very welcome :-)
Denny Denham
2 Intern
•
18.8K Posts
0
January 3rd, 2005 15:00
I assume you have tried simply inserting the Windows XP reinstallation CD that came with your system and it did not work.
I was able to add IIS on my system (which came with Windows XP and no service packs) without difficulty. You might try duplicating the setup I have on my system. Copy all the files from the i386 folder on your reinstallation CD to an i386 folder on your C:\ drive. After doing this, open regedit and navigate to HKEY_LOCAL_MACHINE\Microsoft\Windows\CurrentVersion\Setup and change the value of SourcePath to C:\. (Make sure the i386 folder is on the root of the C:\ partition.)
This should allow you to add Windows components (and will also eliminate the requirement to insert the Windows XP reinstallation CD to add components or to run system file checker).
Denny Denham
2 Intern
•
18.8K Posts
0
January 3rd, 2005 19:00
The difference between your setup and mine is that my i386 folder has not been slipstreamed with SP2 so that the add component wizard is apparently accessing either the C:\i386 folder or the C:\Windows\Service Pack Files folder for the files it needs.
The SP2 CD is available free from here. Despite the stated time requirement, I received my copy in about a week.
chris.ralph
3 Posts
0
January 3rd, 2005 19:00
Hi,
the i386 directory is already on my computer and is slipstreamed with sp2. I have no problem installing iis on other computers that I have built from scratch using both the standard non service pack installation of XP Pro or slipstreamed sp2 installations.
The strange thing is that even when I unpack and expand all of the relevant files (i.e: the ones that the add component wizard is asking for) from the network installation version of the service pack and point the installer to them it comes back with the same message asking for the original sp2 cd which as far as I can tell, I have to pay for from microsoft, only a nominal fee but annoying none-the-less.
The problem displayed by my default dell build is not something I have come across before and I have to re-build my machines on a regular basis because the work I'm involved in which is why I'm stumped. Maybe there is a missing cab file? or a corrupt registry entry?
Thanks for the help, any more ideas will be very welcome :-)
Ralphy