home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.sys.sun.misc:3799 alt.folklore.computers:12809
- Path: sparky!uunet!seismo!darwin.sura.net!zaphod.mps.ohio-state.edu!rpi!bu.edu!dartvax!coos.dartmouth.edu!cardo
- From: cardo@coos.dartmouth.edu (Frederick L. Crabbe IV)
- Newsgroups: comp.sys.sun.misc,alt.folklore.computers
- Subject: Re: what is halt_and_catch_fire?
- Message-ID: <1992Aug20.132029.9746@dartvax.dartmouth.edu>
- Date: 20 Aug 92 13:20:29 GMT
- References: <1992Aug14.181623.16695@exlog.com> <1992Aug17.132819.29817@zoo.bt.co.uk> <1992Aug18.193044.24731@dcatlas.dot.gov>
- Sender: news@dartvax.dartmouth.edu (The News Manager)
- Organization: Dartmouth College, Hanover, NH
- Lines: 24
-
- joet@dcatlas.dot.gov (Joe Trott) writes:
-
-
- >Instruction HCF (Halt and Catch Fire) I understood to be part of HOS, that
- >is, Hostile Operating System. If Dennis Boylan reads this, perhaps he
- >would be so kind as to dig up and post and/or mail a copy of the whole
- >thing. This was an item I saw floating around Georgia Tech sometime in the
- >late 70s.
- >-JTT
-
- From the Jargon file:
- HCF: /H-C-F/ n. Mnemonic for `Halt and Catch Fire', any of
- several undocumented and semi-mythical machine instructions with
- destructive side-effects, supposedly included for test purposes on
- several well-known architectures going as far back as the IBM 360.
- The MC6800 microprocessor was the first for which the HCF opcode
- became widely known. This instruction caused the processor to
- {toggle} a subset of the bus lines as rapidly as it could; in
- some configurations this can actually cause lines to burn
- up.
-
- --
- Ric Crabbe
- Consultant/Postmaster/Stand-Up Philosopher/Grad Student(!?)
-