e-Machine stuck in continual loop

Hi ultra_Classic,

Thanks, I will be able to try all these suggestions tomorrow. I really do
appreciate all the good suggestions and help, I hope one of them works too!
I really do not want to wipe out my HDD until I have tried all I can to get
in there and get the docs I am after. That's going to have to be the last
resort....I am a bit stubborn when I am trying to find a solution to a
problem. Also, thanks for the link to the spec sheet. I will certainly post
back to everyone and let you know what happens. This is a great place to
find solutions!

I did have an emergency Norton disk, but I have not been able to find it
since a recent move. I do have a Norton CD which I tried to boot from and it
ran a scan and did not detect anything, but I still could not reach the C
prompt with it. I get an "invalid drive specification" message. I have
checked the BIOS and the HDD is recognised, so I am hoping that is a good
sign. I also went in and displayed the partition information...looked okay
there.

If I could just get to the C prompt I was going to try to find the dir my
docs are in and try to copy them to disk that way. Then just FDISK, reformat
the HDD and reload from the restore cds that came with the pc, and run a
virus scan.

Someone on this discussion also suggested I use another HDD to jump to the
existing HDD by attaching it as a master and setting the existing as a slave.
The other HDD I would be able to get a hold of and use does not have Win XP
OS on it, it has Win ME. Can you tell me if that would that create a
software conflict if I tried that? I do know that the existing drive is NTFS.
As to your virus roll suggestion, sorry not that knowledgable....how would I
do that? Thanks again!
--
nlee788


"ultra_classic" wrote:

"nlee788" wrote:
ultra_Classic,

Sorry I did not answer the question as to recent hardware or software

upgrade. No I have not upgraded at all in the two years I have had
it. I
was actually looking for memory last week. But I have not even
cracked the case open. Thank you.
Greetings nlee788,
Glad you are hanging in there. Just a thought .... you have Norton AV
2005. Good.... did you make an Emergency Boot disk as they suggested
when you installed Norton? Better yet did they give one? I am not
familiar with Norton but can their CD be used as an Emergency Boot
Disk in case of a virus attack?
Open your side cover and check the inside for DUST! Believe it or not
but damp dust can stop you cold. Blow out under, around, and on the
motherboard, also check and clean the fan/heatsink on the CPU. Check
the fan on the power supply and clean it too.

If nothing suggested helps, consider a virus :roll:

Here is a spec sheet and list of memory and upgrade parts for your
machine.
http://www.pcfactoryoutlet.com/defau....201&storeID=4
Use drop down menus on left and select Mfg. and then the Model
Also here is a site that us eMachiners use...register and have a look.
http://s2.invisionfree.com/emachineupgraders/index.php?

You have gotten a lot of solid suggestions on this forum from
everyone. I hope that one works out for you. Post back to this thread
and let us know how you are doing. Your post with a solution may help
someone else.
Best of luck,
ultra_classic

"nlee788" wrote:
Hi ultra_Classic,

Thanks, I will be able to try all these suggestions tomorrow. I
really do
appreciate all the good suggestions and help, I hope one of them
works
too!
I really do not want to wipe out my HDD until I have tried all I can
to get
in there and get the docs I am after. That’s going to have to
be the last
resort....I am a bit stubborn when I am trying to find a solution to
a

problem. Also, thanks for the link to the spec sheet. I will
certainly post
back to everyone and let you know what happens. This is a great
place
to find solutions!

I did have an emergency Norton disk, but I have not been able to find
it
since a recent move. I do have a Norton CD which I tried to boot
from
and it ran a scan and did not detect anything, but I still could not
reach the C prompt with it. I get an "invalid drive specification"

message. I have checked the BIOS and the HDD is recognised, so I am
hoping that is a good sign. I also went in and displayed the
partition information...looked okay
there.

If I could just get to the C prompt I was going to try to find the
dir
my
docs are in and try to copy them to disk that way. Then just FDISK,
reformat
the HDD and reload from the restore cds that came with the pc, and
run
a
virus scan.

Someone on this discussion also suggested I use another HDD to jump
to
the
existing HDD by attaching it as a master and setting the existing as
a
slave.
The other HDD I would be able to get a hold of and use does not have
Win XP
OS on it, it has Win ME. Can you tell me if that would that create a

