Jump to content











Photo
* * * * - 2 votes

MistyPE

winpe10 winpe5 winpe4 winpe3 winpe2 winpe

  • Please log in to reply
364 replies to this topic

#126 erwan.l

erwan.l

    Gold Member

  • Developer
  • 2249 posts
  • Location:Nantes - France
  •  
    France

Posted 03 May 2014 - 02:51 PM

 

 

wasn't able to get a build from any os iso. i think this misty build is like all the winbuilder builds very bad. need a better way to make a custom pe without doing it manually someone else have a better way?

 

Launch winbuilder,

Go to source,

Select your source directory to point to your windows media installation dvd drive (E:\ for me),

Click play,

Retrieve your winpe iso in x:\MistyPE\MistyPE.Project.Output\.

 

Works for me :)

Attached Thumbnails

  • mistyPE.png

  • misty likes this

#127 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 03 May 2014 - 03:45 PM

wasn't able to get a build from any os iso. i think this misty build is like all the winbuilder builds very bad. need a better way to make a custom pe without doing it manually someone else have a better way?


@Kronus
Sorry to hear that this project doesn't suit your needs. Please do consider having a quick read of the instructions (particularly the Quick Start Guide) and giving it another go. If you have any constructive critism then please feedback.

For a (very) fast non-WinBuilder based project please do take a look at erwan.l's QuickPE - this really does live up to it's name.

Regards,

Misty

P.s. The documentation is also included in the MistyPE download (Readme.html).

#128 kronus

kronus
  • Members
  • 9 posts
  •  
    United States

Posted 03 May 2014 - 04:07 PM

Thanks,

 

i have seen what i did wrong with your release of misty. for some reason i thought it could use the ISO file as source. okay after mounting the iso i was able to make a build of win7pe. the win8.1 iso  even with mounting very lots problems.

 

i like the Quickpe makes things more simple and easy for me.

 

sorry for my comment i was just upset at not being able to make an ISO, i to stupid to see it was my fault. even reading the easy to understand intruction i overlooked the solution right before my eyeballs.

 

thanks for your work and release of the misty script good job.



#129 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 03 May 2014 - 04:52 PM

...even reading the easy to understand intruction i overlooked the solution right before my eyeballs.

thanks for your work and release of the misty script good job.

@kronus
Thanks for the feedback. We are all sometimes guilty of not reading (or perhaps skimming) the instructions - thanks for giving the project another go and particularly for reporting back afterwards.


...the win8.1 iso even with mounting very lots problems...


If you could let me know what went wrong I'd appreciate it - it could help with improving the build for others.
 

...i like the Quickpe makes things more simple and easy for me.

Me too. The first time I used it the build completed so quickly I assumed there had been an error! There hadn't!!

Regards,

Misty

#130 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 25 May 2014 - 09:42 PM

Project updated -
  • Wimlib updated to 1.6.3 Beta. The amended update add command significantly reduces build time when the INJECT method is used.
  • UEFI support has been added.
  • Create ISO script updated. It now contains several options including Flat Boot and RAM Boot or multiboot RAM and Flat boot. It's also possible to create a BIOS or UEFI bootable ISO - or BIOS and UEFI bootable.
  • Create USB updated to include the option to RAM Boot or Flat Boot or multiboot RAM and Flat boot. UEFI support is also included. This script will not work if running WinBuilder on a Windows 2000/XP/2003system.
  • Create USB (GPT UEFI) script added. This script will not work if running WinBuilder on a Windows 2000/XP/2003 system. Only fixed type disks are supported.
  • Added error check to the ADK For Win 8 (and 8.1) scripts - these cannot be executed if running WinBuilder on a Windows 2000/XP/2003 system.
  • Project.Settings.ini is added to the build listing all programs and project settings used in the current build.
  • A special thanks to alacran for requesting UEFI support and beta testing several attempts to get it working.
Regards,

Misty

#131 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 01 June 2014 - 03:03 PM

