MistyPE - Windows 10 PE
#26
Posted 25 March 2017 - 06:37 PM
MistyPE using Windows 10.0.14393 source. All programs included in the project were included in the builds if supported (a number were omited in the 64-bit build without SysWoW64 support). The Windows source files were already cached - as were all programs.
64-bit (SysWoW64)
Build time = 3 minutes 13 seconds
boot.wim file size = 458 MiB
64-bit
Build time = 1 minutes 26 seconds
boot.wim file size = 331 MiB
32-bit
Build time = 2 minutes 15 seconds
boot.wim file size = 327 MiB
A significant part of the build time is the injection of files to boot.wim. In the 64-bit build without SysWoW there were significantly fewer files to inject as a number of sizable 32-bit programs were omitted (including FTK Imager).
Included Programs
7-ZIP
AccessGain
AIDA64 (ommited from 64-bit without SysWoW64 support)
AmmyAdmin (ommited from 64-bit without SysWoW64 support)
CloneDisk
dd (ommited from 64-bit without SysWoW64 support)
Defraggler
DISK.MANAGEMENT
DMDE (ommited from 64-bit without SysWoW64 support)
DriveImageXML (ommited from 64-bit without SysWoW64 support)
Eraser (ommited from 64-bit without SysWoW64 support)
GHOST
HWiNFO
ImDisk
JkDefrag
LinuxReader (ommited from 64-bit without SysWoW64 support)
MWSnap (ommited from 64-bit without SysWoW64 support)
NTPasswordEdit
Opera
PartitionGuru
Recuva
DriveSnapshot
SumatraPDF
TinyHexer (ommited from 64-bit without SysWoW64 support)
TrueCrypt (ommited from 64-bit without SysWoW64 support)
FreeVK (ommited from 64-bit without SysWoW64 support)
WinHex (ommited from 64-bit without SysWoW64 support)
FAU
FTKImager
X-Way.Forensics
- r3boot3d likes this
#27
Posted 26 March 2017 - 01:15 AM
I'd say no as 10.0.15063.x would need new PE tools or dump PE directly from official boot.wim which doesn't exist as far I've looked only WinRE is available from fast ring.
o I take it back... Just did some re-checking at slow ring.. Seems there is RS2 PE out now..
#28
Posted 26 March 2017 - 02:54 AM
Hey Misty,
In the "Quick Start" and in the more detailed "Instructions" section it shows the same pic regarding setting the "SourcePath" in Winbuilder. but neither place discusses the (2) Items under the Source Path section. Is there any caveots to leaving them blank and possibly some other aspect of the program will auto-fill them in when you come to that section or should they be filled in initially when doing the source path? (or does it make a diff)
Not trying to be a pain but, sometimes not doing something one way versus another in that program can cause an irritating hitch in your giddiup from then on. (don't ask me how I know. ha)
thanks, Im glad the interest in your stuff has perked up
Edited by michaeltheclyde, 26 March 2017 - 03:08 AM.
#29
Posted 26 March 2017 - 03:16 AM
Hey again,
I noticed you advised (on page 1) for a mounted .iso as source in Win 10. Does that apply to 3, 3.1, 4 etc ... and is it always best to use a mounted .iso?
thanks
#30
Posted 26 March 2017 - 05:59 AM
The two boxes can be used to set the %TargetDIr% and %ISOFile% variable in projects, however in MistyPE these boxes are not used. The %ISOFile% variable is not used at all, and the %TargetDir% variable is defined in the main project script - this will overide the settings in %TargetDir% box in the the WinBuilder SourcePath section....In the "Quick Start" and in the more detailed "Instructions" section it shows the same pic regarding setting the "SourcePath" in Winbuilder. but neither place discusses the (2) Items under the Source Path section. Is there any caveots to leaving them blank and possibly some other aspect of the program will auto-fill them in when you come to that section or should they be filled in initially when doing the source path? (or does it make a diff)...
Variable in the main project script include -
%TargetDir%=%BaseDir%\MistyPE.Project.Output\ROOT %ISODir%=%BaseDir%\MistyPE.Project.Output.
The reason I suggest a mounted .iso is due to there being less change of missing source files. If an .iso file contents is fully extracted to a local directory or network share then this is equally suitable.I noticed you advised (on page 1) for a mounted .iso as source in Win 10. Does that apply to 3, 3.1, 4 etc ... and is it always best to use a mounted .iso?
If using the Tools > Cache Files script then other sources can be used. Option 1 for example can be used to specify a WinPE .wim file (e.g. boot.wim from RTM source, WinRE.wim, winpe.wim (from ADK), etc) and a source .wim file (e.g. install.wim). This is useful to create a cache using an ADK build with added packages (Optional Components) or WinRE.
Misty
#31
Posted 26 March 2017 - 06:02 AM
Thanks for the information. To be honest I usually avoid the Windows 10 builds until official release (e.g. November Update, Anniversary Update). I might give the 15063 build a try later - time permitting.o I take it back... Just did some re-checking at slow ring.. Seems there is RS2 PE out now..
Misty
Edit - forget what I said about build 15063. The most recent .iso download I can access is build 15058.
#32
Posted 26 March 2017 - 07:11 AM
Misty,
15063 would be better than most builds below it
15063 Enterprise 32bit and 64bit corrects 2 major issues, they fixed a reliability issue from Build 15061 where in M$ Edge would hang hard and be as cold and unresponsive as my last ex-wife
They also fixed at least 1 issue for the Club where most all (if not all) of the localized files and registry keys associated with any additional language packs on the system would be gone/dissapear/not installed after enabling .NOT (needed) Framework 3.5.
I never experienced it since I have a hard enough time with southern slang by itself.
check your messages
#33
Posted 26 March 2017 - 10:16 AM
Hello Mr. Misty,
very nice project indeed and though I'm using the 20170308 version (the update script or full download of 0324 doesn't work until 1th April I guess) & I managed to produce a fine WinPE Wow64 enabled iso on my Win2003SP2 32bit test-machine (yeah)
As Source 10240.16384 DVD (re)install medium of Win10pro 64bit which came with a Dell laptop. Since MistyPE didn't work OOTB for me I had to apply some minor but mandatory changes to Core Files script..
- Had to insert
If,ExistFile,"%SourceDir%\sources\install.swm",Set,%install.wim%,"%SourceDir%\sources\install.swm",GLOBAL
at line 210 to get pass an error (install.wim not found) - option set boot.wim image number to 1
- other settings No|Default|x64|YES and no further changes besides the boot.wim image number
output: WinPE.iso of a whopping 577680KB
Hope my contribution can be of use ... it worked for me...
grtz Peter
Edited by PTAHDEL0H0, 26 March 2017 - 11:07 AM.
- misty likes this
#34
Posted 26 March 2017 - 03:14 PM
Thanks for the information. To be honest I usually avoid the Windows 10 builds until official release (e.g. November Update, Anniversary Update). I might give the 15063 build a try later - time permitting.
Misty
Edit - forget what I said about build 15063. The most recent .iso download I can access is build 15058.
Well, There's 2 variants of that Creators Edition and RTM. You can be sure 1703 15063 is gonna be public soon enough, if it's not already.
But yeah, might be better to just wait for official ADK to be out for version 1703.
#35
Posted 26 March 2017 - 03:19 PM
Misty,
15063 would be better than most builds below it
Well, to be honest those fixes none of them as far I looked doesn't apply to MistyPE, but agree with go with the newest when it comes down to windows working as it should, lol.
#36
Posted 26 March 2017 - 03:30 PM
- Atari800XL and r3boot3d like this
#37
Posted 26 March 2017 - 03:43 PM
---------------------------
Checksum information
---------------------------
Name: MistyPE.2017.03.24.zip
Size: 53584170 bytes (51 MB)
SHA1: 93495C71A0A8243B28A95C1970E624EE8C5FDE5A
#38
Posted 26 March 2017 - 04:16 PM
@misty
this is a good host
https://cloud.mail.ru/public/12S6/KJD6CLg8d Name: MistyPE.2017.03.24.zip Size: 53584170 bytes (51 MB) CRC32: D6F9F557 CRC64: 90559A5705349276 SHA256: B0BAAA587EEB9120654F2F5FB15CD2C065614FD7C08F0B6254CCB617A8A9FAFA SHA1: 93495C71A0A8243B28A95C1970E624EE8C5FDE5A BLAKE2sp: 8668A1832990F7869B9148AAAAA60D4E006C5837D5ADD71BD3E17878D66B4E97
- misty and genetix like this
#39
Posted 26 March 2017 - 05:48 PM
We believe that hosting should be accessible to all, and that's precisely why we offer free hosting for everyone. We even give you unmetered bandwidth and disk space allowing your site to grow without fear of ridiculously low limits like our other free hosting competitors! You won't find many companies doing that free of charge!
New domain - http://mistyrebootfiles.x10host.com/
I'm in the process of uploading files to create a mirror. The most recent MistyPE build (2017-03-24) has already been uploaded and the download portal has been updated.
This will be useful as a mirror or may become the main site.
Regards
Misty
- Atari800XL likes this
#40
Posted 26 March 2017 - 05:56 PM
A number of scripts (40+) have a 1 second delay built into them. Removing the delay from each script will reduce the build times............
64-bit (SysWoW64)
Build time = 3 minutes 13 seconds
boot.wim file size = 458 MiB
64-bit
Build time = 1 minutes 26 seconds
boot.wim file size = 331 MiB
32-bit
Build time = 2 minutes 15 seconds
boot.wim file size = 327 MiB.......
This could reduce the time quoted above for the 32-bit and 64-bit with SysWoW64 support build by over 40 seconds.
Misty
#41
Posted 26 March 2017 - 07:18 PM
03-24-2017 Built the Project with all apps folder selected.
I like the way it continues building the project, but lets you know that a file needs to be installed or required for a certain app.
Finished the build. booted on quemu.
Congrats!
#42
Posted 26 March 2017 - 07:42 PM
Thanks for the feedback. The project has come a long way since your first feedback in 2013! BTW, are you still using spaces in the path?
Misty
#43
Posted 26 March 2017 - 07:55 PM
oh! yeah! forgot. I meant to mention that.
Build directory with spaces.
C:\Users\UserName\Downloads\- Winbuilder\MistyPE - Windows 10 PE\MistyPE.2017.03.24\MistyPE
#44
Posted 27 March 2017 - 09:32 AM
Thanks for the feedback - it's nice to know the project works on Windows 2003 as I do not have a test environment for this version of Windows...very nice project indeed and though I'm using the 20170308 version (the update script or full download of 0324 doesn't work until 1th April I guess) & I managed to produce a fine WinPE Wow64 enabled iso on my Win2003SP2 32bit test-machine (yeah)...
I've not come across any .swm files as I usually use RTM (or equivant) source files. The contribution is definitely of use - thanks for the tip - I'll add this to the next release. The relevant code to search for install.wim and install.esd was moved to a hidden script in the current beta (\MistyPE\Core\verify.script).As Source 10240.16384 DVD (re)install medium of Win10pro 64bit which came with a Dell laptop. Since MistyPE didn't work OOTB for me I had to apply some minor but mandatory changes to Core Files script..
.....Hope my contribution can be of use ... it worked for me......
- Had to insert
If,ExistFile,"%SourceDir%\sources\install.swm",Set,%install.wim%,"%SourceDir%\sources\install.swm",GLOBALat line 210 to get pass an error (install.wim not found)
That's a very large .iso - I dread to think how much junk Dell added to your source file!output: WinPE.iso of a whopping 577680KB
Thanks,
Regards,
Misty
#45
Posted 27 March 2017 - 10:19 AM
---------------------------
Checksum information
---------------------------
Name: MistyPE.2017.03.24.zip
Size: 53584170 bytes (51 MB)
CRC32: D6F9F557
CRC64: 90559A5705349276
SHA256: B0BAAA587EEB9120654F2F5FB15CD2C065614FD7C08F0B6254CCB617A8A9FAFA
SHA1: 93495C71A0A8243B28A95C1970E624EE8C5FDE5A
BLAKE2sp: 8668A1832990F7869B9148AAAAA60D4E006C5837D5ADD71BD3E17878D66B4E97
---------------------------
MistyPE has a new and hopefully permanent home! See post #247 in the MistyPE support thread.
#46
Posted 27 March 2017 - 07:39 PM
MistyPE_20170324 Win7pro x64: WIn10 x64 SYSWOW64 + my oldschool AmiGoXPE 32bit tools
Edited by PTAHDEL0H0, 27 March 2017 - 08:06 PM.
- Brito likes this
#47
Posted 30 March 2017 - 02:05 AM
@misty
#48
Posted 30 March 2017 - 11:20 AM
Thanks for reporting back. I received the same error on my system when the Region settings were changed to Vietnamese. Unfortunately this appears to be a winbuilder error - as version 0.82 is no longer in development it is unlikely to be fixed.
The only workaround is to change region settings.
Sorry,
Misty
#49
Posted 30 March 2017 - 01:19 PM
MistyPE_20170324 Win7pro x64: WIn10 x64 SYSWOW64 + my oldschool AmiGoXPE 32bit tools
Hello!
It's been so long, really happy to see you again! Welcome back!
#50
Posted 30 March 2017 - 05:40 PM
Yeah my friend it's indeed good to be back
- Brito likes this
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users