Jump to content

click-click

Member
  • Posts

    257
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Germany

Posts posted by click-click

  1. I would like to use WinNTSetup to install Win7 on a VHD that was defined for a VM in Oracle's VirtualBox. Is there a way to do this?

    If I mount the vhd on my local system, WinNTSeup wont' let me use the same drive letter for the boot drive. Seems like VBOX supports booting from a VHD.

  2. Thanks, I did stumble upon vhdtool and this is what I ended up doing to clone the WinNTSetup VHD creation
    because I need a different volume label than what WinNTSetup sets. Are these the correct commands to use?

    Also, do you know where I can find the vhdtool that includes the /repair option. I haven't been able to find it yet.
     

    vhdtool /create <filename> <size> /quiet
    select vdisk
    attach vdisk
    automount disable
    attributes disk clear readonly
    create partition primary
    online volume
    attributes volume clear readonly
    Active
    format
    assign
    
  3.  

    @JFX Do you use diskpart from WinNTSetup when creating a VHD with the instant creation option?

    When I run diskpart create vdisk file="d:\Win2Go ltsb.vhd" maximum=16384

    it takes longer than the  instant creation option via WinNTSetup although both VHDs seem to have the

    same properties and size. What commands do you use with the instant creation option?

    Thanks for any infos...

     

     

  4. The usb was formatted with the normal format and the rest was done by winntsetup which I used to created the VHD etc. I also let it updated the boot record (which may be the problem). The usb was clean before I started with WinNT.

  5. I recently wanted to created a bootable usb flash using a Win10 VHD. Everything works fine with WinNT (3.8.7.4), but
    for some reason the BCD is created with 2 VHD entries with the same name. The 2nd entry's partition and device
    are unknown and boots but eventually fails indicating system needs to be reinstalled. The 1st entry boots fine.
    I'm not sure what the 2nd entry is for and I deleted it with Bootice so the correct entry is used. Any idea why the
    2nd entry is created?

     

    WinNTSetup.log

  6. On 6/14/2017 at 7:57 PM, JFX said:

    It are just the offset inside the ISO like jaclaz explained.

    I've made tool for that:

    ISO2Offset.7z

    I wanted to test this using en_Win10_1709_multi_dec_x86_dvd_100406359.iso to see what the offset was for the install.wim, but nothing gets listed just specifying install.wim. If I leave the [file] blank, I get the following:

    	[README.TXT]
    Range=51200-51334
    	[[BOOT]\1-Boot-NoEmul.img]
    Range=1064960-1069055
    	[[BOOT]\2-Boot-NoEmul.img]
    Range=1069056-1069567 

    How does one specify the [file] in the iso to get it's range, or is iso2offset only for the ADK?

    I don't have the ADK downloaded so I can't get a list of any offsets from that.

  7. Thanks.. I'm not sure what to do with the cab files. Will the msi know what to do with them?

    I could not get the adksetup.exe to work for me. I only selected  Application Compatibility Tools and the download would always fail. I finally figured out that I needed  the 1607 version (10.1.14393 ) of the adksetup.exe for it to work.

    Edit: I ran the msi from your link and that was enough for what I needed to do. I used the Compatability Adminstrator from the installed toolkit to unblock the Power Manager setup.exe so I could see if the app still works on W10 and it does.:cool:

  8. On 10/12/2017 at 3:21 PM, JFX said:

     

    Can this tool be used to get only the Application Compatibility Toolkit (ACT)) from the ADK?

    I have a program (Lenovo Power Manager) that I want to install but it is blocked for W10, I understand it can be unblocked

    with ACT, but I don't really want to install the ADK just to get this component. What would I need to enter using

    GWT -range

  9. On 6/13/2017 at 5:13 PM, JFX said:

    Have added command line support for range downloads.

    
    GWT -range:8808448-9236127 -out:"X:\bootmgr" -title:"Download Win8.1 Bootmgr" -link:/download/B/9/9/B999286E-0A47-406D-8B3D-5B5AD7373A4A/9600.16384.WINBLUE_RTM.130821-1623_X86FRE_ENTERPRISE_EVAL_EN-US-IRM_CENA_X86FREE_EN-US_DV5.ISO

    GetWaikTools.zip

    The exe file sizes  from this link are much smaller than the ones downloaded using the link on page 1. Are these the same versions compiled differently?

  10. Is VHDX also supported by WinNTSetup when installing W8.1 and W10 to a vhd and will WinNTSetup create it for me? The reason I ask is that VHDX supports trim and VHD doesn't. Using  a VHDX would allow me to use a USB3 attached SSD for installing W8.1 or W10.

  11. On 5/31/2017 at 6:22 AM, Atari800XL said:

    Very interesting... Thanks again for testing. Hope we can find out why your first attempt didn't work (JFX?)

    At least your test confirms it can work in WinNTSetup, so I can still suggest this solution to others (forced w10 driver updates are a big problem for some, specially on older hardware).

    I'm not sure it confirms anything now. I just did a new clean install as before using the tweak via WinNTSetup and this is what I am seeing below. The only difference I  can make out is that this time I was connnected to the network after the final install reboot. Drivers for my Ethernet  are already included and I happened to be on my docking station which has an Ethernet connection. I checked the registry and it agrees with the tweak.  The interesting thing is that the event viewer shows a lot of warnings: Access to drivers on Windows Update was blocked by policy, but somehow WU ended up offering the drivers anyway.

    WU.png

  12. okay, letting WinNTSetup run the SearchOrderConfig tweak is working now for me too. When applied with WinNTSetup, the tweak tends to influence WU differently than at the point when I applied it. Before, I set  the tweak via a remote registry edit after WinNTSetup had finished installing the image. Seems like either way should have worked. I don't know why my test did not work since I checked the registry after booting to make sure my remote edit was there.

  13. Thanks, I tried that, but when I select check for updates, I get about 8-10 driver offers for my Thinkpad. So far, breaking the driver check with -wuuhext.dl is the only thing that worked for me, but I'm not sure what ramifications doing this on my system will have. Setting SearchOrderConfig doesn't seem to be enough.

×
×
  • Create New...