Project updated
  • SysWOW64 support added when building from Windows 7/7(SP1)/8/8.1/8.1 Update 1 sources (should also work with some Windows Server 2008/2012 sources). The 5-Wow64 script was used as a base to identify file and registry dependencies. Credit therefore goes to everyone involved in the 5-Wow64.script (including JFX, Lancelot, 2aCD, ChrisR and "...to everybody on the BootLand forums for helping on the debuggind and improvement of this script."). Select 4] SysWOW64 in the main project script options to add SysWOW64.
  • A number of changes were made to the core script - wimlib-imagex now uses file lists when extracting dependencies from install.wim/boot.wim. This significantly improves build time, but has meant that any program scripts containing paths for file dependencies has required editing due to wimlib preserving directory structure(when extracting from file lists).
  • Fixed a bug in the Create ISO script - ini file was not being read.
  • Fixed a bug when x64 local sources are used (in Create a cache from WinRE and the ADK scripts). Due to the way in which SysWOW64 redirects to the \Windows\SysWOW64 directory when running WinBuilder on a 64-bit system the file dependencies were being cached from \Windows\SysWOW64 instead of \Windows\System32
  • A special thanks (again) to alacran for requesting SysWOW64 support and beta testing.
  • Due to the number of changes made in this build it is entirely possible that errors may have unintentionally crept in. Please report any issues (or positive feedback) on the support topic at reboot.pro - http://reboot.pro/topic/18917-mistype/
Regards,

Misty

#132 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 01 June 2014 - 08:09 PM

@ misty

 

Found a bug:

 

Host OS 7SP1x64 (Spanish version) cache from WinRE made OK, later during building program stop and aborted building, attached log:

 

http://www.mediafire...2ikhof/log.html

 

Best Regards

 

EDIT: Same problem building from same host OS and now using 8.1u1x64 Enterprise Eval ISO as source, It aborted at the same exact item, I never had this issue when testing your betas, so it has to be something you change in this script. Sorry for not try to switch scrip with one of the betas because I just erase them after seen your post.



#133 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 01 June 2014 - 08:54 PM

This is the problem:

 

 (DiskMgmt.script) FileCopy - Failed to copy [%BaseDir%\Projects\Cache\source\x64\Dependencies\Windows\System32\en-US\mmc.exe.mui] to: [%BaseDir%\MistyPE.Project.Output\ROOT\Programs\DiskMgmt\Dependancies\en-US\mmc.exe.mui]: El sistema no puede encontrar el archivo especificado. (The system can not find the file specified), file is not in the cache as I confirmed.

 

In my running OS the file mmc.exe.mui is located at C:\Windows\System32\es-ES.  There is not any mmc.exe.mui at C:\Windows\System32\en-US.  I guess it is same thing in 8.1u1x64, so miss file is the same.

 

Regards



#134 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 01 June 2014 - 09:01 PM

Hi alacran,

Thanks for the feedback. I think I've isolated the problem. Will fix it and upload as soon as possible - hopefully tonight, if not then in the morning.

Regards,

Misty

#135 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 01 June 2014 - 09:09 PM

As a temporary measure I've attached an updated DiskMgmt script. I'll check the other scripts for similar errors before uploading.

Attached File  DiskMgmt.script   14.37KB   423 downloads

#136 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 01 June 2014 - 09:58 PM

New upload - hopefully fixing the issue reported by alacran :cheers:

In addition to the Disk Management script, I have also amended the Eraser and PartitionGuru scripts.

Regards,

Misty

#137 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 01 June 2014 - 11:18 PM

New build:  7sp1x64 (Spanish version) MBR installed Host OS, using WinRE as source, building OK, but when building ISO (firmware type both) I got following message and abort:

 

Spoiler

 

After selecting fimware BIOS, ISO building was OK.

 

Now I'm going to build from 8.1u1x64 source and report back

 

EDIT: Building from same host OS and using 8.1u1x64 Enterprise Eval as source, & building ISO (firmware type both) just fine, only a single message in log:

Spoiler

 

NEW EDIT: Rebooted to 8.1u1x64PE ISO on HDD using Grub4Dos, and ran all programs excluding WinHex and WinFE related (not included in my build), and all of them open just fine.

 

