Jump to content

WinNTSetup v5.2.4


JFX
 Share

Recommended Posts


There is no description from xml file.

 

KOgXvKS.png

<WIM><IMAGE INDEX="1"><NAME>Windows 7 Drive C 19.01.2016</NAME><DIRCOUNT>29160</DIRCOUNT><FILECOUNT>362872</FILECOUNT><TOTALBYTES>48041669419</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D15237</HIGHPART><LOWPART>0x4C546A3E</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D15239</HIGHPART><LOWPART>0x8089BDD4</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="2"><NAME>Windows 7 Drive C 20.01.2016</NAME><DIRCOUNT>29161</DIRCOUNT><FILECOUNT>363126</FILECOUNT><TOTALBYTES>48091713044</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D15300</HIGHPART><LOWPART>0xA1E39B4A</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D15302</HIGHPART><LOWPART>0x6F7632BA</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="3"><NAME>Windows 7 Drive C 21.01.2016</NAME><DIRCOUNT>29162</DIRCOUNT><FILECOUNT>362995</FILECOUNT><TOTALBYTES>48116751876</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D153C9</HIGHPART><LOWPART>0xE79EF426</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D153CB</HIGHPART><LOWPART>0xF3C2F016</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="4"><NAME>Windows 7 Drive C 22.01.16</NAME><DIRCOUNT>29165</DIRCOUNT><FILECOUNT>362827</FILECOUNT><TOTALBYTES>48187942164</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D15493</HIGHPART><LOWPART>0x3F1D503E</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D15495</HIGHPART><LOWPART>0x4B69C398</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="5"><NAME>Windows 7 Drive C 23.01.16</NAME><DIRCOUNT>29168</DIRCOUNT><FILECOUNT>363189</FILECOUNT><TOTALBYTES>48222490420</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D1555C</HIGHPART><LOWPART>0x7CB80A64</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D1555D</HIGHPART><LOWPART>0xCB0882CE</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="6"><NAME>Windows 7 Drive C 24.01.16</NAME><DIRCOUNT>29169</DIRCOUNT><FILECOUNT>363146</FILECOUNT><TOTALBYTES>48254288233</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D15625</HIGHPART><LOWPART>0xDD14C252</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D15627</HIGHPART><LOWPART>0x7449665E</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><IMAGE INDEX="7"><NAME>Windows 7 Drive C 25.01.16</NAME><DIRCOUNT>29169</DIRCOUNT><FILECOUNT>363168</FILECOUNT><TOTALBYTES>48273197033</TOTALBYTES><HARDLINKBYTES>6134903128</HARDLINKBYTES><CREATIONTIME><HIGHPART>0x01D156EF</HIGHPART><LOWPART>0x10DA3828</LOWPART></CREATIONTIME><LASTMODIFICATIONTIME><HIGHPART>0x01D156F0</HIGHPART><LOWPART>0xADD9BB02</LOWPART></LASTMODIFICATIONTIME><WINDOWS><SYSTEMROOT>WINDOWS</SYSTEMROOT><ARCH>0</ARCH><EDITIONID>Professional</EDITIONID><INSTALLATIONTYPE>Client</INSTALLATIONTYPE><PRODUCTNAME>Windows 7 Professional</PRODUCTNAME><VERSION><MAJOR>6</MAJOR><MINOR>1</MINOR><BUILD>7601</BUILD><SPBUILD>17514</SPBUILD><SPLEVEL>1</SPLEVEL></VERSION><PRODUCTTYPE>WinNT</PRODUCTTYPE><PRODUCTSUITE>Terminal Server</PRODUCTSUITE><HAL>acpiapic</HAL><LANGUAGES><LANGUAGE>ru-RU</LANGUAGE><DEFAULT>ru-RU</DEFAULT></LANGUAGES></WINDOWS><FLAGS>Professional</FLAGS><DISPLAYNAME>Windows 7 Professional</DISPLAYNAME><DISPLAYDESCRIPTION>Windows 7 Professional</DISPLAYDESCRIPTION></IMAGE><TOTALBYTES>30837476908</TOTALBYTES></WIM>
Link to comment
Share on other sites

@commiethebeastie

 

