Dual boot config Vista U 64 and XP Pro

Discussion in 'EasyBCD Support' started by Saberous, Jun 7, 2008.

  1. Saberous

    Saberous New Member

    Joined:
    Jun 7, 2008
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    0
    Well it worked fine yesterday and now today its telling me that

    hal.dll is corrupted or missing

    i have 4 hhd

    disk0=vista
    disk1=xp
    disk2=media
    disk3=backup

    now this is my boot ini text from the vista side. i have ntld, boot and NTDETECT all copied onto my vista drive from xp

    [boot loader]
    timeout=30
    default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
    [operating systems]
    multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /NoExecute=OptIn

    does the one on xp have to match?

    also i unpluged all my hhd and plugged xp in and it give me an error saying

    BootMGR missing and also
    nvidia boot agent 249

    00044b01
    guid

    0a994a0d 034b 0400 0000 00000000000
     
    Last edited: Jun 7, 2008
  2. Mak 2.0

    Mak 2.0 Mod...WAFFLES!?!? Staff Member

    Joined:
    Jul 6, 2006
    Messages:
    4,270
    Likes Received:
    0
    Trophy Points:
    36
    Occupation:
    Online Support Tech
    Location:
    The Source
  3. Saberous

    Saberous New Member

    Joined:
    Jun 7, 2008
    Messages:
    2
    Likes Received:
    0
    Trophy Points:
    0
    I have done that already

    its weird

    when i go to select xp i either get
    ntoskrnl.exe or i get hal.dll error.

    i don't understand i get these errors and the fix is the same for the both, but yet i still get it
     
    Last edited: Jun 7, 2008
  4. Terry60

    Terry60 Coastline Designer Staff Member

    Joined:
    Nov 9, 2007
    Messages:
    9,697
    Likes Received:
    10
    Trophy Points:
    38
    Occupation:
    Retired System Programmer
    Location:
    Wiltshire, England
    Those errors are letting you know your boot.ini is wrong.
    I can see for a start that the one you posted is wrong.
    A boot.ini with only one system should point to the same place in the default line as in the last line.
    They should both point to rdisk (1)

    Only the boot.ini on the "active" partition of the 1st disk in the BIOS boot sequence will be used. (what's in the others won't be read)
     

Share This Page