Saved Bookmarks
| 1. |
Solve : edit boot.ini? |
|
Answer» HELLO, I can't start my computer, I get an invalid boot.ini error. So I tried to rebuild the boot.ini file. I succeded to make a new boot.ini file in notepad and copied it to C: and I can see it in the list but when I enter bootcfg/ rebuild I get; The COMMAND is not recognized. Is the bootini file I copied below into C correct? I have only one operating system, win2k professional and I have 4 partitions. I wonder if the values of partitions are correct? Are the numbers in bold correct? [boot loader] timeout=30 default=multi(0)disk(0)rdisk(0)partition(1)\WINNT [operating systems] multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000 Professional" /fastdetect Help much appreciated, getting desperate.Are you trying the BOOTCFG command from the Windows 2000 Recovery Console?Yes I am Quote from: ccc Code: [Select]bootcfg/ rebuild No wonder it didn't work if that's how you typed it. You need a space after bootcfg and no space after the / thus: bootcfg /rebuild info here- http://support.microsoft.com/kb/317521 Sorry I wrote wrong in the first post but inside Recovery Console I did write : bootcfg /rebuild like you said. But I do still get the; the command is not recognized. Did I write the bootini file CORRECTLY considering I have one operating system and 4 partitions? Thanks. Is BOOTCFG available in the W2k Recovery console? KB317521 refers to Win Server 2003, KB229716 shows that BOOTCFG is not available in W2k Pro, at least it doesn't show that it is available. The boot.ini file shown seems to be spot-on provided that W2k is installed in the first partition of the only drive referenced i.e. drive zero partition one. Good luckSo if I can't use bootcfg /rebuild then how can I fix the boot.ini error? I did the chkdsk /r and it found one error and fixed it but still I get the "invalid system boot.ini error" when attempting to start the computer. Thanks. Here's an outside chance... You created and saved your new boot.ini file using Notepad, did you remember to enclose the filename.ext in double quotes to ensure the file is not saved by Notepad as boot.ini.txt? Please post the old boot.ini so that we can try to locate what the problem with it is, and have a looksee for boot.ini.txt, a common oversight when using Notepad. Please post the old boot.ini so that we can try to locate what the problem with it is, and have a looksee for boot.ini.txt, a common oversight when using Notepad. [/quote] When I first got the invalid boot.ini error and entered the Recovery Console, I could not find the boot.ini file. No, my boot.ini file does not have the txt extension. I no longer get the invalid boot.ini error when I reboot(does this mean my boot.ini file is correct?), but still the computer turns itself off after the startup page and auto restarts. I'm confused about the 'bootcfg /rebuild', some say I have to do it, some say it's not possible in w2k? Do I need to do it even I managed to copy the boot.ini file to C: in Recovery Console? if you don't get a MESSAGE saying there is a boot.ini error, I think you can now turn your attention to the other problems.Quote from: Dias de verano on September 22, 2008, 09:00:40 AM if you don't get a message saying there is a boot.ini error, I think you can now turn your attention to the other problems. OK, so maybe the boot.ini file is correct now. But what do I do now? The computer doesn't start and I don't get any error messages. So far I have tried; Chkdsk /R and it found errors and corrected them Safe mode, VGA mode and all the modes in F8 Made new boot.ini file Any suggestions much appreciated.Hi I have no experience of "Chkdsk /R", but several decades experience of computers not doing what they should. If "Chkdsk /R" has found and fixed one error, I will believe there was PROBABLY an error, BUT I will NOT believe the error is fixed until I re-run "Chkdsk /R" and it then finds no errors. Regards Alan Quote from: ALAN_BR on September 22, 2008, 02:34:58 PM Hi Thanks. You are correct. After I do the chkdsk /R it finds one or more errors and corrects them. Then I reboot the computer and it doesn't boot, and I go into Recovery Console and do the Chkdsk, and again it finds errors Don't know what to do now, since there are no error message at startup. Quote from: ccc on September 22, 2008, 03:15:00 PM After I do the chkdsk /R it finds one or more errors and corrects them. Then I reboot the computer and it doesn't boot, and I go into Recovery Console and do the Chkdsk, and again it finds errors You know what that says to me? It says your hard disk is failing. They don't last forever. Quote Don't know what to do now, since there are no error message at startup. Buy a new hard disk. They have never been cheaper. Do a fresh install. |
|