Sorry for the delay. I cannot find boot.ini. I think it is the crashed drive
with Win98. I try to find in other PC also don't have this particular file. I
chose option view hidden files also cannot find.

"Pegasus (MVP)" wrote:

> Let's have a look at your hidden file c:\boot.ini! Timothy
> Daniels already asked for this file but it seems you chose
> to ignore his request.
>
> By the way, if you again wait almost two weeks until
> you reply then this thread will have disappeared from
> my newsreader's horizon and your reply will be
> invisible to me.
>
>
> "baxter" <baxter@discussions.microsoft.com> wrote in message
> news:010B46F0-A00A-47BF-AE31-50EDF47902A9@microsoft.com...
> > I already install a spare drive with WinXP(with initial D drive
> disconnect) .
> > After that I reattached the drive but the PC just boot with the new OS
> > ignoring the one in D drive. Must I reinstall the spare drive with the D
> > drive attached.
> >
> > "Pegasus (MVP)" wrote:
> >
> > >
> > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > news:22155FFB-15DB-42D1-80BE-04566A16BCAB@microsoft.com...
> > > > I have try copying boot.ini from another bootable PC to D drive(with
> XP)
> > > but
> > > > cannot work.
> > > > Is creating a C partition is the only way out?
> > >
> > > No, it is not the only way but unless you provide answers
> > > to every question in my first reply I cannot tell you how to
> > > do it.
> > >
> > >
> > >
>
>
>

These commands will show it to you:
type c:\boot.ini
notepad c:\boot.ini


"baxter" <baxter@discussions.microsoft.com> wrote in message
news:A554E77A-92EB-40BF-BEC4-D1A4F9C39302@microsoft.com...
> Sorry for the delay. I cannot find boot.ini. I think it is the crashed
drive
> with Win98. I try to find in other PC also don't have this particular
file. I
> chose option view hidden files also cannot find.
>
> "Pegasus (MVP)" wrote:
>
> > Let's have a look at your hidden file c:\boot.ini! Timothy
> > Daniels already asked for this file but it seems you chose
> > to ignore his request.
> >
> > By the way, if you again wait almost two weeks until
> > you reply then this thread will have disappeared from
> > my newsreader's horizon and your reply will be
> > invisible to me.
> >
> >
> > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > news:010B46F0-A00A-47BF-AE31-50EDF47902A9@microsoft.com...
> > > I already install a spare drive with WinXP(with initial D drive
> > disconnect) .
> > > After that I reattached the drive but the PC just boot with the new OS
> > > ignoring the one in D drive. Must I reinstall the spare drive with the
D
> > > drive attached.
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > > >
> > > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > > news:22155FFB-15DB-42D1-80BE-04566A16BCAB@microsoft.com...
> > > > > I have try copying boot.ini from another bootable PC to D
drive(with
> > XP)
> > > > but
> > > > > cannot work.
> > > > > Is creating a C partition is the only way out?
> > > >
> > > > No, it is not the only way but unless you provide answers
> > > > to every question in my first reply I cannot tell you how to
> > > > do it.
> > > >
> > > >
> > > >
> >
> >
> >

I used to have 2 separate drives "c" with Win98 and "d" with WinXP. Now my
"c" is dead. Then I cannot boot even though I remove "c" and reconfigure the
IDE connection, "d" as primary drive. I ever ask guidance to remove WinXP
from dual boot and he point me to "c" that have boot.ini. Currently I also
have a PC with dual boot but the boot.ini is at "c" drive with Win98. So in
my dead PC there are no boot.ini as it is in "c" drive.

"Pegasus (MVP)" wrote:

> These commands will show it to you:
> type c:\boot.ini
> notepad c:\boot.ini
>
>
> "baxter" <baxter@discussions.microsoft.com> wrote in message
> news:A554E77A-92EB-40BF-BEC4-D1A4F9C39302@microsoft.com...
> > Sorry for the delay. I cannot find boot.ini. I think it is the crashed
> drive
> > with Win98. I try to find in other PC also don't have this particular
> file. I
> > chose option view hidden files also cannot find.
> >
> > "Pegasus (MVP)" wrote:
> >
> > > Let's have a look at your hidden file c:\boot.ini! Timothy
> > > Daniels already asked for this file but it seems you chose
> > > to ignore his request.
> > >
> > > By the way, if you again wait almost two weeks until
> > > you reply then this thread will have disappeared from
> > > my newsreader's horizon and your reply will be
> > > invisible to me.
> > >
> > >
> > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > news:010B46F0-A00A-47BF-AE31-50EDF47902A9@microsoft.com...
> > > > I already install a spare drive with WinXP(with initial D drive
> > > disconnect) .
> > > > After that I reattached the drive but the PC just boot with the new OS
> > > > ignoring the one in D drive. Must I reinstall the spare drive with the
> D
> > > > drive attached.
> > > >
> > > > "Pegasus (MVP)" wrote:
> > > >
> > > > >
> > > > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > > > news:22155FFB-15DB-42D1-80BE-04566A16BCAB@microsoft.com...
> > > > > > I have try copying boot.ini from another bootable PC to D
> drive(with
> > > XP)
> > > > > but
> > > > > > cannot work.
> > > > > > Is creating a C partition is the only way out?
> > > > >
> > > > > No, it is not the only way but unless you provide answers
> > > > > to every question in my first reply I cannot tell you how to
> > > > > do it.
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>
>

