Boot Problems...

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

When I boot it's a black screen and it says like

Windows XP Pro (Bootscreen)
Windows XP Pro
Windows Recovery Console


I have to hit enter on one of two top ones to start, then everything works
fine. I'm not even running pro, I have media edition. How do I make it auto
start without having that screen come up every time?
 
This will change the time XP waits before choosing the default system to 3
seconds.
Start, Run, "bootcfg /timeout3" without the quotes.

How to edit the Boot.ini file in Windows XP
http://support.microsoft.com/kb/289022

--
Ronald Sommer

: When I boot it's a black screen and it says like
:
: Windows XP Pro (Bootscreen)
: Windows XP Pro
: Windows Recovery Console
:
:
: I have to hit enter on one of two top ones to start, then everything works
: fine. I'm not even running pro, I have media edition. How do I make it
auto
: start without having that screen come up every time?
 
Replied to [Ron Sommer]s message :

Start, Run, "bootcfg /timeout3" without the quotes.
Click to expand...

Proper syntax is :
bootcfg /timeout 3

To OP:
Run these commands one by one from Start/Run:
bootcfg /default /id 2
bootcfg /delete /id 2
bootcfg /delete /id 2

Then Start> Run> msconfig > Boot.ini tab > Check all boot paths

→ Ayush [ Good :-) Luck ]
 
Your correction implies that the Knowledge Base article is not correct.
bootcfg is only available in Pro so I have no way of checking.
You have to be in a cmd window to run bootcfg commands.
I have another problem with your instructions. Assuming there should be a
space between id and the number. Shouldn't it be:

To OP:
Start, Run, cmd
Run these commands one by one:
bootcfg /default /id 2
bootcfg /delete /id 1
bootcfg /delete /id 2

Then Start> Run> msconfig > Boot.ini tab > Check all boot paths


--
Ronald Sommer

"Ayush" <"ayushmaan.j[aatt]gmail.com"> wrote in message
: Replied to [Ron Sommer]s message :
:
:
: > Start, Run, "bootcfg /timeout3" without the quotes.
:
: Proper syntax is :
: bootcfg /timeout 3
:
: To OP:
: Run these commands one by one from Start/Run:
: bootcfg /default /id 2
: bootcfg /delete /id 2
: bootcfg /delete /id 2
:
: Then Start> Run> msconfig > Boot.ini tab > Check all boot paths
:
: → Ayush [ Good :-) Luck ]
: -------------
: Search - www.Google.com | Wikipedia - http://en.wikipedia.org
: Snip your long urls - http://snipurl.com/
: -------------
 
Replied to [Ron Sommer]s message :
Your correction implies that the Knowledge Base article is not correct.
Click to expand...


Dont know about that but before replying, i tried that and got an error :
- - -
ERROR: Invalid syntax.
Type "BOOTCFG /?" for usage.
- - -
Shouldn't it be:

To OP:
Start, Run, cmd
Run these commands one by one:
bootcfg /default /id 2
bootcfg /delete /id 1
bootcfg /delete /id 2
Click to expand...

The default parameter sets the default boot item to the ID# specified [AND] moves
that ID# to top (ID #1)

So in this case, after running the first line, "windows XP Pro" (that was #2 before)
will be ID #1

→ Ayush [ Good :-) Luck ]
 
If you are going to continue to post in the newsgroups, please include the
previous messages.

My message stated, ""bootcfg /timeout3" without the quotes."

Your message said, Proper syntax is : bootcfg /timeout 3
The KB article had bootcfg /timeout3
Should there be a space between timeout and the number?
You also put a space between id and the number.
Should that space be there?
You are writing ID# with no space, but when you use a number, you are using
a space.
--
Ronald Sommer


"Ayush" <"ayushmaan.j[aatt]gmail.com"> wrote in message
: Replied to [Ron Sommer]s message :
: > Your correction implies that the Knowledge Base article is not correct.
:
:
: Dont know about that but before replying, i tried that and got an error :
: - - -
: ERROR: Invalid syntax.
: Type "BOOTCFG /?" for usage.
: - - -
:
: > Shouldn't it be:
: >
: > To OP:
: > Start, Run, cmd
: > Run these commands one by one:
: > bootcfg /default /id 2
: > bootcfg /delete /id 1
: > bootcfg /delete /id 2
:
: The default parameter sets the default boot item to the ID# specified
[AND] moves
: that ID# to top (ID #1)
:
: So in this case, after running the first line, "windows XP Pro" (that was
#2 before)
: will be ID #1
:
: → Ayush [ Good :-) Luck ]
: -------------
: Search - www.Google.com | Wikipedia - http://en.wikipedia.org
: Snip your long urls - http://snipurl.com/
: -------------
:
:
:
 
Replied to [Ron Sommer]s message :
If you are going to continue to post in the newsgroups, please include the
previous messages.
Click to expand...

I dont understand what you mean by previous messages ..

My message stated, ""bootcfg /timeout3" without the quotes."

