MistyPE

Hi people, where is the 190.48MB link? I only see MistyPE.2017.04.01.zip  54.35MB to download.

there it is a green download button, behind this klick do you find
different zip files where you can download it then

 

from Misty at the first post very bottom
 

Documentation is included in the download and is also available online - http://mistyprojects...ocs/readme.html

For changelog, see here

Click here to download this file

 

^^

there have you to go and behind the green downloadbutton

i don't see also thing else ..

 

best regards
Blacky

Thanks for your response! The thing is that i don't see the 190.48MB file in the green download button. Only 4 files (different versions)  with 54MB size, all without the programs in their projects.

humm, i don't see it too.. well, i guess, we must wait to Misty

 

best regards

Blacky

 

Miiiiiissstttttyyyyyyy ... Baaannnaaannnaaaaaaa !!!!!

The 190,x Mb download was an early-early version (2013), see the changelog:

http://www.mistyproj...s/Changelog.txt

 

You want anyway to get the latest:

MistyPE.2017.04.01.zip

 

Wonko

Just to let you know Win10 1709 (Fall Creator Update) is a suitable source for MistyPE builds.

 

I used Win10_1709_Spanish(Mexico)_x64.iso (Fall Creator Update) selecting image 5 (Education) of install.wim to make a new build and all went flawlessly, latter booted from it, and all was fine.

 

alacran

Where's Dave? We need him...

Hi all,

apologies for the delay in responding to this thread. Work commitments are leaving me without any free time at the moment.

