XP computer fails to reboot

What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
I have a computer that runs XP Pro (SP-3) that fails to boot every time.

This was shut down properly, however, it now will not boot back up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
I have a computer that runs XP Pro (SP-3) that fails to boot every time.

This was shut down properly, however, it now will not boot back up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

What kind of risk is there in wipping out data by running "repair console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
I have a computer that runs XP Pro (SP-3) that fails to boot every time.

This was shut down properly, however, it now will not boot back up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot every
time.

This was shut down properly, however, it now will not boot back up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

You are correct in that I don't have specific experience with the repair
console. However, I am somewhat familiar with the command prompt and a few
"basic" dos commands.

I did not want to approach this full speed ahead only to find out my data
will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these present a
danger of wipping out my data? Is there one that would better than the
others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot every
time.

This was shut down properly, however, it now will not boot back up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

There is *always* a risk of data loss when chkdsk is run. If you have
important data that is not backed up you should take proper steps to
attempt to salvage your data before you run chkdsk.

John

Jbarrick wrote:

You are correct in that I don't have specific experience with the repair
console. However, I am somewhat familiar with the command prompt and a few
"basic" dos commands.

I did not want to approach this full speed ahead only to find out my data
will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these present a
danger of wipping out my data? Is there one that would better than the
others to try first, or should I run all of these?


"databaseben" wrote:


like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...

What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:


i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...

What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:


my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...

I have a computer that runs XP Pro (SP-3) that fails to boot every
time.

This was shut down properly, however, it now will not boot back up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

fixboot and fixmbr will not
affect your personal files.

so you can try to run the above
first then exit and try to boot
w/o the cd.

however, chkdsk reconciles
the files in the file system against
the master file table.

so if the master file table became
corrupted as a result of sp3,
then there are some system files
that need to be audited by the
chkdsk tool.

the question that only you can
answer is if you had pre existing
issues with the functionality of your
system and instead of correcting them
you chose to install sp3 instead which
may have made things worse than
better.

ideally, before installing sp3
some disk and file system maintenance
should have been performed to ensure
a smooth update, like removing the
trash, running a chkdsk and a defrag.

the above plus undertaking precautions
to protect personal data/files would
ensure you a reasonable amount of leaway
to excercise some risk without worrying
about the loss of personal data.

however if sp3 was installed out of convenience
and you had no pre existing issues and
for all practical purposes your system
was functional before sp3, then a chkdsk
should not attibute to any loss of data.

instead the chkdsk will reconcile the
system files that are preventing you
to boot with the master file table.


"Jbarrick" wrote in message
...
You are correct in that I don't have specific experience with the repair
console. However, I am somewhat familiar with the command prompt and a
few
"basic" dos commands.

I did not want to approach this full speed ahead only to find out my data
will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these present a
danger of wipping out my data? Is there one that would better than the
others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot every
time.

This was shut down properly, however, it now will not boot back
up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

I attempted to boot with the CD and ended up with the following error message:

***STOP: 0x0000007E (0xC0000005, 0xF748E0BF, 0xF78DA208, 0xF78D9F08)

*** pci.sys - Address F748E0BF base at F7487000, DateStamp 3b7d855c



"databaseben" wrote:

fixboot and fixmbr will not
affect your personal files.

so you can try to run the above
first then exit and try to boot
w/o the cd.

however, chkdsk reconciles
the files in the file system against
the master file table.

so if the master file table became
corrupted as a result of sp3,
then there are some system files
that need to be audited by the
chkdsk tool.

the question that only you can
answer is if you had pre existing
issues with the functionality of your
system and instead of correcting them
you chose to install sp3 instead which
may have made things worse than
better.

ideally, before installing sp3
some disk and file system maintenance
should have been performed to ensure
a smooth update, like removing the
trash, running a chkdsk and a defrag.

the above plus undertaking precautions
to protect personal data/files would
ensure you a reasonable amount of leaway
to excercise some risk without worrying
about the loss of personal data.

however if sp3 was installed out of convenience
and you had no pre existing issues and
for all practical purposes your system
was functional before sp3, then a chkdsk
should not attibute to any loss of data.

