No physical memory is available at the location required for the Windows Boot Manager. The system can not continue.

(1) Can you boot to the eCS CD & enter maintenance mode to see whether the boot files are intact? Can you examine the IBM Boot Manager? I doubt it is in the MBR. Probably it is an executable invoked from within your BCD. I'm thinking the MBR points the way to that. I still want to see the BCD. Here is an article that shows how to repair an eCS boot, but this was an installation that uses the Windows Boot Manager (not the IBM Boot Manager)...

https://www.os2world.com/wiki/index.php/Installing_eComStation_2.1_and_Windows_8_with_Dual_Boot Installing eComStation 2.1 and Windows 8 with Dual Boot

(2) Let's see...

DiskPart <<<Enter DiskPart

List Vol <<<List volumes & letters

List Disk <<<List the disks

Select Disk 0 <<<Focus on Disk 0

List Part <<<List its partitions

Select Part 1 <<<Focus on partition 1

Detail Part <<<Show its details

=== Select each other partition & show its details ===

Exit <<<Leave DiskPart

I want to see that the System Reserved partition is marked active & that it is the only active partition. Also, we can put a letter on it & try to access the BCD directly.

I am not sure this got posted, so re-posting:

1. I don't think the eCS CDs work for this system and unfortunately I never created new ones.  I will verify they don't work. 2.  The system reserved partition is hidden on this system and supposedly is not used because this system is BIOS/MBR so as I understand it, the BCD should be in C:\boot but I can unhide it and use diskpart as you suggested and report, but it should not be active.Jordan

(1) How did you install eCS if the CD doesn't work?

(2) In a Legacy install, there is a BCD. Normally it will be in the System Reserved partition at S:\Boot (if S: is its letter). Otherwise, it is in the Windows partition at C:\Boot. Its executables will have an ".exe" file type (like bootmgr.exe, winload.exe & winresume.exe) instead of "efi". Also, there will be no Firmware Boot Manager.

(1) I made an image copy from another computer after modifying the config.sys and adding some files so that the new system works. I then put that image on the new computer. That worked until the disaster that I have been trying to solve since 9/16.

(2) My "System Reserved" partition doesn't have a drive letter because it is hidden (0x17) and presumably has never been used. The BCD *should* be at c:\boot which it is and I have looked at it and it seems correct. That being said, I cannot boot almost anything legacy (i.e. F12 Legacy Boot menu) including the Hard Drive and the CD/DVD without getting the dreaded "No physical memory is available at the location required by the Windows Boot Manager".

Can you please explain what is the Firmware Boot Manager that you say there won't be one? I don't know how that interacts with (and/or fouls up perhaps) my Legacy BIOS/MBR boot system.

Jordan

(1) How long was eCS working after you installed it that way? Was that a system image or sector-by-sector clone? I'm unsure the former gets the Boot Sector & MBR. Was it a clone of the entire HDD including the Win 10 partitions? Or how/when was Win 10 installed?

(2) Questions arising from those threads & article I posted...

(a) Did you install new hardware like ilounge & SasaSamardzic were doing?

(b) Was the hardware the same on the old & new computer?

(c) Did you disable/enable any hardware in BIOS?

(d) Did you change BIOS settings like ACPI or AHCI?

(e) Did you resize or move partitions?

(3) Well, a normal Legacy install has 3 partitions: System Reserved, Windows, & Recovery. Then, System Reserved gets the boot files & BCD. Recovery gets WinRE.wim. But it's possible for the Windows partition to take on the role of each of the other partitions. Then the files all will be on C instead.

(4) In a UEFI install, the BCD gets a Firmware Boot Manager, seen this way...

C:\WINDOWS\system32>bcdedit /enum {fwbootmgr}

Firmware Boot Manager

identifier {fwbootmgr}

displayorder {bootmgr}

                    {140ab3f9-3491-11e7-a4a0-952787f57a8e} 

                    {140ab3fa-3491-11e7-a4a0-952787f57a8e} 

timeout 1

It's a means of communication between Windows & BIOS. It shows the state of the BIOS boot screen & can be used to change it.