Windows 2003 boot.ini file missing - how do I recreate it?

  • Thread starter Thread starter David B
  • Start date Start date
D

David B

When investigating our inability to boot from a mirrored system volume, it
came to light that our Server 2003 system did not have a boot.ini file.

Going through Control Panel > System > Advanced > Startup & Recovery >
Settings, I am being given the option of writing a boot.ini file, but fear it
is beyond my abilities.

Is this a very complex file, or can I realistically create one - any advice
would be gratefully received!
 
You can go to the recovery console, use the command bootcfg /rebuild

http://support.microsoft.com/kb/291980

Usually you put

/fastdetect /noexecute=optout

It asks you to input the load identifier (name of OS e.g. 2003 server) and
Load options.. For example

[1] C:\Windows
Add installation to boot list? (Yes/No/All):
Enter Load Identifier: (Custom description for an operating system loading
from the Boot menu)
Enter Operating System Load Options: (that is: /fastdetect)




"David B" <DavidB@discussions.microsoft.com> wrote in message
news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> When investigating our inability to boot from a mirrored system volume, it
> came to light that our Server 2003 system did not have a boot.ini file.
>
> Going through Control Panel > System > Advanced > Startup & Recovery >
> Settings, I am being given the option of writing a boot.ini file, but fear
> it
> is beyond my abilities.
>
> Is this a very complex file, or can I realistically create one - any
> advice
> would be gratefully received!
 
I have followed the procedure you outline and the prompts come up exactly as
you describe, but when I have completed my responses as you suggest and
reboot, the expected boot.ini file is still not there in the C:\ drive.

What can I be doing incorrectly?


"Greg O" wrote:

> You can go to the recovery console, use the command bootcfg /rebuild
>
> http://support.microsoft.com/kb/291980
>
> Usually you put
>
> /fastdetect /noexecute=optout
>
> It asks you to input the load identifier (name of OS e.g. 2003 server) and
> Load options.. For example
>
> [1] C:\Windows
> Add installation to boot list? (Yes/No/All):
> Enter Load Identifier: (Custom description for an operating system loading
> from the Boot menu)
> Enter Operating System Load Options: (that is: /fastdetect)
>
>
>
>
> "David B" <DavidB@discussions.microsoft.com> wrote in message
> news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> > When investigating our inability to boot from a mirrored system volume, it
> > came to light that our Server 2003 system did not have a boot.ini file.
> >
> > Going through Control Panel > System > Advanced > Startup & Recovery >
> > Settings, I am being given the option of writing a boot.ini file, but fear
> > it
> > is beyond my abilities.
> >
> > Is this a very complex file, or can I realistically create one - any
> > advice
> > would be gratefully received!
>
>
>
 
Boot.ini is a hidden system file, do you have the option to show these
files enabled?

John

David B wrote:

> I have followed the procedure you outline and the prompts come up exactly as
> you describe, but when I have completed my responses as you suggest and
> reboot, the expected boot.ini file is still not there in the C:\ drive.
>
> What can I be doing incorrectly?
>
>
> "Greg O" wrote:
>
>
>>You can go to the recovery console, use the command bootcfg /rebuild
>>
>>http://support.microsoft.com/kb/291980
>>
>>Usually you put
>>
>>/fastdetect /noexecute=optout
>>
>>It asks you to input the load identifier (name of OS e.g. 2003 server) and
>>Load options.. For example
>>
>>[1] C:\Windows
>>Add installation to boot list? (Yes/No/All):
>>Enter Load Identifier: (Custom description for an operating system loading
>>from the Boot menu)
>>Enter Operating System Load Options: (that is: /fastdetect)
>>
>>
>>
>>
>>"David B" <DavidB@discussions.microsoft.com> wrote in message
>>news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
>>
>>>When investigating our inability to boot from a mirrored system volume, it
>>>came to light that our Server 2003 system did not have a boot.ini file.
>>>
>>>Going through Control Panel > System > Advanced > Startup & Recovery >
>>>Settings, I am being given the option of writing a boot.ini file, but fear
>>>it
>>>is beyond my abilities.
>>>
>>>Is this a very complex file, or can I realistically create one - any
>>>advice
>>>would be gratefully received!
>>
>>
>>
 
Yes I do, it shows IO.SYS, CONFIG.SYS etc, but no boot.ini.



"John John" wrote:

