This page has a different format from the other site pages and has hardly any adverts. You can view all pages on the entire site like this when you donate £5/$8 (English GBP/US Dollars) or more (on both www.easy2boot.com and www.rmprepusb.com sites). You can read and subscribe to my blog here.
 
 

E2B Users Forum

New! E2B eBooks are now available (eBook #1 contains instructions on how to remove the blue-screen startup banner).
 
If you would like help from me (Steve Si) or other E2B users, or would like to offer help and advice to others, please post here.
 
You will need to check this page regularly for replies or add this page's URL to a page change ch ecker.
 
Alternatively, post on the Easy2Boot discussion page on reboot.pro here - register and subscribe to any threads that interest you or post a new topic.
 
You can use the Chat\Live Help facility - if I am online, I will respond within a minute or so (if I am away from my desk, leave your email address and I will email you). For 1-to-1 email communication, use the Contact Me form and I will reply via email.
 
To post to this Forum, scroll to the bottom of the page and click on 'New comment' (use English please).
 
Also, you can read and subscribe to my blog here.

Topic: Easy2Boot

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

2016 and 2019 both work fine for me with E2B v1.B2b. No one else has yet reported an issue.
Maybe it is a strange issue with the new grub4dos (\grldr)?

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

As stated earlier, I had an older flash drive using v1.a9 that up updated to 1.b1 and that drive fails also. That particular drive has been in use for over a year with no issues. To me, the only thing that has changed is the new 1.b1 version.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

well, you would need to test the same flash drive on the same system. Try an earlier version and then update to 1.B1 and then downgrade to the earlier version again so nothing changes except E2B and the position of the files on the USB drive.
QEMU MENU TEST will boot TI 2016 OK so you can try that too to remove any target system issues.
v1.B1 works OK for me.

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I ran QEMU menu test and it fails there using v1.b1. I have a v1.A9 version flash that works. I will update that to 1.b1, test, and then downgrade again to 1.A9 and test again. Heading to work. Will be back in about 6 hours.

Date 04/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Booted new flash drive created with V1.A9. Boots ok.
Ran Qemu and Acronis loads.
Rebooted 1.A9 flash drive again and selected Acronis to load - loads ok.
Used 1.B1 to update same flash drive.
Booted 1.B1 flash - boots ok.
Tried to load Acronis - just hangs.
Rebooted 1.B1 flash and loaded Kyhi Rescure with no issues - loads ok.
Downgraded same flash drive to 1.A1.
Booted 1.A1 flash - boots ok.
Loaded Acronis - loads ok.
Did not run FakeFlashTest as drive appears ok.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Thats really odd.
Can you update to 1.b1
check it fails to boot TI
Then change the \grldr file to the one used in 1.A1.
If that still fails, change the \_ISO\e2b\grub\QRUN.g4b file to the 1.A1 version too. Thanks.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Progress!!
Booted 1b1 and tried TI - fails.
renamed grldr on flash to 1b1gldr.
copied grldr from 1a9 to flash.
Booted 1b1 flash with 1a9 grldr and loaded Ti with success.

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Could you update to E2B v1.B2c and try it please?
If it doesn't work, can you try various versions of 0.4.6a working back from the latest version. Just extract the grldr file from the zip file and replace the one on the E2B root folder.
http://grub4dos.chenall.net/
I will report to the developers if we can narrow it down to a version change.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Updated to 1.B2c
Ran Qemu to attempt TI load - fail.
Downgraded grldr to 190325
Tested again - Success.
All after 190325 (190507 and 190512) fail

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

That's great! Good work!
The only thing now is that I cannot reproduce the problem. So could you tell me the checksum (MD5\CRC32,SHA1 or whatever) of your ISO and where I can obtain it (so I can download it - you can email me if you prefer at [email protected]).
I will then reproduce the issue using QEMU and raise an issue report for it.
P.S. In E2B - have you selected a different keyboard translation file (not QWERTY USA)? If so, which one are you using (see \_ISO\MyE2B.cfg KBD setting and try removing that line so USA kbd is used).
I have tried 5 different versions of 2016 ISOs and they all work.

Date 05/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I don't have a checksum for the ISO, but if you mean I should create one, I can do that. I am uploading the ISO to Mega at the moment. Once upload, I will send you a link to the file. On the way to work, will send link on return.

Date 09/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

Please try latest grldr file - it seems to work
http://grub4dos.chenall.net/downloads/grub4dos-0.4.6a-2019-06-09/
Should be fixed now in E2B v1.B2e Beta or later.

Date 22/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

The date of your posts is incorrect. Where is the latest beta (v1.B2e) so that I can download and test. Thanks

Date 22/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

v1.B2 is the latest version.
(v1.B2e was a previous Beta.)

Date 23/06/2019

By Dick

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: New Version 1.b1 and Acronis

Reply

I downloaded and tested the latest v1.B2 and all is good now. TI loads correctly. Thank you for your quick and excellent help to resolve this.

Date 02/06/2019

By Krauter_German

Subject 137GB BAD BIOS BUG

Reply

Hello,
I use a Sandisk Extreme Pro 256GB. The first partition NTFS 114Gb for E2B_v1.B2b and a second primary partition NTFS 123GB for data.
1. Dell Workstation T3500 with Windows 7. Data partition visible to Windows 7. Boots from E2B without problems.
2. PC with Asus P6T SE socket 1366 and Windows 7. Data partition visible for Windows 7. Booting E2B with Note: e2b.cfg is corrupt or missing, enter. Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ACCESSING SOME FILES ON THIS DRIVE!
Then the option click U and load USB 2 driver (something like that), then the E2B menu appears.
The first partition for E2B has significantly less than 137GB and still this error appears. Can one ignore this message or do some files not work?
Before I had E2B partition 100GB and data partition 137GB.
RMPrep CTRL-O-2 makes data partition visible but under Windows 7 E2B partition was still visible.

Date 02/06/2019

By SteveSi

Subject Re: 137GB BAD BIOS BUG

Reply

If you load the USB driver (U) OK, then there will be no problem.
If no USB driver, then you will not be able to access files past 128GB on the drive. So E2B\grub4dos will not be able to access some files on the 2nd partition using the BIOS (no problem once booted to Windows). So in your case you can ignore the message.
E2B does not know if you have ISOs etc. on 2nd partition.
But the e2b.cfg file is corrupt or missing message is a bit worrying... not sure why you see that!
Can you use RMPrepUSB - Drive Info - 0 to view partition table - maybe you have accidentally installed E2B to the last partition?

Date 04/06/2019

By Krauter_German

Subject Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I've tested even further: first partition 99GB E2B, second partition 99GB DATA, the remaining capacity unallocated. DATA partition for Windows 7 made visible and booted. e2b.cfg is corrupt or missing does not appear. Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ... will continue to appear. Then I installed with Easy2Boot_v1.B1.exe, EB on the USB stick, deleted the second small partition with EASEUS and a second primary data partition with the remaining capacity erstellet, created PBR and MBR. DATA partition for Windows 7 made visible and booted. e2b.cfg is corrupt or missing appears, Enter, Note: BIOS Bad (possible 137GB BIOS limt?). Warning: THIS BIOS MAY HAVE PROBLEMS ... will continue to appear. E2B partition for Windows 7 made visible and booted: e2b.cfg is corrupt or missing does not appear. Message:
Booting Easy2Boot v1.A9-please wait ...
Using settings in /-ISO/MyE2B.cfg
Using settings from / _ISO / e2b / grub / German / Strings.txt file
BIOS 09/21/10
Last Sector of last partition of (hd0) is 500170748 (238GB)
Checking (HD0) sector 500170494 is accessible ...
BIOS BAD (possible 137GB BIOS limit?)
Warning: This BIOS MAY HAVE PROBLEMS ...
On an AM4 board with Ryzen and Windows 10, there are no problems. On Dell Workstation with Socket 1366, XEON and Data Partition visible for Windows 7, there is also no problem booting E2B. On ASUS Board, Socket 1366, I7 960 witerhin the symptoms described above. Maybe you think of something else.
Incidentally, yesterday I received the download link for the purchased eBooks, a big compliment for a great job.

Date 04/06/2019

By SteveSi

Subject Re: Re: Re: 137GB BAD BIOS BUG

Reply

So to sum up:
ASUS P6T
1.A9 99GB+99GB SWAP >> BIOS BAD
1.B1 99GB+400GB NO SWAP >> BIOS BAD
1.B1 99GB+400GB SWAP >> BIOS BAD + e2b.cfg is corrupt
1.B2b 114GB+123GB SWAP >> BIOS BAD + e2b.cfg is corrupt

I think the e2b.cfg message is caused by a change I made in v1.B1 and 1.B2b. E2B v1.B2c should fix this - please try it.

Since the last partition is always past 137GB, you will always see the BIOS BAD message on the P6T because it has a bad BIOS!

Date 05/06/2019

By Krauter_German

Subject Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I have E2B 1.B2c installed but unfortunately no change:
1.B2c 125GB + 113GB SWAP >> BIOS BAD + e2b.cfg is corrupt.
I think it's very difficult to make all bios (especially older ones) compatible with E2B. For these cases, it is probably advisable to use a USB stick with max. 128GB to use.

Date 05/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

But according to your report, the behavior of the two E2B versions is different:
1.A9 99GB+99GB SWAP >> BIOS BAD
1.B1 99GB+400GB SWAP >> BIOS BAD + e2b.cfg is corrupt
??? I don't understand why you see the e2b.cfg error message ???

Date 05/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

1.B2b 114GB+123GB SWAP >> BIOS BAD + e2b.cfg is corrupt
1.B2B 99GB+99GB remaining capacity unallocated SWAP >> BIOS BAD

v1.B1.exe 127GB+111GB SWAP >> BIOS BAD + e2b.cfg is corrupt,
If e2b is visible for Windows 7, the message Bios Bad appears.

Date 08/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I came to a conclusion.
I have tested with v1.89, v1.A9, v1.B1 and v1.B2c.
The E2B partition must not be larger than max. 99GB.
Then no version will show e2b.cfg is missing or corrupt.
V1.89, v1.A9, v1.B1, v1.B2c 99GB + 138GB SWAP >> BIOS BAD
Interested for you? : If E2B partition in v1.89 greater than 99GB,
I get more information.
Message: Fatal! Inconsistent data read from (0x80) 354345113 + 127
Fatal! Inconsistent data read from (0x80) 354345232 + 2
Error: No such command: ... progamming code? ...
e2b.cfg is missing

Date 08/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

So it will depend on the size of both the first and second partition and where each partition starts. What are the sizes and start positions of the two partitions?
The limit should be 128GiB (or 137GB).
So are you saying a 110GB first partition behaves differently from a 99GiB partition? The start sector of the partition is important not just their size. Even if your 2nd partition is only 3GB but starts at the end of the drive, it will fail.
What folders/files are on the 2nd data partition?

Date 08/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

EaseUS shows for E2B partition:
First Physical Sector: 2048 (Cyl: 0, HD: 32; Sect: 33)
Last Physical Sector: 206551039 (Cyl: 12857, HD: 52, Sect: 59)
All physical sectors: 206548992 (98,49GB)
DATA partition:
First Physical Sector: 206551040 (Cyl: 12857, HD: 52; Sect: 60)
Last Physical Sector: 500170751 (Cyl: 31134, HD: 48, Sect: 18)
All physical sectors: 293619712 (140,01GB)
For testing, the second data partition was empty

Date 08/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Is the Last Physical Sector: 500170751 (Cyl: 31134, HD: 48, Sect: 18)
the very end of your drive (check with RMPrepUSB - Drive Info - 0)? If so you may get errors. You should always leave the last 1MB of a drive unused for best BIOS compatibility. EaseUS Partition Master has a bad habit of using right up to the very last sector of a disk which can cause problems (grub4dos nnn + 127 error messages).
I cannot reproduce the '/_ISO/e2b/grub/E2B.cfg is MISSING or CORRUPT! Press ENTER to continue...' message. I used a 119GB E2B partition and a 119GB DATA partition and swapped them over using RMPrepUSB Crtrl-O and then tested it on an EeePC which has the 128GB USB BIOS bug. I got the BAD BIOS message but not the E2B.cfg message. Strange.. I don't know why you get this message...

Date 10/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Hello,
I have recreated the USB stick:
First partition E2B 119GB, second partition DATA 119GB.
DATA partition created with AOMEI Partition Assistant:

First Physical Sector: 2048 (Cyl: 0, HD: 32; Sect: 33)
Last Physical Sector: 250591231 (Cyl: 15598, HD: 148, Sect: 38)
All physical sectors: 250589184 (119.49GB)
DATA partition:
First Physical Sector: 250597935 (Cyl: 15599, HD: 0, Sect: 1)
Last Physical Sector: 500166655 (Cyl: 31133, HD: 238, Sect: 17)
All physical sectors: 249568721 (119,00GB)

RMPrepUSB_Drive Info:
Disk Signature bytes (1B8h-1BBh) = 21 E0 A7 AC

Partition 1 SIZE = 121859,727MB Type: 07 NTFS
START POS = CYL: 1023 HD: 254 SEC: 63 END POS = CYL: 1023 HD: 254 SEC: 63
START (LBA) = 250,597,935 (0EEFD22F) SIZE (LBA) = 249,568,721 (0EE01DD1) [End = 500,166,655]

Partition 2 SIZE = 122358MIB Type: 07 NTFS * ACTIVE *
START POS = CYL: 0 HD: 32 SEC: 33 END POS = CYL: 1023 HD: 254 SEC: 63
START (LBA) = 2.048 (00000800) SIZE (LBA) = 250,589,184 (0EEFB000) [End = 250,591,231]

P1 start = 250,597,935 (128,306,142,720 bytes) end = 500,166,655 (256,085,327,360 bytes)
P2 start = 2,048 (1,048,576 bytes) end = 250,591,231 (128,302,710,272 bytes)

Drive 6 SanDisk Extreme Pro F / W Rev. = 0 Serial No. = [bytes = 00 00 00 00 00 00 00 00]
Reported size 256,087,425,024 bytes (238.5GiB) Last LBA 500,170,751
RMPrepUSB Max 256,077,642,240 bytes (238,4908GiB) Last LBA 500,151,644
Is that how it should be?

I got the BAD BIOS message but not the E2B.cfg message :-)
This ASUS P6T board has another peculiarity.
On the USB port of the rear panel:
When I click USB Driver U I briefly see the message:
Error 81 No USB Drive found, USB Drive enumeration failed.
On the front panel: USB found.
Tested with 2 SanDisk Extreme Pro 256GB.
It is crazy but the e2b.cfg message does not appear anymore.