software conflict if I tried that? I do know that the existing drive
is NTFS.
As to your virus roll suggestion, sorry not that knowledgable....how
would I
do that? Thanks again!
Greetings nlee,
The more you post the more your situation points to a hardware issue.
If you blow all the dust out, clean the fans/heatsink etc. and it’s
still a no go, I would again suggest pulling out the Memory stick and
getting it tested, along with the voltages on the power supply prior
to wiping the drive. At this point you have nothing to lose.
I believe what Jupiter was referring to was taking the HD from the
computer with the problem and going to another working computer
(should have WIN XP) and attaching it as a ’slave’ so it could be
accessed and your files copied. I believe your current drive uses NTFS
(New Technology File System) because of the WIN XP. I’m not sure if
the WIN ME uses the NTFS file system or the FAT32 (File Allocation
Table 32) like WIN98SE. This would create a problem for you. Hopefully
both drives are formatted using the same file system.
Remember that NTFS can read a FAT32 slave drive but not the other way
around.

Please let us know how you make out.
Best of luck,
ultra_classic

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/Help---...ict553560.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1760218

Hello there. I've encountered the same problem. My XP Home Edition with SP2 is also stuck in an endless loop which started on July 6th. I tried booting in Safe Mode and all that but have had no luck. I hooked up an older computer to the internet and searched for a solution, stumbling upon this forum. I followed the advice below, but I'm confused about the MBR issue. I used the Setup Boot Disks (It required six.), and when I got to the screen for the repair I pressed "R". Then it asked for the administrator's password. I left it blank, but that was okay. Then I typed "fixmbr" - that was what I was able to gather from your link below explaining about the MBR. Now the computer is asking me if I want to write a new MBR. I don't know how to do this. I'm afriad I'm going to destroy all chances of recovering my computer if I proceed blindly like this. Please advise me how to proceed. Should I type "Y" or "N"? If I type "Y", what will be the next step? Thanks for your advice. Oh, by the way, the link you listed was for XP Professional. I don't know if that matters, but anyway I couldn't figure out what I should do next.

- Kyle

Originally Posted by Chelsea

Hiya
As you don't have a Windows XP CD you will only have one way of accessing
the recovery console and that is by using boot disks. Microsoft recognise
that computer builders do not always provide an installation CD and so make
available a set of 3.5 inch diskettes that allow you to get into Windows XP.
This is useless if you don't have a floppy drive and a working PC to make
the boot disks with, but I'll assume you do. You can download a utility for
making the boot disks here
http://www.microsoft.com/downloads/r...sp layLang=en
It is very important to choose the right one. So select the utility for
Windows XP Home that corresponds to the service pack you have loaded on your
PC. Once you have created your boot disks-I think there may be five in
all-Boot your PC with Disk 1 in the A: drive. If your Bios is set to boot
first from the hard disk you will have to change the boot order so that the
A: drive boots first. Eventually you will get to a screen that asks if you
want to install Windows XP or do a repair using the recovery console. Select
to repair using the recovery console. The recovery console will load and you
must enter the administrator's password before it will let you do anything.
If you don't know the administrator's password leave that field empty and
hope that it wasn't set by the system builder. Once that is done you need to
reset the MBR. You can find out how to do that here
http://www.microsoft.com/resources/d...d_tro_ldau.asp

and that hopefully will get Windows XP running once more, if not we'll need
to rethink. Best of luck!

Chelsea

"kyle" wrote in message
...

Hello there. I've encountered the same problem. My XP Home Edition
with SP2 is also stuck in an endless loop which started on July 6th. I
tried booting in Safe Mode and all that but have had no luck. I hooked
up an older computer to the internet and searched for a solution,
stumbling upon this forum. I followed the advice below, but I'm
confused about the MBR issue. I used the Setup Boot Disks (It required
six.), and when I got to the screen for the repair I pressed "R". Then
it asked for the administrator's password. I left it blank, but that
was okay. Then I typed "fixmbr" - that was what I was able to gather
from your link below explaining about the MBR. Now the computer is
asking me if I want to write a new MBR. I don't know how to do this.
I'm afriad I'm going to destroy all chances of recovering my computer
if I proceed blindly like this. Please advise me how to proceed.
Should I type "Y" or "N"? If I type "Y", what will be the next step?
Thanks for your advice. Oh, by the way, the link you listed was for XP
Professional. I don't know if that matters, but anyway I couldn't
figure out what I should do next.

