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 23 of 25 — ← Prev page 1 … 21 22 [23] 24 25 Next page →
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 11:30 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <e9fbc06f-8a41-425d-8191-7d518db50f13n@googlegroups.com> |
| In reply to | #24141 |
On Thursday, 22 October 2020 at 19:22:06 UTC+1, olcott wrote: > On 10/22/2020 1:17 PM, Malcolm McLean wrote: > > On Thursday, 22 October 2020 at 19:12:30 UTC+1, Mr Flibble wrote: > >> olcott > >> > >>> I recommend that you earnestly try to actually understand what I am saying before providing any foolishly baseless attempts at rebuttal. > >> Rebut what exactly? You repeatedly refuse to give a straight answer to the questions that get to the heart of the matter. You have no refutation to rebut, dear. > >> > > You've attempted to rebut his refutation of Linz, and in my view failed. He doesn't need to describe how his halt > > detector works to refute Linz. > > When we change the question from "does this program halt?" to "does DebugTrace raise an abortion condition on > > this program because it would otherwise never terminate?" we don't change anything important, right? > > Or do we? > > > You are the only one that is getting it, congratulations! > I think that's going a bit far. There will be other people who understand exactly what you have done. But at least some posters are unable to provide a refutation of what you have achieved.So it isn't trivial.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 13:35 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <c9Odnf6S-OJ-TQzCnZ2dnUU7-SfNnZ2d@giganews.com> |
| In reply to | #24143 |
On 10/22/2020 1:30 PM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 19:22:06 UTC+1, olcott wrote: >> On 10/22/2020 1:17 PM, Malcolm McLean wrote: >>> On Thursday, 22 October 2020 at 19:12:30 UTC+1, Mr Flibble wrote: >>>> olcott >>>> >>>>> I recommend that you earnestly try to actually understand what I am saying before providing any foolishly baseless attempts at rebuttal. >>>> Rebut what exactly? You repeatedly refuse to give a straight answer to the questions that get to the heart of the matter. You have no refutation to rebut, dear. >>>> >>> You've attempted to rebut his refutation of Linz, and in my view failed. He doesn't need to describe how his halt >>> detector works to refute Linz. >>> When we change the question from "does this program halt?" to "does DebugTrace raise an abortion condition on >>> this program because it would otherwise never terminate?" we don't change anything important, right? >>> Or do we? >>> >> You are the only one that is getting it, congratulations! >> > I think that's going a bit far. There will be other people who understand exactly what you have done. "Will be", yes for sure, eventually. The first step of this "will be" is to drop the idea that I am certainly incorrect long enough to actually pay attention to what I am saying. > But at least some posters are unable to provide a refutation of what you have achieved.So it > isn't trivial. > Yes it looks like I am on the right track so far. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Jeff Barnett <jbb@notatt.com> |
|---|---|
| Date | 2020-10-22 11:59 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <rmsh9u$p3$1@dont-email.me> |
| In reply to | #24129 |
On 10/22/2020 11:35 AM, olcott wrote:
> On 10/22/2020 12:30 PM, Mr Flibble wrote:
>> On 22/10/2020 18:27, olcott wrote:
>>> On 10/22/2020 12:21 PM, Mr Flibble wrote:
>>>> On 22/10/2020 18:19, olcott wrote:
>>>>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>>>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM
>>>>>>>>>> that has
>>>>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>>>>
>>>>>>>>>> It is common knowledge that the RASP architecture is
>>>>>>>>>> equivalent to a
>>>>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>>>>> language is a
>>>>>>>>>> finite implementation of the Random Access Stored Program
>>>>>>>>>> (RASP) model.
>>>>>>>>>>
>>>>>>>>>> x86 UTM has these four key operating system functions
>>>>>>>>>> providing the
>>>>>>>>>> functionality to transform an x86 emulator into a finite
>>>>>>>>>> Universal
>>>>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>>>>
>>>>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>>>>> void SaveState(Registers* state);
>>>>>>>>>> void LoadState(Registers* state);
>>>>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>>>>
>>>>>>>>>> To make x86utm easy to use it directly executes the COFF
>>>>>>>>>> object file
>>>>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>>>>> works on
>>>>>>>>>> both Windows and Linux. It will also directly execute the
>>>>>>>>>> output of the
>>>>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>>>>> format. An
>>>>>>>>>> open source utility is provided for this purpose.
>>>>>>>>>>
>>>>>>>>>> x86utm is based on a very superb x86 emulator. The only change
>>>>>>>>>> the
>>>>>>>>>> needed to be made to the emulator was to very slightly adapt
>>>>>>>>>> it to
>>>>>>>>>> compile under windows and add the feature of disassembling an
>>>>>>>>>> object
>>>>>>>>>> file. All of the adaptations to transform this emulator into a
>>>>>>>>>> master
>>>>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>>>>
>>>>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and
>>>>>>>>>> H_Hat() to
>>>>>>>>>> correctly decide halting of H_Hat()
>>>>>>>>>>
>>>>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>>>>> terminates or
>>>>>>>>>> H() decides that H_Hat() would not otherwise terminate. In
>>>>>>>>>> this case H()
>>>>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>>>>
>>>>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>>>>> separate
>>>>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>>>>> To make things simple the halt deciding aspect of H() and
>>>>>>>>>> H_Hat() is the
>>>>>>>>>> same function. (see below)
>>>>>>>>>
>>>>>>>>> So what is this "the same function"? It looks like that
>>>>>>>>> function is DebugTrace(), right? (A better name might be
>>>>>>>>> Decide(), which expresses its role in the program, but no biggie.)
>>>>>>>>>
>>>>>>>>
>>>>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would
>>>>>>>> not otherwise terminate.
>>>>>>>>
>>>>>>>> At the first point that DebugTrace() determines that M(N) would
>>>>>>>> not otherwise terminate it aborts the DebugStep() of M(N).
>>>>>>>
>>>>>>> How does it determine that an unknown function will never terminate?
>>>>>>
>>>>>> Excellent question; in fact it is the ONLY question that matters
>>>>>> .. we await Olcott's answer... ;D
>>>>>>
>>>>>> /Flibble
>>>>>>
>>>>>
>>>>> The only question that matters more than any other question is
>>>>> whether or not changing the question from:
>>>>> (a) Does the program halt on its input?
>>>>> (b) Was the program aborted because non-halting behavior was detected?
>>>>>
>>>>> eliminates the undecidability of all of the conventional
>>>>> self-referential halting problem proof counter-examples?
>>>>>
>>>>> How the halt decider actually decides these conventional
>>>>> self-referential halting problem proof counter-examples is icing on
>>>>> the cake because its basis is a crucial detail about the halting
>>>>> problem counter-examples that no one (besides me) ever noticed for
>>>>> 80 years.
>>>>
>>>> hubris
>>>> /ˈhjuːbrɪs/
>>>>
>>>
>>> Ad hominem attacks are the first resort of clueless wonders.
>>
>> And you still haven't answered the question: how does it "detect" that
>> the unknown function never terminates, clueless WANKER?
>>
>> /Flibble
>>
>
> Unless what I have currently presented is sufficiently understood no one
> is paying enough attention to appreciate the next step of how halting is
> decided.
Alright. I conclude that you haven't paid enough attention to what you
said; but that's okay, it's gibberish. What is the real problem is you
haven't paid enough attention to what your betters have said.
See? I just agreed with you. Well I've agreed with what you said but
pointed the pronouns more accurately. I hope that doesn't mean we have
to justify the self reference in this case.
--
Jeff Barnett
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 10:45 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <18434c4c-4abb-4d80-bc18-6a33d32588c5n@googlegroups.com> |
| In reply to | #24126 |
On Thursday, 22 October 2020 at 18:30:33 UTC+1, Mr Flibble wrote: > > And you still haven't answered the question: how does it "detect" that the unknown function never terminates, clueless WANKER? > The claim is to have refuted the Linz proof that no universal halt detector is possible. Not to have a completely functional halt detector.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 13:13 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <RJWdnUl7GIFRVgzCnZ2dnUU7-IfNnZ2d@giganews.com> |
| In reply to | #24131 |
On 10/22/2020 12:45 PM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 18:30:33 UTC+1, Mr Flibble wrote: >> >> And you still haven't answered the question: how does it "detect" that the unknown function never terminates, clueless WANKER? >> > The claim is to have refuted the Linz proof that no universal halt detector is possible. Not to have a completely functional > halt detector. > The actual revised claim is that the Linz proof is correct based on its false assumption that the only way to define a universal halt decider is to create a program that answers the following question: Does the input program halt on its input? When-so-ever the halting problem question is stated as: Was the execution of the input program on its input aborted because non-halting behavior was detected? The undecidability of the halting problem has been refuted. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mr Flibble <flibbleREMOVETHISBIT@i42.co.uk> |
|---|---|
| Date | 2020-10-22 19:17 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <21kkH.112222$KL2.7359@fx21.am4> |
| In reply to | #24137 |
On 22/10/2020 19:13, olcott wrote: > On 10/22/2020 12:45 PM, Malcolm McLean wrote: >> On Thursday, 22 October 2020 at 18:30:33 UTC+1, Mr Flibble wrote: >>> >>> And you still haven't answered the question: how does it "detect" that the unknown function never terminates, clueless WANKER? >>> >> The claim is to have refuted the Linz proof that no universal halt detector is possible. Not to have a completely functional >> halt detector. >> > > The actual revised claim is that the Linz proof is correct based on its false assumption that the only way to define a universal halt decider is to create a program that answers the following question: > Does the input program halt on its input? > > When-so-ever the halting problem question is stated as: > Was the execution of the input program on its input aborted because non-halting behavior was detected? > > The undecidability of the halting problem has been refuted. You are now on automatic and are just restating the same thing without addressing the actual question. I can also restate things in a similar way: TROLL DETECTED. /Flibble -- ¬
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 13:24 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <386dnSiESaj1UwzCnZ2dnUU7-LMAAAAA@giganews.com> |
| In reply to | #24139 |
On 10/22/2020 1:17 PM, Mr Flibble wrote: > On 22/10/2020 19:13, olcott wrote: >> On 10/22/2020 12:45 PM, Malcolm McLean wrote: >>> On Thursday, 22 October 2020 at 18:30:33 UTC+1, Mr Flibble wrote: >>>> >>>> And you still haven't answered the question: how does it "detect" >>>> that the unknown function never terminates, clueless WANKER? >>>> >>> The claim is to have refuted the Linz proof that no universal halt >>> detector is possible. Not to have a completely functional >>> halt detector. >>> >> >> The actual revised claim is that the Linz proof is correct based on >> its false assumption that the only way to define a universal halt >> decider is to create a program that answers the following question: >> Does the input program halt on its input? >> >> When-so-ever the halting problem question is stated as: >> Was the execution of the input program on its input aborted because >> non-halting behavior was detected? >> >> The undecidability of the halting problem has been refuted. > > You are now on automatic and are just restating the same thing without > addressing the actual question. On 10/22/2020 1:17 PM, Malcolm McLean wrote: > He doesn't need to describe how his halt detector works to > refute Linz. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 19:40 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <PO-dnaNT6rUZuw_CnZ2dnUU7-L_NnZ2d@giganews.com> |
| In reply to | #24121 |
On 10/22/2020 7:21 PM, Chris M. Thomasson wrote:
> On 10/22/2020 10:19 AM, olcott wrote:
>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM that
>>>>>>> has
>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>
>>>>>>> It is common knowledge that the RASP architecture is equivalent to a
>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>> language is a
>>>>>>> finite implementation of the Random Access Stored Program (RASP)
>>>>>>> model.
>>>>>>>
>>>>>>> x86 UTM has these four key operating system functions providing the
>>>>>>> functionality to transform an x86 emulator into a finite Universal
>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>
>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>> void SaveState(Registers* state);
>>>>>>> void LoadState(Registers* state);
>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>
>>>>>>> To make x86utm easy to use it directly executes the COFF object file
>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>> works on
>>>>>>> both Windows and Linux. It will also directly execute the output
>>>>>>> of the
>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>> format. An
>>>>>>> open source utility is provided for this purpose.
>>>>>>>
>>>>>>> x86utm is based on a very superb x86 emulator. The only change the
>>>>>>> needed to be made to the emulator was to very slightly adapt it to
>>>>>>> compile under windows and add the feature of disassembling an object
>>>>>>> file. All of the adaptations to transform this emulator into a
>>>>>>> master
>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>
>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and H_Hat() to
>>>>>>> correctly decide halting of H_Hat()
>>>>>>>
>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>> terminates or
>>>>>>> H() decides that H_Hat() would not otherwise terminate. In this
>>>>>>> case H()
>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>
>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>> separate
>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>> To make things simple the halt deciding aspect of H() and H_Hat()
>>>>>>> is the
>>>>>>> same function. (see below)
>>>>>>
>>>>>> So what is this "the same function"? It looks like that function
>>>>>> is DebugTrace(), right? (A better name might be Decide(), which
>>>>>> expresses its role in the program, but no biggie.)
>>>>>>
>>>>>
>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would not
>>>>> otherwise terminate.
>>>>>
>>>>> At the first point that DebugTrace() determines that M(N) would not
>>>>> otherwise terminate it aborts the DebugStep() of M(N).
>>>>
>>>> How does it determine that an unknown function will never terminate?
>>>
>>> Excellent question; in fact it is the ONLY question that matters ..
>>> we await Olcott's answer... ;D
>>>
>>> /Flibble
>>>
>>
>> The only question that matters more than any other question is whether
>> or not changing the question from:
>> (a) Does the program halt on its input?
>> (b) Was the program aborted because non-halting behavior was detected?
>
> Wait a minute... How is non-halting behavior detected in an unknown
> function?
As has already been pointed out this does not make any difference.
In the original definition of the halt decider:
H() decides Halts so H_Hat Loops
H() decides Loops so H_Hat Halts
In the revised definition of the halt decider:
H() decides Aborted so H_Hat has already ceased to exist.
H() decides ~Aborted so H_Hat is allowed to execute to completion.
There are no longer any halting problem cases that can be shown to be
undecidable with the revised definition of the halt decider
> Lets say an unknown function has been running for 100 years,
> and still going strong... Would you say it has non-halting behavior? The
> function could be programmed to self terminate after 409 years... If you
> said it is non-halting, well, you would be 100% wrong!
>
> Although, you "might" be right because the unknown function just might
> be programmed to run for infinity. It never terminates. So, would your
> decider have to run infinitely long to tell if the unknown function
> never terminates? ;^)
The key case of correctly deciding the Linz H_hat() Bottom of page 319
http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf
Is very easy to decide because of a key detail about the halting problem
proofs that no one noticed for 80 years.
>>
>> eliminates the undecidability of all of the conventional
>> self-referential halting problem proof counter-examples?
>>
>> How the halt decider actually decides these conventional
>> self-referential halting problem proof counter-examples is icing on
>> the cake because its basis is a crucial detail about the halting
>> problem counter-examples that no one (besides me) ever noticed for 80
>> years.
>>
>>
>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2020-10-22 17:44 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <rmt913$fut$2@gioia.aioe.org> |
| In reply to | #24172 |
On 10/22/2020 5:40 PM, olcott wrote:
> On 10/22/2020 7:21 PM, Chris M. Thomasson wrote:
>> On 10/22/2020 10:19 AM, olcott wrote:
>>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM
>>>>>>>> that has
>>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>>
>>>>>>>> It is common knowledge that the RASP architecture is equivalent
>>>>>>>> to a
>>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>>> language is a
>>>>>>>> finite implementation of the Random Access Stored Program (RASP)
>>>>>>>> model.
>>>>>>>>
>>>>>>>> x86 UTM has these four key operating system functions providing the
>>>>>>>> functionality to transform an x86 emulator into a finite Universal
>>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>>
>>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>>> void SaveState(Registers* state);
>>>>>>>> void LoadState(Registers* state);
>>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>>
>>>>>>>> To make x86utm easy to use it directly executes the COFF object
>>>>>>>> file
>>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>>> works on
>>>>>>>> both Windows and Linux. It will also directly execute the output
>>>>>>>> of the
>>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>>> format. An
>>>>>>>> open source utility is provided for this purpose.
>>>>>>>>
>>>>>>>> x86utm is based on a very superb x86 emulator. The only change the
>>>>>>>> needed to be made to the emulator was to very slightly adapt it to
>>>>>>>> compile under windows and add the feature of disassembling an
>>>>>>>> object
>>>>>>>> file. All of the adaptations to transform this emulator into a
>>>>>>>> master
>>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>>
>>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and H_Hat() to
>>>>>>>> correctly decide halting of H_Hat()
>>>>>>>>
>>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>>> terminates or
>>>>>>>> H() decides that H_Hat() would not otherwise terminate. In this
>>>>>>>> case H()
>>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>>
>>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>>> separate
>>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>>> To make things simple the halt deciding aspect of H() and
>>>>>>>> H_Hat() is the
>>>>>>>> same function. (see below)
>>>>>>>
>>>>>>> So what is this "the same function"? It looks like that function
>>>>>>> is DebugTrace(), right? (A better name might be Decide(), which
>>>>>>> expresses its role in the program, but no biggie.)
>>>>>>>
>>>>>>
>>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would not
>>>>>> otherwise terminate.
>>>>>>
>>>>>> At the first point that DebugTrace() determines that M(N) would
>>>>>> not otherwise terminate it aborts the DebugStep() of M(N).
>>>>>
>>>>> How does it determine that an unknown function will never terminate?
>>>>
>>>> Excellent question; in fact it is the ONLY question that matters ..
>>>> we await Olcott's answer... ;D
>>>>
>>>> /Flibble
>>>>
>>>
>>> The only question that matters more than any other question is
>>> whether or not changing the question from:
>>> (a) Does the program halt on its input?
>>> (b) Was the program aborted because non-halting behavior was detected?
>>
>> Wait a minute... How is non-halting behavior detected in an unknown
>> function?
>
> As has already been pointed out this does not make any difference.
>
> In the original definition of the halt decider:
> H() decides Halts so H_Hat Loops
> H() decides Loops so H_Hat Halts
>
> In the revised definition of the halt decider:
> H() decides Aborted so H_Hat has already ceased to exist.
> H() decides ~Aborted so H_Hat is allowed to execute to completion.
What happens if the unknown function never completes because it runs
forever?
>
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 19:49 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <eZadncyqE7wotQ_CnZ2dnUU7-SPNnZ2d@giganews.com> |
| In reply to | #24173 |
On 10/22/2020 7:44 PM, Chris M. Thomasson wrote:
> On 10/22/2020 5:40 PM, olcott wrote:
>> On 10/22/2020 7:21 PM, Chris M. Thomasson wrote:
>>> On 10/22/2020 10:19 AM, olcott wrote:
>>>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM
>>>>>>>>> that has
>>>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>>>
>>>>>>>>> It is common knowledge that the RASP architecture is equivalent
>>>>>>>>> to a
>>>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>>>> language is a
>>>>>>>>> finite implementation of the Random Access Stored Program
>>>>>>>>> (RASP) model.
>>>>>>>>>
>>>>>>>>> x86 UTM has these four key operating system functions providing
>>>>>>>>> the
>>>>>>>>> functionality to transform an x86 emulator into a finite Universal
>>>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>>>
>>>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>>>> void SaveState(Registers* state);
>>>>>>>>> void LoadState(Registers* state);
>>>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>>>
>>>>>>>>> To make x86utm easy to use it directly executes the COFF object
>>>>>>>>> file
>>>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>>>> works on
>>>>>>>>> both Windows and Linux. It will also directly execute the
>>>>>>>>> output of the
>>>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>>>> format. An
>>>>>>>>> open source utility is provided for this purpose.
>>>>>>>>>
>>>>>>>>> x86utm is based on a very superb x86 emulator. The only change the
>>>>>>>>> needed to be made to the emulator was to very slightly adapt it to
>>>>>>>>> compile under windows and add the feature of disassembling an
>>>>>>>>> object
>>>>>>>>> file. All of the adaptations to transform this emulator into a
>>>>>>>>> master
>>>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>>>
>>>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and H_Hat() to
>>>>>>>>> correctly decide halting of H_Hat()
>>>>>>>>>
>>>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>>>> terminates or
>>>>>>>>> H() decides that H_Hat() would not otherwise terminate. In this
>>>>>>>>> case H()
>>>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>>>
>>>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>>>> separate
>>>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>>>> To make things simple the halt deciding aspect of H() and
>>>>>>>>> H_Hat() is the
>>>>>>>>> same function. (see below)
>>>>>>>>
>>>>>>>> So what is this "the same function"? It looks like that
>>>>>>>> function is DebugTrace(), right? (A better name might be
>>>>>>>> Decide(), which expresses its role in the program, but no biggie.)
>>>>>>>>
>>>>>>>
>>>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would
>>>>>>> not otherwise terminate.
>>>>>>>
>>>>>>> At the first point that DebugTrace() determines that M(N) would
>>>>>>> not otherwise terminate it aborts the DebugStep() of M(N).
>>>>>>
>>>>>> How does it determine that an unknown function will never terminate?
>>>>>
>>>>> Excellent question; in fact it is the ONLY question that matters ..
>>>>> we await Olcott's answer... ;D
>>>>>
>>>>> /Flibble
>>>>>
>>>>
>>>> The only question that matters more than any other question is
>>>> whether or not changing the question from:
>>>> (a) Does the program halt on its input?
>>>> (b) Was the program aborted because non-halting behavior was detected?
>>>
>>> Wait a minute... How is non-halting behavior detected in an unknown
>>> function?
>>
>> As has already been pointed out this does not make any difference.
>>
>> In the original definition of the halt decider:
>> H() decides Halts so H_Hat Loops
>> H() decides Loops so H_Hat Halts
>>
>> In the revised definition of the halt decider:
>> H() decides Aborted so H_Hat has already ceased to exist.
>> H() decides ~Aborted so H_Hat is allowed to execute to completion.
>
> What happens if the unknown function never completes because it runs
> forever?
There may be very complex cases that are very difficult to correctly
decide.
All that I have shown is that deciding the halting problem is no longer
impossible. By showing that deciding the halting problem is no longer
impossible I have refuted all of the proofs of its impossibility.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2020-10-22 17:59 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <rmt9sq$o6k$1@gioia.aioe.org> |
| In reply to | #24174 |
On 10/22/2020 5:49 PM, olcott wrote:
> On 10/22/2020 7:44 PM, Chris M. Thomasson wrote:
>> On 10/22/2020 5:40 PM, olcott wrote:
>>> On 10/22/2020 7:21 PM, Chris M. Thomasson wrote:
>>>> On 10/22/2020 10:19 AM, olcott wrote:
>>>>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>>>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM
>>>>>>>>>> that has
>>>>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>>>>
>>>>>>>>>> It is common knowledge that the RASP architecture is
>>>>>>>>>> equivalent to a
>>>>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>>>>> language is a
>>>>>>>>>> finite implementation of the Random Access Stored Program
>>>>>>>>>> (RASP) model.
>>>>>>>>>>
>>>>>>>>>> x86 UTM has these four key operating system functions
>>>>>>>>>> providing the
>>>>>>>>>> functionality to transform an x86 emulator into a finite
>>>>>>>>>> Universal
>>>>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>>>>
>>>>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>>>>> void SaveState(Registers* state);
>>>>>>>>>> void LoadState(Registers* state);
>>>>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>>>>
>>>>>>>>>> To make x86utm easy to use it directly executes the COFF
>>>>>>>>>> object file
>>>>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>>>>> works on
>>>>>>>>>> both Windows and Linux. It will also directly execute the
>>>>>>>>>> output of the
>>>>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>>>>> format. An
>>>>>>>>>> open source utility is provided for this purpose.
>>>>>>>>>>
>>>>>>>>>> x86utm is based on a very superb x86 emulator. The only change
>>>>>>>>>> the
>>>>>>>>>> needed to be made to the emulator was to very slightly adapt
>>>>>>>>>> it to
>>>>>>>>>> compile under windows and add the feature of disassembling an
>>>>>>>>>> object
>>>>>>>>>> file. All of the adaptations to transform this emulator into a
>>>>>>>>>> master
>>>>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>>>>
>>>>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and
>>>>>>>>>> H_Hat() to
>>>>>>>>>> correctly decide halting of H_Hat()
>>>>>>>>>>
>>>>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>>>>> terminates or
>>>>>>>>>> H() decides that H_Hat() would not otherwise terminate. In
>>>>>>>>>> this case H()
>>>>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>>>>
>>>>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>>>>> separate
>>>>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>>>>> To make things simple the halt deciding aspect of H() and
>>>>>>>>>> H_Hat() is the
>>>>>>>>>> same function. (see below)
>>>>>>>>>
>>>>>>>>> So what is this "the same function"? It looks like that
>>>>>>>>> function is DebugTrace(), right? (A better name might be
>>>>>>>>> Decide(), which expresses its role in the program, but no biggie.)
>>>>>>>>>
>>>>>>>>
>>>>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would
>>>>>>>> not otherwise terminate.
>>>>>>>>
>>>>>>>> At the first point that DebugTrace() determines that M(N) would
>>>>>>>> not otherwise terminate it aborts the DebugStep() of M(N).
>>>>>>>
>>>>>>> How does it determine that an unknown function will never terminate?
>>>>>>
>>>>>> Excellent question; in fact it is the ONLY question that matters
>>>>>> .. we await Olcott's answer... ;D
>>>>>>
>>>>>> /Flibble
>>>>>>
>>>>>
>>>>> The only question that matters more than any other question is
>>>>> whether or not changing the question from:
>>>>> (a) Does the program halt on its input?
>>>>> (b) Was the program aborted because non-halting behavior was detected?
>>>>
>>>> Wait a minute... How is non-halting behavior detected in an unknown
>>>> function?
>>>
>>> As has already been pointed out this does not make any difference.
>>>
>>> In the original definition of the halt decider:
>>> H() decides Halts so H_Hat Loops
>>> H() decides Loops so H_Hat Halts
>>>
>>> In the revised definition of the halt decider:
>>> H() decides Aborted so H_Hat has already ceased to exist.
>>> H() decides ~Aborted so H_Hat is allowed to execute to completion.
>>
>> What happens if the unknown function never completes because it runs
>> forever?
>
> There may be very complex cases that are very difficult to correctly
> decide.
Indeed. Well, especially if an unknown function never terminates. Or
just runs for 1000 years before terminating.
> All that I have shown is that deciding the halting problem is no longer
> impossible.
How?
> By showing that deciding the halting problem is no longer
> impossible I have refuted all of the proofs of its impossibility.
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 18:13 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <58c75e04-c935-4459-b9af-3b0acf809108n@googlegroups.com> |
| In reply to | #24175 |
On Friday, 23 October 2020 at 01:59:13 UTC+1, Chris M. Thomasson wrote: > On 10/22/2020 5:49 PM, olcott wrote: > > > > All that I have shown is that deciding the halting problem is no longer > > impossible. > How? > You simply write "exit(EXIT_FAILURE)" instead of "return 0" in your halt detector, and it is no longer equivalent to a Turing machine.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 20:15 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <wo6dnakfA_MFsw_CnZ2dnUU7-TvNnZ2d@giganews.com> |
| In reply to | #24175 |
On 10/22/2020 7:59 PM, Chris M. Thomasson wrote:
> On 10/22/2020 5:49 PM, olcott wrote:
>> On 10/22/2020 7:44 PM, Chris M. Thomasson wrote:
>>> On 10/22/2020 5:40 PM, olcott wrote:
>>>> On 10/22/2020 7:21 PM, Chris M. Thomasson wrote:
>>>>> On 10/22/2020 10:19 AM, olcott wrote:
>>>>>> On 10/22/2020 11:41 AM, Mr Flibble wrote:
>>>>>>> On 20/10/2020 22:26, Chris M. Thomasson wrote:
>>>>>>>> On 10/20/2020 11:40 AM, olcott wrote:
>>>>>>>>> On 10/20/2020 1:11 PM, Mike Terry wrote:
>>>>>>>>>> On 20/10/2020 17:33, olcott wrote:
>>>>>>>>>>> x86utm is as much as possible a Universal Turing Machine UTM
>>>>>>>>>>> that has
>>>>>>>>>>> the x86 language as its Turing Machine Description language.
>>>>>>>>>>>
>>>>>>>>>>> It is common knowledge that the RASP architecture is
>>>>>>>>>>> equivalent to a
>>>>>>>>>>> universal Turing machine. It is self-evident that the x86
>>>>>>>>>>> language is a
>>>>>>>>>>> finite implementation of the Random Access Stored Program
>>>>>>>>>>> (RASP) model.
>>>>>>>>>>>
>>>>>>>>>>> x86 UTM has these four key operating system functions
>>>>>>>>>>> providing the
>>>>>>>>>>> functionality to transform an x86 emulator into a finite
>>>>>>>>>>> Universal
>>>>>>>>>>> Turing Machine: (Source code will be provided)
>>>>>>>>>>>
>>>>>>>>>>> u32* Allocate(u32 size); // Allocate bytes of memory
>>>>>>>>>>> void SaveState(Registers* state);
>>>>>>>>>>> void LoadState(Registers* state);
>>>>>>>>>>> u32 DebugStep(Registers* master_state, Registers* slave_state);
>>>>>>>>>>>
>>>>>>>>>>> To make x86utm easy to use it directly executes the COFF
>>>>>>>>>>> object file
>>>>>>>>>>> output of the Microsoft C compiler. The entire x86UTM system
>>>>>>>>>>> works on
>>>>>>>>>>> both Windows and Linux. It will also directly execute the
>>>>>>>>>>> output of the
>>>>>>>>>>> GCC compiler when this output has been converted to the COFF
>>>>>>>>>>> format. An
>>>>>>>>>>> open source utility is provided for this purpose.
>>>>>>>>>>>
>>>>>>>>>>> x86utm is based on a very superb x86 emulator. The only
>>>>>>>>>>> change the
>>>>>>>>>>> needed to be made to the emulator was to very slightly adapt
>>>>>>>>>>> it to
>>>>>>>>>>> compile under windows and add the feature of disassembling an
>>>>>>>>>>> object
>>>>>>>>>>> file. All of the adaptations to transform this emulator into
>>>>>>>>>>> a master
>>>>>>>>>>> UTM are contained in a single C++ source file.
>>>>>>>>>>>
>>>>>>>>>>> Here is how x86UTM is applied to the Peter Linz H() and
>>>>>>>>>>> H_Hat() to
>>>>>>>>>>> correctly decide halting of H_Hat()
>>>>>>>>>>>
>>>>>>>>>>> H() continues to DebugStep() though H_Hat() until H_Hat()
>>>>>>>>>>> terminates or
>>>>>>>>>>> H() decides that H_Hat() would not otherwise terminate. In
>>>>>>>>>>> this case H()
>>>>>>>>>>> would stop executing H_Hat() and report Not_Halting behavior.
>>>>>>>>>>>
>>>>>>>>>>> H() executes H_Hat() as if H() was a UTM. H() and H_Hat() are
>>>>>>>>>>> separate
>>>>>>>>>>> processes having their own: {Memory, registers and stack}
>>>>>>>>>>> To make things simple the halt deciding aspect of H() and
>>>>>>>>>>> H_Hat() is the
>>>>>>>>>>> same function. (see below)
>>>>>>>>>>
>>>>>>>>>> So what is this "the same function"? It looks like that
>>>>>>>>>> function is DebugTrace(), right? (A better name might be
>>>>>>>>>> Decide(), which expresses its role in the program, but no
>>>>>>>>>> biggie.)
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Both H() and H_Hat() invoke the same DebugTrace() function.
>>>>>>>>> DebugTrace() continues a DebugStep() of M(N) unless M(N) would
>>>>>>>>> not otherwise terminate.
>>>>>>>>>
>>>>>>>>> At the first point that DebugTrace() determines that M(N) would
>>>>>>>>> not otherwise terminate it aborts the DebugStep() of M(N).
>>>>>>>>
>>>>>>>> How does it determine that an unknown function will never
>>>>>>>> terminate?
>>>>>>>
>>>>>>> Excellent question; in fact it is the ONLY question that matters
>>>>>>> .. we await Olcott's answer... ;D
>>>>>>>
>>>>>>> /Flibble
>>>>>>>
>>>>>>
>>>>>> The only question that matters more than any other question is
>>>>>> whether or not changing the question from:
>>>>>> (a) Does the program halt on its input?
>>>>>> (b) Was the program aborted because non-halting behavior was
>>>>>> detected?
>>>>>
>>>>> Wait a minute... How is non-halting behavior detected in an unknown
>>>>> function?
>>>>
>>>> As has already been pointed out this does not make any difference.
>>>>
>>>> In the original definition of the halt decider:
>>>> H() decides Halts so H_Hat Loops
>>>> H() decides Loops so H_Hat Halts
>>>>
>>>> In the revised definition of the halt decider:
>>>> H() decides Aborted so H_Hat has already ceased to exist.
>>>> H() decides ~Aborted so H_Hat is allowed to execute to completion.
>>>
>>> What happens if the unknown function never completes because it runs
>>> forever?
>>
>> There may be very complex cases that are very difficult to correctly
>> decide.
>
> Indeed. Well, especially if an unknown function never terminates. Or
> just runs for 1000 years before terminating.
The halting problem has never been about an unknown function.
A halt decider is not required to be psychic.
>
>
>> All that I have shown is that deciding the halting problem is no
>> longer impossible.
>
> How?
>
The way that the halting problem works is another program that is
exactly like that halt decider is slightly changed so that it does the
opposite of whatever the halt decider decides.
If the halt decide decides that it will halt it loops.
If the halt decider decides that it loops it halts.
I changed this so that the halt decider executes its input program in
DebugStep() mode until it decides that its input would not halt.
Then it aborts the execution of its input. Once the execution of the
input program has been aborted it can't do anything at all. If it can't
do anything at all then it can't do the opposite of whatever the halt
decider decides.
The aborted input is the programs would never halt unless they are aborted.
>
>> By showing that deciding the halting problem is no longer impossible I
>> have refuted all of the proofs of its impossibility.
>
>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-23 00:10 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <SIskH.675846$AN2.152360@fx46.iad> |
| In reply to | #24178 |
On 10/22/20 9:15 PM, olcott wrote: > > The halting problem has never been about an unknown function. > A halt decider is not required to be psychic. The USEFULNESS of a halting detector, is for cases where you have an problem, with an algorithm, which can be expressed as a Turing Machine, whose calculation is not know whether it will eventally terminate, and thus provide a proof of existence for something, or loop forever, and prove the non-existence of that thing. If we could make this halt decider, we could by running the halt decider on the algorithm instead of just trying to run the algorithm, and thus get the answer of a proof the existence or non-existence of that result. The inability to do this, thus becomes related to the incompleteness theory, where it seems that, at least for sufficient expressive system, that there are some properties that we can not proof whether they are true or not.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 23:28 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <2dmdnQlzpdRwxg_CnZ2dnUU7-XHNnZ2d@giganews.com> |
| In reply to | #24188 |
On 10/22/2020 11:10 PM, Richard Damon wrote: > On 10/22/20 9:15 PM, olcott wrote: >> >> The halting problem has never been about an unknown function. >> A halt decider is not required to be psychic. > > The USEFULNESS of a halting detector, is for cases where you have an > problem, with an algorithm, which can be expressed as a Turing Machine, > whose calculation is not know whether it will eventally terminate, and > thus provide a proof of existence for something, or loop forever, and > prove the non-existence of that thing. If we could make this halt > decider, we could by running the halt decider on the algorithm instead > of just trying to run the algorithm, and thus get the answer of a proof > the existence or non-existence of that result. > I can't make out what you are saying. The halting problem proofs are based on making an input that the halt decider cannot possibly decide. The input program is created from the halt decider and made to do the opposite of whatever ht halt decider decides. This fools the halt decider. If the halt decider decides its input will halt the input program loops. If the halt decider decides its input will loop the input program halts. When the halt decider executes its input in debug trace mode (or a UTM executes its TM one state transition at a time). then as soon as it detects non-halting behavior its stops executing its input and reports non-halting behavior. The input program cannot do the opposite of whatever the halt decider decides because the input program cannot do anything at all because it is no longer executing. There is no longer any input that can fool this halt decider therefore the halting problem proofs have been refuted. > The inability to do this, thus becomes related to the incompleteness > theory, where it seems that, at least for sufficient expressive system, > that there are some properties that we can not proof whether they are > true or not. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-23 22:22 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <YdMkH.39553$xf1.25566@fx27.iad> |
| In reply to | #24190 |
On 10/23/20 12:28 AM, olcott wrote: > On 10/22/2020 11:10 PM, Richard Damon wrote: >> On 10/22/20 9:15 PM, olcott wrote: >>> >>> The halting problem has never been about an unknown function. >>> A halt decider is not required to be psychic. >> >> The USEFULNESS of a halting detector, is for cases where you have an >> problem, with an algorithm, which can be expressed as a Turing Machine, >> whose calculation is not know whether it will eventally terminate, and >> thus provide a proof of existence for something, or loop forever, and >> prove the non-existence of that thing. If we could make this halt >> decider, we could by running the halt decider on the algorithm instead >> of just trying to run the algorithm, and thus get the answer of a proof >> the existence or non-existence of that result. >> > > I can't make out what you are saying. > The halting problem proofs are based on making an input that the halt > decider cannot possibly decide. > > The input program is created from the halt decider and made to do the > opposite of whatever ht halt decider decides. This fools the halt decider. > > If the halt decider decides its input will halt the input program loops. > If the halt decider decides its input will loop the input program halts. > > When the halt decider executes its input in debug trace mode > (or a UTM executes its TM one state transition at a time). > then as soon as it detects non-halting behavior its stops executing its > input and reports non-halting behavior. > > The input program cannot do the opposite of whatever the halt decider > decides because the input program cannot do anything at all because it > is no longer executing. > > There is no longer any input that can fool this halt decider therefore > the halting problem proofs have been refuted. > >> The inability to do this, thus becomes related to the incompleteness >> theory, where it seems that, at least for sufficient expressive system, >> that there are some properties that we can not proof whether they are >> true or not. >> > > I run your Turing machine equivalent, and provide it the program H_Hat(H_Hat). Per Litz, the first step of this operation is to duplicate its input, and then go into the modified H (modified only in what it does in its final states). You have describe these steps as 'calling Debug Step' This executes the sequences describe by H(H_Hat, H_Hat) and eventually it needs to return a result. This result is then used by H_Hat to decide what it will do. A couple of points: THIS invocation of H_Hat is not 'under' any supervisor, so nothing can abort it, (If something does, then you simulator is not an accurate model of a Turing Machine). DebugStep, given the same input must return the same answer, or it is faulty. In practice, since for this proof, we only ever give it one input. DebugStep MUST give an answer in finite time (this doesn't seem to be an issue with your presentation) Presuming that H is supposed to be a proper Halt Decider, the answer return by Debug Step MUST be an accurate, and reflect what this run of H_Hat will eventually do. For H_Hat to represent the H_Hat in Litz, it WILL go into an infinite loop if H would have indicated that it halted, and will Halt, if H would have indicated that it was non-Halting. It isn't the input program to H that misbehaves, it is the outermost caller of H that misbehaves, BUT, since we also provided it as the input to H, the embedded version of the program needs to behave exactly the same as the outer version of the program, at least until H decides it knows the answer, then it can stop the inner version, but NOT the outer version. You keep on talking about the run of H(H_Hat, H_Hat), but don't look at H_Hat(H_Hat). THAT is where the real rubber hits the road. We do need to compare its behavior to what H says, but since the execution of H_Hat includes as a sub-sequence, the execution of H, we can tell from that run what a run of H(H_Hat, H_Hat) would have said.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 21:51 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <A5WdnaUM_9IACw7CnZ2dnUU7-eHNnZ2d@giganews.com> |
| In reply to | #24291 |
On 10/23/2020 9:22 PM, Richard Damon wrote: > On 10/23/20 12:28 AM, olcott wrote: >> On 10/22/2020 11:10 PM, Richard Damon wrote: >>> On 10/22/20 9:15 PM, olcott wrote: >>>> >>>> The halting problem has never been about an unknown function. >>>> A halt decider is not required to be psychic. >>> >>> The USEFULNESS of a halting detector, is for cases where you have an >>> problem, with an algorithm, which can be expressed as a Turing Machine, >>> whose calculation is not know whether it will eventally terminate, and >>> thus provide a proof of existence for something, or loop forever, and >>> prove the non-existence of that thing. If we could make this halt >>> decider, we could by running the halt decider on the algorithm instead >>> of just trying to run the algorithm, and thus get the answer of a proof >>> the existence or non-existence of that result. >>> >> >> I can't make out what you are saying. >> The halting problem proofs are based on making an input that the halt >> decider cannot possibly decide. >> >> The input program is created from the halt decider and made to do the >> opposite of whatever ht halt decider decides. This fools the halt decider. >> >> If the halt decider decides its input will halt the input program loops. >> If the halt decider decides its input will loop the input program halts. >> >> When the halt decider executes its input in debug trace mode >> (or a UTM executes its TM one state transition at a time). >> then as soon as it detects non-halting behavior its stops executing its >> input and reports non-halting behavior. >> >> The input program cannot do the opposite of whatever the halt decider >> decides because the input program cannot do anything at all because it >> is no longer executing. >> >> There is no longer any input that can fool this halt decider therefore >> the halting problem proofs have been refuted. >> >>> The inability to do this, thus becomes related to the incompleteness >>> theory, where it seems that, at least for sufficient expressive system, >>> that there are some properties that we can not proof whether they are >>> true or not. >>> >> >> > > I run your Turing machine equivalent, and provide it the program > H_Hat(H_Hat). > > Per Litz, the first step of this operation is to duplicate its input, > and then go into the modified H (modified only in what it does in its > final states). > > You have describe these steps as 'calling Debug Step' > > This executes the sequences describe by H(H_Hat, H_Hat) and eventually > it needs to return a result. > > This result is then used by H_Hat to decide what it will do. > > A couple of points: > > THIS invocation of H_Hat is not 'under' any supervisor, so nothing can > abort it, (If something does, then you simulator is not an accurate > model of a Turing Machine). > > DebugStep, given the same input must return the same answer, It is DebugTrace() not DebugStep() that makes the halting decision. It turns out that the input given to the outer DebugTrace() is more extensive than the input provided to the inner DebugTrace() because the outer DebugTrace() is a few instructions ahead of the inner DebugTrace(). So when the outer DebugTrace() terminates its invocation of H_Hat() the H_Hat() invocation of DebugTrace() never gets a return value from DebugTrace(). > or it is > faulty. In practice, since for this proof, we only ever give it one input. > > DebugStep MUST give an answer in finite time (this doesn't seem to be an > issue with your presentation) > > Presuming that H is supposed to be a proper Halt Decider, the answer > return by Debug Step MUST be an accurate, and reflect what this run of > H_Hat will eventually do. > > For H_Hat to represent the H_Hat in Litz, it WILL go into an infinite > loop if H would have indicated that it halted, and will Halt, if H would > have indicated that it was non-Halting. > Yes that it why I had to redefine the notion of a halt decider so that the halting problem is no lonegr undecidable. The halt decider no longer decides if its input will halt. Instead it executes its input until it detects non-halting behavior and then the first step is to terminate the input and the next step is to indicate that it has already terminated it input. The halting problem proof trick has been neutered. > It isn't the input program to H that misbehaves, it is the outermost > caller of H that misbehaves, BUT, since we also provided it as the input > to H, the embedded version of the program needs to behave exactly the > same as the outer version of the program, at least until H decides it > knows the answer, then it can stop the inner version, but NOT the outer > version. > No this is not true. The outer version of the program has more data than the inner version of the program. > You keep on talking about the run of H(H_Hat, H_Hat), but don't look at > H_Hat(H_Hat). THAT is where the real rubber hits the road. We do need to > compare its behavior to what H says, but since the execution of H_Hat > includes as a sub-sequence, the execution of H, we can tell from that > run what a run of H(H_Hat, H_Hat) would have said. DebugTrace(H_Hat, H_Hat) makes set same decision whether called from H(H_Hat, H_Hat) and H_Hat(H_Hat) because its input is identical. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 13:07 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <878sbv25ff.fsf@bsb.me.uk> |
| In reply to | #24294 |
olcott <NoOne@NoWhere.com> writes: > Yes that it why I had to redefine the notion of a halt decider so that > the halting problem is no lonegr undecidable. I.e. there is a whole class of computations that are not decided (or at least not correctly decided) by a PO-halt decider. If there are no such computations, then a PO-halt decider is not based on a redefined notion at all. As you know, there is a correct answer to every single instance of the halting problem -- no exceptions. So if your new notion allows a PO-halt decider to do anything with any instance other than give that correct answer, then you simply have the usual, ten-a-penny, partial decider. > The halting problem proof trick has been neutered. Except for all the computations that are not decided by a PO-halt decider. And if there are none, there is no "new notion" involved -- a PO-halt decider is defined in exactly the same way as a proper halt decider. > DebugTrace(H_Hat, H_Hat) makes set same decision whether called from > H(H_Hat, H_Hat) and H_Hat(H_Hat) because its input is identical. And hence, as I (and others) showed you, H(H_Hat, H_Hat) gives the wrong result. Your levels and nesting and recursion are to no avail. At the top level, H and H_Hat disagree no matter what DebugTrace does. How it gets its return value (or what you call it) does not stop H(H_Hat, H_Hat) being wrong, but a people seem to have got sucked into your vortex! Notice that you are wrong in several equally problematic ways. You have redefines the notion of a halt decider so as to give yourself permission to get some cares wrong (that was the 2004 tactic), but you also haven't come up with a way to make H(H_Hat, H_Hat) give the right answer. Not only that, some of your claims about DebugTrace are impossible. Of course you won't show us that code because you know it's wrong or it's only speculative. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-24 11:40 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <e7qdnYkJ06JuxQnCnZ2dnUU7-U_NnZ2d@giganews.com> |
| In reply to | #24309 |
On 10/24/2020 7:07 AM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> Yes that it why I had to redefine the notion of a halt decider so that >> the halting problem is no lonegr undecidable. > > I.e. there is a whole class of computations that are not decided (or at > least not correctly decided) by a PO-halt decider. If there are no such > computations, then a PO-halt decider is not based on a redefined notion > at all. > > As you know, there is a correct answer to every single instance of the > halting problem -- no exceptions. So if your new notion allows a > PO-halt decider to do anything with any instance other than give that > correct answer, then you simply have the usual, ten-a-penny, partial > decider. > >> The halting problem proof trick has been neutered. > > Except for all the computations that are not decided by a PO-halt > decider. And if there are none, there is no "new notion" involved -- a > PO-halt decider is defined in exactly the same way as a proper halt > decider. > >> DebugTrace(H_Hat, H_Hat) makes set same decision whether called from >> H(H_Hat, H_Hat) and H_Hat(H_Hat) because its input is identical. > And hence, as I (and others) showed you, H(H_Hat, H_Hat) gives the wrong > result. Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true means that the input has infinite execution. Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false means that the input DOES NOT HAVE infinite execution. This redefined notion of a halt decider cannot be shown to ever get the wrong answer. > Your levels and nesting and recursion are to no avail. At the > top level, H and H_Hat disagree no matter what DebugTrace does. How it > gets its return value (or what you call it) does not stop H(H_Hat, > H_Hat) being wrong, but a people seem to have got sucked into your > vortex! > When executed from the outermost execution context of x86utm H(H_Hat, H_Hat) and H_Hat(H_Hat) both call Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) and each one receives a return value of true. Also in each case the inner invocation of Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) that was executed in the process context of the inner H_Hat() is aborted when the whole process tree of the inner H_Hat() is aborted. This prevents the inner Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) from ever returning a value to the inner H_Hat(). > Notice that you are wrong in several equally problematic ways. You have > redefines the notion of a halt decider so as to give yourself permission > to get some cares wrong (that was the 2004 tactic), but you also haven't If you foolishly ignore what I say and merely dogmatically state that I am incorrect this is no rebuttal what-so-ever. Merely dogmatically stating that I am incorrect without actually pointing out any error only becomes dishonest when you claim to have pointed out an error and indeed did not point out any error. It is not dishonest if you point something out that you wrongly believe is an error and indeed is not actually an error. In this case it is merely an honest mistake. > come up with a way to make H(H_Hat, H_Hat) give the right answer. Not > only that, some of your claims about DebugTrace are impossible. Of > course you won't show us that code because you know it's wrong or it's > only speculative. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-25 02:07 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <875z6zxdlg.fsf@bsb.me.uk> |
| In reply to | #24324 |
olcott <NoOne@NoWhere.com> writes: > On 10/24/2020 7:07 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> Yes that it why I had to redefine the notion of a halt decider so that >>> the halting problem is no lonegr undecidable. >> >> I.e. there is a whole class of computations that are not decided (or at >> least not correctly decided) by a PO-halt decider. If there are no such >> computations, then a PO-halt decider is not based on a redefined notion >> at all. >> >> As you know, there is a correct answer to every single instance of the >> halting problem -- no exceptions. So if your new notion allows a >> PO-halt decider to do anything with any instance other than give that >> correct answer, then you simply have the usual, ten-a-penny, partial >> decider. >> >>> The halting problem proof trick has been neutered. >> >> Except for all the computations that are not decided by a PO-halt >> decider. And if there are none, there is no "new notion" involved -- a >> PO-halt decider is defined in exactly the same way as a proper halt >> decider. >> >>> DebugTrace(H_Hat, H_Hat) makes set same decision whether called from >>> H(H_Hat, H_Hat) and H_Hat(H_Hat) because its input is identical. > >> And hence, as I (and others) showed you, H(H_Hat, H_Hat) gives the wrong >> result. > > Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true > means that the input has infinite execution. > > Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false > means that the input DOES NOT HAVE infinite execution. > > This redefined notion of a halt decider cannot be shown to ever get > the wrong answer. For the answer to be correct (as you had originally claimed) it must be about the halting or otherwise of the given computation. If the result of Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) differs from that in the case in question, the answer is incorrect. Can you conform that whatever Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) does in other cases Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) == true if and only if H_Hat(H_Hat) does not halt, and that Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) == false if and only if H_Hat(H_Hat) halts? I don't need to know (yet) how it gets the right answer, but if it diverges from indicating halting (in just this one case), then H(H_Hat, H_Hat) can't be correct. (I take it Aborted_Because_Non_Halting_Behavior_Detected is just some silly new name for DebugTrace? If not, answer about DebugTrace instead.) -- Ben.
[toc] | [prev] | [next] | [standalone]
Page 23 of 25 — ← Prev page 1 … 21 22 [23] 24 25 Next page →
Back to top | Article view | comp.theory
csiph-web