Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 11 May 2017 - 07:55 PM

Thanks, I see the question is answered on your E2B website. I'll get around to converting the ISO soon. I find that imgPTNs are usually more useful because they can boot in either legacy or UEFI, ISOs appear to work only in legacy mode.

I have another quick question: Is it possible to run E2B from within a NTFS GPT partition on an internal drive? I would find it very useful to be able to place my most used booting mediums there so I don't have to constantly use a USB flash drive. I would use this as a sort of onboard recovery partition of sorts.

Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 11 May 2017 - 08:27 PM

Thanks for the info. That is really the only major limitation I can find with E2B, since it relies on Grub4DOS, which in turn seems to currently only work in legacy mode. I mean, you can switch to an imgPTN, which will then be presented to the firmware as a valid FAT32 booting medium for UEFI. And I know that you can boot in UEFI mode on a flash drive that has either a MBR or GPT partition table. But for booting recovery tools located on a NTFS GPT partition.....no idea. Can you suggest any other alternatives to accomplish what I am seeking?

With v1.93a Beta I have now included support for the offline installation of Chocolatey packages.

This means that the SDI_CHOCO process can now be completely offline and you can install drivers using Snappy Driver Installer, Windows updates using wsusoffline installer and apps using Chocolatey ready-made packages completely unattended and from an unmodified Windows Install ISO file.

Having some problems with running Win10 ISO files through E2B as of late. The screen will just freeze after I select a profile from the list (home, pro, no repair, repair, choco etc..)

All I see are the ISO name and Unattend.xml followed by a vertical | forever. I've been able to fix it a few times by running the contigous.bat, or moving some files around randomly (I think), or by redownloading the ISO. But it keeps coming back for some reason.

Drive is a 128GB NTFS formatted pendrive from Kingston, but I've also seen it happen on my old 64GB G3 Datatraveler.

While I'll definitely run the Flashtests, I highly doubt they are fakes. All three? (Might be four) drives I've used/made for colleagues have been bought in-house from our suppliers. No dodgy webstores involved.

Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 28 June 2017 - 08:32 AM

I'm getting 2 UEFI boot entries when switching in an imgPTN. I had made a Gandalf's Win10PE imgPTN that can be booted in legacy or UEFI, both modes work 100%. But when I select an entry in my boot options, it shows 2 partitions to select. The first boots into the PE, the 2nd does nothing. I checked the USB FDD in Disk Management while the imgPTN is switched in, the 1st, 3rd, and 4th partitions are unallocated, the 2nd is the PE itself (presumably NTFS). What causes this behavior? Is this a glitch? If 3 of the partitions are unallocated/raw then there is nothing to boot on those partitions, why are they listed (since they're not FAT32)? And for that matter, why are only 2 shown instead of 4? This doesn't present an issue but it hasnt happened until now, and only with this PE. I'm using the latest E2B and MPI released this month.

Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 28 June 2017 - 09:21 AM

You mean....in my BIOS/UEFI boot options?.....pressing Space doesn't do anything, it's just the normal select a boot option with Enter. When I say boot options, I'm referencing what appears on-screen when I press F7 at powerup.

Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 28 June 2017 - 09:45 AM

I'm not using E2B's Clover at all, my laptop only has USB 3.0 ports. I do have a standalone USB FDD on which Clover is installed, and it does work, but it only detects internal partitions, no USB devices. I didn't see a 32 bit option, and I suspect it wouldn't work anyway, since I have a very recent x64 CPU (i7-7700K). When I say boot menu I'm referring to my BIOS's boot menu, not E2B's. i.e. the one built into the hardware.

Interests:An investigation is underway to determine whether Trump has any ties to America.

United States

Posted 28 June 2017 - 10:39 AM

When I say "boot menu" I mean, literally, the boot menu that comes up when I press F7. In other words, the boot selection menu that is built into my BIOS/UEFI firmware. Surely you know what I mean. I really couldn't put it more simply than that. When my boot menu comes up, E2B (being software) hasn't even had a chance to load yet.

So:

1. Switch in imgPTN

2. Use the Reboot option (since the Clover built into E2B doesn't work, I must use my hardware's native UEFI capabilities)

3. Press F7, 2 boot options appear for the USB, partition #1 and partition #2, it doesnt give much more of a description than that. The 1st works, the 2nd doesn't.

I just put on an 8 GB USB stick (NTFS formated) your Great Tool E2B v1.93A and I have some questions:

1.- Selected spanish language and all menus are in spanish now, very well done congratulations, but I didn't find an option for spanish keyboard, can you please tell me how can I change it?

2.- All my *.iso booted just fine from BACKUP, UTILITIES and WINPE subfolders, in order to test *.wim boot, I extracted boot.wim from my MistyPE-10x64.iso to _ISO\WIN and rename it to Misty10x64.wim, it booted flawlessly. I assume it is the same for *.VHD files, just copy it to E2B\ _ISO\WIN and rename it if required. Is that right?

3.- All this was in an old Bios PC, now to boot on a EFI/UEFI Bios only way is *.imgPTN or is there another way using maybe grub2 as loader?

For E2B, we usually just need A-Z,a-z,0-9 to answer questions or enter a password and F1-F10 keys.

Maybe also filenames which use - _ () . / and \ too.

The other keys do not usually need to be translated or used.

If you define your own passwords, I suggest you don't use 'special' characters because you may need to boot E2B on a system that has a different keyboard. Using a PIN number instead of a word-string is a good compromise.

Note that because E2B is coded to look for Y and N as answers to some questions, you should answer using Y=Yes or N=No.