Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.theory > #24043 > unrolled thread

The key aspects of x86utm are now finally complete (Refuting the HP proofs) [ definition of H ]

Started byolcott <NoOne@NoWhere.com>
First post2020-10-20 11:33 -0500
Last post2020-10-29 14:01 +0100
Articles 20 on this page of 499 — 17 participants

Back to article view | Back to comp.theory


Contents

  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 15 of 25 — ← Prev page 1 … 13 14 [15] 16 17 … 25  Next page →


#24199 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 08:43 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<F46dnTPTdo-AQw_CnZ2dnUU7-L_NnZ2d@giganews.com>
In reply to#24194
On 10/23/2020 4:29 AM, Malcolm McLean wrote:
> On Friday, 23 October 2020 at 04:41:59 UTC+1, Richard Damon wrote:
>>
>> A big part of this lack of interest is that detecting halting by
>> simulating adds no information about the halting behavior above simply
>> running the orginal machine and observing if it has halted.
>>
> Exactly. What happens if we have a physical Turing machine?
> 
> It's set up by a human supervisor, who waits to see if it halts. One
> possibility is that it will run out of tape, in which case he, probably rightly,
> concludes that it has got stuck in an infinite loop. Another possibility
> is that it takes a long time and he gets bored. Another possibility is that
> it halts normally.
> 
> Assuming it doesn't halt normally, the machine is destroyed or switched
> off in some manner. It never runs forever.
> 
> So in fact we have a pretty good, though not perfect, halt detector. But
> it's not a Turing machine. A Turing machine can't abort.

A UTM can run its TM until it decides that its TM is would not halt.
Then the UTM stops running its TM and reports non-halting behavior.
The TM cannot then do the opposite of whatever the UTM decided because 
it is no longer running. Bingo halting is decidable !

>  PO is trying to
> get round this problem by saying that DebugTrace aborts the program
> this stepping through (which is possible), then shunts up the "abortion"
> state to H_Hat, which then aborts. That's not valid, of course. H_Hat can't
> abort itself or it's not a Turing machine.
> 
> Remove the requirement that the halt detector be a Turing machine and
> the Linz proof fails. That's the basic point that seems to have been missed,
> and that's what PO is doing, though not so blatantly that most people
> have spotted the error.
> 


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24205 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-23 15:51 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<874kml6ln6.fsf@bsb.me.uk>
In reply to#24194
Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:

> So in fact we have a pretty good, though not perfect, halt detector. But
> it's not a Turing machine. A Turing machine can't abort.

That's a red herring.  An abort is not magic.  It's just another way of
halting which we give an special name to.  A TM can abort by halting in
state we interpret as aborting.

> PO is trying to
> get round this problem by saying that DebugTrace aborts the program 
> this stepping through (which is possible), then shunts up the "abortion"
> state to H_Hat, which then aborts. That's not valid, of course. H_Hat can't
> abort itself or it's not a Turing machine.

H_Hat is not a Turing machine because it is x86 code.  Aborting has
nothing to do with that.

> Remove the requirement that the halt detector be a Turing machine and 
> the Linz proof fails. That's the basic point that seems to have been missed,
> and that's what PO is doing, though not so blatantly that most people
> have spotted the error.

Of course Linz's proof fails.  It fails for Turing machines if they are
defined even slightly differently from the way Linz defines them!
That's how proofs work.  Why should anyone point that out?

He's not simply relying on a poof literally not applying to some other
model of computation.  He's trying to invalidate the method behind the
proof.  What he is claiming is that he can make two computations,
related in the same as the two in Linz's proof (and in other similar
proofs), that do not fall foul of the obvious logic.  He has not done
that.  It can't be done.  It can't be done even in models where halting
is decidable.

-- 
Ben.

[toc] | [prev] | [next] | [standalone]


#24211 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 10:19 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<ho-dneFBLbQRaQ_CnZ2dnUU7-dfNnZ2d@giganews.com>
In reply to#24205
On 10/23/2020 9:51 AM, Ben Bacarisse wrote:
> Malcolm McLean <malcolm.arthur.mclean@gmail.com> writes:
> 
>> So in fact we have a pretty good, though not perfect, halt detector. But
>> it's not a Turing machine. A Turing machine can't abort.
> 
> That's a red herring.  An abort is not magic.  It's just another way of
> halting which we give an special name to.  A TM can abort by halting in
> state we interpret as aborting.
> 
>> PO is trying to
>> get round this problem by saying that DebugTrace aborts the program
>> this stepping through (which is possible), then shunts up the "abortion"
>> state to H_Hat, which then aborts. That's not valid, of course. H_Hat can't
>> abort itself or it's not a Turing machine.
> 
> H_Hat is not a Turing machine because it is x86 code.  Aborting has
> nothing to do with that.
> 
>> Remove the requirement that the halt detector be a Turing machine and
>> the Linz proof fails. That's the basic point that seems to have been missed,
>> and that's what PO is doing, though not so blatantly that most people
>> have spotted the error.
> 
> Of course Linz's proof fails.  It fails for Turing machines if they are
> defined even slightly differently from the way Linz defines them!
> That's how proofs work.  Why should anyone point that out?
> 
> He's not simply relying on a poof literally not applying to some other
> model of computation.  He's trying to invalidate the method behind the
> proof.  What he is claiming is that he can make two computations,
> related in the same as the two in Linz's proof (and in other similar
> proofs), that do not fall foul of the obvious logic.  He has not done
> that.  It can't be done.  It can't be done even in models where halting
> is decidable.
> 

If we take my redefined halting decider and interpret its return value 
using the conventional interpretation:

DebugTrace() executes H_Hat() and decides that it would not otherwise 
halt so it terminates the execution of H_Hat() and reports:

(1) Not_Halting.
     Decision:Not_Halting
     Behavior:Halting
     a contradiction DebugTrace() got the wrong answer.

If we take my redefined halting decider and interpret its return value 
using the redefined interpretation:

(2) Aborted_Because_Non_Halting_Behavior_Detected
     Decision:Aborted_Because_Non_Halting_Behavior_Detected
     Behavior:Aborted_Because_Non_Halting_Behavior_Detected
     Not a contradiction and the right answer!

Instead of the C function DebugTrace() we could simply have a UTM that 
executes an (already on the tape) input UTM. This halt decider UTM would 
execute its (already on the tape) input UTM one state transition at a 
time. As soon as the halt decider UTM detects that its (already on the 
tape) input UTM would not halt, the halt decider UTM stops executing its 
(already on the tape) input UTM and transitions to its own final state 
indicating Aborted_Because_Non_Halting_Behavior_Detected.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24164 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-22 23:14 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<r_2dnVg7lozOmQ_CnZ2dnUU78I_NnZ2d@brightview.co.uk>
In reply to#24113
On 22/10/2020 17:38, olcott wrote:
> On 10/22/2020 10:25 AM, Mike Terry wrote:
>> On 22/10/2020 15:36, olcott wrote:
>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>
>>>>> The difference is that it is no longer possible for H_Hat() to do the
>>>>> opposite of what H() decides. This transforms an undecidable problem
>>>>> into a decidable problem.
>>>>
>>>> If H_Hat no longer does what the proof defined, then your demonstration
>>>> is no longer applicable to the proof.
>>>>
>>>
>>> If the halt decider is to report whether or not its input halts another
>>> program can be constructed on the the basis of this halt decider that
>>> does the opposite of whatever the halt decider decides.
>>>
>>> This is how H() and H_Hat() are defined in the Linz proof.
>>>
>>> If the halt decider is to report whether or not it aborted its input
>>> program because its input program would otherwise cause the halt decider
>>> to get stuck in infinite execution then this other program can no longer
>>> fool its halt decider and do the opposite of whatever it decides.
>>>
>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to
>>> execute because H() has complete control over H_Hat.
>>>
>>> The end result of this slight change is that the halting problem can no
>>> longer be shown to be undecidable.
>>>
>>
>> It is suspicious that in none of this have you ever stated what is
>> actually wrong in the Linz proof.
>
> When the halting problem is defined as:
> bool Does_It_Halt(u32 P, u32 I)
> another program can be constructed on the basis of Does_It_Halt() that
> does the opposite of whatever Does_It_Halt() decides.
>

Yes, regardless of the internal details of Does_It_Halt().

> When the halting problem is defined as:
> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>
> another program CANNOT be constructed on the basis of
> Was_Its_Execution_Aborted() that does the opposite of whatever
> Was_Its_Execution_Aborted() decides.

Sure, if you interpret your question literally as asking whether P would 
actually be aborted if it executes under the UTM within 
Was_Its_Execution_Aborted()!

However, another program CAN be constructed on the basis of 
Was_Its_Execution_Aborted() that:
-   halts if Was_Its_Execution_Aborted() decides "aborted"
-   loops if Was_Its_Execution_Aborted() decides "halted"

(right?)

So your new question literally interpreted is irrelevant to the "does it 
/actually/ halt" problem.  (I.e. the one discussed in the literature and 
specifically the Linz proof.)

Let me give an example which makes that obvious...