Just for the record - there has never been a 190.48MB download of MistyPE. I think this is a bug with the forum software and is the cumulative size of all four downloads (40.99MB (MistyPE.2014.06.04.zip) + 43.98MB (MistyPE.2014.07.06.zip) + 51.1 (MistyPE.2017.03.24.zip) + 54.35MB (MistyPE.2017.04.01.zip = approx 190.48MB).

I will check through my PM's asap.

Regards,

Misty

Hello Misty,
just tried your project with Creators Update ISO from MS MediaCreationTool. 
Finally one working with high DPI out of the box! Thanks. 
 
Some usability suggestions. 
Ideally one should set the ISO folder and go. Instead there are a number plugins pre-checked with annoying warning, unless you add related software. Also the ISO did not work with my VirtualBox VM. I had to struggle a lot to realise that the ISO is intended for old BIOS firmware. I set first "UEFI" and then "Both" in the ISO output plugin and both options worked with my UEFI VM. I think that "Both"  should be the default nowadays. 
 
IMHO small WinPEs should be more widespread among non technicians. In my case, just wanted something to put it in my pocket before travelling (just in case). Most people don't have time to relearn everything because MS has encrypted a couple of files. So kudos to winbuilders... but let's make it just a click away.
 
Thanks again for your efforts.

@Antonjo
Thanks for the feedback. In regards to the issue with the .iso and the suggestion that the default setting be Both (BIOS and UEFI bootable) - this would make sense. If memory serves the reason I did not implement this was due to not being able to find the correct switches (if they exist) for creating a BIOS and UEFOI bootable image using the included MKISOFS. The Microsoft oscdimg.exe is required for this option and cannot be included in the MistyPE download. Attempts will be made to download oscdimg.exe from MS, however the link may change.

Regards,

Misty

If memory serves the reason I did not implement this was due to not being able to find the correct switches (if they exist) for creating a BIOS and UEFOI bootable image using the included MKISOFS. 

The "suitable" MKISOFS and (hopefully correct) switches for it  have been given (to erwan.l), here:

 

http://reboot.pro/to...ickpe/?p=189483

 

and following.

 

Use the MinGW verison (that unlike the cygwin version has no external dependencies).

 

Wonko

@Wonko
Thank you my friend. I'll check this out soon. I think the version included in MistyPE is one Bart compiled for BartPE!

Misty

I'll check this out soon. I think the version included in MistyPE is one Bart compiled for BartPE!

Short version (after 14 years):

Bart included -force-uppercase. Setupldr.bin reads uppercase chars at ISO9660 only.
And Bart added Alex's -duplicates-once.

AN-3.02a07
https://sourceforge....ls/files/alpha/
Jörg included and updated -duplicates-once in the meantime.
And added -no-allow-lowercase.
Current source files are recommended nowadays.

http://opensourcepac...p/cdrtools.html
schily-cdrtools-3.02a07.7z

Replace -force-uppercase with -no-allow-lowercase at create.ISO.script


Added:
A example similiar to a Windows 7 EFI installation DVD: a UDF - ISO9660 bridge, without ISO9660 file names

mkisofs.exe -iso-level 3 -D -udf -hide "*" -hide-udf boot.catalog -no-emul-boot -b boot/etfsboot.com -eltorito-alt-boot -eltorito-platform efi -b efi/microsoft/boot/efisys.bin -no-emul-boot -o W7_x64_efi.iso .

The DVD does boot at a BIOS and a UEFI at VMware Player.

Edited by cdob, 06 December 2017 - 04:46 AM.

@cdob
Many thanks for your post and instructions.

@Misty

 

Hi Misty, it is nice to see you here, hope you and your family are doing fine, I wish you Merry Christmas and happy new year.

 

Your friend

 

alacran

@Misty
 
Hi Misty, it is nice to see you here, hope you and your family are doing fine, I wish you Merry Christmas and happy new year.
 
Your friend
 
alacran

@alacran
Thank you my friend. And the same to you and your family.

I'm hoping to be hanging around the forum for a little while. Can't promise to get any development work done, but I will be checking in regularly.

Misty

Many months ago, when updating Mini-WinFE, I created some video clips as a visual aid to those new to the project. Whilst the clips are based on Mini-WinFE they should also apply to MistyPE. As there was a hell of a lot of work involved in both capturing the footage and adding captions I will not be creating MistyPE specific videos!

Links for the clips are available from the link below -
http://mistyprojects...files/links.htm



Misty

P.s. Both Mini-WinFE and MistyPE are reported as Broken (see screenshot) - let me assure you that they are not!

Hi all,

I'm working on updating the MistyPE iso script that contains options for a BIOS bootable .iso, or a UEFI bootable .iso, or a BIOS and UEFI bootable .iso. Thanks to cdob I have some code for the BIOS only option, and the BIOS and UEFI bootable option (not actually tested yet). Just missing the UEFI bootable only code.

Anyone able to help with the mkisofs equivalent of the following oscdimg.exe command (to create a UEFI bootable .iso)

oscdimg.exe -l"WinPE" -pEF -u2 -udfver102 -b"D:\efisys.bin" "%OutputDir%" "%ISODir%\WinPE.iso"

mkisofs is a hell of a confusing application to use - I just can't figure this out from the help file

Regards,

Misty

Hi all,

I'm working on updating the MistyPE iso script that contains options for a BIOS bootable .iso, or a UEFI bootable .iso, or a BIOS and UEFI bootable .iso. Thanks to cdob I have some code for the BIOS only option, and the BIOS and UEFI bootable option (not actually tested yet). Just missing the UEFI bootable only code.

Anyone able to help with the mkisofs equivalent of the following oscdimg.exe command (to create a UEFI bootable .iso)

oscdimg.exe -l"WinPE" -pEF -u2 -udfver102 -b"D:\efisys.bin" "%OutputDir%" "%ISODir%\WinPE.iso"

mkisofs is a hell of a confusing application to use - I just can't figure this out from the help file

Regards,

Misty

 

 

It has been a long time ago but it has been working for me so that, here below my command line from QuickPE batch to build a BIOS only or BIOS & UEFI iso.

 

I am in doubt thus about -UDF vs -udf (different case).

Same goes with -R vs -r (different case).

In both cases, it is I believe about rationalized vs not rationalized...

Reading here and there I believe one should go for the rationalized switches (small case switches).

And you may also want to drop -D as I am not sure this is really needed (and it violates ISO9660)...

 

What I know is that below worked for me and I am not touching it unless a good reason comes in

 

Last but not least I dont know if you can build an iso with UEFI boot only and why would you when you can have an iso that does both?

if exist "%dest%\iso\efi\microsoft\boot\efisys.bin" (
call mkisofs.exe -iso-level 4 -l -R -UDF -D -volid "WINRE" -b boot/etfsboot.com -no-emul-boot -boot-load-size 8 -hide boot.catalog -eltorito-alt-boot -eltorito-platform efi -no-emul-boot -b efi/microsoft/boot/efisys.bin -o "%dest%\winre.iso" "%dest%\iso"
) else (
echo "!!!!!! efisys.bin MISSING !!!!!!"
call mkisofs.exe -iso-level 4 -l -R -J -joliet-long -D -volid "WINRE" -b boot/etfsboot.com -no-emul-boot -boot-load-size 8 -hide boot.catalog -o "%dest%\winre.iso" "%dest%\iso"
)

Hey Misty,

Info from Jörg and he have corecting the Manpage of mkisofs
---------------------------------------------------------------
-D

-disable-deep-relocation
Do not use Rock Ridge deep directory relocation, and
instead just pack directories in the way they are in
the master directory tree.

This option was needed with old mkisofs versions to
avoid a visible directory rr_moved. Since August 2006,
mkisofs correctly hides the rr_moved directory from the
Rock Ridge filesystem.

If ISO-9660:1999 has not been selected, this violates
the ISO-9660 standard, but it happens to work on many
systems. Use with caution.

[Google > German to English]
Otherwise, someone seems to have overlooked that EFI specifically
for the BIOS to understand

[Microsoft > German to English]
Otherwise, someone here seems to have overlooked the fact that EFI is specifically
Must mark so that the BIOS understands it




-eltorito-platform id
Set the "El Torito" platform id for a boot record or a
section of boot records. The. id parameter may be
either:

x86 This is the default platform id value and speci-
fies entries for the PC platform. If no
-eltorito-platform option appears before the first
-eltorito-boot option, the default boot entry
becomes an entry for the x86 PC platform.

PPC Boot entries for the Power PC platform.

Mac Boot entries for the Apple Mac platform.

efi Boot entries for EFI based PCs.

# A numeric value specifying any platform id.

If the option -eltorito-platform appears before the
first -eltorito-boot option, it sets the platform id
for the default boot entry.

If the option -eltorito-platform appears after an
-eltorito-boot option and sets the platform id to a
value different from the previous value, it starts a
new set of boot entries.

The second boot entry and any new platform id creates a
new section header and reduces the number of boot
entries per CD by one.

Jörg

http://cdrtools.sour...e/cdrecord.htmlRelease 3.00
https://sourceforge....cdrtools/files/
http://cdrtools.sour...cord/index.html
--------------------------------------------------------

Thank you very much Jörg

best regards
Blacky

Anyone able to help with the mkisofs equivalent of the following oscdimg.exe command (to create a UEFI bootable .iso)

oscdimg.exe -l"WinPE" -pEF -u2 -udfver102 -b"D:\efisys.bin" "%OutputDir%" "%ISODir%\WinPE.iso"

.
A Windows 7 installation UEFI DVD boots:

mkisofs.exe -iso-level 3 -udf -hide "*" -hide-udf boot.catalog -eltorito-platform efi -b efi/microsoft/boot/efisys.bin -no-emul-boot -o W7_x64_efi.iso .

.
Try

mkisofs.exe -iso-level 3 -udf -hide "*" -hide-udf boot.catalog -eltorito-platform efi -b efi/microsoft/boot/efisys.bin -no-emul-boot -o "%ISODir%\WinPE.iso" "%OutputDir%"

@erwan.l and @cdob
You guys are amazing. Thank you both for the help and suggestions . You have no doubt saved me hours of time and frustration.

I'm working on updating the project and this information will come in very handy. Lots of testing will be required as usual as there are multiple potential outputs in the project. For example -
RAM loading only -> created using mikisofs -> BIOS bootable
RAM loading only -> created using mikisofs -> UEFI bootable
RAM loading only -> created using oscdimg -> BIOS bootable
RAM loading only -> created using oscdimg -> UEFI bootable
etc

I estimate that there are up to 36 variations possible in MistyPE/Mini-WinFE I'd like to test all potential variations, so lots of time/work.
 

...Last but not least I dont know if you can build an iso with UEFI boot only and why would you when you can have an iso that does both?...

The current project script has this option, which is available if using oscdimg.exe. cdob has suggested example code for mkisofs and I'd like to replicate all of the current options, however I plan to change the default output to a UEFI and BIOS bootable .iso using mkisofs.exe.

Regards,

Misty

@Blackcrack
Thanks for the info. Due to the share volume of options in mkisofs and my lack of knowledge of the program, this further illustrates why I asked for help instead of just trying to work it out myself. Sometimes life is just too short!!!!!! P.s. Did I mention that sometimes I'm just lazy!!!!!!!

building scripts for , it is because we are all to lazy !
(and giving knowing further because the other it is also to lazy for learn*hihi*)
*looooooollll* otherwise could we make all via cmdline and we all would be cmdline scrubbers
( if i am think about configuring ever and ever a new linuxsystem without a script in vbox..uhhhh..)

how ever, for building up some scripts is this also a training for our brain,
this is also why we eat Bananassss BAAANNNAAANNAAASSSSS....... *bg*

best regards
Blacky

@cdob
I tested using the command syntax in post #296

mkisofs.exe -iso-level 3 -udf -hide "*" -hide-udf boot.catalog -eltorito-platform efi -volid "WINPE" -b efi/microsoft/boot/efisys.bin -no-emul-boot -o "%ISODir%\WinPE.iso" "%OutputDir%"

and post #288

mkisofs.exe -iso-level 3 -D -udf -hide "*" -hide-udf boot.catalog -no-emul-boot -b boot/etfsboot.com -eltorito-alt-boot -eltorito-platform efi -b efi/microsoft/boot/efisys.bin -no-emul-boot -o "%ISODir%\WinPE.iso" "%OutputDir%"

Both failed to build with error -

mkisofs.exe: Warning: Cannot add inode hints with -no-cache-inodes.
mkisofs.exe: No such file or directory. Invalid node - '-hide-udf'.

Both attempts completed when the -hide "*" switch was removed. Any thoughts or suggestions?

Please note that I haven't actually tested the resulting .iso files yet.

Regards,

Misty

MIsty, you must also specify which EXACT version of mkisofs you tested with.

 

First try the known to be working version that erwan.l uses with the known working commands (even if possibly to some extents "wrong") erwan.l uses succesfully in his project.

 

Then try the same commands with the new (suggested by cdob) release of mkisofs.

 

Then try the newly suggested by cdob commands with the new  mkisofs version.

 

I don't think that there is any *need*  to "hide "*"", however.

 

Anyway, please allow me , nice exercise in futility .

 

 

Wonko