Date 10/06/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Thanks for re-testing. That is what I expected and yes, the unused sectors at the end of the drive is prudent.
The P6T has two USB controllers (6+6 USB 2.0), so I guess one is compatible with the grub4dos USB driver code and the other controller is not.

Date 10/06/2019

By Krauter_German

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: Re: 137GB BAD BIOS BUG

Reply

Thanks for your help and great respect for your tremendous knowledge.

Date 28/05/2019

By Batfink

Subject UEFI

Reply

Wow, Ok, So i had visions of sugar plums dancing in my UEFI menu, Launching Windows10 Pe's of my making, Modified Pe's, UEFI friendy password changers, UEFI friendly cloning software etc.
Not so Huh ;)
It's very picky, I've even tried cheating and extracting ISO's, renaming the UEFI payloads and booting them extracted and compressed and it's given me no love.
You're almost better off making a huge UEFI capable windows 10PE with every portable tool you can think of (Which I've done on the MBR one and can just burn as UEFI).
Not a criticism, just sharing what I've discovered, I definitely appreciate what you've built here.
I think the only thing I'll miss in a Windows 10PE is MEMtestX86, I know it can be booted as UEFI, but having it as a boot option prior to the Windows 10PE UEFI booting is still eluding me (Not a question, just a ponder) hmmm