Your wim has all the same DISPLAYNAME, so they all look same.

You can use imagex.exe -info, to correct your XML data.

Edited by JFX
Link to comment
Share on other sites

Hi Hunter,

 

that was the command line for the old version 2.

Seams I have not updated the first page for over 2 years  :blushing:

 

Just remove the "VHD" from the switches:

 

WinNTSetup_x86.exe VHD-create -File:"D:\my.vhd" -Size:25GB -Type:expandable

Edited by JFX
Link to comment
Share on other sites

1) Yes /NoBootSect and also /BCD:none.

    However if you do an XP/2003 installlation, it will still create some boot files

 

2) No, not posible, one can not even install Windows Vista and later on an NTFS compressed drive.

    Also double compression usually don't result in any spaced saving.

   

3) I will take a look at it.

Link to comment
Share on other sites

1) I mean option "Virtual Mashine Boot VHD(X)" in WIM2VHD-MOD.

How i can do this in WinNTSetup?


Available modes of compression / decompression for NT6-NT10 OS:

xpess4k, xpess4k+NTFS, xpess8k, xpess8k+NTFS, xpess16k, xpess16k+NTFS, LZX, LZX+NTFS, NTFS.

Can you add this feature in WinNTSetup?

3) Compact MFT is a a very useful utility!

When formatting a NTFS MFT is in the middle section, this area is not available.

This makes it impossible to defragment files that are broken in the area.

The utility formats the partition, creating a MFT at the beginning of this section, and solves the problem of fragmentation.

Link to comment
Share on other sites

 

Hiberating a computer is the equivalent of taking everything on the system's RAM and saving it to a file on the hard drive. When you resume from hibernate, this file must be completely loaded into RAM at a very early stage in the boot process.

So early in fact, that the computer doesn't have any understanding of VHD files or how to access them. It can only read a whole file from disk into memory. (it reams the hibernate file). It isn't possible with raw disk images either becuase Windows has no way of knowing where the hibernate file resides when you boot from what is initially the same general concept as VHD boot.

Not really-really, a RAW (or non-native VHD) booting actually has the disk drive image mapped BEFORE the bootloader gets control and is "hooked" by the suitable driver (say Firadisk or WinVblock) just like a "real" hard disk is "hooked" by the controller driver.

As a matter of fact a "fixed" VHD is ALREADY a RAW image (with a sector appended to it).

Which BTW does not mean that hibernate work (or does not work) with RAW image booting.

 

As for creating a raw disk image, a VHD (not sure about VHDX) can be stripped of its VHD header and become a raw disk image.

Which actually (the header for monolithic, fixed, non-sparse, non-growing non-differential VHD's) is NOT a header but rather a footer, i.e. a single sector "appended" to the RAW image, JFYI:

http://reboot.pro/topic/9715-firadisk-and-vhd-img-images/?p=83781

http://reboot.pro/topic/8480-clonedisk/

jaclaz

 

 

This is a very late response but I just now first read the reply...

 

At the time of my post, I was fully aware of those drivers, and had used them many times.

 

 

The thing is, you can essentially write a driver to extend the functionality of Windows in most any way. But using grub4dos to load the file into memory before the Windows bootloader is invoked is bound 3rd party (pre)bootloaders and 3rd party drivers.

 

 

True though, I should have said footer instead on header.

Link to comment
Share on other sites

Why not simply use these 3 tools. I don't think it's good idea adding all this to WinNTSetup.

Good to have a bunch of screwdrivers, but it's convenient one with a bunch of nozzles.
Your program is more convenient - it's faster, and most importantly supports XP.
Please add these 3 little option in your wonderful program. Why not? Please!
Edited by Hunter23071985
Link to comment
Share on other sites

That's easy, because I'll have all the work to do. :thumbdown

 

Means, to investigate and fully understand these tools.

 

Than to write all the code and test it on all supported Windows version 

including WinPE. Not to mention finding solution for the limitations,

like the 128GB FAT32 limit diskpart has.

 

In the end, it will increase the support needed.

Edited by JFX
  • Upvote 2
Link to comment
Share on other sites

  • JFX changed the title to WinNTSetup v5.2.4
  • wimb featured this topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.


×
×
  • Create New...