Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.theory > #24043 > unrolled thread
| Started by | olcott <NoOne@NoWhere.com> |
|---|---|
| First post | 2020-10-20 11:33 -0500 |
| Last post | 2020-10-29 14:01 +0100 |
| Articles | 20 on this page of 499 — 17 participants |
Back to article view | Back to comp.theory
The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 11:33 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-20 19:11 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 13:40 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 14:19 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 02:57 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-20 22:07 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 16:28 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 16:52 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 11:48 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 20:30 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 15:27 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] André G. Isaak <agisaak@gm.invalid> - 2020-10-21 14:57 -0600
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 16:12 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] André G. Isaak <agisaak@gm.invalid> - 2020-10-21 15:54 -0600
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-21 17:20 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 00:16 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 18:28 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 00:55 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:20 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-21 23:10 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 17:55 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 03:38 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] olcott <NoOne@NoWhere.com> - 2020-10-21 21:54 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 04:38 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-21 23:33 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 11:05 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:44 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 16:14 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 08:00 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:36 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 15:57 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 10:44 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 00:34 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 18:55 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 03:09 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 21:31 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 04:44 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:13 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:03 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:40 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-23 17:18 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 17:28 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:38 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 16:25 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 16:45 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 17:57 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:26 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 21:15 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:36 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:38 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 09:56 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:09 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:27 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:32 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:33 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:58 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:19 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:30 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:34 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-22 20:53 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:24 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 13:28 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:25 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 00:51 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:09 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 02:50 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-22 21:27 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 05:00 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:31 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 17:19 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:22 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 20:36 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:50 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:18 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 10:00 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:04 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 00:12 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 03:47 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:57 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 07:34 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:12 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:20 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:55 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:52 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 09:59 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:20 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 21:02 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 13:29 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 15:56 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 14:12 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 16:58 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:35 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 20:45 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-23 19:54 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:22 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 12:46 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-24 16:43 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:01 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-24 23:14 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:35 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 16:33 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 12:37 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-25 12:10 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:27 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:42 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:11 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 03:18 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 03:21 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:58 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:28 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-23 21:03 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 23:13 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 13:27 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:08 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-24 19:54 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 15:48 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-24 21:41 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:47 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:20 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 13:37 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 11:30 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-26 10:43 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 12:44 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 17:38 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 13:13 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 19:28 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:46 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 15:43 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-26 21:07 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:27 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-27 07:03 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 09:53 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mostowski Collapse <janburse@fastmail.fm> - 2020-10-27 21:07 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:57 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-27 04:53 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 14:30 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 07:52 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 10:28 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 15:30 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 08:45 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 16:05 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 11:05 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 09:53 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 13:36 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 12:05 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 14:44 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-27 16:05 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 03:41 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-28 02:57 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-28 15:54 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] David Kleinecke <dkleinecke@gmail.com> - 2020-10-28 09:25 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-28 18:31 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-29 00:02 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 07:55 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 09:28 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 10:49 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 12:32 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 12:41 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Richard Damon <Richard@Damon-Family.org> - 2020-10-29 16:01 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 15:58 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 06:28 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 10:59 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 09:50 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 12:48 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 11:51 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 14:09 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-29 13:12 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] olcott <NoOne@NoWhere.com> - 2020-10-29 16:08 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-29 22:51 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 18:15 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 01:05 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 20:32 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 02:16 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 21:36 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-29 21:51 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 03:44 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 06:32 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 06:40 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-30 22:08 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 17:21 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 00:46 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 20:07 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 02:30 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 02:44 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 21:56 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:41 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Jeff Barnett <jbb@notatt.com> - 2020-10-31 11:16 -0600
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 23:40 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:28 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 12:56 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 20:49 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 16:07 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 14:55 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:09 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 15:22 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:30 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 16:00 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 18:13 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-11-01 13:56 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Alan Mackenzie <acm@muc.de> - 2020-10-31 22:23 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 17:37 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 19:18 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 18:40 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 20:12 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 21:29 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-10-31 22:34 -0400
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 21:38 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 08:13 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 12:18 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:05 -0600
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-11-01 10:43 -0800
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:56 -0600
Re: The key aspects of x86utm are now finally complete [ x86 machine description language ] olcott <NoOne@NoWhere.com> - 2020-11-01 13:32 -0600
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 17:37 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 17:41 -0600
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Richard Damon <Richard@Damon-Family.org> - 2020-11-01 19:09 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-11-01 12:43 -0600
Re: The key aspects of x86utm are now finally complete [ execution trace described ] olcott <NoOne@NoWhere.com> - 2020-10-31 23:36 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 00:05 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-31 16:40 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 05:36 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 10:32 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 08:54 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 11:30 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:22 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 18:41 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:48 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 18:50 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 16:59 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 19:07 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-30 17:23 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 19:34 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 02:26 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-31 03:05 -0700
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 12:23 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-31 09:22 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-30 14:26 +0000
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] olcott <NoOne@NoWhere.com> - 2020-10-30 10:49 -0500
Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-31 01:26 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-28 08:31 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Jeff Barnett <jbb@notatt.com> - 2020-10-28 10:57 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-28 12:05 -0700
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Richard Damon <Richard@Damon-Family.org> - 2020-10-27 13:09 -0400
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] André G. Isaak <agisaak@gm.invalid> - 2020-10-27 13:57 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-27 11:00 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 16:53 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided olcott <NoOne@NoWhere.com> - 2020-10-27 10:20 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 15:56 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided André G. Isaak <agisaak@gm.invalid> - 2020-10-27 12:53 -0600
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:25 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 18:38 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Alan Mackenzie <acm@muc.de> - 2020-10-25 20:49 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:26 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Andy Walker <anw@cuboid.co.uk> - 2020-10-25 23:57 +0000
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 22:43 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 17:10 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:27 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:34 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:15 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 16:46 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:36 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:05 +0100
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:15 -0500
Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:29 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 23:41 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:02 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Tim Woodall <news001@woodall.me.uk> - 2020-10-23 07:05 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:38 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 11:02 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:45 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 15:56 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:30 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 00:32 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:36 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 21:52 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-23 13:03 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 15:24 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 02:29 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 08:43 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-23 15:51 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:19 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-22 23:14 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 18:05 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 16:55 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:29 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 18:06 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 20:26 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-23 23:51 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:03 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:14 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:10 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 00:17 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:31 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:39 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:54 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 16:58 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:13 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 17:24 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 01:43 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 02:37 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 10:41 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 09:04 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:46 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 00:54 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 22:03 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:35 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:23 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 00:45 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 09:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 07:39 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 10:33 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 12:14 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] olcott <NoOne@NoWhere.com> - 2020-10-25 13:42 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 16:55 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] olcott <NoOne@NoWhere.com> - 2020-10-25 16:07 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation Key Details] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 23:51 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-25 17:26 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 14:16 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 13:55 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 15:56 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-25 17:35 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 14:43 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 16:55 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 14:43 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 08:36 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 12:23 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 22:54 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-25 16:19 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 18:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-25 18:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 01:17 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 02:49 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 03:56 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 02:37 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 12:10 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 06:45 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 17:24 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 10:38 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-27 00:51 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 11:16 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 15:41 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-26 17:28 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:52 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 01:21 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 01:06 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 19:39 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 04:27 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 22:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 23:02 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 16:58 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:38 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 01:17 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:06 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 00:38 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 18:46 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 01:03 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-24 08:04 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:25 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 15:38 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 10:36 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 17:37 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 12:49 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 19:32 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 11:40 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 13:42 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 20:00 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:05 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 20:44 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 15:41 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 21:57 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:05 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-24 22:44 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:01 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 16:11 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:12 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 19:38 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 14:53 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 13:50 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:01 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-26 14:08 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-26 14:26 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-26 20:59 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 20:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-27 02:19 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 16:31 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:08 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 15:16 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 18:30 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 15:47 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 18:08 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 17:45 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-26 16:29 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 13:03 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction olcott <NoOne@NoWhere.com> - 2020-10-26 13:14 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 00:06 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-26 17:16 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] correction Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 00:46 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 20:11 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mike Terry <news.dead.person.stones@darjeeling.plus.com> - 2020-10-27 02:48 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-26 22:38 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 13:36 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 14:13 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 16:55 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-24 14:06 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:31 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 18:17 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 18:00 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 19:48 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 19:29 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 16:24 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:52 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2020-10-22 10:45 -0700
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-21 22:42 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Richard Damon <Richard@Damon-Family.org> - 2020-10-21 21:22 -0400
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-21 21:14 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] Richard Damon <Richard@Damon-Family.org> - 2020-10-22 08:12 -0400
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-22 09:41 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 13:43 -0600
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] olcott <NoOne@NoWhere.com> - 2020-10-22 14:54 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 15:13 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 14:34 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:28 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-22 15:34 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 16:47 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ refutation of HP proofs ] Andy Walker <anw@cuboid.co.uk> - 2020-10-22 16:20 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Richard Damon <Richard@Damon-Family.org> - 2020-10-21 09:09 -0400
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-21 14:36 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:19 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:21 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:27 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:30 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 12:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:43 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:08 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:12 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 11:17 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:21 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 11:30 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:35 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Jeff Barnett <jbb@notatt.com> - 2020-10-22 11:59 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 10:45 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:13 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:17 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 13:24 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-22 17:44 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 19:49 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> - 2020-10-22 17:59 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-22 18:13 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 20:15 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 00:10 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-22 23:28 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:22 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 21:51 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-24 13:07 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:40 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Ben Bacarisse <ben.usenet@bsb.me.uk> - 2020-10-25 02:07 +0000
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 06:29 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 09:10 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 08:30 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 09:52 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 09:04 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 10:49 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 10:06 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:48 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 11:04 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:31 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 12:00 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:12 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 12:35 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 14:04 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] André G. Isaak <agisaak@gm.invalid> - 2020-10-23 15:34 -0600
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 17:05 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-23 22:32 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 21:55 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Richard Damon <Richard@Damon-Family.org> - 2020-10-24 09:50 -0400
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-24 11:14 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Malcolm McLean <malcolm.arthur.mclean@gmail.com> - 2020-10-23 11:15 -0700
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:49 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 17:37 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 11:43 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 17:49 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:06 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:10 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:24 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:35 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 12:46 -0500
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-23 18:53 +0100
Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] olcott <NoOne@NoWhere.com> - 2020-10-23 13:06 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 17:54 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] olcott <NoOne@NoWhere.com> - 2020-10-22 11:57 -0500
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 18:05 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2020-10-22 12:55 -0600
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> - 2020-10-22 19:59 +0100
Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ] Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2020-10-22 19:13 +0000
Stop crossposting you imbecil spammer (Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ]) Mostowski Collapse <janburse@fastmail.fm> - 2020-10-29 14:01 +0100
Page 13 of 25 — ← Prev page 1 … 11 12 [13] 14 15 … 25 Next page →
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-31 01:26 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ defining a non-halting decider ! ] |
| Message-ID | <874kmbxk20.fsf@bsb.me.uk> |
| In reply to | #24679 |
olcott <NoOne@NoWhere.com> writes: > On 10/30/2020 9:26 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> On 10/29/2020 9:16 PM, Ben Bacarisse wrote: >>>>>> olcott <NoOne@NoWhere.com> writes: >> <cut> >>>>>>> The non-halting decider that I defined accepts any and all non-halting >>>>>>> inputs and rejects any and all halting inputs. >> <cut> >>>> Where is the program you claim you can write? The "proving you are >>>> right" is not working out. You should try the "writing the code you >>>> said you could" plan instead. >>>> >>>> Of course I'm fine with you endlessly saying "this is how it will work" >>>> and "this show I could do it" because, as you can imagine, I would >>>> prefer you /not/ to write the code I'm saying can't be written! >>>> >>>> But so far, it's going well for me. How's it going for you? >>> >>> If you are not a learned-by-rote dogmatist you can understand... >> >> Why do you care what I understand? You have a clear and simple claim. >> You have all the "infrastructure" ready (it's a terrible choice, but its >> too late to change that now) and you've said you "just need to write the >> decider". Why are you wasting your time? > > Now the claim has been divided into two different claims. > (a) The claim since 2018-12-13 is that I will have a computer program > that shows exactly how the Linz H_Hat equivalent is correctly > decided. I have already described the details of the basis of this > 2018-12-13 solution. You could tell from the details of the execution > trace that I provided that it does correctly decide the Linz H_Hat. So that one is done and dusted. If the mood takes you, you can simply post the two actual Turing machines you has in Dec 2018. > (b) My new claim is that I have defined a non-halting decider that > accepts any and all non-halting inputs and rejects any and all halting > inputs. Yes, and I see from other posts that you don't want to get on with writing this decider. You want to argue with people rather write the program. That's concerning. >> Write it, post it, and be famous. >> >> Or, as I said, keep posting boasts about what it would work were you to >> ever get round to writing it. That works for me too, (and I suspect >> it's what you want as well). > > I already proved my point two different ways. So why keep on posting about it rather than writing the program that will make you famous? > You made sure to erase this proof without looking at it. You are strangely obsessed with me. Why do you care what I think? Do you think I am in charge of World Computer Science and no one will look at your fully written halt decider until I accept it first? Forget about me and write the program that everyone but you says is impossible. > In the mean time I have to get rid of the bug in the local process > context stacks before I can proceed to the last step of writing a > partial halting decider that correctly decides halting of the Linz > H_Hat() equivalnet. What? Seriously? You had this done and dusted two years ago and yet you will take time out from writing the most significant program ever announced to the world? OK, so we all know what's really going on, but can you at least see how these posts make you look? -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2020-10-28 08:31 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87o8kmtlip.fsf@nosuchdomain.example.com> |
| In reply to | #24534 |
olcott <NoOne@NoWhere.com> writes:
[63 lines deleted]
I've configured my newsreader to ignore all articles that olcott
posts to comp.lang.c. Since I read comp.lang.c before comp.theory,
the result is that I don't see his articles in comp.theory either,
since apparently he cross-posts *everything*.
It's made comp.lang.c and comp.lang.c++ more pleasant without any
loss of relevant information. I suggest that others consider doing
something similar. Those who read comp.theory but not comp.lang.*
might consider filtering out cross-posts. olcott is deliberately
polluting comp.lang.c, comp.lang.c++, and comp.lang.prolog with
his off-topic cross-posts. Perhaps if he realizes that it costs
him attention, he'll change his behavior.
Meanwhile, I again encourage people posting followups to restrict
the set of newsgroups, inconvenient as it is. The denizens of the
comp.lang.* newsgroups will thank you.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Jeff Barnett <jbb@notatt.com> |
|---|---|
| Date | 2020-10-28 10:57 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rnc7tq$lmf$1@dont-email.me> |
| In reply to | #24573 |
On 10/28/2020 9:31 AM, Keith Thompson wrote: > olcott <NoOne@NoWhere.com> writes: > [63 lines deleted] > > I've configured my newsreader to ignore all articles that olcott > posts to comp.lang.c. Since I read comp.lang.c before comp.theory, > the result is that I don't see his articles in comp.theory either, > since apparently he cross-posts *everything*. > > It's made comp.lang.c and comp.lang.c++ more pleasant without any > loss of relevant information. I suggest that others consider doing > something similar. Those who read comp.theory but not comp.lang.* > might consider filtering out cross-posts. olcott is deliberately > polluting comp.lang.c, comp.lang.c++, and comp.lang.prolog with > his off-topic cross-posts. Perhaps if he realizes that it costs > him attention, he'll change his behavior. Since his entire goal is to be noticed and saved from noticing the miserable conditions of his everyday life, it's unrealistic to assume that he'll quit cross-posting. The more attention and the more uproar, the better. I believe his psychology demands that he continue as he is now. If filters worked in real life as well as they do in newsgroups, PO would have disappeared in a puff of smoke years ago. > Meanwhile, I again encourage people posting followups to restrict > the set of newsgroups, inconvenient as it is. The denizens of the > comp.lang.* newsgroups will thank you. -- Jeff Barnett
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2020-10-28 12:05 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87k0vatbl6.fsf@nosuchdomain.example.com> |
| In reply to | #24576 |
Jeff Barnett <jbb@notatt.com> writes:
> On 10/28/2020 9:31 AM, Keith Thompson wrote:
>> olcott <NoOne@NoWhere.com> writes:
>> [63 lines deleted]
>>
>> I've configured my newsreader to ignore all articles that olcott
>> posts to comp.lang.c. Since I read comp.lang.c before comp.theory,
>> the result is that I don't see his articles in comp.theory either,
>> since apparently he cross-posts *everything*.
>>
>> It's made comp.lang.c and comp.lang.c++ more pleasant without any
>> loss of relevant information. I suggest that others consider doing
>> something similar. Those who read comp.theory but not comp.lang.*
>> might consider filtering out cross-posts. olcott is deliberately
>> polluting comp.lang.c, comp.lang.c++, and comp.lang.prolog with
>> his off-topic cross-posts. Perhaps if he realizes that it costs
>> him attention, he'll change his behavior.
>
> Since his entire goal is to be noticed and saved from noticing the
> miserable conditions of his everyday life, it's unrealistic to assume
> that he'll quit cross-posting. The more attention and the more uproar,
> the better. I believe his psychology demands that he continue as he is
> now. If filters worked in real life as well as they do in newsgroups,
> PO would have disappeared in a puff of smoke years ago.
>
>> Meanwhile, I again encourage people posting followups to restrict
>> the set of newsgroups, inconvenient as it is. The denizens of the
>> comp.lang.* newsgroups will thank you.
I understand that encouraging *everyone* in a group to do something
is often futile, but I always hope for exceptions. My (quite
possibly unrealistic) hope is that he'll be convinced that continued
cross-posting will *cost* him attention.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-27 13:09 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <0vYlH.113123$tL.68271@fx15.iad> |
| In reply to | #24528 |
On 10/27/20 12:05 PM, olcott wrote: > > The Linz proof** claims to have proved the the halting problem is > undecidable. It has not actually proved this. All of these proofs merely > show one architectural design of a halt decider that gets the wrong > answer some of the time. My architectural design of a halt decider > cannot be shown to get the wrong answer any of the time. > > ** And all of the conventional self-referential halting problem proofs. > Linz's proof makes NO assumptions on the architectural design of H, other than that it is able to successfully act as a universal halt decider. The requirements on H to be a Turing Halt Decider: * H is a Turning Machine * H accepts as input, a suitable description of another Turing machine, and its input * H then, in finite time, ends up in one of two states to correctly indicate if the provided machine with the provided input would have eventually halted or continued to never halt, but reaching one of two terminal state appropriated indicated. It should be noted that the way that the Halt Decider is built is carefully chosen to be useful, as important applications of it are to embedded it into a larger Turing Machine that will will be generating inputs for another Turing machine, which it wants to know if that machine will be able to eventually halt with an answer, and knowing that is a useful piece of information. Your halt decider/abort detector DOES get the answer to Linz's H_Hat wrong, as with your description of the answer you get for H_Hat(H_Hat), by running H(H_Hat, H_Hat), H says that H_Hat was aborted, or would run forever, when with that answer H_Hat(H_Hat) clearly halts in finite time. You seem to want to try to say that was correct, trying to 'blame' H_Hat for the inability of H, though its internal decider function, to get to an answer. Remember. by its definition, H MUST terminate in finite time, so any need to 'abort' because we hit a max recursion depth or other resource limitation or taking too long to compute is just an admission that it doesn't have the capability to answer the question. Note, that this is NOT like the statement, "This Statement is False" (which has no Truth value because it is self-contradictory) because the halting state of H_Hat has a definite value, for any give H that meets the requirements, H_Hat(H_Hat) WILL definitely either Halt or never Halt, so the question has a truth value. The problem is just that by construction H(H_Hat, H_Hat) will always return the wrong answer, and thus can be shown to not meet its requirements.
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-27 13:57 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn9u33$ghu$1@dont-email.me> |
| In reply to | #24528 |
On 2020-10-27 10:05, olcott wrote: > On 10/27/2020 10:45 AM, Malcolm McLean wrote: >> On Tuesday, 27 October 2020 at 15:30:51 UTC, Mike Terry wrote: >>> >>>> Here's the code >>> Is this code from PO, or is it your code? >>> >>> It is hard enough work dealing with PO, and I don't want to spend much >>> time on /your/ arguments, even if you believe you are making the same >>> argument as PO. If you feel that you have some insight into PO's >>> thinking, by all means respond to my posts saying what you think, but I >>> will probably not seriously engage with you. (I will read what you say >>> at least, and might respond sometimes.) >>> >> It's my code. But based on what PO posted. The key difference is that PO >> hasn't realised that you can stub the detector / abort function, because >> it is a function and it only has to deal with an input set with one >> member. >> >> To be fair, this isn't obvious because the input set makes reference to >> the function itself. You yourself seem to have made this error. You >> forgot >> the word "if". It will cause an infinite recursion IF we don't take >> action. >> But we do take action. >> >> To make this a bit more obvious, replace >> if (M == H_Hatsrc && N == Hatsrc) >> with >> if (strstr(M, "AbortedBecauseNonHaltingBehaviourDetected")) >> >> That has the same effect, but now it's clearer that we're detecting >> what would be an infinite recursion, and taking action against it. >> >> I'm trying to get an insight into why PO is convinced that he has refuted >> the Linz proof. I might be wrong - I'm not him, I can't read his mind, >> and >> he's not been entirely consistent. But I think I've identified it. >> > > The Linz proof** claims to have proved the the halting problem is > undecidable. It has not actually proved this. All of these proofs merely > show one architectural design of a halt decider that gets the wrong > answer some of the time. My architectural design of a halt decider > cannot be shown to get the wrong answer any of the time. Linz doesn't specify anything at all about the 'architectural design' of H. All he does is claim that H is a halt decider; it's internal workings are left entirely unspecified. He shows that for *any* given H it is possible to derive a second TM, H_Hat, such that if the description of H_Hat is used as the input to H, H will not be able to correctly decide whether H_Hat halts. There's absolutely *no* assumptions made about the internal workings / 'architectural design' of H. André -- To email remove 'invalid' & replace 'gm' with well known Google mail service.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-27 11:00 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <H82dnWfLGtWe2QXCnZ2dnUU7-b_NnZ2d@giganews.com> |
| In reply to | #24517 |
On 10/27/2020 9:30 AM, Mike Terry wrote: > On 27/10/2020 10:53, André G. Isaak wrote: >> On 2020-10-26 15:57, olcott wrote: >> >>> If you were paying very close enough attention rather than merely >>> glancing at a few words here and there under the presumption that I >>> must be incorrect you would notice that none of the examples ever >>> showed a single case where: >>> >>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 M, u32 N) >>> ever returned an incorrect value for its input. >> >> Can we get you to commit the following more precise set of claims? >> >> (1) In every instance where its input would not halt when run >> independently, you ABNHBD function will always return 'non halting >> behavior detected - aborted' >> >> (2) In every instance where its input would halt when run independently, >> your ABNHBD will return 'terminated normally' >> >> (3) Your ABNHBD function is actually guaranteed to return one of the >> above two values for every input. >> >> André >> > > This is what I've been trying to get PO to clarify in my last few posts. > He steadfastly declines to provide an actual specification for what > his ABNHDB() function, or even to clarify anything about what it does, This is about ten times now that I have provided a complete description of the full execution trace of how (H_Hat, H_Hat) is decided: (Your claim that I have never answered this question now seems dishonest). bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) decides its input correctly. It creates another process context and executes H-Hat(H_Hat) in this process context in DebugStep() mode. This instance of H_Hat() executes another instance of bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) in its own process context. This instance of bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) creates another process context and executes yet another H-Hat(H_Hat) in this third process context in DebugStep() mode. // 2018-12-13 @7:00 PM solution As soon as H_Hat's second invocation executes bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) a second time from the same machine address and there is no conditional code in the execution trace of H_Hat that would terminate this otherwise infinite recursion then the first instance of bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) stops executing H_Hat() in DebugStep() mode and reports true. This same process can be implemented as UTMs executing subordinate UTMs one state transition at a time where each subordinate UTM has its own portion of the master UTM tape. > saying that he's given a "trace" that shows it making the right decision > (whatever that means!). (He refuses to say define what the "right > decision" is, when it's called with an input pair (Pgm, Data).) That is such a foolish thing to say. You are being as dishonest as Ben. bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) if the above function did detect non halting behavior then Non_Halting_Behavior_Detected is true. if the above function did abort the execution of its input then Aborted_ is true. If the above function detected non halting behavior and aborted the execution of its input because it detected non halting behavior then Aborted_Because_Non_Halting_Behavior_Detected is true. > The most I've ever seen him say is that ABNHDB() steps through its input > program's execution until either it halts, or it "detects non-halting > behaviour", but he WON'T clarify "non-halting behaviour", even to the Yet another dishonesty. The above detailed description of the execution trace of (H_Hat, H_Hat) is terminated as soon as bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) is invoked from the same machine address of H_Hat without any conditional branch instruction in H_Hat that would terminate this otherwise infinite recursion. This is my 2018-12-13 @ 7:00 PM solution. > point of saying whether a halting calculation P(I) can exhibit > non-halting behaviour! I think that's what you're trying to pin him > down on. (It's my focus anyway.) > > The problem with your questions as worded is that he can/will reply "my > decider isn't all-knowing, and it may not work with /every/ input". > Fine, we know it only has to work with his H_Hat(H_Hat) calculation. All > my attempts to get him to talk about that specific case come to nothing. Intuitively, a decider should be a Turing machine that given an input, halts and either accepts or rejects, relaying its answer in one of many equivalent ways, such as halting at an ACCEPT or REJECT state, or leaving its answer on the output tape.Yuval Filmus https://cs.stackexchange.com/questions/84433/what-is-decider Yuval Filmus top 0.04% overall Assistant Professor in the Department of Computer Science at the Technion. The architectural design that I provide is of a halt decider that divides all of its input into: (a) ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED (b) HAS_ALREADY_HALTED The actual fully operational software that I will provide will be a partial ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED decider. > Anyway, I suggest that your wording above will need to have filters > added so that it only talks about the one case his H actually has to > deal with. Also to avoid the "my code is not all-knowing" response, > perhaps (1) should say something like "ABNHDB() returns ABORTED for > input pair (H_Hat, H_Hat) only if it is the case that calculation > H_Hat(H_Hat) is non-halting" ... Hope you have more success than me! > > Mike. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-27 16:53 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <qJCdnSFnces9zQXCnZ2dnUU78V_NnZ2d@brightview.co.uk> |
| In reply to | #24526 |
On 27/10/2020 16:00, olcott wrote: > On 10/27/2020 9:30 AM, Mike Terry wrote: >> On 27/10/2020 10:53, André G. Isaak wrote: >>> On 2020-10-26 15:57, olcott wrote: >>> >>>> If you were paying very close enough attention rather than merely >>>> glancing at a few words here and there under the presumption that I >>>> must be incorrect you would notice that none of the examples ever >>>> showed a single case where: >>>> >>>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 M, u32 N) >>>> ever returned an incorrect value for its input. >>> >>> Can we get you to commit the following more precise set of claims? >>> >>> (1) In every instance where its input would not halt when run >>> independently, you ABNHBD function will always return 'non halting >>> behavior detected - aborted' >>> >>> (2) In every instance where its input would halt when run independently, >>> your ABNHBD will return 'terminated normally' >>> >>> (3) Your ABNHBD function is actually guaranteed to return one of the >>> above two values for every input. >>> >>> André >>> >> >> This is what I've been trying to get PO to clarify in my last few >> posts. He steadfastly declines to provide an actual specification >> for what his ABNHDB() function, or even to clarify anything about what >> it does, > > This is about ten times now that I have provided a complete description > of the full execution trace of how (H_Hat, H_Hat) is decided: > (Your claim that I have never answered this question now seems dishonest). I claimed you have never given any specification of exactly what ABNHDB() function is required to do, in terms of its actual input. A trace, or a description of what it actually does, is not such a specification (because if you say "...and then it returns ABORTED" we do not know /why/ it did that, and whether that is the correct decision according to its specification. So we are unable to provide your "challeng" input function which ABNHDB() cannot "correctly decide". > > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > decides its input correctly. > > It creates another process context and executes H-Hat(H_Hat) in this > process context in DebugStep() mode. > > This instance of H_Hat() executes another instance of > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > in its own process context. > > This instance of bool > Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) creates > another process context and executes yet another H-Hat(H_Hat) in this > third process context in DebugStep() mode. > > // 2018-12-13 @7:00 PM solution > As soon as H_Hat's second invocation executes > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > a second time from the same machine address and there is no conditional > code in the execution trace of H_Hat that would terminate this otherwise > infinite recursion then the first instance of > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > stops executing H_Hat() in DebugStep() mode and reports true. AHA! This is the first time I've seen "..and there is no conditional code in the execution trace of H_Hat that would terminate this otherwise infinite recursion". We're homing in on the problem! The problem is that in the example you're describing, THERE IS conditional code that would terminate this otherwise infinite recursion. So if this "no conditional code that breaks the infinite recursion" is part of the spec for ABNHBD(), then your own example is breaking this spec if it returns ABORTED. Of course, in this case ABNHBD() /did/ abort the emulation of the H_Hat(H_Hat) calculation, but that's exactly why we need the spec to define what a correct return code is, in terms of the functions input. If the spec says just that the ABORT should be returned precisely when an emulation is aborted, and nothing else [like under what conditions such an abort can be taken] then ABNHBD() is free to just abort EVERY emulation straight away and return the "correct" ABORT rc. Nobody can find an input for which it makes an incorrect decision in that case. (Duh! :) ) Mike. > > This same process can be implemented as UTMs executing subordinate UTMs > one state transition at a time where each subordinate UTM has its own > portion of the master UTM tape. > >> saying that he's given a "trace" that shows it making the right >> decision (whatever that means!). (He refuses to say define what the >> "right decision" is, when it's called with an input pair (Pgm, Data).) > > That is such a foolish thing to say. You are being as dishonest as Ben. > > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > > if the above function did detect non halting behavior then > Non_Halting_Behavior_Detected is true. > > if the above function did abort the execution of its input then Aborted_ > is true. > > If the above function detected non halting behavior and aborted the > execution of its input because it detected non halting behavior then > Aborted_Because_Non_Halting_Behavior_Detected is true. > >> The most I've ever seen him say is that ABNHDB() steps through its >> input program's execution until either it halts, or it "detects >> non-halting behaviour", but he WON'T clarify "non-halting behaviour", >> even to the > > Yet another dishonesty. The above detailed description of the execution > trace of (H_Hat, H_Hat) is terminated as soon as > bool Aborted_Because_Non_Halting_Behavior_Detected(H-Hat, H_Hat) > is invoked from the same machine address of H_Hat without any > conditional branch instruction in H_Hat that would terminate this > otherwise infinite recursion. This is my 2018-12-13 @ 7:00 PM solution. > >> point of saying whether a halting calculation P(I) can exhibit >> non-halting behaviour! I think that's what you're trying to pin him >> down on. (It's my focus anyway.) >> >> The problem with your questions as worded is that he can/will reply >> "my decider isn't all-knowing, and it may not work with /every/ >> input". Fine, we know it only has to work with his H_Hat(H_Hat) >> calculation. All my attempts to get him to talk about that specific >> case come to nothing. > > Intuitively, a decider should be a Turing machine that given an input, > halts and either accepts or rejects, relaying its answer in one of many > equivalent ways, such as halting at an ACCEPT or REJECT state, or > leaving its answer on the output tape.Yuval Filmus > https://cs.stackexchange.com/questions/84433/what-is-decider > > Yuval Filmus top 0.04% overall Assistant Professor in the Department of > Computer Science at the Technion. > > The architectural design that I provide is of a halt decider that > divides all of its input into: > (a) ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED > (b) HAS_ALREADY_HALTED > > The actual fully operational software that I will provide will be a > partial ABORTED_BECAUSE_NON_HALTING_BEHAVIOR_DETECTED decider. > >> Anyway, I suggest that your wording above will need to have filters >> added so that it only talks about the one case his H actually has to >> deal with. Also to avoid the "my code is not all-knowing" response, >> perhaps (1) should say something like "ABNHDB() returns ABORTED for >> input pair (H_Hat, H_Hat) only if it is the case that calculation >> H_Hat(H_Hat) is non-halting" ... Hope you have more success than me! >> >> Mike. >> > >
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-27 10:20 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided |
| Message-ID | <GrGdnenXStlEpwXCnZ2dnUU7-UvNnZ2d@giganews.com> |
| In reply to | #24516 |
On 10/27/2020 5:53 AM, André G. Isaak wrote: > On 2020-10-26 15:57, olcott wrote: > >> If you were paying very close enough attention rather than merely >> glancing at a few words here and there under the presumption that I >> must be incorrect you would notice that none of the examples ever >> showed a single case where: >> >> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 M, u32 N) >> ever returned an incorrect value for its input. > > Can we get you to commit the following more precise set of claims? > > (1) In every instance where its input would not halt when run > independently, you ABNHBD function will always return 'non halting > behavior detected - aborted' Here is what I can commit to: There is no input to this function that can be shown to be undecidable: bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) > (2) In every instance where its input would halt when run independently, > your ABNHBD will return 'terminated normally' H_Hat(H_Hat) only terminates because one of the instances of this recursive invocation was aborted. If none of the instances of its recursive invocation were aborted then H_Hat(H_Hat) would never terminate. H_Hat(H_Hat) is yet another example where bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) decides its input correctly. > (3) Your ABNHBD function is actually guaranteed to return one of the > above two values for every input. bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) is a partial WOULD_NOT_HALT decider that will initially only decide (H_Hat, H_Hat). The design for it to correctly decide two other infinite classes of computations is already complete. At no point in my presentation of it will it ever be all knowing. Once it is accepted that this design proves that the conventional self-referential halting problem proofs do not show that the halting problem is undecidable funding may be allocated to enhance the robustness of the halt decider design using deep learning. I would not be interested in this project myself. My interest in in perfecting the upper knowledge ontology of natural language. https://en.wikipedia.org/wiki/Upper_ontology One of the key purposes of this halting problem project is to gain very significant credibility to be able to work on the architecture of the upper knowledge ontology of AI projects like Cyc. The key thing that these projects need is an automated self-validating process to self populate their knowledge base. My upper ontology work would be focused on solving this problem. > > André > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-27 15:56 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided |
| Message-ID | <2d-dnTlwfMWn3gXCnZ2dnUU78Q3NnZ2d@brightview.co.uk> |
| In reply to | #24521 |
On 27/10/2020 15:20, olcott wrote: > On 10/27/2020 5:53 AM, André G. Isaak wrote: >> On 2020-10-26 15:57, olcott wrote: >> >>> If you were paying very close enough attention rather than merely >>> glancing at a few words here and there under the presumption that I >>> must be incorrect you would notice that none of the examples ever >>> showed a single case where: >>> >>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 M, u32 N) >>> ever returned an incorrect value for its input. >> >> Can we get you to commit the following more precise set of claims? >> >> (1) In every instance where its input would not halt when run >> independently, you ABNHBD function will always return 'non halting >> behavior detected - aborted' > > Here is what I can commit to: > There is no input to this function that can be shown to be undecidable: > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) > >> (2) In every instance where its input would halt when run >> independently, your ABNHBD will return 'terminated normally' > > H_Hat(H_Hat) only terminates because one of the instances of this > recursive invocation was aborted. If none of the instances of its > recursive invocation were aborted then H_Hat(H_Hat) would never > terminate. H_Hat(H_Hat) is yet another example where > bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) > decides its input correctly. > This is your point of confusion. H_Hat(H_Hat) is a FIXED calculation, given that we are considering a SPECIFIC PROGRAM H_Hat. For this fixed H_Hat, the calculation H_Hat(H_Hat) halts. I.e. after some definite number of steps, it reaches a halt state. There is no *INFINITE* recursive emulation in H_Hat(H_Hat), although there may well be some *FINITE* level of recursive emulation involved, depending on exactly how ABNHBD() is written. (Nothing wrong with that...) When you say "..If none of the instances of its recursive invocation were aborted then H_Hat(H_Hat) would never terminate." that is effectively meaningless, because H_Hat is a fixed program, and H_Hat(H_Hat) /does/ halt. What you /really/ mean, but won't actually say, is that if you amended H and H_Hat to create H2 and H2_Hat, in such a way that you change the logic of ABNHBD to REMOVE some particular piece of "abort" code, then THE NEW PROGRAM CALCULATION *H2_Hat(H2_Hat)* would not halt. But we are not considering what some different program would do, H_Hat is one fixed program. >> (3) Your ABNHBD function is actually guaranteed to return one of the >> above two values for every input. > > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) > is a partial WOULD_NOT_HALT decider that will initially only decide > (H_Hat, H_Hat). > > The design for it to correctly decide two other infinite classes of > computations is already complete. At no point in my presentation of it > will it ever be all knowing. > > Once it is accepted that this design proves that the conventional > self-referential halting problem proofs do not show that the halting > problem is undecidable funding may be allocated to enhance the > robustness of the halt decider design using deep learning. > > I would not be interested in this project myself. My interest in in > perfecting the upper knowledge ontology of natural language. > https://en.wikipedia.org/wiki/Upper_ontology > > One of the key purposes of this halting problem project is to gain very > significant credibility to be able to work on the architecture of the > upper knowledge ontology of AI projects like Cyc. > > The key thing that these projects need is an automated self-validating > process to self populate their knowledge base. My upper ontology work > would be focused on solving this problem. > >> >> André >> > >
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-27 12:53 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] key definitions provided |
| Message-ID | <rn9qb2$kgt$1@dont-email.me> |
| In reply to | #24521 |
On 2020-10-27 09:20, olcott wrote: > On 10/27/2020 5:53 AM, André G. Isaak wrote: >> On 2020-10-26 15:57, olcott wrote: >> >>> If you were paying very close enough attention rather than merely >>> glancing at a few words here and there under the presumption that I >>> must be incorrect you would notice that none of the examples ever >>> showed a single case where: >>> >>> bool Aborted_Because_Non_Halting_Behavior_Detected(u32 M, u32 N) >>> ever returned an incorrect value for its input. >> >> Can we get you to commit the following more precise set of claims? >> >> (1) In every instance where its input would not halt when run >> independently, you ABNHBD function will always return 'non halting >> behavior detected - aborted' > > Here is what I can commit to: > There is no input to this function that can be shown to be undecidable: > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) Are you attempting to answer my first question or my third question here? Saying no input is undecidable would seem to be an answer to my third question. It doesn't seem to have any relevance to my first question. >> (2) In every instance where its input would halt when run >> independently, your ABNHBD will return 'terminated normally' > > H_Hat(H_Hat) only terminates because one of the instances of this > recursive invocation was aborted. If none of the instances of its > recursive invocation were aborted then H_Hat(H_Hat) would never > terminate. H_Hat(H_Hat) is yet another example where > bool Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) > decides its input correctly. So when we consider H(H_Hat, H_HAT) what are you claiming is the output of: (1) Your ABNHBD contained in H (2) Your ABNHBD contained in the outermost instance of H_Hat? >> (3) Your ABNHBD function is actually guaranteed to return one of the >> above two values for every input. > > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) > is a partial WOULD_NOT_HALT decider that will initially only decide > (H_Hat, H_Hat). This contradicts your earlier claim that no input to this function can be undecidable. Are you here claiming that there *are* inputs that aren't decidable, or that there are currently inputs that are not *correctly* decidable? André -- To email remove 'invalid' & replace 'gm' with well known Google mail service.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-25 01:25 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87mu0bxib6.fsf@bsb.me.uk> |
| In reply to | #24352 |
Alan Mackenzie <acm@muc.de> writes: > Or, put another way, could you give a clear example of something for > which the HP question and your question give different answers? This is the sort of clear question that will definitely be avoided. And if it is answered, the answer will be in riddle form! I've had a go asking it myself (in another format) but I am not hopeful. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-10-25 18:38 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn4gn4$10jb$1@gioia.aioe.org> |
| In reply to | #24352 |
On 24/10/2020 22:41, Alan Mackenzie wrote:
> [...] One could program a brute force search for a
> counterexample to Goldbach's conjecture. [...]
May be worth noting that there is a somewhat curious/paradoxical
nature to brute force searches of this type. Given the set of all
programs in [say] C of length no more than N bytes, there is an integer
K such that after K steps any program in the set that has not yet
terminated will never terminate. [This is very similar to the Busy
Beaver function (qv)]. Thus a search program of general form
for (i = 1; ; i++) {
if (counterexample(i))
report ("conjecture false");
}
may be replaced by
for (i = 1; i < L ; i++) {
if (counterexample(i))
report ("conjecture false");
}
report ("conjecture proved to be true");
where L is K divided by the minimum number of steps per case.
[Of course, all the integers here have to be (very) big_ints.]
Details left to the imagination. Any integer bigger than the
L described above will serve equally well. Note that K is a
very rapidly-increasing function of N, so a very simple search
will likely report success much faster than a sophisticated
search, though the latter would report failure much faster.
--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Godfrey
[toc] | [prev] | [next] | [standalone]
| From | Alan Mackenzie <acm@muc.de> |
|---|---|
| Date | 2020-10-25 20:49 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn4oc1$2crg$2@news.muc.de> |
| In reply to | #24407 |
Andy Walker <anw@cuboid.co.uk> wrote:
> On 24/10/2020 22:41, Alan Mackenzie wrote:
>> [...] One could program a brute force search for a
>> counterexample to Goldbach's conjecture. [...]
> May be worth noting that there is a somewhat curious/paradoxical
> nature to brute force searches of this type. Given the set of all
> programs in [say] C of length no more than N bytes, there is an integer
> K such that after K steps any program in the set that has not yet
> terminated will never terminate. [This is very similar to the Busy
> Beaver function (qv)].
Thanks! I didn't know that
> Thus a search program of general form
> for (i = 1; ; i++) {
> if (counterexample(i))
> report ("conjecture false");
> }
> may be replaced by
> for (i = 1; i < L ; i++) {
> if (counterexample(i))
> report ("conjecture false");
> }
> report ("conjecture proved to be true");
> where L is K divided by the minimum number of steps per case.
> [Of course, all the integers here have to be (very) big_ints.]
> Details left to the imagination. Any integer bigger than the
> L described above will serve equally well. Note that K is a
> very rapidly-increasing function of N, ....
What does "very" mean here? Something like the Ackermann function?
> .... so a very simple search will likely report success much faster
> than a sophisticated search, though the latter would report failure
> much faster.
> --
> Andy Walker, Nottingham.
> Andy's music pages: www.cuboid.me.uk/andy/Music
> Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Godfrey
--
Alan Mackenzie (Nuremberg, Germany).
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-25 23:26 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87y2jt6g6s.fsf@bsb.me.uk> |
| In reply to | #24418 |
Alan Mackenzie <acm@muc.de> writes:
> Andy Walker <anw@cuboid.co.uk> wrote:
>> On 24/10/2020 22:41, Alan Mackenzie wrote:
>>> [...] One could program a brute force search for a
>>> counterexample to Goldbach's conjecture. [...]
>
>> May be worth noting that there is a somewhat curious/paradoxical
>> nature to brute force searches of this type. Given the set of all
>> programs in [say] C of length no more than N bytes, there is an integer
>> K such that after K steps any program in the set that has not yet
>> terminated will never terminate. [This is very similar to the Busy
>> Beaver function (qv)].
>
> Thanks! I didn't know that
>
>> Thus a search program of general form
>
>> for (i = 1; ; i++) {
>> if (counterexample(i))
>> report ("conjecture false");
>> }
>
>> may be replaced by
>
>> for (i = 1; i < L ; i++) {
>> if (counterexample(i))
>> report ("conjecture false");
>> }
>> report ("conjecture proved to be true");
>
>> where L is K divided by the minimum number of steps per case.
>> [Of course, all the integers here have to be (very) big_ints.]
>> Details left to the imagination. Any integer bigger than the
>> L described above will serve equally well. Note that K is a
>> very rapidly-increasing function of N, ....
>
> What does "very" mean here? Something like the Ackermann function?
In terms of fast-growing functions, Ackermann's function is on the
training slopes! But, more importantly, is it computable so it can't
fit the bill here, or the search would have a computable bound. Very
rapidly-increasing, in this context, means faster than any computable
function, like the busy bee function.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-10-25 23:57 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn53d5$f6g$1@gioia.aioe.org> |
| In reply to | #24418 |
On 25/10/2020 20:49, Alan Mackenzie wrote:
>> [...] Note that K is a
>> very rapidly-increasing function of N, ....
> What does "very" mean here? Something like the Ackermann function?
No, Ackermann is a total pussy in this context, as it is in
the Busy Beaver problem. Ackermann is computable; K isn't. Any
function whatsoever that you can write down in a few lines is, by
the meaning of BB(N) or K(N), much too small.
So you can't compute how many steps you need to take to solve
Goldbach. On the other hand, any larger number of steps whatsoever
would be enough; any conjecture of this general type [which is most
of the well-known/interesting ones] can in principle be solved simply
by searching far enough, you don't have to keep going "to infinity".
On the third hand, this is a purely theoretical notion, as K is
literally unimaginably large ["uncomputable", so no combination of
exps and factorials even iterated, recursed and stacked as high as
you like, will be enough except for very small problems]. On the
fourth hand, roll on quantum computing ....
The Wiki entry on Busy Beavers has much more, including
references to Goldbach, the Riemann hypothesis, complexity, ZFC,
.... Recommended, despite having "multiple issues":
https://en.wikipedia.org/wiki/Busy_beaver
--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Godfrey
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 22:43 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <874kmk4o09.fsf@bsb.me.uk> |
| In reply to | #24249 |
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes: > Aborting is the equivalent of saying "let's smash the machine". No it's not. In this case, it's simply a simulator not simulating anymore when some significant condition has been met. In the general case, it's just another way that the control flaw changes. > You > might do that if you think it will never halt. A Turing machine cannot > abort itself. I dislike giving programs agency. What does "abort itself" even mean? A program follows a control path determined by things like inputs, data in memory and maybe signals. Some of those paths result in the program stopping, and some of those are called an abort. There is nothing special about the aborts. I don't the point you are trying to make by saying TMs can't do this. TMs can't add two registers. Register machine code can't alter a tape symbol. They are different models. The fact that one has an event called an abort is not even as substantive a difference as these because it's just a control path. A register machine can do "if R==0 abort" and a TM can detect that some part of the tape is zero and enter the state called "abort!!!". Names are not magic. Neither can "smash itself" but you single out TMs? Both can stop and execute no more steps. I don't understand why you've got sucked in PO's use of terms. >> > The Linz paradox relies on H returning a result to H_Hat. >> There is no paradox in Linz. And in Linz, no results are returned anywhere. >> > I'm not sure I follow you here. H returns a result to H_Hat surely? No. Have you read the proof? H^ is a TM constructed from H. There is no "subprogram" or "function" to return anything to anything. (Actually, didn't I give you the details of what H^ does in actual TM state transitions? I thought I did.) > And H_Hat can't be decided because if H decides "halt" it loops > forever whilst if H decides "no halt" it halts. So H_Hat is a paradox for > H. Why do you call that a paradox? Is a function that returns the largest integer paradoxical because I can write another that calls it and adds one? Maybe we just think of paradoxes in different ways. I don't want to end up arguing about the words, provided we agree on the facts. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 17:10 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <-_2dnbs7NPMlyQ7CnZ2dnUU7-QvNnZ2d@giganews.com> |
| In reply to | #24253 |
On 10/23/2020 4:43 PM, Ben Bacarisse wrote: > Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes: > >> Aborting is the equivalent of saying "let's smash the machine". > > No it's not. In this case, it's simply a simulator not simulating > anymore when some significant condition has been met. In the general > case, it's just another way that the control flaw changes. > >> You >> might do that if you think it will never halt. A Turing machine cannot >> abort itself. > > I dislike giving programs agency. What does "abort itself" even mean? > A program follows a control path determined by things like inputs, data > in memory and maybe signals. Some of those paths result in the program > stopping, and some of those are called an abort. There is nothing > special about the aborts. > > I don't the point you are trying to make by saying TMs can't do this. > TMs can't add two registers. Register machine code can't alter a tape > symbol. They are different models. The fact that one has an event > called an abort is not even as substantive a difference as these because > it's just a control path. A register machine can do "if R==0 abort" and > a TM can detect that some part of the tape is zero and enter the state > called "abort!!!". Names are not magic. > > Neither can "smash itself" but you single out TMs? Both can stop and > execute no more steps. I don't understand why you've got sucked in PO's > use of terms. > >>>> The Linz paradox relies on H returning a result to H_Hat. >>> There is no paradox in Linz. And in Linz, no results are returned anywhere. >>> >> I'm not sure I follow you here. H returns a result to H_Hat surely? > > No. Have you read the proof? H^ is a TM constructed from H. There is > no "subprogram" or "function" to return anything to anything. > (Actually, didn't I give you the details of what H^ does in actual TM > state transitions? I thought I did.) > >> And H_Hat can't be decided because if H decides "halt" it loops >> forever whilst if H decides "no halt" it halts. So H_Hat is a paradox for >> H. > > Why do you call that a paradox? Is a function that returns the largest > integer paradoxical because I can write another that calls it and adds > one? Maybe we just think of paradoxes in different ways. I don't want > to end up arguing about the words, provided we agree on the facts. > A program that was intentionally designed to do the opposite of what its halt decider decided that it would do is paradoxical in the sense that like other paradoxes it is undecidable. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 00:27 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87tuuk34mc.fsf@bsb.me.uk> |
| In reply to | #24256 |
olcott <NoOne@NoWhere.com> writes: > A program that was intentionally designed to do the opposite of what > its halt decider decided that it would do is paradoxical in the sense > that like other paradoxes it is undecidable. Neither is undecidable. I know this is just you not knowing what the words mean, but I am too tired to try to explain them to you again. I just want other people to know that this remark is wrong. The halting (or not) of any finite set of programs is "decidable" though computable is a better term for technical reasons. If anyone else wants to know why, ask away. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 18:34 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <MYSdnZFV8-889Q7CnZ2dnUU7-L-dnZ2d@giganews.com> |
| In reply to | #24262 |
On 10/23/2020 6:27 PM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> A program that was intentionally designed to do the opposite of what >> its halt decider decided that it would do is paradoxical in the sense >> that like other paradoxes it is undecidable. > > Neither is undecidable. I know this is just you not knowing what the > words mean, but I am too tired to try to explain them to you again. I > just want other people to know that this remark is wrong. The halting > (or not) of any finite set of programs is "decidable" though computable > is a better term for technical reasons. If anyone else wants to know > why, ask away. > I already found the paper that answers why. Yes every finite machine's algorithm is decidable if one is willing to wait a googleplex number of years past the heat death of the universe. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
Page 13 of 25 — ← Prev page 1 … 11 12 [13] 14 15 … 25 Next page →
Back to top | Article view | comp.theory
csiph-web