> Boot.ini is a hidden system file, do you have the option to show these
> files enabled?
>
> John
>
> David B wrote:
>
> > I have followed the procedure you outline and the prompts come up exactly as
> > you describe, but when I have completed my responses as you suggest and
> > reboot, the expected boot.ini file is still not there in the C:\ drive.
> >
> > What can I be doing incorrectly?
> >
> >
> > "Greg O" wrote:
> >
> >
> >>You can go to the recovery console, use the command bootcfg /rebuild
> >>
> >>http://support.microsoft.com/kb/291980
> >>
> >>Usually you put
> >>
> >>/fastdetect /noexecute=optout
> >>
> >>It asks you to input the load identifier (name of OS e.g. 2003 server) and
> >>Load options.. For example
> >>
> >>[1] C:\Windows
> >>Add installation to boot list? (Yes/No/All):
> >>Enter Load Identifier: (Custom description for an operating system loading
> >>from the Boot menu)
> >>Enter Operating System Load Options: (that is: /fastdetect)
> >>
> >>
> >>
> >>
> >>"David B" <DavidB@discussions.microsoft.com> wrote in message
> >>news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> >>
> >>>When investigating our inability to boot from a mirrored system volume, it
> >>>came to light that our Server 2003 system did not have a boot.ini file.
> >>>
> >>>Going through Control Panel > System > Advanced > Startup & Recovery >
> >>>Settings, I am being given the option of writing a boot.ini file, but fear
> >>>it
> >>>is beyond my abilities.
> >>>
> >>>Is this a very complex file, or can I realistically create one - any
> >>>advice
> >>>would be gratefully received!
> >>
> >>
> >>
>
 
And what about ntldr and ntdetect.com, do you see those?

John

David B wrote:

> Yes I do, it shows IO.SYS, CONFIG.SYS etc, but no boot.ini.
>
>
>
> "John John" wrote:
>
>
>>Boot.ini is a hidden system file, do you have the option to show these
>>files enabled?
>>
>>John
>>
>>David B wrote:
>>
>>
>>>I have followed the procedure you outline and the prompts come up exactly as
>>>you describe, but when I have completed my responses as you suggest and
>>>reboot, the expected boot.ini file is still not there in the C:\ drive.
>>>
>>>What can I be doing incorrectly?
>>>
>>>
>>>"Greg O" wrote:
>>>
>>>
>>>
>>>>You can go to the recovery console, use the command bootcfg /rebuild
>>>>
>>>>http://support.microsoft.com/kb/291980
>>>>
>>>>Usually you put
>>>>
>>>>/fastdetect /noexecute=optout
>>>>
>>>>It asks you to input the load identifier (name of OS e.g. 2003 server) and
>>>>Load options.. For example
>>>>
>>>>[1] C:\Windows
>>>>Add installation to boot list? (Yes/No/All):
>>>>Enter Load Identifier: (Custom description for an operating system loading
>>>
>>>>from the Boot menu)
>>>
>>>>Enter Operating System Load Options: (that is: /fastdetect)
>>>>
>>>>
>>>>
>>>>
>>>>"David B" <DavidB@discussions.microsoft.com> wrote in message
>>>>news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
>>>>
>>>>
>>>>>When investigating our inability to boot from a mirrored system volume, it
>>>>>came to light that our Server 2003 system did not have a boot.ini file.
>>>>>
>>>>>Going through Control Panel > System > Advanced > Startup & Recovery >
>>>>>Settings, I am being given the option of writing a boot.ini file, but fear
>>>>>it
>>>>>is beyond my abilities.
>>>>>
>>>>>Is this a very complex file, or can I realistically create one - any
>>>>>advice
>>>>>would be gratefully received!
>>>>
>>>>
>>>>
 
"David B" <DavidB@discussions.microsoft.com> wrote in message
news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> When investigating our inability to boot from a mirrored system volume, it
> came to light that our Server 2003 system did not have a boot.ini file.
>
> Going through Control Panel > System > Advanced > Startup & Recovery >
> Settings, I am being given the option of writing a boot.ini file, but fear
> it
> is beyond my abilities.
>
> Is this a very complex file, or can I realistically create one - any
> advice
> would be gratefully received!

I do not know why the tips provided by other respondents should
not work on your server. Here is an alternative method to restart
the server.

