|
|||||||
 |
|
|
LinkBack | Thread Tools | Search this Thread |
Rating: 
|
Display Modes |
11-04-2005, 08:38 AM
|
#1 |
|
Member (7 bit)
Join Date: Feb 2003
Location: Tyler, TX.
Posts: 67
|
Message Confirmation
I get this message when I started my computer this morning.
Message confirmation. The system intruded, chassis opened or tempered before. Please check the system. I tried to boot to cdrom, to see if I could do a windows repair, but it always came back to this screen. I took the battery off the motherboard to reset cmos and that didn't help. (System Specs): Asus a7a/266 1 gig sd pc-133 memory(crucial) Albatron fx5700 NEC 2500 Liteon 167T Maxtor 80 gig IDE Any help would sure be appreciated. |
|
|
|
11-04-2005, 08:43 AM
|
#2 |
|
Served with Pride
Staff
Premium Member
Join Date: Apr 2003
Location: near the left coast of Michigan
Posts: 14,654
 |
Sounds like you have the "Chassis intrusion" enabled in the bios and it thinks the case has been opened. Try disabling this function in the bios.
__________________
Getting old is not for sissies! |
|
|
|
|
11-04-2005, 09:39 AM
|
#3 |
|
Member (7 bit)
Join Date: Feb 2003
Location: Tyler, TX.
Posts: 67
|
Where would that be in the bios?
|
|
|
|
|
11-04-2005, 09:40 AM
|
#4 |
|
Professional gadfly
Join Date: Jan 2002
Location: Minneapolis, MN
Posts: 6,364
 |
Perhaps under System Security or the like, just check everything, you'll find it eventually.
|
|
|
|
|
11-04-2005, 10:28 AM
|
#5 |
|
Member (7 bit)
Join Date: Feb 2003
Location: Tyler, TX.
Posts: 67
|
There was a setting in the bios that had halt on all errors, so I changed it to halt on no errors, and it booted up fine. No more problems so far. I sure do appreciate yall's info. Thanks again.
|
|
|
|
|
11-08-2005, 06:11 PM
|
#6 |
|
Member (7 bit)
Join Date: Feb 2003
Location: Tyler, TX.
Posts: 67
|
I did the halt on all errors deal and that let me boot the last time. This time it has come up with this message and it won't let me do anything. I have turned off the virus stuff and I have tried a few others to no avail. I'm stuck and don't know what else to try.
|
|
|
|
|
11-08-2005, 09:00 PM
|
#7 |
|
Member (7 bit)
Join Date: Feb 2003
Location: Tyler, TX.
Posts: 67
|
This may be one of the most stupid things I have ever done. I have been racking my brain for about half a day on this. It winds up being the clock and the date was wrong in cmos is the reason for the message. I guess you take stuff like that for granite and don't look at the obvious. (LOL)!
|
|
|
|
|
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Linear Mode
