JFX

Geez, these evil antivirus, just making problems. But actually this should not be the reason, cause WinNTSetup will not start without offreg.dll.

JFYI, instead of PEChecksum.exe one can also use Unsigntool. It strips the no longer needed digital signature and fixes the PE Header checksum.

Thanks, It's corrected now.

Small Update to Version 3.6.3 - error code get's logged if offline registry fails - Description field is used if the WIM index has no name - Winntsetup_iso.cmd can be moved into Tools folder

Well, yes dism supports Vista since SP1, but only very limited. Under Vista dism will properly only be a wrapper for pkgmgr.exe

No, You can not use Dism for a Windows Vista Distribution. You should be careful adding patches this way to newer Windows, too. Updates in pending state can cause problems with the fast install way. To add updates to your Vista you have to install it, update it and than generalize it with sysprep again.

I will add more details to the error message in the next version. So we can figure out why it fails to load the registry. But for now you should be careful with this install.esd, cause it's most likely corrupted.

@jamisir Either you an aggressive AV software or your windows distribution have missing or corrupted registry hives. @Atari800XL Well, don't think there can be much interesting stuff about WimBoot. But you can send me the PDF in a PM.

No, I only took a small look on the last issue, were winntsetup was used to install to NAS. @devdevadev Let's wait how wimboot will evolve, before adding such feature. There would be a need to add much more options than just copying or converting the wim format.

Well yeah, it should work, but you have to copy the wimboot.wim to the UDF before using WinNTSetup. To convert your esd try: wimlib-imagex export /?

No, I generally don't read any PC related magazines. What happened, that they get you so upset?

Sigh. Seems you learn by asking, but not reading or actually trying something. Well let me answer questions in numeric order. 1. encrypted install.esd have an ENCRYPTEDESD node inside their XML 2. WinNTSetup doesn't require wimlib for wimboot, if you use windows 8.1 upd 1. 3. Both using the "technique" on Windows 8.1 upd 1, but wimlib can do this experimental on older windows versions, too. 4. same as 3 5. the 1st of course, saving disk space is the purpose of wimboot 6. 3rd! 7. well yes, that the point of dynamic vhd's

You can not use esd files for wimboot. For encrypted files, well you will notice it, if you try to apply them with any tool. I can't support them without making changes to the wim files and that's not an option. But maybe wimlib will support them in future ...

Yes, old winload.exe can load XP/2003, version of bootmgr doesn't matter. If I remember right the Vista RTM version was the last working one. But a small problem was that they checked for digital signature of the kernel. And XP has no signed kernel.

You can do it with bcdedit.exe Bcdedit /create {legacy} /d "Windows XP"Bcdedit /set {legacy} device bootBcdedit /set {legacy} path \ntldrBcdedit /displayorder {legacy} /addlastBut you also need to copy ntldr, ntdetect.com, boot.ini and optional bootfont.bin from your XP partition to the current boot partition. The one where bootmgr and Boot\Bcd is located.

Hi edborg, no there are no problems with Win 8.1 Enterprise 32b. A blinking cursor on the top left screen is usually cause by a BIOS and boot sector incompatibly. If possible delete the partition and create a new one with some partition software.

Well, thinking still the same

You should not use Wimscript.ini, if you not absolutely sure what you do. \Windows\SoftwareDistribution is the only line that okay here. If you really need to get it smaller, check out Dism functionality like /ResetBase and /Compress Recovery

@kreker Thanks, for the updated language file. @devdevadev Yes, of course you can do that.

devdevadev, please stop polluting this and other topics on every forum you see. Currently most people taking summer break or watching football. As you seem to have way much time, why not try to do something on your own? As for your questions: - esd files are not supported, so get a normal sources with install.wim or learn how to convert esd to wim. - reconsider why you need to have two partitions available at the same time, or try karyonix diskmod

Hmm, can't reproduce it, but try re download, I reverted back to an older fileop.lib

Final Version 3.6.0 - new option to use wimlib 1.7.0 for all WIM operations* - wrong error message for VHD checks - fixed applying failed on to low system free space - fixed avoid wimboot uses on server type OS - fixed applying to a folder if current working dir has the same root as install drive - added -regtweaks:{path} commandline and gui option *You have to add the wimlib dll files to "Tool\x??\wimlib" folder and add "-wimlib" commandline parameter

That means that wimlib has a problem with applying a file or other NTFS data from the WIM to disk. If your drive D: contains data already, than format it and try again. If this not helps, right-click on title bar --> "WIM API" and select WimGAPI.

Yes, wimlib improves quite fast. I'll wait until final is out, so we will have two finals. However if you guys make apply speed test, don't forget that you have to reboot your machine every single time. Else the disk cache will make your results useless. BTW: I don't think that the decompressor is wimlibs problem here. I just made a apply test with uncompressed install.wim. Latest wimgapi: 0:51 minutes Current wimlib: 1:46 minutes

I just read the article now. Looks interesting