1. Format a floppy disk on a Win2000/XP PC.
2. Copy ntldr and ntdetect.com from your server CD to A:\
3. Use notepad.exe to create a:\boot.ini. It should contain
these lines:
[boot loader]
timeout=3
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="4 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="5 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="6 Microsoft Windows Server
2003" /fastdetect /NoExecute=OptIn
4. Boot the server with this boot diskette. Try one of the
six options until you find out which one works.
5. When Windows is up and running, copy a:\boot.ini to
c:\. Edit it and remove those lines from it that did not work.
 
Thanks Pegasus. I did what you said and found the option (3) that worked when
booting from the floppy.

I copied the A:\BOOT.INI file to C:\. System would still boot, but did not
reflect the changes I had made to the BOOT.INI file.

I did a search for any other boot.ini files and discovered a second one in
root of my D:\ (data) drive, along with NTLDR and NTDETECT.COM files. I now
realise that this is the file that was created or overwritten when I ran
BOOTCFG /REBUILD earlier.

Why is system insisting on locating and using these files on the D:\ drive
when, by rights, they should be on C:\, where my \WINDOWS folder is located?
Although sytem functions, I am worried that having them on the wrong drive
will lead to other problems.

(I unsuccessfully tried to run Norton Ghost previously, which was not at all
happy coping with morrored volumes and I have since uninstalled. I think this
is where it all started to go wrong...)

Thanks for your continued support.

"Pegasus (MVP)" wrote:

>
> "David B" <DavidB@discussions.microsoft.com> wrote in message
> news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> > When investigating our inability to boot from a mirrored system volume, it
> > came to light that our Server 2003 system did not have a boot.ini file.
> >
> > Going through Control Panel > System > Advanced > Startup & Recovery >
> > Settings, I am being given the option of writing a boot.ini file, but fear
> > it
> > is beyond my abilities.
> >
> > Is this a very complex file, or can I realistically create one - any
> > advice
> > would be gratefully received!
>
> I do not know why the tips provided by other respondents should
> not work on your server. Here is an alternative method to restart
> the server.
>
> 1. Format a floppy disk on a Win2000/XP PC.
> 2. Copy ntldr and ntdetect.com from your server CD to A:\
> 3. Use notepad.exe to create a:\boot.ini. It should contain
> these lines:
> [boot loader]
> timeout=3
> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> [operating systems]
> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="4 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="5 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="6 Microsoft Windows Server
> 2003" /fastdetect /NoExecute=OptIn
> 4. Boot the server with this boot diskette. Try one of the
> six options until you find out which one works.
> 5. When Windows is up and running, copy a:\boot.ini to
> c:\. Edit it and remove those lines from it that did not work.
>
>
>
 
Good logical thinking there!

I suspect that your drive D: is currently marked as your
active partition. Run diskmgmt.msc - it will tell you.


"David B" <DavidB@discussions.microsoft.com> wrote in message
news:D11C5090-A57E-4E3F-9897-BD2BD61D0767@microsoft.com...
> Thanks Pegasus. I did what you said and found the option (3) that worked
> when
> booting from the floppy.
>
> I copied the A:\BOOT.INI file to C:\. System would still boot, but did not
> reflect the changes I had made to the BOOT.INI file.
>
> I did a search for any other boot.ini files and discovered a second one in
> root of my D:\ (data) drive, along with NTLDR and NTDETECT.COM files. I
> now
> realise that this is the file that was created or overwritten when I ran
> BOOTCFG /REBUILD earlier.
>
> Why is system insisting on locating and using these files on the D:\ drive
> when, by rights, they should be on C:\, where my \WINDOWS folder is
> located?
> Although sytem functions, I am worried that having them on the wrong drive
> will lead to other problems.
>
> (I unsuccessfully tried to run Norton Ghost previously, which was not at
> all
> happy coping with morrored volumes and I have since uninstalled. I think
> this
> is where it all started to go wrong...)
>
> Thanks for your continued support.
>
> "Pegasus (MVP)" wrote:
>
>>
>> "David B" <DavidB@discussions.microsoft.com> wrote in message
>> news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
>> > When investigating our inability to boot from a mirrored system volume,
>> > it
>> > came to light that our Server 2003 system did not have a boot.ini file.
>> >
>> > Going through Control Panel > System > Advanced > Startup & Recovery >
>> > Settings, I am being given the option of writing a boot.ini file, but
>> > fear
>> > it
>> > is beyond my abilities.
>> >
>> > Is this a very complex file, or can I realistically create one - any
>> > advice
>> > would be gratefully received!
>>
>> I do not know why the tips provided by other respondents should
>> not work on your server. Here is an alternative method to restart
>> the server.
>>
>> 1. Format a floppy disk on a Win2000/XP PC.
>> 2. Copy ntldr and ntdetect.com from your server CD to A:\
>> 3. Use notepad.exe to create a:\boot.ini. It should contain
>> these lines:
>> [boot loader]
>> timeout=3
>> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
>> [operating systems]
>> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="4 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="5 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="6 Microsoft Windows Server
>> 2003" /fastdetect /NoExecute=OptIn
>> 4. Boot the server with this boot diskette. Try one of the
>> six options until you find out which one works.
>> 5. When Windows is up and running, copy a:\boot.ini to
>> c:\. Edit it and remove those lines from it that did not work.
>>
>>
>>
 
