Windows 10 Recovery Tools - Bootable Rescue Disk

  1. Kyhi's Avatar
    Posts : 3,566
    Windows 3.1 to Windows 10
    Thread Starter
       #1191

    you need to have the x86 boot.wim in the Winpese_Multi\x86\Sources folder
    and the x64 boot.wim in the Winpese_Multi\x64\Sources folder...

    Although the program should tell you if not present...

    Can you explain how you are using the process and explain or screen shot the error message??
      My Computer

  2. alr tech's Avatar
    Posts : 14
    Windows 10 Home
       #1192

    Hi again

    yes, like is explain I copy the files one for each source directory...
    (your zip files creates the main dir estructure)
    then I run the script in an administrator window..
    and like you can see it makes the copy, and try to create the new ISO file...
    attention i don't create the output directory, so I suppose that the script can make them....
    Windows 10 Recovery Tools - Bootable Rescue Disk-err_3.jpg

    I hope this is the proper way to send the file...
    tanks
      My Computer

  3. lx07's Avatar
    Posts : 5,479
    2004
       #1193

    alr tech said:
    attention i don't create the output directory, so I suppose that the script can make them....
    Sorry to interject but @Kyhi is offline.

    At the end of your path is "/01.iso". You can't have a "/" in a file name. It isn't clear if you want the file name to be "01.ISO" or "WinPESE_x86_x64_181/01.iso". Anyway it looks wrong. You can swap "/" and "\" interchangeably in the path (afaik) but can't include them in the file name.

    Try it without the "/" and if that doesn't work try creating directory "D:\varios\Toni\etc etc" as error 3 means "path not found"

    Note also that OSCDIMG will also fail with error 3 if D is formatted ReFS (see here). Something to think about if it still doesn't work but looks more like the file name is invalid.
      My Computer

  4. alr tech's Avatar
    Posts : 14
    Windows 10 Home
       #1194

    Tanks Lx07

    The D drive is formated in NTSF...
    but good point... it may be a typo in the script...
    I believe that it was Kyhi that make it...
    a will try to change it...
    and lets see...
    hum... it isn't... it look likes more a wrong use of char table... maybe different compiling win versions...

    the file "ModifyWinPESE.cmd" have the culprit line :
    %Oscdimg% -bootdata:2#p0,e,b%Etfsboot%#pEF,e,b%Efisys% -h -m -o -u1 -udfver102 -lWinPESE_x86_x64 "%~dp0WinPESE_Multi" "%~dp0WinPESE_x86_x64_%dtStamp%.iso"

    and to be more exactly with the variable 'dtStamp' that receive the actual date
    the value of this variable changes along the script
    so it's what I understand... the system functions that return day-Month-year are returning wrong values.
    the 'set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%' must be change in my system...

    for a try I will change the var with a date...
    Done...
    That's it ... now with the changes it creates the ISO file properly...
    so if anyone knows how to change...
    in my system if i input in a DOS window echo dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    I will get : dtstamp=04/01/2018

    and running the script I will get error again because of the "/". In your language it outputs with a "." so there's no problem...
    so its a system char problem..? does anyone knows how to change the code?
    tanks
    Last edited by alr tech; 04 Jan 2018 at 11:23. Reason: writing errors
      My Computer

  5. lx07's Avatar
    Posts : 5,479
    2004
       #1195

    The ModifyWinPESE.cmd has this
    Code:
    set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    If I try it in cmd prompt it looks not correct (18an18) but this could be my lack of understanding of how batch files work or date formats or anything. I don't know.

    Code:
    C:\WINDOWS\system32>set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    
    C:\WINDOWS\system32>echo %dtStamp%
    18an18
    
    C:\WINDOWS\system32>
    I'd just hard code the ISO name until Kyhi or someone who knows batch files can respond.

    Something like
    Code:
    %Oscdimg% -bootdata:2#p0,e,b%Etfsboot%#pEF,e,b%Efisys% -h -m -o -u1 -udfver102 -lWinPESE_x86_x64 "%~dp0WinPESE_Multi" "%~dp0WinPESE_x86_x64_TEST.iso"
    or perhaps just
    Code:
    set dtStamp=TEST
      My Computer

  6. Kbird's Avatar
    Posts : 2,202
    Win10 202H
       #1196

    lx07 said:
    The ModifyWinPESE.cmd has this
    Code:
    set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    If I try it in cmd prompt it looks not correct (18an18) but this could be my lack of understanding of how batch files work or date formats or anything. I don't know.

    Code:
    C:\WINDOWS\system32>set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    
    C:\WINDOWS\system32>echo %dtStamp%
    18an18
    
    C:\WINDOWS\system32>
    I'd just hard code the ISO name until someone Kyhi or who knows batch files can respond.

    Something like
    Code:
    %Oscdimg% -bootdata:2#p0,e,b%Etfsboot%#pEF,e,b%Efisys% -h -m -o -u1 -udfver102 -lWinPESE_x86 "%~dp0WinPESE_x86" "%~dp0WinPESE_X86_TEST.iso"
    Looks like it doesn't work so well if not using US English Date Format of year-month-day

    Echo %dtstamp% should return 180104 today ............. if set using the "set dtstamp" line above 1st

    *** note there is no / or . in the Date

    Edit : I just set my system date to the day-month-year short setting and I get the same error as LX07 ie 18an18
    so try setting your Date to the US method of year-month-day and see if it helps....



    KB
      My Computers

  7. Kyhi's Avatar
    Posts : 3,566
    Windows 3.1 to Windows 10
    Thread Starter
       #1197

    at the very end of batch file you will see the date stamp code info saved

    Windows 10 Recovery Tools - Bootable Rescue Disk-screenshot00002.png


    Code:
    set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%
    Code:
    %Oscdimg% -bootdata:2#p0,e,b%Etfsboot%#pEF,e,b%Efisys% -h -m -o -u1 -udfver102 -lWinPESE_x86_x64 "%~dp0WinPESE_Multi" "%~dp0WinPESE_x86_x64_%dtStamp%.iso"
    or remove datestamp from iso name

    Code:
    %Oscdimg% -bootdata:2#p0,e,b%Etfsboot%#pEF,e,b%Efisys% -h -m -o -u1 -udfver102 -lWinPESE_x86_x64 "%~dp0WinPESE_Multi" "%~dp0WinPESE_x86_x64.iso"
      My Computer

  8. alr tech's Avatar
    Posts : 14
    Windows 10 Home
       #1198

    Hi
    yes, i Believe the same...
    i try changing the script too...
    and I get the proper ISO that I will test... to see if it works properly...
    I began working in changing the script putting more code for validating the system, code page... but it will take time...
    for now I will just make a few adjustments, just set dtStamp="Jan2017"
    tanks for now
    :)
      My Computer

  9. Kbird's Avatar
    Posts : 2,202
    Win10 202H
       #1199

    Instead of this line :

    Code:

    set dtStamp=%date:~-2%%date:~4,2%%date:~7,2%

    Try this , which should just use the Local Computer Date I believe, when you echo %dtstamp% on the command line

    Code:

    set dtStamp=%date%
      My Computers

  10. Ztruker's Avatar
    Posts : 13,521
    Windows 10 Pro X64 20H4 19042.928
       #1200

    On my system, echo %date% yields Fri 01/05/2018.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 20:21.
Find Us




Windows 10 Forums