Suppose I wrote an implementation of bool Was_Its_Execution_Aborted(u32 
P, u32 I) which works like this:
1.  Run P in our UTM until either it halts by itself,
     or 5 instructions have been executed.
2.  If P halted by itself, report back that P halted.
3.  Otherwise abort P, and report back that P was aborted.

As you say, Was_Its_Execution_Aborted() can (will!) give a correct 
answer to the question "Would P's execution under the UTM within 
Was_Its_Execution_Aborted() be aborted?"

For example, let's suppose that P actually does halt but it takes 500 
instructions.  OK, we now have to perform two experiments to check 
whether Was_Its_Execution_Aborted() is answering correctly:
-  first we run Was_Its_Execution_Aborted(P, I) and
    note that it returns "execution was aborted".
-  next we trace step by step through
    Was_Its_Execution_Aborted(H_Hat, H_Hat), and note that
    indeed the execution of H_Hat WAS aborted!

Was_Its_Execution_Aborted() managed to answer correctly!  Yipeee.

(Alternatively we could combine both of these experiments into one, 
looking for two things at once, but conceptually we have two separate 
experiments.)

Unfortunately, it is now obvious that asking the question "Would P's 
execution under the UTM within Was_Its_Execution_Aborted() be aborted?" 
is not equivalent to the halting question, and the fact that such a new 
question can be correctly answered has no relevence to the HP question 
or to Linz proof.

In fact doesn't the new question, literally interpreted as above, seem a 
little facile?

The only way to make your new question relevant to the Linz proof would 
be if your implementation of Was_Its_Execution_Aborted() had the 
additional characteristics:

a)  if Was_Its_Execution_Aborted() returns "program halted"
     then H_Hat(H_Hat) [IF RUN NATIVELY] will actually terminate
b)  if Was_Its_Execution_Aborted() returns "program aborted"
     then H_Hat(H_Hat) [IF RUN NATIVELY] will never halt

If Was_Its_Execution_Aborted() had those properties, it could just be 
name-changed to Does_It_Halt() and I think you've already admitted 
elsewhere the Linz argument is correct with the [IF RUN NATIVELY] 
proviso, and so this can't be possible.

>
> All of the cases where Was_Its_Execution_Aborted() returns true are
> cases of non-halting behavior.
>
> All of the cases where Was_Its_Execution_Aborted() returns false are
> cases of halting behavior.
>

Um, ok, that /sounds/ like you're saying it has characteristics (a) and 
(b) above?  In which case although it may be answering your new 
question, IT WOULD AT THE SAME TIME BE CORRECTLY ANSWERING THE OLD QUESTION!

..And it can't be doing that, because then H_Hat could employ the "do 
the opposite of what H() says strategy, which I think you've agreed 
elsewhere works for the OLD question.

Is the issue here that when you say "cases of non-halting behavior", you 
mean something other than "cases where P run with input I never halts 
[when run natively]"?

Thinking about it, your use of the term "non-halting *behavior*" seems a 
likely area of confusion!

What exactly do you mean by "cases of non-halting behavior"?

And just to be doubly clear, does this /mean/ the same as "program run 
/natively/ with given input never halts"?  (I.e. in the usual sense of 
"non-halting TMs" in the literature and HP proof?)

>> It's almost as though you accept there is nothing wrong with it, and
>> yet you still think its conclusion is incorrect!  Or that you can't
>> see anything wrong with it, and in your head the mistake in the proof
>> is that its conclusion is wrong? (Thinking a conclusion is wrong does
>> not refute anything...)
>>
>> Anyhow, you talk about the halt decider reporting that it "aborted its
>> input program, because blah blah".  If you read the Linz proof, you'll
>> notice that it is completely unaffected of any internal reasoning as
>> to WHY H might have made whatever decision it made.  All it depends on
>> is that H actually makes a decision!
>>
>
> In the Linz case if a program would not halt and we are asking would it
> halt and we abort the execution of H_Hat() then H() gets the wrong
> answer because H() says that it would not halt and it does halt.
>
> If we keep everything else the same except change the question to:
> Was the input program aborted because it would not otherwise terminate?
>
> Now when we answer yes we get the right answer. H_hat() cannot possibly
> do the opposite of what H() decides because H_Hat() is under the
> complete control of H().
>

..but as explained above, H_Hat CAN have the behaviour that it halts if 
H() decides it was aborted, and it loops if H() decides it terminated.

(The H_Hat in your skeleton code is designed exactly this way.)

[... snip ...]
>> So... this was to be the culmination of your life's work, and now
>> you're simply not going to publish it?  I thought the whole purpose of
>
> I didn't say that. As soon as people pay enough attention they will see
> that I am correct.

I fear this is one of your delusions!  Your proof is almost nonexistent 
- stepping back a bit I can cast it as another version of your numerous 
attempts to refute various proofs by redefining key terms in the proof, 
then pointing out that the proof no longer works using those new terms. 
I don't believe /anyone/ has ever agreed with /any/ of those attempts, 
so I can't see them starting now.

In the end you will be left with the choice of "proving them wrong" by 
publishing the code anyway (and I think you can see by now that will get 
you nowhere), or abandoning your life's work, having wasted 12,000 hours 
(your own reckoning) unnecessarily.

It's slightly interesting that 12,000 is exactly the figure Dudley 
quotes that one of his Trisectors spent on the trisection problem in his 
essay:

<http://web.mst.edu/~lmhall/WhatToDoWhenTrisectorComes.pdf>

He remarks (of the trisector of course, not of you):

"Twelve thousand working hours!  Full time is forty hours a week for 
fifty weeks, so the poor deluded man had devoted the equivalent of six 
years of his life to something as useless as finding two even numbers 
whose sum is odd.  What wouldn't you or I give for an extra six years of 
time?  What couldn't we accomplish?  What a deplorable waste!"

In your case it must seem doubly wasteful, in that you could be exactly 
where you are now if you had simply published your high level design at 
the start of all this.  (Well, I suppose then you wouldn't have your x86 
emulator program, so there's some compensation...)

Mike.

[toc] | [prev] | [next] | [standalone]


#24165 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 18:05 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<vMadnaxSWr-njQ_CnZ2dnUU7-VXNnZ2d@giganews.com>
In reply to#24164
On 10/22/2020 5:14 PM, Mike Terry wrote:
> On 22/10/2020 17:38, olcott wrote:
>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>> On 22/10/2020 15:36, olcott wrote:
>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>
>>>>>> The difference is that it is no longer possible for H_Hat() to do the
>>>>>> opposite of what H() decides. This transforms an undecidable problem
>>>>>> into a decidable problem.
>>>>>
>>>>> If H_Hat no longer does what the proof defined, then your 
>>>>> demonstration
>>>>> is no longer applicable to the proof.
>>>>>
>>>>
>>>> If the halt decider is to report whether or not its input halts another
>>>> program can be constructed on the the basis of this halt decider that
>>>> does the opposite of whatever the halt decider decides.
>>>>
>>>> This is how H() and H_Hat() are defined in the Linz proof.
>>>>
>>>> If the halt decider is to report whether or not it aborted its input
>>>> program because its input program would otherwise cause the halt 
>>>> decider
>>>> to get stuck in infinite execution then this other program can no 
>>>> longer
>>>> fool its halt decider and do the opposite of whatever it decides.
>>>>
>>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to
>>>> execute because H() has complete control over H_Hat.
>>>>
>>>> The end result of this slight change is that the halting problem can no
>>>> longer be shown to be undecidable.
>>>>
>>>
>>> It is suspicious that in none of this have you ever stated what is
>>> actually wrong in the Linz proof.
>>
>> When the halting problem is defined as:
>> bool Does_It_Halt(u32 P, u32 I)
>> another program can be constructed on the basis of Does_It_Halt() that
>> does the opposite of whatever Does_It_Halt() decides.
>>
> 
> Yes, regardless of the internal details of Does_It_Halt().
> 
>> When the halting problem is defined as:
>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>
>> another program CANNOT be constructed on the basis of
>> Was_Its_Execution_Aborted() that does the opposite of whatever
>> Was_Its_Execution_Aborted() decides.
> 
> Sure, if you interpret your question literally as asking whether P would 
> actually be aborted if it executes under the UTM within 
> Was_Its_Execution_Aborted()!
> 
> However, another program CAN be constructed on the basis of 
> Was_Its_Execution_Aborted() that:
> -   halts if Was_Its_Execution_Aborted() decides "aborted"
> -   loops if Was_Its_Execution_Aborted() decides "halted"
> 
> (right?)

Wrong. There is no way to make the revised halting question contradictory.

DebugTrace() either reports that it has aborted the execution of its 
input or it reports that its input has not been aborted after its input 
has terminated.

> So your new question literally interpreted is irrelevant to the "does it 
> /actually/ halt" problem.  (I.e. the one discussed in the literature and 
> specifically the Linz proof.)
> 
> Let me give an example which makes that obvious...
> 
> Suppose I wrote an implementation of bool Was_Its_Execution_Aborted(u32 
> P, u32 I) which works like this:
> 1.  Run P in our UTM until either it halts by itself,
>      or 5 instructions have been executed.
> 2.  If P halted by itself, report back that P halted.
> 3.  Otherwise abort P, and report back that P was aborted.
> 
> As you say, Was_Its_Execution_Aborted() can (will!) give a correct 
> answer to the question "Would P's execution under the UTM within 
> Was_Its_Execution_Aborted() be aborted?"
> 
> For example, let's suppose that P actually does halt but it takes 500 
> instructions.  OK, we now have to perform two experiments to check 
> whether Was_Its_Execution_Aborted() is answering correctly:
> -  first we run Was_Its_Execution_Aborted(P, I) and
>     note that it returns "execution was aborted".
> -  next we trace step by step through
>     Was_Its_Execution_Aborted(H_Hat, H_Hat), and note that
>     indeed the execution of H_Hat WAS aborted!
> 
> Was_Its_Execution_Aborted() managed to answer correctly!  Yipeee.
> 
> (Alternatively we could combine both of these experiments into one, 
> looking for two things at once, but conceptually we have two separate 
> experiments.)
> 
> Unfortunately, it is now obvious that asking the question "Would P's 
> execution under the UTM within Was_Its_Execution_Aborted() be aborted?" 
> is not equivalent to the halting question, and the fact that such a new 
> question can be correctly answered has no relevence to the HP question 
> or to Linz proof.
> 

