Jump to content

JFX

Member
 View Profile  See their activity

  • Posts

    1,238

  • Joined

  • Days Won

    6

  • Donations

    0.00 USD 

 Content Type 

Posts posted by JFX

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    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?

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted · Edited by JFX

    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.

    WinCopy.gif

    5

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    11 hours ago, Antonino said:

    btw, have you modified any text files in the remove folder of this new edition?

    where do we get it from anyway?

    I do not see any link

    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.

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    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)
     

    3

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    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.

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    11 hours ago, Antonino said:

    so will those files be removed from across the whole volume, regardless of where they are found?

    Yes, it will scan the entire drive.
     

    11 hours ago, Antonino said:

    my second question was related to a group of system32 and syswow64 root files that I have to keep in order to let my favorite software still work after the miniwin deletions. so I was thinking of as many instances of !\windows\system32\filename.dll and !\windows\syswow64\filename.dll as my files to keep to be appended to system32-dll.txt and syswow.dll respectively. but just in case I place these strings elsewhere, in some other scripts, will they be effective, viz, will the files be kept where they are even if the instructions are not in the proper textfile? 

    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... 

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    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.

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    Found the VCRuntime dependencys.

    \Windows\System32\sxsstore.dll
    \Windows\System32\config\TxR

    Not so easy to track, if it's a folder which is required.

    MSI Afterburner shows an error messages when closing.
    But I'll will not add fix for this in default profile.

    \Windows\SysWOW64\taskschd.dll

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    Thanks for these files enuser2k :thumbup

    I have not done much with Windows 11, but the volume and calendar tray is working with classic taskbar using StartAllBack.

    MSI Afterburner needs the 2008 VCRuntimes (both x86 and x64).
    Seems I broke these installers, will be fixed.

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    16 minutes ago, click-click said:

    FYI  - Newer version of IMDisk available: 2.1.1 vs. 2.0.10

    Yes, but IMDisk 2.1.1 no longer supports unpatched Window7 (which include all Win7PE based WinPE and the Windows 7 WinRE).
    If you only use it on updated Windows 7, you can replace the 2 IMDisk files in Tools\imdisk.

    1

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted · Edited by JFX

    On 8/16/2022 at 4:18 AM, alacran said:

    By the way only fixed size VHDs are capable to Ramboot by means of grub4dos for UEFI + SVBus driver, unless there is new info I'm not aware.

    Last time I checked, SVBus was supporting dynamic VHDs. No RAM saving, but faster loading than fixed VHDs.
    Separate ESP partition does not make much sense here. It depends on Grub2 and this one can load a NTFS driver.


    Hope someone figures how to setup the native vhdramdiskboot from bootmgr.efi.
    If this one support differencing VHDs, I might get some interest in RAM booting again.

    As for your profile, nice one. You could get rid of this WUB, as Windows Update is removed in MinWin anyway.

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    Yeah, there i no wimboot switch, cause wimboot actually means a weeker compression form of xpress.

    Image_path is the name MS choose in imagex.exe

    Quote

     

    Captures a volume image from a drive to a new WIM file.

      image_path - The path to the volume image to be captured.
      image_file - The path of the new WIM file.
      image_name - The unique name for the image being captured.
      description - The text that provides additional reference information.

     

    As for your command line there is no equivalent to "--include-integrity" and you should set "-wimlib" to make sure you actually capture with wimlib and not wimgapi.

    WinNTSetup_x64.exe CAPTURE-CLI J:\ "D:\Wimboot\MinWin-10x64-LZX.wim" "MinWin-10x64-LZX_220803_044206" "MinWin LZX WIMBOOT IMAGE" -compress lzx -config wimscript.ini -wimlib

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    Normally Windows 10 systems above build 17000 don't need any WOF exclusion.

    But there were some reports that it don't work for some people (maybe hardware related).
    None of them told if they used BIOS or UEFI booting. This also makes a difference!
    EFI bootmgr has reading support for compressed files, BIOS bootmgr has not.

    You can set SkipBuildsAbove17000 in Tools\Compact\WimBootCompress.ini if you sure you don't have
    this problem with your machines.

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    There is bit more to translate now in:

    WinNTSetup 5.2.6

    - fixed Feeds did not got disabled on Windows 10
    - added log files wimgapi_error.log and wimlib_error.log
    - added VHD-DIFF option
    - added commandline option VHD-DIFF -file:{file} -parent:{file}
    - added commandline switch for VHD-CREATE -mbresp
    - added commandline switch for VHD-CREATE -vhdbootletter:{0|1}
    - added commandline switch for NT6 -vhdbootfiles:{0|1}
    - new commandline switch -syspart and -tempdrive support VHD(X) files
    - workaround: added AMD's Shadercache to wimscript exclusion (buggy SecurityDescriptors)
     

    3

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    1 hour ago, alacran said:

    --recover-data parameter emulates the way Dism works during apply.

    No, --recover-data ignores data corruption. That's not something that should be simply ignored.
    Wimlib has an error output. Don't know why I have not add this. Will be available in next version.

    BTW: DISABLE_INTEGRITY_CHECKS is useless in BCD loadoptions.

    0

    WinNTSetup v5.3.5

    in Install Windows from USB

    Posted

    Yeah, I guess this is the problem. You change the system disk to be a RAMDisk,
    Windows reacts like this is a full hardware change and will need same SysWoW64 files to be signed.

    You can edit Tools\CATTrim.ini and add the lines: 

    ..\SysWOW64\basesrv.dll
..\SysWOW64\bcryptprimitives.dll
..\SysWOW64\csrsrv.dll
..\SysWOW64\ntdll.dll
..\SysWOW64\kernel32.dll
..\SysWOW64\kernelbase.dll
..\SysWOW64\gdi32.dll
..\SysWOW64\gdi32full.dll
..\SysWOW64\ucrtbase.dll
..\SysWOW64\winsrv.dll
..\SysWOW64\win32u.dll
..\SysWOW64\normaliz.dll
..\SysWOW64\advapi32.dll
..\SysWOW64\bcryptprimitives.dll
..\SysWOW64\cfgmgr32.dll
..\SysWOW64\clbcatq.dll
..\SysWOW64\combase.dll
..\SysWOW64\comctl32.dll
..\SysWOW64\coml2.dll
..\SysWOW64\crypt32.dll
..\SysWOW64\cryptbase.dll

    BTW: there is a newer SVBUS available.

    1
×
×
  • Create New...