Home > Fatal Error > Fatal Error 256 Reading Boot Ini
Fatal Error 256 Reading Boot Ini
I was able to expand it to 149GB with Dynamic Drive Overlay(DDO). Better safe than sorry. I want to try this in the above link but I do not understand all the steps. That would be the best bet. this contact form
So yeah, may have just made this worse. Aged home-built computer is now... He added something that messed up a driver somewhere more than likely to get that hal.dll error. Any help will be appreciated.
If we have ever helped you in the past, please consider helping us. Fragmented dependency files for NTLDR, in this case the fragmentation of boot.ini, can cause this error to occur. Sorry, it has been ages >> since I worked on them much, and so there might be new things I'm not up >> to date on... >> >> Glitchie >> >> Reply With Quote November 28th, 2007,01:40 PM #2 Steve R Jones View Profile View Forum Posts Visit Homepage Administrator Join Date Sep 1999 Location Dallas, Tx.
- What is your computer make and model?
- Then, I backed up the drive.
- Reply With Quote Quick Navigation Windows XP Top Site Areas Settings Private Messages Subscriptions Who's Online Search Forums Forums Home Forums Center For Disease Control Security News / Warnings / Updates
- Discussions cover Windows 2003 Server, Windows installation, adding and removing programs, driver problems, crashes, upgrading, and other OS-related questions.Real-Time ActivityMy Tracked DiscussionsFAQsPoliciesModerators General discussion NTLDR Fatal Error 256 Reading Boot.ini by
- Since then, I tried booted from the > Windows XP cd again and it reads the disk in the drive, but I'm not > given the option to boot from the
- I made two boot disks from the disk that came with the drive - Data Life Guard Boot Disk and Data Life Guard Diagnostics Boot Disk and have tried booting from
- Register now to gain access to all of our features, it's FREE and only takes one minute.
- I have gone on web and located boot drivers for xp, and put floppy in, and nothing.
- Choose "Automated Repair" in Easy Recovery Essentials After EasyRE scans your computer's drives, identify and select the drive letter for your Windows installation from the list, and then click on the Automated
- Cause 3: Fragmented BOOT.INI file An obscure cause of "NTLDR: Fatal error reading boot.ini" on Windows XP is excessive disk fragmentation.
I have Windows ME on a brand new SEAGATE 160GB Hard Drive and I upgraded to Windows XP Home Edition Upgrade multiple times due to the fact that I wanted have I'm only semi-tech-speak literate and i've never really "fixed" a computer before so you may have to explain some things clearly. Powered by vBulletin Version 3.6.7Copyright ©2000 - 2016, Jelsoft Enterprises Ltd. The automated system repair function of EasyRE which is responsible for this action will also search for and correct any other incidental boot issues.
Please refer to our CNET Forums policies for details. Password Site Map Posting Help Register Rules Today's Posts Search Site Map Home Forum Rules Members List Contact Us Community Links Pictures & Albums Members List Search Forums Show Threads This should help by allowing time to write down the STOP code properly. https://www.cnet.com/forums/discussions/ntldr-fatal-error-256-reading-boot-ini-210615/ When you are at the recovery console command prompt, enter this: Code: bootcfg /rebuild 04-21-2007, 05:04 PM #3 flynshue Registered Member Join Date: Apr 2007 Location: Cary,
Click on the Restart button to reboot your PC and test the changes. Gerry ~~~~ FCA Stourport, England Enquire, plan and execute ~~~~~~~~~~~~~~~~~~~ Glitchie wrote: > Why use an NT disk when I'm running XP pro? Follow 3 Simple Steps to Repair PC Instantly! PROGRAM FILES?
Try and boot the computer with the startup disk. Member Login Remember Me Forgot your password? Cause 3: Fragmented BOOT.INI file The cause of the “NTLDR: Fatal error in reading the boot:ini” on the Windows excessive disk fragmentation. I don't know what is going on with this, these drives have been nothing but trouble.
floppybootstomp posted Oct 14, 2016 at 3:53 PM Toe-tale Taffycat posted Oct 14, 2016 at 11:04 AM WCG Stats Friday 14 October 2016 WCG Stats posted Oct 14, 2016 at 8:00 http://bashprofile.net/fatal-error/fatal-error-512-reading-boot-ini.html So yeah, may have just made this > worse. > > Anyway, I went in and ran this after I found out I had the wrong > command, and did the It has been making some noise lately. Proffitt Forum moderator / October 5, 2006 4:42 AM PDT In reply to: NTLDR Fatal Error 256 Reading Boot.ini You'll have to look to booting the XP CD, find your way
My thinking was that 256 in the error message might have been a memory error. What the heck is going on? This cured the same problem for me.
Sorry, there was a problem flagging this post.
Posts 21,200 What's the rest of the story behind the problem? "Common Sense is a flower that doesn't grow in everyone's garden." Reply With Quote November 28th, 2007,02:11 PM #3 ginky4 Backup first. The fixmbr command is only available when you are using the Recovery Console. Especially if Microsoft made it! « Unusual "FAIL" message after login to XP | Mouseover Effect on Clock Doesn't Work » Thread Tools Show Printable Version Download Thread Search this
Corruption may occur in the boot partition may be result of unsafe writes on the boot partition, interrupted writes, sudden power loss that prevents some or all the contents from being About Us PC Review is a computing review website with helpful tech support forums staffed by PC experts. Make sure that you use an NT type machine to format the floppy > drive, the disk will fail if you format it with a Windows 9x machine. > > John his comment is here Close out of the My Computer window and reopen it.
John John - MVP wrote: > Because Windows XP is Windows NT 6.0, it's an NT operating system. At least I got Windows XP to work. Content Relevant URLs by vBSEO 3.1.0 LinkBack LinkBack URL About LinkBacks Bookmark & Share Digg this Thread! Hello all, i'm hoping someone might be able to help me (bet you get that alot).
Press R to open the Recovery Console once at the Options menu. I have used this fairly straight forward and simple resolution for your issue. So, would this mean I would do a complete install? Just make certain you are running a repair and not new installation. 0 #7 id990176 Posted 27 April 2005 - 03:20 AM id990176 Member Member 10 posts I have this similar
The only other thing that I tried to do was change the 2 sticks of 256 Kingston ram. When installing it,,,,,,,,,I chose to just copy the contents of the old one, onto the new one. I am still getting the hal.dll error. Symptom 1: Fatal error while reading boot.ini If you are attempting to boot up your Windows PC this fatal error may be exhibited by NTLDR, which restricts the computer from successfully
The time now is 01:50 PM. I have a lot of my graphics program >> stuff installed on it already before it came up with this error with the >> boot.ini file and I REALLY don't want It has already prompted us to put in the Win 98 CD to prove we are eligible to use this upgrade version. Join Date Aug 2000 Location White Marsh, Maryland Posts 2,153 Supersparks I followed your suggestion and it did not work.
Easy Recovery Essentials is guaranteed to fix the "NTLDR: Fatal error reading BOOT.INI" error automatically using its built-in Automated Repair option. Regards, __________________ Dave T. So when I ran the console, I ran fixboot, I thought that's what I needed, but I didn't have the computer with this page on it to double check. Reply With Quote November 28th, 2007,07:18 PM #9 ginky4 View Profile View Forum Posts Virtual PC Specialist!!!