That you can define a halt decider that does not meet the conventional 
specs of a halt decider provide zero rebuttal what-so-ever.

> In fact doesn't the new question, literally interpreted as above, seem a 
> little facile?
> 
> The only way to make your new question relevant to the Linz proof would 
> be if your implementation of Was_Its_Execution_Aborted() had the 
> additional characteristics:
> 
> a)  if Was_Its_Execution_Aborted() returns "program halted"
>      then H_Hat(H_Hat) [IF RUN NATIVELY] will actually terminate
YES

> b)  if Was_Its_Execution_Aborted() returns "program aborted"
>      then H_Hat(H_Hat) [IF RUN NATIVELY] will never halt

Not really because H_Hat() has the same halt decider as H() so when we 
run H_Hat() on itself it aborts itself.

> If Was_Its_Execution_Aborted() had those properties, it could just be 
> name-changed to Does_It_Halt() and I think you've already admitted 
> elsewhere the Linz argument is correct with the [IF RUN NATIVELY] 
> proviso, and so this can't be possible.

We could say that the Linz proof is correct on the basis of its terribly 
incorrect basic assumptions or we cold say that the Linz proof is 
fundamentally incorrect because its foundational basis is incorrect.
These are two different ways of saying the same thing.

>>
>> All of the cases where Was_Its_Execution_Aborted() returns true are
>> cases of non-halting behavior.
>>
>> All of the cases where Was_Its_Execution_Aborted() returns false are
>> cases of halting behavior.
>>
> 
> Um, ok, that /sounds/ like you're saying it has characteristics (a) and 
> (b) above?  In which case although it may be answering your new 
> question, IT WOULD AT THE SAME TIME BE CORRECTLY ANSWERING THE OLD 
> QUESTION!

No because in the case where DebugTrace() decides to abort its input in 
the prior language this would be a case where H() decides not halting 
and then H_Hat() halts.

> ..And it can't be doing that, because then H_Hat could employ the "do 
> the opposite of what H() says strategy, which I think you've agreed 
> elsewhere works for the OLD question.
> 
> Is the issue here that when you say "cases of non-halting behavior", you 
> mean something other than "cases where P run with input I never halts 
> [when run natively]"?
> 

Not exactly.
Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't 
really say that when it runs natively it never halts. We can say that 
unless H_Hat() is aborted it would never halt.

> Thinking about it, your use of the term "non-halting *behavior*" seems a 
> likely area of confusion!
> 
> What exactly do you mean by "cases of non-halting behavior"?

The obvious one is infinite loop. Can you think of the other one?

> And just to be doubly clear, does this /mean/ the same as "program run 
> /natively/ with given input never halts"?  (I.e. in the usual sense of 
> "non-halting TMs" in the literature and HP proof?)
> 

If H_Hat() is run and never aborted it would never halt.
If it is executed with itself as input its invocation of DebugTrace() 
would abort this input.

>>> It's almost as though you accept there is nothing wrong with it, and
>>> yet you still think its conclusion is incorrect!  Or that you can't
>>> see anything wrong with it, and in your head the mistake in the proof
>>> is that its conclusion is wrong? (Thinking a conclusion is wrong does
>>> not refute anything...)
>>>
>>> Anyhow, you talk about the halt decider reporting that it "aborted its
>>> input program, because blah blah".  If you read the Linz proof, you'll
>>> notice that it is completely unaffected of any internal reasoning as
>>> to WHY H might have made whatever decision it made.  All it depends on
>>> is that H actually makes a decision!
>>>
>>
>> In the Linz case if a program would not halt and we are asking would it
>> halt and we abort the execution of H_Hat() then H() gets the wrong
>> answer because H() says that it would not halt and it does halt.
>>
>> If we keep everything else the same except change the question to:
>> Was the input program aborted because it would not otherwise terminate?
>>
>> Now when we answer yes we get the right answer. H_hat() cannot possibly
>> do the opposite of what H() decides because H_Hat() is under the
>> complete control of H().
>>
> 
> ..but as explained above, H_Hat CAN have the behaviour that it halts if 
> H() decides it was aborted, and it loops if H() decides it terminated.

As soon as H_Hat() is terminated and DebugTrace() returns a value the 
H_Hat() process ceases to exist in memory because it was stored on the 
DebugTrace() stack.

> (The H_Hat in your skeleton code is designed exactly this way.)

It is designed to precisely match the Linz templates.


> [... snip ...]
>>> So... this was to be the culmination of your life's work, and now
>>> you're simply not going to publish it?  I thought the whole purpose of
>>
>> I didn't say that. As soon as people pay enough attention they will see
>> that I am correct.
> 
> I fear this is one of your delusions!  Your proof is almost nonexistent 

My proof is very very concise yet infinitely more elborate than any 
rebuttals of it.

Try and show how a non existent H_Hat() that no longer exists as a 
process in memory can do anything at all and you will start to begin to 
see that changing the halt deciding question converts an undecidable 
problem into a decidable one.

> - stepping back a bit I can cast it as another version of your numerous 
> attempts to refute various proofs by redefining key terms in the proof, 
> then pointing out that the proof no longer works using those new terms. 
> I don't believe /anyone/ has ever agreed with /any/ of those attempts, 
> so I can't see them starting now.
> 

That no one agrees with me is zero rebuttal at all.

> In the end you will be left with the choice of "proving them wrong" by 
> publishing the code anyway (and I think you can see by now that will get 
> you nowhere), or abandoning your life's work, having wasted 12,000 hours 
> (your own reckoning) unnecessarily.
> 

Take my challenge and show how the H_Hat() process that no longer exists 
in memory can do anything at all that is the opposite of what 
DebugTrace() decided.


