Re: Startup problems


"JAD" <kapasitor@xxxxxxxxxxxxxxxx> wrote in message
news:KenUf.395$WZ4.358@xxxxxxxxxxx

"Bill Wittmer" <wr.wittmer1@xxxxxxxxxxx> wrote in message
news:sDlUf.5505$8G2.1479@xxxxxxxxxxx

"Mike T." <hello@xxxxxxxxxxxxx> wrote in message
news:44215de1$0$16324$892e7fe2@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

"Bill Wittmer" <wr.wittmer1@xxxxxxxxxxx> wrote in message
news:1p4Uf.4540$8G2.3272@xxxxxxxxxxx
I put together a system using an Asus P4P800 VM motherboard, and Intel
3.0
CPU, an Antec 40 watt PSU, a Western Digital Cavier 200 GB SATA hard
drive
and 1024 Mb's of Crucial DDR PC 3200 memory. Windows XP Home was
installed
on the system. The computer was working fine for about 4 months and
then
it began to take about 5 minutes for the computer to boot. I thought
is
was a software issue and did everything from doing a System Restore,
doing
a repair install to doing a total wipe of the hard drive and doing a
fresh
install. Booting would take 5 minutes or more still. I put in another
hard drive, used a new SATA cable, and checked the memory with no luck.
I
found that when using diagnostic software, using a floppy disk and
booting
into DOS, it would still take several minutes before I would get the
prompt command or the diagnostic program would begin to run. So
whether
I
boot into Windows, DOS or use a Linux based diagnostic program, it can
take 5 minutes or more for the program to start. I am looking at a
hardware issue and have no idea as to what else could be causing my
problem. If anyone has any ideas, I would greatly appreciate any help.


OK, your computer must run POST before it boots. This program is run
by
the CPU, with support from the mainboard, and is stored in BIOS.
Although
I haven't seen this before, it is theoretically possible that funky
CMOS
settings (variable settings of BIOS) could affect the POST procedure.
First thing I would try is to remove the CMOS battery (probably a
CR2032
button battery) from the mainboard. Leave it out for about 15 minutes.
While the battery is out, find the "clear CMOS" jumper on the mainboard
and set it into the position to CLEAR CMOS settings. Again, leave this
jumper set to clear for about 15 minutes. Of course the computer
should
be powered off and unplugged while you are doing this. :)

Then after about 15 minutes, reinstall the battery and set the clear
CMOS
jumper to the normal/run position.

I'd be surprised if that doesn't fix the problem.

If the symptom changes, but it's still taking longer than normal to
boot
.
. .

You might as a last resort try updating the BIOS of the mainboard. You
can find instructions for doing that at the Asus web site. Follow them
carefully, or your mainboard is history. -Dave
Thanks for your response, but I am in worst shape than I was before. I
turned off the computer and unplugged it. I removed the CMOS battery and
then I moved the "Clear CMOS Jumper" to the clear position. About an
hour
later I came back to the computer, set the jumper back to the normal
position and replaced the battery. When I started up the computer, it
immediately started running the BIOS setup without my having hit the
"delete" key during startup. Then the following message appeared:
CMOS Settings Wrong
CMOS Date/Time Not Set
Chassis Intruded!
Fatal Error...System Halted

This is as far as I can go. If I can get into the BIOS settings I can
enter
the necessary settings. However, whether I hit the "delete" key or not,
the
BIOS setup automatically begins and then ends with the above error
message
and then it stops, not allowing me to go any further and that includes
going
into the Windows startup. Is there any hope for my situation or should I
just go and get my shotgun and drag the computer outside and use if for
target practice.

Bill




Hey no problem this is normal
go into bios and load safe boot defaults (or performance defaults if you
feel confident) ((option usually at the bottom of the first screen))
Disable onboard (integrated) sound for now

JAD
Thanks for the help, I was finally able to get into the BIOS setup and
was able to load the default setting. The system is now starting up at
normal speed.

Regards,
Bill


.