Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site ecsvax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!mcnc!ecsvax!hes
From: hes@ecsvax.UUCP (Henry Schaffer)
Newsgroups: net.dcom,net.micro
Subject: Re: Squeezing files. - really on "Binary"
Message-ID: <1495@ecsvax.UUCP>
Date: Thu, 20-Jun-85 12:20:35 EDT
Article-I.D.: ecsvax.1495
Posted: Thu Jun 20 12:20:35 1985
Date-Received: Sun, 23-Jun-85 01:55:14 EDT
References: <789@turtlevax.UUCP>
Organization: NC State Univ.
Lines: 11
Xref: watmath net.dcom:1044 net.micro:10842

In the old days, one could have several forms of a program on punched
cards.  Instead of having source or assembler or whatever punched on
the card in the normal Hollerith code, one could choose the "binary"
format, in which each position on the card represented a 0 or a 1
by being blank or punched.  The program in that form (usually a
direct transcription of how it appears in memory) was then called a
"binary deck" or sometimes just a "binary".
Therefore when I read "binary image", I think of a memory image (i.e.,
dump) in binary format.  I didn't interpret it as an image (picture)
in which each pixel could only take on one of two possible values.
--henry schaffer