Windows XP Startup Probs

  • Thread starter Thread starter allen.hoessli
  • Start date Start date
A

allen.hoessli

I recently reinstalled Windows XP. I installed all the basic stuff and
performed basic maintenance. For some reason, every time I log into my
Administrator account (the account I perform all maintenance and
installation), my System32 folder opens up on Windows Explorer. What
is going on?
 
I tried to run that script. It told me that the value wasn't in my
registry and that it couldn't repair the problem. Any other ideas?
 
I recently reinstalled Windows XP. I installed all the basic stuff and
performed basic maintenance. For some reason, every time I log into my
Administrator account (the account I perform all maintenance and
installation), my System32 folder opens up on Windows Explorer. What
is going on?

System Folder Opens When Logging on to Windows XP, Windows 2000, or Windows
NT 4.0
http://support.microsoft.com/kb/170086/en-us
 
I hope this is still an open forum because I may have a similar problem.
My startup takes more than 15, yes, 15 mitutes, most of the time the machine
sits quietly -- the HD not cranking -- with XP start time-bar running on the
screen- before asking for password. AND, IT TAKES THE SAME 15 minutes TO SHUT
DOWN!There are related problems that may help people to help me:
1. the XP does not see my CD ROM Drives any more
2. Everytime I do "search for new hardware" it will hang up for more than 10
minutes
3. I am not able to restore the system to a previous setting
 
I don't remember the details but if you press F8 doing the boot process you
will have the option of creating a log of boot time events. Review this log
to see what is hanging your system.

Microsoft recently released a fix for slow shutdown problems.
 
Thanks. I have found what's hanging there and disconnected it. Now I got a
new problem. A blue screen telling to CHKDSK before restart. How do I do it
without starting XP? I kept hitting the F deys but could not get around the
blue screen.
 
Thanks. I have found what's hanging there and disconnected it. Now I got a
new problem. A blue screen telling to CHKDSK before restart. How do I do
it
without starting XP? I kept hitting the F deys but could not get around
the
blue screen.

<snip>

It's best not to post your new question as a response to someone else's
thread - that's called hijacking. Start a new thread giving relevant
information about the problem. Here is a link for how to make a good
newsgroup post:

Making Good Newsgroup Posts


Some of the things that are unclear in your post are, when did the problem
start? Is it sudden or has it been developing over time? What is the
malware status of the computer? Do you regularly scan for viruses and other
malware in safe mode using a combination of programs? What changes have
occurred just prior to this problem starting?

In your response to WWII you said you "found what's hanging there and
disconnected it". What does that mean? Hardware? Where are you getting
this message about chkdsk? Does it not give the option to run it?

One way to run chkdsk is from the recovery console. Insert the XP
installation CD and reboot the computer. You may have to enter the BIOS to
set the CD as the first boot device. Boot from the CD and take the first
"R" for repair. Enter the number for the Windows installation when
prompted - I assume you only have one so enter 1. Then enter the password
for the built in Administrator account. If this is XP Pro enter whatever
password was assigned for that account when the OS was installed. If it's
XP Home it's normally blank so just hit enter.

At the command prompt type chkdsk /p and press enter. It will take some
time. Caution - chkdsk can result in some data loss. Do you have a full
and complete backup of important data?

Keep you responses in this thread for now, but in the future don't post onto
someone else's thread.
 
My apologies if I violated some unseen rules here.

what's hanging there was an unresponding CD Write Drive. Once it was
removed, the machine started without the 15 min delay.
As to the blue screen claiming that my HD was at risk, here is my solution
to share --sorry I do not know if this is appropriate since I am new here-- i
thought it would be good to let people know how a problem was solved rather
than just walked away:

The issue: the machine asked my to CHKDSK while it would not start at all,
how could I check my HD?

Here's what I did to revive the computer:
1. Went to Best Buy to purchase a hard drive "enclusure" ($50) that enabled
me to read my HD from my laptop via USB port; I found nothing wrong on it. --
I put the HD back on the desktop and it still did not start -- the same blue
screen again.

2. I placed a driver file IOMDISK.SYS that I had removed earlier by mistake
back in the windows\system32 folder

3. Remounted the HD to my desktop and it woke up!!!!

So the bottom line is that we cannot trust Microsoft's message on a blue
screen; and, unfortunately, it is impossible to solve the problem in a
situation like this without the help of a second computer.

-- TXZ
 
My apologies if I violated some unseen rules here.

what's hanging there was an unresponding CD Write Drive. Once it was
removed, the machine started without the 15 min delay.
As to the blue screen claiming that my HD was at risk, here is my solution
to share --sorry I do not know if this is appropriate since I am new
here-- i
thought it would be good to let people know how a problem was solved
rather
than just walked away:

The issue: the machine asked my to CHKDSK while it would not start at all,
how could I check my HD?

Here's what I did to revive the computer:
1. Went to Best Buy to purchase a hard drive "enclusure" ($50) that
enabled
me to read my HD from my laptop via USB port; I found nothing wrong on
it. --
I put the HD back on the desktop and it still did not start -- the same
blue
screen again.

2. I placed a driver file IOMDISK.SYS that I had removed earlier by
mistake
back in the windows\system32 folder

3. Remounted the HD to my desktop and it woke up!!!!

So the bottom line is that we cannot trust Microsoft's message on a blue
screen; and, unfortunately, it is impossible to solve the problem in a
situation like this without the help of a second computer.

-- TXZ

I'm glad it's fixed for you now. You could have done everything you did by
using the recovery console as I indicated in my first response to you.
Chkdsk can be run and files replaced. Not sure why you didn't try that, and
bought an enclosure instead.

It think the real bottom line here is don't be removing files from the
system32 directory unless you know what you are doing and how to restore the
system such as by restoring an image.

It's great you posted back the resolution, so anyone else with a similar
problem can benefit by it.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top