Slow bootup

[hypergeek7]

I recently rebuilt my PC, using mostly new components, but keeping the
drives. Put quite simply, I didn't feel like going to the trouble of
copying everything over from my old PATA drives to new SATA drives,
especially since system data really, really doesn't like being copied
without a fight.

The good news is that everything is almost working, the bad news is
that there is now a period of half an hour (sometimes ten minutes more
or less) between the XP splash screen and the login box where the
screen goes blank and there is no drive activity.

My own guess is that this stems from the new motherboard. It's an
ASUS P5LD2, which uses ITE 8211 for the two primary IDE connections.
I installed the drivers for it, (and had to do a repair install as a
result) and the drives seem to run fine with two exceptions. The
previously mentioned extremely slow bootup process, and the fact that
the computer locks up any time a CD with any sort of data on it is
inserted. If the CD is present in the drive at the time of startup,
there are no problems. For the record, I can still burn discs if I
have the burning utility (I use Nero 6) open when the disc is
inserted. Whether or not the two problems are connected, I don't
know.

During startup, the event log has this:
Source: iteatapi
Event ID: 9
Description: The device, \Device\Scsi\iteatapi1, did not respond
within the timeout period.

I tried googling that one with absolutely dismal results. Try it for
yourself and see.

And then this:
Event Source: Service Control Manager
Event ID: 7005
Description: The LoadUserProfile call failed with the following
error: The configuration registry database is corrupt.

This one sounds pretty bad to me, but personally, the registry has
always scared me.

Any help would be vastly appreciated.

Thanks in advance,
Hypergeek

 

[Patrick Keenan]

I recently rebuilt my PC, using mostly new components, but keeping the
drives. Put quite simply, I didn't feel like going to the trouble of
copying everything over from my old PATA drives to new SATA drives,
especially since system data really, really doesn't like being copied
without a fight.

Too bad, because SATA drives tend to be faster overall, and you don't really
need to copy system data since it's rebuilt as you reinstall.

And, in your case, key system data would be automatically invalid because
of the new hardware. So you really don't want to be carrying it forward.

The good news is that everything is almost working, the bad news is
that there is now a period of half an hour (sometimes ten minutes more
or less) between the XP splash screen and the login box where the
screen goes blank and there is no drive activity.

My own guess is that this stems from the new motherboard. It's an
ASUS P5LD2, which uses ITE 8211 for the two primary IDE connections.
I installed the drivers for it, (and had to do a repair install as a
result) and the drives seem to run fine with two exceptions. The
previously mentioned extremely slow bootup process, and the fact that
the computer locks up any time a CD with any sort of data on it is
inserted. If the CD is present in the drive at the time of startup,
there are no problems. For the record, I can still burn discs if I
have the burning utility (I use Nero 6) open when the disc is
inserted. Whether or not the two problems are connected, I don't
know.

During startup, the event log has this:
Source: iteatapi
Event ID: 9
Description: The device, \Device\Scsi\iteatapi1, did not respond
within the timeout period.
I tried googling that one with absolutely dismal results. Try it for
yourself and see.

And then this:
Event Source: Service Control Manager
Event ID: 7005
Description: The LoadUserProfile call failed with the following
error: The configuration registry database is corrupt.

This one sounds pretty bad to me, but personally, the registry has
always scared me.

Any help would be vastly appreciated.

Thanks in advance,
Hypergeek

Your system has a new motherboard. Did you install the drivers for it? If
not, XP may be spending time looking for hardware that isn't there anymore,
and registry information for the old hardware will be invalid (or
effectively corrupt).

In your scenario, you would have to do a repair install *and* install the
board drivers from the CD that came with the board, or downloaded from the
manufacturer's website.

Clear the event logs.

And your user profile may be corrupt. If you boot to Safe Mode as
Administrator, make a new account, and boot to that, is it any faster?

HTH
-pk

 

[hypergeek7]

Too bad, because SATA drives tend to be faster overall, and you don't really

need to copy system data since it's rebuilt as you reinstall.

And, in your case, key system data would be automatically invalid because
of the new hardware. So you really don't want to be carrying it forward.

True enough. I'll probably invest in a SATA when I get some money.
The data I didn't want to lose was more along the lines of my user
settings and installed programs in the registry, which would be a pain
to put back, although I suppose I could reassemble my collection piece
by piece as I needed them.

Your system has a new motherboard. Did you install the drivers for it? If
not, XP may be spending time looking for hardware that isn't there anymore,
and registry information for the old hardware will be invalid (or
effectively corrupt).

Yes, after my first boot, when I realized that this was very not
normal behavior I made sure to install the drivers. Didn't seem to
make much of difference.

Clear the event logs.
Done.

And your user profile may be corrupt. If you boot to Safe Mode as
Administrator, make a new account, and boot to that, is it any faster?

As you can probably imagine, rebooting isn't something I look forward
to in this condition. I'll try this tomorrow and let you know how it
goes.

HTH
-pk

Many thanks!

 

[hypergeek7]

As an update, I tried creating a new account via safe mode, but the
result was the same. Also, paying a bit more attention to the event
logs made me realize that both the errors I reported are actually
occuring at the time of login, not during the blank period before
that, so I really have no idea why it just sits there for so long.