Jump to content

JFX

Member
  • Posts

    1,043
  • Joined

  • Last visited

  • Days Won

    6
  • Donations

    $0.00 
  • Country

    Germany

JFX last won the day on October 25

JFX had the most liked content!

About JFX

Profile Information

  • OS
    Windows 10 x64

Recent Profile Visitors

18,985 profile views

JFX's Achievements

282

Reputation

  1. Hi sakatgg, this seems to be a bug with the MUI file cleaning. I'll fix it.
  2. Your right, bcdboot.exe call fails with volume path. Bcdedit.exe does accept a path stating with "\\?\Volume{.." , but bcdboot.exe wants "Volume{...".
  3. @bapt Why not create your own DriveTypeCategorizer, you can get an example on how to do this in ExplorerPatcher source. Better invest 10 min once instead of asking every couple of weeks.
  4. No, there no way to bypass. In your 500GB source partition there must be at least 1 cluster that's located beyond 250 GB offset. However, this error message needs to be improved, it should display the needed space. BTW: I't might be possible for some defragment tool, to move all used data to beginning of the drive.
  5. I'll add this to "unattend\Win7-11-Select.xml" in next release: <?xml version="1.0" encoding="utf-8"?> <!-- [WinNTSetup] process=1 ;process 1 - asks for user input and replaces all 4 %variables% ;process 2 - don't ask and only replaces %WinNTSetup-Arch% ;WinNTSetup-Arch ;WinNTSetup-User ;WinNTSetup-PC ;WinNTSetup-Group --> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="specialize"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <ComputerName>%WinNTSetup-PC%</ComputerName> </component> <component name="Microsoft-Windows-UnattendedJoin" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Identification> <JoinWorkgroup>%WinNTSetup-Group%</JoinWorkgroup> </Identification> </component> </settings> <settings pass="oobeSystem"> <component name="Microsoft-Windows-Shell-Setup" processorArchitecture="%WinNTSetup-Arch%" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="NonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UserAccounts> <LocalAccounts> <LocalAccount wcm:action="add"> <Name>%WinNTSetup-User%</Name> <Group>Administrators</Group> <Password> <PlainText>true</PlainText> <Value /> </Password> </LocalAccount> </LocalAccounts> <AdministratorPassword> <Value /> </AdministratorPassword> </UserAccounts> <AutoLogon> <Password> <Value /> </Password> <Enabled>true</Enabled> <LogonCount>1</LogonCount> <Username>%WinNTSetup-User%</Username> </AutoLogon> <OOBE> <NetworkLocation>Home</NetworkLocation> <HideEULAPage>true</HideEULAPage> <HideWirelessSetupInOOBE>true</HideWirelessSetupInOOBE> <SkipMachineOOBE>true</SkipMachineOOBE> <SkipUserOOBE>true</SkipUserOOBE> </OOBE> <FirstLogonCommands> <SynchronousCommand wcm:action="add"> <CommandLine>net accounts /maxpwage:unlimited</CommandLine> <Order>1</Order> </SynchronousCommand> </FirstLogonCommands> </component> </settings> </unattend>
  6. Thanks for the translation. You can force dark theme in WinNTSetup.ini. [Options] DarkMode=1 Same goes to BootICE and Tools\x64\BootICE\BootICE.ini. Seems my last fix disabled that option in BootICE.ini. So you will need Beta2 to have it work. I'm not sure about 3 and 4, but couldn't you do that with $OEM$ and SetupComplete.cmd?
  7. WinCopy will create a copy of windows installation. For example, move the current installation into a VHD. The first 6 modes are using wimlib (with optional WOF compression). It's like capture and apply without actually creating a WIM file. File exclusion using a WimScript.ini are possible as well using MinWin by clicking on the Mode label. The VOLUME COPY option is more like Drive SnapShot, it copies the entire NTFS File System (used clusters only). It's much faster than the other modes, but does not offer any options. Destination drive can be smaller as the source drive, but the last used cluster must fit in it.
  8. Yes, there are some changes to the default minwin profile. Properly best if you compare old and new profile folder with something like WinDiff or WinMerge. Mega and Mediafire link at the end of the first post.
  9. WinNTSetup 5.3 Beta 1 - compiler updated to PureBasic 6.00 C-Backend - updated wimlib to version 1.13.6 - right-click on apply mode combo opens Tools\Compact\WimBootCompress.ini - fixed errors with native 4K drives - fixed VSS error not displayed - fixed Bootice Mod always starts in darkmode - added commandline switch for VHD-CREATE -uuid:{UUID} (simular to VBoxManage internalcommands sethduuid) - added WinCopy option (copy Windows from one partition to another) - added WinCopy and WinCopy-CLI command line - changed wimlib is the default compression engine - MinWin: support inline comments (//) - MinWin: grant full admin access to files - MinWin: fixed VCRuntime 2008 installer needs sxsstore.dll and config\TxR - MinWin: fixed diskpart shrink needs defragproxy.dll - RegImport: added support for [?HKEY_LOCAL_MACHINE\...] (only processed if key exists)
  10. There is no noticeable difference in speed between the 2. WIMBoot is the most space saving option, that's all.
  11. What does the part of adding drivers actually do to the operating system?

    I install the operating system in the vhdx file, and then start it through Ventoy. It can be used normally, but when I use Hyper-V and start the Vhdx system, Ventoy cannot be started again.
    I suspect the drive program has changed!

     

    So, I want to know what Windows NT Setup actually does to the operating system when it adds drivers?

    1. JFX

      JFX

      Actually it does nothing, WinNTSetup only uses DISMAddDriver function from dismapi.dll.

  12. Well, you will have a stand alone VHD WIMBoot Windows, that can be easily use in a Virtual Machine. Normal WIMBoot mode will have you to copy WIM file to a NTFS partition before. It was quite useful for me, example for P2V copies, however up coming beta version will have a better option for this scenario.
  13. The name does not matter, just add a .txt file to \Tools\MinWin\Default\Remove folder. There is nothing hard coded, profile should be entirely under control of the user.
  14. Yes, it will scan the entire drive. Name of the *.txt file does not matter. Best to create a new "MySoftware.txt" that contains the whitelist or this specific software. About custom_command.cmd in win_reduce_trusted you only get the driveletter as %WorkDrive%. There could be added much more information...
  15. Hi Antonino, a line like "\*.kyk" will remove all files that match *.kyk and are not part of any whitelist. As for custom_command, no currently there are none. Give me some examples, so I know what these commands need. I mean I can add needed environment variables like %tempdrive%, %minwinprofile% or %OSBuild% before execute them commands.


×
×
  • Create New...