- Kyle



Hi Kyle never thought about that statement being misleading ie asking if
I want to write a new MBR. Don't worry you don't write the MBR the operating
system does that for you.

Chelsea

I typed Y to write a new MBR. Suddenly I got a blue screen with a message "A problem has been detected and Windows has been shut down to prevent damage to your computer." Then it listed "Technical Information:
*** STOP: 0x0000008E (0xC0000005, 0x80882211, 0xF93DEEBC, 0x00000000)". I restarted the computer, and it went into the endless loop of trying to boot Windows, failing, and restarting. I restarted with the Boot Disks again and got to the Recovery Console and went through all the steps of fixmbr and hit Y again. This time it said that a new Boot Record was successfully written. I typed "Exit" at the C:\windows\ prompt, and the computer restarted, but unfortunately it went back into the endless loop again. I tried restarting in Safe Mode, but it still won't boot up Windows. If you have any other advice, it would be greatly appreciated. By the way, my computer had up-to-date active anti-virus software running prior to all the trouble.
-Kyle

Originally Posted by Chelsea

"kyle" wrote in message
...

Hello there. I've encountered the same problem. My XP Home Edition
with SP2 is also stuck in an endless loop which started on July 6th. I
tried booting in Safe Mode and all that but have had no luck. I hooked
up an older computer to the internet and searched for a solution,
stumbling upon this forum. I followed the advice below, but I'm
confused about the MBR issue. I used the Setup Boot Disks (It required
six.), and when I got to the screen for the repair I pressed "R". Then
it asked for the administrator's password. I left it blank, but that
was okay. Then I typed "fixmbr" - that was what I was able to gather
from your link below explaining about the MBR. Now the computer is
asking me if I want to write a new MBR. I don't know how to do this.
I'm afriad I'm going to destroy all chances of recovering my computer
if I proceed blindly like this. Please advise me how to proceed.
Should I type "Y" or "N"? If I type "Y", what will be the next step?
Thanks for your advice. Oh, by the way, the link you listed was for XP
Professional. I don't know if that matters, but anyway I couldn't
figure out what I should do next.

- Kyle



Hi Kyle never thought about that statement being misleading ie asking if
I want to write a new MBR. Don't worry you don't write the MBR the operating
system does that for you.

Chelsea

"kyle" wrote in message
...

I typed Y to write a new MBR. Suddenly I got a blue screen with a
message "A problem has been detected and Windows has been shut down to
prevent damage to your computer." Then it listed "Technical
Information:
*** STOP: 0x0000008E (0xC0000005, 0x80882211, 0xF93DEEBC, 0x00000000)".
I restarted the computer, and it went into the endless loop of trying
to boot Windows, failing, and restarting. I restarted with the Boot
Disks again and got to the Recovery Console and went through all the
steps of fixmbr and hit Y again. This time it said that a new Boot
Record was successfully written. I typed "Exit" at the C:\windows\
prompt, and the computer restarted, but unfortunately it went back into
the endless loop again. I tried restarting in Safe Mode, but it still
won't boot up Windows. If you have any other advice, it would be
greatly appreciated. By the way, my computer had up-to-date active
anti-virus software running prior to all the trouble.
-Kyle



Hi Kyle,
Sorry to hear it didn't work. I need you to run a little experiment for me.
If this allows you to get into Windows XP it is not fixed, but we will get a
good indication of what is wrong.

I want you to slightly modify Disk 6 of the recovery console boot disks
On a working PC open notepad and type dcpromo then save the text file as
dcpromo.log onto Disk 6, which will need to be in your diskette drive

On the machine that will not start properly use the recovery disks to enter
the recovery console as before.
In the Recovery Console type the following at the prompt

copy a:\dcpromo.log c:\windows\debug
attrib +R c:\windows\debug\dcpromo.log

There will not be acknowledgement that anything much has happened, but you
should just be returned to the prompt without any error message. Now exit
the recovery console and reboot Windows from the hard disk. Tell me if that
allows you to get into Windows. If it does remember this is not fixed!!!!

