JFX

So to switch the topic, there new beta version available. This and the next Beta versions will use wimlib to handle WIM / SWM / ESD files. Thanks to wimlib, it also adds support for wimboot without the need of the WOF driver. Keeps in mind that's a bit experimental.

Sure the authors of nlite / ryanvm integrator could maybe fix the WinNTSetup problem with the double listed files. Like the ones occurred in the OnPiece update pack. However that will not solve the problems Ikky_Phoenix has here. I'm sure using the normal "winnt32.exe /makelocalsource" install will rise the exact same errors. And that's simply a bug in most update/addon packs, they only support install form CD/DVD. Well, I can't make it any more clear, you just asking for solution in the wrong place here.

For me XP/2003 setup stuff is settled. Decision made to not parse txtsetup.sif and not to rely on Setup API, was for various reasons. And there have never been any problem with official hotfix integration. If an update pack support installing with the normal winnt32.exe, - and not all do, that properly one of the main problems - than the author should be able to make it compatible with WinNTSetup, pretty easy.

HI Ikky_Phoenix, This an usual problem with these update packs, they are not supported by WinNTSetup.

@Atari800XL No not this time, adding support for Onpiece pack was just because it's final and was simple to do. The XP setup stuff, I will not touch anymore, therefor the sysprep support was added. However you should be able to solve these issues by compare the $WIN_NT$.~LS folder create by winntsetup and the one created by winnt32.exe. @AZJIO Hmm, I still don't see the problem with the file dialog that I currently use.

I guess, this more a matter of taste. A combobox has it's disadvantages, too. Such as these ugly focus rectangles, or the need of a refresh button cause not everything send device message on changes. With the current input box, you just need to push the key for the letter you want.

Nice find Well changing the ProductOptions is very dangerous and good to hear it's not required. The "HKLM\System\WPA\POSReady\Installed" reminds me of the VLK version of XPMCE with Tablet Inkball game that I made years ago. Not sure if MS will react and fix this leak, properly not. Cause it's not really legal to upgrade the windows edition, I'll not add this tweak. But maybe I'll add support for custom .reg files.

Hi The Rookie, I don't know how screen readers work, I guess they simply sends a WM_GETTEXT message to every control. If so, it would require a massive change to the UI, that I don't like to do. But if there is a way to add hidden text to the controls the will be spoken than I would be glad to add it.

Well, these are all WIM files, and yes everything you can create with dism is supported.

Well, no. But there isn't any reason to use it ,too. It just a customization option, some like, it some not, but most people properly don't care about. So no, I don't add an option for it. Such things belong in the unattended file.

Here is another tool that a bit more talky attachment=38367:ximage.zip You can run it like imagex, it should show Info, warning or error message while applying

VHD drives are disabled from boot drive by default. Right-click on VHD button and unckeck the popup menu

Properly one of the oldest bugs, fixed in 3.5.1.

You should have mentioned why you think it's fast. 1. reason why Wimlib is so much slower could be cause it's a cross platform library. Properly using a not so great compiler. 2. There seams to be a bug, while applying and image to NTFS. Apparently, it messed up hard links. Well if it writes 2GB more data, it's actually not that slow.

Fast? It took 2,5 minutes here, that's much slower that normal wim file. Well the speed dependent on the used wimgapi.dll. Currently the Windows 8.1 versions is the fastest, but this one is no longer compatible with windows xp.

Thanks for the report. I see no reason to still call it Beta. WinNTSetup 3.5 Final added support for WimBootfixed mounted ISO files on Windows 8 was not unmounted on exitfixed EditionID was not detected on self made WIM filesfixed missing English fallback on not translated stringsadded combo box to select bcdboot firmware optionadded new cmdline switch: -bcd:{ALL|BIOS|UEFI} to specific bcdboot firmware option

Dism will check if the WIMBoot entry is set in the Wim XML. But this check can be skipped by setting an environment variable: set WIM_SKIP_WIMBOOT_CHECK=1

@jaclaz Well here, the link you gave has the same tutorial as the one I posted (at least the same pictures).

Yes, imagex will do, it. Here's a small guide that looks good.

The 8.1 Dism can capture and apply eds files.

Normally WimBoot only supports optimized WIM files, exported or captured with the /WimBoot parameter. These files have XPRESS compression with smaller dictionary size. However, normal XPRESS or LZX compressed WIM files can be used, too. But not esd files. Not sure what's the exact requirement for WIM file placement, definitive not CDFS/UDF, maybe not even removable drives at all. But for sure local NTFS drives.

Well, you could simply use my WinNTSetup. Or you would need your Windows 8.1 32bit DVD. Using the setup.exe on the 32bit DVD you can make use of the command line option /installfrom to specific the install.wim form your 64 bit windows http://technet.microsoft.com/en-us/library/cc766446(v=ws.10).aspx

Okay thanks for the info. I added a combo box to Beta 4, with the 3 firmware option that bcdboot has. As well as a new cmdline switch: -bcd:{ALL|BIOS|UEFI}

Hmm, I changed it to only create EFI boot files if the selected boot disk is an EFI system partition. Cause there was a report here, that EFI files causing problem in MBR mode. So you mean, you have a MBR USB-Stick with a FAT32 boot partition, and you can boot that in (U)EFI without compatible mode? Guess I really should add a check box for EFI files (and select it by default)

Thanks, I think, I fixed it in Beta3