In diskmgmt.msc the C: drive's status is shown as 'Heathy (Boot)' and the D:
drive is 'Healthy (System)', which looks hopeful.

In diskmgmt.msc, if I right-click C: to make it active, I don't get that
option.

I tried DISKPART.EXE instead and it tells me:

"The disk is not a fixed basic MBR disk."
"Select a fixed basic MBR disk to use this command."

Is this because I have dynamic drives, in order to provide RAID 1 protection?



"Pegasus (MVP)" wrote:

> Good logical thinking there!
>
> I suspect that your drive D: is currently marked as your
> active partition. Run diskmgmt.msc - it will tell you.
>
>
> "David B" <DavidB@discussions.microsoft.com> wrote in message
> news:D11C5090-A57E-4E3F-9897-BD2BD61D0767@microsoft.com...
> > Thanks Pegasus. I did what you said and found the option (3) that worked
> > when
> > booting from the floppy.
> >
> > I copied the A:\BOOT.INI file to C:\. System would still boot, but did not
> > reflect the changes I had made to the BOOT.INI file.
> >
> > I did a search for any other boot.ini files and discovered a second one in
> > root of my D:\ (data) drive, along with NTLDR and NTDETECT.COM files. I
> > now
> > realise that this is the file that was created or overwritten when I ran
> > BOOTCFG /REBUILD earlier.
> >
> > Why is system insisting on locating and using these files on the D:\ drive
> > when, by rights, they should be on C:\, where my \WINDOWS folder is
> > located?
> > Although sytem functions, I am worried that having them on the wrong drive
> > will lead to other problems.
> >
> > (I unsuccessfully tried to run Norton Ghost previously, which was not at
> > all
> > happy coping with morrored volumes and I have since uninstalled. I think
> > this
> > is where it all started to go wrong...)
> >
> > Thanks for your continued support.
> >
> > "Pegasus (MVP)" wrote:
> >
> >>
> >> "David B" <DavidB@discussions.microsoft.com> wrote in message
> >> news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
> >> > When investigating our inability to boot from a mirrored system volume,
> >> > it
> >> > came to light that our Server 2003 system did not have a boot.ini file.
> >> >
> >> > Going through Control Panel > System > Advanced > Startup & Recovery >
> >> > Settings, I am being given the option of writing a boot.ini file, but
> >> > fear
> >> > it
> >> > is beyond my abilities.
> >> >
> >> > Is this a very complex file, or can I realistically create one - any
> >> > advice
> >> > would be gratefully received!
> >>
> >> I do not know why the tips provided by other respondents should
> >> not work on your server. Here is an alternative method to restart
> >> the server.
> >>
> >> 1. Format a floppy disk on a Win2000/XP PC.
> >> 2. Copy ntldr and ntdetect.com from your server CD to A:\
> >> 3. Use notepad.exe to create a:\boot.ini. It should contain
> >> these lines:
> >> [boot loader]
> >> timeout=3
> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
> >> [operating systems]
> >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="4 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="5 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="6 Microsoft Windows Server
> >> 2003" /fastdetect /NoExecute=OptIn
> >> 4. Boot the server with this boot diskette. Try one of the
> >> six options until you find out which one works.
> >> 5. When Windows is up and running, copy a:\boot.ini to
> >> c:\. Edit it and remove those lines from it that did not work.
> >>
> >>
> >>
>
>
>
 
I'm out of my depth here. You can certainly have a RAID1
array (mirrored disk) with just two disks, and why you are
unable to mark your first disk active I do not know. If this
was my show then I would set up a test machine and play
with it until I found the answer. Since I am in the middle
of an overseas relocation, I cannot run this type of experiment
right now. I suggest you start a new thread with an appropriate
Subject line.



