msconfig problem.....

[Guest]

After copying my windows installation to a new drive, using MaxBlast 4, and
after booting to the new drive successfully msconfig no longer works. When I
type it into the RUN box and press OK it does not work. I see a little flash
on the screen like something happening in the background and then nothing.
Can i repair msconfig somehow?

 

[Pegasus \(MVP\)]

After copying my windows installation to a new drive, using MaxBlast 4, and
after booting to the new drive successfully msconfig no longer works. When I
type it into the RUN box and press OK it does not work. I see a little flash
on the screen like something happening in the background and then nothing.
Can i repair msconfig somehow?

You're jumping to conclusions by assuming that msconfig.exe
does not work. I suspect something entirely different. Give
yourself some eyes so that you can see what's going on, by
running msconfig.exe from a Command Prompt. You can
start a Command Prompt by clicking Start / Run / cmd {OK}.

 

[Guest]

Ok I opened a cmd prompt window and when I type msconfig.exe it says that
command is not recognized as an internal or external command. The only reason
i ran it is because, for some reason, upon boot I get to choose between 2
windows(default) and i only ave 1 windows installation on c drive.

 

[Haggis]

After copying my windows installation to a new drive, using MaxBlast 4,
and
after booting to the new drive successfully msconfig no longer works. When
I
type it into the RUN box and press OK it does not work. I see a little
flash
on the screen like something happening in the background and then nothing.
Can i repair msconfig somehow?

try a "repair" install

http://www.michaelstevenstech.com/XPrepairinstall.htm

 

[HeyBub]

Ok I opened a cmd prompt window and when I type msconfig.exe it says
that command is not recognized as an internal or external command.

That simply means that Windows cannot FIND msconfig. So,

1. Does msconfig.exe exist on your machine?
2. Is its location mentioned in the PATH environment variable?

 

[Pegasus \(MVP\)]

This is what I expected. Next three steps:
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?
2. Type set systemroot {Enter}
Does it say "c:\windows"?
3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

 

[Guest]

ok I just performed a file search and I found it does exist in the machine.
It is there in the system32 dll cache and also in prefetch as
msconfig.exe-330AFD63.pf. So it is there bit it seems not to want to run. i
think a repair install may be my only option at this point.

 

[Brian Ryman]

From your description, msconfig cannot solve your problem(upon boot I get to
choose between 2 windows) and the problem is in boot.ini. You may check
below article for how to edit boot.ini.

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

Regards,
-Brian

 

[Guest]

when I open the control panel under advanced and then Edit I see
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\winnt
[operating systems]

This seems normal to me.

 

[Guest]

Pegasus,
This is what I got..........
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?

Yes. on my system it is c:\winnt\system32

2. Type set systemroot {Enter}
Does it say "c:\windows"?

yes. it says c:\winnt

3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

No. Windows does not find the file.

 

[Pegasus \(MVP\)]

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm

 

[Guest]

Pegasus, HeyBub, Brian and Haggis,

I took a look at the boot.ini file and compared it to the sample one on the
microsoft knowledge base from the link provided by Brian. I simple copied and
pasted it to my boot.ini file and changed "windows" to "winnt" for my system
and Msconfig works like a charm now.And the dual boot choice is gone. So
thanks to all who weighed in on this problem!

when I open the control panel under advanced and then Edit I see
[boot loader]
timeout=5
default=multi(0)disk(0)rdisk(0)partition(1)\winnt
[operating systems]

This seems normal to me.

From your description, msconfig cannot solve your problem(upon boot I get to
choose between 2 windows) and the problem is in boot.ini. You may check
below article for how to edit boot.ini.

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

Regards,
-Brian

 

[Wesley Vogel]

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows. On
an upgrade, Setup uses the current path for %WinDir% - for Windows 98 or
Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows 2000,
the drive letter may vary, but the name of the system folder is usually
\Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the installation
will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in WINNT
if they used the System Preparation Tool and never changed the setup from
WINNT to WINDOWS. Or decided for whatever reason to use WINNT instead of
WINDOWS.

I know a good number of people who have bought Gateways with XP preinstalled
in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting the
install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that it
can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

 

[Wesley Vogel]

That got away from me. After reading all of the posts I see that the OP had
a dual boot.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows. On
an upgrade, Setup uses the current path for %WinDir% - for Windows 98 or
Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows
2000, the drive letter may vary, but the name of the system folder is
usually \Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the
installation will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in
WINNT if they used the System Preparation Tool and never changed the
setup from WINNT to WINDOWS. Or decided for whatever reason to use WINNT
instead of WINDOWS.

I know a good number of people who have bought Gateways with XP
preinstalled in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting
the install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that
it can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm

 

[Kelly]

I know a good number of people who have bought Gateways with XP

preinstalled
in C:\WINNT.

Add me to the list.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows. On
an upgrade, Setup uses the current path for %WinDir% - for Windows 98 or
Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows
2000,
the drive letter may vary, but the name of the system folder is usually
\Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the
installation
will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in
WINNT
if they used the System Preparation Tool and never changed the setup from
WINNT to WINDOWS. Or decided for whatever reason to use WINNT instead of
WINDOWS.

I know a good number of people who have bought Gateways with XP
preinstalled
in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting
the
install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that
it
can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm

 

[Kelly]

Boot.ini is in msconfig.exe

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm

 

[Pegasus \(MVP\)]

