JFX

No, Dism can't return the xml data, only imagex.exe can do. You can download it with my Get WAIK Tools

@ljycslg That was a bug, new 3.5 beta2 unmount all iso when it exits. @bios83 You use a Core version of Windows 8, but only Pro and Server editions support VHD booting. But your screen shot say you use Pro Try right click on VHD button and uncheck the check box that appears. Can you attach the xml from your wim file. You can get the XML by using imagex.exe imagex -info install.wim > install.xml

@bios83 Sure it's possible, just select a mounted VHD as installation drive @ljycslg There is no point in forcing imdisk, the native ISO driver of windows 8 is always used.

You have to run it on a Windows 8.1 Update or WinPE5.1, because of the new WOF driver. If you select a Windows 8.1 Update Wim file there will be a new check box displayed.

New 3.5 beta1 is out! - added WimBoot support WinNTSetup does support normal WIM files for wimboot, means you don't have to capture them using the WimBoot command. However, the stronger the compression the lower the performance of course.

Hmm, if anyone can give me a valid reason for ADK update than yes. But as far I can see it, all changes of the Update are only for the WimBoot feature. And cause Wimboot features depend on WOF driver, one needs a Windows 8.1 updated OS, that already has all these tools

This light gray label is the name and the version of the Software Licensing Description Table in your BIOS. It shows you that this machine is licensed to run a specific version of windows.

Hi wimb, that's properly a missing ADVPACK.DLL in system32 (or syswow64 on x64 PE). I'll drop this dependency in some future version.

@SIW2 There shouldn't be a problem with lng parameter and cfg file. One solution I forgot to mention is setting an environment variable: set winntsetup_lng=2052 @tranngocyd Well, yes it should work nicely, or do you noticed any problem. Only thing it doesn't do is flashing the NVRAM.

Yeah, some files are missing because the download would require a few hundred MB. But you can simply use the Waik_4 tools, they are still compatible with Windows XP.

Hi SIW2, you can either use command line (example add. -lng:1028 to load Lang\1028.dll ) or create a file call language.dll in the Lang folder. You can always get the current English template by clicking on the title bar and select "create language file"

I used an API that's not available on XP, so it should have displayed a "function not found in kernel32.dll" error.

Hmm, that strange it should have displayed and error message, well it does if I run it through the ide. However fixed and re-uploaded now.

So a new final version available, with minor changes to the latest beta Version v3.4.0 - adding support for XP/2003 WIM files - fixed problems with Final OnePiece XP Update packs - EFI Boot files are now only created on EFI partitions - UAC tweak disables now also defender

The older 8.1 dism can apply esd already. So can the old wimgapi.dll (6.2.9200.16384) that I'm using.

Yes, Winntsetup supports esd. But only decrypted ones (likes the ones dism creates) For decypting there seems to be tool available at MDL forum but i have not tried it yet.

@ilkertezcan, yes the tools are updated with the Windows Deployment Tools-x86_en-us.msp patch But I'm not sure if it useful to add the download, cause the only changes are for the new WimBoot feature. And deploying a wimboot image would still not be possible using the new tools. So the only reason for bigger download would be the Wimboot optimization (recompression) of an wim image.

Tranngocyd, winntsetup is no partition software, you have to make sure there is an EFI partition already. Easiest way is to create partitions with bootice

The copying done in beta2 will not cause any problems. But it actually should solve the problem, at least it does here with unchanged English and German ONEPIECE update packs.

Yes, the 6 files (you forget sqmapi.dll) seams to be the only problem. Beta 2 is online making copies of these files after copying them. Also I removed EFI boot files creation if no EFI system partition is selected as boot drive. If no further issues, this one will be final.

OnePiece is absolutely correct here, it's a WInNTSetup issue. I only parse dosnet.inf to create the boot files, but not txtsetup.sif to create $WIN_NT$.~LS folder. Instead the complete folder is copied. While this is of course not the right solution, it much faster. But It only works flawless as long no files are renamed or new created during $WIN_NT$.~LS population. And so it always was with official and unchanged sources. Well, I won't change that anymore, but adding a small check for these 6 files shouldn't be a problem.

If I remember right, the problem with these double entries could be fixed by adding these files in both states (compressed and uncompressed). so you would have 2 files in i386 or AMD64 folder \i386\ie4uinit.mui \i386\ie4uinit.mu_ ie4uinit.mu_ could be a simple copy of ie4uinit.mui and doesn't have to be compressed ie4uinit.mui needs to be decompressed (using expand.exe)

Hmm, I said a bit more complicated not that it's all too much work. And since XP did not get updates any more, you will only have to create it a single time.

Well, main advantage is that the setup time, is reduced. The disadvantage is that is a bit more complicated to create a hardware independent image of XP than Vista and later. The HAL has to be set to oldest require standard. Some drivers like intel processor driver needs to be deactivated else AMD machines could blue screen. All mouse and Keyboard drivers needs to be set to run. Maybe you find some good info, search for "universal XP image ghost"

New Beta version 3.4 Beta 1 So for the end of Windows XP, WinNTSetup now finally supports syspreped WIM images for NT5 systems. Just select them using right - click and setup as usual. one requirement for XP wims: ntldr and ntdetect.com needs to be in the root of an image