Chelsea











You cannot start in Safe Mode is that correct?

I copied the dcpromo.log onto Disk 6 as you advised. I booted up with the disks and got to the Recovery Console. I typed the commands as you advised. Unfortunately, the computer said it couldn't find the file. I double-checked the disk using the other computer. The file dcpromo.log definitely exists. I exited, and as before my computer went into its loop. And it won't boot up Windows in Safe Mode, either. Oh well. . . . Looking forward to your reply.
Kyle

Originally Posted by Chelsea

"kyle" wrote in message
...

I typed Y to write a new MBR. Suddenly I got a blue screen with a
message "A problem has been detected and Windows has been shut down to
prevent damage to your computer." Then it listed "Technical
Information:
*** STOP: 0x0000008E (0xC0000005, 0x80882211, 0xF93DEEBC, 0x00000000)".
I restarted the computer, and it went into the endless loop of trying
to boot Windows, failing, and restarting. I restarted with the Boot
Disks again and got to the Recovery Console and went through all the
steps of fixmbr and hit Y again. This time it said that a new Boot
Record was successfully written. I typed "Exit" at the C:\windows\
prompt, and the computer restarted, but unfortunately it went back into
the endless loop again. I tried restarting in Safe Mode, but it still
won't boot up Windows. If you have any other advice, it would be
greatly appreciated. By the way, my computer had up-to-date active
anti-virus software running prior to all the trouble.
-Kyle



Hi Kyle,
Sorry to hear it didn't work. I need you to run a little experiment for me.
If this allows you to get into Windows XP it is not fixed, but we will get a
good indication of what is wrong.

I want you to slightly modify Disk 6 of the recovery console boot disks
On a working PC open notepad and type dcpromo then save the text file as
dcpromo.log onto Disk 6, which will need to be in your diskette drive

On the machine that will not start properly use the recovery disks to enter
the recovery console as before.
In the Recovery Console type the following at the prompt

copy a:\dcpromo.log c:\windows\debug
attrib +R c:\windows\debug\dcpromo.log

There will not be acknowledgement that anything much has happened, but you
should just be returned to the prompt without any error message. Now exit
the recovery console and reboot Windows from the hard disk. Tell me if that
allows you to get into Windows. If it does remember this is not fixed!!!!

Chelsea











You cannot start in Safe Mode is that correct?

"kyle" wrote in message
...

I copied the dcpromo.log onto Disk 6 as you advised. I booted up with
the disks and got to the Recovery Console. I typed the commands as you
advised. Unfortunately, the computer said it couldn't find the file. I
double-checked the disk using the other computer. The file dcpromo.log
definitely exists. I exited, and as before my computer went into its
loop. And it won't boot up Windows in Safe Mode, either. Oh well. . .
Looking forward to your reply.
Kyle


Hello Kyle,
I am foxed as to why that doesn't work. The dcpromo.log file is normally
installed from within Windows, but as you are unable to get into Windows, I
modified things to use the Recovery Console. If you would be prepared to
persevere with this a little and can face another 10 minutes of tedium with
the recovery console try this. Incidently I just tried this on a laptop
using a USB A drive and can assure you it does work.

In the Recovery Console type the following at the c:\windows prompt

With diskette 6 in the drive type
a:
then type dir-can you see dcpromo.log on the diskette?
Now type
copy dcpromo.log c:\windows\debug

Type c: and return -that takes you back to c:\windows prompt

Finally type
attrib +r c:\windows\debug\dcpromo.log

Type exit

Remove the diskette from the 3.5 inch drive and see what happens when
Windows restarts.

What I am trying to do is plug a vulnerability in the lsass service, which I
think may be crashing everytime you start Windows. This is well known and
causes the infinite loop that you are experiencing. So lets see how it goes.

Chelsea

