MSCONFIG of slave drive

[Paul Smith]

MSCONFIG of slave drive

Hi all

I would like to know if there is a way how I could see the startup config of
a hard drive connected as slave?

That is seeing the same output that gives MSCONFIG...

any help is appreciated! Thanks all

 

[Malke]

MSCONFIG of slave drive

Hi all

I would like to know if there is a way how I could see the startup config of
a hard drive connected as slave?

That is seeing the same output that gives MSCONFIG...

I'm sorry but this doesn't make sense. A slave drive usually only has
data on it. While you may have installed some programs on it, the
registry information - including startup calls - is on the system drive.
So there is no "msconfig" to run on a slave drive, only on a system
drive. That's why the command msconfig calls the System Configuration
Utility.

If the slave drive has another operating system on it and you have a
dual-boot situation and if the second operating system is XP also, then
running msconfig while booted into the second operating system will give
information for it and not the operating system installed on the first
drive.

Perhaps if you explain exactly what you've done and are trying to do
someone can give you more specific help.


Malke

 

[Paul Smith]

OK heres the scenario

I have a problem which pops up a script like window just before getting into
Windows and then causes PC to restart. Happens in safe mode too so theres no
way to avoid it!

I thought connecting the drive as slave and seeing the startup config might
be able to allow me to tweak something there and then.

 

[Detlev Dreyer]

I would like to know if there is a way how I could see the startup config
of a hard drive connected as slave?

Your question doesn't make any sense. Therefore, the short answer is 'No'.

 

[Malke]

OK heres the scenario

I have a problem which pops up a script like window just before getting into
Windows and then causes PC to restart. Happens in safe mode too so theres no
way to avoid it!

I thought connecting the drive as slave and seeing the startup config might
be able to allow me to tweak something there and then.

You can boot with a Bart's PE or other rescue system such as ERD
Commander (no longer available and it was very expensive when it was)
and look at the registry on the hard drive to see what may be there.

You might be able to slave the drive in a working XP system and load its
registry hive to look at it. I always use a rescue CD so someone else
will need to address this point.

You cannot run the registry editor or msconfig on the drive while it is
slaved to a working XP install.

http://www.nu2.nu/pebuilder/ - Bart's PE Builder

There is no guarantee that looking at the registry will provide the
answer. What does the "script like window" say? What changed between the
time things worked and the time they didn't? Have you tried Last Known
Good Configuration? (If not, then try it.)


Malke

 

[Gerry]

Paul

Disable automatic restart on system failure. This should help by
allowing time to write down the STOP code properly. Right click on
the My Computer icon on the Desktop and select Properties, Advanced,
Start-Up and Recovery, System Failure and uncheck box before
Automatically Restart.

Do not re-enable automatic restart on system failure even after you have
solved the problem as it's better disabled. Check for variants of the
Stop Error message.

An alternative is to keep pressing the F8 key during Start-Up and select
option - Disable automatic restart on system failure.

If you are using a wireless keyboard and the F8 key does not work
substitute a wired keyboard and mouse for this exercise only.


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~