Your message said, Proper syntax is : bootcfg /timeout 3
The KB article had bootcfg /timeout3
Should there be a space between timeout and the number?
Click to expand...

Yes, i told you. Without the space, there will be error message :
ERROR: Invalid syntax.
Type "BOOTCFG /?" for usage.

You also put a space between id and the number.
Should that space be there?
Click to expand...

Yes, if you run the command without the space then :
ERROR: Invalid Argument/Option - '/ID4'.
Type "BOOTCFG /DELETE /?" for usage.

(I tested on bootcfg /delete /ID4)

You are writing ID# with no space, but when you use a number, you are using
a space.
Click to expand...

There should be a space after ID and before the number.


→ Ayush [ Good :-) Luck ]
 
Ayush said:
Replied to [Ron Sommer]s message :
If you are going to continue to post in the newsgroups, please include the
previous messages.
Click to expand...

I dont understand what you mean by previous messages ..
Click to expand...


He means to quote the thread. These microsoft.public NGs fill so fast
that the MVPs seem to flush their cache (i.e. "local folders") after every
pass through the NG, and when you follow up with another question, they
don't have a clue what had already been said in the thread.

*TimDaniels*
 
Ayush said:
Replied to [Ron Sommer]s message :
If you are going to continue to post in the newsgroups, please include
the previous messages.
Click to expand...

I dont understand what you mean by previous messages ..
Click to expand...


He means to quote the thread. These microsoft.public NGs fill so fast
that the MVPs seem to flush their cache (i.e. "local folders") after every
pass through the NG, and when you follow up with another question, they
don't have a clue what had already been said in the thread.

*TimDaniels*
Click to expand...

Even when we have it front of us we might not have a clue, eh? Lol
 
Replied to [Timothy Daniels]s message :
Ayush said:
Replied to [Ron Sommer]s message :
If you are going to continue to post in the newsgroups, please
include the previous messages.
Click to expand...

I dont understand what you mean by previous messages ..
Click to expand...


He means to quote the thread. These microsoft.public NGs fill so fast
that the MVPs seem to flush their cache (i.e. "local folders") after every
pass through the NG, and when you follow up with another question, they
don't have a clue what had already been said in the thread.

*TimDaniels*
Click to expand...



I followed the USENET posting standard :
http://www.netmeister.org/news/learn2quote2.html


→ Ayush [ Good :-) Luck ]
 
"Ayush" <"ayushmaan.j[aatt]gmail.com"> wrote in message
: Replied to [Timothy Daniels]s message :
: > "Ayush" wrote:
: >> Replied to [Ron Sommer]s message :
: >>> If you are going to continue to post in the newsgroups, please
: >>> include the previous messages.
: >>
: >> I dont understand what you mean by previous messages ..
: >
: >
: > He means to quote the thread. These microsoft.public NGs fill so
fast
: > that the MVPs seem to flush their cache (i.e. "local folders") after
every
: > pass through the NG, and when you follow up with another question, they
: > don't have a clue what had already been said in the thread.
: >
: > *TimDaniels*
:
:
:
: I followed the USENET posting standard :
: http://www.netmeister.org/news/learn2quote2.html
:
:
Last time I looked this is not USENET.
Why should I have to look for previous messages to understand what was
posted before.
After I have marked a message as read, it is extra effort to look for the
earlier posts.
I also do not understand the logic of putting replies under the original
post. If I am following a thread, I have to scroll to the bottom to read
the replies.
 
from the wonderful said:
"Ayush" <"ayushmaan.j[aatt]gmail.com"> wrote in message
: Replied to [Timothy Daniels]s message :
: > "Ayush" wrote:
: >> Replied to [Ron Sommer]s message :
: >>> If you are going to continue to post in the newsgroups, please
: >>> include the previous messages.
: >>
: >> I dont understand what you mean by previous messages ..
: >
: >
: > He means to quote the thread. These microsoft.public NGs fill so
fast
: > that the MVPs seem to flush their cache (i.e. "local folders") after
every
: > pass through the NG, and when you follow up with another question, they
: > don't have a clue what had already been said in the thread.
: >
: > *TimDaniels*
:
:
:
: I followed the USENET posting standard :
: http://www.netmeister.org/news/learn2quote2.html
:
Last time I looked this is not USENET.
Click to expand...

You are deeply confused, of course it is USENET (aka NNTP, aka News
service).
 
Last time I looked this is not USENET.
Why should I have to look for previous messages to understand what was
posted before.
After I have marked a message as read, it is extra effort to look for the
earlier posts.
I also do not understand the logic of putting replies under the original
post. If I am following a thread, I have to scroll to the bottom to read
the replies.
Click to expand...

This is Usenet. Bottom posting is the norm because that's the flow of
communication. - one response follows another - but in this newsgroup
(which goes for the other MS newsgroups), top posting is accepted too.
Either way is ok. One should quote part of the message to which they reply
and snip unneeded parts.
 
Back
Top