"kyle" wrote:
I typed Y to write a new MBR. Suddenly I got a blue screen with a
message "A problem has been detected and Windows has been shut down
to
prevent damage to your computer." Then it listed "Technical
Information:
*** STOP: 0x0000008E (0xC0000005, 0x80882211, 0xF93DEEBC,
0x00000000)".
I restarted the computer, and it went into the endless loop of trying
to boot Windows, failing, and restarting. I restarted with the Boot
Disks again and got to the Recovery Console and went through all the
steps of fixmbr and hit Y again. This time it said that a new Boot
Record was successfully written. I typed "Exit" at the
C:\windows\
prompt, and the computer restarted, but unfortunately it went back
into
the endless loop again. I tried restarting in Safe Mode, but it
still
won’t boot up Windows. If you have any other advice, it would
be
greatly appreciated. By the way, my computer had up-to-date active
anti-virus software running prior to all the trouble.
-Kyle

Greetings Kyle,
Boy, this problem seems to be an epidemic lately. Here is MS
explanation of the latest error. I hope it helps somewhat.
:arrow: http://support.microsoft.com/?kbid=315335&sd=RMVP
also
:arrow: http://msdn.microsoft.com/library/de...b81455.xml.asp

Let us know how you are progressing. We are getting ready for a
hurricane here so I’ll be in and out.
Best of luck,
ultra_classic