> It's slightly interesting that 12,000 is exactly the figure Dudley 
> quotes that one of his Trisectors spent on the trisection problem in his 
> essay:
> 
> <http://web.mst.edu/~lmhall/WhatToDoWhenTrisectorComes.pdf>
> 
> He remarks (of the trisector of course, not of you):
> 
> "Twelve thousand working hours!  Full time is forty hours a week for 
> fifty weeks, so the poor deluded man had devoted the equivalent of six 
> years of his life to something as useless as finding two even numbers 
> whose sum is odd.  What wouldn't you or I give for an extra six years of 
> time?  What couldn't we accomplish?  What a deplorable waste!"
> 
> In your case it must seem doubly wasteful, in that you could be exactly 
> where you are now if you had simply published your high level design at 
> the start of all this.  (Well, I suppose then you wouldn't have your x86 
> emulator program, so there's some compensation...)
> 
> Mike.
> 


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24169 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-22 16:55 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<fdc8452d-df92-48f9-b8c3-4a12a7010ab1n@googlegroups.com>
In reply to#24165
On Friday, 23 October 2020 at 00:05:38 UTC+1, olcott wrote:
> On 10/22/2020 5:14 PM, Mike Terry wrote: 

> > Is the issue here that when you say "cases of non-halting behavior", you 
> > mean something other than "cases where P run with input I never halts 
> > [when run natively]"? 
> >
> Not exactly. 
> Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't 
> really say that when it runs natively it never halts. We can say that 
> unless H_Hat() is aborted it would never halt.
>
Abortion is sticky. So one there is an abortion anywhere in the system, the
whole thing aborts. If you are running DebugTrace, this isn't a problem -
just shunt the "abortion" condition up the instances.
However a Turing machine can't abort itself. 

 

[toc] | [prev] | [next] | [standalone]


#24171 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 19:29 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<z_OdnS-iof9Ovg_CnZ2dnUU7-bPNnZ2d@giganews.com>
In reply to#24169
On 10/22/2020 6:55 PM, Malcolm McLean wrote:
> On Friday, 23 October 2020 at 00:05:38 UTC+1, olcott wrote:
>> On 10/22/2020 5:14 PM, Mike Terry wrote:
> 
>>> Is the issue here that when you say "cases of non-halting behavior", you
>>> mean something other than "cases where P run with input I never halts
>>> [when run natively]"?
>>>
>> Not exactly.
>> Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't
>> really say that when it runs natively it never halts. We can say that
>> unless H_Hat() is aborted it would never halt.
>>
> Abortion is sticky. So one there is an abortion anywhere in the system, the
> whole thing aborts. If you are running DebugTrace, this isn't a problem -
> just shunt the "abortion" condition up the instances.
> However a Turing machine can't abort itself.

H() executes DebugTrace() that creates a separate virtual machine 
process and executes H_Hat() that executes DebugTrace() that creates a 
separate virtual machine process and executes another H_Hat() process.

If DebugTrace() returns a value where 1 == Halts and 0 == ~Halts then 
the conventional self-referential halting problem proof counter-example 
can be created where H_Hat() does the opposite of whatever H() decides.

H() decides Halts so H_Hat Loops
H() decides Loops so H_Hat Halts

If DebugTrace() returns a value where 1 == Aborted and 0 == ~Aborted 
then the conventional self-referential halting problem proof 
counter-example CANNOT be created and H_Hat() CANNOT do the opposite of 
whatever H() decides.

H() decides Aborted so H_Hat has already ceased to exist.
H() decides ~Aborted so H_Hat is allowed to execute to completion.

There are no longer any halting problem cases that can be shown to be 
undecidable with the revised definition of the halt decider.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24176 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-22 18:06 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<85eda149-3f0b-4162-ad98-416baa1c7057n@googlegroups.com>
In reply to#24171
On Friday, 23 October 2020 at 01:29:15 UTC+1, olcott wrote:
> On 10/22/2020 6:55 PM, Malcolm McLean wrote: 
> > On Friday, 23 October 2020 at 00:05:38 UTC+1, olcott wrote: 
> >> On 10/22/2020 5:14 PM, Mike Terry wrote: 
> > 
> >>> Is the issue here that when you say "cases of non-halting behavior", you 
> >>> mean something other than "cases where P run with input I never halts 
> >>> [when run natively]"? 
> >>> 
> >> Not exactly. 
> >> Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't 
> >> really say that when it runs natively it never halts. We can say that 
> >> unless H_Hat() is aborted it would never halt. 
> >> 
> > Abortion is sticky. So one there is an abortion anywhere in the system, the 
> > whole thing aborts. If you are running DebugTrace, this isn't a problem - 
> > just shunt the "abortion" condition up the instances. 
> > However a Turing machine can't abort itself.
> H() executes DebugTrace() that creates a separate virtual machine 
> process and executes H_Hat() that executes DebugTrace() that creates a 
> separate virtual machine process and executes another H_Hat() process. 
> 
> If DebugTrace() returns a value where 1 == Halts and 0 == ~Halts then
> the conventional self-referential halting problem proof counter-example
> can be created where H_Hat() does the opposite of whatever H() decides. 
> 
> H() decides Halts so H_Hat Loops 
> H() decides Loops so H_Hat Halts 
> 
> If DebugTrace() returns a value where 1 == Aborted and 0 == ~Aborted 
> then the conventional self-referential halting problem proof 
> counter-example CANNOT be created and H_Hat() CANNOT do the opposite of 
> whatever H() decides. 
> 
> H() decides Aborted so H_Hat has already ceased to exist. 
> H() decides ~Aborted so H_Hat is allowed to execute to completion. 
> 
> There are no longer any halting problem cases that can be shown to be 
> undecidable with the revised definition of the halt decider.
> 
If we call H_Hat directly, there are two instances of H_Hat.

There are several ways of looking at what you are doing, depending 
on the exact details of the "abort" logic. One is to say that the Halt decider
isn't a Turing machine because it can destroy its own execution environment.
Then Linz's proof doesn't apply. Another way of looking at it is to say that
you've a hidden parameter (the number of live instances of H_Hat) which
allows you to toggle the behaviour. 

[toc] | [prev] | [next] | [standalone]


#24179 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-22 20:26 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<CsKdnR6NKOrHrA_CnZ2dnUU7-ffNnZ2d@giganews.com>
In reply to#24176
On 10/22/2020 8:06 PM, Malcolm McLean wrote:
> On Friday, 23 October 2020 at 01:29:15 UTC+1, olcott wrote:
>> On 10/22/2020 6:55 PM, Malcolm McLean wrote:
>>> On Friday, 23 October 2020 at 00:05:38 UTC+1, olcott wrote:
>>>> On 10/22/2020 5:14 PM, Mike Terry wrote:
>>>
>>>>> Is the issue here that when you say "cases of non-halting behavior", you
>>>>> mean something other than "cases where P run with input I never halts
>>>>> [when run natively]"?
>>>>>
>>>> Not exactly.
>>>> Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't
>>>> really say that when it runs natively it never halts. We can say that
>>>> unless H_Hat() is aborted it would never halt.
>>>>
>>> Abortion is sticky. So one there is an abortion anywhere in the system, the
>>> whole thing aborts. If you are running DebugTrace, this isn't a problem -
>>> just shunt the "abortion" condition up the instances.
>>> However a Turing machine can't abort itself.
>> H() executes DebugTrace() that creates a separate virtual machine
>> process and executes H_Hat() that executes DebugTrace() that creates a
>> separate virtual machine process and executes another H_Hat() process.
>>
>> If DebugTrace() returns a value where 1 == Halts and 0 == ~Halts then
>> the conventional self-referential halting problem proof counter-example
>> can be created where H_Hat() does the opposite of whatever H() decides.
>>
>> H() decides Halts so H_Hat Loops
>> H() decides Loops so H_Hat Halts
>>
>> If DebugTrace() returns a value where 1 == Aborted and 0 == ~Aborted
>> then the conventional self-referential halting problem proof
>> counter-example CANNOT be created and H_Hat() CANNOT do the opposite of
>> whatever H() decides.
>>
>> H() decides Aborted so H_Hat has already ceased to exist.
>> H() decides ~Aborted so H_Hat is allowed to execute to completion.
>>
>> There are no longer any halting problem cases that can be shown to be
>> undecidable with the revised definition of the halt decider.
>>
> If we call H_Hat directly, there are two instances of H_Hat.
> 
> There are several ways of looking at what you are doing, depending
> on the exact details of the "abort" logic. One is to say that the Halt decider
> isn't a Turing machine because it can destroy its own execution environment.

Think of it in terms of a UTM the simply decides to stop executing its TM.

> Then Linz's proof doesn't apply. Another way of looking at it is to say that
> you've a hidden parameter (the number of live instances of H_Hat) which
> allows you to toggle the behaviour.
> 

x86utm execute main() that executes H() that executes DebugTrace() that 
creates a whole new process that executes H_Hat() in DebugStep() mode 
that executes DebugTrace() that creates a whole new process that 
executes H_hat() in DebugStep() mode.

Nothing is hidden DebugStep() can see every single detail of every 
process that it executes and it can store some (or all) of these details 
to be used later.

Since DebugTrace() itself is executed in its own process it can keep the 
details of its own slave process separate from every other invocation of 
every other slave process.





-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24257 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-23 23:51 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<QvSdnW7sQP0dww7CnZ2dnUU78TfNnZ2d@brightview.co.uk>
In reply to#24165
On 23/10/2020 00:05, olcott wrote:
> On 10/22/2020 5:14 PM, Mike Terry wrote:
>> On 22/10/2020 17:38, olcott wrote:
>>> On 10/22/2020 10:25 AM, Mike Terry wrote:
>>>> On 22/10/2020 15:36, olcott wrote:
>>>>> On 10/22/2020 7:00 AM, Richard Damon wrote:
>>>>>> On 10/22/20 12:33 AM, olcott wrote:
>>>>>>>
>>>>>>> The difference is that it is no longer possible for H_Hat() to do
>>>>>>> the
>>>>>>> opposite of what H() decides. This transforms an undecidable problem
>>>>>>> into a decidable problem.
>>>>>>
>>>>>> If H_Hat no longer does what the proof defined, then your
>>>>>> demonstration
>>>>>> is no longer applicable to the proof.
>>>>>>
>>>>>
>>>>> If the halt decider is to report whether or not its input halts
>>>>> another
>>>>> program can be constructed on the the basis of this halt decider that
>>>>> does the opposite of whatever the halt decider decides.
>>>>>
>>>>> This is how H() and H_Hat() are defined in the Linz proof.
>>>>>
>>>>> If the halt decider is to report whether or not it aborted its input
>>>>> program because its input program would otherwise cause the halt
>>>>> decider
>>>>> to get stuck in infinite execution then this other program can no
>>>>> longer
>>>>> fool its halt decider and do the opposite of whatever it decides.
>>>>>
>>>>> If H() aborts the execution of H_Hat() then H_Hat() cannot continue to
>>>>> execute because H() has complete control over H_Hat.
>>>>>
>>>>> The end result of this slight change is that the halting problem
>>>>> can no
>>>>> longer be shown to be undecidable.
>>>>>
>>>>
>>>> It is suspicious that in none of this have you ever stated what is
>>>> actually wrong in the Linz proof.
>>>
>>> When the halting problem is defined as:
>>> bool Does_It_Halt(u32 P, u32 I)
>>> another program can be constructed on the basis of Does_It_Halt() that
>>> does the opposite of whatever Does_It_Halt() decides.
>>>
>>
>> Yes, regardless of the internal details of Does_It_Halt().
>>
>>> When the halting problem is defined as:
>>> bool Was_Its_Execution_Aborted(u32 P, u32 I)
>>>
>>> another program CANNOT be constructed on the basis of
>>> Was_Its_Execution_Aborted() that does the opposite of whatever
>>> Was_Its_Execution_Aborted() decides.
>>
>> Sure, if you interpret your question literally as asking whether P
>> would actually be aborted if it executes under the UTM within
>> Was_Its_Execution_Aborted()!
>>
>> However, another program CAN be constructed on the basis of
>> Was_Its_Execution_Aborted() that:
>> -   halts if Was_Its_Execution_Aborted() decides "aborted"
>> -   loops if Was_Its_Execution_Aborted() decides "halted"
>>
>> (right?)
>
> Wrong.

No, right.  To avoid a silly pantomine argument, here is an example of 
such a function:


int H_Hat(u32 M)
{
    if (Was_Its_Execution_Aborted(M, M))
    {
      // Was_Its_Execution_Aborted says that M(M) was aborted
      HALT;       // so we halt
    }
    else
    {
      // Was_Its_Execution_Aborted says that M(M) halted
      HERE: goto HERE;   // so we loop
    }
}

and for completeness, here is the function being invoked from main():

int main()
{
    u32 M = (u32)H_Hat;

    H_Hat(M);       // run H_Hat with input H_Hat
    HALT;
}

You see, H_Hat /is/ constructed so that if  Was_Its_Execution_Aborted(M, 
M) returns "aborted" (nonzero), H_Hat will halt, and if 
Was_Its_Execution_Aborted(M, M) returns "halted" (zero), H_Hat will 
loop.  Just like I said.  Thre is no subtle philosophical point here, 
just beginner knowledge of the C programming language.

(To save you making a silly response, yes IF we were to run the program 
under a debugger or emulator of some kind, and we aborted the run at the 
"if (Abort)" statement or earlier, then of course we would not get to 
see what it actually does next.  (Duh.)  That's irrelevent because 
regardless of this, H_Hat as constructed meets the conditions just as I 
described.)

 > There is no way to make the revised halting question contradictory.
>
> DebugTrace() either reports that it has aborted the execution of its
> input or it reports that its input has not been aborted after its input
> has terminated.
>

[A quick observation: you've flipped to talking about DebugTrace() 
rather than Was_Its_Execution_Aborted() which we were discussing.  I'll 
just take it they're the same thing, and continue saying 
Was_Its_Execution_Aborted().]

I never said otherwise.

BUT bear in mind that H (as opposed to Was_Its_Execution_Aborted()) 
plays the role in all this of a Linz *Halt Decider*, and so is required 
to deliver its HD decision *HALT* or *NOT_HALT*.  (It does not output 
any decision on whether some internal routine made some particular 
decision and ceased emulating something or other - all that is beside 
the point from the Linz proof perspective.)

If you want to change the interpretation of the return code from 
Was_Its_Execution_Aborted() to mean something other than HALT/NOT_HALT, 
then you will now have to provide extra logic in H, and hence also in 
H_Hat, to convert that return code into its final HALT/NOT_HALT 
decision.  (Regardless of your new question, H must still deliver the 
Halting Decider required output.)

There's really nothing to be gained from choosing to do this. 
Originally the reason for extracting the Halt Decider logic into a 
separate routine outside of H() was that exactly the same logic needed 
to be employed in both H() and H_Hat().  The role of H in the Linz proof 
is to make the Halt Decider decision of either HALT or NOT_HALT, and so 
if we extract the logic into an external routine, it's pointless for 
that routine to return anything other than HALT/NOT_HALT.  Given that 
your Was_Its_Execution_Aborted() does not return HALT/NOT_HALT then the 
thing to do is call it from within the halt decider logic routine.

Here is a revised program, showing just that:

...
int DeciderLogic (u32 M, u32 I)
{
    bool aborted;
    int  HD_decision;

    aborted = Was_Its_Execution_Aborted (M, I);

    // set HD_decision to RC_HALT/RC_NOT_HALT based on aborted
    ...

    return HD_decision;
}

int H_Hat(u32 M)
{
    if (DeciderLogic(M,M) == RC_HALT)
    {
      // DeciderLogicsays that M(M) does not halts, so we halt
      HALT;
    }
    else
    {
      // DeciderLogicsays that M(M) halts, so we loop
      HERE: goto HERE;
    }
}

For completeness, the H routine would be a minimal wrapper because we've 
sensibly modularised DeciderLogic():

int H (u32 M, u32 I)
{
    if (DeciderLogic(M,I) == RC_HALT)
       MOV_EAX_1;
    else
       MOV_EAX_0;
    HALT;
}

Note in H there is no need to convert Was_Its_Execution_Aborted's return 
code, because DeciderLogic() returned the appropriate data of direct 
interest to both H() and H_Hat().

Also, what is important in the (adapted) Linz proof is the return code 
from DeciderLogic(), NOT the return code from 
Was_Its_Execution_Aborted().  The contridiction derived in the proof 
comes from examining the former, and you have clearly not made that go 
away...

In any case, WHAT IS THE MISSING CODE TO COMPLETE DeciderLogic() ABOVE, 
i.e. which converts Was_Its_Execution_Aborted() return code to 
HALT/NOT_HALT decision?


>> So your new question literally interpreted is irrelevant to the "does
>> it /actually/ halt" problem.  (I.e. the one discussed in the
>> literature and specifically the Linz proof.)
>>
>> Let me give an example which makes that obvious...
>>
>> Suppose I wrote an implementation of bool
>> Was_Its_Execution_Aborted(u32 P, u32 I) which works like this:
>> 1.  Run P in our UTM until either it halts by itself,
>>      or 5 instructions have been executed.
>> 2.  If P halted by itself, report back that P halted.
>> 3.  Otherwise abort P, and report back that P was aborted.
>>
>> As you say, Was_Its_Execution_Aborted() can (will!) give a correct
>> answer to the question "Would P's execution under the UTM within
>> Was_Its_Execution_Aborted() be aborted?"
>>
>> For example, let's suppose that P actually does halt but it takes 500
>> instructions.  OK, we now have to perform two experiments to check
>> whether Was_Its_Execution_Aborted() is answering correctly:
>> -  first we run Was_Its_Execution_Aborted(P, I) and
>>     note that it returns "execution was aborted".
>> -  next we trace step by step through
>>     Was_Its_Execution_Aborted(H_Hat, H_Hat), and note that
>>     indeed the execution of H_Hat WAS aborted!
>>
>> Was_Its_Execution_Aborted() managed to answer correctly!  Yipeee.
>>
>> (Alternatively we could combine both of these experiments into one,
>> looking for two things at once, but conceptually we have two separate
>> experiments.)
>>
>> Unfortunately, it is now obvious that asking the question "Would P's
>> execution under the UTM within Was_Its_Execution_Aborted() be
>> aborted?" is not equivalent to the halting question, and the fact that
>> such a new question can be correctly answered has no relevence to the
>> HP question or to Linz proof.
>>
>
> That you can define a halt decider that does not meet the conventional
> specs of a halt decider provide zero rebuttal what-so-ever.
>

