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 3 of 25 — ← Prev page 1 2 [3] 4 5 … 25 Next page →
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 00:40 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87imb033zr.fsf@bsb.me.uk> |
| In reply to | #24214 |
olcott <NoOne@NoWhere.com> writes: > On 10/23/2020 10:03 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> Your answer does not have a correct yes or no answer. >> s/answer/question/ >>> I have run DebugTrace() and it did correctly return a value is a >>> correct but misleading answer. >>> >>>> So what is the returned result from DebugTrace(H_Hat, H_Hat)? >>> >>> It is the fixed value of 1 that I used to test if it could correctly >>> return a value. >> >> I don't think you are taking this seriously. It's up to if you want to >> come across as a clown. If not, you can take the questions people ask >> seriously. > > DebugTrace() is totally complete as a function that creates new > process contexts and executes virtual machines within this new process > context. I didn't ask about that > The most difficult part was to get DebugTrace() to DebugTrace() itself > to an arbitrary recursive depth. nor that > I had to do this because H() invokes DebugTrace() to invoke H_Hat() to > invoke DebugTrace() to invoke another H_Hat() process. or that. > As I have said dozens of times now the halt decider code has not been > written. You said the DebugTrace was "fully operational". That appears to be a deliberately obtuse answer to my question. Or maybe you don't know what I was asking. But I don't care either way anymore. I withdraw the question. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-23 17:18 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <g8OdnarLx6DGnw7CnZ2dnUU78bfNnZ2d@brightview.co.uk> |
| In reply to | #24189 |
On 23/10/2020 05:13, olcott wrote: > On 10/22/2020 10:44 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> On 10/22/2020 9:09 PM, Ben Bacarisse wrote: >>>> olcott <NoOne@NoWhere.com> writes: >>>> >>>>> On 10/22/2020 6:34 PM, Ben Bacarisse wrote: >> <cut> >>>>>> Further questions: is DebugTrace vapourware or do you have it written >>>>>> and running? >>>>> >>>>> The reason for the great delay is that I waited until I got >>>>> DebugTrace() fully operational before I presented H() and H_Hat(). >>>>> >>>>>> It you have it running, can you run DebugTrace(H_Hat, >>>>>> H_Hat) to get a return value? If not why not? If you can, what >>>>>> is the >>>>>> return value? >>>>> >>>>> It took me a man-year to write my x86utm operating system. Now I >>>>> finally have the full basis to write the most robust halt deciding >>>>> code. >>>> >>>> Can you run DebugTrace(H_Hat, H_Hat) to get a return value? >>> >>> I have already answered this question completely. >> >> That's pure crank 101. People who want to be understood are happy to >> repeat an answer: "sorry, did you miss it? I said yes". You see? >> Clear and unambiguous. Cranks don't do that because they want as many >> get-out clauses left open as they can. >> > > It is bad for me to have patience with people to to pay so little > attention to what I am saying that after I have answered their question > five times they did not bother to notice the answer even a single time. > > Your answer does not have a correct yes or no answer. > I have run DebugTrace() and it did correctly return a value is a correct > but misleading answer. > LOL, I think I can see what's happened now! :) Two years ago you genuinely thought you had a /design/ for a TM that would actually contradict the Linz logic, and so you announced that you had two fully coded TMs that worked, when in fact you just had an idea. [You clearly thought at the time it would only be a couple of weeks of coding to implement your idea, so what harm in lying about actually having the TMs? That's not a lie, because you would have them soon and nobody would know otherwise. And the lie sounds "more convincing" than the truth that it was just an idea you had, so you went for it...] Since then you've been playing catchup, realising you couldn't code a TM, and then even coding in a C environment would be months/years of work. Now (in the last week or so) for the first time, you've actually been able to try out your idea, and I provided you with an H_Hat skeleton which forced you to follow the Linz proof restrictions - and you FINALLY realised your idea didn't work, and WHY it didn't! The decision of H_copy [the copy of H embedded in H_Hat] on running H_Hat with input <H_Hat> is made BEFORE H_Hat actually finishes running, so H_Hat's actual behaviour can be different, showing H's decision to be incorrect. FINALLY I think you (at least partially) understand the proof, which everybody else understood all along, and you are stuffed. Rather than admit you'd just been a dumbo for 15 years, you did what you always do: just carry on regardless, changing whatever needs to be changed about your original claim and the meaning of the terms in the proof you're "refuting" to try to make your revised claim still true! [I'd have to say that you are one of the most inflexible thinkers I've come across on UseNet when it comes to recognising mistakes/dead ends and switching to better approaches - totally the opposite behaviour exhibited by "true geniuses"...] Hence all the rubbish in the last week or so about "changing the question" to try to make your problem go away. I think that what you're thinking is that you can make the problem of H_Hat finishing AFTER H_Copy has returned its decision JUST GO AWAY by saying the decision of H_Copy is not "whether H_Hat halts", but in fact should be read as "whether or not I decided H_Hat would halt and aborted it". And since your H_Copy aborts it's emulation of H_Hat before the emulation actually finishes, we're for some reason not allowed to talk about what H_Hat /actually/ does. (Duh!) You can't make the basic problem you've suddenly encountered go away like that - Linz's proof worked all along, and you've only just understood (at least partially) how it works in the last couple of weeks. And now you can't bring yourself to just admit it, because you are an unacknowledged genius who CAN'T be wrong, so you MUST have be right all along for some other reason... [now if only you could come up with a plausible reason, but you can't! :) ] Regards, Mike.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 17:28 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87wnzg52l3.fsf@bsb.me.uk> |
| In reply to | #24218 |
Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > Two years ago you genuinely thought you had a /design/ for a TM that > would actually contradict the Linz logic, and so you announced that > you had two fully coded TMs that worked, when in fact you just had an > idea. [You clearly thought at the time it would only be a couple of > weeks of coding to implement your idea, so what harm in lying about > actually having the TMs? That's not a lie, because you would have > them soon and nobody would know otherwise. And the lie sounds "more > convincing" than the truth that it was just an idea you had, so you > went for it...] > > Since then you've been playing catchup, realising you couldn't code a > TM, and then even coding in a C environment would be months/years of > work. For the record, that's exactly what I've thought all along. As usual, you are being a bit kinder than I would be, but that's your way. > Now (in the last week or so) for the first time, you've actually been > able to try out your idea, and I provided you with an H_Hat skeleton > which forced you to follow the Linz proof restrictions - and you > FINALLY realised your idea didn't work, and WHY it didn't! I find this much more of a stretch! -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 12:40 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <A_WdnTO2jN80iA7CnZ2dnUU7-f3NnZ2d@giganews.com> |
| In reply to | #24220 |
On 10/23/2020 11:28 AM, Ben Bacarisse wrote: > Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > >> Two years ago you genuinely thought you had a /design/ for a TM that >> would actually contradict the Linz logic, and so you announced that >> you had two fully coded TMs that worked, when in fact you just had an >> idea. [You clearly thought at the time it would only be a couple of >> weeks of coding to implement your idea, so what harm in lying about >> actually having the TMs? That's not a lie, because you would have >> them soon and nobody would know otherwise. And the lie sounds "more >> convincing" than the truth that it was just an idea you had, so you >> went for it...] >> >> Since then you've been playing catchup, realising you couldn't code a >> TM, and then even coding in a C environment would be months/years of >> work. > > For the record, that's exactly what I've thought all along. As usual, > you are being a bit kinder than I would be, but that's your way. > Instead of the C function DebugTrace() we could simply have a UTM that executes an (already on the tape) input UTM. This halt decider UTM would execute its (already on the tape) input UTM one state transition at a time. As soon as the halt decider UTM detects that its (already on the tape) input UTM would not halt, the halt decider UTM stops executing its (already on the tape) input UTM and transitions to its own final state indicating Aborted_Because_Non_Halting_Behavior_Detected. Thus DebugTrace() <is> equivalent to a UTM doing the same thing. >> Now (in the last week or so) for the first time, you've actually been >> able to try out your idea, and I provided you with an H_Hat skeleton >> which forced you to follow the Linz proof restrictions - and you >> FINALLY realised your idea didn't work, and WHY it didn't! > > I find this much more of a stretch! > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 11:38 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <pZidnbSdJISHmg7CnZ2dnUU7-N3NnZ2d@giganews.com> |
| In reply to | #24218 |
On 10/23/2020 11:18 AM, Mike Terry wrote:
> On 23/10/2020 05:13, olcott wrote:
>> On 10/22/2020 10:44 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 10/22/2020 9:09 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 10/22/2020 6:34 PM, Ben Bacarisse wrote:
>>> <cut>
>>>>>>> Further questions: is DebugTrace vapourware or do you have it
>>>>>>> written
>>>>>>> and running?
>>>>>>
>>>>>> The reason for the great delay is that I waited until I got
>>>>>> DebugTrace() fully operational before I presented H() and H_Hat().
>>>>>>
>>>>>>> It you have it running, can you run DebugTrace(H_Hat,
>>>>>>> H_Hat) to get a return value? If not why not? If you can, what
>>>>>>> is the
>>>>>>> return value?
>>>>>>
>>>>>> It took me a man-year to write my x86utm operating system. Now I
>>>>>> finally have the full basis to write the most robust halt deciding
>>>>>> code.
>>>>>
>>>>> Can you run DebugTrace(H_Hat, H_Hat) to get a return value?
>>>>
>>>> I have already answered this question completely.
>>>
>>> That's pure crank 101. People who want to be understood are happy to
>>> repeat an answer: "sorry, did you miss it? I said yes". You see?
>>> Clear and unambiguous. Cranks don't do that because they want as many
>>> get-out clauses left open as they can.
>>>
>>
>> It is bad for me to have patience with people to to pay so little
>> attention to what I am saying that after I have answered their question
>> five times they did not bother to notice the answer even a single time.
>>
>> Your answer does not have a correct yes or no answer.
>> I have run DebugTrace() and it did correctly return a value is a correct
>> but misleading answer.
>>
>
> LOL, I think I can see what's happened now! :)
>
> Two years ago you genuinely thought you had a /design/ for a TM that
> would actually contradict the Linz logic, and so you announced that you
> had two fully coded TMs that worked, when in fact you just had an idea.
> [You clearly thought at the time it would only be a couple of weeks of
> coding to implement your idea, so what harm in lying about actually
> having the TMs? That's not a lie, because you would have them soon and
> nobody would know otherwise. And the lie sounds "more convincing" than
> the truth that it was just an idea you had, so you went for it...]
>
> Since then you've been playing catchup, realising you couldn't code a
> TM, and then even coding in a C environment would be months/years of work.
>
> Now (in the last week or so) for the first time, you've actually been
> able to try out your idea, and I provided you with an H_Hat skeleton
> which forced you to follow the Linz proof restrictions -
> and you FINALLY
> realised your idea didn't work, and WHY it didn't!
Not at all. Not in the least little bit.
You aren't paying very close attention are you?
> The decision of
> H_copy [the copy of H embedded in H_Hat] on running H_Hat with input
> <H_Hat> is made BEFORE H_Hat actually finishes running, so H_Hat's
> actual behaviour can be different, showing H's decision to be incorrect.
>
As in all of the conventional proofs the input program is based on
modifications made to the halt decider.
Next, we modify H to produce a Turing machine H' with the structure
shown in Figure 12.2.
http://www.liarparadox.org/Peter_Linz_HP(Pages_315-320).pdf
// Simpifications of H() and H_Hat() provided by
// Ben Bacarisse wrote On 10/22/2020 11:00 PM
// M has address of H_Hat()
void H_Hat(u32 M)
{
if (!DebugTrace(M, M)) // M(M) Aborted?
HERE: goto HERE;
HALT
}
// M and N have the address of H_Hat()
void H(u32 M, u32 N)
{
if (DebugTrace(M, N)) // M(N) Aborted?
MOV_EAX_0 // Execution of M(N) has been aborted
else
MOV_EAX_1 // M(N) has halted
HALT
}
int main()
{
u32 M = (u32)H_Hat;
H(M, M);
HALT;
}
> FINALLY I think you (at least partially) understand the proof, which
> everybody else understood all along, and you are stuffed. Rather than
> admit you'd just been a dumbo for 15 years, you did what you always do:
> just carry on regardless, changing whatever needs to be changed about
> your original claim and the meaning of the terms in the proof you're
> "refuting" to try to make your revised claim still true! [I'd have to
> say that you are one of the most inflexible thinkers I've come across on
> UseNet when it comes to recognising mistakes/dead ends and switching to
> better approaches - totally the opposite behaviour exhibited by "true
> geniuses"...]
>
> Hence all the rubbish in the last week or so about "changing the
> question" to try to make your problem go away. I think that what you're
> thinking is that you can make the problem of H_Hat finishing AFTER
> H_Copy has returned its decision JUST GO AWAY by
Forcing H_Hat() to terminate before the decision is returned.
This makes it impossible for H_Hat() to do anything at all, thus H_Hat()
cannot possibly do the opposite of whatever DebugTrace() decides.
> saying the decision of
> H_Copy is not "whether H_Hat halts", but in fact should be read as
> "whether or not I decided H_Hat would halt and aborted it". And since
The unique discovery that I made in 2016 indicates that H_Hat() would
never terminate unless it was aborted.
> your H_Copy aborts it's emulation of H_Hat before the emulation actually
> finishes, we're for some reason not allowed to talk about what H_Hat
> /actually/ does. (Duh!)
>
No. The DebugTrace() of H_Hat() that is invoked by H() aborts its
execution of H_Hat() because unless H_Hat() is aborted it would never
terminate.
> You can't make the basic problem you've suddenly encountered go away
> like that - Linz's proof worked all along, and you've only just
> understood (at least partially) how it works in the last couple of
> weeks. And now you can't bring yourself to just admit it, because you
> are an unacknowledged genius who CAN'T be wrong, so you MUST have be
> right all along for some other reason... [now if only you could come up
> with a plausible reason, but you can't! :) ]
>
> Regards,
> Mike.
>
The reason that I can't admit that I am wrong this that I am correct and
you can't show otherwise.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-22 16:25 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <f9Cdnfu9pZjAOQzCnZ2dnUU78U3NnZ2d@brightview.co.uk> |
| In reply to | #24104 |
On 22/10/2020 15:36, olcott wrote: > On 10/22/2020 7:00 AM, Richard Damon wrote: >> On 10/22/20 12:33 AM, olcott wrote: >>> >>> The difference is that it is no longer possible for H_Hat() to do the >>> opposite of what H() decides. This transforms an undecidable problem >>> into a decidable problem. >> >> If H_Hat no longer does what the proof defined, then your demonstration >> is no longer applicable to the proof. >> > > If the halt decider is to report whether or not its input halts another > program can be constructed on the the basis of this halt decider that > does the opposite of whatever the halt decider decides. > > This is how H() and H_Hat() are defined in the Linz proof. > > If the halt decider is to report whether or not it aborted its input > program because its input program would otherwise cause the halt decider > to get stuck in infinite execution then this other program can no longer > fool its halt decider and do the opposite of whatever it decides. > > If H() aborts the execution of H_Hat() then H_Hat() cannot continue to > execute because H() has complete control over H_Hat. > > The end result of this slight change is that the halting problem can no > longer be shown to be undecidable. > It is suspicious that in none of this have you ever stated what is actually wrong in the Linz proof. It's almost as though you accept there is nothing wrong with it, and yet you still think its conclusion is incorrect! Or that you can't see anything wrong with it, and in your head the mistake in the proof is that its conclusion is wrong? (Thinking a conclusion is wrong does not refute anything...) Anyhow, you talk about the halt decider reporting that it "aborted its input program, because blah blah". If you read the Linz proof, you'll notice that it is completely unaffected of any internal reasoning as to WHY H might have made whatever decision it made. All it depends on is that H actually makes a decision! In your example, as long as H actually makes /some/ decision, the H_Hat will do the opposite of what H decided, and so the Linz proof will be confirmed, not refuted. If H loops, never making any decision, then H is not a decider for the H_Hat(H_Hat) question (contrary to what you have always explicitly stated) and so is irrelevant to the Linz proof. You have said you won't reveal your final code unless I (and others) agree that what you've said so far already proves your point. Well, you haven't proved anything, so that's that. So... this was to be the culmination of your life's work, and now you're simply not going to publish it? I thought the whole purpose of producing the actual TMs was that it would override any objections people raised to a mere verbal claim, and prove you right despite the objections? Two years ago I told you that if you just gave your reasoning and perhaps some high-level pseudo-code, and forgot about producing actual "TM"s and traces and whatnot, people would quickly tell you your mistake and you could save months of effort. And it turns out (no surprise) that this was correct! Had you posted 2 years ago just what you've said in this thread people would have said exactly the same as they're saying now, and nothing whatsoever would be different, except you would have saved a year's work on your part. :) Regards, Mike.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-22 16:45 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87o8ku9sdb.fsf@bsb.me.uk> |
| In reply to | #24110 |
Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > On 22/10/2020 15:36, olcott wrote: >> On 10/22/2020 7:00 AM, Richard Damon wrote: >>> On 10/22/20 12:33 AM, olcott wrote: >>>> >>>> The difference is that it is no longer possible for H_Hat() to do the >>>> opposite of what H() decides. This transforms an undecidable problem >>>> into a decidable problem. >>> >>> If H_Hat no longer does what the proof defined, then your demonstration >>> is no longer applicable to the proof. >>> >> >> If the halt decider is to report whether or not its input halts another >> program can be constructed on the the basis of this halt decider that >> does the opposite of whatever the halt decider decides. >> >> This is how H() and H_Hat() are defined in the Linz proof. >> >> If the halt decider is to report whether or not it aborted its input >> program because its input program would otherwise cause the halt decider >> to get stuck in infinite execution then this other program can no longer >> fool its halt decider and do the opposite of whatever it decides. >> >> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >> execute because H() has complete control over H_Hat. >> >> The end result of this slight change is that the halting problem can no >> longer be shown to be undecidable. > > It is suspicious that in none of this have you ever stated what is > actually wrong in the Linz proof. He has! He's wrong, of course, but he /has/ said. The part PO disputes is asserting that H can not give the correct halting answer for the input pair <[H^], [H^]>. And to show that that assertion is wrong he was going to produce two actual Turing machines, fully encoded, exactly as in Linz, but where H correctly decides the <[H^], [H^]> case. We will never see that. And he's not going to do that now with H and H_Hat, but he appears to be wavering about exactly what error to commit to making. He has suggested that his H and H_Hat are not in the correct relationship with each other, but he has also suggested that H won't give the right answer. Maybe he'll go with both errors, but I suspect we won't see this code either. Much simpler to just keep boasting that the proofs have been refuted: "I have correctly refuted each and every mechanism by which the [halting theorem] has been proven to be true." Care to guess the date? 13 Aug 2004. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Mike Terry <news.dead.person.stones@darjeeling.plus.com> |
|---|---|
| Date | 2020-10-22 17:57 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <1qSdnYGsfY-KJwzCnZ2dnUU78K_NnZ2d@brightview.co.uk> |
| In reply to | #24112 |
On 22/10/2020 16:45, Ben Bacarisse wrote: > Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > >> On 22/10/2020 15:36, olcott wrote: >>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>> On 10/22/20 12:33 AM, olcott wrote: >>>>> >>>>> The difference is that it is no longer possible for H_Hat() to do the >>>>> opposite of what H() decides. This transforms an undecidable problem >>>>> into a decidable problem. >>>> >>>> If H_Hat no longer does what the proof defined, then your demonstration >>>> is no longer applicable to the proof. >>>> >>> >>> If the halt decider is to report whether or not its input halts another >>> program can be constructed on the the basis of this halt decider that >>> does the opposite of whatever the halt decider decides. >>> >>> This is how H() and H_Hat() are defined in the Linz proof. >>> >>> If the halt decider is to report whether or not it aborted its input >>> program because its input program would otherwise cause the halt decider >>> to get stuck in infinite execution then this other program can no longer >>> fool its halt decider and do the opposite of whatever it decides. >>> >>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >>> execute because H() has complete control over H_Hat. >>> >>> The end result of this slight change is that the halting problem can no >>> longer be shown to be undecidable. >> >> It is suspicious that in none of this have you ever stated what is >> actually wrong in the Linz proof. > > He has! He's wrong, of course, but he /has/ said. The part PO disputes > is asserting that H can not give the correct halting answer for the > input pair <[H^], [H^]>. And to show that that assertion is wrong he > was going to produce two actual Turing machines, fully encoded, exactly > as in Linz, but where H correctly decides the <[H^], [H^]> case. We > will never see that. > That doesn't count as stating what is wrong with the Linz proof, because "H can not give the correct halting answer for the input pair <[H^], [H^]>" is a /conclusion/ within the proof, based on a contradiction generated in turn by the previous state transition diagrams. PO would need to do one of the following: identify one of the state transition claims which is wrong; agree that the state transition diagrams are correct, but there is no contradiction in them; or say that there is a contradiction, but this doesn't mean that one of the assumptions leading to the contradiction is wrong; or say that one of the assumptions leading to the contradiction is wrong, but it is some other assumption than "H is a halt decider"; etc.. Just saying "It's wrong that H can not give the correct halting answer for the input pair <[H^], [H^]>" is just disagreeing with a conclusion. Perhaps I should have said that he has never identified the specific /reasoning/ step in the proof which is wrong. (If he had, we could have expanded any missing/unclear reasoning steps to the point where he would have to agree that particular step was in fact ok. Hmm, ok maybe we couldn't do that as for some people there's really no convincing them, but I don't believe he's ever been this specific about the problem. I could be wrong on that I guess.) Mike.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 12:26 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <2u6dna1sWuonXQzCnZ2dnUU7-V_NnZ2d@giganews.com> |
| In reply to | #24118 |
On 10/22/2020 11:57 AM, Mike Terry wrote: > On 22/10/2020 16:45, Ben Bacarisse wrote: >> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: >> >>> On 22/10/2020 15:36, olcott wrote: >>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>>> On 10/22/20 12:33 AM, olcott wrote: >>>>>> >>>>>> The difference is that it is no longer possible for H_Hat() to do the >>>>>> opposite of what H() decides. This transforms an undecidable problem >>>>>> into a decidable problem. >>>>> >>>>> If H_Hat no longer does what the proof defined, then your >>>>> demonstration >>>>> is no longer applicable to the proof. >>>>> >>>> >>>> If the halt decider is to report whether or not its input halts another >>>> program can be constructed on the the basis of this halt decider that >>>> does the opposite of whatever the halt decider decides. >>>> >>>> This is how H() and H_Hat() are defined in the Linz proof. >>>> >>>> If the halt decider is to report whether or not it aborted its input >>>> program because its input program would otherwise cause the halt >>>> decider >>>> to get stuck in infinite execution then this other program can no >>>> longer >>>> fool its halt decider and do the opposite of whatever it decides. >>>> >>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >>>> execute because H() has complete control over H_Hat. >>>> >>>> The end result of this slight change is that the halting problem can no >>>> longer be shown to be undecidable. >>> >>> It is suspicious that in none of this have you ever stated what is >>> actually wrong in the Linz proof. >> >> He has! He's wrong, of course, but he /has/ said. The part PO disputes >> is asserting that H can not give the correct halting answer for the >> input pair <[H^], [H^]>. And to show that that assertion is wrong he >> was going to produce two actual Turing machines, fully encoded, exactly >> as in Linz, but where H correctly decides the <[H^], [H^]> case. We >> will never see that. >> > > That doesn't count as stating what is wrong with the Linz proof, because > "H can not give the correct halting answer for the input pair <[H^], > [H^]>" is a /conclusion/ within the proof, based on a contradiction > generated in turn by the previous state transition diagrams. > Within Linz's faulty assumption that the only possible way to create a universal halt decider is to directly ask the question: Does the input program halt on its input? The Linz proof is correct. When we realize that this assumption is faulty and instead ask the question: Was the execution of the input program on its input aborted because non halting behavior was detected? Then creating a universal halt decider is no longer "proved" to be impossible on the basis of the conventional self-referential halting problem counter-examples. The halt decider either detects non-halting behavior and reports it or allows the input program to terminate on its own. > PO would need to do one of the following: identify one of the state > transition claims which is wrong; agree that the state transition > diagrams are correct, but there is no contradiction in them; or say that > there is a contradiction, but this doesn't mean that one of the > assumptions leading to the contradiction is wrong; or say that one of > the assumptions leading to the contradiction is wrong, but it is some > other assumption than "H is a halt decider"; etc.. > > Just saying "It's wrong that H can not give the correct halting answer > for the input pair <[H^], [H^]>" is just disagreeing with a conclusion. > > Perhaps I should have said that he has never identified the specific > /reasoning/ step in the proof which is wrong. (If he had, we could have > expanded any missing/unclear reasoning steps to the point where he would > have to agree that particular step was in fact ok. Hmm, ok maybe we > couldn't do that as for some people there's really no convincing them, > but I don't believe he's ever been this specific about the problem. I > could be wrong on that I guess.) > > Mike. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-22 21:15 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <877dri9fw0.fsf@bsb.me.uk> |
| In reply to | #24118 |
Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > On 22/10/2020 16:45, Ben Bacarisse wrote: >> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: >> >>> On 22/10/2020 15:36, olcott wrote: >>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>>> On 10/22/20 12:33 AM, olcott wrote: >>>>>> >>>>>> The difference is that it is no longer possible for H_Hat() to do the >>>>>> opposite of what H() decides. This transforms an undecidable problem >>>>>> into a decidable problem. >>>>> >>>>> If H_Hat no longer does what the proof defined, then your demonstration >>>>> is no longer applicable to the proof. >>>>> >>>> >>>> If the halt decider is to report whether or not its input halts another >>>> program can be constructed on the the basis of this halt decider that >>>> does the opposite of whatever the halt decider decides. >>>> >>>> This is how H() and H_Hat() are defined in the Linz proof. >>>> >>>> If the halt decider is to report whether or not it aborted its input >>>> program because its input program would otherwise cause the halt decider >>>> to get stuck in infinite execution then this other program can no longer >>>> fool its halt decider and do the opposite of whatever it decides. >>>> >>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >>>> execute because H() has complete control over H_Hat. >>>> >>>> The end result of this slight change is that the halting problem can no >>>> longer be shown to be undecidable. >>> >>> It is suspicious that in none of this have you ever stated what is >>> actually wrong in the Linz proof. >> >> He has! He's wrong, of course, but he /has/ said. The part PO disputes >> is asserting that H can not give the correct halting answer for the >> input pair <[H^], [H^]>. And to show that that assertion is wrong he >> was going to produce two actual Turing machines, fully encoded, exactly >> as in Linz, but where H correctly decides the <[H^], [H^]> case. We >> will never see that. >> > > That doesn't count as stating what is wrong with the Linz proof, > because "H can not give the correct halting answer for the input pair > <[H^], [H^]>" is a /conclusion/ within the proof, based on a > contradiction generated in turn by the previous state transition > diagrams. Sure, but it's hard to describe it any other way than as something he once though was wrong with the proof. (I have to change tense because, at for least today, he is accepting Linz's proof.) > Perhaps I should have said that he has never identified the specific > /reasoning/ step in the proof which is wrong. Yes, then I probably would not have said anything. > (If he had, we could have expanded any missing/unclear reasoning steps > to the point where he would have to agree that particular step was in > fact ok. Hmm, ok maybe we couldn't do that as for some people there's > really no convincing them, but I don't believe he's ever been this > specific about the problem. I could be wrong on that I guess.) It's hard to people like you and me to know what it feels like inside the head of someone so delusional they honestly think they are God. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 15:36 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <uNCdncymKuTScAzCnZ2dnUU7-cnNnZ2d@giganews.com> |
| In reply to | #24155 |
On 10/22/2020 3:15 PM, Ben Bacarisse wrote: > Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: > >> On 22/10/2020 16:45, Ben Bacarisse wrote: >>> Mike Terry <news.dead.person.stones@darjeeling.plus.com> writes: >>> >>>> On 22/10/2020 15:36, olcott wrote: >>>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>>>> On 10/22/20 12:33 AM, olcott wrote: >>>>>>> >>>>>>> The difference is that it is no longer possible for H_Hat() to do the >>>>>>> opposite of what H() decides. This transforms an undecidable problem >>>>>>> into a decidable problem. >>>>>> >>>>>> If H_Hat no longer does what the proof defined, then your demonstration >>>>>> is no longer applicable to the proof. >>>>>> >>>>> >>>>> If the halt decider is to report whether or not its input halts another >>>>> program can be constructed on the the basis of this halt decider that >>>>> does the opposite of whatever the halt decider decides. >>>>> >>>>> This is how H() and H_Hat() are defined in the Linz proof. >>>>> >>>>> If the halt decider is to report whether or not it aborted its input >>>>> program because its input program would otherwise cause the halt decider >>>>> to get stuck in infinite execution then this other program can no longer >>>>> fool its halt decider and do the opposite of whatever it decides. >>>>> >>>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >>>>> execute because H() has complete control over H_Hat. >>>>> >>>>> The end result of this slight change is that the halting problem can no >>>>> longer be shown to be undecidable. >>>> >>>> It is suspicious that in none of this have you ever stated what is >>>> actually wrong in the Linz proof. >>> >>> He has! He's wrong, of course, but he /has/ said. The part PO disputes >>> is asserting that H can not give the correct halting answer for the >>> input pair <[H^], [H^]>. And to show that that assertion is wrong he >>> was going to produce two actual Turing machines, fully encoded, exactly >>> as in Linz, but where H correctly decides the <[H^], [H^]> case. We >>> will never see that. >>> >> >> That doesn't count as stating what is wrong with the Linz proof, >> because "H can not give the correct halting answer for the input pair >> <[H^], [H^]>" is a /conclusion/ within the proof, based on a >> contradiction generated in turn by the previous state transition >> diagrams. > > Sure, but it's hard to describe it any other way than as something he > once though was wrong with the proof. (I have to change tense because, > at for least today, he is accepting Linz's proof.) > >> Perhaps I should have said that he has never identified the specific >> /reasoning/ step in the proof which is wrong. > > Yes, then I probably would not have said anything. > If we assume that all cats are dogs then we can prove that cats must bark and there are no incorrect steps of our proof. If we assume that a halt decider can only be defined as follows: bool Does_It_Halt(u32 P, u32 I) then it can be proved that no universal halt decider can possibly exist. On the other hand changing to this assumption: bool Execution_aborted_because_non_halting_was_detected(u32 P, u32 I) it cannot be proved that no universal halt decider can possibly exist. >> (If he had, we could have expanded any missing/unclear reasoning steps >> to the point where he would have to agree that particular step was in >> fact ok. Hmm, ok maybe we couldn't do that as for some people there's >> really no convincing them, but I don't believe he's ever been this >> specific about the problem. I could be wrong on that I guess.) > > It's hard to people like you and me to know what it feels like inside > the head of someone so delusional they honestly think they are God. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 11:38 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <dYmdnXRdH4cMKAzCnZ2dnUU7-c_NnZ2d@giganews.com> |
| In reply to | #24110 |
On 10/22/2020 10:25 AM, Mike Terry wrote: > On 22/10/2020 15:36, olcott wrote: >> On 10/22/2020 7:00 AM, Richard Damon wrote: >>> On 10/22/20 12:33 AM, olcott wrote: >>>> >>>> The difference is that it is no longer possible for H_Hat() to do the >>>> opposite of what H() decides. This transforms an undecidable problem >>>> into a decidable problem. >>> >>> If H_Hat no longer does what the proof defined, then your demonstration >>> is no longer applicable to the proof. >>> >> >> If the halt decider is to report whether or not its input halts another >> program can be constructed on the the basis of this halt decider that >> does the opposite of whatever the halt decider decides. >> >> This is how H() and H_Hat() are defined in the Linz proof. >> >> If the halt decider is to report whether or not it aborted its input >> program because its input program would otherwise cause the halt decider >> to get stuck in infinite execution then this other program can no longer >> fool its halt decider and do the opposite of whatever it decides. >> >> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to >> execute because H() has complete control over H_Hat. >> >> The end result of this slight change is that the halting problem can no >> longer be shown to be undecidable. >> > > It is suspicious that in none of this have you ever stated what is > actually wrong in the Linz proof. When the halting problem is defined as: bool Does_It_Halt(u32 P, u32 I) another program can be constructed on the basis of Does_It_Halt() that does the opposite of whatever Does_It_Halt() decides. When the halting problem is defined as: bool Was_Its_Execution_Aborted(u32 P, u32 I) another program CANNOT be constructed on the basis of Was_Its_Execution_Aborted() that does the opposite of whatever Was_Its_Execution_Aborted() decides. All of the cases where Was_Its_Execution_Aborted() returns true are cases of non-halting behavior. All of the cases where Was_Its_Execution_Aborted() returns false are cases of halting behavior. > It's almost as though you accept > there is nothing wrong with it, and yet you still think its conclusion > is incorrect! Or that you can't see anything wrong with it, and in your > head the mistake in the proof is that its conclusion is wrong? (Thinking > a conclusion is wrong does not refute anything...) > > Anyhow, you talk about the halt decider reporting that it "aborted its > input program, because blah blah". If you read the Linz proof, you'll > notice that it is completely unaffected of any internal reasoning as to > WHY H might have made whatever decision it made. All it depends on is > that H actually makes a decision! > In the Linz case if a program would not halt and we are asking would it halt and we abort the execution of H_Hat() then H() gets the wrong answer because H() says that it would not halt and it does halt. If we keep everything else the same except change the question to: Was the input program aborted because it would not otherwise terminate? Now when we answer yes we get the right answer. H_hat() cannot possibly do the opposite of what H() decides because H_Hat() is under the complete control of H(). > In your example, as long as H actually makes /some/ decision, the H_Hat > will do the opposite of what H decided, and so the Linz proof will be No not at all, not in the least little bit, as exaplained above. > confirmed, not refuted. If H loops, never making any decision, then H That violates the defintion of a halt decider. > is not a decider for the H_Hat(H_Hat) question (contrary to what you > have always explicitly stated) and so is irrelevant to the Linz proof. > > You have said you won't reveal your final code unless I (and others) > agree that what you've said so far already proves your point. Well, you > haven't proved anything, so that's that. > I took me 12,000 hours to derive this simple little proof so it is OK if you don't get it right away. > So... this was to be the culmination of your life's work, and now you're > simply not going to publish it? I thought the whole purpose of I didn't say that. As soon as people pay enough attention they will see that I am correct. > producing the actual TMs was that it would override any objections > people raised to a mere verbal claim, and prove you right despite the > objections? > The "objections" are merely not paying enough attention to understand what I am saying. > Two years ago I told you that if you just gave your reasoning and > perhaps some high-level pseudo-code, and forgot about producing actual > "TM"s and traces and whatnot, people would quickly tell you your mistake > and you could save months of effort. And it turns out (no surprise) > that this was correct! Had you posted 2 years ago just what you've said > in this thread people would have said exactly the same as they're saying > now, and nothing whatsoever would be different, except you would have > saved a year's work on your part. :) > > Regards, > Mike. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 09:56 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <7d7dea3d-a258-4e04-9159-1f77c09d7e27n@googlegroups.com> |
| In reply to | #24113 |
On Thursday, 22 October 2020 at 17:38:49 UTC+1, olcott wrote: > On 10/22/2020 10:25 AM, Mike Terry wrote: > > On 22/10/2020 15:36, olcott wrote: > >> On 10/22/2020 7:00 AM, Richard Damon wrote: > > >> The end result of this slight change is that the halting problem can no > >> longer be shown to be undecidable. > >> > > > > It is suspicious that in none of this have you ever stated what is > > actually wrong in the Linz proof. > When the halting problem is defined as: > bool Does_It_Halt(u32 P, u32 I) > another program can be constructed on the basis of Does_It_Halt() that > does the opposite of whatever Does_It_Halt() decides. > > When the halting problem is defined as: > bool Was_Its_Execution_Aborted(u32 P, u32 I) > > another program CANNOT be constructed on the basis of > Was_Its_Execution_Aborted() that does the opposite of whatever > Was_Its_Execution_Aborted() decides. > As I said, you're right. If we change the question from "will the program halt?" to "will DebugTrace raise an abortion anywhere on the call stack?" the paradox goes away. I'll leave it to others to explain why this only seems to refute the LInz proof that halting is undecideable.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 12:09 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <gI-dnaYF_P1YIQzCnZ2dnUU7-b3NnZ2d@giganews.com> |
| In reply to | #24116 |
On 10/22/2020 11:56 AM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 17:38:49 UTC+1, olcott wrote: >> On 10/22/2020 10:25 AM, Mike Terry wrote: >>> On 22/10/2020 15:36, olcott wrote: >>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >> >>>> The end result of this slight change is that the halting problem can no >>>> longer be shown to be undecidable. >>>> >>> >>> It is suspicious that in none of this have you ever stated what is >>> actually wrong in the Linz proof. >> When the halting problem is defined as: >> bool Does_It_Halt(u32 P, u32 I) >> another program can be constructed on the basis of Does_It_Halt() that >> does the opposite of whatever Does_It_Halt() decides. >> >> When the halting problem is defined as: >> bool Was_Its_Execution_Aborted(u32 P, u32 I) >> >> another program CANNOT be constructed on the basis of >> Was_Its_Execution_Aborted() that does the opposite of whatever >> Was_Its_Execution_Aborted() decides. >> > As I said, you're right. If we change the question from "will the program > halt?" to "will DebugTrace raise an abortion anywhere on the call stack?" > the paradox goes away. > > I'll leave it to others to explain why this only seems to refute the LInz > proof that halting is undecideable. > It refutes the general assertion that the halting problem is undecidable by showing how the halting question can be transformed into an equivalent question that cannot be thwarted by pathological self-reference. So within Linz's faulty assumption that the only possible way to create a universal halt decider is to directly ask the question: Does the input program halt on its input? The Linz proof is correct. When we realize that this assumption is faulty and instead ask the question: Was the execution of the input program on its input aborted? Then creating a universal halt decider is no longer "proved" to be impossible on the basis of the conventional self-referential halting problem counter-examples. The halt decider either detects non-halting behavior and reports it or allows the input program to terminate on its own. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 10:27 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <db14ea67-109b-4965-831e-1d03bdc7db17n@googlegroups.com> |
| In reply to | #24120 |
On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: > On 10/22/2020 11:56 AM, Malcolm McLean wrote: > > On Thursday, 22 October 2020 at 17:38:49 UTC+1, olcott wrote: > >> On 10/22/2020 10:25 AM, Mike Terry wrote: > >>> On 22/10/2020 15:36, olcott wrote: > >>>> On 10/22/2020 7:00 AM, Richard Damon wrote: > >> > >>>> The end result of this slight change is that the halting problem can no > >>>> longer be shown to be undecidable. > >>>> > >>> > >>> It is suspicious that in none of this have you ever stated what is > >>> actually wrong in the Linz proof. > >> When the halting problem is defined as: > >> bool Does_It_Halt(u32 P, u32 I) > >> another program can be constructed on the basis of Does_It_Halt() that > >> does the opposite of whatever Does_It_Halt() decides. > >> > >> When the halting problem is defined as: > >> bool Was_Its_Execution_Aborted(u32 P, u32 I) > >> > >> another program CANNOT be constructed on the basis of > >> Was_Its_Execution_Aborted() that does the opposite of whatever > >> Was_Its_Execution_Aborted() decides. > >> > > As I said, you're right. If we change the question from "will the program > > halt?" to "will DebugTrace raise an abortion anywhere on the call stack?" > > the paradox goes away. > > > > I'll leave it to others to explain why this only seems to refute the LInz > > proof that halting is undecideable. > > > It refutes the general assertion that the halting problem is undecidable > by showing how the halting question can be transformed into an > equivalent question that cannot be thwarted by pathological self-reference. > I transforms it into what looks like an equivalent question. > > So within Linz's faulty assumption that the only possible way to create > a universal halt decider is to directly ask the question: > Does the input program halt on its input? > The Linz proof is correct. > > When we realize that this assumption is faulty and instead ask the > question: Was the execution of the input program on its input aborted? > You're asking a different question. > > Then creating a universal halt decider is no longer "proved" to be > impossible on the basis of the conventional self-referential halting > problem counter-examples. > Linz proved the a halt decider cannot be a Turing machine. Not that no halt decider is possible. You've managed to smuggle into H information about whether H is called directly or not. So far, no-one has called you out on it, so you're doing well. > > The halt decider either detects non-halting behavior and reports it or > allows the input program to terminate on its own. > Sure. The details of the infinite loop detection aren't important here.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 12:32 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <lMWdnb1_gMe8XwzCnZ2dnUU7-SfNnZ2d@giganews.com> |
| In reply to | #24125 |
On 10/22/2020 12:27 PM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: >> On 10/22/2020 11:56 AM, Malcolm McLean wrote: >>> On Thursday, 22 October 2020 at 17:38:49 UTC+1, olcott wrote: >>>> On 10/22/2020 10:25 AM, Mike Terry wrote: >>>>> On 22/10/2020 15:36, olcott wrote: >>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>> >>>>>> The end result of this slight change is that the halting problem can no >>>>>> longer be shown to be undecidable. >>>>>> >>>>> >>>>> It is suspicious that in none of this have you ever stated what is >>>>> actually wrong in the Linz proof. >>>> When the halting problem is defined as: >>>> bool Does_It_Halt(u32 P, u32 I) >>>> another program can be constructed on the basis of Does_It_Halt() that >>>> does the opposite of whatever Does_It_Halt() decides. >>>> >>>> When the halting problem is defined as: >>>> bool Was_Its_Execution_Aborted(u32 P, u32 I) >>>> >>>> another program CANNOT be constructed on the basis of >>>> Was_Its_Execution_Aborted() that does the opposite of whatever >>>> Was_Its_Execution_Aborted() decides. >>>> >>> As I said, you're right. If we change the question from "will the program >>> halt?" to "will DebugTrace raise an abortion anywhere on the call stack?" >>> the paradox goes away. >>> >>> I'll leave it to others to explain why this only seems to refute the LInz >>> proof that halting is undecideable. >>> >> It refutes the general assertion that the halting problem is undecidable >> by showing how the halting question can be transformed into an >> equivalent question that cannot be thwarted by pathological self-reference. >> > I transforms it into what looks like an equivalent question. >> >> So within Linz's faulty assumption that the only possible way to create >> a universal halt decider is to directly ask the question: >> Does the input program halt on its input? >> The Linz proof is correct. >> >> When we realize that this assumption is faulty and instead ask the >> question: Was the execution of the input program on its input aborted? >> > You're asking a different question. >> >> Then creating a universal halt decider is no longer "proved" to be >> impossible on the basis of the conventional self-referential halting >> problem counter-examples. >> > Linz proved the a halt decider cannot be a Turing machine. Not that no > halt decider is possible. You've managed to smuggle into H information > about whether H is called directly or not. So far, no-one has called you > out on it, so you're doing well. >> >> The halt decider either detects non-halting behavior and reports it or >> allows the input program to terminate on its own. >> > Sure. The details of the infinite loop detection aren't important here. > 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 18:33 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <TnjkH.258722$ZL3.237978@fx33.am4> |
| In reply to | #24127 |
On 22/10/2020 18:32, olcott wrote: > On 10/22/2020 12:27 PM, Malcolm McLean wrote: >> On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: >>> On 10/22/2020 11:56 AM, Malcolm McLean wrote: >>>> On Thursday, 22 October 2020 at 17:38:49 UTC+1, olcott wrote: >>>>> On 10/22/2020 10:25 AM, Mike Terry wrote: >>>>>> On 22/10/2020 15:36, olcott wrote: >>>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote: >>>>> >>>>>>> The end result of this slight change is that the halting problem can no >>>>>>> longer be shown to be undecidable. >>>>>>> >>>>>> >>>>>> It is suspicious that in none of this have you ever stated what is >>>>>> actually wrong in the Linz proof. >>>>> When the halting problem is defined as: >>>>> bool Does_It_Halt(u32 P, u32 I) >>>>> another program can be constructed on the basis of Does_It_Halt() that >>>>> does the opposite of whatever Does_It_Halt() decides. >>>>> >>>>> When the halting problem is defined as: >>>>> bool Was_Its_Execution_Aborted(u32 P, u32 I) >>>>> >>>>> another program CANNOT be constructed on the basis of >>>>> Was_Its_Execution_Aborted() that does the opposite of whatever >>>>> Was_Its_Execution_Aborted() decides. >>>>> >>>> As I said, you're right. If we change the question from "will the program >>>> halt?" to "will DebugTrace raise an abortion anywhere on the call stack?" >>>> the paradox goes away. >>>> >>>> I'll leave it to others to explain why this only seems to refute the LInz >>>> proof that halting is undecideable. >>>> >>> It refutes the general assertion that the halting problem is undecidable >>> by showing how the halting question can be transformed into an >>> equivalent question that cannot be thwarted by pathological self-reference. >>> >> I transforms it into what looks like an equivalent question. >>> >>> So within Linz's faulty assumption that the only possible way to create >>> a universal halt decider is to directly ask the question: >>> Does the input program halt on its input? >>> The Linz proof is correct. >>> >>> When we realize that this assumption is faulty and instead ask the >>> question: Was the execution of the input program on its input aborted? >>> >> You're asking a different question. >>> >>> Then creating a universal halt decider is no longer "proved" to be >>> impossible on the basis of the conventional self-referential halting >>> problem counter-examples. >>> >> Linz proved the a halt decider cannot be a Turing machine. Not that no >> halt decider is possible. You've managed to smuggle into H information >> about whether H is called directly or not. So far, no-one has called you >> out on it, so you're doing well. >>> >>> The halt decider either detects non-halting behavior and reports it or >>> allows the input program to terminate on its own. >>> >> Sure. The details of the infinite loop detection aren't important here. >> > > 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. I am calling TROLL at this point. Move on, nothing to see here. /Flibble -- ¬
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-22 10:58 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <876dec59-2ed5-40a7-8860-d2010ea7a568n@googlegroups.com> |
| In reply to | #24127 |
On Thursday, 22 October 2020 at 18:32:25 UTC+1, olcott wrote: > On 10/22/2020 12:27 PM, Malcolm McLean wrote: > > On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: > >> On 10/22/2020 11:56 AM, Malcolm McLean wrote: > > >> It refutes the general assertion that the halting problem is undecidable > >> by showing how the halting question can be transformed into an > >> equivalent question that cannot be thwarted by pathological self-reference. > >> > > I transforms it into what looks like an equivalent question. > > 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. > Sounds reasonable, doesn't it? As I said, if you want H to make the correct call on H_Hat, you have to smuggle into H the information about whether it is being called directly or through H_Hat. You appear to have done that quite well. People are distracted because you don't say how DebugTrace detects the "no- halt" condition, but that's not relevant here.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 13:19 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <386dnS6ESaiBUAzCnZ2dnUU7-LPNnZ2d@giganews.com> |
| In reply to | #24133 |
On 10/22/2020 12:58 PM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 18:32:25 UTC+1, olcott wrote: >> On 10/22/2020 12:27 PM, Malcolm McLean wrote: >>> On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: >>>> On 10/22/2020 11:56 AM, Malcolm McLean wrote: >> >>>> It refutes the general assertion that the halting problem is undecidable >>>> by showing how the halting question can be transformed into an >>>> equivalent question that cannot be thwarted by pathological self-reference. >>>> >>> I transforms it into what looks like an equivalent question. >> >> 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. >> > Sounds reasonable, doesn't it? Most people here have not gotten anywhere near the point where it seems that what I am saying is reasonable. They are all stuck on I know that you must be wrong because I really really believe that you are wrong therefore there is no need to pay any attention to what you say. > As I said, if you want H to make the correct call > on H_Hat, you have to smuggle into H the information about whether it is > being called directly or through H_Hat. You appear to have done that quite well. > > People are distracted because you don't say how DebugTrace detects the "no- > halt" condition, but that's not relevant here. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 13:30 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <a9CdnUh-F6tJUgzCnZ2dnUU7-TvNnZ2d@giganews.com> |
| In reply to | #24133 |
On 10/22/2 020 12:58 PM, Malcolm McLean wrote: > On Thursday, 22 October 2020 at 18:32:25 UTC+1, olcott wrote: >> On 10/22/2020 12:27 PM, Malcolm McLean wrote: >>> On Thursday, 22 October 2020 at 18:09:33 UTC+1, olcott wrote: >>>> On 10/22/2020 11:56 AM, Malcolm McLean wrote: >> >>>> It refutes the general assertion that the halting problem is undecidable >>>> by showing how the halting question can be transformed into an >>>> equivalent question that cannot be thwarted by pathological self-reference. >>>> >>> I transforms it into what looks like an equivalent question. >> >> 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. >> > Sounds reasonable, doesn't it? As I said, if you want H to make the correct call > on H_Hat, you have to smuggle into H the information about whether it is > being called directly or through H_Hat. You appear to have done that quite well. > Executing von Neumann architecture machine in DebugStep() mode or executing a UTM inside another UTM is a perfectly legitimate thing to do. By doing this a halt decider can directly see all the relevant details. > People are distracted because you don't say how DebugTrace detects the "no- > halt" condition, but that's not relevant here. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
Page 3 of 25 — ← Prev page 1 2 [3] 4 5 … 25 Next page →
Back to top | Article view | comp.theory
csiph-web