--
Posted using the http://www.windowsforumz.com interface, at author's request
Articles individually checked for conformance to usenet standards
Topic URL: http://www.windowsforumz.com/Help---...ict553560.html
Visit Topic URL to contact author (reg. req'd). Report abuse: http://www.windowsforumz.com/eform.php?p=1762650

"Greg Ro" wrote in message
...
I had all the problems on my emachine.

I fixed it by getting windows 98se bootdisk with fdisk on it.
www.bootdisk.com

(Note-you may need to change the bios to boot to the floppy first)
Does not matter if you disk is formated as NTFS-Still works.

Let it boot up.

Type fdisk /mbr

Remove floppy. Restart.

Hi Greg thanks for the suggestion but fdisk/mbr is really the same as using
the Recovery Console and the command FixMbr which doesn't work. This is
really a difficult one to repair I'm afraid.

Chelsea

Hello everyone,

Well, I spent the entire weekend trying to get into my hard drive--with no
success. Since I was planning on upgrading my memory anyway, rather than
trying to find a place around here to test the memory stick originally
installed, I bought a new one and installed it. Still the same problem.

I downloaded the installation disks from the MS site and tried to rewrite
the MBR, got a success message. I do not have a full win xp installation
disk so when after installing the setup files, it asked for the win xp
cd....I was out of luck.

I dug around and found an old pc of mine, but it had win me os on it, so
though the system bios recognised the "sick" HDD slaved to the good HDD in
the bios, I could not see it in the Win ME. So I went out and bought the Win
xp home edition upgrade disk and upgraded the HDD from the old pc I had and
slaved the "sick" HDD to the upgraded HDD and installed them both in the
emachine, thinking I could get my files ( I also ran Norton 2005 anti
virus.... it sound nothing).

The emachine boots just fine from the upgraded HDD and I was able to see
the "sick" HDD. BUT I cannot find any files. I went to the prompt and typed
the drive letter to the sick drive and typed DIR. When I type DIR, there are
no windows files, no program files, no doc file names. I ran a search in in
Windows in the sick HDD using file names and it does not find anything. I
think whatever attacked it corrupted everything and wiped out windows. The
funny thing is, this is a 40GB HDD and Windows XP is reading it as a 10 GB.

It doesn't look like I am going to be able to recover my documents...at
least I am more at a loss at this point. I still have not reformatted the
sick drive, so if by some chance someone has any last ditch magic to recover
the data, I am still open to sugggestions.

I do want to thank everyone for the great suggestions and the help. I will
be coming back and posting.
--
nlee788


"Chelsea" wrote:


"kyle" wrote in message
...

I copied the dcpromo.log onto Disk 6 as you advised. I booted up with
the disks and got to the Recovery Console. I typed the commands as you
advised. Unfortunately, the computer said it couldn't find the file. I
double-checked the disk using the other computer. The file dcpromo.log
definitely exists. I exited, and as before my computer went into its
loop. And it won't boot up Windows in Safe Mode, either. Oh well. . .
Looking forward to your reply.
Kyle


Hello Kyle,
I am foxed as to why that doesn't work. The dcpromo.log file is normally
installed from within Windows, but as you are unable to get into Windows, I
modified things to use the Recovery Console. If you would be prepared to
persevere with this a little and can face another 10 minutes of tedium with
the recovery console try this. Incidently I just tried this on a laptop
using a USB A drive and can assure you it does work.

In the Recovery Console type the following at the c:\windows prompt

With diskette 6 in the drive type
a:
then type dir-can you see dcpromo.log on the diskette?
Now type
copy dcpromo.log c:\windows\debug

Type c: and return -that takes you back to c:\windows prompt

Finally type
attrib +r c:\windows\debug\dcpromo.log

Type exit

Remove the diskette from the 3.5 inch drive and see what happens when
Windows restarts.

What I am trying to do is plug a vulnerability in the lsass service, which I
think may be crashing everytime you start Windows. This is well known and
causes the infinite loop that you are experiencing. So lets see how it goes.

Chelsea

Hi Greg Ro,

I have been having similar problems to Kyle's. I went to the
www.bootdisk.com site you posted, and I saw a utility called Active NTFS
Reader. Would this possibly let me read and access the files on the HDD I am
having trouble finding my documents on? I have slaved it to another HDD, but
the files are not accessable or readable. Thnaks.
--
nlee788


"Greg Ro" wrote:

I had all the problems on my emachine.

I fixed it by getting windows 98se bootdisk with fdisk on it.
www.bootdisk.com

(Note-you may need to change the bios to boot to the floppy first)
Does not matter if you disk is formated as NTFS-Still works.

Let it boot up.

Type fdisk /mbr

Remove floppy. Restart.

Greg R

Hi Nlee
Check that the PC Bios is recognising your hard disk correctly? ie as 40GB

Chelsea

"nlee788" wrote in message
...
Hello everyone,

Well, I spent the entire weekend trying to get into my hard drive--with no
success. Since I was planning on upgrading my memory anyway, rather than
trying to find a place around here to test the memory stick originally
installed, I bought a new one and installed it. Still the same problem.

I downloaded the installation disks from the MS site and tried to rewrite
the MBR, got a success message. I do not have a full win xp installation
disk so when after installing the setup files, it asked for the win xp
cd....I was out of luck.

I dug around and found an old pc of mine, but it had win me os on it, so
though the system bios recognised the "sick" HDD slaved to the good HDD in
the bios, I could not see it in the Win ME. So I went out and bought the
Win
xp home edition upgrade disk and upgraded the HDD from the old pc I had
and
slaved the "sick" HDD to the upgraded HDD and installed them both in the
emachine, thinking I could get my files ( I also ran Norton 2005 anti
virus.... it sound nothing).

The emachine boots just fine from the upgraded HDD and I was able to see
the "sick" HDD. BUT I cannot find any files. I went to the prompt and
typed
the drive letter to the sick drive and typed DIR. When I type DIR, there
are
no windows files, no program files, no doc file names. I ran a search in
in
Windows in the sick HDD using file names and it does not find anything. I
think whatever attacked it corrupted everything and wiped out windows.
The
funny thing is, this is a 40GB HDD and Windows XP is reading it as a 10
GB.

It doesn't look like I am going to be able to recover my documents...at
least I am more at a loss at this point. I still have not reformatted the
sick drive, so if by some chance someone has any last ditch magic to
recover
the data, I am still open to sugggestions.

I do want to thank everyone for the great suggestions and the help. I
will
be coming back and posting.
--
nlee788


"Chelsea" wrote:


"kyle" wrote in message
...

I copied the dcpromo.log onto Disk 6 as you advised. I booted up with
the disks and got to the Recovery Console. I typed the commands as you
advised. Unfortunately, the computer said it couldn't find the file.
I
double-checked the disk using the other computer. The file dcpromo.log
definitely exists. I exited, and as before my computer went into its
loop. And it won't boot up Windows in Safe Mode, either. Oh well. . .
Looking forward to your reply.
Kyle


Hello Kyle,
I am foxed as to why that doesn't work. The dcpromo.log file is normally
installed from within Windows, but as you are unable to get into Windows,
I
modified things to use the Recovery Console. If you would be prepared to
persevere with this a little and can face another 10 minutes of tedium
with
the recovery console try this. Incidently I just tried this on a laptop
using a USB A drive and can assure you it does work.

In the Recovery Console type the following at the c:\windows prompt

With diskette 6 in the drive type
a:
then type dir-can you see dcpromo.log on the diskette?
Now type
copy dcpromo.log c:\windows\debug

Type c: and return -that takes you back to c:\windows prompt

Finally type
attrib +r c:\windows\debug\dcpromo.log

Type exit

Remove the diskette from the 3.5 inch drive and see what happens when
Windows restarts.

What I am trying to do is plug a vulnerability in the lsass service,
which I
think may be crashing everytime you start Windows. This is well known and
causes the infinite loop that you are experiencing. So lets see how it
goes.

Chelsea

After typing "dir" at the A: prompt, I see dcpromo.log.txt listed as one of the files. I typed "copy dcpromo.log c:\windows\debug", but once again it said it can't locate the file. I'm wondering if this is because on the drive it's being listed as dcpromo.log.txt. I took the disk and put it in the other computer. I checked the file name, which is dcpromo.log. Then I checked its properties. It's attribute is Archive. And its msdos name is dcpromo.log.txt. Should I change my command line to "copy dcpromo.log.txt c:\windows\debug"? I tried renaming the file with no success.
-Kyle

Originally Posted by Chelsea

"kyle" wrote in message
...

I copied the dcpromo.log onto Disk 6 as you advised. I booted up with
the disks and got to the Recovery Console. I typed the commands as you
advised. Unfortunately, the computer said it couldn't find the file. I
double-checked the disk using the other computer. The file dcpromo.log
definitely exists. I exited, and as before my computer went into its
loop. And it won't boot up Windows in Safe Mode, either. Oh well. . .
Looking forward to your reply.
Kyle


Hello Kyle,
I am foxed as to why that doesn't work. The dcpromo.log file is normally
installed from within Windows, but as you are unable to get into Windows, I
modified things to use the Recovery Console. If you would be prepared to
persevere with this a little and can face another 10 minutes of tedium with
the recovery console try this. Incidently I just tried this on a laptop
using a USB A drive and can assure you it does work.

In the Recovery Console type the following at the c:\windows prompt

With diskette 6 in the drive type
a:
then type dir-can you see dcpromo.log on the diskette?
Now type
copy dcpromo.log c:\windows\debug

Type c: and return -that takes you back to c:\windows prompt

Finally type
attrib +r c:\windows\debug\dcpromo.log

Type exit

Remove the diskette from the 3.5 inch drive and see what happens when
Windows restarts.

What I am trying to do is plug a vulnerability in the lsass service, which I
think may be crashing everytime you start Windows. This is well known and
causes the infinite loop that you are experiencing. So lets see how it goes.

Chelsea

"kyle" wrote in message
...

After typing "dir" at the A: prompt, I see dcpromo.log.txt listed as one
of the files. I typed "copy dcpromo.log c:\windows\debug", but once
again it said it can't locate the file. I'm wondering if this is
because on the drive it's being listed as dcpromo.log.txt. I took the
disk and put it in the other computer. I checked the file name, which
is dcpromo.log. Then I checked its properties. It's attribute is
Archive. And its msdos name is dcpromo.log.txt. Should I change my
command line to "copy dcpromo.log.txt c:\windows\debug"? I tried
renaming the file with no success.
-Kyle


Hi Kyle,
that is really weird Kyle. The msdos name, dcpromo.log.txt, is the reason
why the copy command is not working in the Recovery Console and it would
almost certainly copy if you used

copy dcpromo.log.txt c:\windows\debug

But that is not any good because its the presence of a file with the name
dcpromo.log that blocks the vulnerability in the Lsass process. I will see
if I can find out why this name issue is occuring. Trouble is Kyle this was
intended as a test and Lsass may not be your problem, particularly as you
have SP2 installed. I'm conscious of the time this is taking you so maybe a
different approach is needed here.Consider this
http://www.webtree.ca/windowsxp/repair_xp.htm

and select how to run a repair install from the list. Might be worth a go.
Remember to disconnect your machine from the Internet if you do this and
after the repair-if Windows starts reapply SP2 before reconnecting to the
Internet. Also reapply all hotfixes released after SP2. Good luck Kyle

Chelsea