It refutes the idea that merely "changing the question" and having a 
routine that can answer the new question correctly refutes the Linz 
proof.  My example has a routine which correctly answers your new 
question but obviously doesn't refute anything in Linz.

>> In fact doesn't the new question, literally interpreted as above, seem
>> a little facile?
>>
>> The only way to make your new question relevant to the Linz proof
>> would be if your implementation of Was_Its_Execution_Aborted() had the
>> additional characteristics:
>>
>> a)  if Was_Its_Execution_Aborted() returns "program halted"
>>      then H_Hat(H_Hat) [IF RUN NATIVELY] will actually terminate
> YES
>
>> b)  if Was_Its_Execution_Aborted() returns "program aborted"
>>      then H_Hat(H_Hat) [IF RUN NATIVELY] will never halt
>
> Not really because H_Hat() has the same halt decider as H() so when we
> run H_Hat() on itself it aborts itself.
>

You have a MAJOR confusion here and elsewhere in your post.  H_Hat() 
never aborts "itself"!  It /could/ call HALT, I guess, and we /might/ 
label that as an "abort" but in fact it /doesn't/ do that, and that's 
not what you meant anyway. :)

Hey! I've just realised that H_Hat actually /does/ call HALT in one of 
its branches.  Of course that's not an "abort", just the normal required 
"end of program" halt state call.  Hehe.

