Talk:Halt and Catch Fire (computing)

The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.

This is the talk page for discussing improvements to the Halt and Catch Fire (computing) article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1: 12 months

The following references may be useful when improving this article in the future:

Anon./Unknown (1967). [Abbreviation appearance, article title unknown], Datamation (magazine), p. 116, 120, New York, NY, USA: Technical Publishing Company. This source mentions HCF, see [1].
Anon./Unknown (1968). [Abbreviation appearance, article title unknown], Modern Data Systems (journal), p. 136, Framingham, MA, USA: Delta Publications. This source mentions HCF, see [2].
Belzer, Boris (1971). The Architecture and Engineering of Digital Computer Complexes, Vol. 1, p. 85, New York, NY, USA: Plenum Publishers, OCLC 209102. This source mentions HCF and other commands, providing a further hidden citation, see [3].
Banks, Walter (2000). "Mailing list entry". Retrieved 2014-06-08.

Z80 halt

I'm not really sure why the Zilog Z80 is mentioned here at all. As on the Intel 8080, what would be otherwise be a MOV M,M instruction is encoded as a HALT; the CPU stops until it gets interrupted. If, however, the program has disabled interrupts, obviously the CPU is going to stay halted -- unless it is sent a non-maskable interrupt, which both the 8080 and the Z80 provide. So in neither case does DI followed by HALT cause anything unusual; certainly not catching fire. --jpgordon^{𝄢𝄆𝄐𝄇} 04:28, 20 March 2022 (UTC)[reply]