Discussion in 'Scripting' started by murphy78, Apr 2, 2014.
First show me a screen of what you already have accomplished?
ok i will show you all the screens with command lines later, now i am a little bit busy.
thank you for trying to help me, that's nice of you.
Halt your project please, just remembered for 8.1 we have to use 1.2.6, i am testing it as i write this, on a french 8.1 boot.wim (i did it years ago on my en-US and nl-NL base wims)
I re-figured it out
I have the original zip from Murphy78 but forgot the pw, so i rezipped my folders:
Actually you can follow Murphy78's own explanation at the OP but in short:
thank you for the reply, i've followed step by step all the new instructions with the 1.2.6 script described in your previous post and all went well, but unfortunately it didn't work at the end when booting from the iso.
when booting from the new iso created, the blue prompt command of the script 1.2.6 appeared indeed as you can see below :
But when i pressed "y" to use the script, instead of having the index menu, here's what i got :
So what's wrong ? something is clearly missing from the instructions you sent me, maybe a setting to add or something else but it doesn't work as you can see with the screens that i sent.
Another thing, you said in the instructions that i have to copy the folders "windows" and "murphy" but both of these folders are available into x86 folder and into x64 folder so if i choose to copy both folders from x64 folder into mount folder, when booting from the iso, you get an error message with the blue command prompt with the script saying "this version of x:\windows\system32\choice.exe is not compatible with the windows version running currently....."
On the other hand, if i choose to copy both folders from x86 folder into mount folder, it works well without any error message when booting from the the iso except that it's not the index menu that appears with the script but another menu as i showed you above with the screen.
Something else, when i copy both windows and murphy folders into mount folder, there is a mesage that appears saying "The destination already contains file called startnet.cmd, do you want to replace it ? or ignore it ?
i choose to replace it, that's what i had to do, right ?
here's what i can tell you about all this, i tried to be as clear as possible so that you can see if something is missing from your side or if i did something wrong from my side.
The x64 folders would be for x64 windows boot.wim index 2, x86 would be for x86 windows boot.wim index 2
Did you see my or murphy78's screens? The second screen you show is the script running gloriously
Press "F" for fast setup and you'll be able to setup your windows 7 install.
Oh god, it was obvious and i didn't pay attention to the menu, yes by pressing "F" , the index menu appeared and i was able to choose which version to install and all went well after that, the installation ended successfully so i can say that it worked like a charm
Thank you my friend for all your help, your are a great helper, there is no doubt about that and i would like to thank murphy as well for all his work here and for his great script.
i guess i could do the same method for win8.1 and win10.
if i'm correct, i would have to use the same script 1.2.6 to implement it in boot.wim from win8.1 install.esd and script 1.2.8 for win10 or maybe i could use the same script 1.2.6 for win10 as well.
Win 8.x and 10 can handle WIM/SWM/ESD by itself.
yes i know, what i meant is to implement the script into boot.wim to be able to benefit of all scripts' options as the option that can automatically detect whether the machine uses bios system or UEFI.
For 8.1 = 1.2.6
For 10 = 1.2.8 But the winrecfg cabs can only be integrated by DISM on 10240. Higher builds you need to unpack the cabs and put the files in the correct place by hand.
MUI = boot.wim\2\windows\system32\en-US\
EXE = boot.wim\2\windows\system32\
PS, if you leave the winpeshl.ini untouched it will start with the standard setup, when you use SHIFT+F10, a cmd screen opens and when you type "menu" it will start the script.
i don't know if i've alreday asked you this but what is the use of these winrecfg cabs files ?
Otherwise for winpeshl.ini file, i can simply edit it for win8.1 and win10 as i did previously with win7 install.esd into win8.1 iso so that the script opens automatically when booting from the win8.1 iso and win10 iso. don't you agree ?
If you don't want the standard setup, yes.
You didn't ask but i did tell what they would be for, for the recovery options. It's best to integrate them (keep in mind i am only a fan user of this script, and by trial and error i've learned most about it, + asking @murphy78)
ok i see, thank you again for all these information and for your help today, i've learnt a lot from this forum and i will certainly learn more in the next days.
By the way now i know where you are from, i don't know if you you did it by mistake but you mentionned about it in one of your previous posts so hurry up to remove these posts before someone finds out
I think many know where i am from but it didn't have anything to do with the discussion in the chat
i was only teasing you, but some forum members don't want to disclose any information about them for unknown reason.
You get the winre packages from the latest ADK that's compatible with the build of your boot.wim
For example, when using build 15063, you use the packages from the 15063 adk.
I could probably just include an older winre, but it would be a bad idea as the new versions may handle newer hardware differently.
first of all, i would like to thank you for this great script you created, i've tested it with enthousiast help and it worked great.
could you please send me winre packages for win10 1607 and win10 1703 versions ?
I didn't save the 1607 versions as I never use the script with older boot files, but here's the 1703 versions: http://mir.cr/03XBXWCN
You can just ignore or delete the fmapi versions if you're not also adding dart10 to your boot. I add them b/c it's more compressed to have the system add the files than to just copy them.
thank you my friend, @Enthousiast told me that winre cab fles for 1607 and 1703 versions must be unpacked and put manuelly in the right place (MUI fles in boot.wim\2\windows\system32\en-US\ and EXE files in boot.wim\2\windows\system32\
Do you confirm this ?
i downloaded the winre 1703 packages from the link you've just sent, i unpacked (unzip) cab files and found only 1 exe file which is winrecfg.exe but didn't found any MUI file.