Here is what /actually/ happens, based on my last skeleton code above:

H_Hat starts (main() calls H_Hat(H_Hat))
   H_Hat calls DeciderLogic(H_Hat,H_Hat)
     DeciderLogic calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
       Was_Its_Execution_Aborted decides the emulation is looping
       Was_Its_Execution_Aborted stops emulating and returns ABORTED
     DeciderLogic converts ABORTED to HALT/NOT_HALT and returns result
   H_Hat does the opposite of HALT/NOT_HALT

For comparison here is what H does:

H starts (main() calls H(H_Hat,H_Hat))
   H calls DeciderLogic(H_Hat,H_Hat)
     DeciderLogic calls Was_Its_Execution_Aborted(H_Hat,H_Hat)
       Was_Its_Execution_Aborted emulates H_Hat(H_Hat)
       Was_Its_Execution_Aborted decides the emulation is looping
       Was_Its_Execution_Aborted stops emulating and returns ABORTED
     DeciderLogic converts ABORTED to HALT/NOT_HALT and returns result
   H_Hat halts indicating decision returned by DeciderLogic

So you see, H_Hat never aborts "itself" - it just decides to stop 
emulating something or other, which may happen to be its own program code.

IT'S OWN PROGRAM CODE IS NOT "ITSELF".  "Itself" refers to code running 
in the machine which IT is running in.  In our case, this is the (H_Hat) 
machine: the first trace above, which starts with main() calling 
H_Hat(H_Hat).  There is nothing to "abort" that.  In that machine there 
is an emulation of H_Hat, which we could say is "aborted", but not by 
"itself" [not by the emulated H_Hat].

Anyway, we can see from comparing H and H_Hat runs above that despite 
introducing the unnecessary "new question" routine, nothing substantial 
has changed, and the results AGREE with the Linz proof.  Your 
"refutation" has failed.

At this point, I can't think of what else needs to be said, so I'm 
basically stopping, but I'll carry on making perfunctory comments below.

Mike.

>> If Was_Its_Execution_Aborted() had those properties, it could just be
>> name-changed to Does_It_Halt() and I think you've already admitted
>> elsewhere the Linz argument is correct with the [IF RUN NATIVELY]
>> proviso, and so this can't be possible.
>
> We could say that the Linz proof is correct on the basis of its terribly
> incorrect basic assumptions or we cold say that the Linz proof is
> fundamentally incorrect because its foundational basis is incorrect.
> These are two different ways of saying the same thing.
>
>>>
>>> All of the cases where Was_Its_Execution_Aborted() returns true are
>>> cases of non-halting behavior.
>>>
>>> All of the cases where Was_Its_Execution_Aborted() returns false are
>>> cases of halting behavior.
>>>
>>
>> Um, ok, that /sounds/ like you're saying it has characteristics (a)
>> and (b) above?  In which case although it may be answering your new
>> question, IT WOULD AT THE SAME TIME BE CORRECTLY ANSWERING THE OLD
>> QUESTION!
>
> No because in the case where DebugTrace() decides to abort its input in
> the prior language this would be a case where H() decides not halting
> and then H_Hat() halts.
>

IF Was_Its_Execution_Aborted() has properties (a) and (b), and returns 
"aborted", the H_Hat(H_Hat) will never halt.  Check what property (b) 
says.

So /assuming/ Was_Its_Execution_Aborted() is correct about its own 
aborted decision, /and/ that (b) holds, it /would/ be the case that 
H_Hat(H_Hat) will never halt, and so we could correctly take "aborted" 
as indicating a NO answer to the old question "Does H_Hat(H_Hat) halt?"

What you're saying is that this leads to a contradiction.  Of course it 
does - that's the basis of the Linz proof.

And if Was_Its_Execution_Aborted() doesn't have property (b) that's 
another kettle of fish.

>> ..And it can't be doing that, because then H_Hat could employ the "do
>> the opposite of what H() says strategy, which I think you've agreed
>> elsewhere works for the OLD question.
>>
>> Is the issue here that when you say "cases of non-halting behavior",
>> you mean something other than "cases where P run with input I never
>> halts [when run natively]"?
>>
>
> Not exactly.
> Since the invocation of DebugTrace() by H_Hat() aborts H_Hat() we can't
> really say that when it runs natively it never halts. We can say that
> unless H_Hat() is aborted it would never halt.
>
>> Thinking about it, your use of the term "non-halting *behavior*" seems
>> a likely area of confusion!
>>
>> What exactly do you mean by "cases of non-halting behavior"?
>
> The obvious one is infinite loop. Can you think of the other one?
>

There are other scenarios where a TM does not halt, but the TM is not in 
a "loop".  I.e. it need not be the case that there is a cycle of machine 
calculation states being repeated.  I see several other people have 
pointed this out to you.  (Well, maybe some authors call all non-halting 
behaviour "loops", which would encourage this misconception.)

I suppose that for your limited purposes (exhibiting one specific H and 
H^) it can be arranged that the only non-halting behaviour of interest 
is the tight loop in H_Hat, and loops like that easy enough to identify 
in a trace...  (not that this solves your problem.)

>> And just to be doubly clear, does this /mean/ the same as "program run
>> /natively/ with given input never halts"?  (I.e. in the usual sense of
>> "non-halting TMs" in the literature and HP proof?)
>>
>
> If H_Hat() is run and never aborted it would never halt.

OK, that's saying that it is non-halting in the TM sense.

> If it is executed with itself as input its invocation of DebugTrace()
> would abort this input.
>

As above this is confusing.  "Input" is data, which cannot be aborted. 
What you mean is that H_Hat will internally run an emulation of H_Hat, 
and the emulation will be aborted by DebugTrace(), but the outer level 
H_Hat is still running and has not been aborted, so by what you've just 
said, it will run forever.  ["> If H_Hat() is run and never aborted it 
would never halt."]

[But you've already seen that leads to a contradiction, because 
DeciderLogic will presumably map "aborted" to RC_NOT_HALT(??), and the 
(outer) H_Hat(H_Hat) reacts to that by halting.  So DebugTrace() has 
/incorrectly/ detected "non-halting behaviour" for H_Hat(H_Hat)...]

>>>> It's almost as though you accept there is nothing wrong with it, and
>>>> yet you still think its conclusion is incorrect!  Or that you can't
>>>> see anything wrong with it, and in your head the mistake in the proof
>>>> is that its conclusion is wrong? (Thinking a conclusion is wrong does
>>>> not refute anything...)
>>>>
>>>> Anyhow, you talk about the halt decider reporting that it "aborted its
>>>> input program, because blah blah".  If you read the Linz proof, you'll
>>>> notice that it is completely unaffected of any internal reasoning as
>>>> to WHY H might have made whatever decision it made.  All it depends on
>>>> is that H actually makes a decision!
>>>>
>>>
>>> In the Linz case if a program would not halt and we are asking would it
>>> halt and we abort the execution of H_Hat() then H() gets the wrong
>>> answer because H() says that it would not halt and it does halt.
>>>
>>> If we keep everything else the same except change the question to:
>>> Was the input program aborted because it would not otherwise terminate?
>>>
>>> Now when we answer yes we get the right answer. H_hat() cannot possibly
>>> do the opposite of what H() decides because H_Hat() is under the
>>> complete control of H().
>>>
>>
>> ..but as explained above, H_Hat CAN have the behaviour that it halts
>> if H() decides it was aborted, and it loops if H() decides it terminated.
>
> As soon as H_Hat() is terminated and DebugTrace() returns a value the
> H_Hat() process ceases to exist in memory because it was stored on the
> DebugTrace() stack.

Again, only the /emulated/ H_Hat is ever "terminated".  The outer one is 
never terminated as there's nothing in a position to do so.

>
>> (The H_Hat in your skeleton code is designed exactly this way.)
>
> It is designed to precisely match the Linz templates.
>
>
>> [... snip ...]
>>>> So... this was to be the culmination of your life's work, and now
>>>> you're simply not going to publish it?  I thought the whole purpose of
>>>
>>> I didn't say that. As soon as people pay enough attention they will see
>>> that I am correct.
>>
>> I fear this is one of your delusions!  Your proof is almost nonexistent
>
> My proof is very very concise yet infinitely more elborate than any
> rebuttals of it.
>
> Try and show how a non existent H_Hat() that no longer exists as a
> process in memory can do anything at all and you will start to begin to
> see that changing the halt deciding question converts an undecidable
> problem into a decidable one.
>
>> - stepping back a bit I can cast it as another version of your
>> numerous attempts to refute various proofs by redefining key terms in
>> the proof, then pointing out that the proof no longer works using
>> those new terms. I don't believe /anyone/ has ever agreed with /any/
>> of those attempts, so I can't see them starting now.
>>
>
> That no one agrees with me is zero rebuttal at all.
>

 From your perspective perhaps.  But you are supposed to be the rebutter 
here!  That means you have to convince everybody else that you are 
correct.  Nobody thinks you are correct, and loads of people point out 
why your rebuttal is a failure.  You just choose not to acknowledge 
their criticisms, which is ok, if a little annoying at times :)

