Technology, Support, and News Forum

[Grav!ty Profile]

Copy and paste the files ntldr, boot.ini and NTDETECT.COM to the same place as you see the file bootmgr and the folder Boot. That is to the root of the C drive which is the one tagged (System).

Please post a screenshot of your disk management here so that we can check your boot.ini for you.

There really should be no reason why you are having such major issues with getting these two operating systems working off a dual boot menu, and I'm hoping I'll pick something up from the screenshot and some more questions following that.

[lormar Profile]

[quote="Grav!ty"]Copy and paste the files ntldr, boot.ini and NTDETECT.COM to the same place as you see the file bootmgr and the folder Boot. That is to the root of the C drive which is the one tagged (System).

The mentioned files already are on the C drive (system) which is the win7 partition working perfectly.

Cattura.JPG (140.84 KiB) Viewed 1098 times

[Grav!ty Profile]

Your boot.ini should show rdisk(0)partition(2) under both Default and Operating systems. You can check that by doubling clicking it.

Your BCD entries should show drive C for Win 7 and drive D for XP on the operating systems page of DualBootPRO.

Once that is as it should be, go to the System Bootloader page and select Install Win 7 bootloader>All Drives and then press Install bootloader. It's a good idea to take all DVD or CD media out of the drive, and particularly where it's Win 7 as there are duplicated boot system files on it that could confuse the boot configuration data. Reboot and test each entry and then let us know the result.

[lormar Profile]

>Your boot.ini should show rdisk(0)partition(2) under both Default and Operating systems. You can check that by doubling clicking it.


Ok, now the boot.ini file in the D partition root (winserver) is as follow:

[boot loader]
timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Server 2003 standard" /fastdetect
multi(0)disk(1)rdisk(0)partition(2)\WINDOWS="Microsoft Windows 7"


Are the quoted parts of the commands "microsoft windows..." significant or whatever works?

Can't open the boot file on win7 partition to check the content. I could replace it with the boot file on Winserver partition but I don't want to mess up the win7 installation (no other working OS on the machine)


>Your BCD entries should show drive C for Win 7 and drive D for XP on the operating systems page of DualBootPRO.

They do

[Grav!ty Profile]

Your boot.ini should read:

[boot loader]
timeout=30 default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows Server 2003 standard" /fastdetect


boot.ini is not used by Windows 7 at all.


Did you try to boot to both operating systems all ready? You need to fix your boot.ini and then delete the false W 7 entry and if necessary, create a new BCD entry for W 7 using DualBootPRO. YOu will also have to reinstall the Win 7 bootloader after doing the above.

[lormar Profile]

>Your boot.ini should read:

...

ok, done.





> create a new BCD entry for W 7 using DualBootPRO.


Nope. It's already there.

>YOu will also have to reinstall the Win 7 bootloader after doing the above.[/quote]


done.

Now winserver starts but says that hal.dll library is corrupt. The standard procedure in this case is to repair the installation using the win server 03 CD but it would overwrite what DualBootPro have done and render Win7 nor bootable or selectable.

[NT50 Profile]

Try changing the boot.ini to partition(3) instead of partition(2)

The hal.dll error means the boot.ini is pointing to the wrong disk / partition.

I'm thinking maybe the Win7 bootmgr is seeign the 63 meg partition as partition(1), Win7 is partition(2), nad XP as partition(3)

[NT50 Profile]

By the way, I figure you will keep having problems and may not get Win server running due to the fact you have it installed on a "Logical" partition. It needs to be a primary partition, this could also be leading to the cause of the hal.dll error.

[lormar Profile]

Doesn't work with part # 3 or even 4 (same hal.dll error message).
I don't think it's a matter of (non)primary partition: winserver can boot on my system if i have the recovery console to replace the boot stuff. Obviously the problem then is that win7 would "disappear"...

[lormar Profile]

Is there anything useful in the Boot Information:


Windows Boot Manager
--------------------
identifier {bootmgr}
device partition=C:
description Windows Boot Manager
locale it-IT
inherit {globalsettings}
default {current}
resumeobject {54b3db2d-0746-11df-a347-ef3ae4c4c44e}
displayorder {current}
{54b3db32-0746-11df-a347-ef3ae4c4c44e}
toolsdisplayorder {memdiag}
timeout 30

Windows Boot Loader
-------------------
identifier {current}
device partition=C:
path \Windows\system32\winload.exe
description Windows 7
locale it-IT
inherit {bootloadersettings}
recoverysequence {54b3db2f-0746-11df-a347-ef3ae4c4c44e}
recoveryenabled Yes
osdevice partition=C:
systemroot \Windows
resumeobject {54b3db2d-0746-11df-a347-ef3ae4c4c44e}
nx OptIn

Windows Boot Loader
-------------------
identifier {54b3db2f-0746-11df-a347-ef3ae4c4c44e}
device ramdisk=[C:]\Recovery\54b3db2f-0746-11df-a347-ef3ae4c4c44e\Winre.wim,{54b3db30-0746-11df-a347-ef3ae4c4c44e}
path \windows\system32\winload.exe
description Windows Recovery Environment
inherit {bootloadersettings}
osdevice ramdisk=[C:]\Recovery\54b3db2f-0746-11df-a347-ef3ae4c4c44e\Winre.wim,{54b3db30-0746-11df-a347-ef3ae4c4c44e}
systemroot \windows
nx OptIn
winpe Yes

Resume from Hibernate
---------------------
identifier {54b3db2d-0746-11df-a347-ef3ae4c4c44e}
device partition=C:
path \Windows\system32\winresume.exe
description Windows Resume Application
locale it-IT
inherit {resumeloadersettings}
filedevice partition=C:
filepath \hiberfil.sys
pae Yes
debugoptionenabled No

Windows Memory Tester
---------------------
identifier {memdiag}
device partition=C:
path \boot\memtest.exe
description Diagnostica memoria Windows
locale it-IT
inherit {globalsettings}
badmemoryaccess Yes

Windows Legacy OS Loader
------------------------
identifier {ntldr}
device partition=C:
path \ntldr
description Versione precedente di Windows

Windows Legacy OS Loader
------------------------
identifier {54b3db32-0746-11df-a347-ef3ae4c4c44e}
device partition=D:
path \ntldr
description Win Server 2003

EMS Settings
------------
identifier {emssettings}
bootems Yes

Debugger Settings
-----------------
identifier {dbgsettings}
debugtype Serial
debugport 1
baudrate 115200

RAM Defects
-----------
identifier {badmemory}

Global Settings
---------------
identifier {globalsettings}
inherit {dbgsettings}
{emssettings}
{badmemory}

Boot Loader Settings
--------------------
identifier {bootloadersettings}
inherit {globalsettings}
{7ff607e0-4395-11db-b0de-0800200c9a66}

Inherited Settings (20200003)
-----------------------------
identifier {7ff607e0-4395-11db-b0de-0800200c9a66}
custom:250000f3 0
custom:250000f4 1
custom:250000f5 115200

Resume Loader Settings
----------------------
identifier {resumeloadersettings}
inherit {globalsettings}

Device options
--------------
identifier {54b3db30-0746-11df-a347-ef3ae4c4c44e}
description Ramdisk Options
ramdisksdidevice partition=C:
ramdisksdipath \Recovery\54b3db2f-0746-11df-a347-ef3ae4c4c44e\boot.sdi