Tripredacus

Edit your posts instead of making a new one (where possible) if you have had no replies within 24 hours. Did you do what MagicAndre recommended?

Alec Empire - La Guerre D'Opium Some of Alec Empire's instrumental albums remind me of the background music in old black and white horror movies. Goes good with Halloween coming up.

It would be easier to put it up someplace that has free hosting like SkyDrive.

Post the commands you are using and the full error message reported by DISM.

Another reason is because a lot of companies still use out-dated software. They become to reliant on it that the prospect of changing to a newer OS that may not support it is a big problem. Especially if they have to get a newer version, or even have it rewritten. The healthcare and accounting/banking software is known for this for sure. A lot of companies still rely on terminal emulators (such as Hummingbird) to connect to databases too.

I can't see why.

Its too early to tell about this. The Dev Preview didn't have anything to build a system like that.

Merging to currently listening.

Both 32bit and 64bit drivers are here: http://www.msi.com/product/nb/GT683.html#/?div=Driver&os=All Use the appropriate driver for your WinPE architecture. if you don't know which driver to use, search for the HwID of your NIC in the file contents to find the correct INF.

The documentation I have doesn't list en-GB as an option for that, which is probably why people have a problem using it. The only English option is en-US. Language Pack Default Values It appears that en-GB is a valid value for all the other locale settings except UILanguage. You may need to do a reg key to make the change you need during FirstLogonCommands or SetupComplete.cmd.

Is this printer physically connected to a computer or is it just connected to the network?

Well that picture won't work...

What is your OS, Vista or Win7? If you mount your winre.wim and look at the structure, you should be able to make a functional WinPE to replace it. Or even you can try to add packages to the mounted winre.wim. I've not tried to modify a Win7 winre.wim other than adding XML and injecting RAID drivers.

Copy all files to the ramdisk and launch from the ramdisk.

Let's hope this is a language barrier problem. Please clarify 1. Drive works perfect in another computer. 2. Problem CD works in another computer 3. No CD can boot. If no CD can boot, but CD works in other computer. Do you have a CD Cleaner?

I'll find some drivers tomorrow. I can't find the correct link here, but I have it bookmarked at work. Post what WinPE version you are using.

You realise you bumped a topic from 7 years ago! Did you see my reply?

Can this CD be read on another computer?

Considering that XP doesn't support DirectX 10, I'm going to say Vista or 7. I guess some people can hack DX10 to work in XP but I never trusted that idea.

My first dumb thing was with my first computer! That makes sense right? My first PC had a 30MB HDD with WFW 3.11 on it. It also was partitioned to J drive letter for some weird reason. So I decided to delete the stuff that was in all the other partitions (besides C... I wasn't that dumb) and then I'd delete those partitions and extend the C volume. I remember seeing that there were other Windows files in those partitions but thought they were a backup or something. Nope... They were shadow copies. Alas, when I rebooted I got a nice error... to which I formatted the drive and reinstalled WFW.

Imagex would be faster for sure, but Setup can install a captured WIM as well. That is how I use it. The answer file is likely optional, but even if you have captured an image after using sysprep /unattend switch, Setup ignores that answer file. For example, even if your XML only specified the Locale settings (to hide the language select page of OOBE), after Setup applies the image, you'd still see that page. So if you didn't have any special settings, you don't even need to specify a custom tool or have the answer file. Just overwrite the install.wim with your custom WIM, but it still needs to be called install.wim. The only reason I needed to come up with this was because I needed the image in the recovery partition to deploy and then boot to the desktop. If the image is supposed to boot to OOBE, I don't use the custom tool option.

#3 is a program. You should not try to slipstream its driver in, instead install this program. It should give you the HD monitor when your drive type is set to AHCI or RAID. Do not use it if your drive type is IDE, since sometimes the program will crash. For the USB3 driver, grab this: USB3 Renesas from Intel. Extract the EXE with WinRar. In the Files folder, there are the x86 and x64 folder. Inside are the driver files you need. Make sure to use both the 'hub' and 'xhc' INFs because after the drivers for the controller are installed, a "Hub" device will appear and be flagged. As you can tell, I made that mistake already. As I said for the Intel Chipset, install it on something. Then there will be a C:\Intel\logs folder. In there is a log file that shows what it installs. Most importantly, it tells you where it extracts the driver files. Someplace near the top is going to be: [EnumDev] [GetDrivers] [Find INFs] Found INF = C:\Users\LIOKAI~1\AppData\Local\Temp\IPMx2\All\5000XZVP.inf Hello there drivers! of course you'll probably just need to grab the "All" folder. Its really the easiest way to get the files, and updating a chipset driver on some random PC isn't too bad either.

This is a fine place. If the troubleshooting moves into another direction and moving the topic to another area provides better visibility, it will be considered.

Well there are multiple ways to do it. By injecting the updates into the WIM, it will shorten your deployment time. Regarding hotfixes, noticed I removed the link in your post. See the forum rules:

You can make WIMs for XP but you can't service them. Your should probably look at MDT 2010 http://technet.microsoft.com/en-us/solutionaccelerators/dd407791 Cluberti has a 3 part series on how to use MDT http://www.cluberti.com/blog/2011/06/23/mdt-for-the-smaller-guys-part-1/