Sounds like a stalemate?  But a stalemate is a complete failure on your 
part, as you don't get anything out of all your work - just a decrease 
in credibility, when you wanted the opposite.

>> In the end you will be left with the choice of "proving them wrong" by
>> publishing the code anyway (and I think you can see by now that will
>> get you nowhere), or abandoning your life's work, having wasted 12,000
>> hours (your own reckoning) unnecessarily.
>>
>
> Take my challenge and show how the H_Hat() process that no longer exists
> in memory can do anything at all that is the opposite of what
> DebugTrace() decided.
>

Um, ok - your confusion is over emulated vs. outer level runs of H_Hat 
as explained above.

>
>> It's slightly interesting that 12,000 is exactly the figure Dudley
>> quotes that one of his Trisectors spent on the trisection problem in
>> his essay:
>>
>> <http://web.mst.edu/~lmhall/WhatToDoWhenTrisectorComes.pdf>
>>
>> He remarks (of the trisector of course, not of you):
>>
>> "Twelve thousand working hours!  Full time is forty hours a week for
>> fifty weeks, so the poor deluded man had devoted the equivalent of six
>> years of his life to something as useless as finding two even numbers
>> whose sum is odd.  What wouldn't you or I give for an extra six years
>> of time?  What couldn't we accomplish?  What a deplorable waste!"
>>
>> In your case it must seem doubly wasteful, in that you could be
>> exactly where you are now if you had simply published your high level
>> design at the start of all this.  (Well, I suppose then you wouldn't
>> have your x86 emulator program, so there's some compensation...)
>>
>> Mike.
>>

[toc] | [prev] | [next] | [standalone]


#24258 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-23 16:03 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<cf046f4e-3283-4816-a52b-a0ace15a3214n@googlegroups.com>
In reply to#24257
On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
> 
> No, right. To avoid a silly pantomine argument, here is an example of 
> such a function: 
> 
> 
> int H_Hat(u32 M) 
> { 
> if (Was_Its_Execution_Aborted(M, M)) 
> {
// Machine no longer exists. Control flow can't get to this point. 
> // Was_Its_Execution_Aborted says that M(M) was aborted 
> HALT; // so we halt 
> } 

That's the step you are missing. At least this is what I understand. PO
sems to be changing his argument slightly and I don't want to speak for 
him.

[toc] | [prev] | [next] | [standalone]


#24260 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 18:14 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<ZcydnUMwAp5f_g7CnZ2dnUU7-VHNnZ2d@giganews.com>
In reply to#24258
On 10/23/2020 6:03 PM, Malcolm McLean wrote:
> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>
>> No, right. To avoid a silly pantomine argument, here is an example of
>> such a function:
>>
>>
>> int H_Hat(u32 M)
>> {
>> if (Was_Its_Execution_Aborted(M, M))
>> {
> // Machine no longer exists. Control flow can't get to this point.
>> // Was_Its_Execution_Aborted says that M(M) was aborted
>> HALT; // so we halt
>> }
> 
> That's the step you are missing. At least this is what I understand. PO
> sems to be changing his argument slightly and I don't want to speak for
> him.
> 

Good job. You are the only one that mostly understands me.


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24276 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromBen Bacarisse <ben.usenet@bsb.me.uk>
Date2020-10-24 01:10 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<871rho32mn.fsf@bsb.me.uk>
In reply to#24260
olcott <NoOne@NoWhere.com> writes:

> On 10/23/2020 6:03 PM, Malcolm McLean wrote:
<stuff>

> Good job. You are the only one that mostly understands me.

But do you agree with him -- that you are (a) wrong, and (b) a showman
trying to bamboozle your audience to hine an otherwise obvious trick?

-- 
Ben.

[toc] | [prev] | [next] | [standalone]


#24261 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMike Terry <news.dead.person.stones@darjeeling.plus.com>
Date2020-10-24 00:17 +0100
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<nsidnWtS_5o_-Q7CnZ2dnUU78bXNnZ2d@brightview.co.uk>
In reply to#24258
On 24/10/2020 00:03, Malcolm McLean wrote:
> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>
>> No, right. To avoid a silly pantomine argument, here is an example of
>> such a function:
>>
>>
>> int H_Hat(u32 M)
>> {
>> if (Was_Its_Execution_Aborted(M, M))
>> {
> // Machine no longer exists. Control flow can't get to this point.
>> // Was_Its_Execution_Aborted says that M(M) was aborted
>> HALT; // so we halt
>> }
>
> That's the step you are missing. At least this is what I understand. PO
> sems to be changing his argument slightly and I don't want to speak for
> him.
>

No, this is you not undertanding the whole emulation thing that's going 
on.  If you'd read on you'd have seen a quite thorough explanation of 
the flow of control that's involved.

If you read the rest of my post and are still unclear, post back and 
I'll try to explain better - but really it's all in my earlier post. 
Check out the "stack trace" (sort-of) of the two machines H and H_Hat 
running.

Mike.

[toc] | [prev] | [next] | [standalone]


#24263 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 18:31 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<MYSdnZZV8-9y-g7CnZ2dnUU7-L_NnZ2d@giganews.com>
In reply to#24261
On 10/23/2020 6:17 PM, Mike Terry wrote:
> On 24/10/2020 00:03, Malcolm McLean wrote:
>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>
>>> No, right. To avoid a silly pantomine argument, here is an example of
>>> such a function:
>>>
>>>
>>> int H_Hat(u32 M)
>>> {
>>> if (Was_Its_Execution_Aborted(M, M))
>>> {
>> // Machine no longer exists. Control flow can't get to this point.
>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>> HALT; // so we halt
>>> }
>>
>> That's the step you are missing. At least this is what I understand. PO
>> sems to be changing his argument slightly and I don't want to speak for
>> him.
>>
> 
> No, this is you not undertanding the whole emulation thing that's going 
> on.  If you'd read on you'd have seen a quite thorough explanation of 
> the flow of control that's involved.
> 
> If you read the rest of my post and are still unclear, post back and 
> I'll try to explain better - but really it's all in my earlier post. 
> Check out the "stack trace" (sort-of) of the two machines H and H_Hat 
> running.
> 
> Mike.

The outermost H_Hat() has its process terminated before:
if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().

This is because the DebugTrace() that H() invoked that created the 
process that H_Hat() resides in is a few steps ahead of what the inner 
DebugStep() invoked by H_Hat() can see.

-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24268 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-23 16:39 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<7fa1f47a-e7e4-473f-a16d-cac046f5b7c6n@googlegroups.com>
In reply to#24263
On Saturday, 24 October 2020 at 00:32:07 UTC+1, olcott wrote:
> On 10/23/2020 6:17 PM, Mike Terry wrote: 
> > On 24/10/2020 00:03, Malcolm McLean wrote: 
> >> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote: 
> >>> 
> >>> No, right. To avoid a silly pantomine argument, here is an example of 
> >>> such a function: 
> >>> 
> >>> 
> >>> int H_Hat(u32 M) 
> >>> { 
> >>> if (Was_Its_Execution_Aborted(M, M)) 
> >>> { 
> >> // Machine no longer exists. Control flow can't get to this point. 
> >>> // Was_Its_Execution_Aborted says that M(M) was aborted 
> >>> HALT; // so we halt 
> >>> } 
> >> 
> >> That's the step you are missing. At least this is what I understand. PO 
> >> sems to be changing his argument slightly and I don't want to speak for 
> >> him. 
> >> 
> > 
> > No, this is you not undertanding the whole emulation thing that's going 
> > on. If you'd read on you'd have seen a quite thorough explanation of 
> > the flow of control that's involved. 
> > 
> > If you read the rest of my post and are still unclear, post back and 
> > I'll try to explain better - but really it's all in my earlier post. 
> > Check out the "stack trace" (sort-of) of the two machines H and H_Hat 
> > running. 
> > 
> > Mike.
> The outermost H_Hat() has its process terminated before: 
> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat(). 
> 
> This is because the DebugTrace() that H() invoked that created the 
> process that H_Hat() resides in is a few steps ahead of what the inner 
> DebugStep() invoked by H_Hat() can see.
> 
You're going to have to clarify.
If H is called, DebugTrace emulates the outer instance of H_Hat, and can
abort the emulation without aborting itself.
If H_Hat is called directly, and not through H, does the outer instance of
H_Hat abort, or does it terminate normally?

[toc] | [prev] | [next] | [standalone]


#24272 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 18:54 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<UM2dnW5YuZTQ8A7CnZ2dnUU7-bHNnZ2d@giganews.com>
In reply to#24268
On 10/23/2020 6:39 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 00:32:07 UTC+1, olcott wrote:
>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>
>>>>> No, right. To avoid a silly pantomine argument, here is an example of
>>>>> such a function:
>>>>>
>>>>>
>>>>> int H_Hat(u32 M)
>>>>> {
>>>>> if (Was_Its_Execution_Aborted(M, M))
>>>>> {
>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>> HALT; // so we halt
>>>>> }
>>>>
>>>> That's the step you are missing. At least this is what I understand. PO
>>>> sems to be changing his argument slightly and I don't want to speak for
>>>> him.
>>>>
>>>
>>> No, this is you not undertanding the whole emulation thing that's going
>>> on. If you'd read on you'd have seen a quite thorough explanation of
>>> the flow of control that's involved.
>>>
>>> If you read the rest of my post and are still unclear, post back and
>>> I'll try to explain better - but really it's all in my earlier post.
>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>> running.
>>>
>>> Mike.
>> The outermost H_Hat() has its process terminated before:
>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>
>> This is because the DebugTrace() that H() invoked that created the
>> process that H_Hat() resides in is a few steps ahead of what the inner
>> DebugStep() invoked by H_Hat() can see.
>>
> You're going to have to clarify.
> If H is called, DebugTrace emulates the outer instance of H_Hat, and can
> abort the emulation without aborting itself.

As soon as DebugTrace() returns a value all of its local stack memory is 
freed and the process that it created only existed in this local stack 
memory.

> If H_Hat is called directly, and not through H, does the outer instance of
> H_Hat abort, or does it terminate normally?

Whether or not H() or H_Hat() is the outermost process that invokes the 
outermost DebugTrace() in either case this outermost DebugTrace() aborts 
the inner H_Hat() before the inner DebugTrace() returns a value to it.


-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24273 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-23 16:58 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<182c74dc-b0d4-4363-897e-e7b6392d3d28n@googlegroups.com>
In reply to#24272
On Saturday, 24 October 2020 at 00:55:00 UTC+1, olcott wrote:
> On 10/23/2020 6:39 PM, Malcolm McLean wrote: 
> > On Saturday, 24 October 2020 at 00:32:07 UTC+1, olcott wrote: 
> >> On 10/23/2020 6:17 PM, Mike Terry wrote: 
> >>> On 24/10/2020 00:03, Malcolm McLean wrote: 
> >>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote: 
> >>>>> 
> >>>>> No, right. To avoid a silly pantomine argument, here is an example of 
> >>>>> such a function: 
> >>>>> 
> >>>>> 
> >>>>> int H_Hat(u32 M) 
> >>>>> { 
> >>>>> if (Was_Its_Execution_Aborted(M, M)) 
> >>>>> { 
> >>>> // Machine no longer exists. Control flow can't get to this point. 
> >>>>> // Was_Its_Execution_Aborted says that M(M) was aborted 
> >>>>> HALT; // so we halt 
> >>>>> } 
> >>>> 
> >>>> That's the step you are missing. At least this is what I understand. PO 
> >>>> sems to be changing his argument slightly and I don't want to speak for 
> >>>> him. 
> >>>> 
> >>> 
> >>> No, this is you not undertanding the whole emulation thing that's going 
> >>> on. If you'd read on you'd have seen a quite thorough explanation of 
> >>> the flow of control that's involved. 
> >>> 
> >>> If you read the rest of my post and are still unclear, post back and 
> >>> I'll try to explain better - but really it's all in my earlier post. 
> >>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat 
> >>> running. 
> >>> 
> >>> Mike. 
> >> The outermost H_Hat() has its process terminated before: 
> >> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat(). 
> >> 
> >> This is because the DebugTrace() that H() invoked that created the 
> >> process that H_Hat() resides in is a few steps ahead of what the inner 
> >> DebugStep() invoked by H_Hat() can see. 
> >> 
> > You're going to have to clarify. 
> > If H is called, DebugTrace emulates the outer instance of H_Hat, and can 
> > abort the emulation without aborting itself.
> As soon as DebugTrace() returns a value all of its local stack memory is 
> freed and the process that it created only existed in this local stack 
> memory.
> > If H_Hat is called directly, and not through H, does the outer instance of 
> > H_Hat abort, or does it terminate normally?
> Whether or not H() or H_Hat() is the outermost process that invokes the 
> outermost DebugTrace() in either case this outermost DebugTrace() aborts 
> the inner H_Hat() before the inner DebugTrace() returns a value to it.
> 
But the when H_Hat is called directly, the outermost H_Hat terminates normally? 
Or is it aborted?

[toc] | [prev] | [next] | [standalone]


#24277 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

Fromolcott <NoOne@NoWhere.com>
Date2020-10-23 19:13 -0500
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<NoKdnbzcPOFf7A7CnZ2dnUU7-cvNnZ2d@giganews.com>
In reply to#24273
On 10/23/2020 6:58 PM, Malcolm McLean wrote:
> On Saturday, 24 October 2020 at 00:55:00 UTC+1, olcott wrote:
>> On 10/23/2020 6:39 PM, Malcolm McLean wrote:
>>> On Saturday, 24 October 2020 at 00:32:07 UTC+1, olcott wrote:
>>>> On 10/23/2020 6:17 PM, Mike Terry wrote:
>>>>> On 24/10/2020 00:03, Malcolm McLean wrote:
>>>>>> On Friday, 23 October 2020 at 23:51:47 UTC+1, Mike Terry wrote:
>>>>>>>
>>>>>>> No, right. To avoid a silly pantomine argument, here is an example of
>>>>>>> such a function:
>>>>>>>
>>>>>>>
>>>>>>> int H_Hat(u32 M)
>>>>>>> {
>>>>>>> if (Was_Its_Execution_Aborted(M, M))
>>>>>>> {
>>>>>> // Machine no longer exists. Control flow can't get to this point.
>>>>>>> // Was_Its_Execution_Aborted says that M(M) was aborted
>>>>>>> HALT; // so we halt
>>>>>>> }
>>>>>>
>>>>>> That's the step you are missing. At least this is what I understand. PO
>>>>>> sems to be changing his argument slightly and I don't want to speak for
>>>>>> him.
>>>>>>
>>>>>
>>>>> No, this is you not undertanding the whole emulation thing that's going
>>>>> on. If you'd read on you'd have seen a quite thorough explanation of
>>>>> the flow of control that's involved.
>>>>>
>>>>> If you read the rest of my post and are still unclear, post back and
>>>>> I'll try to explain better - but really it's all in my earlier post.
>>>>> Check out the "stack trace" (sort-of) of the two machines H and H_Hat
>>>>> running.
>>>>>
>>>>> Mike.
>>>> The outermost H_Hat() has its process terminated before:
>>>> if (Was_Its_Execution_Aborted(M, M)) returns a value to H_Hat().
>>>>
>>>> This is because the DebugTrace() that H() invoked that created the
>>>> process that H_Hat() resides in is a few steps ahead of what the inner
>>>> DebugStep() invoked by H_Hat() can see.
>>>>
>>> You're going to have to clarify.
>>> If H is called, DebugTrace emulates the outer instance of H_Hat, and can
>>> abort the emulation without aborting itself.
>> As soon as DebugTrace() returns a value all of its local stack memory is
>> freed and the process that it created only existed in this local stack
>> memory.
>>> If H_Hat is called directly, and not through H, does the outer instance of
>>> H_Hat abort, or does it terminate normally?
>> Whether or not H() or H_Hat() is the outermost process that invokes the
>> outermost DebugTrace() in either case this outermost DebugTrace() aborts
>> the inner H_Hat() before the inner DebugTrace() returns a value to it.
>>
> But the when H_Hat is called directly, the outermost H_Hat terminates normally?
> Or is it aborted?
> 

The outermost H_Hat() terminates normally because the inner one was 
aborted.

// 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
}




-- 
Copyright 2020 Pete Olcott

[toc] | [prev] | [next] | [standalone]


#24281 — Re: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]

FromMalcolm McLean <malcolm.arthur.mclean@gmail.com>
Date2020-10-23 17:24 -0700
SubjectRe: The key aspects of x86utm are now finally complete [ HP proof refutation has been provided ]
Message-ID<eeac643b-5dd7-473e-9fe1-da1dc78eff9bn@googlegroups.com>
In reply to#24277
On Saturday, 24 October 2020 at 01:14:01 UTC+1, olcott wrote:
> On 10/23/2020 6:58 PM, Malcolm McLean wrote: 
> > 
> > But the when H_Hat is called directly, the outermost H_Hat terminates normally? 
> > Or is it aborted? 
> >
> The outermost H_Hat() terminates normally because the inner one was 
> aborted. 
>
OK, that's crucial. If H_Hat terminates normally when invoked directly, then
H() has to return "Not aborted". But that's impossible. There's an infinite
recursion of DebugTraces.
So you've got a choice. You can keep H_Hat as a Turing machine, and say
Linz hasn;t been refuted. Or you can make a tiny change to H_Hat so that
it is no longer a Turing machine.  Then H() and H_Hat() will give consistent
results. 
>
> // 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 
>
So what is this doing if H_Hat hasn't aborted?
>
> else 
> { 
> MOV_EAX_1 // M(N) has halted 
> HERE: goto HERE; 
> } 
> HALT
> } 
> 

[toc] | [prev] | [next] | [standalone]


Page 15 of 25 — ← Prev page 1 … 13 14 [15] 16 17 … 25  Next page →

Back to top | Article view | comp.theory


csiph-web