Olaf Berli
asked on
boot.ini editing
I have restored a disk image from a win2000 server to a new (same server). When booting, I initialy got two OS choices when booting - both called "Microsoft Windows 2000 Server". One entry worked ok, but the other gave an error message and didn't boot. I then edited boot.ini and found that the choice that didn't work had something like "default=signature(1111111 1111)" at the beginning of the lines. I removed this "signature" stuff and have now a boot.ini file that looks like this:
[boot loader]
timeout=50
default=disk(0)rdisk(0)par tition(2)\ WINNT
[operating systems]
multi(0)disk(0)rdisk(0)par tition(2)\ WINNT="Mic rosoft Windows 2000 Server" /fastdetect
The strange thing is that when this machine is booting, there are two OS choices - like:
Microsoft Windows 2000 Server
Windows 2000 (default)
When going into ControlPanel/System/Advanc ed/Startup &Recovery, however, there is only one choice - the first shown above. Since the system seems to pick the wrong OS choice - this creates problems whenever the server is booted. Any ideas how to fix this?
Thanks!
Olaf
[boot loader]
timeout=50
default=disk(0)rdisk(0)par
[operating systems]
multi(0)disk(0)rdisk(0)par
The strange thing is that when this machine is booting, there are two OS choices - like:
Microsoft Windows 2000 Server
Windows 2000 (default)
When going into ControlPanel/System/Advanc
Thanks!
Olaf
> Show hidden files and folders > Edit the ini in Notepad.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the very quick answer! Tried it, and after adding the (obvious) multi(0) to the default= line, the server boots like a dream. (Since there are only one OS to boot, the choices are not shown).
BTW, any ideas what the previous "signature" stuff at the beginning of each line is for?
Thanks!
Olaf
BTW, any ideas what the previous "signature" stuff at the beginning of each line is for?
Thanks!
Olaf
Check out http://support.microsoft.com/kb/q227704/ ("Windows May Use Signature() Syntax in the Boot.ini File"), the scoop is
-------------------------- ---------- ---->8---- ---------- ---------- ----------
The signature() syntax is equivalent to the scsi() syntax, but is used instead to support the Plug and Play architecture in Windows. Because Windows is a Plug and Play operating system, the SCSI controller number instance may vary each time you start Windows, especially if you add new SCSI controller hardware after Setup is finished.
Using the signature() syntax instructs Ntldr to locate the drive whose disk signature matches the value in the parentheses, no matter which SCSI controller number the drive is connected to.
The signature() value is extracted from the physical disk's Master Boot Record (MBR). This unique hexadecimal number is either written to the MBR during the Text-mode portion of Setup, or is written by an installation of Microsoft Windows NT version 4.0 or earlier.
-------------------------- ---------- ---->8---- ---------- ---------- ----------
--------------------------
The signature() syntax is equivalent to the scsi() syntax, but is used instead to support the Plug and Play architecture in Windows. Because Windows is a Plug and Play operating system, the SCSI controller number instance may vary each time you start Windows, especially if you add new SCSI controller hardware after Setup is finished.
Using the signature() syntax instructs Ntldr to locate the drive whose disk signature matches the value in the parentheses, no matter which SCSI controller number the drive is connected to.
The signature() value is extracted from the physical disk's Master Boot Record (MBR). This unique hexadecimal number is either written to the MBR during the Text-mode portion of Setup, or is written by an installation of Microsoft Windows NT version 4.0 or earlier.
--------------------------