dleblanc22
asked on
Server 2003 RIS unexpected error (21) after riprep of an image with new Mass Storage Device drivers
I am trying to build a new image for a new Compaq nc6320 laptop which has the intel 945GM chipset. I had to modify my RIS flat image of XP SP2 to incorporate the new SATA controler. To do this I added the directory $OEM$\Textmode with the appropriate drivers and added a [MassStorageDrivers] and [OEMBootFiles] section in the ristndrd.sif with the appropriate entries. I also copied the files to the i386 folder. This worked well and I was able to load a base Windows XP SP2 installation onto the laptop.
After I finished applying my changes to this new installation I created my system image using riprep.exe which completed normally. I then modified my new image riprep.sif file to include the same new [MassStorageDrivers] and [OEMBootFiles] and created the $OEM$\Textmode directory and copied the driver files into it. However, now when I try to load the image on a laptop, the process can not finish the textmode stage and stops half way with the following error: Unexpected Error (21) in txtsetup.oem on line 1742 in d:\xpsp1\base\boot\setup\o
I can see the copied drivers in the i386\Mirror1\UserData\Driv
I am hoping someone else has encountered this and was able to find the solution.
After I finished applying my changes to this new installation I created my system image using riprep.exe which completed normally. I then modified my new image riprep.sif file to include the same new [MassStorageDrivers] and [OEMBootFiles] and created the $OEM$\Textmode directory and copied the driver files into it. However, now when I try to load the image on a laptop, the process can not finish the textmode stage and stops half way with the following error: Unexpected Error (21) in txtsetup.oem on line 1742 in d:\xpsp1\base\boot\setup\o
I can see the copied drivers in the i386\Mirror1\UserData\Driv
I am hoping someone else has encountered this and was able to find the solution.
ASKER
The original OS load from the flat network files works. The problem lies after the imaging with riprep. The build is obviously not an OEM version of windows since it originates from a flat network installation. The corporate key is injected with the .sif file.
The txtsetup.oem file can not be modified since it is created at the beginning of the image load and includes all the .oem instructions from the OEM drivers added to the image and then copied to a virtual D:\ drive created by the RIS process prior to the textmode stage.
I actually was able to find the problem today which is caused by the RIS not being able to differentiate between 2 different flat network installs of XP. I had to rename the flat installation folder which wasn't used during the riprep so that it was listed after the actual source flat install folder. What was happening is that the textsetup file was created using the OEM drivers in the ripreped image but then referencing the wrong flat image file. Seems to be a RIS bug.
All is working well now.
The txtsetup.oem file can not be modified since it is created at the beginning of the image load and includes all the .oem instructions from the OEM drivers added to the image and then copied to a virtual D:\ drive created by the RIS process prior to the textmode stage.
I actually was able to find the problem today which is caused by the RIS not being able to differentiate between 2 different flat network installs of XP. I had to rename the flat installation folder which wasn't used during the riprep so that it was listed after the actual source flat install folder. What was happening is that the textsetup file was created using the OEM drivers in the ripreped image but then referencing the wrong flat image file. Seems to be a RIS bug.
All is working well now.
Sounds like you've done some work with this - nice job.
I wasn't trying to imply you weren't legit, but I was concerned you might have been imaging an OEM build then redeploying and using the key on the outside of each PC.
Turns out that was a non-issue.
Good work and thanks for the heads up.
I wasn't trying to imply you weren't legit, but I was concerned you might have been imaging an OEM build then redeploying and using the key on the outside of each PC.
Turns out that was a non-issue.
Good work and thanks for the heads up.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Did you slipstream the source?
It appears the contents of the CD still think it's SP1.
On the reference machine, can you find that OEM file? You may need to edit it before RIPREP'ing it.
Are you mass imaging an OEM build? Not exactly legal...