PLEASE HELP! I'm locked out because of chasis intrusion detection

[Lightning Notes]

Hello Everyone.
I sure hope someone can help me. I purchased an old DELL
Optiplex running XP. When I first got the machine, I went into bios
and disabled the chasis intrusion detection and saved cmos. I was up
and running great. Well it appears the cmos battery went dead and the
bios defaults kicked in and the chasis intrusion was set to detect.
Now, XP will only get to a point and stop.

I remember having this problem a long time ago and having to
use a diskette to reset something. Once done, XP would boot up fine.
I don't remember what was needed, so now I'm stuck.

Since I have been using this machine, I have a lot of stuff on
there I need to get to. If anyone can give me any help in fixing
this, I'd GREATLY appreciate it!

Thanks!

Lightning Notes

 

[Gordon]

Hello Everyone.
I sure hope someone can help me. I purchased an old DELL
Optiplex running XP. When I first got the machine, I went into bios
and disabled the chasis intrusion detection and saved cmos. I was up
and running great. Well it appears the cmos battery went dead and the
bios defaults kicked in and the chasis intrusion was set to detect.
Now, XP will only get to a point and stop.

I remember having this problem a long time ago and having to
use a diskette to reset something. Once done, XP would boot up fine.
I don't remember what was needed, so now I'm stuck.

Since I have been using this machine, I have a lot of stuff on
there I need to get to. If anyone can give me any help in fixing
this, I'd GREATLY appreciate it!

Thanks!

Lightning Notes

Have you actually tried looking on the DELL website? Seems to me this is a
DELL problem, NOT a Windows one.

 

[Lightning Notes]

Actually, I have, but couldn't find anything. AS I stated before, I
remember this happening at one of the places I worked in the past and
the tech had a file that had to be loaded from diskette. Something
with the intrusion detection triggers a file within windows and it has
to be reset. I used to have the program a long time ago, but haven't
needed it, and have since misplace it.

It's possible I'm looking in the wrong places on the dell site, but of
course, they don't provide support for a system this old.

Thanks

 

[Patrick Keenan]

Hello Everyone.
I sure hope someone can help me. I purchased an old DELL
Optiplex running XP. When I first got the machine, I went into bios
and disabled the chasis intrusion detection and saved cmos. I was up
and running great. Well it appears the cmos battery went dead and the
bios defaults kicked in and the chasis intrusion was set to detect.
Now, XP will only get to a point and stop.

I remember having this problem a long time ago and having to
use a diskette to reset something. Once done, XP would boot up fine.
I don't remember what was needed, so now I'm stuck.

Since I have been using this machine, I have a lot of stuff on
there I need to get to. If anyone can give me any help in fixing
this, I'd GREATLY appreciate it!

Thanks!

Lightning Notes

Do a search on the Dell site using the Service Tag on the back of the
machine. Dell keeps a lot of records about older gear. You should be
able to find lots of information on your *specific* system as it was when it
left their plant.

And this might be of help:
http://tomcat.yc.edu/servman/Desktops/GX400_UG/ch2.htm#1056150

That said, chassis detection devices often show their alerts during boot,
not when the OS is loading. So your boot problem may have nothing to do
with chassis detection.

You might consider removing the drive, taking it to another system, and
taking a copy of all your data before anything further goes wrong.

HTH
-pk

 

[Patrick Keenan]

Actually, I have, but couldn't find anything. AS I stated before, I
remember this happening at one of the places I worked in the past and
the tech had a file that had to be loaded from diskette. Something
with the intrusion detection triggers a file within windows and it has
to be reset. I used to have the program a long time ago, but haven't
needed it, and have since misplace it.

It's possible I'm looking in the wrong places on the dell site, but of
course, they don't provide support for a system this old.

You'd be surprised. Use the Service Tag number as the search term.

HTH
-pk

 

[Lightning Notes]

Do a search on the Dell site using the Service Tag on the back of the
machine. Dell keeps a lot of records about older gear. You should be
able to find lots of information on your *specific* system as it was when it
left their plant.

And this might be of help:
http://tomcat.yc.edu/servman/Desktops/GX400_UG/ch2.htm#1056150

That said, chassis detection devices often show their alerts during boot,
not when the OS is loading. So your boot problem may have nothing to do
with chassis detection.

You might consider removing the drive, taking it to another system, and
taking a copy of all your data before anything further goes wrong.

HTH
-pk

Actually yes...the chasis detection alert does show during boot..this
then prevents the system from booting, or is how it worked to my best
memory.

Thanks for the above info. I'll try the link you posted as well.

Just a rundown of how it was explained to me way back when:

Chasis intrusion sets a flag somewhere in the boot sector preventing
OS from booting. OS will continue to try to boot, but will not get
past certain point unless the flag in the boot sector is set back.

Thank you again for your input, and thanks to anyone else that chimes
in.

Lightning Notes.

 

[Tim Jackson]

Hello Everyone.
I sure hope someone can help me. I purchased an old DELL
Optiplex running XP. When I first got the machine, I went into bios
and disabled the chasis intrusion detection and saved cmos. I was up
and running great. Well it appears the cmos battery went dead and the
bios defaults kicked in and the chasis intrusion was set to detect.
Now, XP will only get to a point and stop.

I remember having this problem a long time ago and having to
use a diskette to reset something. Once done, XP would boot up fine.
I don't remember what was needed, so now I'm stuck.

Since I have been using this machine, I have a lot of stuff on
there I need to get to. If anyone can give me any help in fixing
this, I'd GREATLY appreciate it!

Thanks!

Lightning Notes

The DELL PCs I run have never stopped Windows from booting after a chassis
intrusion detection. It only appears to be a warning on the GX150 models we
use.

We have had boot problems after BIOS "resets" due to the IOAPIC setting (in
Integrated Devices menu) changing. We normally run with this set to ENABLED
but found after a BIOS reset it was set to DISABLED. A quick change back to
ENABLED fixed our boot problems.

You can reset the Intrusion Detected warning via the BIOS Security menu.

 

[Lightning Notes]

The DELL PCs I run have never stopped Windows from booting after a chassis
intrusion detection. It only appears to be a warning on the GX150 models we
use.

We have had boot problems after BIOS "resets" due to the IOAPIC setting (in
Integrated Devices menu) changing. We normally run with this set to ENABLED
but found after a BIOS reset it was set to DISABLED. A quick change back to
ENABLED fixed our boot problems.

You can reset the Intrusion Detected warning via the BIOS Security menu.

Thanks to all for the help. I went into the setup, but didn't find
any IOAPIC settings. My machine is a GX-1. I'll have to see if I can
dig up more info, but I did want to thank everyone here for trying.

If anyone else can think of anything (shoot, I'd spit on a spark-plug
if I thought it would help) I'd really appreciate it.

Thanks

Lightning Notes

 

[Guest]

Your best bet is the Dell Forums. There is probably a way to put in a jumper
on the MoBo to bypass the intrusion detect.

http://support.dell.com/support

 

[Mark L. Ferguson]

Well, I just got access to the rest of that thread. If it's a boot sector
entry, you might try a boot to setup CD, choose R for Repair, enter the
Recovery Console, and run the command:

FIXMBR
then maybe
FIXBOOT