dford

You need the Windows WAIK Use Windows system image manager and create the answer file for removal. In Package Node right click the Language you want to remove and Add to answer file. Detailed answer on Microsoft site: http://technet.microsoft.com/en-us/library/cc749497.aspx

This will work <DiskConfiguration> <Disk wcm:action="add"> <CreatePartitions> <CreatePartition wcm:action="add"> <Extend>true</Extend> <Order>1</Order> <Type>Primary</Type> </CreatePartition> </CreatePartitions> <ModifyPartitions> <ModifyPartition wcm:action="add"> <Active>true</Active> <Format>NTFS</Format> <Label>Vista</Label> <Letter>C</Letter> <Order>1</Order> <PartitionID>1</PartitionID> </ModifyPartition> </ModifyPartitions> <DiskID>0</DiskID> <WillWipeDisk>true</WillWipeDisk> </Disk> <WillShowUI>OnError</WillShowUI> </DiskConfiguration> <ImageInstall> <OSImage> <InstallTo> <DiskID>0</DiskID> <PartitionID>1</PartitionID> </InstallTo> <WillShowUI>OnError</WillShowUI> </OSImage> </ImageInstall> <UserData> <ProductKey> <Key>xxxxx-xxxxx-xxxxx-xxxxx-xxxxx</Key> <WillShowUI>OnError</WillShowUI> </ProductKey> <AcceptEula>true</AcceptEula> </UserData> <UseConfigurationSet>true</UseConfigurationSet> </component> </settings>

I use 2 methods with server installs 1) Use DHCP and have RIS with WDS and I have the PXE load the WINPE 2.0 and have my script automated to auto install 2) I use DHCP and boot the workstation with a WinPE CD and net use the Vista folder on the server and run my automated scriped example in tyhe Vista folder setup /unattend:w:\configsets\ultimate\autounattend.xml

In diskpart simply unhide the partition ID=07 and assign letter and then imagex

You need to run BCD Fix to boot the applied image

SATA/150 First-generation Serial ATA interfaces, also known as SATA/150, run at 1.5 gigahertz. This results in an actual data transfer rate of 1.2 gigabits per second (Gbit/s), or 150 megabytes per second. This transfer rate is only slightly higher than that provided by the fastest Parallel ATA mode, Ultra ATA at 133 MB/second (UDMA/133). SATA/300 has a maximum throughput of 300 MB/s. This increased data rate specification is very widely referred to as “Serial ATA II” (“SATA II”) SATA 300 is backwards-compatible with SATA 150 devices, meaning you can plug older SATA 150 hardware into newer SATA 300 ports (and vice versa). If you have a SATA II drive I would recommend that you use that as your boot drive and the PATA as your storage drive. In BIOS you should have the option to set the SATA drive as RAID, SATA or AHCI, you can set it to RAID and have the RAID utility set it up as a JBOD (Just a Bunch of Disks). If you install windows on the JBOD Drive you will need to press F6 at the beginning of your XP Installation (Watch the bottom of the Blue screen when you boot up your Windows Installation CD you will see the F6 prompt) You will need to have your RAID Driver on a diskette. If you do not set up the BIOS for a RAID Drive and just set it to SATA you do not need to specify or press F6 to load a driver for it. If it is SATA II you should notice a difference in the speed. If it is SATA 1 ... you will not notice muchof a difference at all. If your BIOS supports loading the SATA driver as AHCI you will need to load the Driver for this as well

I have seen this problem before: My resolution 1) Re-install the Codec ( I use Intervideo WinDVD) 2) After reboot use Microsoft's Codec Checker to make sure your perferred Codec is set for Media Center 3) Make sure your resolution is set to 32bit In rare occasions I have also had to re-install the Video driver. Hope this helps

1) Are you loading a couple of Drives in RAID MODE? 2) If you are not simply switch to SATA Mode only in BIOS 3) Your Windows XP CD sounds like you have a Winnt.sif file in I386 with the [unattend] section, simply copy the Winnt.sif file to diskette and edit it and remove everything in the [unattend] including [unattend]. 4) Put your RAID drivers on the diskette as well with your new Winnt.sif file (make sure you have the drivers txtsetup.oem file on the diskette 5) Boot the system with your XP CD and the diskette in A: drive (at the same time) make sure to press F6 to specify the driver when prompted. Hope this helps

What is unusual about this setup is the following. Intel and SIS Chipsets with SATA drives have no problems booting and loading the OS from the RIS Server. Loading XP from the CD which was used in the RIS setup does not require the F6 key to load on the NVidia NForce board. But the issue as far as I can tell only exists with the NForce 4 (Non-RAID) and SATA with Server 2003 RIS installation.

I am using a Windows RIS 2003 Server to load Windows XP. My network connects fine and I can install Windows XP image on PATA HD's no problem. However I can not install with SATA drives. I have noticed that the HD activity light stays locked on and the RIS installation reports no Hard Drive. Has any one had success with type of installation? The board I am trying to install on is the Asus A8N-E

Your doing a RIS install and the method you are using probably works with just about every network card out thier except for the new Intel on board NICS. I had the same problem, all you have to do extract the new Intel NIC drivers and you will see a sub folder 2 deep under drivers that has the correct inf files to add to your RIS deployment. I used the same method but added the extra inf into my image being deployed

I take it you have the Winpe folder. In Winpe run OSCDIMG -n -h -bETFSBOOT.COM C:\YourCD Foler Files C:\YourCDIMG.iso

That is a really wierd problem, I have made several slip streamed CD's and only saw that problem once. All I did to resolve the issue was change my optical drive.

http://www.microsoft.com/globaldev/DrIntl/faqs/muifaq.mspx Sorry .......You have to buy it

If I incorporate the 5.10.2600.475 driver that I use from the setup diskette into the txtsetup.sif all drivers are loaded except that I end up with idecoi.dll version 1.0.0.1 and nvatabus.sys 5.10.2600.475 as "unsigned". The only driver that I have had no issues with is 5.10.2600.412 but if the newest driver is installed the same files are unsigned. Does anyone else have problems using windows XP Txtmode setup witrh installing the NForce 4 whql driver 5.10.2600.475. Here's what's happening, If I use the 5.10.2600.412 driver I have no issues: sigverify reports all my drivers as signed. My txtsetup.sif has no issues and all my drivers are signed but if I install the WHQL package with 5.10.2600.475 after setup I will have my SCSI driver updated (RAID Class Controller) as signed..... but I will end up with idecoi.dll version 1.0.0.1 and nvatabus.sys 5.10.2600.475 as "unsigned" If I do a regular install preesing F6 and providing the same driver 5.10.2600.475 there will be no issues all drivers are signed. Has anybody else ran into this problem and any idea's? No need to make a poll!