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 14 of 25 — ← Prev page 1 … 12 13 [14] 15 16 … 25 Next page →
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 01:15 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87v9f01ntl.fsf@bsb.me.uk> |
| In reply to | #24265 |
olcott <NoOne@NoWhere.com> writes: > On 10/23/2020 6:27 PM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> A program that was intentionally designed to do the opposite of what >>> its halt decider decided that it would do is paradoxical in the sense >>> that like other paradoxes it is undecidable. >> >> Neither is undecidable. I know this is just you not knowing what the >> words mean, but I am too tired to try to explain them to you again. I >> just want other people to know that this remark is wrong. The halting >> (or not) of any finite set of programs is "decidable" though computable >> is a better term for technical reasons. If anyone else wants to know >> why, ask away. >> > > I already found the paper that answers why. Yes every finite machine's > algorithm is decidable if one is willing to wait a googleplex number > of years past the heat death of the universe. Sounds like the wrong paper. Every finite set is decidable for a simple and rather trivial reason. Does it matter? Not really. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 16:46 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87h7ql54ic.fsf@bsb.me.uk> |
| In reply to | #24192 |
olcott <NoOne@NoWhere.com> writes:
> On 10/22/2020 11:00 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 10/22/2020 8:50 PM, Ben Bacarisse wrote:
<cut>
>>>> You, two years ago:
>>>>
>>>> "I am waiting to encode the UTM in C++ so that I can actually execute
>>>> H on the input pair: (Ĥ, Ĥ). This should take a week or two. It is not
>>>> a universal halt decider, yet it is exactly and precisely the Peter
>>>> Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis
>>>> of Ĥ actually deciding itself."
>>>>
>>>> No x86 code. No programs aborting others. No memory being released.
>>>> No changed questions. Just Turing machines H and H^ exactly as in Linz
>>>> doing something incredible! Don't you just wish you really had those
>>>> two Turing machines so you could post them and stun your critics? What
>>>> a shame you never did.
>>>
>>> My current claim that I have already provided an unequivocal
>>> refutation ALL of the conventional self-referential halting problem
>>> proofs and this naturally takes precedence over all of your lesser
>>> points above.
>>
>> You don't have what you claimed to have. That's why you will never post
>> it.
>>
>>> There is a simple and direct path to a correct rebuttal of my current
>>> claim if and only if I am incorrect.
>>
>> Yes there is. Here are H and H_Hat with some of the noise removed:
>>
>> void H(u32 M, u32 N)
>> {
>> if (DebugTrace(M, N))
>> MOV_EAX_0 // M(N) would not otherwise terminate
>> else
>> MOV_EAX_1 // M(N) has terminated
>> HALT
>> }
>>
>
> Since I strive for complete honestly I do have to say this this is a
> clear improvement.
Except you didn't have what you said you had two years ago, did you?
That was a big lie (or you were simply mistaken and the lies came later
when you doubled down -- I can't tell which).
>> void H_Hat(u32 M)
>> {
>> if (!DebugTrace(M, M))
>> HERE: goto HERE;
>> HALT
>> }
<cut>
>> Now, since you refuse to say what DebugTrace(H_Hat, H_Hat) returns (I
>> don't think you know yet), we need to consider both cases:
>
> I have known for 3.5 years. We discussed this at great length yet you
> were so sure that I must be wrong that you paid no attention at all.
Don't be silly. I wanted to know something (Mike Terry and I do now)
and you refused to say. I paid as much attention as the lack of
information required.
I will come clean, though. I don't believe you. I don't think you have
run a finished version of DebugTrace on (H_Hat, H_Hat) and got a
definitive answer. That's why you won't say.
>> When DebugTrace(H_Hat, H_Hat) == 1 the two computations execute like this:
>>
>> H(H_Hat, H_Hat):
>> MOV_EAX_0 // H_Hat(H_Hat) would not otherwise terminate
>> HALT
>>
>> H_Hat(H_Hat):
>> HALT
>>
>> and when DebugTrace(H_Hat, H_Hat) == 0 they execute
>>
>> H(H_Hat, H_Hat):
>> MOV_EAX_1 // H_Hat(H_Hat) has terminated
>> HALT
>>
>> H_Hat(H_Hat):
>> HERE: goto HERE;
>>
>> Sure looks like H gets the wrong answer to me.
>
> You actually did quite well in analyzing the above except for one very
> glaring exception. One of the two return values from DebugTrace() is
> correct.
Since you get to define what it does, you alone get to say what the
correct return from DebugTrace(H_Hat, H_Hat) is. I don't see why you
think I disagree with that. The problem is that H(H_Hat, H_Hat) is not
correct, no matter what DebugTrace(H_Hat, H_Hat) is. And if that is not
the whole point, what have you been banging on about all this time?
And remember, H_Hat is still not in the correct relationship with H. It
just so happens that H(H_Hat, H_Hat) is wrong despite this, but you
should fix it nonetheless.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 12:36 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <5pOdneEOcKUAiQ7CnZ2dnUU7-SnNnZ2d@giganews.com> |
| In reply to | #24215 |
On 10/23/2020 10:46 AM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 10/22/2020 11:00 PM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 10/22/2020 8:50 PM, Ben Bacarisse wrote:
> <cut>
>>>>> You, two years ago:
>>>>>
>>>>> "I am waiting to encode the UTM in C++ so that I can actually execute
>>>>> H on the input pair: (Ĥ, Ĥ). This should take a week or two. It is not
>>>>> a universal halt decider, yet it is exactly and precisely the Peter
>>>>> Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis
>>>>> of Ĥ actually deciding itself."
>>>>>
>>>>> No x86 code. No programs aborting others. No memory being released.
>>>>> No changed questions. Just Turing machines H and H^ exactly as in Linz
>>>>> doing something incredible! Don't you just wish you really had those
>>>>> two Turing machines so you could post them and stun your critics? What
>>>>> a shame you never did.
>>>>
>>>> My current claim that I have already provided an unequivocal
>>>> refutation ALL of the conventional self-referential halting problem
>>>> proofs and this naturally takes precedence over all of your lesser
>>>> points above.
>>>
>>> You don't have what you claimed to have. That's why you will never post
>>> it.
>>>
>>>> There is a simple and direct path to a correct rebuttal of my current
>>>> claim if and only if I am incorrect.
>>>
>>> Yes there is. Here are H and H_Hat with some of the noise removed:
>>>
>>> void H(u32 M, u32 N)
>>> {
>>> if (DebugTrace(M, N))
>>> MOV_EAX_0 // M(N) would not otherwise terminate
>>> else
>>> MOV_EAX_1 // M(N) has terminated
>>> HALT
>>> }
>>>
>>
>> Since I strive for complete honestly I do have to say this this is a
>> clear improvement.
>
> Except you didn't have what you said you had two years ago, did you?
> That was a big lie (or you were simply mistaken and the lies came later
> when you doubled down -- I can't tell which).
>
>>> void H_Hat(u32 M)
>>> {
>>> if (!DebugTrace(M, M))
>>> HERE: goto HERE;
>>> HALT
>>> }
> <cut>
>>> Now, since you refuse to say what DebugTrace(H_Hat, H_Hat) returns (I
>>> don't think you know yet), we need to consider both cases:
>>
>> I have known for 3.5 years. We discussed this at great length yet you
>> were so sure that I must be wrong that you paid no attention at all.
>
> Don't be silly. I wanted to know something (Mike Terry and I do now)
> and you refused to say. I paid as much attention as the lack of
> information required.
>
> I will come clean, though. I don't believe you. I don't think you have
> run a finished version of DebugTrace on (H_Hat, H_Hat) and got a
> definitive answer. That's why you won't say.
>
>>> When DebugTrace(H_Hat, H_Hat) == 1 the two computations execute like this:
>>>
>>> H(H_Hat, H_Hat):
>>> MOV_EAX_0 // H_Hat(H_Hat) would not otherwise terminate
>>> HALT
>>>
>>> H_Hat(H_Hat):
>>> HALT
>>>
>>> and when DebugTrace(H_Hat, H_Hat) == 0 they execute
>>>
>>> H(H_Hat, H_Hat):
>>> MOV_EAX_1 // H_Hat(H_Hat) has terminated
>>> HALT
>>>
>>> H_Hat(H_Hat):
>>> HERE: goto HERE;
>>>
>>> Sure looks like H gets the wrong answer to me.
>>
>> You actually did quite well in analyzing the above except for one very
>> glaring exception. One of the two return values from DebugTrace() is
>> correct.
>
> Since you get to define what it does, you alone get to say what the
> correct return from DebugTrace(H_Hat, H_Hat) is. I don't see why you
> think I disagree with that. The problem is that H(H_Hat, H_Hat) is not
> correct, no matter what DebugTrace(H_Hat, H_Hat) is. And if that is not
> the whole point, what have you been banging on about all this time?
> And remember, H_Hat is still not in the correct relationship with H. It
> just so happens that H(H_Hat, H_Hat) is wrong despite this, but you
> should fix it nonetheless.
>
Sure it is. DebugTrace() <is> the ⊢* state transition code.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 01:05 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <877drg32uc.fsf@bsb.me.uk> |
| In reply to | #24235 |
olcott <NoOne@NoWhere.com> writes:
> On 10/23/2020 10:46 AM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 10/22/2020 11:00 PM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 10/22/2020 8:50 PM, Ben Bacarisse wrote:
>> <cut>
>>>>>> You, two years ago:
>>>>>>
>>>>>> "I am waiting to encode the UTM in C++ so that I can actually execute
>>>>>> H on the input pair: (Ĥ, Ĥ). This should take a week or two. It is not
>>>>>> a universal halt decider, yet it is exactly and precisely the Peter
>>>>>> Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis
>>>>>> of Ĥ actually deciding itself."
>>>>>>
>>>>>> No x86 code. No programs aborting others. No memory being released.
>>>>>> No changed questions. Just Turing machines H and H^ exactly as in Linz
>>>>>> doing something incredible! Don't you just wish you really had those
>>>>>> two Turing machines so you could post them and stun your critics? What
>>>>>> a shame you never did.
>>>>>
>>>>> My current claim that I have already provided an unequivocal
>>>>> refutation ALL of the conventional self-referential halting problem
>>>>> proofs and this naturally takes precedence over all of your lesser
>>>>> points above.
>>>>
>>>> You don't have what you claimed to have. That's why you will never post
>>>> it.
>>>>
>>>>> There is a simple and direct path to a correct rebuttal of my current
>>>>> claim if and only if I am incorrect.
>>>>
>>>> Yes there is. Here are H and H_Hat with some of the noise removed:
>>>>
>>>> void H(u32 M, u32 N)
>>>> {
>>>> if (DebugTrace(M, N))
>>>> MOV_EAX_0 // M(N) would not otherwise terminate
>>>> else
>>>> MOV_EAX_1 // M(N) has terminated
>>>> HALT
>>>> }
>>>>
>>>
>>> Since I strive for complete honestly I do have to say this this is a
>>> clear improvement.
>>
>> Except you didn't have what you said you had two years ago, did you?
>> That was a big lie (or you were simply mistaken and the lies came later
>> when you doubled down -- I can't tell which).
>>
>>>> void H_Hat(u32 M)
>>>> {
>>>> if (!DebugTrace(M, M))
>>>> HERE: goto HERE;
>>>> HALT
>>>> }
>> <cut>
>>>> Now, since you refuse to say what DebugTrace(H_Hat, H_Hat) returns (I
>>>> don't think you know yet), we need to consider both cases:
>>>
>>> I have known for 3.5 years. We discussed this at great length yet you
>>> were so sure that I must be wrong that you paid no attention at all.
>>
>> Don't be silly. I wanted to know something (Mike Terry and I do now)
>> and you refused to say. I paid as much attention as the lack of
>> information required.
>>
>> I will come clean, though. I don't believe you. I don't think you have
>> run a finished version of DebugTrace on (H_Hat, H_Hat) and got a
>> definitive answer. That's why you won't say.
>>
>>>> When DebugTrace(H_Hat, H_Hat) == 1 the two computations execute like this:
>>>>
>>>> H(H_Hat, H_Hat):
>>>> MOV_EAX_0 // H_Hat(H_Hat) would not otherwise terminate
>>>> HALT
>>>>
>>>> H_Hat(H_Hat):
>>>> HALT
>>>>
>>>> and when DebugTrace(H_Hat, H_Hat) == 0 they execute
>>>>
>>>> H(H_Hat, H_Hat):
>>>> MOV_EAX_1 // H_Hat(H_Hat) has terminated
>>>> HALT
>>>>
>>>> H_Hat(H_Hat):
>>>> HERE: goto HERE;
>>>>
>>>> Sure looks like H gets the wrong answer to me.
>>>
>>> You actually did quite well in analyzing the above except for one very
>>> glaring exception. One of the two return values from DebugTrace() is
>>> correct.
>>
>> Since you get to define what it does, you alone get to say what the
>> correct return from DebugTrace(H_Hat, H_Hat) is. I don't see why you
>> think I disagree with that. The problem is that H(H_Hat, H_Hat) is not
>> correct, no matter what DebugTrace(H_Hat, H_Hat) is. And if that is not
>> the whole point, what have you been banging on about all this time?
I don't have time for the wave of nonsense that's come over this
newsgroup so I was going to say that I would only concentrate on this
sub-thread, since this is where I show that you are wrong, but when I
eventually get round to this post, I see you have nothing to say!
That's fine by the way. I'd prefer to leave it like this. People can
read your posts and they can read this one and make up their own minds.
>> And remember, H_Hat is still not in the correct relationship with H. It
>> just so happens that H(H_Hat, H_Hat) is wrong despite this, but you
>> should fix it nonetheless.
>
> Sure it is. DebugTrace() <is> the ⊢* state transition code.
I know what you mean by this poetic remark (you can't mean it literally
because ⊦ is about Turing machines) and if I thought you'd pay any
attention I'd fix it for you myself. But it suits me even better that
you have an H_Hat (supposedly based on Linz's) that makes no reference
to H! It makes the surface appearance match the deeper truth.
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 19:15 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <NoKdnb_cPOGy7w7CnZ2dnUU7-cudnZ2d@giganews.com> |
| In reply to | #24274 |
On 10/23/2020 7:05 PM, Ben Bacarisse wrote:
> olcott <NoOne@NoWhere.com> writes:
>
>> On 10/23/2020 10:46 AM, Ben Bacarisse wrote:
>>> olcott <NoOne@NoWhere.com> writes:
>>>
>>>> On 10/22/2020 11:00 PM, Ben Bacarisse wrote:
>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>
>>>>>> On 10/22/2020 8:50 PM, Ben Bacarisse wrote:
>>> <cut>
>>>>>>> You, two years ago:
>>>>>>>
>>>>>>> "I am waiting to encode the UTM in C++ so that I can actually execute
>>>>>>> H on the input pair: (Ĥ, Ĥ). This should take a week or two. It is not
>>>>>>> a universal halt decider, yet it is exactly and precisely the Peter
>>>>>>> Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis
>>>>>>> of Ĥ actually deciding itself."
>>>>>>>
>>>>>>> No x86 code. No programs aborting others. No memory being released.
>>>>>>> No changed questions. Just Turing machines H and H^ exactly as in Linz
>>>>>>> doing something incredible! Don't you just wish you really had those
>>>>>>> two Turing machines so you could post them and stun your critics? What
>>>>>>> a shame you never did.
>>>>>>
>>>>>> My current claim that I have already provided an unequivocal
>>>>>> refutation ALL of the conventional self-referential halting problem
>>>>>> proofs and this naturally takes precedence over all of your lesser
>>>>>> points above.
>>>>>
>>>>> You don't have what you claimed to have. That's why you will never post
>>>>> it.
>>>>>
>>>>>> There is a simple and direct path to a correct rebuttal of my current
>>>>>> claim if and only if I am incorrect.
>>>>>
>>>>> Yes there is. Here are H and H_Hat with some of the noise removed:
>>>>>
>>>>> void H(u32 M, u32 N)
>>>>> {
>>>>> if (DebugTrace(M, N))
>>>>> MOV_EAX_0 // M(N) would not otherwise terminate
>>>>> else
>>>>> MOV_EAX_1 // M(N) has terminated
>>>>> HALT
>>>>> }
>>>>>
>>>>
>>>> Since I strive for complete honestly I do have to say this this is a
>>>> clear improvement.
>>>
>>> Except you didn't have what you said you had two years ago, did you?
>>> That was a big lie (or you were simply mistaken and the lies came later
>>> when you doubled down -- I can't tell which).
>>>
>>>>> void H_Hat(u32 M)
>>>>> {
>>>>> if (!DebugTrace(M, M))
>>>>> HERE: goto HERE;
>>>>> HALT
>>>>> }
>>> <cut>
>>>>> Now, since you refuse to say what DebugTrace(H_Hat, H_Hat) returns (I
>>>>> don't think you know yet), we need to consider both cases:
>>>>
>>>> I have known for 3.5 years. We discussed this at great length yet you
>>>> were so sure that I must be wrong that you paid no attention at all.
>>>
>>> Don't be silly. I wanted to know something (Mike Terry and I do now)
>>> and you refused to say. I paid as much attention as the lack of
>>> information required.
>>>
>>> I will come clean, though. I don't believe you. I don't think you have
>>> run a finished version of DebugTrace on (H_Hat, H_Hat) and got a
>>> definitive answer. That's why you won't say.
>>>
>>>>> When DebugTrace(H_Hat, H_Hat) == 1 the two computations execute like this:
>>>>>
>>>>> H(H_Hat, H_Hat):
>>>>> MOV_EAX_0 // H_Hat(H_Hat) would not otherwise terminate
>>>>> HALT
>>>>>
>>>>> H_Hat(H_Hat):
>>>>> HALT
>>>>>
>>>>> and when DebugTrace(H_Hat, H_Hat) == 0 they execute
>>>>>
>>>>> H(H_Hat, H_Hat):
>>>>> MOV_EAX_1 // H_Hat(H_Hat) has terminated
>>>>> HALT
>>>>>
>>>>> H_Hat(H_Hat):
>>>>> HERE: goto HERE;
>>>>>
>>>>> Sure looks like H gets the wrong answer to me.
>>>>
>>>> You actually did quite well in analyzing the above except for one very
>>>> glaring exception. One of the two return values from DebugTrace() is
>>>> correct.
>>>
>>> Since you get to define what it does, you alone get to say what the
>>> correct return from DebugTrace(H_Hat, H_Hat) is. I don't see why you
>>> think I disagree with that. The problem is that H(H_Hat, H_Hat) is not
>>> correct, no matter what DebugTrace(H_Hat, H_Hat) is. And if that is not
>>> the whole point, what have you been banging on about all this time?
>
> I don't have time for the wave of nonsense that's come over this
> newsgroup so I was going to say that I would only concentrate on this
> sub-thread, since this is where I show that you are wrong, but when I
> eventually get round to this post, I see you have nothing to say!
>
> That's fine by the way. I'd prefer to leave it like this. People can
> read your posts and they can read this one and make up their own minds.
>
>>> And remember, H_Hat is still not in the correct relationship with H. It
>>> just so happens that H(H_Hat, H_Hat) is wrong despite this, but you
>>> should fix it nonetheless.
>>
>> Sure it is. DebugTrace() <is> the ⊢* state transition code.
>
> I know what you mean by this poetic remark (you can't mean it literally
> because ⊦ is about Turing machines) and if I thought you'd pay any
> attention I'd fix it for you myself. But it suits me even better that
> you have an H_Hat (supposedly based on Linz's) that makes no reference
> to H! It makes the surface appearance match the deeper truth.
>
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.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 01:29 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <87pn581n5s.fsf@bsb.me.uk> |
| In reply to | #24279 |
olcott <NoOne@NoWhere.com> writes:
> On 10/23/2020 7:05 PM, Ben Bacarisse wrote:
>> olcott <NoOne@NoWhere.com> writes:
>>
>>> On 10/23/2020 10:46 AM, Ben Bacarisse wrote:
>>>> olcott <NoOne@NoWhere.com> writes:
>>>>
>>>>> On 10/22/2020 11:00 PM, Ben Bacarisse wrote:
>>>>>> olcott <NoOne@NoWhere.com> writes:
>>>>>>
>>>>>>> On 10/22/2020 8:50 PM, Ben Bacarisse wrote:
>>>> <cut>
>>>>>>>> You, two years ago:
>>>>>>>>
>>>>>>>> "I am waiting to encode the UTM in C++ so that I can actually execute
>>>>>>>> H on the input pair: (Ĥ, Ĥ). This should take a week or two. It is not
>>>>>>>> a universal halt decider, yet it is exactly and precisely the Peter
>>>>>>>> Linz H and Ĥ, with H actually deciding input pair: (Ĥ, Ĥ) on the basis
>>>>>>>> of Ĥ actually deciding itself."
>>>>>>>>
>>>>>>>> No x86 code. No programs aborting others. No memory being released.
>>>>>>>> No changed questions. Just Turing machines H and H^ exactly as in Linz
>>>>>>>> doing something incredible! Don't you just wish you really had those
>>>>>>>> two Turing machines so you could post them and stun your critics? What
>>>>>>>> a shame you never did.
>>>>>>>
>>>>>>> My current claim that I have already provided an unequivocal
>>>>>>> refutation ALL of the conventional self-referential halting problem
>>>>>>> proofs and this naturally takes precedence over all of your lesser
>>>>>>> points above.
>>>>>>
>>>>>> You don't have what you claimed to have. That's why you will never post
>>>>>> it.
>>>>>>
>>>>>>> There is a simple and direct path to a correct rebuttal of my current
>>>>>>> claim if and only if I am incorrect.
>>>>>>
>>>>>> Yes there is. Here are H and H_Hat with some of the noise removed:
>>>>>>
>>>>>> void H(u32 M, u32 N)
>>>>>> {
>>>>>> if (DebugTrace(M, N))
>>>>>> MOV_EAX_0 // M(N) would not otherwise terminate
>>>>>> else
>>>>>> MOV_EAX_1 // M(N) has terminated
>>>>>> HALT
>>>>>> }
>>>>>>
>>>>>
>>>>> Since I strive for complete honestly I do have to say this this is a
>>>>> clear improvement.
>>>>
>>>> Except you didn't have what you said you had two years ago, did you?
>>>> That was a big lie (or you were simply mistaken and the lies came later
>>>> when you doubled down -- I can't tell which).
>>>>
>>>>>> void H_Hat(u32 M)
>>>>>> {
>>>>>> if (!DebugTrace(M, M))
>>>>>> HERE: goto HERE;
>>>>>> HALT
>>>>>> }
>>>> <cut>
>>>>>> Now, since you refuse to say what DebugTrace(H_Hat, H_Hat) returns (I
>>>>>> don't think you know yet), we need to consider both cases:
>>>>>
>>>>> I have known for 3.5 years. We discussed this at great length yet you
>>>>> were so sure that I must be wrong that you paid no attention at all.
>>>>
>>>> Don't be silly. I wanted to know something (Mike Terry and I do now)
>>>> and you refused to say. I paid as much attention as the lack of
>>>> information required.
>>>>
>>>> I will come clean, though. I don't believe you. I don't think you have
>>>> run a finished version of DebugTrace on (H_Hat, H_Hat) and got a
>>>> definitive answer. That's why you won't say.
>>>>
>>>>>> When DebugTrace(H_Hat, H_Hat) == 1 the two computations execute like this:
>>>>>>
>>>>>> H(H_Hat, H_Hat):
>>>>>> MOV_EAX_0 // H_Hat(H_Hat) would not otherwise terminate
>>>>>> HALT
>>>>>>
>>>>>> H_Hat(H_Hat):
>>>>>> HALT
>>>>>>
>>>>>> and when DebugTrace(H_Hat, H_Hat) == 0 they execute
>>>>>>
>>>>>> H(H_Hat, H_Hat):
>>>>>> MOV_EAX_1 // H_Hat(H_Hat) has terminated
>>>>>> HALT
>>>>>>
>>>>>> H_Hat(H_Hat):
>>>>>> HERE: goto HERE;
>>>>>>
>>>>>> Sure looks like H gets the wrong answer to me.
>>>>>
>>>>> You actually did quite well in analyzing the above except for one very
>>>>> glaring exception. One of the two return values from DebugTrace() is
>>>>> correct.
>>>>
>>>> Since you get to define what it does, you alone get to say what the
>>>> correct return from DebugTrace(H_Hat, H_Hat) is. I don't see why you
>>>> think I disagree with that. The problem is that H(H_Hat, H_Hat) is not
>>>> correct, no matter what DebugTrace(H_Hat, H_Hat) is. And if that is not
>>>> the whole point, what have you been banging on about all this time?
>>
>> I don't have time for the wave of nonsense that's come over this
>> newsgroup so I was going to say that I would only concentrate on this
>> sub-thread, since this is where I show that you are wrong, but when I
>> eventually get round to this post, I see you have nothing to say!
Nothing?
>> That's fine by the way. I'd prefer to leave it like this. People can
>> read your posts and they can read this one and make up their own
>> minds.
>>
>>>> And remember, H_Hat is still not in the correct relationship with H. It
>>>> just so happens that H(H_Hat, H_Hat) is wrong despite this, but you
>>>> should fix it nonetheless.
>>>
>>> Sure it is. DebugTrace() <is> the ⊢* state transition code.
>>
>> I know what you mean by this poetic remark (you can't mean it literally
>> because ⊦ is about Turing machines) and if I thought you'd pay any
>> attention I'd fix it for you myself. But it suits me even better that
>> you have an H_Hat (supposedly based on Linz's) that makes no reference
>> to H! It makes the surface appearance match the deeper truth.
>>
>
> 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.
Is this a cut and paste? It does not address what's wrong with your
published code (outlined further up), and it does not address the point
about H_Hat not making reference to H. In fact, it appears not to be
about your publish code at all, but about Turing machines.
Have you completely abandoned the project of showing an H/H_Hat pair,
related as in Linz, but where (unlike in Linz) the computation H(H_Hat,
H_Hat) gives the correct answer? If so, what do you now claim to have
that is supposedly significant?
--
Ben.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-22 23:41 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <7iskH.112285$lZ.97154@fx12.iad> |
| In reply to | #24156 |
On 10/22/20 4:24 PM, olcott wrote: > > The more general claim that I made is that I would show exactly how the > conventional self-referential halting problem proof counter-examples do > not prove that the halting problem is undecidable. > > This has now been totally fulfilled. > > As soon as you acknowledge this we can move on to talking about other > aspects. You ave done NO such thing. You have shown that a DIFFERENT, non-equivalent sort of halting problem statement can't be disproven by a Linz like system. Unfortunately, the original halting problem (that you haven't touched, and even seems to be that you admit the proof is actually valid for) has some mathematical interesting uses, while your revised statement has know known use, and without some major tightening of the conditions in it, is almost assuredly not to be mathematically interesting. A big part of this lack of interest is that detecting halting by simulating adds no information about the halting behavior above simply running the orginal machine and observing if it has halted.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-22 23:02 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <rpudnQoSPo5YyA_CnZ2dnUU7-VXNnZ2d@giganews.com> |
| In reply to | #24184 |
On 10/22/2020 10:41 PM, Richard Damon wrote: > On 10/22/20 4:24 PM, olcott wrote: >> >> The more general claim that I made is that I would show exactly how the >> conventional self-referential halting problem proof counter-examples do >> not prove that the halting problem is undecidable. >> >> This has now been totally fulfilled. >> >> As soon as you acknowledge this we can move on to talking about other >> aspects. > > You ave done NO such thing. You have shown that a DIFFERENT, > non-equivalent sort of halting problem statement can't be disproven by a > Linz like system. > > Unfortunately, the original halting problem (that you haven't touched, > and even seems to be that you admit the proof is actually valid for) has > some mathematical interesting uses, while your revised statement has > know known use, and without some major tightening of the conditions in > it, is almost assuredly not to be mathematically interesting. > When I said that the original proof is correct yet was based on a fundamentally incorrect assumption it is exactly the same thing as the statement that "cats bark" is correct when we assume that all cats are dogs. Perhaps it is easier to understand it when I say that the original proof is fundamentally incorrect because it is based on fundmentally incorrect assumptions. > A big part of this lack of interest is that detecting halting by > simulating adds no information about the halting behavior above simply > running the orginal machine and observing if it has halted. > This statement is incorrect. A halt decider can easily detect infinite loops when the program under test is executed in debug step mode. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Tim Woodall <news001@woodall.me.uk> |
|---|---|
| Date | 2020-10-23 07:05 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <rmtvc7$t4g$1@einstein.home.woodall.me.uk> |
| In reply to | #24187 |
On 2020-10-23, olcott <NoOne@NoWhere.com> wrote:
>
> This statement is incorrect. A halt decider can easily detect infinite
> loops when the program under test is executed in debug step mode.
>
Does the below function g() terminate?
N.B. this code is meant to be simple, not efficient.
int p(int n)
{
int p = 0;
int d;
if(n<=2)
return 0;
n--; //n is never increased therefore this function always returns a value less than its input
d = n;
while(d>2) //This loop always terminates as d or n decreases with each iteration and d<=n
{
d--;
p = n;
while(p >= d) //This loop always terminates as p decreases with each iteration
p -= d;
if(!p)
{
n--;
d = n;
}
}
return n;
}
void g()
{
int n = 6;
int p1 = n;
while( p(p1) + p(p1) >=n ) //Does this loop terminate?
{
p1 = p(p1); //p1 is always less than n
int p2 = p1;
while(p1 + p2 > n) //p2 monotonically decreases to zero and p1<n therefore this loop always terminates
p2 = p(p2);
if(p1+p2 == n)
{
n = n + 2;
p1 = n;
}
}
}
Does g terminate? (assuming ints never overflow)
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 08:38 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <wpGdndtdy4JAQQ_CnZ2dnUU7-cudnZ2d@giganews.com> |
| In reply to | #24193 |
On 10/23/2020 2:05 AM, Tim Woodall wrote:
> On 2020-10-23, olcott <NoOne@NoWhere.com> wrote:
>
>>
>> This statement is incorrect. A halt decider can easily detect infinite
>> loops when the program under test is executed in debug step mode.
>>
>
> Does the below function g() terminate?
>
> N.B. this code is meant to be simple, not efficient.
>
> int p(int n)
> {
> int p = 0;
> int d;
>
> if(n<=2)
> return 0;
>
> n--; //n is never increased therefore this function always returns a value less than its input
> d = n;
>
> while(d>2) //This loop always terminates as d or n decreases with each iteration and d<=n
> {
> d--;
>
> p = n;
>
> while(p >= d) //This loop always terminates as p decreases with each iteration
> p -= d;
>
> if(!p)
> {
> n--;
> d = n;
> }
> }
>
> return n;
> }
>
> void g()
> {
> int n = 6;
>
> int p1 = n;
>
> while( p(p1) + p(p1) >=n ) //Does this loop terminate?
> {
> p1 = p(p1); //p1 is always less than n
>
> int p2 = p1;
> while(p1 + p2 > n) //p2 monotonically decreases to zero and p1<n therefore this loop always terminates
> p2 = p(p2);
>
> if(p1+p2 == n)
> {
> n = n + 2;
> p1 = n;
> }
>
> }
> }
>
> Does g terminate? (assuming ints never overflow)
>
All that I have done is refuted the conventional self-referential
halting problem proofs that show that a universal halt decider is
impossible. I don't handle any difficult cases. I only handle the
impossible cases.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 11:02 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87d0196z0e.fsf@bsb.me.uk> |
| In reply to | #24187 |
olcott <NoOne@NoWhere.com> writes: > A halt decider can easily detect infinite loops when the program under > test is executed in debug step mode. For the simple (and common) definition of "infinite loops" that's right. A program loops (in this simple sense) when it enters a configuration it has previously been in (the configuration being the sum total of all the state that can affect the outcome). But a halt decider must be able to decide computations that don't terminate, but which don't "loop" in this naive sense. The word is also used as a slightly clumsy synonym for non-terminating, so if you want to be clear (ha!) you should avoid the word or specify the meaning when you use it as one form of "looping" is easily detectable but the other is impossible to detect. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 08:45 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <F46dnTLTdo8XQw_CnZ2dnUU7-L-dnZ2d@giganews.com> |
| In reply to | #24195 |
On 10/23/2020 5:02 AM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> A halt decider can easily detect infinite loops when the program under >> test is executed in debug step mode. > > For the simple (and common) definition of "infinite loops" that's right. > A program loops (in this simple sense) when it enters a configuration it > has previously been in (the configuration being the sum total of all the > state that can affect the outcome). But a halt decider must be able to > decide computations that don't terminate, but which don't "loop" in this > naive sense. > > The word is also used as a slightly clumsy synonym for non-terminating, > so if you want to be clear (ha!) you should avoid the word or specify > the meaning when you use it as one form of "looping" is easily > detectable but the other is impossible to detect. > What form of looping is literally impossible to detect? -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-23 15:56 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87y2jx56u3.fsf@bsb.me.uk> |
| In reply to | #24200 |
olcott <NoOne@NoWhere.com> writes: > On 10/23/2020 5:02 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: >> >>> A halt decider can easily detect infinite loops when the program under >>> test is executed in debug step mode. >> >> For the simple (and common) definition of "infinite loops" that's right. >> A program loops (in this simple sense) when it enters a configuration it >> has previously been in (the configuration being the sum total of all the >> state that can affect the outcome). But a halt decider must be able to >> decide computations that don't terminate, but which don't "loop" in this >> naive sense. >> >> The word is also used as a slightly clumsy synonym for non-terminating, >> so if you want to be clear (ha!) you should avoid the word or specify >> the meaning when you use it as one form of "looping" is easily >> detectable but the other is impossible to detect. > > What form of looping is literally impossible to detect? The sort where the computation never enters a configuration it has been in before. /Some/ instances of this type can be detected, but there is no effective procedure to detect them all. There /is/ an effective procedure for the other kind where a previously entered configuration is entered again. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 10:30 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <OcadnU_Id868ag_CnZ2dnUU7-WnNnZ2d@giganews.com> |
| In reply to | #24207 |
On 10/23/2020 9:56 AM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> On 10/23/2020 5:02 AM, Ben Bacarisse wrote: >>> olcott <NoOne@NoWhere.com> writes: >>> >>>> A halt decider can easily detect infinite loops when the program under >>>> test is executed in debug step mode. >>> >>> For the simple (and common) definition of "infinite loops" that's right. >>> A program loops (in this simple sense) when it enters a configuration it >>> has previously been in (the configuration being the sum total of all the >>> state that can affect the outcome). But a halt decider must be able to >>> decide computations that don't terminate, but which don't "loop" in this >>> naive sense. >>> >>> The word is also used as a slightly clumsy synonym for non-terminating, >>> so if you want to be clear (ha!) you should avoid the word or specify >>> the meaning when you use it as one form of "looping" is easily >>> detectable but the other is impossible to detect. >> >> What form of looping is literally impossible to detect? > > The sort where the computation never enters a configuration it has been > in before. /Some/ instances of this type can be detected, but there is > no effective procedure to detect them all. There /is/ an effective > procedure for the other kind where a previously entered configuration is > entered again. > None-the-less I have refuted all of the conventional self-referential halting problem proof counter-examples. Also it is well known that machines such as this cannot physically exist. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-24 00:32 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87o8ks34d0.fsf@bsb.me.uk> |
| In reply to | #24213 |
olcott <NoOne@NoWhere.com> writes: > On 10/23/2020 9:56 AM, Ben Bacarisse wrote: >> olcott <NoOne@NoWhere.com> writes: <cut> >>> What form of looping is literally impossible to detect? >> >> The sort where the computation never enters a configuration it has >> been in before. /Some/ instances of this type can be detected, but >> there is no effective procedure to detect them all. There /is/ an >> effective procedure for the other kind where a previously entered >> configuration is entered again. > > None-the-less I have refuted all of the conventional self-referential > halting problem proof counter-examples. You are alone in this belief. > Also it is well known that machines such as this cannot physically > exist. Of course. Halting for programs running on an x86 chip is theoretically decidable. Not sure why you think this matters. -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 18:36 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <MYSdnZBV8--N9A7CnZ2dnUU7-L-dnZ2d@giganews.com> |
| In reply to | #24264 |
On 10/23/2020 6:32 PM, Ben Bacarisse wrote: > olcott <NoOne@NoWhere.com> writes: > >> On 10/23/2020 9:56 AM, Ben Bacarisse wrote: >>> olcott <NoOne@NoWhere.com> writes: > <cut> >>>> What form of looping is literally impossible to detect? >>> >>> The sort where the computation never enters a configuration it has >>> been in before. /Some/ instances of this type can be detected, but >>> there is no effective procedure to detect them all. There /is/ an >>> effective procedure for the other kind where a previously entered >>> configuration is entered again. >> >> None-the-less I have refuted all of the conventional self-referential >> halting problem proof counter-examples. > > You are alone in this belief. > Maybe not. In any case I am objectively correct and it can be shown to anyone that is reasonably intelligent and not totally biased. >> Also it is well known that machines such as this cannot physically >> exist. > > Of course. Halting for programs running on an x86 chip is > theoretically decidable. Not sure why you think this matters. > -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-23 21:52 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <wNLkH.675946$AN2.624356@fx46.iad> |
| In reply to | #24213 |
On 10/23/20 11:30 AM, olcott wrote: > > Also it is well known that machines such as this cannot physically exist. Full capacity Turing Machines can not physically exist, as they have an infinite capacity tape. In the same way, the Natural Numbers can't 'physically' exist, as there are more of them the particles in the known universe. Note, that there IS a correlation on these two facts, the Logic System that describes Turing machines is 'complicated' enough deal with propositions about Natural Numbers. The Halting Problem is related to this, a number of theorems about the Natural Numbers can be expressed as Turing Machines, where if the Turing Machine halts, its output is a counter example to the theorem (disproving it), while if it can be shown to never halt, the theorem is true (and proof of non-halting is proof of the theorem). Thus, the existence of a true halt decider implies the provability of any theorem that can be formulated into a Turing Machine.
[toc] | [prev] | [next] | [standalone]
| From | Keith Thompson <Keith.S.Thompson+u@gmail.com> |
|---|---|
| Date | 2020-10-23 13:03 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <87d01890cp.fsf@nosuchdomain.example.com> |
| In reply to | #24187 |
olcott <NoOne@NoWhere.com> writes:
[SNIP]
The parent article was posted only to comp.theory. You deliberately
cross-posted your followup to comp.theory, comp.lang.c,
comp.lang.prolog, and comp.lang.c++. You've done that multiple
times.
Please stop doing that. You've already taken over comp.theory.
You're not discussing programming languages. Please stop polluting
other newsgroups where people are still trying to discuss programming
languages.
I expect you'll reply to this with some ridiculous excuse and
continue your misbehavior. If so, I will resume ignoring you.
And again, I ask everyone else replying to olcott's posts to remove
irrelevant newsgroups from your followups. I know it's annoying
to have to do that.
--
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Philips Healthcare
void Void(void) { Void(); } /* The recursive call of the void */
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 15:24 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <NqKdnWVNUZd6pg7CnZ2dnUU7-bHNnZ2d@giganews.com> |
| In reply to | #24247 |
On 10/23/2020 3:03 PM, Keith Thompson wrote: > olcott <NoOne@NoWhere.com> writes: > [SNIP] > > The parent article was posted only to comp.theory. You deliberately > cross-posted your followup to comp.theory, comp.lang.c, > comp.lang.prolog, and comp.lang.c++. You've done that multiple > times. > > Please stop doing that. You've already taken over comp.theory. > You're not discussing programming languages. Please stop polluting > other newsgroups where people are still trying to discuss programming > languages. > > I expect you'll reply to this with some ridiculous excuse and > continue your misbehavior. If so, I will resume ignoring you. > > And again, I ask everyone else replying to olcott's posts to remove > irrelevant newsgroups from your followups. I know it's annoying > to have to do that. > I will stop cross-posting as soon as: (1) It is accepted that I just correctly refuted the halting problem proofs. (2) It is proven that I did not correctly refute the halting problem proofs. This latter proof would be very easy if and only if I am incorrect and utterly impossible if I am correct. If a halt decider is defined to return a value that indicates that its input program halts and input program can be defined on the basis of the halt decider that does the opposite of whatever the halt decider decides. If a UTM executes an (already on the tape) input UTM. The halt decider UTM could 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. In this case the (already on the tape) input UTM cannot possibly do the opposite of what the halt decider UTM decided because it is no longer executing. This redefinition of the halt decider eliminates the undecidability of the halting problem. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-23 02:29 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ] |
| Message-ID | <ebf563ec-d07b-4eec-aa3d-35fa327e3d84n@googlegroups.com> |
| In reply to | #24184 |
On Friday, 23 October 2020 at 04:41:59 UTC+1, Richard Damon wrote: > > A big part of this lack of interest is that detecting halting by > simulating adds no information about the halting behavior above simply > running the orginal machine and observing if it has halted. > Exactly. What happens if we have a physical Turing machine? It's set up by a human supervisor, who waits to see if it halts. One possibility is that it will run out of tape, in which case he, probably rightly, concludes that it has got stuck in an infinite loop. Another possibility is that it takes a long time and he gets bored. Another possibility is that it halts normally. Assuming it doesn't halt normally, the machine is destroyed or switched off in some manner. It never runs forever. So in fact we have a pretty good, though not perfect, halt detector. But it's not a Turing machine. A Turing machine can't abort. PO is trying to get round this problem by saying that DebugTrace aborts the program this stepping through (which is possible), then shunts up the "abortion" state to H_Hat, which then aborts. That's not valid, of course. H_Hat can't abort itself or it's not a Turing machine. Remove the requirement that the halt detector be a Turing machine and the Linz proof fails. That's the basic point that seems to have been missed, and that's what PO is doing, though not so blatantly that most people have spotted the error.
[toc] | [prev] | [next] | [standalone]
Page 14 of 25 — ← Prev page 1 … 12 13 [14] 15 16 … 25 Next page →
Back to top | Article view | comp.theory
csiph-web