instead the chkdsk will reconcile the
system files that are preventing you
to boot with the master file table.


"Jbarrick" wrote in message
...
You are correct in that I don't have specific experience with the repair
console. However, I am somewhat familiar with the command prompt and a
few
"basic" dos commands.

I did not want to approach this full speed ahead only to find out my data
will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these present a
danger of wipping out my data? Is there one that would better than the
others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot every
time.

This was shut down properly, however, it now will not boot back
up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

Jbarrick

Chkdsk can corrupt the data on the disk. It's an inherent risk. If you
have not backed up the data there are two ways you can still do so.

For either way you need a second computer. If the second computer is a
desktop and can take two drives you can remove the drive from first
computer and put it in the second computer as a slave. The computer
boots off the first (or master ) drive and you should be able to read
and copy off the data on the second drive. If the second computer does
not the capability of taking a second hard drive or it is a laptop you
can place the hard drive from the first computer in an external cradle
linked to the second computer. You can then read and copy from the drive
in the external cradle.

The next link illustrates what I mean by an external cradle:
http://www.storagedepot.co.uk/Enclos...c884/p753.aspx

Alternatively any small computer repair shop can back up data for you.


--



Hope this helps.

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


Jbarrick wrote:
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few "basic" dos commands.

I did not want to approach this full speed ahead only to find out my
data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot back
up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

When attempting to boot from the CD, I never got the option of repair console
or a command prompt to try fixboot, fixmbr or chkdsk.

Could I be doing something wrong?






"Gerry" wrote:


Jbarrick

Chkdsk can corrupt the data on the disk. It's an inherent risk. If you
have not backed up the data there are two ways you can still do so.

For either way you need a second computer. If the second computer is a
desktop and can take two drives you can remove the drive from first
computer and put it in the second computer as a slave. The computer
boots off the first (or master ) drive and you should be able to read
and copy off the data on the second drive. If the second computer does
not the capability of taking a second hard drive or it is a laptop you
can place the hard drive from the first computer in an external cradle
linked to the second computer. You can then read and copy from the drive
in the external cradle.

The next link illustrates what I mean by an external cradle:
http://www.storagedepot.co.uk/Enclos...c884/p753.aspx

Alternatively any small computer repair shop can back up data for you.


--



Hope this helps.

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


Jbarrick wrote:
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few "basic" dos commands.

I did not want to approach this full speed ahead only to find out my
data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot back
up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

Jbarrick

Background information on Stop Error message:
http://msdn2.microsoft.com/en-us/library/ms795746.aspx

0x0000007E: SYSTEM_THREAD_EXCEPTION_NOT_HANDLED
A system thread generated an exception which the error handler did not
catch. There are numerous individual causes for this problem, including
hardware incompatibility, a faulty device driver or system service, or
some software issues. Check Event Viewer (EventVwr.msc) for additional
information.
Source: http://aumha.org/a/stop.htm

How to Troubleshoot a Stop 0x0000007E Error in Windows XP
http://support.microsoft.com/kb/330182/en-us

This is not an easy error to resolve:
http://www.google.com/search?hl=en&l...ys+XP&as_qdr=y


--



Hope this helps.

Gerry
~~~~
FCA
Stourport, England
Enquire, plan and execute
~~~~~~~~~~~~~~~~~~~
Jbarrick wrote:
I attempted to boot with the CD and ended up with the following error
message:

***STOP: 0x0000007E (0xC0000005, 0xF748E0BF, 0xF78DA208, 0xF78D9F08)

*** pci.sys - Address F748E0BF base at F7487000, DateStamp 3b7d855c



"databaseben" wrote:

fixboot and fixmbr will not
affect your personal files.

so you can try to run the above
first then exit and try to boot
w/o the cd.

however, chkdsk reconciles
the files in the file system against
the master file table.

so if the master file table became
corrupted as a result of sp3,
then there are some system files
that need to be audited by the
chkdsk tool.

the question that only you can
answer is if you had pre existing
issues with the functionality of your
system and instead of correcting them
you chose to install sp3 instead which
may have made things worse than
better.

