NTLDR missing

Discussion in 'Acronis True Image Product Line' started by Alainp, May 18, 2005.

Thread Status:
Not open for further replies.
  1. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    Have you tried editing your boot.ini to match mine?
     
  2. MiniMax

    MiniMax Registered Member

    Joined:
    Mar 17, 2005
    Posts:
    566
    Problem is, boot.ini is read/used by NTLDR, but right now the partition loader is not able to find NTLDR in the first place o_O

    Still, I think the key to this puzzle is to figure out why bootcfg gets the rdisk(1) wrong...
     
  3. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    You may be right MiniMax, but I've fixed "NTLDR is missing" but fixing the boot.ini. See cause 4 on computerhope page.

    I now edit boot.ini with BartPE but I used to use pqfile.exe. What method do you employ?

    Alain has nothing to lose by trying this.
     
  4. MiniMax

    MiniMax Registered Member

    Joined:
    Mar 17, 2005
    Posts:
    566
    Sure - "NTLDR missing" message could be a "false" message in the sense that it is caused by something completely different. So by all means, fix that boot.ini so we can rule that out.
    I cheat ;) My C-partition is a 400 MB FAT32 with Win95 installed in C:\WINDOWS. My main WinXP is installed in H:\WINDOWS. Whenever I need to do some boot-level stuff on C:, I reboot into DOS 7.0 (Win95).
     
  5. Alainp

    Alainp Registered Member

    Joined:
    May 18, 2005
    Posts:
    14
    Success !
    Finally, I found my mistake :

    I unplugged my hard drive and rebooted => NTLDR missing o_O
    I unplugged my CD Rom and rebooted :p => NTLDR missing o_O o_O

    Then I remembered my SATA Raid Array :oops: - For some strange reason, the BIOS was set-up to start from my Raid Array (used for data only, with no OS).

    This explains a lot :
    - of course NTLDR was missing
    - this also explains the rdisk(1)

    So, after re-ordering my bios boot sequence, I finally got to a new error message :D - but this one I can manage (I think)

    So now that my problem is solved, I restore the image (for the 4th time) and I hope that my system will start up !

    Thank you for your kind assistance and patience. I would not have been to figure it out without your insightfull contributions.

    Also, I get back my unfair complaints about TI : once again, the software was working, but the human was full of bugs :oops: (although I still remain disappointed by Acronis's poor support).

    Alain
     
  6. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    Thanks for letting us know the outcome.

    By the way, how do you generate that report.exe?
     
  7. Alainp

    Alainp Registered Member

    Joined:
    May 18, 2005
    Posts:
    14
    Brian,

    I'm not sure what you mean by "report.exe", the report.txt I attached are generated with Acronis Report utility (http://www.acronis.com/files/support/AcronisReport.exe).

    (BTW, I could not make the boot disk created byt Acronis Report work for me, so I launched Acronis Report from Bart Boot Disk...)

    Did I reply to your question ?

    Alain
     
  8. Brian K

    Brian K Imaging Specialist

    Joined:
    Jan 28, 2005
    Posts:
    12,175
    Location:
    NSW, Australia
    Sorry, typo. report.txt. Thanks
     
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.