Jump to content

Guimenez

Member
  • Posts

    91
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    Russian Federation

Posts posted by Guimenez

  1. On 8/1/2019 at 12:17 PM, click-click said:

    I'm not sure if what I am asking is possible, but I would like to create a recovery flash drive that will boot on
    PCs that have either UEFI or legacy set in the BIOS. I currently have a recovery flash that I created with WinNTSetup
    that has W10 installed in a VHD. The system boots and runs well if the hardware BIOS is set for legacy. The other
    day I tried to boot from a laptop that was set up for UEFI and the flash gets ignored and there is no way to boot it
    unless I go into the BIOS and set it to legacy. Not all BIOS implementations allow a legacy mode, so is there a way to
    avoid having to create 2 flash recovery drives to accommodate both modes?

    I have a working 100% UEFI+CSM Flash drive.

    Create 2 partitions. 1st with big size in NTFS with bootsect nt60 (activate the partition) and 2nd in fat32 with 1gb in FAT32 with bootsect nt60(doesn't need activation) too.

    Now create a WINPE and edit with your choices and menus. I've made 2 WINPE. 1 with menu for formatting and installing all windows version(XP to 10) in CSM mode ( normal partitions) and another with menus of formatting and installing windows 8.1 and 10 with UEFI partitions. 

    You will have some work but it will work flawless with this perfect tool WinNTSsetup

  2. On 14/01/2017 at 6:27 PM, Atari800XL said:

    Guimenez, there are other sites that explain how to do that, but even then:

    I would not advise to make updated iso/wim/esd files anymore. Here are my reasons:

    (1) For windows 10, there are only 3 updates you need, wether you install from an "old" or a "new/ updated" iso. You only need the latest Cumulative Update, one other update, and maybe Flash update. In the old days, an "old" source file would need more updates than a newer source, but with Cumulative updates, that's a thing of the past.

    (2) Better wait for next week anyway: There will be a new "Windows 10 1607.1" esd directly from microsoft. So that's version 1607 (july 2016), "with update".

    Thanks.

    I've made some changes to my Batch files so, the only thing i need to do it's download the new iso from microsoft :D

  3. 6 hours ago, LinksysRouter said:

    Hi, I've been a long time user of winntsetup and love it (I even wrote a wrapper gui to dumb it down a bit for people who use my pe environment).

    One problem I have is that I have found it *impossible* to have vista install as C:\ correctly. Even setting the command line option for the setup letter, it still installs itself as D drive, which is unacceptable as it breaks a lot of programs that assume C:\ is the system drive.

    Is there a way to force vista to install as C:\? At the moment, I have basically said that the pe is incompatible with vista to get around this, and to use the vista setup instead.

    I've the same problem with Vista :(

  4. Hi,

    i found a problem with my script, maybe someone can help me.

    When i'm on Winpe i must set Windows HDD to T: because When my disks doesn't have partitions, my pendrive is C:

    But after installing, my windows is installed on T: and not C:.

    This is my script:

     

    %usb%\winntsetup\WinNTSetup_x64.exe NT6 -source:l:\sources\install.wim -WimIndex:1 -syspart:S: -tempdrive:T: -Sysletter:T -setup -reboot

     

    Thanks

  5. I'm taking 30 minutes to backup a new installed machine with dism.

    Is there any other software I can use to backup?

    I like savepart but I can make it run in winpe. Maybe I'm missing any optional package :(

  6. Good :), in some cases the issue might be actually memory related, but with 4 Gb of RAM it is not possible.

     

    Clearly it is a resource limit of some kind, the "root" cause of similar errors has been reported in the past to be connected with the "driver packs" when they are "integrated", but this should be not your case since you use them as "external" resource. :unsure:

     

    jaclaz

    The strange it's the same massstorage driverpack work flawless in XP Home, and the problem it's not the ISO because if i use that iso in the perfect tool too, Easy2Boot that inject the driver too, it works well

  7. AFAIK  XP does not boot from UEFI systems. So why would you want to UEFI-boot to install XP?

    Sorry, i explain me wrong.

    I'm making about 20 installation in one day, some are UEFI and another CSM.

    But i've one pendrive with 128GB and i want to put everything there.

    I will not install XP in UEFI mode (it's not possible), but i want use the same pendrive in any computer that i repair.

    Hope you understand me now :D

  8. You might like to also check out WinSetupFromUSB and Easy2Boot which can install 32-bit XP from an unmodified XP install ISO. It automatically adds the correct SRS Mass Storage Driver. No need to modify the ISO or add SRS drivers yourself.

    Not as versatile as WinNTSetup, of course!

    I'm using Easy2Boot, but because of UEFI, and Easy2Boot it's a little bit complicated when working with that, i'm making my WinPE that will install both, i hope.

    But thanks for sharing 

  9.  

    But it will inject the drivers in textmode to work after reboot to recognize sata?

    Yes, the MSSTMake tool will scan the complete folder tree for Sata drivers and WinNTSetup will merge it's output into the new install.

     

    There are only a few sata drivers that doesn't work with that method. I plan to address these in Version 4.

     

    It just works perfect!!!

    Man, congratulation for you software, it's amazing the things we can do with it :D

    Now i've a WinPE with all windows version to install on any pc :D

    Now i will try to find a way to have WinPE working in CSM and UEFI mode at the same time!!

     

    Thank you once again for your amazing software.

  10. The driverpacks need to decompressed to let's say D:\Drivers.

     

    %usb%\WinntSetup\WinNTSetup_x86.exe NT5 -source:l:\ -syspart:C: -tempdrive:c: -setup -reboot -drivers:D:\Drivers

    Thanks,

    I will decompress the masstorage drivers to my USB and then use this command that i've tried but without decompressed drivers.

    i will use this:

     

    %usb%\WinntSetup\WinNTSetup_x86.exe NT5 -source:l:\ -syspart:C: -tempdrive:c: -setup -reboot -drivers:%usb%\Drivers

     

    But it will inject the drivers in textmode to work after reboot to recognize sata?

     

    thanks

  11. Good to hear it works now.

     

    I'm no expert about GPT, but maybe this diskpart options should hide the volume

    rem telling Windows this volume is the WinRE location

    set id="de94bba4-06d1-4d40-a16a-bfd50179d6ac"

     

    if it still not helps, maybe also use this on your recovery volume

    rem telling Windows to not assign a drive letter by default

    gpt attributes=0x8000000000000000

    Just want to thank you for all the help and such a great tool.

    The code to hide is this: gpt attributes=0x8000000000000001

  12.  

    First of all, congratulations for this nice tool :D

     

    I'm creating UEFI partitions with diskpart then format C: drive and then i use this tool to restore the WIM to C:.

    After rebooting, the Windows doesn't start given boot error :(

    If i create the same partitions, but next install with normal setup and then there format C:, after reboot it start Windows.

    Does anyone know what can be? i know that GPT partitions doesn't have boot flag, so i don't know what is happening :(

    Thank you

    Could you give more detail about what error is shown.

     

    You diskpart option are correct.

    In WinNTSetup the boot partition should be auto selected to S: and all icons should be green.

     

    I just to thank you again,

    it works flawless with S: :D

     

    I've created a Recovery Partition, Is there any way to hide before first Windows Startup?

    If i use diskpart on WinPE it only hide on WinPE, but i want to hide in Real Windows.

    thank you

  13. First of all, congratulations for this nice tool :D

     

    I'm creating UEFI partitions with diskpart then format C: drive and then i use this tool to restore the WIM to C:.

    After rebooting, the Windows doesn't start given boot error :(

    If i create the same partitions, but next install with normal setup and then there format C:, after reboot it start Windows.

    Does anyone know what can be? i know that GPT partitions doesn't have boot flag, so i don't know what is happening :(

    Thank you

    Could you give more detail about what error is shown.

     

    You diskpart option are correct.

    In WinNTSetup the boot partition should be auto selected to S: and all icons should be green.

    Thank you for your reply.

    My boot partition was wrong, i was choosen C:

    Tomorrow i will try it out.

    Thank you :)

  14.  

    Thanks for replying,

    i have that partition, it's called System.

    Do i need to copy the files to that partition?

    If so, can you tell me what are the files?

    Well it is a bit more complex than simply copying a few files.

    The default (or "failover") EFI boot files are:

    \efi\boot\bootia32.efi <- for 32 bit UEFI

    \efi\boot\bootx64.efi <- for 64 bit UEFI

    For windows you will need to get from the install .wim the file \source\bootmgrfw.efi (but then there are all the "localized" files or get it and all the other files from the installed system, usually C:\Windows\Boot\EFI\) and rename it to either bootia32.efi or bootx64.efi,

    BUT a normally installed windows will have that file as:

    \EFI\Microsoft\Boot\bootmgfw.efi

    then you will need to have (actually create) a (proper) BCD as \EFI\Microsoft\Boot\BCD, *like*:

    https://technet.microsoft.com/en-us/library/dn336950.aspx

    or:

    http://www.hasper.info/repair-a-destroyed-windows-7-uefi-boot-sector/

    And then you will need to add the boot entry to the NVRAM. How? :unsure:

    But that's where the BCDboot tool comes handy:

    https://technet.microsoft.com/en-us/library/dd744347(v=ws.10).aspx

    https://msdn.microsoft.com/en-us/library/hh824874.aspx

    jaclaz

     

    I didn't know that we need to make lots of thing just to boot to UEFI :(

    So, when i format with normal UEFI setup and install Windows on C: it will auto create everything like that?

    Well, i will try does batch files with bcdedit too.

    Thank you.

  15. Thanks for replying,

    i have that partition, it's called System.

    Do i need to copy the files to that partition?

    If so, can you tell me what are the files?

    Thanks

     

    This is my batch to create the partition:

     

    select disk 0
    clean
    convert gpt
    rem == 1. System partition ================================
    create partition efi size=100
    format quick fs=fat32 label="System"
    assign letter="S"
    rem == 2. Microsoft Reserved (MSR) partition ==============
    create partition msr size=16
    rem == 3. Create Windows partition ========================
    create partition primary size=100000 
    format quick fs=ntfs label="Windows"
    assign letter="C"
    rem == 4. Create Restore Partition ========================
    create partition primary size=20000 
    format quick fs=fat32
    rem == 5. Create Backup partition ========================= 
    create partition primary
    format quick fs=ntfs label="Backup"
    assign letter="W"
    list volume
    exit
  16. First of all, congratulations for this nice tool :D

     

    I'm creating UEFI partitions with diskpart then format C: drive and then i use this tool to restore the WIM to C:.

    After rebooting, the Windows doesn't start given boot error :(

    If i create the same partitions, but next install with normal setup and then there format C:, after reboot it start Windows.

    Does anyone know what can be? i know that GPT partitions doesn't have boot flag, so i don't know what is happening :(

    Thank you



×
×
  • Create New...