Isid Iooo IoooE , duh!

Mitch Bailey · 20 Dec 1999, 00:17 · from urth-v0028.mbox · original

This is the message as the crawl holds it, before anything here touched it. What the conversation shows has been through ingest: transfer encodings decoded, attachments dropped, quote markers repaired, and the archiver’s ? resolved into quotation marks and dashes. Those repairs are judgements and some of them are wrong, which is what this page is for. Email addresses are obscured here as they are everywhere else on the site, so it is before our repairs rather than byte for byte.

From: "Mitch Bailey" <chemmie at MINDSPRING.COM>
Subject: (urth) Isid Iooo IoooE , duh!
Date: Mon, 20 Dec 1999 00:17:09
Message-ID: <urth-v0028-0648 at digest.urth.net>
X-Urthmirror-Source: http://www.urth.net/urth/archives/v0028/0648.shtml
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="----=_NextPart_000_0016_01BF4A7F.8EBB3A00"

This is a multi-part message in MIME format.

------=_NextPart_000_0016_01BF4A7F.8EBB3A00
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

"Then you could read the whole assemblage as two 64-bit hex numbers and =
one 128-bit hex number:
=20
151D, 1000, 1000E
=20
Now, what their significance might be, I still couldn't say, but maybe =
this is a step in the right direction."=20

DUH!

I meant, of course, two 32-bit numbers and a 48-bit number. Where do you =
ever run across 48 bit numbers in computer science?

This of course comes to us from the man who had a character spend his =
entire childhood reading "M*MILLION" as Monsieur Million.

------=_NextPart_000_0016_01BF4A7F.8EBB3A00
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2314.1000" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>"Then you could read the whole =
assemblage as two=20
64-bit hex numbers and one 128-bit hex number:
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>151D, 1000, 1000E</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Now, what their significance might be, =
I still=20
couldn't say, but maybe this is a step in the right direction." =
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV>DUH!</DIV>
<DIV>&nbsp;</DIV>
<DIV>I meant, of course, two 32-bit numbers and a 48-bit number. Where =
do you=20
ever run across 48 bit numbers in computer science?</DIV>
<DIV>&nbsp;</DIV>
<DIV>This of course comes to us from the man who had a character spend =
his=20
entire childhood reading "M*MILLION" as Monsieur=20
Million.</DIV></FONT></DIV></BODY></HTML>

------=_NextPart_000_0016_01BF4A7F.8EBB3A00--

*More Wolfe info & archive of this list at http://www.urth.net/urth/

An unofficial mirror of a public mailing list · about & removal requests · download the archive · before the list · original archive at urth.net