Date 28/05/2019

By SteveSi

Subject Re: UEFI

Reply

There is no multiboot UEFI menu unless you use the E2B grub2 menu system which is limited.
Except for grub2 and syslinux-EFI with some linux ISOs (which are limited in what they can do), EFI booting requires the files to be in a 'flat-file' structure. This means you cannot have two OS's with the same files/directories on the same partition.
The E2B grub2 menu will let you have multiple PEs and linux's in a large menu, but you basically have to hand-craft each menu entry. There is no simple automatic or even semi-automatic way.
WinSetupFromUSB may be a better option for UEFI for you (mainly Windows-based source files) but it is limited too.
The MBR CSM menu can be customized and have animations, etc. using grub4dos commands and you can put the mods in the CUSTOM folder so that any new .imgPTN file you make will look the same.
The latest UEFI eBook #3 describes how you can add MemTest86 (or most other EFI small payloads) into your main UEFI .imgPTN file and includes URLs to ready-made UEFI files.
The .imgPTN solution allows you to Secure Boot from any signed UEFI payload or from a very wide range of other UEFI payloads (just not all from the same menu at the same time).
By adding a 2nd FAT32 partition containing a UEFI-bootable WinPE (see UEFI eBook #3 which includes download URLs for required WinPE files) you can boot on a pure UEFI system and choose any .imgPTN file that you want to boot to.
P.S. Latest BETA files in Alternate Download Area have improved E2B_Editor and MakePartImage CSM menu functions (see Change History for details).

Date 28/05/2019

By Batfink

Subject Re: Re: UEFI

Reply

That's actually what I've done as an experiment .. The dual partition usb stick.. *sigh*, I suppose I could use it primarily for mbr like the pictures I've shown you, replicating that to a new dual partition stick isn't a problem and then keep MEMTESTX86 and a few other maybe useful apps that are on the excel list in the efi partition... But ultimately as you said the items on the Excel list have limited functionality depending on your needs... Looking at the list there's almost nothing there I can't do on a UEFI secure boot enabled Windows 10pe.
Ultimately I was going to use two usb sticks anyway, even though your dual partition supports mbr grub I was going to ignore it and have one for mbr and one for uefi.
I know I can do the whole change a single file to imgptn, boot from it and then change it back, but by then I could have booted a winpe environment in the same length of time it takes to change it to imgptn and back again.
Just out of curiosity, which of the Linux uefi payloads on the list contains a MEMTESTX86 option in its menu before it boots the Linux.

Date 28/05/2019

By Batfink

Subject Re: Re: Re: UEFI

Reply

Sorry, I was just rereading the last bit of your message, so I can have the GRUB mbr menu on the first partition and a UEFI WINPE System and boot any imgptn file... Does it have a menu system or does it boot to a Windows desktop?

Date 28/05/2019

By Batfink

Subject Re: Re: Re: Re: UEFI

Reply

If it boots to a WINPE quick select sort of menu then I'll look at the books, I presume I need books 1&3, if it boots to a windows desktop and uses that as a launcher, I've got win pe environments that can already do everything I need, really I wanted a nice easy to select menu that comes up very fast (obviously not as fast as grub since it's a PE) but something with some kind of selectable menu.. Is there a place I can look at what it looks like or see it working.
Haha I'll stop bothering you now... I appreciate all your help.

Date 28/05/2019

By SteveSi

Subject Re: Re: Re: Re: Re: UEFI

Reply

The E2B grub2 menu system uses two partitions, the first is a .imgPTN file with grub2. The second is your existing 2nd partition which can contain linux ISOs, etc. (as well as your WinPE boot files, etc.)
http://www.easy2boot.com/uefi-grub2-ptn2/
The WinPE UEFI 2nd ptn just allows you to run SWITCH_E2B to choose a .imgPTN - you then need to reboot. Use the SITE MAP!
http://www.easy2boot.com/add-payload-files/refind/

Date 26/05/2019

By Batfink

Subject Fastload Caching menu spacing

Reply

Hahaha I hate asking for your help, I feel i should be able to work it out myself but out of all the things I've built this USB stick to do, Your menu is always the hardest thing for me :) .
Is there a way when you enable FASTLOAD.YES to not be directly under the bottom menu option.
https://imgur.com/6tPp528
This link shows the top one as it looks by default, and the bottom one is a photoshop i made to ask if it can be done to look like that or something along those lines.
As soon as I find out if this is written in stone or can be spaced out a bit I've finished my legacy stick, Then I'll be moving on to the UEFI...SMH hahaha I don't even know where to start.

Date 26/05/2019

By Batfink

Subject Re: Fastload Caching menu spacing

Reply

Oooops sorry, I thought the two pictures would appear in the same link.
https://imgur.com/u0mmtaB
This is the photoshop one.

Date 26/05/2019

By SteveSi

Subject Re: Re: Fastload Caching menu spacing

Reply

Hi
FASTLOAD is controlled by \_ISO\MAINMENU\ZZSubMenuAll.mnu
If you look at the start it has
# --- FASTLOAD ---

iftitle [if not exist CD && if not exist NOFLDMNU && cat --locate=NO ()/FASTLOAD.YES > nul] $$STRhMFE
# use current menu
echo YES > /FASTLOAD.YES && set MFOLDER=/_ISO/MAINMENU
# update cached menu file
cat (md)0xa000+0xA0 > /_ISO/e2b/grub/FASTLOAD.MNU
configfile (md)0xa000+0xA0

iftitle [if not exist CD && if not exist NOFLDMNU && cat --locate=YES ()/FASTLOAD.YES > nul] $$STRhMFD
# Disable fastload
echo NO > /FASTLOAD.YES && set MFOLDER=/_ISO/MAINMENU
configfile /_ISO/e2b/grub/menu.lst

# --- FASTLOAD STATUS INDICATOR

iftitle [if not exist NOFLDST if exist STALE && cat --locate=YES ()/FASTLOAD.YES > nul] $$STRmFS1
if not "%GFX%"=="" configfile (md)0xa000+0xA0
root ()

So NOFLDMNU will stop the menu entries from appearing
However the Status indicator line is suppressed by NOFLDST.
So if you use
set NOFLDMNU=1
set NOFLDST=1
in your MyE2B.cfg file, then it should suppress them.
Now if you want to add your own .mnu file for Fastload, then copy these lines and change them as you wish.
Obviously, you will need to remove the 'if not exist NOxxxxxx' bit or they won't display!
http://www.easy2boot.com/speeding-up-e2b/
(Tip: Use the Search box and search for FASTLOAD if you want to find out about FASTLOAD - or - look in Sample_MyE2B.cfg for all possible settings ;-)

Date 26/05/2019

By Batfink

Subject Re: Re: Re: Fastload Caching menu spacing

Reply

Thank you Sir, You are a gentleman and a scholar, That worked perfectly.
The problem is I'm a computer technician, not a programmer.

Date 25/05/2019

By Krauter_German

Subject Multiple partitions

Reply

Hello, I still have a USB stick with Easy2Boot v1.89 and a second primary partition for data. If I make the data partition visible in Windows 7 with RMPrep Ctrl-O-2 I can still boot from e2b. This no longer works with the newer Easy2boot versions and ends with an error. Only after restart can then be booted from the E2B partition.
With Windows 10, it does not matter because both partitons are recognized.
Since Windows 7 is still very common it makes sense to use the data partition but to boot from e2b. Can this feature be integrated into the new e2b version?

Date 25/05/2019

By SteveSi

Subject Re: Multiple partitions

Reply

I don't see how it can have worked? When you boot to Windows 7 Setup, the Win7 ISO will be on the 2nd partition which is inaccessible to Windows 7 PE and so it will not be able to find the ISO.
1. Can you retest with v1.89 and confirm you can fully install from a Win 7 ISO.
2. What is the exact error message that you get with E2B v1.B1?
3. You say after running RMPrepUSB Ctrl-O you must do a reboot before it will boot to the E2B menu. So how are you managing to run RMPrepUSB and then boot to E2B without rebooting the PC?

Date 25/05/2019

By Krauter_German

Subject Re: Re: Multiple partitions

Reply

Hello, Maybe I have expressed myself inaccurately by the bad English. I have 2 Windows 10 PC and a Windows 7 PC. The USB stick with Easy2boot v 1.89 and visible data partition can boot on the Windows 7 PC, Easy2boot and I can use Acronis, Aomei, Easeus or other software, all imgPTNAUTO files.
The Windows 7 install imgPTNAUTO will start to select the partition selection for the installation, then I canceled.
I can later gladly install for testing on other SSD completely.
If I use another USB stick with Easy2boot v 1.B0A on the Windows 7 PC with visible data partition, Acronis, Aomei ... imgPTNAUTO in the main menu can not be executed.
(hd0,0) EASEUS_PART_ASSIST__13.5_PE.imgPTNAUTO
root ()> nul
ERROR 22: (http://grub4dos.chenall.net/e/22) No such partition
Press any key to continue ...

Date 25/05/2019

By SteveSi

Subject Re: Re: Re: Multiple partitions

Reply

ah, OK. So you are saying that switching to a .imgPTNauto file when the two partitions are switched produces an error.
I think this is now fixed in todays version of E2B v1.B2b in the Alternate Download Area. Please update your E2B drive to it and try again.

Date 25/05/2019

By Krauter_German

Subject Re: Re: Re: Re: Multiple partitions

Reply

Yeah, it's working perfectly.
Many thanks and best regards

Date 19/05/2019

By Batfink

Subject Space after Subdirectories

Reply

I've been beavering away at this for ages, modding PE Windows, 7Zip compressing executables etc and I'm finally close to finishing the Legacy version (haha haven't even started the UEFI version), But for the life of me I can't figure out if there is a way to put a space after a Sub Dir, especially between the F8 to rebuild the main menu...I know I can turn it off, but i actually want to keep it.
Menu's 23,24,25 & 26 are sub menu's, is there a way to put a space between Menu 26 and the F8 menu below it.
https://imgur.com/acOYAYi
Many Thanks for making such a great menu system, I've been able to get things to work that I've never had working before.

Date 19/05/2019

By SteveSi

Subject Re: Space after Subdirectories

Reply

The submenus and the F7-F10 menu entries are all in one .mnu file (\_ISO\MAINMENU\ZZSubMenuAll.mnu).
Now you can change the name of this file (so it is not overwritten by any future update) and edit it to add a blank menu entry before the F8 entry.
If you do run 'Update E2B' on the drive in the future, the update script will detect that you have renamed the ZZSubmenu.mnu file (because there wasn't one!) and ask if you want to delete the new copy that it has just added.
The other alternative would be to suppress the F8 menu entry and simply add you own ZZTF8.mnu file which has the same F8 menu code in it as used in ZZSubMenu.mnu.
P.S. Online chat facility is available on this website for quick help.

Date 20/05/2019

By Batfink

Subject Re: Re: Space after Subdirectories

Reply

I've scoured your Sample E2B config file, Googled laboriously how to make a blank menu entry (I know how to make a blank menu to produce a gap between runnable payloads but these are subdirectories), I've scoured your website but keep going in circles..it's not that there's not enough information, there's soooo much information.
Could you be a little clearer and throw a guy a bone :)
Seriously, I don't even know where to start..Do I need to make a physical blank menu on the USB stick..I already have some blank menu's and they don't show up because they're empty.

Date 20/05/2019

By Batfink

Subject Re: Re: Re: Space after Subdirectories

Reply

Nevermind, I found the bone myself.
What you meant was take the text from a physical blank zzz_blank.mn.mnu and insert it into the ZZSubMenuAll.mnu like this

title \n
root ()

Date 20/05/2019

By SteveSi

Subject Re: Re: Re: Re: Space after Subdirectories

Reply

yes - OR simply add another blank.mnu file and another F8 mnu file.
E2B orders files alphabetically, so
ZZSubMenuAll.mnu (unchanged) < sub menus listed (NOF8MAIN)
ZZTBlank.mnu < separator
ZZUMyF8.mnu < your F8 menu

Copy the F8 menu entry from the ZZSubMenuAll.mnu file into a new ZZUMyF8.mnu file but delete the 'if not exist NOF8MAIN' text so it is always seen.

Date 08/05/2019

By infuscomus

Subject load custom DSDT for XP?

Reply

Can Easy2boot load a custom DSDT table before loading XP ISO?
like add a kernel variable
acpi=/boot/dsdt.aml
then update grub?
sudo update-grub2
can I update grub when using easy2boot?

Date 08/05/2019

By SteveSi

Subject Re: load custom DSDT for XP?

Reply

E2B uses grub4dos not grub2.
So the answer is no!

Date 08/05/2019

By infuscomus

Subject Re: Re: load custom DSDT for XP?

Reply

are there any multiboot ISO software that use grub2?

Date 09/05/2019

By SteveSi

Subject Re: Re: Re: load custom DSDT for XP?

Reply

I think MultiSystem is based on grub2, or you can try the E2B grub2 menu system.
http://www.easy2boot.com/uefi-grub2-ptn2/

Date 13/05/2019

By infuscomus

Subject Re: Re: Re: Re: load custom DSDT for XP?

Reply

Thanks,
I will try that

Date 28/04/2019

By Krauter

Subject Update 1.A9 to 1.B0

Reply

Hi, I have updated Easy2Boot from version 1.A9 to 1.B0. I use a master password. If I now enter the master password and confirm with Enter nothing happens. Only when I press a button afterwards loads the main menu.

Date 28/04/2019

By SteveSi

Subject Re: Update 1.A9 to 1.B0

Reply

Try updating to the latest Beta v1.B0A.zip

Date 30/04/2019

By Krauter

Subject Re: Re: Update 1.A9 to 1.B0

Reply

Hi, I have the menu.Ist (\ _ISO \ e2b \ grub \) from v1.B0 with the newer menu.Ist from v1.B0A replaced.
The input of the master password works perfectly again.
I have one more question: if I choose in the main menu HDD0 [F7] it works for most PC, with a PC with M.2 NVME SSD remains a flashing cursor and I have to restart the PC. Can it be because it is PCIe and not SATA.
Thank you for solving the problem with the master password.
Best wishes

Date 30/04/2019

By SteveSi

Subject Re: Re: Re: Update 1.A9 to 1.B0

Reply

Nvme Drive should be listed as bios disk 1 with usb as drive 0. Check in utilities menu. Configure bios for legacy support of the drive. Ensure NVMe drive is NOT set to RAID.
Some BIOSes will only UEFI-boot from NVMe drives. The F7 key will only MBR-boot.

Date 08/05/2019

By Krauter_German

Subject Re: Re: Re: Re: Update 1.A9 to 1.B0

Reply

Hi,
the F7 error is probably due to the GPT partition style of the NVMe drive.
The small detour via F9 is OK.

Date 28/04/2019

By mariano

Subject virus?

Reply

antivirus trend micro tells me that Easy2Boot_v1.B0.exe contains virus

Date 28/04/2019

By SteveSi

Subject Re: virus?

Reply

VirusTotal does not show any problem with Trend Micro or 70 other antivirus packages.
http://tiny.cc/fowu5y
So it is safe to assume it is a false positive. You can always download the .zip file instead of the .exe.

Date 22/04/2019

By infuscomus

Subject install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

I am attempting to install Windows XP via WinPE - but I have run into a problem when the install complains about "Basic Disks created by Windows NT 4.0" and as far as I can tell in computer management, all my disks are dynamic

why would the installer complain about basic disks? have I missed something?

Date 22/04/2019

By SteveSi

Subject Re: install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

Not quite sure what you mean? Are you booting from an XP ISO to XP Setup in the normal way, or some other way? Are you installing to a blank, clean disk? Are you attempting to install XP to a dynamic disk using XP Setup? When installing XP it has to be to a Basic disk - you can then convert it to Dynamic if you wish (AFAIK).
https://www.techrepublic.com/article/solutionbase-managing-dynamic-disks-in-windows-xp/

Date 23/04/2019

By infuscomus

Subject Re: Re: install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

I am using the "Install Windows XP using WinPE" method
http://www.easy2boot.com/add-payload-files/windows-install-isos/install-xp-using-winpe/
yes I am installing to a clean disk
I get the error after I enter the license key and select language

Date 23/04/2019

By SteveSi

Subject Re: Re: Re: install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

What x86 32-bit WinPE OS did you use? Windows 10?
I think you need to use Windows 7 PE which does work.
I get the same error with WinPE 10 1607.
Win8 works. So Win10 is different in some way!

Date 23/04/2019

By infuscomus

Subject Re: Re: Re: Re: install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

I have been using Windows 10 PE
I will try Windows 7 PE

Date 25/04/2019

By infuscomus

Subject Re: Re: Re: Re: Re: install XP via WinPE - setup cant continue - "Basic Disks created by Windows NT 4.0"

Reply

Windows 8 PE worked although I thought on reboot it would start Step 2 of XP install not Step 1

Date 15/04/2019

By utilman

Subject Samsung T5 SSD - how have 2nd partition visible with UEFI-boot

Reply

I have 2 primary partitions on the T5. MBR boot works, and second partition (NTFS) is visible and usable. When I change with SWITCH_E2B.exe to a imgPTN for UEFI-boot, the 2nd partiton is not visible after booting. When I have a look disk management in windows I see a unused diskspace and are able to make a partition. But partition should already be there. Can someone help me out on how to make this work. So that the 2nd partition is usable with MBR and UEFI boot?

Date 15/04/2019

By SteveSi

Subject Re: Samsung T5 SSD - how have 2nd partition visible with UEFI-boot

Reply

The .imgPTN file extension clears the MBR partition table and uses Ptn1 for the .imgPTN file.
If you want to keep the 2nd (and 3rd) partitions, simply change the file extension to .imgPTN23.
http://www.easy2boot.com/add-payload-files/wizard/primer/

Date 15/04/2019

By utilman

Subject Re: Re: Samsung T5 SSD - how have 2nd partition visible with UEFI-boot

Reply

thx SteveSi !! Exactly what I was looking for. Sometimes hard to find between all the documentation on the website :)... simple solution, but works like a charm. Renamed the files, and now works.. Now I can boot UEFI from acronis/easeus WinPE and backup to 2nd partition on external SSD.. great!

Date 06/04/2019

By Krauter_Germany

Subject SanDisk Extreme PRO 128GB Solid State USB-Flash-Laufwerk USB 3.1

Reply

Hello,
I've been using Sandisk Extreme PRO USB 3.0 Flash Drive with E2B for a long time and I'm still excited. I wanted to buy Sandisk Extreme PRO USB 3.1 Solid State Flash Drive, although there are always problems with the Flash Drive (Amazon reviews).
On Amazon Germany I read in questions and answers:
I want to install a bootable linux on the stick. Is the stick USB 3 bootable?
SanDisk Customer Care: We would like to point out that we did not test the sticks like bootable drives and we do not recommend this usage. Because our USB sticks are not suitable as bootable devices in contrast to our internal SSDs. Using a SanDisk USB flash drive as a boot device is not covered under our warranty.
What is your opinion on this statement? I am now testing an NVME M.2 SSD with external housing (JMS583 chip).
Many Thanks

Date 06/04/2019

By SteveSi

Subject Re: SanDisk Extreme PRO 128GB Solid State USB-Flash-Laufwerk USB 3.1

Reply

Hi, if you want a fast, removable USB flash drive I recommend the Extreme Pro 3.1. I have 5 SanDisk Extremes and never had a problem using them as E2B drives in over 5 years.
All MLC Flash memory wears out and has a limited number of erase/write cycles of about 30,000. Unlike SSDs, flash drives don't tend to have expensive controllers which fully handle wear leveling, so it all comes down to how you are going to use the drive.
As a USB multiboot drive, booting to Linux LiveCD ISOs or WinPE is not going to do many writes to the drive. However, if you intend to run WindowsToGo or Linux from the Flash drive all day and every day and have a swap file on the drive and hyberfile, then you will probably wear it out after a year or so.
SanDisk cannot give a 3-5yr Warranty if you use a drive in this way (so just don't tell them!).

Date 27/03/2019

By Mihkel Kukk

Subject disable Wimboot

Reply

Hey, Would it be possible to disable Wimboot, as in, I'd like it that if I choose the windows 10 install ISO, it would start the installation like if it would boot straight into a windows install disk. as in I wouldn't need to press any keys until it'll prompt me into the windows installer.

I'm asking it because I would like to not have any key files or anythings as this is for a commercial use, I would like to have my windows install as clean as possible, whilst still be able to multi boot to different tools on the drive.

Thank you!

Date 27/03/2019

By SteveSi

Subject Re: disable Wimboot

Reply

Hi
I am assuming that you don't really mean that you don't want to run WIMBOOT...
If you dont want the XML choice, then as soon as you see the message to press ENTER quickly to run Repair\Setup then just press ENTER quickly.
The alternative is to copy the Windows Install ISO to some other folder (e.g. \_ISO\WIN).
The keys used are general purpose installation-only keys. They are perfectly 'legal' because they cannot be activated. They are for installation of Windows only and are actually made public by Microsoft for that purpose.

Date 20/03/2019

By Carlos

Subject Cannot boot Linux ISOs with persistence.

Reply

Hello! I've been trying to boot Linux ISOs (Xubuntu 16.04.3 i386 and KDE Neon amd64 in particular) with persistence, but i get an error message that says that the persistence file was not found.

I'm running the latest E2B release, 1.A9 and using an edited ubuntu-13.04-desktop-i386_Persistent.mnu file from the sample mnu files folder where i changed the ISO and persistence file paths accordingly.

I created a 1024 MB persistence file using Make_Ext.exe at the root of my flash drive, named it "neon-rw" for KDE Neon but while trying to boot it says the neon-rw persistence file was not found. I even tryed moving the neon-rw file inside the MNU folder and changing the set PF line to set PF=$HOME$/neon-rw, but it still said persistence file was not found.

The ISO files are detected fine, before showing the error message, it says the file system is joliet. Also, both ISO files boot fine without persistence. My flash drive is formatted NTFS.

Date 20/03/2019

By Stevesi

Subject Re: Cannot boot Linux ISOs with persistence.

Reply

Can you post here the exact line that you used for the PER line in the menu?
Also check that the file exists by booting from the E2B drive and use the utilities menu to list the root directory files.
Also test the menu using the test_using_qemu CMD file under Windows.

Date 20/03/2019

By Carlos

Subject Re: Re: Cannot boot Linux ISOs with persistence.

Reply

I've put the KDE Neon ISO, edited MNU file and neon-rw file inside /Linux/MNU folder. Using the ls dir command from the utilities menu lists the 3 files correctly.
The lines i used for the MNU files are the following:
"set ISO=$HOME$/xubuntu-16.04.3-i386.iso"
and
"set PF=$HOME$/neon-rw"
Both without quotation marks.

Date 20/03/2019

By SteveSi

Subject Re: Re: Re: Cannot boot Linux ISOs with persistence.

Reply

see below...

Date 20/03/2019

By SteveSi

Subject Re: Re: Re: Re: Cannot boot Linux ISOs with persistence.

Reply

P.S. You said that you were using ubuntu-13.04-desktop-i386_Persistent.mnu
Well that mnu file uses PER not PF!!!
...
set ISO=$HOME$/ubuntu-13.04-desktop-i386.iso
set PER=/ubuntu1304-rw

Date 08/03/2019

By mac

Subject How do I install W7 & W10, as Dual-Boot OS's?

Reply

I've built a new PC.
I want to be able to Dual-Boot by installing W7 & W10,
preferably by installing each of them into their own GPT partition on one HDD.
So can I install each of these OS from their original install DVD's ?
And what should my BIOS settings be ?
I seem to getting issues, so could you provide a detailed guide as to how to do this?
Hoping you can help,
Many thanks.

Date 08/03/2019

By SteveSi

Subject Re: How do I install W7 & W10, as Dual-Boot OS's?

Reply

Hi
First convert each ISO to a .imgPTN file and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in) and install Win7.
Then reduce the OS partition to make room for the Win10 OS.
Then boot to the Win10 .imgPTN file (after switching it in) and install Win10.
Note that to make the Win7 imgPTN bootable you will need to add the bootx64.efi file - see http://www.easy2boot.com/add-payload-files/win7-uefi/
Also note that Win7 is very old and does not contain drivers for USB 3 - so you may have problems installing Win7 from a USB drive!
or you could always read my eBook... ;-)

Date 08/03/2019

By mac

Subject Re: Re: How do I install W7 & W10, as Dual-Boot OS's?

Reply

Hi Steve,
Many thanks for your reply, seems like a great website!
I'm new to these problems, so I have a few queries & questions:
Q1: Firstly, I was told that installing W7 & W10 with UEFI enabled in my BIOS
would 'Cause Problems' because W7 was developed B4 UEFI ?
Q2: Also, Do I need UEFI enabled in my BIOS ?
Q3: What exactly do I need to 'SET' in my BIOS ?
And in your reply you said...
First convert each ISO to a .imgPTN file
(Q4: How do I do that? *)
...and add the two files to the E2B drive.
Then UEFI-boot from the Win7 x64 .imgPTN file (after switching it in)
(Q5: * after switching it in * So how do I do that ?)
...and install Win7.
...Also note that Win7 is very old and does not contain drivers for USB 3 -
so you may have problems installing Win7 from a USB drive!
(Q6: * Win7 does not contain USB 3 drivers * So can I use USB2 ?)
...or you could always read my eBook... ;-)
(Q7: Does that explain everything in more detail ? If so where's the link ? )
Many thanks

Date 08/03/2019

By mac

Subject Re: Re: Re: How do I install W7 & W10, as Dual-Boot OS's?

Reply

I also forgot to ask:
Q8: What preparation do I need to make to my HDD before I use easy"boot to install the Os's ?
Q9: Eg BIOS settings / Formatting HDD to GPT etc ?
Thanks

Date 08/03/2019

By SteveSi

Subject Re: Re: Re: Re: How do I install W7 & W10, as Dual-Boot OS's?

Reply

Q1. If you have 2TB or larger disks, then you need GPT partitions. If you need GPT partitions then you need UEFI. If your disk is smaller than 2TB there is no need for GPT and no need for UEFI. Win7 64-bit works OK with UEFI+GPT.
Q2. See Q1 above.
Q3. For BIOS - just do not disable UEFI. preferably also enable CSM.
Q4. - Q9. Please use the Site Map or Google for your answers. This is an E2B forum, not a 'How do I install Windows' forum.
Read http://www.easy2boot.com/useful-things-to-know/

Date 03/03/2019

By Harold Robinson

Subject XP wiping out boot record on E2B flash drive

Reply

I am trying to install XP on a MSI MS-6570 XP wipes out the boot record of the E2B flash. I am using the boot menu (F8) with the same issue. I am using a SIL3114 SATA card and a Kingston 240GB SSD.

Date 03/03/2019

By Harold Robinson

Subject Re: XP wiping out boot record on E2B flash drive

Reply

I can tell this because after the initial dos screen where XP copies the basic files and reboots, this error comes up "Windows could not start because of a computer disk hardware configuration problem.
Could not read from the selected boot disk. Check boot path and disk hardware.
Please check the windows documentation about hardware disk configuration and your hardware reference manuals for additional information.
When I remove all disks except the E2B flash this error comes up. anyway else and I get the standard "No boot disk found" error. "BOOT DISK FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"

Date 03/03/2019

By Harold Robinson

Subject Re: XP wiping out boot record on E2B flash drive

Reply

When I remove the E2B USB drive and insert it into the PC that I built the drive with, and press with "TEST with QEMU I see the same "Windows could not start" error

Date 03/03/2019

By Harold Robinson

Subject Re: XP wiping out boot record on E2B flash drive

Reply

After removing all drives from BIOS, i have stopped XP from wiping out the boot record on the flash drive but the second step for the xp install only copies the image to ram disk and then reboots to the E2B menu.

Date 03/03/2019

By SteveSi

Subject Re: Re: XP wiping out boot record on E2B flash drive

Reply

It sounds like the first hard disk in the system is not the disk you are installing XP onto? It needs to be the first hard disk (if you boot to E2B - Utilities and use List BIOS Disks - it should list hd1 as the SSD drive).
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD.
Step 2 assumes that you have installed the boot code to Disk 0.
When you run Step 2 - you should see a message like
'Mapping (hd0) to (hd1) and (hd1) to (hd0)
SPACEBAR=Pause, ENTER=Start now - STARTING IN 5 SECONDS...'

When you see the last message - quickly press the C key and then press ENTER key to get to the command line. Then type

find
ls (hd0,0)/
ls (hd1,0)/
ls (hd2,0)/

now if one of these lists the file /ntldr on the XP hard disk, type the following (assuming that (hd1,0) has the XP files...

root (hd1,0)
chainloader +1
boot

Date 03/03/2019

By Harold Robinson

Subject Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Hi Steve, Yes I do have an IDE controller enabled. It has a optical drive attached. I will do as you suggested and get back to you. I saw your response after giving up. The file copy takes such a LOOOOOOONNNNNGGGG time. Its easily 40 minutes for each try.

Date 03/03/2019

By Harold Robinson

Subject Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Steve: >It sounds like the first hard disk in the system is not the disk you are installing XP onto? It needs to be the first hard disk (if you boot to E2B - Utilities and use List BIOS Disks - it should list hd1 as the SSD drive).
Do you have both an internal IDE controller enabled in the BIOS and the SATA card? If so disable all controllers and disks except for the SATA card and SSD."

Yes I did have the IDE controller enabled. As of this posting it is Disabled (both controllers)

I ran List Bios disks and here is what came out:
(fd3): Volume name is "(unsupported)".
Filesstem type is fat12, using whole disk
(hd0,0): Volume name is "E2B"
File System type is ntfs, partition type 0x07
(hd0,1): Volume name is "PTN2"
file system type is fat12 partition type is 0x21
=================hd0===============
drive 0x80(LBA): C/H/S=1885/255/63. sector count/size=30282525/512
Partition num: 0, active, filesystem type is ntfs, partition type 0x07
Partition num: 1, filesystem type is fat12, partition type 0x21

Contents of (hd0,0) E2B
{looks like it lists some files}
Contents of (hd0,1) PTN2
System\ Volume\ Information
==========
Press a key for current drive map...
floppies_orig=1, Harddrives_orig=2, floppies_curr=0, harddrives_curr=2
Number of atapi CD-ROMs: 0
ram_drive=0x7f, rd_base=0x3FFAF000, rd_size=0x13000
Fr To Hm Sm To_c _H _S Start_Sector Sector _Count DHR
03 ff 00 88 8882 FE 3F 00000000001FFE40 0000000000000140 M=R
After waiting for 10 minutes, I pressed a key and it returned to the utilities menu.

Date 03/03/2019

By Harold Robinson

Subject Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

ok. After running the find command it returned the following:

(0xff)
(hd0,0)
(hd0,1)
(fd0)
(fd1)

ls (hd0,0)/ returned files that appeared to be on the e2b flash drive. I see "MAKE_E2B_USB_DRIVE (run\ as\ admin).cmd etc
ls (hd1,0)/ returned the same files. (yes I don't understand it but there it is.)
ls (hd2,0)/ returned Error 21: (http://grup4dos.chenall.net/e/21) The selected disk does not exist.
It seems your environment is not seeing the SSD drive.
I will hold off installing the XP OS from CD rom (as I know this does work) and work with you on this. If you want to take this to email let me know.
Sincerely,
Harold Robinson

Date 03/03/2019

By SteveSi

Subject Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Hi
You obviously need to enable the external SATA controller in the BIOS so the SSD can be seen by the BIOS (and XP).
If E2B warns you that no HDD was detected, then it is never going to boot from the SSD.
Ensure the first boot device in the BIOS settings is set to the SSD drive.
If the SSD is not visible in the BIOS settings, then it obviously can't boot from the SSD.
If XP Setup is trying to write the boot code to the USB drive, then there will be no boot code on the SSD so it will not boot in Step 2. You must configure the BIOS so the SSD is the first drive in the system and keep the E2B drive connected so that you can tell if it has corrupted it or not after Step 1. If the boot code has been written to the USB drive, then there is no point trying Step 2.
If any more problems - use the online Chat facility on this website (enable pop-ups if using FireFox) or Contact Me page.

Date 03/03/2019

By Harold Robinson

Subject Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

There is no BIOS setting to make the external SATA visable. I went into the SATA cards bios and there is no option in there either only menu selections dealing with creating a array, deleting an array, repairing an array, and an exit option. I am not seeing an error that tells me that there is no drive or hard disk present. I do see that when I run under QEMU when testing to make sure it will boot. The computers BIOS is set as follows:
Advanced BIOS Features
1st boot device [HDD-0]
2nd boot device [Disabled]
3rd boot device [Disabled]
Boot Other Device [Disabled]
I can list other BIOS settings if you wish.

Date 03/03/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Ignore QEMU - it is a virtual system and has nothing to do with your real system.
If the 1st boot device [HDD-0] is set - then what exactly is that HDD-0 device (with no USB drive or other storage device connected). Surely it must be the SSD if that is the only device connected?
If E2B does not give you a warning on boot, then it must see an internal BIOS HDD in the system.
Can you boot to E2B and go to the Utilities Menu and run the List BIOS devices option? hd0 should be the USB drive and hd1 should be the SSD.

Date 03/03/2019

By Harold Robinson

Subject Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

I can confirm that if I slipstream the SIL drivers into my ISO and burn that to a CD, XP will install successfully. So Your Easy2Boot drive is selecting the correct drivers. during XP's first stage installer (the text part) It does see the drive, it formats it and (that is when the USB key boot record is wiped out). the USB key is listed as Drive 0 and the SSD is listed as Drive 1, which is were we are having our problem.

Date 04/03/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

So does the E2B Utilities - List BIOS disks menu option list hd0 as the USB drive and hd1 as the SSD?

The issue here is that the BIOS must see the SSD.
Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it.

The boot code is transferred to the internal hard disk at the end of the copy files stage. So pulling out the USB drive just means that it cannot write the boot code and files to the USB drive (if it was going to). XP Setup will want to update the boot code on the 'boot' drive and E2B takes steps to ensure this happens by changing hdd0 to be the internal hdd instead of hd1.
For instance, if you run Step 1 and then allow it to reboot from the SSD, it should boot OK (it will fail later with an 'asms not found' error - but at least it will boot).
So your 'objective' is to run Step 1, when it starts the 10 second timer to reboot at the end - pull out the USB drive and allow it to boot to the SSD. If it does not boot - then Setup has gone wrong.
Once it does boot from the SSD, you can reboot and run Step 2 (which should then also work) and complete the install.
P.S. Make sure you use the F8 boot selection pop-up menu when booting to E2B - do NOT set the USB drive as the first boot device in the BIOS Settings menu.
If you do spoil your E2B drive, you should be able to fix it by running RMPrepUSB - Install grub4dos twice, once for MBR and once for PBR.

Date 04/03/2019

By Harold Robinson

Subject Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Steve:> "So does the E2B Utilities - List BIOS disks menu option list hd0 as the USB drive and hd1 as the SSD?"
Harold: No I just checked again and it only lists the USB drive as HDD0
Steve:>"The issue here is that the BIOS must see the SSD. Of course XP Setup can see the SSD because it loads the driver for it. But in order to boot from the SSD, the BIOS must be able to see it."
Harold: "After the computer BIOS has completed its post stage, I then see:
Sil 3114 SataRaid BIOS Version 5.4.03
Copyright (C) 1997-2006 Silicon Image, Inc.
Press <Ctrl+S> or F4 to enter RAID utility
0 KINGSTON SV300S37A24 223 GB"

My BIOS does not support SATA drives, hence I am using the SATA card. I don't even have an option in BIOS (I don't think) to see the drive because the BIOS of the SATA card had not been initialized yet.
If you want I can run freedos to see if I can see the drive. but under grub4dos (E2B) I am not seeing it. I am guessing you are using grub4dos.

Date 04/03/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Thanks for the clarification. So if E2B does not list the SSD SATA drive as a BIOS drive then installing XP from the E2B drive is not going to work.
BUT I don't understand why E2B does not warn you that it cannot see an internal hard disk when you boot to E2B??? If E2B does not detect an hd1 (the first internal hard disk) you should see that coloured warning text???

What should happen is that after switch-on, POST should run, it should add its Option ROM code into the BIOS and detect SATA drive, then it should allow you to boot from USB or from the SATA drive or go into the BIOS and see the SATA drive listed.
According to the SIL website, if you are not using RAID, you should update the firmware on the SIL card to use the 'IDE' base 'b' version of the firmware. Maybe this will help? http://www.latticesemi.com/en/Support/AnswerDatabase/4/7/8/4784
Do you still say that you can install XP from CD (with the only drive being the SSD drive) and it boots to XP OK? I am not quite sure how it could do that!
P.S. Update firmware+manual is here https://1drv.ms/u/s!AqlrQcdsFA-KsQhnt96X0lkfYfFs
Extract the files to the root of your E2B drive, boot to E2B and run DOS menu - boot to FreeDOS - choose default NTFS option to get to C: prompt. Now you can type UpdFlash and load the b5403.bin file (r is for RAID version).
Here is an excellent post from someone who seems to know where his towel is...
https://www.vogons.org/viewtopic.php?f=46&t=49471#p734172

Date 04/03/2019

By SteveSi

Subject Re: Re: Re: Re: Re: Re: Re: Re: Re: XP wiping out boot record on E2B flash drive

Reply

Please try v1.B0c Beta
http://tiny.cc/i4nr3y
If you try it before you update the SIL3114 firmware, it should give you plenty of warnings.
If you try it after updating the SIL3114 firmware, hopefully it will work :-). I have not changed E2B XP install functions though - it won't fix your issue (unless you update the SIL3114 firmware).

New comment

There is a LOT of information on this site which should cover all common questions and problems - please use the Site Map to find the page you need.

For specific problems, it is much easier for 1-to-1 communication to use the Contact Me form and I will reply via email.