Can' t boot
Posted 14 August 2009 - 10:30 AM
Have you been Dual Booting and deleted another Operating System?
Deleted a Partition?
Have you changed any settings in BIOS, what relevance is the screenshot?
It seems you may have deleted the MBR, Master Boot Record.
In earlier versions of the Windows operating system that run on a basic input/output system (BIOS)-based computer, such as Windows XP, the boot process starts with the system BIOS. The BIOS determines the boot device, and then loads the first physical sector. This physical sector is named the master boot record (MBR). The MBR contains the partition table and the necessary boot execution code. This code searches the partition table to find the active partition and passes control to the boot sector on the active partition. Then, the boot sector on the active partition loads the Ntldr program. The Ntldr program parses the Boot.ini file. This file is used to enumerate the operating systems that are installed.
Give us some more info on what you've done previous to this problem, i.e. any changes to Operating System, Software Installation, etc.
While I'm here can offer some options while you think about any changes that you may have made to cause this problem.
Fixes for NTLDR Errors
1. Restart the PC. The NTLDR error could be a fluke.
2. Check your floppy and optical (CD/DVD) drives for media. Often times, the "NTLDR is Missing" error will appear if your PC is trying to boot to a non-bootable floppy disk or CD/DVD.
Note: If you find that this is the cause of your problem and it's happening a lot, you might want to consider changing the boot order in BIOS so the hard drive is listed first.
3. Check the hard drive and other drive settings in BIOS and ensure they are correct. The BIOS configuration tells the computer how to use a drive so incorrect settings can cause problems, including NTLDR errors.
Note: There is usually an Auto setting for hard drive and optical drive configurations in BIOS which is usually a safe bet if you're not sure what to do.
NTLDR Is Missing Resolution
Restore NTLDR and Ntdetect.com From the Windows XP CD
Posted 14 August 2009 - 12:24 PM
Use the CD you burnt with the directions.
Posted 17 August 2009 - 10:06 AM
Missing NTLDR (fixed by specialist)
Hi, i\'v got my pc to a service and my boot.ini and some other files were replaced by an specialist so now i'm get this:
Invalid BOOT.INI file
Booting from C:/WINDOWS
Is that normal ?
Lock at this, is everyting fine ? Before the ''fix'' i had like 30-33 procesess running at the starup, i noticed that like mybe some SYSTEM processes are missing right?
Can i try this topic to fix the BOOT.INI?
Edited by knoker, 17 August 2009 - 11:34 AM.
Posted 17 August 2009 - 01:49 PM
Click on Recovery Console Instructions in my sig... follow the directions to burn a CD. Then go here: http://icrontic.com/...pair_windows_xp
Use the CD you burnt with the directions.
Big big thanks!
I can't start my ESET NOD32 av 4.0v, when I launch it an error apears - ''Error comunicating with kernel''
I reinstalled NOD and all was fine, and today it won't start agen..
I tryed this fix - http://www.eset.eu/s...-kernel-service (I reinstalled Microsoft .NET Framework 1.1) and still no luck.
Edited by knoker, 17 August 2009 - 11:09 PM.
Posted 18 August 2009 - 11:04 AM
Posted 18 August 2009 - 11:18 AM
1. Insert your Windows XP CD into your CD and assure that your CD-ROM drive is capable of booting the CD.
2. Once you have booted from CD, do NOT select the option that states: Press F2 to initiate the Automated System Recovery (ASR) tool.
You’re going to proceed until you see the following screen, at which point you will press the “R” key to enter the recovery console:
3. After you have selected the appropriate option from step two, you will be prompted to select a valid Windows installation (typically number “1″).
Select the installation number, and hit Enter.
If there is an administrator password for the administrator account, enter it and hit Enter (if asked for the password, and you don't know it, you're out of luck).
You will be greeted with this screen, which indicates a recovery console at the ready:
4. There are eight commands you must enter in sequence to repair any of the issues I noted in the opening of this guide.
I will introduce them here, and then show the results graphically in the next six steps.
NOTE. Make sure, you press Enter after each command. Make sure, all commands are exact, including "spaces".
These commands are as follows:
ATTRIB -H C:\\boot.ini
ATTRIB -S C:\\boot.ini
ATRIB -R C:\\boot.ini
Note about the above command.
BOOTCFG /REBUILD command which searches for pre-existing installations of Windows XP and rebuilds sundry essential components of the Windows operating system, recompiles the BOOT.INI file and corrects a litany of common Windows errors.
It is very important that you do one or both of the following two things:
A.) Every Windows XP owner must use /FASTDETECT as OS Load Option when the rebuild process is finalizing.
B.) If you are the owner of a CPU featuring Intel’s XD or AMD’s NX buffer overflow protection, you must also use /NOEXECUTE=OPTIN as an OS Load Option.
For the Enter Load Identifier portion of this command, you should enter the name of the operating system you have installed.
If, for example, you are using Windows XP Home, you could type Microsoft Windows XP Home Edition for the identifier (it's not crucial, however what the name is, as long, as it's meaningful).
Here is your computer screen:
5. Following command verifies the integrity of the hard drive containing the Windows XP installation. While this step is not an essential function in our process, it’s still good to be sure that the drive is physically capable of running windows, in that it contains no bad sectors or other corruptions that might be the culprit:
6. This last command writes a new boot sector to the hard drive and cleans up all the loose ends we created by rebuilding the BOOT.INI file and the system files. When the Windows Recovery Console asks you if you are Sure you want to write a new bootsector to the partition C: ? just hit “Y”, then Enter to confirm your decision:
7. It’s time to reboot your PC by typing
and pressing Enter.
With any luck, your PC will boot successfully into Windows XP as if your various DLL, Hive, EXE and NTLDR errors never existed.
2. If you don't have Windows CD...
Download Windows Recovery Console: http://www.thecomput...om/files/rc.iso
Download, and install free Imgburn: http://www.imgburn.c...hp?act=download
Using Imgburn, burn rc.iso to a CD.
Boot to the CD...let it finish loading.
When the "Welcome to Setup" screen appears, press R to start the Recovery Console.
Then, follow instructions from Step #3 above.
Thanks To Broni For The Instructions
Posted 18 August 2009 - 11:55 AM
Run Windows Update, and install everything. Reboot and try running NOD32 again.
Try downloading and installing this: http://www.microsoft...;displaylang=en
Posted 18 August 2009 - 03:03 PM
In Safe Mode, go to Start -> Run -> msconfig
Under Startup, uncheck everything. Then go to the Services tab. Check the box, "Hide All MS Services"
Then uncheck all the non-MS services. Save the settings, and boot into normal mode... try running NOD32.
Posted 19 August 2009 - 07:00 AM
Posted 19 August 2009 - 07:21 AM
And nod still won't start.
What the... is kernel?
Edited by knoker, 19 August 2009 - 07:31 AM.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users