MSi Error help with XP
I am trying to tweak the winnt32.msi for XP deployment . I open the xp msi in Orca and change the Runsetup and Runsetup immediate parameters to point to the network location. This launches the install when clicking on the msi but it stops towards the end with "Internal Error 2356.Data1.cab" error. Am I missing a step with ORCA? I copied the entire contents of the xp disc to the network and have a proper unattend file. What does the msi need to run complete?
Thanks for any insights
Thanks for any insights
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
VikingLoki
19 years ago
2356 Could not locate cabinet in stream: [2].
It can't find Data1.cab. I'd strongly suspect the winnt32.msi to be an extremely customized msi and a bear to modify. You're choosing a rough path to your XP deployment and will be better off scripting it. Since you're upgrading your OS, you won't get any benefits of Windows Installer. Script it.
It can't find Data1.cab. I'd strongly suspect the winnt32.msi to be an extremely customized msi and a bear to modify. You're choosing a rough path to your XP deployment and will be better off scripting it. Since you're upgrading your OS, you won't get any benefits of Windows Installer. Script it.
Posted by:
C3PO
19 years ago
This is what were trying to do
"Next, you must edit the default .msi file that comes with XP. To perform this step, you need an .msi database editor, such as Orca. (To learn how to obtain and install Orca, see the sidebar "Installing Orca.") Run the .msi editor, then open winnt32.msi from the shared directory you created. You must change the action that occurs when the installer runs. Click CustomAction, as Figure 1 shows, then change the value in the Target field for both RunSetupImmediate and RunSetup to
"<SourceDir>winnt32" /s:"<SourceDir>."
/unattend:"<SourceDir>unattend.txt" /batch "
This tells the msi the location of the network share, and then you are able to deploy with Group Policy.
The unattend text that it calls has the NTUpgrade=Yes to upgrade the os. What would cause the msi to be unreceptive to the change? If the entire disc is copied to the network share why would the msi have trouble with the cab? The only thing I can see that relates to data1.cab is under the media section of ORCA after opening the msi to edit. If anyone could test an winnt32.msi that ships with Xp And open in ORCA do you guys seethe same stuff?
We have a unattend install that works , but I was interested in deploying a customized msi with GPO
"Next, you must edit the default .msi file that comes with XP. To perform this step, you need an .msi database editor, such as Orca. (To learn how to obtain and install Orca, see the sidebar "Installing Orca.") Run the .msi editor, then open winnt32.msi from the shared directory you created. You must change the action that occurs when the installer runs. Click CustomAction, as Figure 1 shows, then change the value in the Target field for both RunSetupImmediate and RunSetup to
"<SourceDir>winnt32" /s:"<SourceDir>."
/unattend:"<SourceDir>unattend.txt" /batch "
This tells the msi the location of the network share, and then you are able to deploy with Group Policy.
The unattend text that it calls has the NTUpgrade=Yes to upgrade the os. What would cause the msi to be unreceptive to the change? If the entire disc is copied to the network share why would the msi have trouble with the cab? The only thing I can see that relates to data1.cab is under the media section of ORCA after opening the msi to edit. If anyone could test an winnt32.msi that ships with Xp And open in ORCA do you guys seethe same stuff?
We have a unattend install that works , but I was interested in deploying a customized msi with GPO
Posted by:
C3PO
19 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.