Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Windows Logon problem

  • 12-12-2005 4:09pm
    #1
    Closed Accounts Posts: 57 ✭✭


    I cant seem to log on to windows. Whenever I boot up it says "NTLDR is missing. Press any key to continue."
    I tried to do window recovery console but nothing I do seems to work. Can someone advice me what need to be done?

    Also is it possible to see whats in my RAID0 when I cant even get windows to boot? Even on DOS mode? I just want to check that my Windows file is still in tact.

    Thanks.


Comments

  • Registered Users, Registered Users 2 Posts: 67 ✭✭Lush


    [V3] wrote:
    I cant seem to log on to windows. Whenever I boot up it says "NTLDR is missing. Press any key to continue."
    I tried to do window recovery console but nothing I do seems to work. Can someone advice me what need to be done?

    Also is it possible to see whats in my RAID0 when I cant even get windows to boot? Even on DOS mode? I just want to check that my Windows file is still in tact.

    Thanks.

    Don't shoot me for asking the simple question, but... is there a floppy disk in the floppy drive? If so remove it...


  • Moderators, Education Moderators, Technology & Internet Moderators, Regional South East Moderators Posts: 24,056 Mod ✭✭✭✭Sully


    Lush wrote:
    Don't shoot me for asking the simple question, but... is there a floppy disk in the floppy drive? If so remove it...

    Most computers wont boot up at all with a floppy in the drive and thats not the error that they would get anyway :)


  • Moderators, Education Moderators, Technology & Internet Moderators, Regional South East Moderators Posts: 24,056 Mod ✭✭✭✭Sully




  • Closed Accounts Posts: 57 ✭✭[V3]


    Nothing is in the floppy drive bay.


  • Registered Users, Registered Users 2 Posts: 5,278 ✭✭✭mordeith


    Sully04 wrote:
    Most computers wont boot up at all with a floppy in the drive and thats not the error that they would get anyway :)

    Actually, I've seen this error crop up and a floppy disc left in is exactly the problem ;)
    (Although not necessarily in this case :rolleyes: )


  • Advertisement
  • Moderators, Education Moderators, Technology & Internet Moderators, Regional South East Moderators Posts: 24,056 Mod ✭✭✭✭Sully


    mordeith wrote:
    Actually, I've seen this error crop up and a floppy disc left in is exactly the problem ;)
    (Although not necessarily in this case :rolleyes: )

    My appologizes. Iv never experienced this error myself. Cheers for correcting me :)


  • Closed Accounts Posts: 57 ✭✭[V3]


    Sully04 wrote:

    I tried everything there but nothing seems to work at all.


  • Closed Accounts Posts: 210 ✭✭HomunQlus


    [V3] wrote:
    I cant seem to log on to windows. Whenever I boot up it says "NTLDR is missing. Press any key to continue."
    I tried to do window recovery console but nothing I do seems to work. Can someone advice me what need to be done?

    Also is it possible to see whats in my RAID0 when I cant even get windows to boot? Even on DOS mode? I just want to check that my Windows file is still in tact.

    Thanks.

    NTLDR is the file that looks for Windows when control is handed over to the OS after the BIOS is finished. The information where to look for NTDLR is usually written in the Master Boot Record, this information usually signs to the first boot device (if nothing else is found on the first boot device).

    Now, that the file is not there can have many causes.

    Most simple of all, like said before, is a floppy left in the bay. If that's not it, check the BIOS settings, and see if the first boot drive is something other than your harddrive on which Windows is installed on. If so, correct that setting.

    If this doesn't work, try to boot up with your XP CD, then go into the Recovery Console.

    There you can do many things to repair your installation. Best guess of all are two commands:

    FIXBOOT
    FIXMBR

    Do these two, it doesn't matter which one first, then reboot again.

    If this still doesn't help, then the file is really no longer available on the drive, which, in most cases, means a re-install of Windows itself.


  • Registered Users, Registered Users 2 Posts: 5 Curry Monster


    When your operating system eg. WinXP is starting up it uses several files to get started. NTLDR is one of these files. The error message that you are getting is more or less stating that the file is corrupt.

    A way around it is to go to another computer with the same operating system.

    Open file explorer go to Tools-Folder Option-View.... tick show hidden files and UN-tick hide protected operating system files...select YES bla de bla
    Then view the c: drive in explorer and you will see all the files.

    Copy the files NTLDR & Boot & IO & NTDETECT onto a floppy disk ...I would then recommend reversing the above in tools -folder option- View.etc..

    Then put the floppy into the broken pc and leave it in the floppy drive and power up. About a 98% chance this will work. When your system powers up copy over the NTLDR file.
    Let me know if this works

    Regards
    Jimmy


  • Closed Accounts Posts: 121 ✭✭biofreak


    Had this problem myself. I went into Recovery Console through the Windows XP CD and replaced system file with system.bak in C:\windows. I forget the exact commands though.


  • Advertisement
  • Registered Users, Registered Users 2 Posts: 5,578 ✭✭✭CyberGhost


    Had this problem too, grrrr

    and I too used XP recovery cd. worked.


  • Registered Users, Registered Users 2 Posts: 5,578 ✭✭✭CyberGhost


    btw, if you have Linux and Windows dual boot, with lilo or grub handling booting, and you delete Linux partition, you'll get the same thing too, if you don't make windows bootloader "take over" the MBR.


  • Closed Accounts Posts: 2,148 ✭✭✭angelofdeath


    Copy the files NTLDR & Boot & IO & NTDETECT onto a floppy disk ...I would then recommend reversing the above in tools -folder option- View.etc..

    Then put the floppy into the broken pc and leave it in the floppy drive and power up. About a 98% chance this will work. When your system powers up copy over the NTLDR file.
    Let me know if this works

    Regards
    Jimmy

    aye this works, had to do it before, only i found i only needed the ntldr file and had to use a computer with the exact same service pack and the same updates


  • Closed Accounts Posts: 57 ✭✭[V3]


    Insert the Windows XP bootable CD into the computer.
    When prompted to press any key to boot from the CD, press any key.
    Once in the Windows XP setup menu press the "R" key to repair Windows.
    Log into your Windows installation by pressing the "1" key and pressing enter.

    Whenever I do Windows recovery, it doesnt give me the option to press 1 to log into my windows intallation. Does anyone know why?

    Curry Monster: thanks, I'll give it a try. I did try copying NTLDR & NTDETECT.com from my windows CD and then create a boot.ini but then it says my display.sys file is missing and corrupt and then my config.sys may be damage.

    I think it looks like my windows is really screwed up though it was fine the last time I used it.


  • Closed Accounts Posts: 1,746 ✭✭✭0utshined


    I've come across this problem before and got software off sysinternals that did the job. I can't recall exactly which one it was but I think it was this : http://www.sysinternals.com/utilities/ntfsdosprofessional.html


  • Registered Users, Registered Users 2 Posts: 14,010 ✭✭✭✭Cuddlesworth


    Tried clearing cmos? Worked for me.


Advertisement