[help] Endless to-and-fro at progress-meter when PC starup

  • Thread starter Thread starter mebanna
  • Start date Start date
M

mebanna

My PC:
CPU: PentiuD820
MOBO: Abit IL8
RAM: Kingtiger/DDRII667/512*2
Graph:Sapphire/RadeonX1300
HDD: Maxtor10/Sata/8M/160G, WestDigital/Pata/80G
OS: Winxp+Sp2 (installed on the first HDD, Maxtor160G)

The problem:
When start pc after a longtime of shut-down, e.g.5 or 6 hours, it just
endlessly repeat (not stop) the circulation of progress-meter, instead
of the normal situation that repeat 5, or 6 time then go into desktop.
It just repeat and repeat, repeat... but not go into the following
desktop. During the endless repeation, the HDD-LED is extinct.

One thing that have to say initially, is one of the two HDD make a few
times sound, like "clock, clock" at the begining of STARTing(not
RESTARTing) the computer as well as don't make sound when RESTART.
(I can't differentiate which HDD make the sound)

As I havn't other hardware parts, I can't check by substituting seriatim.

Any response would be appreciated.
Best regards
mebanna.
 
mebanna said:
My PC:
CPU: PentiuD820
MOBO: Abit IL8
RAM: Kingtiger/DDRII667/512*2
Graph:Sapphire/RadeonX1300
HDD: Maxtor10/Sata/8M/160G, WestDigital/Pata/80G
OS: Winxp+Sp2 (installed on the first HDD, Maxtor160G)

The problem:
When start pc after a longtime of shut-down, e.g.5 or 6 hours, it just
endlessly repeat (not stop) the circulation of progress-meter, instead
of the normal situation that repeat 5, or 6 time then go into desktop.
It just repeat and repeat, repeat... but not go into the following
desktop. During the endless repeation, the HDD-LED is extinct.

One thing that have to say initially, is one of the two HDD make a few
times sound, like "clock, clock" at the begining of STARTing(not
RESTARTing) the computer as well as don't make sound when RESTART.
(I can't differentiate which HDD make the sound)

As I havn't other hardware parts, I can't check by substituting seriatim.
Click to expand...


Well, you can unplug one of the drives. If it still clicks, it's the
one still present in your system. And if the clicking stops, then it's
the one that was unplugged.

Get maxtors hard drive diagnostic tool (powermax) to dagnose both of
your drives. If you don't have a backup, you should make one now,
because one common failure mode of a hard drive is the "click of
death". Which is a hdd that constantly clicks and refuses to work.
 
Edit Boot.ini the root directory. At the end of the lines specifying the operating system add /sos. That could give you a better idea of what the problem is when it occurs.
 
Mike said:
Edit Boot.ini the root directory. At the end of the lines specifying the operating system add /sos. That could give you a better idea of what the problem is when it occurs.
Click to expand...
Thanks a lot for responding.
But..I can't figure out what you talk about, as I know few about boot.ini.
I copy its content here, could you do me a favor of checking it?
Thanks.


boot.ini:
*****************
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /noexecute=optin /fastdetect
*****************
 
Well, you can unplug one of the drives. If it still clicks, it's the
one still present in your system. And if the clicking stops, then it's
the one that was unplugged.

Get maxtors hard drive diagnostic tool (powermax) to dagnose both of
your drives. If you don't have a backup, you should make one now,
because one common failure mode of a hard drive is the "click of
death". Which is a hdd that constantly clicks and refuses to work.
Click to expand...
Yah, unplug one, It's a good ideal !
As the problem occur if only start AFTER a long time of shut-down, I'll
try this way this weekend.

Thanks very much.
 
mebanna said:
Mike said:
Edit Boot.ini the root directory. At the end of the lines specifying the operating system add /sos. That could give you a better idea of what the problem is when it occurs.
Click to expand...
Thanks a lot for responding.
But..I can't figure out what you talk about, as I know few about boot.ini.
I copy its content here, could you do me a favor of checking it?
Thanks.

boot.ini:
*****************
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /sos
*****************
Click to expand...

/sos is added to the last line. There is only one line under [operating systems]. It may line wrap with your news reader but should be one line in your Boot.ini file.
 
Mike said:
Mike said:
Edit Boot.ini the root directory. At the end of the lines specifying the operating system add /sos. That could give you a better idea of what the problem is when it occurs.
Click to expand...
Thanks a lot for responding.
But..I can't figure out what you talk about, as I know few about boot.ini.
I copy its content here, could you do me a favor of checking it?
Thanks.

boot.ini:
*****************
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /sos
*****************
Click to expand...

/sos is added to the last line. There is only one line under [operating systems]. It may line wrap with your news reader but should be one line in your Boot.ini file.
Click to expand...
Yes, the "line wrap" has been selected in notepad.exe what I used to
open the boot.ini and copy content from.
Interesting, I just check the boot.ini again, and found that its content
changed compareing with the content which I put in the last post.

here is the content of new boot.ini(this time, I've undo selecting 'line
wrap' in notepad before I copy them here):
----------------------------------
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP
Professional" /noexecute=optin /fastdetect
----------------------------------

As you have seen, "/sos" disappeared in new boot.ini.
Dose it have something to do with the problem in original post?

Best regards
mebanna
 
Back
Top