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 2 of 25 — ← Prev page 1 [2] 3 4 … 25 Next page →
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-21 17:55 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] |
| Message-ID | <u7-dnWAvkeDjIQ3CnZ2dnUU7-YfNnZ2d@giganews.com> |
| In reply to | #24082 |
On 10/21/2020 5:10 PM, Mike Terry wrote:
> On 21/10/2020 21:27, olcott wrote:
>> On 10/21/2020 2:30 PM, Mike Terry wrote:
>>> On 21/10/2020 17:48, olcott wrote:
>>>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>>> On 21/10/2020 04:07, olcott wrote:
> [... snip ...]
>
>>>>>>
>>>>>> I liked your simplest possible H_Hat() so I used it.
>>>>>> Immediately before I saw your simplest possible H_Hat() I had just
>>>>>> reduced the complexity of mine to be exactly the same so we are of
>>>>>> one
>>>>>> mind on this.
>>>>>>
>>>>>>
>>>>>> // M has address of H_Hat()
>>>>>> int H_Hat(u32 M)
>>>>>> {
>>>>>> int Abort = DebugTrace(M, M);
>>>>>> if (Abort)
>>>>>> {
>>>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>>>> HALT // has been aborted
>>>>>> }
>>>>>> else
>>>>>> {
>>>>>> MOV_EAX_1 // M(M) has halted
>>>>>> HERE: goto HERE;
>>>>>> HALT
>>>>>> }
>>>>>> }
>>>>>>
>>>>>>
>>>>>> // M and N have the address of H_Hat()
>>>>>> int H(u32 M, u32 N)
>>>>>> {
>>>>>> int Abort = DebugTrace(M, N);
>>>>>> if (Abort)
>>>>>> {
>>>>>> MOV_EAX_0 // DebugTrace says that M(N)
>>>>>> HALT // has been aborted
>>>>>> }
>>>>>> else
>>>>>> {
>>>>>> MOV_EAX_1 // M(N) has halted
>>>>>> HALT
>>>>>> }
>>>>>> }
>>>>>>
>>>>>> int main()
>>>>>> {
>>>>>> u32 M = (u32)H_Hat;
>>>>>> H(M, M);
>>>>>> HALT;
>>>>>> }
>>>>>>
> [... snip ...]
>
>>>>> Above, I mentioned execution contexts (or paths) and there are two of
>>>>> these that matter at the high level I am interested in.
>>>>>
>>>>> CONTEXT 1: In the *H* COFF file execution, DebugTrace(H_Hat,H_Hat)
>>>>> is called ONCE at the highest level (from main()). [If DebugTrace()
>>>>> internally results in further DebugTrace() invocations, at the high
>>>>> level I'm considering those don't matter...]
>>>>>
>>>>
>>>> A new and totally separate execution context is created every single
>>>> time that DebugTrace() is invoked.
>>>>
>>>>> CONTEXT 2: DebugTrace(H_Hat,H_Hat) is also called in the *H^* COFF
>>>>> file. It is called ONCE at the highest level, from H_Hat which in
>>>>> turn has just been called by main(). [Again, if DebugTrace()
>>>>> internally results in further DebugTrace() invocations, at the high
>>>>> level I'm considering those don't matter...]
>>>>>
>>>>> My question was whether /those/ two specific calls to DebugTrace
>>>>> returns the same RC.
>>>>>
>>>>> Mike.
>>>>>
>>>>
>>>> As Ben has very carefully elaborated twice the invocation of a function
>>>> with the same input must result in the same output. The return value
>>>> from H_Hat() and the return value from H() are the same return value.
>>>
>>> Hopefully this is a typo - I asked about return codes from DebugTrace,
>>
>> The return value from DebugTrace() is the same for H() and H_Hat().
>>
>>> not from H or H_Hat. H^ in the Linz proof is not a decider of
>>> anything, so output from H^ is irrelevant; all that matters is whether
>>> it halts.
>>>
>>
>>> I'll take it that you mean:
>>>
>>> "The calls to DebugTrace() in the two contexts you've
>>> described both return the same return code"
>>>
>>
>> Yes.
>>
> [... snip ...]
>
>>> OK, so you say the calls to DebugTrace() in Context (1) and (2) return
>>> the same result. There are just two possibilities:
>>>
>>> *Both DebugTrace() RCs are zero* :
>>>
>>> In Context (1) this indicates that H will decide that
>>> calculation H_Hat (H_Hat) halts. (MOV_EAX_1; HALT; will
>>> be executed.)
>>>
>>> In Context (2) this means that the H_Hat code will take
>>> the branch containing HERE: goto HERE;, and so H_Hat will
>>> loop at this point.
>>>
>>> So H clearly made the wrong halt decision for the calculation. OK, so
>>> the other possibility is...
>>>
>>> *Both DebugTrace() RCs are non-zero* :
>>>
>>> In Context (1) this indicates that H will decide that
>>> calculation H_Hat (H_Hat) does not halt. (MOV_EAX_0; HALT; will
>>> be executed.)
>>>
>>> In Context (2) this means that the H_Hat code will take
>>> the branch containing MOV_EAX_0; HALT;, and so H_Hat(H_Hat)
>>> will halt at this point.
>>>
>>> Again H has made the wrong decision for the calculation.
>>>
>>
>> No you have this incorrectly.
>
> You say that I have this incorrectly, without giving any indication of
> what you think is incorrect. That looks like being deliberately unhelpful!
Carefully study my words immediately below again and again until you
fully understand exactly how I transformed a question subject to
pathological self-reference into a question that is not subject to
pathological self-reference thus eliminating the impossibility of
solving the halting problem.
>> When I change the halting problem question:
>> (a) Does H_Hat() halt on its input?
>>
>> (b) Does the execution of H_Hat() have to be aborted to prevent the halt
>> decider from getting stuck in infinite execution?
>>
>> The previously undecidable halting problem becomes decidable.
>>
>> There are no longer any cases that are impossible to decide:
>> (a) The input program must have its execution aborted.
>>
>> (b) The input program continues to execute until its execution
>> terminates.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-22 03:38 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] |
| Message-ID | <9sidnXDcRvQAbQ3CnZ2dnUU78LXNnZ2d@brightview.co.uk> |
| In reply to | #24084 |
On 21/10/2020 23:55, olcott wrote:
> On 10/21/2020 5:10 PM, Mike Terry wrote:
>> On 21/10/2020 21:27, olcott wrote:
>>> On 10/21/2020 2:30 PM, Mike Terry wrote:
>>>> On 21/10/2020 17:48, olcott wrote:
>>>>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>>>> On 21/10/2020 04:07, olcott wrote:
>> [... snip ...]
>>
>>>>>>>
>>>>>>> I liked your simplest possible H_Hat() so I used it.
>>>>>>> Immediately before I saw your simplest possible H_Hat() I had just
>>>>>>> reduced the complexity of mine to be exactly the same so we are
>>>>>>> of one
>>>>>>> mind on this.
>>>>>>>
>>>>>>>
>>>>>>> // M has address of H_Hat()
>>>>>>> int H_Hat(u32 M)
>>>>>>> {
>>>>>>> int Abort = DebugTrace(M, M);
>>>>>>> if (Abort)
>>>>>>> {
>>>>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>>>>> HALT // has been aborted
>>>>>>> }
>>>>>>> else
>>>>>>> {
>>>>>>> MOV_EAX_1 // M(M) has halted
>>>>>>> HERE: goto HERE;
>>>>>>> HALT
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>>
>>>>>>> // M and N have the address of H_Hat()
>>>>>>> int H(u32 M, u32 N)
>>>>>>> {
>>>>>>> int Abort = DebugTrace(M, N);
>>>>>>> if (Abort)
>>>>>>> {
>>>>>>> MOV_EAX_0 // DebugTrace says that M(N)
>>>>>>> HALT // has been aborted
>>>>>>> }
>>>>>>> else
>>>>>>> {
>>>>>>> MOV_EAX_1 // M(N) has halted
>>>>>>> HALT
>>>>>>> }
>>>>>>> }
>>>>>>>
>>>>>>> int main()
>>>>>>> {
>>>>>>> u32 M = (u32)H_Hat;
>>>>>>> H(M, M);
>>>>>>> HALT;
>>>>>>> }
>>>>>>>
>> [... snip ...]
>>
>>>>>> Above, I mentioned execution contexts (or paths) and there are two of
>>>>>> these that matter at the high level I am interested in.
>>>>>>
>>>>>> CONTEXT 1: In the *H* COFF file execution, DebugTrace(H_Hat,H_Hat)
>>>>>> is called ONCE at the highest level (from main()). [If DebugTrace()
>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>> level I'm considering those don't matter...]
>>>>>>
>>>>>
>>>>> A new and totally separate execution context is created every single
>>>>> time that DebugTrace() is invoked.
>>>>>
>>>>>> CONTEXT 2: DebugTrace(H_Hat,H_Hat) is also called in the *H^* COFF
>>>>>> file. It is called ONCE at the highest level, from H_Hat which in
>>>>>> turn has just been called by main(). [Again, if DebugTrace()
>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>> level I'm considering those don't matter...]
>>>>>>
>>>>>> My question was whether /those/ two specific calls to DebugTrace
>>>>>> returns the same RC.
>>>>>>
>>>>>> Mike.
>>>>>>
>>>>>
>>>>> As Ben has very carefully elaborated twice the invocation of a
>>>>> function
>>>>> with the same input must result in the same output. The return value
>>>>> from H_Hat() and the return value from H() are the same return value.
>>>>
>>>> Hopefully this is a typo - I asked about return codes from DebugTrace,
>>>
>>> The return value from DebugTrace() is the same for H() and H_Hat().
>>>
>>>> not from H or H_Hat. H^ in the Linz proof is not a decider of
>>>> anything, so output from H^ is irrelevant; all that matters is whether
>>>> it halts.
>>>>
>>>
>>>> I'll take it that you mean:
>>>>
>>>> "The calls to DebugTrace() in the two contexts you've
>>>> described both return the same return code"
>>>>
>>>
>>> Yes.
>>>
>> [... snip ...]
>>
>>>> OK, so you say the calls to DebugTrace() in Context (1) and (2) return
>>>> the same result. There are just two possibilities:
>>>>
>>>> *Both DebugTrace() RCs are zero* :
>>>>
>>>> In Context (1) this indicates that H will decide that
>>>> calculation H_Hat (H_Hat) halts. (MOV_EAX_1; HALT; will
>>>> be executed.)
>>>>
>>>> In Context (2) this means that the H_Hat code will take
>>>> the branch containing HERE: goto HERE;, and so H_Hat will
>>>> loop at this point.
>>>>
>>>> So H clearly made the wrong halt decision for the calculation. OK, so
>>>> the other possibility is...
>>>>
>>>> *Both DebugTrace() RCs are non-zero* :
>>>>
>>>> In Context (1) this indicates that H will decide that
>>>> calculation H_Hat (H_Hat) does not halt. (MOV_EAX_0; HALT; will
>>>> be executed.)
>>>>
>>>> In Context (2) this means that the H_Hat code will take
>>>> the branch containing MOV_EAX_0; HALT;, and so H_Hat(H_Hat)
>>>> will halt at this point.
>>>>
>>>> Again H has made the wrong decision for the calculation.
>>>>
>>>
>>> No you have this incorrectly.
>>
>> You say that I have this incorrectly, without giving any indication of
>> what you think is incorrect. That looks like being deliberately
>> unhelpful!
>
> Carefully study my words immediately below again and again until you
> fully understand exactly how I transformed a question subject to
> pathological self-reference into a question that is not subject to
> pathological self-reference thus eliminating the impossibility of
> solving the halting problem.
You forgot to answer the question! Here it is again:
Will both the DebugTrace() return codes be ZERO, or will they be
NON-ZERO? (You previously agreed they would be the same...)
Mike.
>
>>> When I change the halting problem question:
>>> (a) Does H_Hat() halt on its input?
>>>
>>> (b) Does the execution of H_Hat() have to be aborted to prevent the halt
>>> decider from getting stuck in infinite execution?
>>>
>>> The previously undecidable halting problem becomes decidable.
>>>
>>> There are no longer any cases that are impossible to decide:
>>> (a) The input program must have its execution aborted.
>>>
>>> (b) The input program continues to execute until its execution
>>> terminates.
>
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-21 21:54 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] |
| Message-ID | <a4WdnWTtk5T9aQ3CnZ2dnUU7-K3NnZ2d@giganews.com> |
| In reply to | #24093 |
On 10/21/2020 9:38 PM, Mike Terry wrote:
> On 21/10/2020 23:55, olcott wrote:
>> On 10/21/2020 5:10 PM, Mike Terry wrote:
>>> On 21/10/2020 21:27, olcott wrote:
>>>> On 10/21/2020 2:30 PM, Mike Terry wrote:
>>>>> On 21/10/2020 17:48, olcott wrote:
>>>>>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>>>>> On 21/10/2020 04:07, olcott wrote:
>>> [... snip ...]
>>>
>>>>>>>>
>>>>>>>> I liked your simplest possible H_Hat() so I used it.
>>>>>>>> Immediately before I saw your simplest possible H_Hat() I had just
>>>>>>>> reduced the complexity of mine to be exactly the same so we are
>>>>>>>> of one
>>>>>>>> mind on this.
>>>>>>>>
>>>>>>>>
>>>>>>>> // M has address of H_Hat()
>>>>>>>> int H_Hat(u32 M)
>>>>>>>> {
>>>>>>>> int Abort = DebugTrace(M, M);
>>>>>>>> if (Abort)
>>>>>>>> {
>>>>>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>>>>>> HALT // has been aborted
>>>>>>>> }
>>>>>>>> else
>>>>>>>> {
>>>>>>>> MOV_EAX_1 // M(M) has halted
>>>>>>>> HERE: goto HERE;
>>>>>>>> HALT
>>>>>>>> }
>>>>>>>> }
>>>>>>>>
>>>>>>>>
>>>>>>>> // M and N have the address of H_Hat()
>>>>>>>> int H(u32 M, u32 N)
>>>>>>>> {
>>>>>>>> int Abort = DebugTrace(M, N);
>>>>>>>> if (Abort)
>>>>>>>> {
>>>>>>>> MOV_EAX_0 // DebugTrace says that M(N)
>>>>>>>> HALT // has been aborted
>>>>>>>> }
>>>>>>>> else
>>>>>>>> {
>>>>>>>> MOV_EAX_1 // M(N) has halted
>>>>>>>> HALT
>>>>>>>> }
>>>>>>>> }
>>>>>>>>
>>>>>>>> int main()
>>>>>>>> {
>>>>>>>> u32 M = (u32)H_Hat;
>>>>>>>> H(M, M);
>>>>>>>> HALT;
>>>>>>>> }
>>>>>>>>
>>> [... snip ...]
>>>
>>>>>>> Above, I mentioned execution contexts (or paths) and there are
>>>>>>> two of
>>>>>>> these that matter at the high level I am interested in.
>>>>>>>
>>>>>>> CONTEXT 1: In the *H* COFF file execution, DebugTrace(H_Hat,H_Hat)
>>>>>>> is called ONCE at the highest level (from main()). [If DebugTrace()
>>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>>> level I'm considering those don't matter...]
>>>>>>>
>>>>>>
>>>>>> A new and totally separate execution context is created every single
>>>>>> time that DebugTrace() is invoked.
>>>>>>
>>>>>>> CONTEXT 2: DebugTrace(H_Hat,H_Hat) is also called in the *H^* COFF
>>>>>>> file. It is called ONCE at the highest level, from H_Hat which in
>>>>>>> turn has just been called by main(). [Again, if DebugTrace()
>>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>>> level I'm considering those don't matter...]
>>>>>>>
>>>>>>> My question was whether /those/ two specific calls to DebugTrace
>>>>>>> returns the same RC.
>>>>>>>
>>>>>>> Mike.
>>>>>>>
>>>>>>
>>>>>> As Ben has very carefully elaborated twice the invocation of a
>>>>>> function
>>>>>> with the same input must result in the same output. The return value
>>>>>> from H_Hat() and the return value from H() are the same return value.
>>>>>
>>>>> Hopefully this is a typo - I asked about return codes from DebugTrace,
>>>>
>>>> The return value from DebugTrace() is the same for H() and H_Hat().
>>>>
>>>>> not from H or H_Hat. H^ in the Linz proof is not a decider of
>>>>> anything, so output from H^ is irrelevant; all that matters is whether
>>>>> it halts.
>>>>>
>>>>
>>>>> I'll take it that you mean:
>>>>>
>>>>> "The calls to DebugTrace() in the two contexts you've
>>>>> described both return the same return code"
>>>>>
>>>>
>>>> Yes.
>>>>
>>> [... snip ...]
>>>
>>>>> OK, so you say the calls to DebugTrace() in Context (1) and (2) return
>>>>> the same result. There are just two possibilities:
>>>>>
>>>>> *Both DebugTrace() RCs are zero* :
>>>>>
>>>>> In Context (1) this indicates that H will decide that
>>>>> calculation H_Hat (H_Hat) halts. (MOV_EAX_1; HALT; will
>>>>> be executed.)
>>>>>
>>>>> In Context (2) this means that the H_Hat code will take
>>>>> the branch containing HERE: goto HERE;, and so H_Hat will
>>>>> loop at this point.
>>>>>
>>>>> So H clearly made the wrong halt decision for the calculation. OK, so
>>>>> the other possibility is...
>>>>>
>>>>> *Both DebugTrace() RCs are non-zero* :
>>>>>
>>>>> In Context (1) this indicates that H will decide that
>>>>> calculation H_Hat (H_Hat) does not halt. (MOV_EAX_0; HALT; will
>>>>> be executed.)
>>>>>
>>>>> In Context (2) this means that the H_Hat code will take
>>>>> the branch containing MOV_EAX_0; HALT;, and so H_Hat(H_Hat)
>>>>> will halt at this point.
>>>>>
>>>>> Again H has made the wrong decision for the calculation.
>>>>>
>>>>
>>>> No you have this incorrectly.
>>>
>>> You say that I have this incorrectly, without giving any indication of
>>> what you think is incorrect. That looks like being deliberately
>>> unhelpful!
>>
>> Carefully study my words immediately below again and again until you
>> fully understand exactly how I transformed a question subject to
>> pathological self-reference into a question that is not subject to
>> pathological self-reference thus eliminating the impossibility of
>> solving the halting problem.
>
> You forgot to answer the question! Here it is again:
>
> Will both the DebugTrace() return codes be ZERO, or will they be
> NON-ZERO? (You previously agreed they would be the same...)
>
> Mike.
That question will only be answered by fully operational code.
The key proof has already been provided. No matter what return value
that DebugTrace() provides if it is always answering the question:
Was your input aborted because it would not otherwise halt?
The halting problem becomes decidable.
>>>> When I change the halting problem question:
>>>> (a) Does H_Hat() halt on its input?
>>>>
>>>> (b) Does the execution of H_Hat() have to be aborted to prevent the
>>>> halt
>>>> decider from getting stuck in infinite execution?
>>>>
>>>> The previously undecidable halting problem becomes decidable.
>>>>
>>>> There are no longer any cases that are impossible to decide:
>>>> (a) The input program must have its execution aborted.
>>>>
>>>> (b) The input program continues to execute until its execution
>>>> terminates.
>>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-22 04:38 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ HP proof refutation ] |
| Message-ID | <P8WdndjHabJYYw3CnZ2dnUU78b_NnZ2d@brightview.co.uk> |
| In reply to | #24094 |
On 22/10/2020 03:54, olcott wrote:
> On 10/21/2020 9:38 PM, Mike Terry wrote:
>> On 21/10/2020 23:55, olcott wrote:
>>> On 10/21/2020 5:10 PM, Mike Terry wrote:
>>>> On 21/10/2020 21:27, olcott wrote:
>>>>> On 10/21/2020 2:30 PM, Mike Terry wrote:
>>>>>> On 21/10/2020 17:48, olcott wrote:
>>>>>>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>>>>>> On 21/10/2020 04:07, olcott wrote:
>>>> [... snip ...]
>>>>
>>>>>>>>>
>>>>>>>>> I liked your simplest possible H_Hat() so I used it.
>>>>>>>>> Immediately before I saw your simplest possible H_Hat() I had just
>>>>>>>>> reduced the complexity of mine to be exactly the same so we are
>>>>>>>>> of one
>>>>>>>>> mind on this.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> // M has address of H_Hat()
>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>> {
>>>>>>>>> int Abort = DebugTrace(M, M);
>>>>>>>>> if (Abort)
>>>>>>>>> {
>>>>>>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>>>>>>> HALT // has been aborted
>>>>>>>>> }
>>>>>>>>> else
>>>>>>>>> {
>>>>>>>>> MOV_EAX_1 // M(M) has halted
>>>>>>>>> HERE: goto HERE;
>>>>>>>>> HALT
>>>>>>>>> }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> // M and N have the address of H_Hat()
>>>>>>>>> int H(u32 M, u32 N)
>>>>>>>>> {
>>>>>>>>> int Abort = DebugTrace(M, N);
>>>>>>>>> if (Abort)
>>>>>>>>> {
>>>>>>>>> MOV_EAX_0 // DebugTrace says that M(N)
>>>>>>>>> HALT // has been aborted
>>>>>>>>> }
>>>>>>>>> else
>>>>>>>>> {
>>>>>>>>> MOV_EAX_1 // M(N) has halted
>>>>>>>>> HALT
>>>>>>>>> }
>>>>>>>>> }
>>>>>>>>>
>>>>>>>>> int main()
>>>>>>>>> {
>>>>>>>>> u32 M = (u32)H_Hat;
>>>>>>>>> H(M, M);
>>>>>>>>> HALT;
>>>>>>>>> }
>>>>>>>>>
>>>> [... snip ...]
>>>>
>>>>>>>> Above, I mentioned execution contexts (or paths) and there are
>>>>>>>> two of
>>>>>>>> these that matter at the high level I am interested in.
>>>>>>>>
>>>>>>>> CONTEXT 1: In the *H* COFF file execution,
>>>>>>>> DebugTrace(H_Hat,H_Hat)
>>>>>>>> is called ONCE at the highest level (from main()). [If
>>>>>>>> DebugTrace()
>>>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>>>> level I'm considering those don't matter...]
>>>>>>>>
>>>>>>>
>>>>>>> A new and totally separate execution context is created every single
>>>>>>> time that DebugTrace() is invoked.
>>>>>>>
>>>>>>>> CONTEXT 2: DebugTrace(H_Hat,H_Hat) is also called in the *H^*
>>>>>>>> COFF
>>>>>>>> file. It is called ONCE at the highest level, from H_Hat which in
>>>>>>>> turn has just been called by main(). [Again, if DebugTrace()
>>>>>>>> internally results in further DebugTrace() invocations, at the high
>>>>>>>> level I'm considering those don't matter...]
>>>>>>>>
>>>>>>>> My question was whether /those/ two specific calls to DebugTrace
>>>>>>>> returns the same RC.
>>>>>>>>
>>>>>>>> Mike.
>>>>>>>>
>>>>>>>
>>>>>>> As Ben has very carefully elaborated twice the invocation of a
>>>>>>> function
>>>>>>> with the same input must result in the same output. The return value
>>>>>>> from H_Hat() and the return value from H() are the same return
>>>>>>> value.
>>>>>>
>>>>>> Hopefully this is a typo - I asked about return codes from
>>>>>> DebugTrace,
>>>>>
>>>>> The return value from DebugTrace() is the same for H() and H_Hat().
>>>>>
>>>>>> not from H or H_Hat. H^ in the Linz proof is not a decider of
>>>>>> anything, so output from H^ is irrelevant; all that matters is
>>>>>> whether
>>>>>> it halts.
>>>>>>
>>>>>
>>>>>> I'll take it that you mean:
>>>>>>
>>>>>> "The calls to DebugTrace() in the two contexts you've
>>>>>> described both return the same return code"
>>>>>>
>>>>>
>>>>> Yes.
>>>>>
>>>> [... snip ...]
>>>>
>>>>>> OK, so you say the calls to DebugTrace() in Context (1) and (2)
>>>>>> return
>>>>>> the same result. There are just two possibilities:
>>>>>>
>>>>>> *Both DebugTrace() RCs are zero* :
>>>>>>
>>>>>> In Context (1) this indicates that H will decide that
>>>>>> calculation H_Hat (H_Hat) halts. (MOV_EAX_1; HALT; will
>>>>>> be executed.)
>>>>>>
>>>>>> In Context (2) this means that the H_Hat code will take
>>>>>> the branch containing HERE: goto HERE;, and so H_Hat will
>>>>>> loop at this point.
>>>>>>
>>>>>> So H clearly made the wrong halt decision for the calculation.
>>>>>> OK, so
>>>>>> the other possibility is...
>>>>>>
>>>>>> *Both DebugTrace() RCs are non-zero* :
>>>>>>
>>>>>> In Context (1) this indicates that H will decide that
>>>>>> calculation H_Hat (H_Hat) does not halt. (MOV_EAX_0; HALT; will
>>>>>> be executed.)
>>>>>>
>>>>>> In Context (2) this means that the H_Hat code will take
>>>>>> the branch containing MOV_EAX_0; HALT;, and so H_Hat(H_Hat)
>>>>>> will halt at this point.
>>>>>>
>>>>>> Again H has made the wrong decision for the calculation.
>>>>>>
>>>>>
>>>>> No you have this incorrectly.
>>>>
>>>> You say that I have this incorrectly, without giving any indication of
>>>> what you think is incorrect. That looks like being deliberately
>>>> unhelpful!
>>>
>>> Carefully study my words immediately below again and again until you
>>> fully understand exactly how I transformed a question subject to
>>> pathological self-reference into a question that is not subject to
>>> pathological self-reference thus eliminating the impossibility of
>>> solving the halting problem.
>>
>> You forgot to answer the question! Here it is again:
>>
>> Will both the DebugTrace() return codes be ZERO, or will they be
>> NON-ZERO? (You previously agreed they would be the same...)
>>
>> Mike.
>
> That question will only be answered by fully operational code.
>
That's what I expected you to say. It won't make the slightest
difference to how your work is received if you answer now or in a few
weeks, but it's your choice.
> The key proof has already been provided.
?!
All you've provided so far is: a) the skeleton C code, which clearly is
going to support the Linz proof, if what you've said about how
DebugTrace() behaves is true; and b) what you've said below about
changing the question, which makes no difference to anything at all.
Have I missed an actual proof of something? The Usenet server I use
(Giganews) does that from time to time - it has a bug in its "add new
message to database" logic where certain updates are not atomic (w.r.t
client enquiries) when they should be.
(Or is your "changing the question" supposed to be some kind of proof?)
> No matter what return value
> that DebugTrace() provides if it is always answering the question:
>
> Was your input aborted because it would not otherwise halt?
> The halting problem becomes decidable.
>
Sorry, but that's nonsense. Oh well, guess we'll just have to wait and
see the full code.
Mike.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-21 23:33 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <Z6ednZI6mLYZlgzCnZ2dnUU7-Y_NnZ2d@giganews.com> |
| In reply to | #24096 |
On 10/21/2020 10:38 PM, Mike Terry wrote:
> On 22/10/2020 03:54, olcott wrote:
>> On 10/21/2020 9:38 PM, Mike Terry wrote:
>>> On 21/10/2020 23:55, olcott wrote:
>>>> On 10/21/2020 5:10 PM, Mike Terry wrote:
>>>>> On 21/10/2020 21:27, olcott wrote:
>>>>>> On 10/21/2020 2:30 PM, Mike Terry wrote:
>>>>>>> On 21/10/2020 17:48, olcott wrote:
>>>>>>>> On 10/21/2020 10:28 AM, Mike Terry wrote:
>>>>>>>>> On 21/10/2020 04:07, olcott wrote:
>>>>> [... snip ...]
>>>>>
>>>>>>>>>>
>>>>>>>>>> I liked your simplest possible H_Hat() so I used it.
>>>>>>>>>> Immediately before I saw your simplest possible H_Hat() I had
>>>>>>>>>> just
>>>>>>>>>> reduced the complexity of mine to be exactly the same so we are
>>>>>>>>>> of one
>>>>>>>>>> mind on this.
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> // M has address of H_Hat()
>>>>>>>>>> int H_Hat(u32 M)
>>>>>>>>>> {
>>>>>>>>>> int Abort = DebugTrace(M, M);
>>>>>>>>>> if (Abort)
>>>>>>>>>> {
>>>>>>>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>>>>>>>> HALT // has been aborted
>>>>>>>>>> }
>>>>>>>>>> else
>>>>>>>>>> {
>>>>>>>>>> MOV_EAX_1 // M(M) has halted
>>>>>>>>>> HERE: goto HERE;
>>>>>>>>>> HALT
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> // M and N have the address of H_Hat()
>>>>>>>>>> int H(u32 M, u32 N)
>>>>>>>>>> {
>>>>>>>>>> int Abort = DebugTrace(M, N);
>>>>>>>>>> if (Abort)
>>>>>>>>>> {
>>>>>>>>>> MOV_EAX_0 // DebugTrace says that M(N)
>>>>>>>>>> HALT // has been aborted
>>>>>>>>>> }
>>>>>>>>>> else
>>>>>>>>>> {
>>>>>>>>>> MOV_EAX_1 // M(N) has halted
>>>>>>>>>> HALT
>>>>>>>>>> }
>>>>>>>>>> }
>>>>>>>>>>
>>>>>>>>>> int main()
>>>>>>>>>> {
>>>>>>>>>> u32 M = (u32)H_Hat;
>>>>>>>>>> H(M, M);
>>>>>>>>>> HALT;
>>>>>>>>>> }
>>>>>>>>>>
>>>>> [... snip ...]
>>>>>
>>>>>>>>> Above, I mentioned execution contexts (or paths) and there are
>>>>>>>>> two of
>>>>>>>>> these that matter at the high level I am interested in.
>>>>>>>>>
>>>>>>>>> CONTEXT 1: In the *H* COFF file execution,
>>>>>>>>> DebugTrace(H_Hat,H_Hat)
>>>>>>>>> is called ONCE at the highest level (from main()). [If
>>>>>>>>> DebugTrace()
>>>>>>>>> internally results in further DebugTrace() invocations, at the
>>>>>>>>> high
>>>>>>>>> level I'm considering those don't matter...]
>>>>>>>>>
>>>>>>>>
>>>>>>>> A new and totally separate execution context is created every
>>>>>>>> single
>>>>>>>> time that DebugTrace() is invoked.
>>>>>>>>
>>>>>>>>> CONTEXT 2: DebugTrace(H_Hat,H_Hat) is also called in the *H^*
>>>>>>>>> COFF
>>>>>>>>> file. It is called ONCE at the highest level, from H_Hat which in
>>>>>>>>> turn has just been called by main(). [Again, if DebugTrace()
>>>>>>>>> internally results in further DebugTrace() invocations, at the
>>>>>>>>> high
>>>>>>>>> level I'm considering those don't matter...]
>>>>>>>>>
>>>>>>>>> My question was whether /those/ two specific calls to DebugTrace
>>>>>>>>> returns the same RC.
>>>>>>>>>
>>>>>>>>> Mike.
>>>>>>>>>
>>>>>>>>
>>>>>>>> As Ben has very carefully elaborated twice the invocation of a
>>>>>>>> function
>>>>>>>> with the same input must result in the same output. The return
>>>>>>>> value
>>>>>>>> from H_Hat() and the return value from H() are the same return
>>>>>>>> value.
>>>>>>>
>>>>>>> Hopefully this is a typo - I asked about return codes from
>>>>>>> DebugTrace,
>>>>>>
>>>>>> The return value from DebugTrace() is the same for H() and H_Hat().
>>>>>>
>>>>>>> not from H or H_Hat. H^ in the Linz proof is not a decider of
>>>>>>> anything, so output from H^ is irrelevant; all that matters is
>>>>>>> whether
>>>>>>> it halts.
>>>>>>>
>>>>>>
>>>>>>> I'll take it that you mean:
>>>>>>>
>>>>>>> "The calls to DebugTrace() in the two contexts you've
>>>>>>> described both return the same return code"
>>>>>>>
>>>>>>
>>>>>> Yes.
>>>>>>
>>>>> [... snip ...]
>>>>>
>>>>>>> OK, so you say the calls to DebugTrace() in Context (1) and (2)
>>>>>>> return
>>>>>>> the same result. There are just two possibilities:
>>>>>>>
>>>>>>> *Both DebugTrace() RCs are zero* :
>>>>>>>
>>>>>>> In Context (1) this indicates that H will decide that
>>>>>>> calculation H_Hat (H_Hat) halts. (MOV_EAX_1; HALT; will
>>>>>>> be executed.)
>>>>>>>
>>>>>>> In Context (2) this means that the H_Hat code will take
>>>>>>> the branch containing HERE: goto HERE;, and so H_Hat will
>>>>>>> loop at this point.
>>>>>>>
>>>>>>> So H clearly made the wrong halt decision for the calculation.
>>>>>>> OK, so
>>>>>>> the other possibility is...
>>>>>>>
>>>>>>> *Both DebugTrace() RCs are non-zero* :
>>>>>>>
>>>>>>> In Context (1) this indicates that H will decide that
>>>>>>> calculation H_Hat (H_Hat) does not halt. (MOV_EAX_0; HALT; will
>>>>>>> be executed.)
>>>>>>>
>>>>>>> In Context (2) this means that the H_Hat code will take
>>>>>>> the branch containing MOV_EAX_0; HALT;, and so H_Hat(H_Hat)
>>>>>>> will halt at this point.
>>>>>>>
>>>>>>> Again H has made the wrong decision for the calculation.
>>>>>>>
>>>>>>
>>>>>> No you have this incorrectly.
>>>>>
>>>>> You say that I have this incorrectly, without giving any indication of
>>>>> what you think is incorrect. That looks like being deliberately
>>>>> unhelpful!
>>>>
>>>> Carefully study my words immediately below again and again until you
>>>> fully understand exactly how I transformed a question subject to
>>>> pathological self-reference into a question that is not subject to
>>>> pathological self-reference thus eliminating the impossibility of
>>>> solving the halting problem.
>>>
>>> You forgot to answer the question! Here it is again:
>>>
>>> Will both the DebugTrace() return codes be ZERO, or will they be
>>> NON-ZERO? (You previously agreed they would be the same...)
>>>
>>> Mike.
>>
>> That question will only be answered by fully operational code.
>>
>
> That's what I expected you to say. It won't make the slightest
> difference to how your work is received if you answer now or in a few
> weeks, but it's your choice.
>
>> The key proof has already been provided.
>
> ?!
>
> All you've provided so far is: a) the skeleton C code, which clearly is
> going to support the Linz proof, if what you've said about how
> DebugTrace() behaves is true; and b) what you've said below about
> changing the question, which makes no difference to anything at all.
>
The difference is that it is no longer possible for H_Hat() to do the
opposite of what H() decides. This transforms an undecidable problem
into a decidable problem.
> Have I missed an actual proof of something? The Usenet server I use
> (Giganews) does that from time to time - it has a bug in its "add new
> message to database" logic where certain updates are not atomic (w.r.t
> client enquiries) when they should be.
>
> (Or is your "changing the question" supposed to be some kind of proof?)
By changing the question H_Hat() can no longer do the opposite of what
H() decides making an undecidable problem into a decidable problem.
>
>> No matter what return value
>> that DebugTrace() provides if it is always answering the question:
>>
>> Was your input aborted because it would not otherwise halt?
>> The halting problem becomes decidable.
>>
>
> Sorry, but that's nonsense. Oh well, guess we'll just have to wait and
> see the full code.
>
> Mike.
>
The full code will not be provided until you (and others) understand how
I already proved my point.
By searching the comp.theory forum for "olcott" (11,415 messages from
me) it can be verified that it took me about 12,000 hours since 2004 to
come up with this simple "change the question" refutation.
In the mean time I will complete the code that uses a key detail about
the halting problem that no one ever noticed for 80 years to correctly
decide the halting of H_Hat().
I already showed THAT the halting problem is decidable.
Next I will show HOW the conventional self-referential halting problem
counter examples are decided.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-22 11:05 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87mu0ebmon.fsf@bsb.me.uk> |
| In reply to | #24099 |
olcott <NoOne@NoWhere.com> writes: > By changing the question H_Hat() can no longer do the opposite of what > H() decides making an undecidable problem into a decidable problem. and from a side thread: | When we make the single change that I suggest the halting problem | ceases to be impossible to solve because this revised question is not | subject to pathological self-reference. This makes it all the more important that you post what you had two years ago. What you had back then "is exactly and precisely the Peter Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis of Ĥ actually deciding itself." (Dec 2018) directly addresses Linz's proof. If you post the pair that are exactly and precisely the Peter Linz H and Ĥ, the argument over having "changed the question" will become side issues. Of course, this is a problem for you if you have been lying about the claim that "H and Ĥ are 100% fully encoded as actual Turing machines" (Dec 2018) You can silence all your critics simply by posting these fully encoded actual Turing machines. You do have those two fully encoded actual Turing machines, don't you? > The full code will not be provided until you (and others) understand > how I already proved my point. The original is much more interesting because it addresses Linz's proof directly. There is going to be a lot of disappointment with the code that addresses your modified question, whereas the original code would be a revelation. You do have these two fully encoded actual Turing machines, don't you? You are not the sort of person to have been lying about that for months are you? -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 09:44 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <hPudnQ4e2tUkBwzCnZ2dnUU7-RudnZ2d@giganews.com> |
| In reply to | #24100 |
On 10/22/2020 5:05 AM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> By changing the question H_Hat() can no longer do the opposite of what >> H() decides making an undecidable problem into a decidable problem. > > and from a side thread: > > | When we make the single change that I suggest the halting problem > | ceases to be impossible to solve because this revised question is not > | subject to pathological self-reference. > > This makes it all the more important that you post what you had two > years ago. What you had back then > > "is exactly and precisely the Peter Linz H and Ĥ, with H actually > deciding input pair: (Ĥ, Ĥ) on the basis of Ĥ actually deciding > itself." (Dec 2018) > > directly addresses Linz's proof. If you post the pair that are exactly > and precisely the Peter Linz H and Ĥ, the argument over having "changed > the question" will become side issues. > > Of course, this is a problem for you if you have been lying about the > claim that > > "H and Ĥ are 100% fully encoded as actual Turing machines" (Dec 2018) > > You can silence all your critics simply by posting these fully encoded > actual Turing machines. You do have those two fully encoded actual > Turing machines, don't you? > >> The full code will not be provided until you (and others) understand >> how I already proved my point. > > The original is much more interesting because it addresses Linz's proof > directly. There is going to be a lot of disappointment with the code > that addresses your modified question, whereas the original code would > be a revelation. > > You do have these two fully encoded actual Turing machines, don't you? > You are not the sort of person to have been lying about that for months > are you? > I have already refuted the conventional self-referential halting problem proofs. You are clearly smart enough to see this yet far too biased to say this. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-22 16:14 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87tuum9ttn.fsf@bsb.me.uk> |
| In reply to | #24106 |
olcott <NoOne@NoWhere.com> writes: > On 10/22/2020 5:05 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> By changing the question H_Hat() can no longer do the opposite of what >>> H() decides making an undecidable problem into a decidable problem. >> >> and from a side thread: >> >> | When we make the single change that I suggest the halting problem >> | ceases to be impossible to solve because this revised question is not >> | subject to pathological self-reference. >> >> This makes it all the more important that you post what you had two >> years ago. What you had back then >> >> "is exactly and precisely the Peter Linz H and Ĥ, with H actually >> deciding input pair: (Ĥ, Ĥ) on the basis of Ĥ actually deciding >> itself." (Dec 2018) >> >> directly addresses Linz's proof. If you post the pair that are exactly >> and precisely the Peter Linz H and Ĥ, the argument over having "changed >> the question" will become side issues. >> >> Of course, this is a problem for you if you have been lying about the >> claim that >> >> "H and Ĥ are 100% fully encoded as actual Turing machines" (Dec 2018) >> >> You can silence all your critics simply by posting these fully encoded >> actual Turing machines. You do have those two fully encoded actual >> Turing machines, don't you? You won't answer, will you? You don't like to lie, and you'd have to lie again or admit you were wrong, so all you can do is ignore the question. >>> The full code will not be provided until you (and others) understand >>> how I already proved my point. >> >> The original is much more interesting because it addresses Linz's proof >> directly. There is going to be a lot of disappointment with the code >> that addresses your modified question, whereas the original code would >> be a revelation. >> >> You do have these two fully encoded actual Turing machines, don't you? >> You are not the sort of person to have been lying about that for months >> are you? No answer. See above. > I have already refuted the conventional self-referential halting > problem proofs. You are clearly smart enough to see this yet far too > biased to say this. Deflection. You said you had two Turing machines, related exactly as in Linz, two years ago but you can't post them can you? And you can't bring yourself to answer the simplest question: do have those two fully encoded actual Turing machines? You can't answer it because you don't want to lying again, but admitting you are wrong is almost impossible for you. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-22 08:00 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <VvekH.299966$r25.235063@fx08.iad> |
| In reply to | #24099 |
On 10/22/20 12:33 AM, olcott wrote: > > The difference is that it is no longer possible for H_Hat() to do the > opposite of what H() decides. This transforms an undecidable problem > into a decidable problem. If H_Hat no longer does what the proof defined, then your demonstration is no longer applicable to the proof. One possible counter might be showing that the steps that Linz did to make H_Hat aren't allowed by the definition of Turning Machines, but they clearly are, being a fairly simple augmentation to the state table of H. Showing that some thing you call "H_Hat" doesn't contradict something you call "H", which doesn't do what H is required to do proves absolutely nothing. At best it provides some evidence that the creation of a universal halt detector is in fact impossible, because you are going to such off-beat arguments that it is possible.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 09:36 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <ENSdnbrsnaxjBQzCnZ2dnUU7-UHNnZ2d@giganews.com> |
| In reply to | #24101 |
On 10/22/2020 7:00 AM, Richard Damon wrote: > On 10/22/20 12:33 AM, olcott wrote: >> >> The difference is that it is no longer possible for H_Hat() to do the >> opposite of what H() decides. This transforms an undecidable problem >> into a decidable problem. > > If H_Hat no longer does what the proof defined, then your demonstration > is no longer applicable to the proof. > If the halt decider is to report whether or not its input halts another program can be constructed on the the basis of this halt decider that does the opposite of whatever the halt decider decides. This is how H() and H_Hat() are defined in the Linz proof. If the halt decider is to report whether or not it aborted its input program because its input program would otherwise cause the halt decider to get stuck in infinite execution then this other program can no longer fool its halt decider and do the opposite of whatever it decides. If H() aborts the execution of H_Hat() then H_Hat() cannot continue to execute because H() has complete control over H_Hat. The end result of this slight change is that the halting problem can no longer be shown to be undecidable. > One possible counter might be showing that the steps that Linz did to > make H_Hat aren't allowed by the definition of Turning Machines, but > they clearly are, being a fairly simple augmentation to the state table > of H. > > Showing that some thing you call "H_Hat" doesn't contradict something > you call "H", which doesn't do what H is required to do proves > absolutely nothing. At best it provides some evidence that the creation > of a universal halt detector is in fact impossible, because you are > going to such off-beat arguments that it is possible. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-22 15:57 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87zh4e9uls.fsf@bsb.me.uk> |
| In reply to | #24104 |
olcott <NoOne@NoWhere.com> writes: > On 10/22/2020 7:00 AM, Richard Damon wrote: >> On 10/22/20 12:33 AM, olcott wrote: >>> >>> The difference is that it is no longer possible for H_Hat() to do the >>> opposite of what H() decides. This transforms an undecidable problem >>> into a decidable problem. >> >> If H_Hat no longer does what the proof defined, then your demonstration >> is no longer applicable to the proof. > > If the halt decider is to report whether or not its input halts > another program can be constructed on the the basis of this halt > decider that does the opposite of whatever the halt decider decides. > > This is how H() and H_Hat() are defined in the Linz proof. Yes, and this is what you have been claiming to have had for nearly two years and everyone else has been saying is impossible. Do you now accept that it is impossible and that you were wrong to say you had such a pair? > If the halt decider is to report whether or not it aborted its input > program because its input program would otherwise cause the halt > decider to get stuck in infinite execution then this other program can > no longer fool its halt decider and do the opposite of whatever it > decides. > > If H() aborts the execution of H_Hat() then H_Hat() cannot continue to > execute because H() has complete control over H_Hat. > > The end result of this slight change is that the halting problem can > no longer be shown to be undecidable. Unfortunately, pairs like this -- where H and H^ are not related exactly as in Linz, or where they are but H gets the answer wrong -- are ten-a-penny. What you wasted everyone's time with was a clear claim to have a pair, H and H^, related exactly as in Linz, where H gives the correct halting answer for H(H^, H^). Do you now see that such a pair is impossible? -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 10:44 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <vu2dnQ0pFuZYNQzCnZ2dnUU7-LnNnZ2d@giganews.com> |
| In reply to | #24107 |
On 10/22/2020 9:57 AM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>
>>>> The difference is that it is no longer possible for H_Hat() to do the
>>>> opposite of what H() decides. This transforms an undecidable problem
>>>> into a decidable problem.
>>>
>>> If H_Hat no longer does what the proof defined, then your demonstration
>>> is no longer applicable to the proof.
>>
>> If the halt decider is to report whether or not its input halts
>> another program can be constructed on the the basis of this halt
>> decider that does the opposite of whatever the halt decider decides.
>>
>> This is how H() and H_Hat() are defined in the Linz proof.
>
> Yes, and this is what you have been claiming to have had for nearly two
> years and everyone else has been saying is impossible. Do you now
> accept that it is impossible and that you were wrong to say you had such
> a pair?
>
>> If the halt decider is to report whether or not it aborted its input
>> program because its input program would otherwise cause the halt
>> decider to get stuck in infinite execution then this other program can
>> no longer fool its halt decider and do the opposite of whatever it
>> decides.
>>
>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to
>> execute because H() has complete control over H_Hat.
>>
>> The end result of this slight change is that the halting problem can
>> no longer be shown to be undecidable.
>
> Unfortunately, pairs like this -- where H and H^ are not related exactly
> as in Linz, or where they are but H gets the answer wrong -- are
> ten-a-penny. What you wasted everyone's time with was a clear claim to
> have a pair, H and H^, related exactly as in Linz, where H gives the
> correct halting answer for H(H^, H^). Do you now see that such a pair
> is impossible?
>
I think that the problem is that you are not even glancing at what I say
before you form your baseless rebuttal.
I have already proven that the H() to H_Hat() relationship is the same
as the conventional self-referential halting problem counter-example
relationship by providing its exact source code.
I adapted Mike's version of H_Hat(),
His comments regarding the halting decision were incorrect.
On 10/20/2020 8:57 PM, Mike Terry wrote:
> OK. I've added a valid implementation for H_Hat below.
> int H_Hat(u32 M)
> {
> int Abort = DebugTrace(M, M);
> if (Abort)
> {
> // DebugTrace says M(M) does not halt
> HALT // ..so we halt
> }
> else
> {
> // DebugTrace says M(M) halts
> for (;;); // ..so we loop
> }
> }
// M has address of H_Hat()
int H_Hat(u32 M)
{
int Abort = DebugTrace(M, M);
if (Abort)
{
MOV_EAX_0 // DebugTrace says that M(M)
HALT // has been aborted
}
else
{
MOV_EAX_1 // M(M) has halted
HERE: goto HERE;
HALT
}
}
The much more subtle nuance that cannot be understood by anyone that is
not an expert in this field and only then with very intense focused
concentration is that my simple change to the halting question converts
the halting problem from an undecidable problem into a decidable problem.
Did the input program have to be aborted to prevent the halt decider
from getting stuck in infinite execution?
Cannot be thwarted by pathological self-reference.
It is no longer impossible for a halt decider to divide all of its
inputs into (a) halting and (b) would not otherwise halt.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 00:34 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87imb196o6.fsf@bsb.me.uk> |
| In reply to | #24111 |
olcott <NoOne@NoWhere.com> writes:
> On 10/22/2020 9:57 AM, Ben Bacarisse wrote:
<cut>
>> Unfortunately, pairs like this -- where H and H^ are not related exactly
>> as in Linz, or where they are but H gets the answer wrong -- are
>> ten-a-penny. What you wasted everyone's time with was a clear claim to
>> have a pair, H and H^, related exactly as in Linz, where H gives the
>> correct halting answer for H(H^, H^). Do you now see that such a pair
>> is impossible?
>
> I think that the problem is that you are not even glancing at what I
> say before you form your baseless rebuttal.
I didn't rebut anything. Mike Terry is doing the rebutting (and doing
it very well I might add).
If you want someone else picking your claim apart, I am happy to join
in, but as you know I'm a nit-picking details guy. You won't get the
big-picture view of your mistakes that Mike Terry will give you.
> // M has address of H_Hat()
> int H_Hat(u32 M)
> {
> int Abort = DebugTrace(M, M);
> if (Abort)
> {
> MOV_EAX_0 // DebugTrace says that M(M)
> HALT // has been aborted
> }
> else
> {
> MOV_EAX_1 // M(M) has halted
> HERE: goto HERE;
> HALT
> }
> }
I'd start by saying that H_Hat neither includes nor makes reference to H
as Linz's H^ does. Yes, I know that H is just a thin shim over
DebugTrace but I am sure you want to get the details right.
Further questions: is DebugTrace vapourware or do you have it written
and running? It you have it running, can you run DebugTrace(H_Hat,
H_Hat) to get a return value? If not why not? If you can, what is the
return value?
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 18:55 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <tIadnb_W1fxuhg_CnZ2dnUU7-XXNnZ2d@giganews.com> |
| In reply to | #24166 |
On 10/22/2020 6:34 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 10/22/2020 9:57 AM, Ben Bacarisse wrote:
> <cut>
>>> Unfortunately, pairs like this -- where H and H^ are not related exactly
>>> as in Linz, or where they are but H gets the answer wrong -- are
>>> ten-a-penny. What you wasted everyone's time with was a clear claim to
>>> have a pair, H and H^, related exactly as in Linz, where H gives the
>>> correct halting answer for H(H^, H^). Do you now see that such a pair
>>> is impossible?
>>
>> I think that the problem is that you are not even glancing at what I
>> say before you form your baseless rebuttal.
>
> I didn't rebut anything. Mike Terry is doing the rebutting (and doing
> it very well I might add).
>
> If you want someone else picking your claim apart, I am happy to join
> in, but as you know I'm a nit-picking details guy. You won't get the
> big-picture view of your mistakes that Mike Terry will give you.
>
>> // M has address of H_Hat()
>> int H_Hat(u32 M)
>> {
>> int Abort = DebugTrace(M, M);
>> if (Abort)
>> {
>> MOV_EAX_0 // DebugTrace says that M(M)
>> HALT // has been aborted
>> }
>> else
>> {
>> MOV_EAX_1 // M(M) has halted
>> HERE: goto HERE;
>> HALT
>> }
>> }
>
> I'd start by saying that H_Hat neither includes nor makes reference to H
> as Linz's H^ does. Yes, I know that H is just a thin shim over
> DebugTrace but I am sure you want to get the details right.
>
Linz's H^ is defined as a sequence of two sets of modifications to his
H. DebugTrace() contains all of the ⊢* state transtions.
> Further questions: is DebugTrace vapourware or do you have it written
> and running?
The reason for the great delay is that I waited until I got DebugTrace()
fully operational before I presented H() and H_Hat().
> It you have it running, can you run DebugTrace(H_Hat,
> H_Hat) to get a return value? If not why not? If you can, what is the
> return value?
>
It took me a man-year to write my x86utm operating system. Now I finally
have the full basis to write the most robust halt deciding code.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 03:09 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87y2jx7kx4.fsf@bsb.me.uk> |
| In reply to | #24168 |
olcott <NoOne@NoWhere.com> writes:
> On 10/22/2020 6:34 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 10/22/2020 9:57 AM, Ben Bacarisse wrote:
>> <cut>
>>>> Unfortunately, pairs like this -- where H and H^ are not related exactly
>>>> as in Linz, or where they are but H gets the answer wrong -- are
>>>> ten-a-penny. What you wasted everyone's time with was a clear claim to
>>>> have a pair, H and H^, related exactly as in Linz, where H gives the
>>>> correct halting answer for H(H^, H^). Do you now see that such a pair
>>>> is impossible?
>>>
>>> I think that the problem is that you are not even glancing at what I
>>> say before you form your baseless rebuttal.
>>
>> I didn't rebut anything. Mike Terry is doing the rebutting (and doing
>> it very well I might add).
>>
>> If you want someone else picking your claim apart, I am happy to join
>> in, but as you know I'm a nit-picking details guy. You won't get the
>> big-picture view of your mistakes that Mike Terry will give you.
>>
>>> // M has address of H_Hat()
>>> int H_Hat(u32 M)
>>> {
>>> int Abort = DebugTrace(M, M);
>>> if (Abort)
>>> {
>>> MOV_EAX_0 // DebugTrace says that M(M)
>>> HALT // has been aborted
>>> }
>>> else
>>> {
>>> MOV_EAX_1 // M(M) has halted
>>> HERE: goto HERE;
>>> HALT
>>> }
>>> }
>>
>> I'd start by saying that H_Hat neither includes nor makes reference to H
>> as Linz's H^ does. Yes, I know that H is just a thin shim over
>> DebugTrace but I am sure you want to get the details right.
>
> Linz's H^ is defined as a sequence of two sets of modifications to his
> H.
Yup, and your H_Hat is not like that. It makes no reference to H at
all.
> DebugTrace() contains all of the ⊢* state transtions.
You don't know what that symbol means. You never have. In particular,
it has no meaning for x96 code. You are simply bullshitting.
Anyway, you don't plan to give H_Hat the same relationship to H as done
in Linz, right? But you will still want everyone else to pretend that
there is a direct correspondence, yes? I thought you'd prefer to get at
least this detail right, but apparently not.
>> Further questions: is DebugTrace vapourware or do you have it written
>> and running?
>
> The reason for the great delay is that I waited until I got
> DebugTrace() fully operational before I presented H() and H_Hat().
>
>> It you have it running, can you run DebugTrace(H_Hat,
>> H_Hat) to get a return value? If not why not? If you can, what is the
>> return value?
>
> It took me a man-year to write my x86utm operating system. Now I
> finally have the full basis to write the most robust halt deciding
> code.
Can you run DebugTrace(H_Hat, H_Hat) to get a return value?
If not why not?
If you can, what is the return value?
I'm wondering if spacing the questions out will help you see them.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 21:31 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <8vOdnfqKTbHs3Q_CnZ2dnUU7-efNnZ2d@giganews.com> |
| In reply to | #24181 |
On 10/22/2020 9:09 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 10/22/2020 6:34 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 10/22/2020 9:57 AM, Ben Bacarisse wrote:
>>> <cut>
>>>>> Unfortunately, pairs like this -- where H and H^ are not related exactly
>>>>> as in Linz, or where they are but H gets the answer wrong -- are
>>>>> ten-a-penny. What you wasted everyone's time with was a clear claim to
>>>>> have a pair, H and H^, related exactly as in Linz, where H gives the
>>>>> correct halting answer for H(H^, H^). Do you now see that such a pair
>>>>> is impossible?
>>>>
>>>> I think that the problem is that you are not even glancing at what I
>>>> say before you form your baseless rebuttal.
>>>
>>> I didn't rebut anything. Mike Terry is doing the rebutting (and doing
>>> it very well I might add).
>>>
>>> If you want someone else picking your claim apart, I am happy to join
>>> in, but as you know I'm a nit-picking details guy. You won't get the
>>> big-picture view of your mistakes that Mike Terry will give you.
>>>
>>>> // M has address of H_Hat()
>>>> int H_Hat(u32 M)
>>>> {
>>>> int Abort = DebugTrace(M, M);
>>>> if (Abort)
>>>> {
>>>> MOV_EAX_0 // DebugTrace says that M(M)
>>>> HALT // has been aborted
>>>> }
>>>> else
>>>> {
>>>> MOV_EAX_1 // M(M) has halted
>>>> HERE: goto HERE;
>>>> HALT
>>>> }
>>>> }
>>>
>>> I'd start by saying that H_Hat neither includes nor makes reference to H
>>> as Linz's H^ does. Yes, I know that H is just a thin shim over
>>> DebugTrace but I am sure you want to get the details right.
>>
>> Linz's H^ is defined as a sequence of two sets of modifications to his
>> H.
>
> Yup, and your H_Hat is not like that. It makes no reference to H at
> all.
>
>> DebugTrace() contains all of the ⊢* state transtions.
>
> You don't know what that symbol means. You never have. In particular,
> it has no meaning for x96 code. You are simply bullshitting.
>
> Anyway, you don't plan to give H_Hat the same relationship to H as done
> in Linz, right? But you will still want everyone else to pretend that
> there is a direct correspondence, yes? I thought you'd prefer to get at
> least this detail right, but apparently not.
>
>>> Further questions: is DebugTrace vapourware or do you have it written
>>> and running?
>>
>> The reason for the great delay is that I waited until I got
>> DebugTrace() fully operational before I presented H() and H_Hat().
>>
>>> It you have it running, can you run DebugTrace(H_Hat,
>>> H_Hat) to get a return value? If not why not? If you can, what is the
>>> return value?
>>
>> It took me a man-year to write my x86utm operating system. Now I
>> finally have the full basis to write the most robust halt deciding
>> code.
>
> Can you run DebugTrace(H_Hat, H_Hat) to get a return value?
I have already answered this question completely.
To force you to pay attention I do not provide yes or no answers to yes
or no questions. I provide full explanations from which the yes or no
answer can be derived.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 04:44 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87sga57git.fsf@bsb.me.uk> |
| In reply to | #24183 |
olcott <NoOne@NoWhere.com> writes: > On 10/22/2020 9:09 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> On 10/22/2020 6:34 PM, Ben Bacarisse wrote: <cut> >>>> Further questions: is DebugTrace vapourware or do you have it written >>>> and running? >>> >>> The reason for the great delay is that I waited until I got >>> DebugTrace() fully operational before I presented H() and H_Hat(). >>> >>>> It you have it running, can you run DebugTrace(H_Hat, >>>> H_Hat) to get a return value? If not why not? If you can, what is the >>>> return value? >>> >>> It took me a man-year to write my x86utm operating system. Now I >>> finally have the full basis to write the most robust halt deciding >>> code. >> >> Can you run DebugTrace(H_Hat, H_Hat) to get a return value? > > I have already answered this question completely. That's pure crank 101. People who want to be understood are happy to repeat an answer: "sorry, did you miss it? I said yes". You see? Clear and unambiguous. Cranks don't do that because they want as many get-out clauses left open as they can. So what is the returned result from DebugTrace(H_Hat, H_Hat)? > To force you to pay attention I do not provide yes or no answers to > yes or no questions. I provide full explanations from which the yes or > no answer can be derived. No, you do it to make lying less obvious. If, as I suspect will be the case, you can't give the returned value from DebugTrace(H_Hat, H_Hat) you can claim that having it "fully operational" was a theoretical claim, not a practical one and you never intended me to think you meant that you can actually run DebugTrace(H_Hat, H_Hat) to get a return value. Of course, sometimes, it's just your compulsion to re-word everything in your own terms. Maybe "fully operational" means what it appears to mean. Anyway, I prefer "yes" or "no" or "sorry, can you explain what you mean by returned result?". -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 23:13 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <z9Sdnc82b9PQxQ_CnZ2dnUU7-c_NnZ2d@giganews.com> |
| In reply to | #24185 |
On 10/22/2020 10:44 PM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> On 10/22/2020 9:09 PM, Ben Bacarisse wrote: >>> olcott <NoOne@NoWhere.com> writes: >>> >>>> On 10/22/2020 6:34 PM, Ben Bacarisse wrote: > <cut> >>>>> Further questions: is DebugTrace vapourware or do you have it written >>>>> and running? >>>> >>>> The reason for the great delay is that I waited until I got >>>> DebugTrace() fully operational before I presented H() and H_Hat(). >>>> >>>>> It you have it running, can you run DebugTrace(H_Hat, >>>>> H_Hat) to get a return value? If not why not? If you can, what is the >>>>> return value? >>>> >>>> It took me a man-year to write my x86utm operating system. Now I >>>> finally have the full basis to write the most robust halt deciding >>>> code. >>> >>> Can you run DebugTrace(H_Hat, H_Hat) to get a return value? >> >> I have already answered this question completely. > > That's pure crank 101. People who want to be understood are happy to > repeat an answer: "sorry, did you miss it? I said yes". You see? > Clear and unambiguous. Cranks don't do that because they want as many > get-out clauses left open as they can. > It is bad for me to have patience with people to to pay so little attention to what I am saying that after I have answered their question five times they did not bother to notice the answer even a single time. Your answer does not have a correct yes or no answer. I have run DebugTrace() and it did correctly return a value is a correct but misleading answer. > So what is the returned result from DebugTrace(H_Hat, H_Hat)? It is the fixed value of 1 that I used to test if it could correctly return a value. >> To force you to pay attention I do not provide yes or no answers to >> yes or no questions. I provide full explanations from which the yes or >> no answer can be derived. > > No, you do it to make lying less obvious. If, as I suspect will be the > case, you can't give the returned value from DebugTrace(H_Hat, H_Hat) > you can claim that having it "fully operational" was a theoretical > claim, not a practical one and you never intended me to think you meant > that you can actually run DebugTrace(H_Hat, H_Hat) to get a return > value. > This is the part that is completely done: It was the most difficult part of the x86utm operating system) DebugTrace() does correctly create separate processes and it executes them in DebugStep() mode. Most crucially it can execute functions in DebugStep() mode that execute DebugTrace() in DebugStep() mode to an arbitrary recursive depth. Each time DebugTrace() is executed it creates a whole brand new process with its own execution context. As a DebugTrace() system it is completely done. > Of course, sometimes, it's just your compulsion to re-word everything in > your own terms. Maybe "fully operational" means what it appears to > mean. Anyway, I prefer "yes" or "no" or "sorry, can you explain what > you mean by returned result?". > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 16:03 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87sga556ic.fsf@bsb.me.uk> |
| In reply to | #24189 |
olcott <NoOne@NoWhere.com> writes: > Your answer does not have a correct yes or no answer. s/answer/question/ > I have run DebugTrace() and it did correctly return a value is a > correct but misleading answer. > >> So what is the returned result from DebugTrace(H_Hat, H_Hat)? > > It is the fixed value of 1 that I used to test if it could correctly > return a value. I don't think you are taking this seriously. It's up to if you want to come across as a clown. If not, you can take the questions people ask seriously. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 10:40 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <ad-dnWVSSbz9ZA_CnZ2dnUU7-QXNnZ2d@giganews.com> |
| In reply to | #24208 |
On 10/23/2020 10:03 AM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> Your answer does not have a correct yes or no answer. > s/answer/question/ >> I have run DebugTrace() and it did correctly return a value is a >> correct but misleading answer. >> >>> So what is the returned result from DebugTrace(H_Hat, H_Hat)? >> >> It is the fixed value of 1 that I used to test if it could correctly >> return a value. > > I don't think you are taking this seriously. It's up to if you want to > come across as a clown. If not, you can take the questions people ask > seriously. > DebugTrace() is totally complete as a function that creates new process contexts and executes virtual machines within this new process context. The most difficult part was to get DebugTrace() to DebugTrace() itself to an arbitrary recursive depth. I had to do this because H() invokes DebugTrace() to invoke H_Hat() to invoke DebugTrace() to invoke another H_Hat() process. As I have said dozens of times now the halt decider code has not been written. The x86utm operating system is complete. This took one man-year. The halt deciding criteria for the Linz proof has been complete since 2016. We spoke about this at very great length and you made sure not to pay any attention at all. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
Page 2 of 25 — ← Prev page 1 [2] 3 4 … 25 Next page →
Back to top | Article view | comp.theory
csiph-web