XPost: 24hoursupport.helpdesk, alt.usenet.kooks, alt.os.windows-xp   
   From: snuhwolf@netscape.net   
      
   Kadaitcha Man  pinched out a steaming pile   
   of:   
      
   >Gene Abner  Thou mud-soaked hookworm. Thou   
   >hell-hated fat-brained followers. Ye maundered:   
   >   
   >> I would try reinstalling windows.   
   >   
   >BWAHAHAHAHAHA! The Abnertard strikes again.   
   >   
   >> "Kadaitcha Man"  wrote in message   
   >> news:f4eqrg$55g$1@blackhelicopter.databasix.com...   
   >>> Lightning Notes  Thou paunchy false deluding   
   slave.   
   >>> Thou maggot-infested rash bavin wit. Ye panted:   
   >>>> 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.   
   >>>>   
   >>>> I have an old Dell GX-1   
   >>>>   
   >>>> 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!   
   >>>>   
   >>>> I went into the setup, but didn't find any IOAPIC settings.  My   
   >>>> machine is a GX-1.   
   >>>>   
   >>>> Thanks   
   >>>>   
   >>>> Lightning Notes   
   >>>   
   >>> What a fucking load of crapola. Firstly, a BIOS problem has less   
   >>> than fuck all to do with XP, you dumbfuck cunt. Secondly, chassis   
   >>> intrusion detection   
   >>> will take you into a BIOS warning, which also has fuck all to do   
   >>> with XP. If XP is not loading then the problem is not the chassis   
   >>> intrusion   
   >>> warning.   
   >>>   
      
   Theres the answer. The problem is that no-one wants to listen to the K-   
   man :(   
      
   Remove & replace CMOS battery and set BIOS accordingly. Like you said   
   :)   
      
   I also disable CPU "unique identifier" in my kit. IIRC they dis-allow   
   that on mobos built after 2004 though.   
   :(   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)