-
Lynda Design Aesthetics For Web Design카테고리 없음 2020. 2. 29. 18:37
Sponsoring website:TheBOOT.INI File ofMicrosoft® Windows NT/2000/XP/2003Web Presentation and Text Copyright©2004-2006, 2015 by Daniel B. SedoryNOT to be reproduced in any form without Permission of the Author!. (Don't skip it, unless you're a BOOT.INI expert.). A Simple Dual-Boot File.
Complex Multi-Boot File.IntroductionThis page will help you make changes to a file you might not even know exists!Whenever you try out a copy of aWindows 2000, XP or 2003 OS on a computer that already has Windows 9x/Me installed, a new OS boot selectormenu will appear after installing one of these operating systems. That menu is controlled by a BOOT.INI file.Many have asked me how to remove that menu after they deleted the new (but temporary) OS from their hard drive. Well, it's actually a lot easier (andsafer) to simply change the menu. Because your old system now has a new look:Most likely you'll be quite surprised to find a handful of new files in your Windows 9x/Me root directory! Alongwith the new file, NTLDR, and other NT-type system files, you'll also find this BOOT.INI file which is used to make that OS bootselector menu. Unfortunately, you can not just remove those files!
Doing so will make it impossible(until corrected)to boot upyour Windows 9x/Me OS! The reason for this is:Installing one of these new OSs (2000/XP/2003) will, without any warning, changethe Boot Record of a Windows 9x/Me OS.Instead of looking for the files IO.SYS and MSDOS.SYS, the changed OS Boot Record will search for and run theNTLDR system file.
Or maybe it's locking-up instead, because you already deleted those files before reading this! If you were to look at your OS's Boot Sector in a disk editor, you'd find that your old (Windows OSR2 /98 /98SE /Me ) code had been replaced with a FAT32 version ofthe ( even though it may still have an OEM ID of ' MSWIN4.1').You can, however, easily make changes to the BOOT.INI file so the menu will show only the Microsoft® operating systems youwant to boot up, or set it to only one and have it flash by so quick you'll forget about it being there. So, maybe you'll find a use for all those extrafiles you never asked for! If you really want to get your old Windows 9x/Mepartition back to its original state, you'll either need some expert advice, or spend enough time studying until you can edit the volume's BootRecord before finally deleting the added system files.
Your Choices for Changing the Boot Menu What about Windows™ 7 or Vista?You can notuse BOOT.INI with these operating systems! Vista and Windows™ 7 requre the use of a new boot manager(' bootmgr') and other associated files in order to boot. If you try booting these systems using BOOT.INI and NTLDR, the operationwill fail. For example, if you install Windows™ 7 in unallocated space on a computer running Win XP and look inside the XP partition, you'll find theinstall process made backups of the original boot sector (BOOSECT.BAK) and boot.ini (Boot.BAK) files, and these lines added to the new boot.ini file:;Warning: Boot.ini is used on Windows XP and earlier operating systems.;Warning: Use.exe to modify Windows Vista boot options. If the NT-type OS is still InstalledBoot up the Windows 2000, XP or 2003 OS and open 'Control Panel' then click on ' System' ( or select'Properties' after right-clicking on My Computer). Under the 'System Properties' window's ' Advanced' tab,ifyou click on ' Startup and Recovery.'
you'll see at least two basic items in the BOOT.INI file that you're allowed to changefrom this dialog box: 1) You can select the default OS to boot up, and 2) How many seconds to display the boot menu.Andunder Windows XP or 2003, you'll find another button that gives you direct access to editing the whole BOOT.INI file! Under Windows 2000, you'll need to find the BOOT.INI file on your own for further editing; such asarranging the order in which the OS selections appear in the menu. So, if you decide to delete the new OS, simply set your old OS as the default boot OSand uncheck the item for displaying the menu list (or manually set it to zero; same result). You could then safely delete the new OS partition, but not thefiles it added to your old partition.This is actually a very interesting feature of the'NT' Operating Systems! Each time you open this window, it immediately checks the MBR's Partition Table (not just in Memory, but directly fromthe HDD) to see which Partition is set to boot (' Active'; 80h byte) and then opens the BOOT.INI file in that partition's rootdirectory.
This is how it determines which of several possible BOOT.INI files on a system it should open for editing. We know this for a fact,because: After initially using 'Startup and Recovery' to view one particular BOOT.INI file under Windows 2000, we changed the'Active' partition with a disk editor. Then, without rebooting(!), we used this feature again, and it opened a completely different BOOT.INI file from theroot directory of the other partition! If only the NT-type OS Partition was DeletedIf you already deleted the new OS, you'll need to: 1) Make sure your old OS is set toshow ' Hidden, System' files then look for the BOOT.INI file in C:, 2) Once you've found it, checkthe 'Properties' settings of its attributes and make sure it's not set to 'Read-only' (so you can edit it), 3)Open the file in a text editor, such as NOTEPAD, and edit the ' default' and ' timeout' lines; you can also delete any lines that refer to an OS you removed from the system.
Andfinally, 4) Do a quick check of the file's attributes to make sure they're still 'Hidden, System' (the 'Read-only' attribute is not required). If no OS (old or new) boots up!In this case, we have to assume (for now) that you deleted a critical component.
Windows Xp Boot
Write downany error messages you see on the screen whentrying to boot up your computer! These three files (located in your original OS's root directory ) are necessary to boot up eitheryour old OS or the NT-type OS:The BOOT.INI file, NTLDR (or ntldr; no extension!)and NTDETECT.COM. Apart from these, in order to boot up a Windows 9x/ Me OS afteran NT-type OS haschanged its Boot Sector, the file BOOTSECT.DOS (or its equivalent under a different file name) must also be present!
Withboth (or more?) OSs incapable of booting, the cause must first be determined before a course of action can be suggested. Read our page for some helpful thoughts related to boot up issues and to contact us for more information.One thing specific to NT-Type boot-up issues: If you incorrectly edited or deletedyour BOOT.INI file, the older NT-Type OSs (WindowsNT, 2000 and we believe original versions of XP) will no longer boot up! We purposely deleted our BOOT.INI file under Windows XP SP2 to see whatwould happen, and the OS was still able to boot up; if that doesn't work for you, we'd like to know about it! So, how do you boot up one of the old systemsif boot.ini is missing? Well, you either already have a boot diskette for this purpose, or you'll have to create one from another system or download thefiles from the Net.
After copying the files listed above to the diskette and setting (editing) the boot.ini file to boot up your non-booting OSpartition, it should boot up as normal so you can fix/create its boot.ini file! For more information, see the Microsoft article:. Example BOOT.INI Files A Simple Dual Boot File:boot loadertimeout=10default=multi(0)disk(0)rdisk(0)partition(2)WINDOWSoperating systemsmulti(0)disk(0)rdisk(0)partition(2)WINDOWS=' Microsoft Windows XP' /fastdetectC: = ' Microsoft Windows'For most, this should be very similar to your (first) BOOT.INI file. Ifyou installed Windows 2000 Pro, instead of Windows XP, then the ' WINDOWS' portion would be ' WINNT' instead. The descriptions of the Windows® Operating Systems in the Menu may vary; this install didn'teven mention that the old OS was Windows 98 Second Edition.
However, this is irrelevant, since you can change it to anything you want when editingthe file! A Complex Multi-Boot File:boot loadertimeout=30default=multi(0)disk(0)rdisk(0)partition(1)WINNToperating systemsmulti(0)disk(0)rdisk(0)partition(1)WINNT=' Win 2000 Pro(SP3)' /fastdetectC:CMDCONSBOOTSECT.DAT=' Windows 2000 Recovery Console' /cmdconsmulti(0)disk(0)rdisk(1)partition(1)WINNT=' Windows2000 Pro' /fastdetectC: = ' Windows 98 SE / DOS 7.1'The next section offers a detailed explanation for all the differences you see in the example above. Explanations for each part of BOOT.INIIn the ' boot loader' section above, the ' timeout' entry is how many seconds ( 30 in this case) that the menu will remain onscreen before trying to boot upthe ' default' OS.
Invalid Boot Ini File Ntdetect Failed Server 2003 Key
Example Line:multi(0)disk(0)rdisk(0)partition(1)WINNT=' Descrip.' Most of these lines use what are known as ARC (Advanced RISC Computing) paths to specify the location of various boot partitions. Almostevery machine using ATA (E IDE / IDE or SATA) hard drives will have: ' multi(0)disk(0)'. The multi(x) parameter is used to set the disk controller number, where x=0,1,2.The multi(x) parameter is alwaysfollowed by disk(0); unless you're using a SCSI controller without the BIOSenabled.The ' rdisk(n)' parameter is for the HDD drive number, where n=0,1,2.
Depending upon which physical drive this HDD is in yoursystem. The ' partition(p)' parameter is its partition on that drive, where p=1,2,3. In order, counting from a 1(not a zero).So, the very first partition on this first physical drive (where our main Windows 2000 OS is located ) is: ' multi(0)disk(0)rdisk(0)partition(1).'
The ' WINNT'which follows that, lets the OS Loader know that the system files are in the ' C:WINNT' folder! However, the Windows XP OSoften uses the older folder name of 'C:WINDOWS,' so the last part of its ARC might be ' WINDOWS' instead.The Descriptions of the OS boot choices, such as my default: ' Win 2000 Pro (SP3)' (shown in GREEN characters above) are simply what NTLDR displays in the boot menu; so you can change them to anything you wish!The second line under the ' operating systems' section is what you could call an alternate, backup or rescuecopy of my main Win2000 OS which is located in the same volume as the main OS.
A line like this will only be found ifyou install theRecovery Consolefiles from your install CD onto your hard disk! Though its entry appears to differ radically from the usual' multi(0)disk(0)' + ' rdisk(n)' + ' partition(p)' + ' systemroot' format,that's not really the case as we'll see later.The third line under the ' operating systems' section is an entirely different partition and version of Windows 2000;note the ' rdisk(1)' in the line which places it on the second physical drive!
Yes, Windows 2000, XP, 2003 can bootfrom any hard drive; I'm not sure if this would be true without the NTLDR/BOOT.INI files being located in a Primary partition on the first HDD though. Doesanyone have a working example where that's not true?NOTE: The fourth line under ' operating systems' is what you're likely to see if youinstalled one of these new NT-type OSs on a system that already had Windows 9x/Me.
Windows Nt Error
You'll see a line similar to this: C: = ' Microsoft Windows ME' (where C: = 'description'is all that's required),and they don't appearto use ARC paths! Well, it's just an illusionbuilt into NTLDR! If youwere to add such a line to a BOOT.INI file that hadn't been processed during an OS install ( or if you accidentally removed the file that C: = ' ' actually refers to. We'll get to that very soon), then attempting to bootthat selection would cause your system to lockup after displaying this message: I/O Error accessing boot sector filemulti(0)disk(0)rdisk(0)partition(1)BOOTSECT.DOSWhy?Because the filename BOOTSECT.DOS and its ARC pathare built into the programs ntldr and arcldr.exe and unless this file exists in the same folder they are in, you must supply apath to some other file and/or location.
Now you know why the second line in boot.ini above contains the path: C:CMDCONSBOOTSECT.DAT That's the file which initially boots the Recovery Console! What can I do if BOOTSECT.DOS was Deleted?To see a similar method for booting up DOS or older Windows partitions or even Linux ( if LiLo is its bootsector) using a Bootsectdata file and BOOT.INI, see:. Though bootpart was first written for Windows NT (some material onthe page is outdated, and links may be broken), the bootpart program is still quite useful for creating a file that will boot alternate OSs from aBOOT.INI file.
The program runs under Windows NT, 2000, XP, 2003 or DOS (with certain limitations).