"David B" <DavidB@discussions.microsoft.com> wrote in message
news:6E6BC4FD-68A4-4840-9260-F380B3B78C89@microsoft.com...
> In diskmgmt.msc the C: drive's status is shown as 'Heathy (Boot)' and the
> D:
> drive is 'Healthy (System)', which looks hopeful.
>
> In diskmgmt.msc, if I right-click C: to make it active, I don't get that
> option.
>
> I tried DISKPART.EXE instead and it tells me:
>
> "The disk is not a fixed basic MBR disk."
> "Select a fixed basic MBR disk to use this command."
>
> Is this because I have dynamic drives, in order to provide RAID 1
> protection?
>
>
>
> "Pegasus (MVP)" wrote:
>
>> Good logical thinking there!
>>
>> I suspect that your drive D: is currently marked as your
>> active partition. Run diskmgmt.msc - it will tell you.
>>
>>
>> "David B" <DavidB@discussions.microsoft.com> wrote in message
>> news:D11C5090-A57E-4E3F-9897-BD2BD61D0767@microsoft.com...
>> > Thanks Pegasus. I did what you said and found the option (3) that
>> > worked
>> > when
>> > booting from the floppy.
>> >
>> > I copied the A:\BOOT.INI file to C:\. System would still boot, but did
>> > not
>> > reflect the changes I had made to the BOOT.INI file.
>> >
>> > I did a search for any other boot.ini files and discovered a second one
>> > in
>> > root of my D:\ (data) drive, along with NTLDR and NTDETECT.COM files. I
>> > now
>> > realise that this is the file that was created or overwritten when I
>> > ran
>> > BOOTCFG /REBUILD earlier.
>> >
>> > Why is system insisting on locating and using these files on the D:\
>> > drive
>> > when, by rights, they should be on C:\, where my \WINDOWS folder is
>> > located?
>> > Although sytem functions, I am worried that having them on the wrong
>> > drive
>> > will lead to other problems.
>> >
>> > (I unsuccessfully tried to run Norton Ghost previously, which was not
>> > at
>> > all
>> > happy coping with morrored volumes and I have since uninstalled. I
>> > think
>> > this
>> > is where it all started to go wrong...)
>> >
>> > Thanks for your continued support.
>> >
>> > "Pegasus (MVP)" wrote:
>> >
>> >>
>> >> "David B" <DavidB@discussions.microsoft.com> wrote in message
>> >> news:8FC33E41-6323-4178-9E54-6259832A6986@microsoft.com...
>> >> > When investigating our inability to boot from a mirrored system
>> >> > volume,
>> >> > it
>> >> > came to light that our Server 2003 system did not have a boot.ini
>> >> > file.
>> >> >
>> >> > Going through Control Panel > System > Advanced > Startup & Recovery
>> >> > >
>> >> > Settings, I am being given the option of writing a boot.ini file,
>> >> > but
>> >> > fear
>> >> > it
>> >> > is beyond my abilities.
>> >> >
>> >> > Is this a very complex file, or can I realistically create one - any
>> >> > advice
>> >> > would be gratefully received!
>> >>
>> >> I do not know why the tips provided by other respondents should
>> >> not work on your server. Here is an alternative method to restart
>> >> the server.
>> >>
>> >> 1. Format a floppy disk on a Win2000/XP PC.
>> >> 2. Copy ntldr and ntdetect.com from your server CD to A:\
>> >> 3. Use notepad.exe to create a:\boot.ini. It should contain
>> >> these lines:
>> >> [boot loader]
>> >> timeout=3
>> >> default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
>> >> [operating systems]
>> >> multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="1 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="2 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> multi(0)disk(0)rdisk(0)partition(3)\WINDOWS="3 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> multi(0)disk(0)rdisk(1)partition(1)\WINDOWS="4 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> multi(0)disk(0)rdisk(1)partition(2)\WINDOWS="5 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> multi(0)disk(0)rdisk(1)partition(3)\WINDOWS="6 Microsoft Windows
>> >> Server
>> >> 2003" /fastdetect /NoExecute=OptIn
>> >> 4. Boot the server with this boot diskette. Try one of the
>> >> six options until you find out which one works.
>> >> 5. When Windows is up and running, copy a:\boot.ini to
>> >> c:\. Edit it and remove those lines from it that did not work.
>> >>
>> >>
>> >>
>>
>>
>>
 
Back
Top