CONGRATULATIONS, you added UEFI before, and now sysWOW64 is working great!!!!!!!!!!!!!

 

Best Regards


Edited by alacran, 02 June 2014 - 02:37 AM.

  • misty likes this

#138 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 03 June 2014 - 03:57 PM

Hi alacran,

Thanks as always for taking the time to feedback. Following your report regarding the error when building from WinRE souces...

[Warning] (create.ISO.script) \efi\microsoft\boot\efisys.bin IS MISSING
[Warning] (create.ISO.script) A file required for UEFI compatibility is missing - see warnings above

...I have noticed a few errors in the WinRE and ADK scripts - they have been defaulting to the %LANG% variable set in the main project options (option 8] WinPE Language) when they should be using language settings obtained from source files. I don't think this is related to the missing efisys.bin, but it could be - either way this needs fixing. Just out of curiosity what language was set in option 8 when you experienced the build errors?

The WinRE script is currently set to extract efisys.bin from \Windows\Boot\DVD\EFI\%LANG%\efisys.bin - in my case \Windows\Boot\DVD\EFI\en-US\efisys.bin. Is it possible to check your WinRE .wim file for the path to efisys.bin?

If 7-zip fails to open the .wim file you could always boot it and check for the file in the running WinPE.

Regards,

Misty

#139 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 04 June 2014 - 12:45 AM

@misty

 

Just out of curiosity what language was set in option 8 when you experienced the build errors?

 

es-ES

 

Is it possible to check your WinRE .wim file for the path to efisys.bin?

 

Winre.wim\Windows\Boot\DVD\EFI\en-US\efisys.bin

 

There is not es-ES folder in EFI subdirectory

 

Best Regards


  • misty likes this

#140 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 04 June 2014 - 09:29 PM

Project updated -
  • Fixed bugs in Create a Cache From WinRE, ADK for Win 8 and ADK for Win 8.1 scripts. Language settings from source files was not being used.
  • (Hopefully) fixed a bug in Create a Cache From WinRE - efisys.bin (required for UEFI boot from CD/DVD) was not being extracted on non-en-US sources.
  • CloneDisk script added.
  • Free Virtual Keyboard script added.
Regards,

Misty

#141 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 04 June 2014 - 10:42 PM

@ misty

 

I guess it is a false posite, but I want to informe you Avast is blocking your project download since MistyPE.2014.06.01v2 and also the last updated one, in order to download it I need to disable Avast during downloading.

Link to image: http://www.mediafire...t_detection.jpg

 

Best Regards



#142 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 05 June 2014 - 07:06 AM

Hi alacran,

Thanks for letting me know. I've been including the exact same version of WProtect.exe since the first release of MistyPE - I suspect this must be due to a virus definition update.

According to Mr Ramsden's site (see here) the md5 checksum for WProtect should be -
Current Version: 1.0.0.155
MD5 Hash: B10AA293D061DB2DBC156BCE9E5FE9FC
Please feel free to check this against the one in the MistyPE download.

I'll double check myself when I get home.

Regards,

Misty

P.s. any build issues with the new release?

#143 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 06 June 2014 - 01:09 AM

@ misty

 

As I told you my guess is it is a false positive, about buiding using last version:

 

Win7SP1x64 (MBR partitions) host OS source WinRE, Building very fine, ISO building (firmware type both) just fine, Booting only tested in legacy Bios, x86 programs running fine. Only comment is when you select any x86 script it says "Warning - Working in x86 buids only".

 

Let me suggest you it should say: "Select sysWOW64 to run x86 programs in x64 builds"

 

I don't have any more the laptop in UEFI, I formated it and installed Win7x86 on MBR partitioned HDD (it is downgrade capable), the win8 x64 was running very slow in 2 GB RAM, so I could no test UEFI booting for now.

 

I have some problems to select a custom folder using the select push button in script, only way is typing path and enter (I have a main folder with several folders with some files in each one), This is not new, I forgot to tell you before.

 

Best Regards



#144 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 06 June 2014 - 08:42 AM

...Only comment is when you select any x86 script it says "Warning - Working in x86 buids only".

