WinNTSetup v5.4.1

[JFX]

Wimlib's shapshot option does not include any writer components.
These are required to correctly read an open data base, like the windows registry.

There is a VSHADOW.exe in windows SDK, i guess redistributable ,
but there is also a simular vscsc on sourceforge.net.

Both create "good" shadow copies and have an option called "-exec=" to run a batch file
after creation of the shadow and before it's removale.

[wimb]

What do you use in WinNTSetup4 that allows to capture wim file from running Windows ?

[JFX]

I've written my own code, but creating a small vss.exe in purebasic will result in huge amount a false positives.
I'm still planing to make a tiny vsshelper application in C++, that will be required to get
WinNTSetup_x86.exe fully working inside Windows 10 ARM64.

[JFX]

Beta 2 is ready, should fix all mentioned problems.

[wimb]

6 hours ago, JFX said:

Beta 2 is ready, should fix all mentioned problems.

Perfect  - WinNTSetup4 is a very Powerful Program

   

 

Edited August 15, 2019 by wimb

[wimb]

You might consider to Add in the Download of WinNTSetup4 some useful Tools, so that they are ready to be used by the program:

- wimlib files libwim-15.dll
- BOOTICE v1.3.3.2
- some sample unattend.xml files for Unattended Install of Windows 10
- the slightly modified WimBootCompress.ini file as used in VHD_WIMBOOT
- some extra DiskPart scripts as given in VHD_WIMBOOT to make UEFI/MBR based portable SSD

Edited August 22, 2019 by wimb

[wimb]

I found a bug in WinNTSetup4 Beta 2

After launching WinNTSetup, then I can Load a previously Saved .ini file with Settings to overrule the default WinNTSetup.ini

It turns out that the Tweaks from that previously other saved .ini file are not taken into account to switch off tweaks, allthough the switch offs are present correctly in that saved .ini file.

Also the program WinNTSetup crashes when a wrong type of wim file like boot.wim is selected.
May be for the unexperienced user it is good to give WARNING - This WIM file is Not Valid as Installation file

Edited August 19, 2019 by wimb

[Sonic]

What condition / When " : ( " smiley is written in title bat of WinNTSetup ?

[ginzu]

Hi friends.

Win xp vhd I would like to ask you help with winntsetup.
My english is so bad, sorry.
Experiments on laptop and desktop computer.Real system.
Received errors are the same, no virus.
Laptop Toshiba 3gb ram, intel, host system windows 8.1x32.
Desktop computer 4 GB RAM, Intel, Host System Windows 7x32.
VHD for Windows XP 10 GB. Winntsetup version 3.9.4
Codes wimb's codes for winntsetup (winvblock.ima)
I tried various xp cd s. Xp integral -msdn-msdn + sata and modified.

The system is set up and powered on. Desktop screen comes. For example, integral and modified xp 's without installing anything, the second or third reboot, the blue screen comes.

Error:
PFN_LIST_CORRUPT
0x4E (0x99, 0x14D93, 0x3, 0x0)

msdn + sata works if I don't install any drivers. But if I install it, it gives the above error.
I checked the Sata-ahci settings. There's no solution.
Safe mode is always available (for all XP's.)
Only fully modified vista-xp works stably with drivers and programs (boot ntldr-xp, not vista)
I am surprised. I think a reg or patch file will solve the event.
Thanks in advance for your help.

info: I installed integral xp with winntsetup, next to win 7 on the local disk.
I've installed the full driver and program. Stable works smoothly.

[wimb]

For Install of XP in VHD

Download VHD_XP_Setup with Support Topic VHD_XP_Setup

 

[ginzu]

hi @wimb

I had a vhd made with ready-made VHD_XP_Setup.
It never opens. But it works in the virtual.
VHD_XP_Setup is very nice but does not remove the modified.A little more limited.

[JFX]

20 hours ago, Sonic said:

What condition / When " : ( " smiley is written in title bat of WinNTSetup ?

Smiley is for the secure boot state. Disabled, enabled or if no smiley the EFI does not support this "feature".

[Sergei Strelec]

JFX, Hello!

Thank you very much for the new version and additional features, it is very convenient 👍

I updated and slightly corrected the Russian translation

MD5 389671383CBD771F4E39B647024F5234

When one of the drivers is not installed in the program, an incomprehensible inscription appears.
Or maybe it's just me so displayed

Have a good day!

1049.dll

[JFX]

Thanks, It should now be fixed in Beta 3.

[Sergei Strelec]

JFX, good evening!
I conducted several tests, integrated 50 different drivers.
Now everything is working fine.
Thank you very much! 👍

Edited August 27, 2019 by Sergei Strelec