JCadenhead

Ahhh. that'll explain my Server boot.wim problem! Never quite clicked that DISM wasn't part of the mounted offline image. Doh! I suppose the clue is in the description: 'offline'! Cheers! Think I've finally figured out my setup.exe issue with my custom wim. Was mentioned on a much earlier thread, turned out to be resolved by putting a lang.ini file into the source folder where the setup.exe was (got the lang.ini from the source folder on the server disk). I've spent days trawling the internet for guidance, and this forum is the first I've seen mention a lang.ini file! Amazing that MS can't think to mention it in any of their regular documentation on WinPE/WDS! All seems to be working nicely now. Just got to get my XP driver injection up and running, and get it working across VLANs. Have got our network guys adding the helper records on our cisco kit, but something ain't quite working... Anyhow, thanks for the replies. Hopefully this thread will help someone else with the same kind of problems. - Jaspar

Thanks for the reply Leen. Unfortunately, it's none of the above. I'd previously experienced the quotes oddities with DSM, and have been quite happily working around it's nuances in the WAIK wim. The error that comes up with the Server 2008 boot.wim is that DISM is not compatible with Vista RTM or earlier, and then refers to checking a DLL is present (which it is). If it weren't for my inability to get the WAIK wim to work with WDS, I'd be staying well clear of the server 2008 wim, as it's rather out of date (and clearly not quality controlled!). If anyone can help me get the custom WAIK wim to work properly with WDS, that's the way I'd rather go (rather than trying to fix an out of date flaky product!) As far as the associated laguage pack is concerned, unfortunately, I had installed it (winpe-wds-tools_en-us.cab), so that sadly doesn't appear to be the problem. Once again many thanks. Anyone else got any advice?

Hi, This is my first post on this forum! I've been messing around with Windows Deployment Services for the last few days, with frequent frustration! Now I've got it all up and running, and working fine, but still have a few niggles. After much messing about, I found that the only WinPE image that I could get to work with WDS were the ones off the Win 2008 Server disks. Problem is, the x86 boot.wim from the server disks has a compatibility problem with the DISM included on the image! This means I can't install any updated network drivers. So while this setup is working for now, I imagine sooner or later I'm going to get driver issues. I've spent plenty of time trying to build a custom PE image through the WAIK, installing all the appropriate packages, including the WDS client. However, the WDS Client setup.exe fails with the following error message: 'Windows could not determine the language to use for Setup. Error code: 0x80004005' I've done endless googling on this error, and come up with nothing. Anyone got any idea? Unfortunately, the environment just reboots, without any chance to look for logs relating to the failure. I've set the languages in every place I could think of. I've spent so long on these little issues, it's sending me a bit twitchy! Eternally grateful for any advice! Thanks, Jaspar