ideally, before installing sp3
some disk and file system maintenance
should have been performed to ensure
a smooth update, like removing the
trash, running a chkdsk and a defrag.

the above plus undertaking precautions
to protect personal data/files would
ensure you a reasonable amount of leaway
to excercise some risk without worrying
about the loss of personal data.

however if sp3 was installed out of convenience
and you had no pre existing issues and
for all practical purposes your system
was functional before sp3, then a chkdsk
should not attibute to any loss of data.

instead the chkdsk will reconcile the
system files that are preventing you
to boot with the master file table.


"Jbarrick" wrote in message
...
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few
"basic" dos commands.

I did not want to approach this full speed ahead only to find out
my data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in
message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot
back up.
Even in
safe mode it restarts just as windows should be loading.

Any ideas?

"Jbarrick" wrote in message
...
When attempting to boot from the CD, I never got the option of repair
console
or a command prompt to try fixboot, fixmbr or chkdsk.

Could I be doing something wrong?

It sounds like your attempts have been unsuccessful. This page should
help:

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

After you enter the BIOS, configure your PC to boot off the CD-ROM drive
first.

is the cd a winxp
cd?

if so, then the label side
will be holographically
inscribed and you will
have a product key for
it as well.

you may be using a
recovery disk provided
by the machines' maker.

so you may have to borrow
a winxp cd.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
When attempting to boot from the CD, I never got the option of repair console
or a command prompt to try fixboot, fixmbr or chkdsk.

Could I be doing something wrong?






"Gerry" wrote:


Jbarrick

Chkdsk can corrupt the data on the disk. It's an inherent risk. If you
have not backed up the data there are two ways you can still do so.

For either way you need a second computer. If the second computer is a
desktop and can take two drives you can remove the drive from first
computer and put it in the second computer as a slave. The computer
boots off the first (or master ) drive and you should be able to read
and copy off the data on the second drive. If the second computer does
not the capability of taking a second hard drive or it is a laptop you
can place the hard drive from the first computer in an external cradle
linked to the second computer. You can then read and copy from the drive
in the external cradle.

The next link illustrates what I mean by an external cradle:
http://www.storagedepot.co.uk/Enclos...c884/p753.aspx

Alternatively any small computer repair shop can back up data for you.


--



Hope this helps.

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


Jbarrick wrote:
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few "basic" dos commands.

I did not want to approach this full speed ahead only to find out my
data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot back
up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

The CD is a Windows XP Professional disk. I am not certain that it is the
one that came with this specific computer.



"db.·.. ))) ·` .. ." wrote:

is the cd a winxp
cd?

if so, then the label side
will be holographically
inscribed and you will
have a product key for
it as well.

you may be using a
recovery disk provided
by the machines' maker.

so you may have to borrow
a winxp cd.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
When attempting to boot from the CD, I never got the option of repair console
or a command prompt to try fixboot, fixmbr or chkdsk.

Could I be doing something wrong?






"Gerry" wrote:


Jbarrick

Chkdsk can corrupt the data on the disk. It's an inherent risk. If you
have not backed up the data there are two ways you can still do so.

For either way you need a second computer. If the second computer is a
desktop and can take two drives you can remove the drive from first
computer and put it in the second computer as a slave. The computer
boots off the first (or master ) drive and you should be able to read
and copy off the data on the second drive. If the second computer does
not the capability of taking a second hard drive or it is a laptop you
can place the hard drive from the first computer in an external cradle
linked to the second computer. You can then read and copy from the drive
in the external cradle.

The next link illustrates what I mean by an external cradle:
http://www.storagedepot.co.uk/Enclos...c884/p753.aspx

Alternatively any small computer repair shop can back up data for you.


--



Hope this helps.

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


Jbarrick wrote:
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few "basic" dos commands.

I did not want to approach this full speed ahead only to find out my
data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·... ¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot back
up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?

ok,

your first step is to
ensure your bios is
set to boot directly
from the cd.

to access the bios you
may have to review your
computer manual.

but generally, when you
first power up the machine
you will see a message
stating to press f2 to enter
the setup.

once the cd is set to be
the device to boot, then
save and exit.