I think we both know full well that Windows can go into just
about any folder on any drive. My question was a wild guess,
based on what the OP reported and his apparent level of
experience.

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows. On
an upgrade, Setup uses the current path for %WinDir% - for Windows 98 or
Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows 2000,
the drive letter may vary, but the name of the system folder is usually
\Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the installation
will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in WINNT
if they used the System Preparation Tool and never changed the setup from
WINNT to WINDOWS. Or decided for whatever reason to use WINNT instead of
WINDOWS.

I know a good number of people who have bought Gateways with XP preinstalled
in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting the
install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that it
can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm

 

[Wesley Vogel]

Hi Kelly,

You're already on the list.

From a question I posted in one of the DTS lists a year or so ago. You
mentioned, "All three of my Gateway systems here are Winnt."

I was really confused about WINNT or WINDOWS at that time. I have moved on
to being confused about other things now. ;-)

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I know a good number of people who have bought Gateways with XP
preinstalled
in C:\WINNT.

Add me to the list.

--

All the Best,
Kelly (MS-MVP/DTS&XP)

Taskbar Repair Tool
http://www.kellys-korner-xp.com/taskbarplus!.htm

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows.
On an upgrade, Setup uses the current path for %WinDir% - for Windows 98
or Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows
2000,
the drive letter may vary, but the name of the system folder is usually
\Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the
installation
will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in
WINNT
if they used the System Preparation Tool and never changed the setup from
WINNT to WINDOWS. Or decided for whatever reason to use WINNT instead of
WINDOWS.

I know a good number of people who have bought Gateways with XP
preinstalled
in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting
the
install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that
it
can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm


Pegasus,
This is what I got..........
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?

Yes. on my system it is c:\winnt\system32

2. Type set systemroot {Enter}
Does it say "c:\windows"?

yes. it says c:\winnt

3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

No. Windows does not find the file.


:

This is what I expected. Next three steps:
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?
2. Type set systemroot {Enter}
Does it say "c:\windows"?
3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

Ok I opened a cmd prompt window and when I type msconfig.exe it says
that command is not recognized as an internal or external command.
The only reason i ran it is because, for some reason, upon boot I
get to choose between 2 windows(default) and i only ave 1 windows
installation on c drive.

:


After copying my windows installation to a new drive, using
MaxBlast
4,
and
after booting to the new drive successfully msconfig no longer
works.
When
I
type it into the RUN box and press OK it does not work. I see a
little flash on the screen like something happening in the
background and then nothing. Can i repair msconfig somehow?

You're jumping to conclusions by assuming that msconfig.exe
does not work. I suspect something entirely different. Give
yourself some eyes so that you can see what's going on, by
running msconfig.exe from a Command Prompt. You can
start a Command Prompt by clicking Start / Run / cmd {OK}.

 

[Wesley Vogel]

Pegasus,

As I stated, that post got away from me. I didn't mean to send it. <shrug>

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

I think we both know full well that Windows can go into just
about any folder on any drive. My question was a wild guess,
based on what the OP reported and his apparent level of
experience.

Windows XP can be in the WINNT folder or the WINDOWS folder.

[[On a clean install, Setup creates a top-level folder called Windows.
On an upgrade, Setup uses the current path for %WinDir% - for Windows 98
or Windows Me, that’s typically C:\Windows; for Windows NT 4 and Windows
2000, the drive letter may vary, but the name of the system folder is
usually \Winnt. ]]

If you do an upgrade over Win 2000, which uses WINNT, then the
installation will be in WINNT.

If you have an OEM installed version (like on a Gateway) it may be in
WINNT if they used the System Preparation Tool and never changed the
setup from WINNT to WINDOWS. Or decided for whatever reason to use
WINNT instead of WINDOWS.

I know a good number of people who have bought Gateways with XP
preinstalled in C:\WINNT.

%windir% can be anything that the person doing the install, or scripting
the install, chooses.

When performing a clean install, you can specify a different folder name,
but your safest choice is to use the default name.

It makes no difference if the %windir% is WINNT or WINDOWS. Except that
it can be confusing.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In

You're posting in a Windows XP newsgroup but I suspect
that you're running Windows 2000. If so then you must
download msconfig.exe from the site below and copy it
into c:\winnt\system32.
http://www.svrops.com/svrops/dwnldoth.htm


Pegasus,
This is what I got..........
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?

Yes. on my system it is c:\winnt\system32

2. Type set systemroot {Enter}
Does it say "c:\windows"?

yes. it says c:\winnt

3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

No. Windows does not find the file.


:

This is what I expected. Next three steps:
1. At the Command Prompt, type path {Enter}.
Is the folder "c:\windows\system32" included?
2. Type set systemroot {Enter}
Does it say "c:\windows"?
3. Type dir c:\windows\system32\msconfig.exe {Enter}
Can Windows find the file?

Ok I opened a cmd prompt window and when I type msconfig.exe it says
that command is not recognized as an internal or external command.
The only reason i ran it is because, for some reason, upon boot I
get to choose between 2 windows(default) and i only ave 1 windows
installation on c drive.

:


After copying my windows installation to a new drive, using
MaxBlast
4,
and
after booting to the new drive successfully msconfig no longer
works.
When
I
type it into the RUN box and press OK it does not work. I see a
little flash on the screen like something happening in the
background and then nothing. Can i repair msconfig somehow?

You're jumping to conclusions by assuming that msconfig.exe
does not work. I suspect something entirely different. Give
yourself some eyes so that you can see what's going on, by
running msconfig.exe from a Command Prompt. You can
start a Command Prompt by clicking Start / Run / cmd {OK}.