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 6 of 25 — ← Prev page 1 … 4 5 [6] 7 8 … 25 Next page →
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-10-24 23:14 +0100 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn28vl$78t$1@gioia.aioe.org> |
| In reply to | #24334 |
On 24/10/2020 20:01, olcott wrote:
>>> Infinite recursion on an actual UTM would never exhaust the stack.
>>> The key thing that no one ever noticed for 80 years is that none of
>>> the conventional self-referential halting problem proof
>>> counter-examples ever reach their undecidable state transitions.
>> The reason why no-one ever noticed such things is that the
>> "conventional" proofs are neither recursive [infinitely or otherwise]
> // M has address of H_Hat()
> void H_Hat(u32 M)
> {
> if (DebugTrace(M, M)) // M(M) Aborted?
[...]
> Since DebugTrace(M, M) executes its input one step at a time it is
> obvious that the first line of H_Hat() is infinitely recursive.
That's not what "recursive" means. If you can't sort out what
you mean and express it clearly, it's small wonder that the rest of us
can't do it for you, and that you seem not to understand what we are
trying to tell you.
> There may be other ways to decide halting [...].
As you have been told many times, there are many other ways
to show that there is no general algorithm to decide this; which is
different from any given problem being undecidable. You have been
referred several times to the "Busy Beaver" problem, which might
just possibly give you a clue as to what is happening with the HP.
Meanwhile, I commend unto you once again ...
>> nor self-referential. This would be clearer to you if you stopped
>> calling things "H" and "H_Hat" and instead distinguished [eg] "H.src"
>> and "H.exe", "H_Hat.src" and "H_Hat.exe", where the ".exe" files are
>> the result of compiling the corresponding ".src" source files. [...]
... that your articles would be much less obfuscated if you
would distinguish clearly between source files and executables, or
between TMs and descriptions thereof. That you don't is either a
cause of your confusions or a deliberate choice that you don't want
to express yourself clearly. Your decision.
--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Sinding
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-24 17:35 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <er2dnZqNJ5TdMQnCnZ2dnUU7-RvNnZ2d@giganews.com> |
| In reply to | #24359 |
On 10/24/2020 5:14 PM, Andy Walker wrote:
> On 24/10/2020 20:01, olcott wrote:
>>>> Infinite recursion on an actual UTM would never exhaust the stack.
>>>> The key thing that no one ever noticed for 80 years is that none of
>>>> the conventional self-referential halting problem proof
>>>> counter-examples ever reach their undecidable state transitions.
>>> The reason why no-one ever noticed such things is that the
>>> "conventional" proofs are neither recursive [infinitely or otherwise]
>> // M has address of H_Hat()
>> void H_Hat(u32 M)
>> {
>> if (DebugTrace(M, M)) // M(M) Aborted?
> [...]
>> Since DebugTrace(M, M) executes its input one step at a time it is
>> obvious that the first line of H_Hat() is infinitely recursive.
>
> That's not what "recursive" means. If you can't sort out what
> you mean and express it clearly, it's small wonder that the rest of us
> can't do it for you, and that you seem not to understand what we are
> trying to tell you.
Most computer programming languages support recursion by allowing a
function to call itself from within its own code.
https://en.wikipedia.org/wiki/Recursion_(computer_science)
When a software function calls itself this is recursive invocation.
When When a software function calls another function that calls itself
this indirect recursive invocation.
When H_Hat() calls
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
unless the above function aborts its execution trace of H_Hat() it will
continue to execute forever, UTMs do not have any stack depth limit.
The only reason that H_Hat(H_Hat) ever terminates is that
Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat)
aborted it execution.
>> There may be other ways to decide halting [...].
>
> As you have been told many times, there are many other ways
> to show that there is no general algorithm to decide this; which is
> different from any given problem being undecidable. You have been
Undecided is not at all the same thing as undecidable.
> referred several times to the "Busy Beaver" problem, which might
> just possibly give you a clue as to what is happening with the HP.
>
> Meanwhile, I commend unto you once again ...
>
>>> nor self-referential. This would be clearer to you if you stopped
>>> calling things "H" and "H_Hat" and instead distinguished [eg] "H.src"
>>> and "H.exe", "H_Hat.src" and "H_Hat.exe", where the ".exe" files are
>>> the result of compiling the corresponding ".src" source files. [...]
>
> ... that your articles would be much less obfuscated if you
> would distinguish clearly between source files and executables, or
> between TMs and descriptions thereof. That you don't is either a
> cause of your confusions or a deliberate choice that you don't want
> to express yourself clearly. Your decision.
All of the C code that I have provided is ultimately anchored in the x86
machine language that is generated with the Microsoft C compiler. This
is the byte for byte exact Turing machine Description language of my
machines.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Andy Walker <anw@cuboid.co.uk> |
|---|---|
| Date | 2020-10-25 16:33 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn49d3$1k7f$1@gioia.aioe.org> |
| In reply to | #24364 |
On 24/10/2020 23:35, olcott wrote:
>>> if (DebugTrace(M, M)) // M(M) Aborted?
>> [...]
>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>> obvious that the first line of H_Hat() is infinitely recursive.
>> That's not what "recursive" means. If you can't sort out what
>> you mean and express it clearly, it's small wonder that the rest of us
>> can't do it for you, and that you seem not to understand what we are
>> trying to tell you.
> Most computer programming languages support recursion by allowing a
> function to call itself from within its own code.
Yes, but "DebugTrace(M, M)" is not an example of a function
that calls itself. Nor, for that matter is the comment "M(M)" if
you re-write it as I suggested, "M.exe(M.src)", where we distinguish
a TM and its actions from the description of that TM. Of course,
"(M, M)" in that line is actually "(M.src, M.src)" as "DebugTrace"
is emulating what "M.exe(M.src)" would do, but it is still neither
recursive nor self-referential. Conflating "H.exe" with "H.src" is
either confusion on your part or deliberate obfuscation. "H.src"
cannot /be/ recursive, but it may /describe/ a recursive process.
[...]
>> As you have been told many times, there are many other ways
>> to show that there is no general algorithm to decide this; which is
>> different from any given problem being undecidable. You have been
> Undecided is not at all the same thing as undecidable.
Indeed, but whereas each individual instance of the HP is
decidable, the general case is undecidable. The order of quantifiers
matters:
Given an instance, there is a machine [and even a useful machine]
that decides it.
Given a machine, there is an instance [and indeed an infinity of
instances] that it cannot decide.
[..]
> All of the C code that I have provided is ultimately anchored in the
> x86 machine language that is generated with the Microsoft C compiler.
> This is the byte for byte exact Turing machine Description language
> of my machines.
You have thus far provided C code that any competent CS student
could write in an afternoon. After that, no-one cares whether it is C
written for the world's latest and greatest supercomputer or for an old
"x86" computer that someone happens to have lying around; it's C, and
lots of people here are competent to see what it does. Machine code and
"byte for byte exact" are completely irrelevant.
--
Andy Walker, Nottingham.
Andy's music pages: www.cuboid.me.uk/andy/Music
Composer of the day: www.cuboid.me.uk/andy/Music/Composers/Godfrey
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-25 12:37 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <u4ednZ0g0oZMKgjCnZ2dnUU7-XfNnZ2d@giganews.com> |
| In reply to | #24397 |
On 10/25/2020 11:33 AM, Andy Walker wrote:
> On 24/10/2020 23:35, olcott wrote:
>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>> [...]
>>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>>> obvious that the first line of H_Hat() is infinitely recursive.
>>> That's not what "recursive" means. If you can't sort out what
>>> you mean and express it clearly, it's small wonder that the rest of us
>>> can't do it for you, and that you seem not to understand what we are
>>> trying to tell you.
>> Most computer programming languages support recursion by allowing a
>> function to call itself from within its own code.
>
long int Factorial(int n) {
if (n>=1)
return n * Factorial((n-1);
else
return 1;
}
> Yes, but "DebugTrace(M, M)" is not an example of a function
> that calls itself. Nor, for that matter is the comment "M(M)" if
> you re-write it as I suggested, "M.exe(M.src)", where we distinguish
> a TM and its actions from the description of that TM. Of course,
This would create the problem as it typically is presented with purely
arbitrary extraneous complexity.
If on the other hand when the Turing Machine Decription language <is>
x86 machine language then its description is directly executable.
To make things easier to understand the machine language is disassmbled
as it executes and can be examined as C before it has been compiled.
So YES DebugTrace(H_Hat, H_Hat) does specify infinite recursion and the
above two parameters are the machine address of the H_Hat machine code.
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-25 12:10 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn4f38$7hq$1@dont-email.me> |
| In reply to | #24405 |
On 2020-10-25 11:37, olcott wrote:
> On 10/25/2020 11:33 AM, Andy Walker wrote:
>> On 24/10/2020 23:35, olcott wrote:
>>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>>> [...]
>>>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>>>> obvious that the first line of H_Hat() is infinitely recursive.
>>>> That's not what "recursive" means. If you can't sort out what
>>>> you mean and express it clearly, it's small wonder that the rest of us
>>>> can't do it for you, and that you seem not to understand what we are
>>>> trying to tell you.
>>> Most computer programming languages support recursion by allowing a
>>> function to call itself from within its own code.
>>
>
> long int Factorial(int n) {
> if (n>=1)
> return n * Factorial((n-1);
> else
> return 1;
> }
>
>
>> Yes, but "DebugTrace(M, M)" is not an example of a function
>> that calls itself. Nor, for that matter is the comment "M(M)" if
>
>
>> you re-write it as I suggested, "M.exe(M.src)", where we distinguish
>> a TM and its actions from the description of that TM. Of course,
>
> This would create the problem as it typically is presented with purely
> arbitrary extraneous complexity.
>
> If on the other hand when the Turing Machine Decription language <is>
> x86 machine language then its description is directly executable.
x86 machine language is not a "Turing Description Language".
> To make things easier to understand the machine language is disassmbled
> as it executes and can be examined as C before it has been compiled.
>
> So YES DebugTrace(H_Hat, H_Hat) does specify infinite recursion and the
> above two parameters are the machine address of the H_Hat machine code.
Linz's Ĥ is simply a modified version of Linz's H. Linz's H is a Turing
Machine alleged to answer, for a given description of a Turing Machine
and a given input, will this TM halt?
Nothing in that definition specifies that H (or Ĥ) actually 'executes'
that TM description. That's a strategy which you've chosen to adopt, so
at best you can claim that *your* specific implementation includes
recursion. There's absolutely nothing in Linz's definition which
indicates or requires recursion of any kind.
So any argument which rests on 'infinite recursion' tells us nothing
about the actual Linz proof.
André
--
To email remove 'invalid' & replace 'gm' with well known Google mail
service.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-25 15:27 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <-eSdnSo_pLo8QgjCnZ2dnUU7-eXNnZ2d@giganews.com> |
| In reply to | #24406 |
On 10/25/2020 1:10 PM, André G. Isaak wrote:
> On 2020-10-25 11:37, olcott wrote:
>> On 10/25/2020 11:33 AM, Andy Walker wrote:
>>> On 24/10/2020 23:35, olcott wrote:
>>>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>>>> [...]
>>>>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>>>>> obvious that the first line of H_Hat() is infinitely recursive.
>>>>> That's not what "recursive" means. If you can't sort out what
>>>>> you mean and express it clearly, it's small wonder that the rest of us
>>>>> can't do it for you, and that you seem not to understand what we are
>>>>> trying to tell you.
>>>> Most computer programming languages support recursion by allowing a
>>>> function to call itself from within its own code.
>>>
>>
>> long int Factorial(int n) {
>> if (n>=1)
>> return n * Factorial((n-1);
>> else
>> return 1;
>> }
>>
>>
>>> Yes, but "DebugTrace(M, M)" is not an example of a function
>>> that calls itself. Nor, for that matter is the comment "M(M)" if
>>
>>
>>> you re-write it as I suggested, "M.exe(M.src)", where we distinguish
>>> a TM and its actions from the description of that TM. Of course,
>>
>> This would create the problem as it typically is presented with purely
>> arbitrary extraneous complexity.
>>
>> If on the other hand when the Turing Machine Decription language <is>
>> x86 machine language then its description is directly executable.
>
> x86 machine language is not a "Turing Description Language".
It is common knowledge that the x86 language implements the von Neumann
architecture and that the von Neumann architecture is equivalent to a
UTM: https://en.wikipedia.org/wiki/Random-access_stored-program_machine
So for all practical purposes the x86 language <is> a UTM description
language, thus making x86utm a x86 based UTM operating system.
>> To make things easier to understand the machine language is
>> disassmbled as it executes and can be examined as C before it has been
>> compiled.
>>
>> So YES DebugTrace(H_Hat, H_Hat) does specify infinite recursion and
>> the above two parameters are the machine address of the H_Hat machine
>> code.
>
> Linz's Ĥ is simply a modified version of Linz's H. Linz's H is a Turing
> Machine alleged to answer, for a given description of a Turing Machine
> and a given input, will this TM halt?
>
> Nothing in that definition specifies that H (or Ĥ) actually 'executes'
> that TM description. That's a strategy which you've chosen to adopt, so
> at best you can claim that *your* specific implementation includes
> recursion. There's absolutely nothing in Linz's definition which
> indicates or requires recursion of any kind.
Yes for all we know the machine specified by Linz might not implement
the simplest of all possible halt deciders instead it might always make
a phone call to the psychic hotline.
There is only one [simplest of all possible halt deciders] thus proving
that it is a very execllent basis.
If you don't not believe that there is only one
[simplest of all possible halt deciders] then provide a counter-example
or admit that you cannot.
> So any argument which rests on 'infinite recursion' tells us nothing
> about the actual Linz proof.
>
> André
>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-25 15:42 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <eMGdnZgvJJGrfgjCnZ2dnUU7-QnNnZ2d@giganews.com> |
| In reply to | #24412 |
On 10/25/2020 3:27 PM, olcott wrote:
> On 10/25/2020 1:10 PM, André G. Isaak wrote:
>> On 2020-10-25 11:37, olcott wrote:
>>> On 10/25/2020 11:33 AM, Andy Walker wrote:
>>>> On 24/10/2020 23:35, olcott wrote:
>>>>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>>>>> [...]
>>>>>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>>>>>> obvious that the first line of H_Hat() is infinitely recursive.
>>>>>> That's not what "recursive" means. If you can't sort out what
>>>>>> you mean and express it clearly, it's small wonder that the rest
>>>>>> of us
>>>>>> can't do it for you, and that you seem not to understand what we are
>>>>>> trying to tell you.
>>>>> Most computer programming languages support recursion by allowing a
>>>>> function to call itself from within its own code.
>>>>
>>>
>>> long int Factorial(int n) {
>>> if (n>=1)
>>> return n * Factorial((n-1);
>>> else
>>> return 1;
>>> }
>>>
>>>
>>>> Yes, but "DebugTrace(M, M)" is not an example of a function
>>>> that calls itself. Nor, for that matter is the comment "M(M)" if
>>>
>>>
>>>> you re-write it as I suggested, "M.exe(M.src)", where we distinguish
>>>> a TM and its actions from the description of that TM. Of course,
>>>
>>> This would create the problem as it typically is presented with
>>> purely arbitrary extraneous complexity.
>>>
>>> If on the other hand when the Turing Machine Decription language <is>
>>> x86 machine language then its description is directly executable.
>>
>> x86 machine language is not a "Turing Description Language".
>
> It is common knowledge that the x86 language implements the von Neumann
> architecture and that the von Neumann architecture is equivalent to a
> UTM: https://en.wikipedia.org/wiki/Random-access_stored-program_machine
>
> So for all practical purposes the x86 language <is> a UTM description
> language, thus making x86utm a x86 based UTM operating system.
>
>>> To make things easier to understand the machine language is
>>> disassmbled as it executes and can be examined as C before it has
>>> been compiled.
>>>
>>> So YES DebugTrace(H_Hat, H_Hat) does specify infinite recursion and
>>> the above two parameters are the machine address of the H_Hat machine
>>> code.
>>
>> Linz's Ĥ is simply a modified version of Linz's H. Linz's H is a
>> Turing Machine alleged to answer, for a given description of a Turing
>> Machine and a given input, will this TM halt?
>>
>> Nothing in that definition specifies that H (or Ĥ) actually 'executes'
>> that TM description. That's a strategy which you've chosen to adopt,
>> so at best you can claim that *your* specific implementation includes
>> recursion. There's absolutely nothing in Linz's definition which
>> indicates or requires recursion of any kind.
>
> Yes for all we know the machine specified by Linz might not implement
> the simplest of all possible halt deciders instead it might always make
> a phone call to the psychic hotline.
>
> There is only one [simplest of all possible halt deciders] thus proving
> that it is a very excellent basis.
The key aspect of defining a halt decider that executes its input one
execution step / state transition at a time to decide:
bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I)
Every syntatatically correct machine description can be divided into
(a) HAS_INFINITE_EXECUTION
(b) DOES_NOT_HAVE_INFINITE_EXECUTION
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Ben Bacarisse <ben.usenet@bsb.me.uk> |
|---|---|
| Date | 2020-10-25 23:11 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <874kmh7vf9.fsf@bsb.me.uk> |
| In reply to | #24414 |
olcott <NoOne@NoWhere.com> writes: > The key aspect of defining a halt decider that executes its input one > execution step / state transition at a time to decide: > > bool Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) > > Every syntatatically correct machine description can be divided into > (a) HAS_INFINITE_EXECUTION > (b) DOES_NOT_HAVE_INFINITE_EXECUTION And the key aspect of defining H so that it can give the correct answer to H(H_Hat, H_Hat) is whether H_Hat(H_Hat) halts or not. These two distinctions (your a/b and halts/does not halt) can't be the same in all cases (and you've said this explicitly) but you have resisted all attempts to get you to say in what cases they differ. Of course, only the H_Hat(H_Hat) case matters for your claim, so avoid any more ambiguity you should state whether in Aborted_Because_Non_Halting_Behavior_Detected(H_Hat, H_Hat) true corresponds to "halts" and false to "does not halt", or vice versa. (Actually only one needs to correspond because the value of ABNHBD(H_Hat, H_Hat) is known, but since you won't tell us, we have to keep making more general remarks.) -- Ben.
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-26 03:18 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn649o$a1p$1@dont-email.me> |
| In reply to | #24412 |
On 2020-10-25 14:27, olcott wrote:
> On 10/25/2020 1:10 PM, André G. Isaak wrote:
>> On 2020-10-25 11:37, olcott wrote:
>>> On 10/25/2020 11:33 AM, Andy Walker wrote:
>>>> On 24/10/2020 23:35, olcott wrote:
>>>>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>>>>> [...]
>>>>>>> Since DebugTrace(M, M) executes its input one step at a time it is
>>>>>>> obvious that the first line of H_Hat() is infinitely recursive.
>>>>>> That's not what "recursive" means. If you can't sort out what
>>>>>> you mean and express it clearly, it's small wonder that the rest
>>>>>> of us
>>>>>> can't do it for you, and that you seem not to understand what we are
>>>>>> trying to tell you.
>>>>> Most computer programming languages support recursion by allowing a
>>>>> function to call itself from within its own code.
>>>>
>>>
>>> long int Factorial(int n) {
>>> if (n>=1)
>>> return n * Factorial((n-1);
>>> else
>>> return 1;
>>> }
>>>
>>>
>>>> Yes, but "DebugTrace(M, M)" is not an example of a function
>>>> that calls itself. Nor, for that matter is the comment "M(M)" if
>>>
>>>
>>>> you re-write it as I suggested, "M.exe(M.src)", where we distinguish
>>>> a TM and its actions from the description of that TM. Of course,
>>>
>>> This would create the problem as it typically is presented with
>>> purely arbitrary extraneous complexity.
>>>
>>> If on the other hand when the Turing Machine Decription language <is>
>>> x86 machine language then its description is directly executable.
>>
>> x86 machine language is not a "Turing Description Language".
>
> It is common knowledge that the x86 language implements the von Neumann
> architecture and that the von Neumann architecture is equivalent to a
> UTM: https://en.wikipedia.org/wiki/Random-access_stored-program_machine
>
> So for all practical purposes the x86 language <is> a UTM description
> language, thus making x86utm a x86 based UTM operating system.
No, it isn't. Your constant repetition of this claim does not make it
true. To the extent that 'UTM description language' means anything, one
would assume it means a a language for specifying a particular TM (where
TM refers to a well-defined type of mathematical object) to be used as
the input for a UTM. x86 machine language doesn't do this.
>>> To make things easier to understand the machine language is
>>> disassmbled as it executes and can be examined as C before it has
>>> been compiled.
>>>
>>> So YES DebugTrace(H_Hat, H_Hat) does specify infinite recursion and
>>> the above two parameters are the machine address of the H_Hat machine
>>> code.
>>
>> Linz's Ĥ is simply a modified version of Linz's H. Linz's H is a
>> Turing Machine alleged to answer, for a given description of a Turing
>> Machine and a given input, will this TM halt?
>>
>> Nothing in that definition specifies that H (or Ĥ) actually 'executes'
>> that TM description. That's a strategy which you've chosen to adopt,
>> so at best you can claim that *your* specific implementation includes
>> recursion. There's absolutely nothing in Linz's definition which
>> indicates or requires recursion of any kind.
>
> Yes for all we know the machine specified by Linz might not implement
> the simplest of all possible halt deciders instead it might always make
> a phone call to the psychic hotline.
First off, there is no possible way to construct a halt decider, as
demonstrated by Linz. This means there is also no such thing as the
'simplest of all possible halt deciders'. Your attempt to redefine the
question doesn't change this fact (and as far as I can tell, your
solution still suffers from the exact same contradiction that Linz draws
attention to anyways).
Second, if you want to talk about partial halt deciders, then your claim
that this is the simplest possible approach is simply something you are
pulling out of your ass. There is no actual argument which has been
offered by you to support this claim.
Third, your insistence on always choosing the most absurd interpretation
of people's comments you can think of rather than looking for a more
reasonable one is highly aggravating. Analyzing the state transitions of
the input without actually running the TM in some sort of emulation is a
reasonable interpretation. Calling a psychic hotline is not.
Since an approach which involves analyzing the state transitions without
actually running the TM in some sort of emulation involves no recursion
at all, you cannot claim that H(Ĥ-description, Ĥ-description) is
inherently recursive, let alone infinitely recursive.
André
--
To email remove 'invalid' & replace 'gm' with well known Google mail
service.
[toc] | [prev] | [next] | [standalone]
| From | André G. Isaak <agisaak@gm.invalid> |
|---|---|
| Date | 2020-10-26 03:21 -0600 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn64fh$a1p$2@dont-email.me> |
| In reply to | #24451 |
On 2020-10-26 03:18, André G. Isaak wrote: > Since an approach which involves analyzing the state transitions without > actually running the TM in some sort of emulation involves no recursion > at all, you cannot claim that H(Ĥ-description, Ĥ-description) is > inherently recursive, let alone infinitely recursive. Just to add something to this, the recursion you claim exists occurs *inside* your DebugTrace. If it is possible for DebugTrace to get stuck in infinite recursion, then your DebugTrace procedure fails to actually do what it purports to do since that procedure is not itself guaranteed to halt. André -- To email remove 'invalid' & replace 'gm' with well known Google mail service.
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-23 22:58 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <gLMkH.639593$eN2.538280@fx47.iad> |
| In reply to | #24289 |
On 10/23/20 9:45 PM, olcott wrote:
> On 10/23/2020 8:35 PM, Richard Damon wrote:
>> On 10/23/20 5:58 PM, olcott wrote:
>>>
>>> The more detailed execution trace is H() calls DebugTrace() that creates
>>> a separate execution context that executes H_Hat() that calls
>>> DebugTrace() the creates another separate execution context that
>>> executes another instance of H_Hat().
>>>
>>> The outermost DebugTrace() sees the infinite recursion of the outermost
>>> H_Hat() before H_Hat() sees its own infinite recursion. The outermost
>>> DebugTrace() stops running the outermost H_Hat() in the outermost
>>> DebugTrace() DebugStep() loop. Then the outermost DebugTrace() returns
>>> Aborted_Because_Non_Halting_Behavior_Detected.
>>
>> Graphic picture:
>>
>> First Run:
>>
>> Run H(H_Hat)
>> H call DebugTrace on H_Hat(), which (apparently) detects that it needed
>> to abort H_Hat, so H returns the result, H_Hat does not halt.
>
> Not quite. H() calls DebugTrace() which executes H_Hat() until it
> detects infinite recursion. Then DebugTrace() terminates H_Hat() and
> notifies H() that H_Hat() was terminated.
>
>> Next Run H_Hat
>>
>> H_Hat calls the same DebugTrace on H_Hat(), which by necessity, must
>> return the same answer, that it needed to abort H_Hat,
>> So H_Hat halt, Thus showing H, and thus DebugTrace to be wrong.
>
> Not quite. H_Hat() calls DebugTrace() which executes another separate
> instance of H_Hat() until it detects infinite recursion on this inner
> instance. Then DebugTrace() terminates H_Hat() and notifies the outer
> H_Hat() that the inner H_Hat() was terminated.
>
>> There IS not 'supervisor' above this outer invocation of H_Hat, so
>> nothing will 'abort' it.
>
> No need to abort it. It takes the M(M) was aborted path.
>
> // M has address of H_Hat()
> void H_Hat(u32 M)
> {
> if (DebugTrace(M, M)) // M(M) Aborted?
> MOV_EAX_0 // Execution of M(N) has been aborted
> else
> {
> MOV_EAX_1 // M(N) has halted
> HERE: goto HERE;
> }
> HALT
> }
>
>> Now, if instead DebugTrace decided that H_Hat did stop, the the first
>> run, of H() will indicate that H_Hat stops, but on the second run,
>> H_Hat() becomes just an ordinary infinate loop that will never stop, so
>> H() is again proven wrong.
>>
>
> The second run also gets the correct answer.
>
Since DebugTrace indicates that it had to abort H_Hat(H_Hat), this means
that the H() run will indicate that the provide program is non-halting,
BUT in the second run, since DebugTrace indicates that it had to abort
H_Hat(H_Hat), H_Hat will immediate halt.
This says that the run of H_Hat(H_Hat) halted, but H(H_Hat, H_Hat) said
that H_Hat(H_Hat) will be non-Halting, thus H was wrong, so it is not a
proper halt decider.
Note, the running of H_Hat(H_Hat) determines what the correct answer is,
not what DebugTrace told it.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 22:28 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <dNWdnf8SRt7mAg7CnZ2dnUU7-bvNnZ2d@giganews.com> |
| In reply to | #24297 |
On 10/23/2020 9:58 PM, Richard Damon wrote:
> On 10/23/20 9:45 PM, olcott wrote:
>> On 10/23/2020 8:35 PM, Richard Damon wrote:
>>> On 10/23/20 5:58 PM, olcott wrote:
>>>>
>>>> The more detailed execution trace is H() calls DebugTrace() that creates
>>>> a separate execution context that executes H_Hat() that calls
>>>> DebugTrace() the creates another separate execution context that
>>>> executes another instance of H_Hat().
>>>>
>>>> The outermost DebugTrace() sees the infinite recursion of the outermost
>>>> H_Hat() before H_Hat() sees its own infinite recursion. The outermost
>>>> DebugTrace() stops running the outermost H_Hat() in the outermost
>>>> DebugTrace() DebugStep() loop. Then the outermost DebugTrace() returns
>>>> Aborted_Because_Non_Halting_Behavior_Detected.
>>>
>>> Graphic picture:
>>>
>>> First Run:
>>>
>>> Run H(H_Hat)
>>> H call DebugTrace on H_Hat(), which (apparently) detects that it needed
>>> to abort H_Hat, so H returns the result, H_Hat does not halt.
>>
>> Not quite. H() calls DebugTrace() which executes H_Hat() until it
>> detects infinite recursion. Then DebugTrace() terminates H_Hat() and
>> notifies H() that H_Hat() was terminated.
>>
>>> Next Run H_Hat
>>>
>>> H_Hat calls the same DebugTrace on H_Hat(), which by necessity, must
>>> return the same answer, that it needed to abort H_Hat,
>>> So H_Hat halt, Thus showing H, and thus DebugTrace to be wrong.
>>
>> Not quite. H_Hat() calls DebugTrace() which executes another separate
>> instance of H_Hat() until it detects infinite recursion on this inner
>> instance. Then DebugTrace() terminates H_Hat() and notifies the outer
>> H_Hat() that the inner H_Hat() was terminated.
>>
>>> There IS not 'supervisor' above this outer invocation of H_Hat, so
>>> nothing will 'abort' it.
>>
>> No need to abort it. It takes the M(M) was aborted path.
>>
>> // M has address of H_Hat()
>> void H_Hat(u32 M)
>> {
>> if (DebugTrace(M, M)) // M(M) Aborted?
>> MOV_EAX_0 // Execution of M(N) has been aborted
>> else
>> {
>> MOV_EAX_1 // M(N) has halted
>> HERE: goto HERE;
>> }
>> HALT
>> }
>>
>>> Now, if instead DebugTrace decided that H_Hat did stop, the the first
>>> run, of H() will indicate that H_Hat stops, but on the second run,
>>> H_Hat() becomes just an ordinary infinate loop that will never stop, so
>>> H() is again proven wrong.
>>>
>>
>> The second run also gets the correct answer.
>>
>
> Since DebugTrace indicates that it had to abort H_Hat(H_Hat), this means
> that the H() run will indicate that the provide program is non-halting,
> BUT in the second run, since DebugTrace indicates that it had to abort
> H_Hat(H_Hat), H_Hat will immediate halt.
That is why we have to change the question.
If the halt decider executes its input in DebugStep() mode, aborts the
execution of this input, and reports not halting, then is gets the wrong
answer because it decided not halting and it halted.
With exact same situation except that the halt decider reports:
Aborted_Because_Non_Halting_Behavior_Detected.
Now it correctly decided halting AND got the correct answer.
> This says that the run of H_Hat(H_Hat) halted, but H(H_Hat, H_Hat) said
> that H_Hat(H_Hat) will be non-Halting, thus H was wrong, so it is not a
> proper halt decider.
>
> Note, the running of H_Hat(H_Hat) determines what the correct answer is,
> not what DebugTrace told it.
>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> |
|---|---|
| Date | 2020-10-23 21:03 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn092g$147e$3@gioia.aioe.org> |
| In reply to | #24301 |
On 10/23/2020 8:28 PM, olcott wrote:
> On 10/23/2020 9:58 PM, Richard Damon wrote:
>> On 10/23/20 9:45 PM, olcott wrote:
>>> On 10/23/2020 8:35 PM, Richard Damon wrote:
>>>> On 10/23/20 5:58 PM, olcott wrote:
>>>>>
>>>>> The more detailed execution trace is H() calls DebugTrace() that
>>>>> creates
>>>>> a separate execution context that executes H_Hat() that calls
>>>>> DebugTrace() the creates another separate execution context that
>>>>> executes another instance of H_Hat().
>>>>>
>>>>> The outermost DebugTrace() sees the infinite recursion of the
>>>>> outermost
>>>>> H_Hat() before H_Hat() sees its own infinite recursion. The outermost
>>>>> DebugTrace() stops running the outermost H_Hat() in the outermost
>>>>> DebugTrace() DebugStep() loop. Then the outermost DebugTrace() returns
>>>>> Aborted_Because_Non_Halting_Behavior_Detected.
>>>>
>>>> Graphic picture:
>>>>
>>>> First Run:
>>>>
>>>> Run H(H_Hat)
>>>> H call DebugTrace on H_Hat(), which (apparently) detects that it needed
>>>> to abort H_Hat, so H returns the result, H_Hat does not halt.
>>>
>>> Not quite. H() calls DebugTrace() which executes H_Hat() until it
>>> detects infinite recursion. Then DebugTrace() terminates H_Hat() and
>>> notifies H() that H_Hat() was terminated.
>>>
>>>> Next Run H_Hat
>>>>
>>>> H_Hat calls the same DebugTrace on H_Hat(), which by necessity, must
>>>> return the same answer, that it needed to abort H_Hat,
>>>> So H_Hat halt, Thus showing H, and thus DebugTrace to be wrong.
>>>
>>> Not quite. H_Hat() calls DebugTrace() which executes another separate
>>> instance of H_Hat() until it detects infinite recursion on this inner
>>> instance. Then DebugTrace() terminates H_Hat() and notifies the outer
>>> H_Hat() that the inner H_Hat() was terminated.
>>>
>>>> There IS not 'supervisor' above this outer invocation of H_Hat, so
>>>> nothing will 'abort' it.
>>>
>>> No need to abort it. It takes the M(M) was aborted path.
>>>
>>> // M has address of H_Hat()
>>> void H_Hat(u32 M)
>>> {
>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>> MOV_EAX_0 // Execution of M(N) has been aborted
>>> else
>>> {
>>> MOV_EAX_1 // M(N) has halted
>>> HERE: goto HERE;
>>> }
>>> HALT
>>> }
>>>
>>>> Now, if instead DebugTrace decided that H_Hat did stop, the the first
>>>> run, of H() will indicate that H_Hat stops, but on the second run,
>>>> H_Hat() becomes just an ordinary infinate loop that will never stop, so
>>>> H() is again proven wrong.
>>>>
>>>
>>> The second run also gets the correct answer.
>>>
>>
>> Since DebugTrace indicates that it had to abort H_Hat(H_Hat), this means
>> that the H() run will indicate that the provide program is non-halting,
>> BUT in the second run, since DebugTrace indicates that it had to abort
>> H_Hat(H_Hat), H_Hat will immediate halt.
>
> That is why we have to change the question.
> If the halt decider executes its input in DebugStep() mode, aborts the
> execution of this input, and reports not halting, then is gets the wrong
> answer because it decided not halting and it halted.
>
> With exact same situation except that the halt decider reports:
> Aborted_Because_Non_Halting_Behavior_Detected.
> Now it correctly decided halting AND got the correct answer.
And how EXACTLY do you get to the
Aborted_Because_Non_Halting_Behavior_Detected
state? And is it guaranteed to be 100% correct?
Scary Sarcasm:
I can see it now... There are two possible scenarios.
Person A is on a ventilator for 3 months... Your program halts the
machine, A dies. Yikes!
Now, get this...
The same Person A is on a ventilator for 4 months... And recovers to a
point where A can breath on its own!
Therefore, your crap would have killed A prematurely at 3 months because
it incorrectly detected non halting behavior!
DAMN!
>
>> This says that the run of H_Hat(H_Hat) halted, but H(H_Hat, H_Hat) said
>> that H_Hat(H_Hat) will be non-Halting, thus H was wrong, so it is not a
>> proper halt decider.
>>
>> Note, the running of H_Hat(H_Hat) determines what the correct answer is,
>> not what DebugTrace told it.
>>
>
>
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-23 23:13 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <y6ednYqkhsafNw7CnZ2dnUU7-fnNnZ2d@giganews.com> |
| In reply to | #24304 |
On 10/23/2020 11:03 PM, Chris M. Thomasson wrote:
> On 10/23/2020 8:28 PM, olcott wrote:
>> On 10/23/2020 9:58 PM, Richard Damon wrote:
>>> On 10/23/20 9:45 PM, olcott wrote:
>>>> On 10/23/2020 8:35 PM, Richard Damon wrote:
>>>>> On 10/23/20 5:58 PM, olcott wrote:
>>>>>>
>>>>>> The more detailed execution trace is H() calls DebugTrace() that
>>>>>> creates
>>>>>> a separate execution context that executes H_Hat() that calls
>>>>>> DebugTrace() the creates another separate execution context that
>>>>>> executes another instance of H_Hat().
>>>>>>
>>>>>> The outermost DebugTrace() sees the infinite recursion of the
>>>>>> outermost
>>>>>> H_Hat() before H_Hat() sees its own infinite recursion. The outermost
>>>>>> DebugTrace() stops running the outermost H_Hat() in the outermost
>>>>>> DebugTrace() DebugStep() loop. Then the outermost DebugTrace()
>>>>>> returns
>>>>>> Aborted_Because_Non_Halting_Behavior_Detected.
>>>>>
>>>>> Graphic picture:
>>>>>
>>>>> First Run:
>>>>>
>>>>> Run H(H_Hat)
>>>>> H call DebugTrace on H_Hat(), which (apparently) detects that it
>>>>> needed
>>>>> to abort H_Hat, so H returns the result, H_Hat does not halt.
>>>>
>>>> Not quite. H() calls DebugTrace() which executes H_Hat() until it
>>>> detects infinite recursion. Then DebugTrace() terminates H_Hat() and
>>>> notifies H() that H_Hat() was terminated.
>>>>
>>>>> Next Run H_Hat
>>>>>
>>>>> H_Hat calls the same DebugTrace on H_Hat(), which by necessity, must
>>>>> return the same answer, that it needed to abort H_Hat,
>>>>> So H_Hat halt, Thus showing H, and thus DebugTrace to be wrong.
>>>>
>>>> Not quite. H_Hat() calls DebugTrace() which executes another separate
>>>> instance of H_Hat() until it detects infinite recursion on this inner
>>>> instance. Then DebugTrace() terminates H_Hat() and notifies the outer
>>>> H_Hat() that the inner H_Hat() was terminated.
>>>>
>>>>> There IS not 'supervisor' above this outer invocation of H_Hat, so
>>>>> nothing will 'abort' it.
>>>>
>>>> No need to abort it. It takes the M(M) was aborted path.
>>>>
>>>> // M has address of H_Hat()
>>>> void H_Hat(u32 M)
>>>> {
>>>> if (DebugTrace(M, M)) // M(M) Aborted?
>>>> MOV_EAX_0 // Execution of M(N) has been aborted
>>>> else
>>>> {
>>>> MOV_EAX_1 // M(N) has halted
>>>> HERE: goto HERE;
>>>> }
>>>> HALT
>>>> }
>>>>
>>>>> Now, if instead DebugTrace decided that H_Hat did stop, the the first
>>>>> run, of H() will indicate that H_Hat stops, but on the second run,
>>>>> H_Hat() becomes just an ordinary infinate loop that will never
>>>>> stop, so
>>>>> H() is again proven wrong.
>>>>>
>>>>
>>>> The second run also gets the correct answer.
>>>>
>>>
>>> Since DebugTrace indicates that it had to abort H_Hat(H_Hat), this means
>>> that the H() run will indicate that the provide program is non-halting,
>>> BUT in the second run, since DebugTrace indicates that it had to abort
>>> H_Hat(H_Hat), H_Hat will immediate halt.
>>
>> That is why we have to change the question.
>> If the halt decider executes its input in DebugStep() mode, aborts the
>> execution of this input, and reports not halting, then is gets the
>> wrong answer because it decided not halting and it halted.
>>
>> With exact same situation except that the halt decider reports:
>> Aborted_Because_Non_Halting_Behavior_Detected.
>> Now it correctly decided halting AND got the correct answer.
>
> And how EXACTLY do you get to the
>
> Aborted_Because_Non_Halting_Behavior_Detected
>
> state? And is it guaranteed to be 100% correct?
The whole scope of my work is to show that the conventional
self-referential halting problem proof counter-examples do not prove
that halting is undecidiable.
I have already done that.
The greatest scope of this whole project involves one more step to show
the precise C code steps of actually correctly deciding one of the
conventional self-referential halting problem proof counter-examples.
I wrote this code in 2018-12-13 and I think that I may use this same
simplest possible method. I have much more robust methods too.
> Scary Sarcasm:
>
> I can see it now... There are two possible scenarios.
>
> Person A is on a ventilator for 3 months... Your program halts the
> machine, A dies. Yikes!
>
> Now, get this...
>
> The same Person A is on a ventilator for 4 months... And recovers to a
> point where A can breath on its own!
>
> Therefore, your crap would have killed A prematurely at 3 months because
> it incorrectly detected non halting behavior!
>
> DAMN!
>
>
>>
>>> This says that the run of H_Hat(H_Hat) halted, but H(H_Hat, H_Hat) said
>>> that H_Hat(H_Hat) will be non-Halting, thus H was wrong, so it is not a
>>> proper halt decider.
>>>
>>> Note, the running of H_Hat(H_Hat) determines what the correct answer is,
>>> not what DebugTrace told it.
>>>
>>
>>
>
--
Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Richard Damon <Richard@Damon-Family.org> |
|---|---|
| Date | 2020-10-24 13:27 -0400 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <AuZkH.42912$zj1.876@fx28.iad> |
| In reply to | #24301 |
On 10/23/20 11:28 PM, olcott wrote: > That is why we have to change the question. > If the halt decider executes its input in DebugStep() mode, aborts the > execution of this input, and reports not halting, then is gets the wrong > answer because it decided not halting and it halted. > > With exact same situation except that the halt decider reports: > Aborted_Because_Non_Halting_Behavior_Detected. > Now it correctly decided halting AND got the correct answer. > And since you changed the question to something different, you CAN'T say anything about the original question! Someone asks, Do Dogs Bark, and you reply Cows Moo. The original question has important implications in mathematics. If I design a Turing Machine for a purpose, and I want to know if that machine will ever halt and give me an answer, that machine will never 'Abort', as it isn't running under your Debug logic. If I want to ask your system if this machine will ever halt, for some machines, you will say it halts, and I presume that this will be accurate and I know that my machine will halt. Sometimes your machine will say that it needed to abort, and from that, I can't be sure of what the original machine will do. It might loop forever, or maybe for some other reason it was aborted. Thus, your new question is a lot less interesting, and a lot less useful. Note, that a lot of the interesting machines we want to ask the halting question on are the machines where you method is most apt to have the problem, they are machines that grow in an unbounded manner as they progress, and WILL use the infinite storage if they do loop forever. Now, if you change your question to one where you give 3 answers, Yes, it will halt, No it will not halt, or I don't know if it will halt or not, AND you can provide some reasonably limited conditions when you will give that last answer, perhaps you can have something usable, but if part of that condition is the problem got 'too big' or took 'too long' then it won't be. From what I see so far, you are going to answer I don't know on most of the interesting machines.
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-24 14:08 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <htidnSdDk4FV5gnCnZ2dnUU7-QnNnZ2d@giganews.com> |
| In reply to | #24325 |
On 10/24/2020 12:27 PM, Richard Damon wrote: > On 10/23/20 11:28 PM, olcott wrote: > >> That is why we have to change the question. >> If the halt decider executes its input in DebugStep() mode, aborts the >> execution of this input, and reports not halting, then is gets the wrong >> answer because it decided not halting and it halted. >> >> With exact same situation except that the halt decider reports: >> Aborted_Because_Non_Halting_Behavior_Detected. >> Now it correctly decided halting AND got the correct answer. >> > And since you changed the question to something different, you CAN'T say > anything about the original question! > I can say that the halting problem, cannot be shown to be undecidable when we simply rephrase the question to a question that is not subject to a cheap trick: Does the input have to be aborted to prevent infinite execution? This question correctly divides the set of all programs into correct and incorrect and it cannot be fooled by any cheap trick. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Alan Mackenzie <acm@muc.de> |
|---|---|
| Date | 2020-10-24 19:54 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn20p8$1pi9$1@news.muc.de> |
| In reply to | #24336 |
In comp.theory olcott <NoOne@nowhere.com> wrote: > On 10/24/2020 12:27 PM, Richard Damon wrote: [ .... ] >> And since you changed the question to something different, you CAN'T say >> anything about the original question! > I can say that the halting problem, cannot be shown to be undecidable > when we simply rephrase the question to a question that is not subject > to a cheap trick: The use of emotional language says more about you that about the maths involved. > Does the input have to be aborted to prevent infinite execution? Even after following this thread, more or less, I can't see how that question is essentially different from the proper halting problem question. > This question correctly divides the set of all programs into correct > and incorrect and it cannot be fooled by any cheap trick. It does nothing of the kind. Halting programs are not necessarily correct, and non-halting ones need not be incorrect. The latter category includes control programs which MUST NOT under any circumstances halt, except when the hardware they are controlling is taken out of service or ceases to exist. > -- > Copyright 2020 Pete Olcott -- Alan Mackenzie (Nuremberg, Germany).
[toc] | [prev] | [next] | [standalone]
| From | olcott <NoOne@NoWhere.com> |
|---|---|
| Date | 2020-10-24 15:48 -0500 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <UIqdnWvQQ76fDgnCnZ2dnUU7-XHNnZ2d@giganews.com> |
| In reply to | #24339 |
On 10/24/2020 2:54 PM, Alan Mackenzie wrote: > In comp.theory olcott <NoOne@nowhere.com> wrote: >> On 10/24/2020 12:27 PM, Richard Damon wrote: > > [ .... ] > >>> And since you changed the question to something different, you CAN'T say >>> anything about the original question! > >> I can say that the halting problem, cannot be shown to be undecidable >> when we simply rephrase the question to a question that is not subject >> to a cheap trick: > > The use of emotional language says more about you that about the maths > involved. > >> Does the input have to be aborted to prevent infinite execution? > > Even after following this thread, more or less, I can't see how that > question is essentially different from the proper halting problem > question. > The difference is that the revised question cannot be contradicted to make the halting problem undecidable: Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true means that the input has infinite execution. Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false means that the input DOES NOT HAVE infinite execution. There is no input that the redefined halt decider cannot decide. Every input is divided into: (a) Has infinite execution. (b) DOES NOT HAVE infinite execution. -- Copyright 2020 Pete Olcott
[toc] | [prev] | [next] | [standalone]
| From | Alan Mackenzie <acm@muc.de> |
|---|---|
| Date | 2020-10-24 21:41 +0000 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <rn271j$1if7$1@news.muc.de> |
| In reply to | #24342 |
In comp.theory olcott <NoOne@nowhere.com> wrote: > On 10/24/2020 2:54 PM, Alan Mackenzie wrote: >> In comp.theory olcott <NoOne@nowhere.com> wrote: >>> On 10/24/2020 12:27 PM, Richard Damon wrote: >> [ .... ] >>>> And since you changed the question to something different, you CAN'T say >>>> anything about the original question! >>> I can say that the halting problem, cannot be shown to be undecidable >>> when we simply rephrase the question to a question that is not subject >>> to a cheap trick: >> The use of emotional language says more about you that about the maths >> involved. >>> Does the input have to be aborted to prevent infinite execution? >> Even after following this thread, more or less, I can't see how that >> question is essentially different from the proper halting problem >> question. > The difference is that the revised question cannot be contradicted to > make the halting problem undecidable: I can't see that at all. The two questions are essentially the same, aren't they, so your modified question will be just as applicable to the Halting problem proofs as the original, won't it? Or, put another way, could you give a clear example of something for which the HP question and your question give different answers? > Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == true > means that the input has infinite execution. Or for which a halting program would say "doesn't halt". > Aborted_Because_Non_Halting_Behavior_Detected(u32 P, u32 I) == false > means that the input DOES NOT HAVE infinite execution. Or for which a halting program would say "does halt". > There is no input that the redefined halt decider cannot decide. That seems very unlikely. One could program a brute force search for a counterexample to Goldbach's conjecture. Your redefined halt decider would likely be unable to say if the brute force search would ever terminate. > Every input is divided into: > (a) Has infinite execution. > (b) DOES NOT HAVE infinite execution. and (c) it is unknown whether there's infinite execution. > -- > Copyright 2020 Pete Olcott -- Alan Mackenzie (Nuremberg, Germany).
[toc] | [prev] | [next] | [standalone]
| From | Malcolm McLean <malcolm.arthur.mclean@gmail.com> |
|---|---|
| Date | 2020-10-24 14:47 -0700 |
| Subject | Re: The key aspects of x86utm are now finally complete [ I dare you to prove that I am wrong ] |
| Message-ID | <393e4c75-1a34-4d89-8b2f-7391e5ddad23n@googlegroups.com> |
| In reply to | #24352 |
On Saturday, 24 October 2020 at 22:41:10 UTC+1, Alan Mackenzie wrote: > In comp.theory olcott <No...@nowhere.com> wrote: > > > > There is no input that the redefined halt decider cannot decide. > That seems very unlikely. One could program a brute force search for a > counterexample to Goldbach's conjecture. Your redefined halt decider > would likely be unable to say if the brute force search would ever > terminate. > Yes, PO is starting to get too ambitious. The scope of this is to refute the Linz proof, not to write a halt decider, not even to refute the other proofs that halt deciders are impossible. That's quite enough for now. For the record, I think Linz is sound. But it only refers to halt deciders which are Turing machines.
[toc] | [prev] | [next] | [standalone]
Page 6 of 25 — ← Prev page 1 … 4 5 [6] 7 8 … 25 Next page →
Back to top | Article view | comp.theory
csiph-web