if the win cd is in the
cd drive, then the machine
will boot from it and skip
booting from the harddisk.

after the cd executes and
installs the necessary set
up files a menu will be provided
with the option to install the
o.s. or install the repair console.

--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
The CD is a Windows XP Professional disk. I am not certain that it is the
one that came with this specific computer.



"db.·.. ))) ·` .. ." wrote:

is the cd a winxp
cd?

if so, then the label side
will be holographically
inscribed and you will
have a product key for
it as well.

you may be using a
recovery disk provided
by the machines' maker.

so you may have to borrow
a winxp cd.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message ...
When attempting to boot from the CD, I never got the option of repair console
or a command prompt to try fixboot, fixmbr or chkdsk.

Could I be doing something wrong?






"Gerry" wrote:


Jbarrick

Chkdsk can corrupt the data on the disk. It's an inherent risk. If you
have not backed up the data there are two ways you can still do so.

For either way you need a second computer. If the second computer is a
desktop and can take two drives you can remove the drive from first
computer and put it in the second computer as a slave. The computer
boots off the first (or master ) drive and you should be able to read
and copy off the data on the second drive. If the second computer does
not the capability of taking a second hard drive or it is a laptop you
can place the hard drive from the first computer in an external cradle
linked to the second computer. You can then read and copy from the drive
in the external cradle.

The next link illustrates what I mean by an external cradle:
http://www.storagedepot.co.uk/Enclos...c884/p753.aspx

Alternatively any small computer repair shop can back up data for you.


--



Hope this helps.

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


Jbarrick wrote:
You are correct in that I don't have specific experience with the
repair console. However, I am somewhat familiar with the command
prompt and a few "basic" dos commands.

I did not want to approach this full speed ahead only to find out my
data will get erased.

Among "fixboot", "chkdsk" or "fixmbr" commands, do any of these
present a danger of wipping out my data? Is there one that would
better than the others to try first, or should I run all of these?


"databaseben" wrote:

like all tools, they can be
used as weapons as well
for those who are perversely
experienced with its power.

however, it seems that perhaps
the repair console is something
you are unfamaliar with.

it is really a window that provides
a disk prompt where you can
run commands from it.

i would describe it as being
similar to the old dos command
prompt, but i think you haven't
experienced this as well.

but if you had the opportunity
to do a run and open the cmd
window from the desktop, then
this is similar except that the
repair console is outside of the
windows enviroment.

there is more info at microsoft.com
if you want to research the subject
of the repair console.


"Jbarrick" wrote in message
...
What kind of risk is there in wipping out data by running "repair
console"?




"db.·.. ))) ·` .. ." wrote:

i suggested the commands
to help resolve disk issues
that are keeping you from
booting the o.s. at this time.

the only options you have
utilizing your win cd is to
either use the repair console
or format the disk to reinstall
sp2.

in regards to the integrity of
your data, it all depends on
what measures you had
taken in the past to ensure
or minimize risks.

------------

the other option could be
to install another disk and
install the o.s. to it and then
use it to access your faulty
drive "or"

you could take your faulty
drive and install it as a slave
on a functional computer and
use it to access the faulty drive.

but accessing data and repairing
the disk system and file system
would require to at least run the
commands i provided or repair
the faulty o.s. with a winxp cd.

however you cannot utilize your
winxp sp2 cd to repair the
winxp sp3.
--

db·´¯`·...¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
What is my risk of loosing data on the C: drive?




"db.·.. ))) ·` .. ." wrote:

my suggestion is to
boot with a windows
xp cd, then select the
repair/recovery console.

then you can execute
a couple of commands
at the disk prompt:

chkdsk
fixmbr
fixboot

then exit and
try to boot again
w/o the cd.

--

db·´¯`·... ¸)))º
DatabaseBen, Retired Professional
- Systems Analyst
- Database Developer
- Accountancy
- Veteran of the Armed Forces

"Jbarrick" wrote in message
...
I have a computer that runs XP Pro (SP-3) that fails to boot
every time.

This was shut down properly, however, it now will not boot back
up. Even in
safe mode it restarts just as windows should be loading.

Any ideas?