• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1029
  • Last Modified:

where to find hotfix executable programs for xp install problem

working on a cpu upgrade from xp home to pro and at the 34 min mark the cpu reboots and restarts in an endless loop.

I understand this problem is refered to in MS Article 814847 "How to Slipstream hotfixes hat replace preexisting driver files".

I have looked at the setupact log and found

"""The external program RUNDLL32 shell32,Control_RunDLL intl.cpl,,/f:"C:\WINDOWS\System32\$winnt$.inf" /s:"M:\I386" returned exit code 0.
NetSetup: SetupMode: 0x1, ProductType: 0x0, OperationFlags: 0x800c
Setup encountered an error while trying to set system security.

An extended error has occurred.

C:\WINDOWS\System32\usbhub.sys was not deleted because of the following error:
The system cannot find the file specified."""

This is where I get lost and need help.

1. It says to connect to the cpu you want to make a distribution folders on.  
How do I do this?  Can I use boot disks and do this from a command prompt?

2. next it says to create an i386 distribution folder by typing the following MD E:\i386

What is E: suppose to be my hard drive (C:)?

3. Use the xcopy command-line utility to copy the files and subfolders from the Windows 2000 SP3 CD-ROM (integrated installation) to the E:\i386 folder. For example, if your CD-ROM drive is drive D, type the following:
XCOPY /E /I /V D:\i386 E:\i386

I am installing XP pro sp1 not windows 2000 sp3 so do all the commands stay the same?

4. Create an E:\i386\svcpack folder. For example, to create a svcpack subfolder in the i386 folder, type the following:
MD E:\i386\SVCPACK

This should be easy once I figure out step 2

5. Copy the hotfix executable program (Qnnnnnn_XXX_YYY_ZZZ_LL.exe) to the E:\i386\svcpack folder by using the 8.3 naming format (Qnnnnnn.exe), where nnnnnn represents the actual hotfix number.

Where do I find this hotfix executable program????


0
rngrfan
Asked:
rngrfan
  • 2
  • 2
1 Solution
 
Carlo-GiulianiCommented:

These instructions are about creating a "distribution share" which can then be used to install from.   They assume you are running some version of Windows on your target computer and will be able to map to the "distribution share" and launch the install from there.  

1)  Can you still boot the original OS (XP Home?)   If not, you will either have to install some other version of Windows or try do use the recovery console (which you can run from the XP install CD).

2) No, they did not mean C: ....but I suppose you could use C: (or any other available volume)

3) I have not done this with XP, but yes, I think the commands will be the same.

5) You can find the executable here:
http://www.microsoft.com/downloads/details.aspx?amp;amp;displaylang=en&familyid=4e370d0f-bca4-4a2a-9cde-dfe2da16672a&displaylang=en
0
 
BillDLCommented:
Most (if not all) windows updates and hotfixes use msiexec.exe (The Windows Installer) to perform the installation by creating an .msi file as the setup script.

There are some common administrative setup options that can be used with the msiexec.exe command:

http://msdn.microsoft.com/library/en-us/msi/setup/command_line_options.asp

The options to overwrite (replace) pre-existing files is /f  followed by the appropriate qualifier:

a - Forces all files to be reinstalled

The /p option is used to install a patch.
msiexec /p <PatchPackage>[;patchPackage2…] /a <Package>

So, to chain patches together, just separate them by a ;

If you want to install a package, and then chain on the patches, you can use the /i (install) option for the package, and then specify the patches, but generally the /i and /p can't be used together.

msiexec /i A:\Example.msi PATCH=msipatch.msp;msipatch2.msp

You should also consider the /q option and qualifiers, and have a look at this page:

http://msdn.microsoft.com/library/en-us/msi/setup/standard_installer_command_line_options.asp

where you will see options to prevent windows restarting between patches.

Here's a good presentation on a cleaner page that shows the options:

http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpCmdLineMSI.htm

You should also acquaint yourself with "Transforms" (.mst files):

http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpTransformsApply.htm
http://helpnet.installshield.com/robo/projects/helplibdevstudio9/IHelpTransforms.htm

Just ignore the bits about "creating" transforms and the "transform wizard", as this relates to the installshield developer studio.

See also:

http://msdn.microsoft.com/library/en-us/msi/setup/windows_installer_start_page.asp

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/platform_sdk_components_for_windows_installer_developers.asp

http://www.installsite.org/pages/en/msifaq/a/1005.htm

http://www.developer.com/net/net/article.php/3318381

To install Windows Installer SDK

1. Download and install the Windows Installer SDK
2. Navigate to the installation location and launch Orca.msi from the \bin folder.
3. The Orca.msi launches the Orca setup program. Once the setup program is complete, an Orca shortcut is added to the Start Menu.

Hope this is helpful.



0
 
rngrfanAuthor Commented:
Thats the file I needed but unsure if I can set up a distributed share since this cpu isnt on a network
0
 
Carlo-GiulianiCommented:
Well, you could put the I386 directory on a CD....but it will not be a bootable install CD.  Creating a bootable Install CD is really another subject.   You don't need it if you have a working copy of Windows on the machine.
0

Featured Post

Important Lessons on Recovering from Petya

In their most recent webinar, Skyport Systems explores ways to isolate and protect critical databases to keep the core of your company safe from harm.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now