Let my suggest you it should say: "Select sysWOW64 to run x86 programs in x64 builds"...

Good suggestion :thumbsup:
 

...I have some problems to select a custom folder using the select push button in script, only way is typing path and enter (I have a main folder with several folders with some files in each one), This is not new, I forgot to tell you before....

An oversight on my part. As a temporary measure please change line 13 in this script from -
pFileBox1=,1,13,71,110,428,20,File
to -
pFileBox1=,1,13,71,110,428,20,Dir
I'll add these changes to the next upload. As they are relatively minor changes I will wait a week or so just in case any further bugs are reported.

Regards,

Misty

#145 alacran

alacran

    Silver Member

  • Advanced user
  • 566 posts
  •  
    Mexico

Posted 06 June 2014 - 08:04 PM

@ misty

 

Good, I am totally agree with you, there is no reason for a new quick update, until you add new script it is working fine, (just changing line 13 in custom folder script is not a problem), the suggestion I made do not interfere in any way with building, it is only cosmetic.

 

Best Regards

 

EDIT: When you have time, Could you add an script for Gimagex v2.11 ? (for use with the Windows ADK for Windows 8.1) to download only required files, JFX little application GetWaikTools may be used, Gimagex v2.11 is working fine for capturing and applying wim images in GUI, it works from Win7 to latest (not for XP or Vista).

 

EDIT2: I just tested ReTokener tool (GUI for winimage v1.70): http://reboot.pro/to...-line-compiler/ this may be a better GUI option as you can get Recovery compression from it.

 

EDIT3: No need to make an script.  I added both to Custom Folders and Files, and they can run from there.


Edited by alacran, 10 June 2014 - 09:31 PM.


#146 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 06 July 2014 - 06:33 PM

Project updated -
  • wimlib updated to version 1.7.0
  • Fixed a bug with SysWOW64 support when building from source files created by running the Create a Cache from WinRE script. SysWOW64 registry settings were missing - resulting in a number of errors including open with and save as not working in running programs. Fix also applied to the ADK scripts (when building from host OS source files).
  • Cosmetic updates as requested by alacran (see http://reboot.pro/to...type/?p=184695)
  • Developing Program Scripts section rewritten to include some example scripts + additional information about how tasks are handled in MistyPE
Regards,

Misty

P.s. Sorry for the delay - updated the Developing Program Scripts section of the instructions proved to be a bit of a chore!
  • alacran and devdevadev like this

#147 misty

misty

    Silver Member

  • Developer
  • 869 posts
  •  
    United Kingdom

Posted 26 July 2014 - 06:16 AM

Please do not use a path with apostrophes/single quotes (') in it - e.g. C:\_Forensic_Boot_Disk_ISO's. If you do then the build will appear to complete successfully however the build files will not actually be injected into boot.wim. See http://reboot.pro/to...ot-the-project/ (thanks to seanpowell for bringing this to my attention).

Regards,

Misty

#148 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 13988 posts
  • Location:The Outside of the Asylum (gate is closed)
  •  
    Italy

Posted 11 September 2014 - 06:26 PM

MIsty, 

if (when) you are back and have time, can you check this? (colours of selected text in menus):

http://www.911cd.net...topic=25776&hl=

 

I may well be going after a wild goose with that one :w00t: :ph34r:

 

:duff:

Wonko



#149 sebus

sebus

    Frequent Member

  • Advanced user
  • 305 posts

Posted 31 December 2014 - 04:18 PM

Download links no longer work

 

http://mistype.reboot.pro/

 

is

 

default.domain

#150 Mr.JoeM

Mr.JoeM
  • Members
  • 4 posts
  •  
    United States

Posted 07 January 2015 - 09:35 PM

Download links also show 404 for me. Any suggestion on who to contact to get this fixed?

 

I am desperately hunting for a fix to a bug you seem to have addressed. I was hopeful I could find the fix in your scripts. 

 

The issue I am seeing is bblean 1.17 only shows black background on WinPE 4 and 5. This worked fine in PE3.

 

~joe







Also tagged with one or more of these keywords: winpe10, winpe5, winpe4, winpe3, winpe2, winpe

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users