I just reread the whole thread in an attempt to
refamiliarise myself with your problem. Assuming
that you have a formatted drive C: in your machine,
presumably more or less empty, and a working c
opy of WinXP on drive D:, then you can revive
it like so:
1. Boot the machine with your WinXP CD.
2. Select Repair, then Recovery Console.
3. Execute these commands:
fixboot (to create a WinXP boot sector on drive C
fixmbr (to create a WinXP Master Boot Record)
bootcfg /rebuild (to create a new version of c:\boot.ini)
exit (to reboot the machine)

"baxter" <baxter@discussions.microsoft.com> wrote in message
news:75817E45-CEAC-459F-88E8-1DD146644803@microsoft.com...
> I used to have 2 separate drives "c" with Win98 and "d" with WinXP. Now my
> "c" is dead. Then I cannot boot even though I remove "c" and reconfigure
the
> IDE connection, "d" as primary drive. I ever ask guidance to remove WinXP
> from dual boot and he point me to "c" that have boot.ini. Currently I also
> have a PC with dual boot but the boot.ini is at "c" drive with Win98. So
in
> my dead PC there are no boot.ini as it is in "c" drive.
>
> "Pegasus (MVP)" wrote:
>
> > These commands will show it to you:
> > type c:\boot.ini
> > notepad c:\boot.ini
> >
> >
> > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > news:A554E77A-92EB-40BF-BEC4-D1A4F9C39302@microsoft.com...
> > > Sorry for the delay. I cannot find boot.ini. I think it is the crashed
> > drive
> > > with Win98. I try to find in other PC also don't have this particular
> > file. I
> > > chose option view hidden files also cannot find.
> > >
> > > "Pegasus (MVP)" wrote:
> > >
> > > > Let's have a look at your hidden file c:\boot.ini! Timothy
> > > > Daniels already asked for this file but it seems you chose
> > > > to ignore his request.
> > > >
> > > > By the way, if you again wait almost two weeks until
> > > > you reply then this thread will have disappeared from
> > > > my newsreader's horizon and your reply will be
> > > > invisible to me.
> > > >
> > > >
> > > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > > news:010B46F0-A00A-47BF-AE31-50EDF47902A9@microsoft.com...
> > > > > I already install a spare drive with WinXP(with initial D drive
> > > > disconnect) .
> > > > > After that I reattached the drive but the PC just boot with the
new OS
> > > > > ignoring the one in D drive. Must I reinstall the spare drive with
the
> > D
> > > > > drive attached.
> > > > >
> > > > > "Pegasus (MVP)" wrote:
> > > > >
> > > > > >
> > > > > > "baxter" <baxter@discussions.microsoft.com> wrote in message
> > > > > > news:22155FFB-15DB-42D1-80BE-04566A16BCAB@microsoft.com...
> > > > > > > I have try copying boot.ini from another bootable PC to D
> > drive(with
> > > > XP)
> > > > > > but
> > > > > > > cannot work.
> > > > > > > Is creating a C partition is the only way out?
> > > > > >
> > > > > > No, it is not the only way but unless you provide answers
> > > > > > to every question in my first reply I cannot tell you how to
> > > > > > do it.
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >

"Pegasus (MVP)" wrote:
>I just reread the whole thread in an attempt to
> refamiliarise myself with your problem. Assuming
> that you have a formatted drive C: in your machine,
> presumably more or less empty, and a working c
> opy of WinXP on drive D:, then you can revive
> it like so:
> 1. Boot the machine with your WinXP CD.
> 2. Select Repair, then Recovery Console.
> 3. Execute these commands:
> fixboot (to create a WinXP boot sector on drive C
> fixmbr (to create a WinXP Master Boot Record)
> bootcfg /rebuild (to create a new version of c:\boot.ini)
> exit (to reboot the machine)


What utility would supply the ntldr and ntdetect.com
files (needed along with boot.ini for booting the OS)?

*TimDaniels*

"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
news:6umdnf_Xmpg6bCnenZ2dnUVZ_sOdnZ2d@comcast.com. ..
> "Pegasus (MVP)" wrote:
> >I just reread the whole thread in an attempt to
> > refamiliarise myself with your problem. Assuming
> > that you have a formatted drive C: in your machine,
> > presumably more or less empty, and a working c
> > opy of WinXP on drive D:, then you can revive
> > it like so:
> > 1. Boot the machine with your WinXP CD.
> > 2. Select Repair, then Recovery Console.
> > 3. Execute these commands:
> > fixboot (to create a WinXP boot sector on drive C
> > fixmbr (to create a WinXP Master Boot Record)
> > bootcfg /rebuild (to create a new version of c:\boot.ini)
> > exit (to reboot the machine)
>
>
> What utility would supply the ntldr and ntdetect.com
> files (needed along with boot.ini for booting the OS)?
>
> *TimDaniels*

Mhhm. Good question. Boot.ini is easily generated
by the bootcfg command (it's just a humble text file)
but the OP would probably have to copy the two
other files from the i386 folder of his WinXP CD,
perhaps via a floppy disk if his CD drive is inaccessible
while in the Recovery Console. Seeing how this is a
looooooooooooong drawn out thread, I think the OP
will easy find the time to test this for himself.

"Pegasus (MVP)" replied:
> "Timothy Daniels" wrote:
>> "Pegasus (MVP)" wrote:
>> > [...] Assuming
>> > that you have a formatted drive C: in your machine,
>> > presumably more or less empty, and a working c
>> > opy of WinXP on drive D:, then you can revive
>> > it like so:
>> > 1. Boot the machine with your WinXP CD.
>> > 2. Select Repair, then Recovery Console.
>> > 3. Execute these commands:
>> > fixboot (to create a WinXP boot sector on drive C
>> > fixmbr (to create a WinXP Master Boot Record)
>> > bootcfg /rebuild (to create a new version of c:\boot.ini)
>> > exit (to reboot the machine)
>>
>>
>> What utility would supply the ntldr and ntdetect.com
>> files (needed along with boot.ini for booting the OS)?
>>
>> *TimDaniels*
>
> Mhhm. Good question. Boot.ini is easily generated
> by the bootcfg command (it's just a humble text file)
> but the OP would probably have to copy the two
> other files from the i386 folder of his WinXP CD,
> perhaps via a floppy disk if his CD drive is inaccessible
> while in the Recovery Console. Seeing how this is a
> looooooooooooong drawn out thread, I think the OP
> will easy find the time to test this for himself.


Thanks. I asked the question because there frequently
appears the problem about single-booting an OS that had
previously been part of a dual-boot where the load files
(i.e. boot.ini, ntldr, and ntdetect.com) were in the partition
containing the removed OS. More specifically, the load
files and OS #1 were in what the poster calls the "C:"
drive, and OS #2 resides in the "D:" drive, and he wants
to boot OS #2 without the "C:" drive present. So the
problem then arises about providing the load files for the
"D:" drive. If ntldr and ntdetect.com could simply be copied
over from the "C:" drive, would they work on the "D:" drive?

*TimDaniels*

"Timothy Daniels" <TDaniels@NoSpamDot.com> wrote in message
news:fuWdnYmURrYqGyjeRVn-sw@comcast.com...
>
> "Pegasus (MVP)" replied:
> > "Timothy Daniels" wrote:
> >> "Pegasus (MVP)" wrote:
> >> > [...] Assuming
> >> > that you have a formatted drive C: in your machine,
> >> > presumably more or less empty, and a working c
> >> > opy of WinXP on drive D:, then you can revive
> >> > it like so:
> >> > 1. Boot the machine with your WinXP CD.
> >> > 2. Select Repair, then Recovery Console.
> >> > 3. Execute these commands:
> >> > fixboot (to create a WinXP boot sector on drive C
> >> > fixmbr (to create a WinXP Master Boot Record)
> >> > bootcfg /rebuild (to create a new version of c:\boot.ini)
> >> > exit (to reboot the machine)
> >>
> >>
> >> What utility would supply the ntldr and ntdetect.com
> >> files (needed along with boot.ini for booting the OS)?
> >>
> >> *TimDaniels*
> >
> > Mhhm. Good question. Boot.ini is easily generated
> > by the bootcfg command (it's just a humble text file)
> > but the OP would probably have to copy the two
> > other files from the i386 folder of his WinXP CD,
> > perhaps via a floppy disk if his CD drive is inaccessible
> > while in the Recovery Console. Seeing how this is a
> > looooooooooooong drawn out thread, I think the OP
> > will easy find the time to test this for himself.
>
>
> Thanks. I asked the question because there frequently
> appears the problem about single-booting an OS that had
> previously been part of a dual-boot where the load files
> (i.e. boot.ini, ntldr, and ntdetect.com) were in the partition
> containing the removed OS. More specifically, the load
> files and OS #1 were in what the poster calls the "C:"
> drive, and OS #2 resides in the "D:" drive, and he wants
> to boot OS #2 without the "C:" drive present. So the
> problem then arises about providing the load files for the
> "D:" drive. If ntldr and ntdetect.com could simply be copied
> over from the "C:" drive, would they work on the "D:" drive?
>
> *TimDaniels*

Yes, they would, and it's what I should have said in the
first place. Thanks for pointing it out.

"Pegasus (MVP)" replied:
>> "Timothy Daniels" asked:
>> [........] there frequently
>> appears the problem about single-booting an OS that had
>> previously been part of a dual-boot where the load files
>> (i.e. boot.ini, ntldr, and ntdetect.com) were in the partition
>> containing the removed OS. More specifically, the load
>> files and OS #1 were in what the poster calls the "C:"
>> drive, and OS #2 resides in the "D:" drive, and he wants
>> to boot OS #2 without the "C:" drive present. So the
>> problem then arises about providing the load files for the
>> "D:" drive. If ntldr and ntdetect.com could simply be copied
>> over from the "C:" drive, would they work on the "D:" drive?
>
> Yes, they would, and it's what I should have said in the
> first place. Thanks for pointing it out.


Whew! Thanks. That question has been echoing
around the WindowsXP newsgroups for more than a
year without an answer until now.

*TimDaniels*

I think I can follow Pegasus way to recreate a boot.ini file. But for ntldr
and ntdetect I will be copying from WinXP CD. Right?

"Timothy Daniels" wrote:

> "Pegasus (MVP)" replied:
> >> "Timothy Daniels" asked:
> >> [........] there frequently
> >> appears the problem about single-booting an OS that had
> >> previously been part of a dual-boot where the load files
> >> (i.e. boot.ini, ntldr, and ntdetect.com) were in the partition
> >> containing the removed OS. More specifically, the load
> >> files and OS #1 were in what the poster calls the "C:"
> >> drive, and OS #2 resides in the "D:" drive, and he wants
> >> to boot OS #2 without the "C:" drive present. So the
> >> problem then arises about providing the load files for the
> >> "D:" drive. If ntldr and ntdetect.com could simply be copied
> >> over from the "C:" drive, would they work on the "D:" drive?
> >
> > Yes, they would, and it's what I should have said in the
> > first place. Thanks for pointing it out.
>
>
> Whew! Thanks. That question has been echoing
> around the WindowsXP newsgroups for more than a
> year without an answer until now.
>
> *TimDaniels*
>