Hello, NeoSmart Technologies.
I was trying to unroll my good old Windows 2000 partition image alongside installed Windows 10 x64.
In pursuit of doing this easy way I used EasyBCD to create boot menu item, and your excellent tool has placed in NST folder easyldr loader and made a copy of it named ntldr in root directory.
But when I tried to boot to Windows 2000, it gave me following error message:
Windows could not start because following file is missing or corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEM
Which I know is not true, becuse it is there and can be loaded in registry editor. But I suspect that I face the same issue as when I installed Windows XP SP3 alongside Windows 2000. XP has replaced ntldr of 2k with its own and then I saw the same error at 2k boot. After some googling I have found that with one of XP Service Packs ntldr was updated and maximal size of registry hive it can load was lowered. Replacing XP SP3's ntldr with 2k SP4's ntldr didn't let me boot XP in its turn. So I had to dig old ntldr from CD with Windows XP without service packs. With that ntldr booting both OS became possible.
My SYSTEM registry hive just suffers on a little overweight (8,16 Mb).
May I ask to address this issue in one of next versions of EasyBCD?
I was trying to unroll my good old Windows 2000 partition image alongside installed Windows 10 x64.
In pursuit of doing this easy way I used EasyBCD to create boot menu item, and your excellent tool has placed in NST folder easyldr loader and made a copy of it named ntldr in root directory.
But when I tried to boot to Windows 2000, it gave me following error message:
Windows could not start because following file is missing or corrupt:
\WINNT\SYSTEM32\CONFIG\SYSTEM
Which I know is not true, becuse it is there and can be loaded in registry editor. But I suspect that I face the same issue as when I installed Windows XP SP3 alongside Windows 2000. XP has replaced ntldr of 2k with its own and then I saw the same error at 2k boot. After some googling I have found that with one of XP Service Packs ntldr was updated and maximal size of registry hive it can load was lowered. Replacing XP SP3's ntldr with 2k SP4's ntldr didn't let me boot XP in its turn. So I had to dig old ntldr from CD with Windows XP without service packs. With that ntldr booting both OS became possible.
My SYSTEM registry hive just suffers on a little overweight (8,16 Mb).
May I ask to address this issue in one of next versions of EasyBCD?