Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.sys.raspberry-pi > #11730 > unrolled thread
| Started by | "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> |
|---|---|
| First post | 2016-06-13 19:32 +0100 |
| Last post | 2016-07-05 14:28 +0000 |
| Articles | 20 on this page of 788 — 65 participants |
Back to article view | Back to comp.sys.raspberry-pi
Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-13 19:32 +0100
Re: Is it a lost cause? Melzzzzz <mel@zzzzz.com> - 2016-06-13 21:02 +0200
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-13 21:25 +0000
Re: Is it a lost cause? rickman <gnuarm@gmail.com> - 2016-06-13 17:43 -0400
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-06-13 23:05 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:52 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:52 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:55 +0100
Re: Is it a lost cause? rickman <gnuarm@gmail.com> - 2016-06-14 12:53 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 18:22 +0100
Re: Is it a lost cause? rickman <gnuarm@gmail.com> - 2016-06-14 13:27 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 18:41 +0100
Re: Is it a lost cause? rickman <gnuarm@gmail.com> - 2016-06-14 15:05 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-20 14:09 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-13 23:07 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-13 23:02 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:56 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 08:13 +0000
Re: Is it a lost cause? Darren Salt <newsspam@moreofthespa.m.invalid> - 2016-06-17 03:39 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-17 08:46 +0200
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-17 10:51 +0200
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-13 20:14 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-14 10:54 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 11:57 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 13:02 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 14:45 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 15:32 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 15:22 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 19:56 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-14 15:30 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 19:59 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-14 23:42 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 07:48 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-15 11:22 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 11:28 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 10:39 +0000
Re: Is it a lost cause? Dr J R Stockton <reply1600@merlyn.demon.co.uk.invalid> - 2016-06-18 13:56 +0100
Re: Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-06-14 09:48 -0500
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-14 19:08 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 00:18 +0000
Re: Is it a lost cause? Anonymous <no_email@invalid.invalid> - 2016-06-15 01:57 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 11:05 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 07:53 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 10:53 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 11:24 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 13:03 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 12:53 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-15 13:10 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 12:28 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-15 15:37 +0100
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-15 20:19 +0300
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-15 17:52 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-15 21:08 +0300
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-16 12:30 +0000
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-16 12:46 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-17 12:53 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-17 16:09 +0300
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-16 22:58 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 21:03 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 20:12 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 21:24 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-16 03:47 +0100
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-02 23:55 -0400
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-03 11:03 +0300
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-03 10:20 -0400
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 12:43 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-15 08:27 -0400
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-02 04:38 -0400
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-02 14:00 -0400
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-02 08:13 -0700
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 12:09 -0400
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-02 12:36 -0700
Re: Is it a lost cause? Anonymous <no_email@invalid.invalid> - 2016-06-15 01:32 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 07:49 +0000
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-01 22:17 -0400
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 09:10 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-02 12:26 -0400
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-02 21:35 +0300
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-02 20:45 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-02 22:14 +0100
Re: Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-02 21:42 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 19:12 -0400
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 22:41 -0400
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 07:11 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 11:33 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 12:45 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 12:36 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 11:54 -0400
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-03 13:33 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 15:20 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 15:38 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 12:03 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 17:18 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 15:17 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 18:28 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-05 03:14 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 06:17 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 14:53 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-05 09:55 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 15:15 +0100
Re: Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-05 09:42 -0500
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-05 15:51 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 14:45 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 14:54 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-04 12:06 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 19:10 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-04 15:33 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 20:16 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 22:12 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 21:20 +0100
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-04 17:15 -0400
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-04 12:42 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 14:26 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-04 17:33 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 17:35 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-04 18:20 +0100
Re: Is it a lost cause? "Osmium" <r124c4u102@comcast.net> - 2016-07-04 09:01 -0500
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 14:55 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 15:11 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 16:01 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 17:32 +0200
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-05 19:47 -0400
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-07-05 17:11 -0700
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-05 21:08 -0400
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-06 14:44 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-07 12:52 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-05 18:19 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-04 13:01 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-03 11:30 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-03 17:31 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 11:54 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 17:30 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 17:57 +0000
Re: Is it a lost cause? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-07-03 14:51 -0400
Re: software origami, was Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-03 23:18 +0000
Re: software origami, was Is it a lost cause? andrew@cucumber.demon.co.uk (Andrew Gabriel) - 2016-07-04 08:24 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 17:20 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 16:15 -0400
Re: ancient history, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-03 22:55 +0000
Re: ancient history, Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 06:35 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 11:54 -0400
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-03 11:22 -0400
Re: Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-07-03 12:33 -0500
Re: Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-03 22:57 +0000
Re: Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-07-04 15:47 -0500
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-04 17:24 -0400
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 22:31 -0400
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-04 13:10 -0400
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-05 01:47 -0400
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 21:56 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 00:44 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-03 00:55 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 11:21 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-03 11:39 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 12:21 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-03 13:06 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-03 13:53 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-03 13:02 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 01:16 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 22:35 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-02 23:23 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-03 00:07 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-03 11:20 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-03 13:37 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-03 22:41 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-04 13:22 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-04 10:59 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-04 14:49 -0400
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-04 15:33 -0400
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-04 12:06 -0400
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-04 10:00 -0700
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-05 01:42 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 08:52 +0100
Re: Is it a lost cause? sidd@situ.com (sidd) - 2016-07-05 22:59 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-04 06:44 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-04 09:45 -0400
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-03 07:11 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-02 19:12 -0400
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-03 11:14 +0300
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 12:04 +0100
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-03 07:49 -0700
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-03 11:26 -0400
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 21:53 -0400
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-07-04 17:33 -0400
Re: self-modifying code, was Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 19:05 +0100
Re: self-modifying code, was Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-04 21:05 +0000
Re: self-modifying code, was Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 21:12 +0000
Re: self-modifying code, was Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 08:30 +0100
Re: self-modifying code, was Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-05 12:03 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 06:43 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 18:39 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 18:40 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 18:42 +0000
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 19:53 +0100
Re: self-modifying code, Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-04 15:20 -0400
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 20:50 +0000
Re: self-modifying code, Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-04 16:28 -0500
Re: self-modifying code, Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-05 16:37 +0100
Re: self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-04 21:03 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 21:08 +0000
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 06:13 +0100
Re: self-modifying code, Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-05 06:36 -0400
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 12:37 +0100
Re: self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 15:12 +0100
Re: self-modifying code, Is it a lost cause? Raymond Wiker <rwiker@gmail.com> - 2016-07-05 20:09 +0200
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 19:52 +0100
Re: self-modifying code, Is it a lost cause? Raymond Wiker <rwiker@gmail.com> - 2016-07-05 21:11 +0200
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 20:30 +0100
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-06 00:51 +0000
Re: self-modifying code, Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 20:09 +0100
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 20:32 +0100
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-06 00:44 +0000
Re: tiny old computers, was self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-05 21:08 +0000
Re: tiny old computers, was self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: tiny old computers, was self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-06 15:01 +0000
Re: tiny old computers, was self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-07 12:52 +0000
Re: self-modifying code, Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-05 20:49 -0400
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-06 10:45 +0100
Re: self-modifying code, Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-06 12:05 +0200
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-06 11:41 +0100
Re: self-modifying code, Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-06 08:59 -0400
Re: self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: self-modifying code, Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 16:00 +0200
Re: self-modifying code, Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-05 20:46 -0400
Re: self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 19:56 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 20:52 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 21:25 +0000
Re: stacks, was self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-04 21:12 +0000
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 06:10 +0100
Re: self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: self-modifying code, Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-05 09:35 -0500
Re: self-modifying code, Is it a lost cause? Robert Riches <spamtrap42@jacob21819.net> - 2016-07-05 16:33 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-05 18:16 +0000
Re: self-modifying code, Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: self-modifying code, Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 15:05 +0100
Re: self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-05 21:12 +0000
Re: self-modifying code, Is it a lost cause? cb@elaine.df.lth.se (Christian Brunschen) - 2016-07-05 21:49 +0000
Re: self-modifying code, Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-07-06 06:12 -0500
Re: self-modifying code, Is it a lost cause? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-07-05 08:51 -0600
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 16:05 +0100
Re: self-modifying code, Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-04 23:04 +0300
Re: self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-04 20:35 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 20:54 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-04 21:12 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 20:49 +0000
Re: self-modifying code, Is it a lost cause? mm0fmf <none@invalid.com> - 2016-07-04 21:54 +0100
Re: self-modifying code, Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-05 14:16 +0300
Re: self-modifying code, Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-05 09:40 -0500
Re: self-modifying code, Is it a lost cause? mm0fmf <none@invalid.com> - 2016-07-05 18:51 +0100
Re: self-modifying code, Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-07-05 21:08 +0300
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-04 17:21 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 17:28 +0100
Re: self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-04 16:38 +0000
Re: self-modifying code, Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 17:53 +0100
Re: self-modifying code, Is it a lost cause? Joe Pfeiffer <pfeiffer@cs.nmsu.edu> - 2016-07-04 14:52 -0600
Re: self-modifying code, Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-04 17:22 -0400
Re: self-modifying code, was Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-04 16:35 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-04 12:41 +0000
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-13 21:50 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:00 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-13 23:03 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-13 23:37 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-13 20:43 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-14 11:05 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 12:07 +0100
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-06-14 10:20 -0700
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-14 19:16 -0400
Re: Is it a lost cause? Andy Leighton <andyl@azaal.plus.com> - 2016-06-15 08:01 -0500
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 13:06 +0000
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-06-15 14:26 +0100
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-02 03:24 -0400
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-07-02 08:43 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 09:11 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 10:38 +0100
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-02 07:56 -0700
Re: Is it a lost cause? "Osmium" <r124c4u102@comcast.net> - 2016-07-02 10:30 -0500
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-07-02 16:50 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-02 17:21 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 16:58 +0000
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-02 11:52 -0700
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 10:38 +0100
Re: Is it a lost cause? Andy Leighton <andyl@azaal.plus.com> - 2016-07-02 06:23 -0500
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 13:02 +0100
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 06:09 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:01 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-14 13:09 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 15:29 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-14 20:30 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 08:57 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-15 23:14 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-16 08:36 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btopenworld.com> - 2016-06-16 12:46 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-16 13:25 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-16 14:22 +0100
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-02 22:33 -0400
Re: Is it a lost cause? Mike Tomlinson <mike@jasper.org.uk> - 2016-06-14 23:24 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 11:02 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 12:02 +0100
Re: Is it a lost cause? rickman <gnuarm@gmail.com> - 2016-06-15 09:38 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:35 +0100
Re: Is it a lost cause? Rob Morley <nospam@ntlworld.com> - 2016-06-15 17:36 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 21:02 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:32 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 17:00 +0100
Re: Is it a lost cause? mm0fmf <none@invalid.com> - 2016-06-18 18:14 +0100
Re: Is it a lost cause? "Osmium" <r124c4u102@comcast.net> - 2016-06-18 12:25 -0500
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-13 20:11 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:04 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-14 09:44 +0100
Re: Is it a lost cause? Mike Tomlinson <mike@jasper.org.uk> - 2016-06-14 23:26 +0100
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-14 20:43 -0500
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:48 +0000
Re: Is it a lost cause? Darren Salt <newsspam@moreofthespa.m.invalid> - 2016-06-17 03:50 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 10:08 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:42 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:50 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:52 +0100
Re: Is it a lost cause? Luke A. Guest <laguest@archeia.com> - 2016-07-01 20:28 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-01 20:21 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-01 23:10 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-01 22:35 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 10:35 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 09:53 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 11:24 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 11:21 +0000
Re: Is it a lost cause? mm0fmf <none@invalid.com> - 2016-07-02 12:39 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 13:01 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 13:51 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-02 12:26 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 17:32 +0100
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-07-02 19:51 -0700
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-01 18:39 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 10:36 +0100
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-02 18:56 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 19:14 -0400
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-07-03 15:28 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 17:23 +0100
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-07-03 17:35 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-03 19:48 +0100
Re: Is it a lost cause? Lew Pitcher <lew.pitcher@digitalfreehold.ca> - 2016-07-03 15:01 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-03 20:25 +0100
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-03 13:17 -0700
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-07-06 01:24 +1000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-05 16:29 +0100
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 12:09 -0400
Re: Is it a lost cause? Rob Morley <nospam@ntlworld.com> - 2016-07-05 17:38 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 18:23 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-05 18:30 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-05 18:29 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 23:07 +0200
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-06 12:45 +0000
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-06 09:05 -0400
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-06 13:52 +0000
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-06 07:37 -0700
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-06 08:51 -0700
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-06 15:09 -0400
Re: Is it a lost cause? Michael J. Mahon <mjmahon@aol.com> - 2016-07-07 00:26 -0500
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-07 13:12 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-04 12:41 +0000
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-07-04 12:47 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-02 12:59 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-02 17:43 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-02 18:40 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-02 12:26 -0400
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-02 12:59 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 09:14 -0400
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-02 12:26 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-02 13:00 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-02 13:46 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-02 14:59 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-02 14:08 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-02 12:27 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-02 17:34 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-02 16:57 +0000
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 06:23 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 12:06 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-03 13:33 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 15:17 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 15:42 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-04 12:41 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-04 14:17 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 15:10 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 17:18 +0200
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 17:28 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 18:53 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-06 21:34 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-07 12:52 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-07 14:45 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-07 16:27 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-07 11:53 -0400
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-07 17:33 +0200
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-07 19:30 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-08 12:18 +0000
Re: Is it a lost cause? pechter@t61.(none) (William Pechter) - 2016-07-07 01:38 +0000
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-07 13:19 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-07 14:22 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-04 12:42 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-04 22:30 +0200
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-05 13:32 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 15:25 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-06 13:11 +0000
Re: Is it a lost cause? pechter@t61.(none) (William Pechter) - 2016-07-07 01:51 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-07 07:47 +0000
Re: Is it a lost cause? Anonymous <no_email@invalid.invalid> - 2016-07-07 23:41 +0000
Re: Is it a lost cause? pechter@t61.(none) (William Pechter) - 2016-07-09 00:46 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-09 12:51 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-09 13:05 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-09 14:12 +0100
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-09 14:21 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-09 19:35 +0100
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-09 18:55 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-07-09 10:40 -0400
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-09 09:02 -0700
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-09 15:28 +0000
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-09 14:13 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-07-09 15:25 +0100
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-09 16:39 +0100
Re: Is it a lost cause? Richard Ashbery <basura@invalid.addr.uk> - 2016-07-09 16:56 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-09 16:30 +0000
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-09 18:43 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-09 21:52 +0000
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-07-09 18:25 +0000
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-09 18:53 +0000
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-07-09 20:55 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-10 12:06 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-07-10 14:05 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-11 11:32 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-11 11:29 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-11 16:57 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-11 16:01 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-11 17:27 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-11 16:46 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-11 18:00 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-11 18:39 +0000
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-11 16:44 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-11 17:59 +0100
Re: Is it a lost cause? Robert Riches <spamtrap42@jacob21819.net> - 2016-07-12 01:47 +0000
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-07-12 20:48 +0200
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-13 06:34 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-13 13:34 +0000
Re: Is it a lost cause? Gordon Henderson <gordon+usenet@drogon.net> - 2016-07-13 15:46 +0000
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-07 13:23 +0000
Re: Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-05 09:49 -0500
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 16:04 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 17:20 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 16:43 +0200
Re: Is it a lost cause? cb@elaine.df.lth.se (Christian Brunschen) - 2016-07-05 19:30 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-05 20:32 -0400
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 17:19 +0000
Re: Is it a lost cause? pechter@t61.(none) (William Pechter) - 2016-07-07 01:48 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-07 12:52 +0000
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-07 15:30 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-07 17:36 +0200
Re: Is it a lost cause? pechter@t61.(none) (William Pechter) - 2016-07-08 20:43 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-09 14:18 +0000
Re: Is it a lost cause? antispam@math.uni.wroc.pl - 2016-07-06 00:28 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-03 17:32 +0200
Re: Is it a lost cause? Dr J R Stockton <reply1600@merlyn.demon.co.uk.invalid> - 2016-07-02 19:20 +0100
Re: Is it a lost cause? Rambo <Rambo@thisaintreal.org> - 2016-06-13 20:07 +0100
Re: Is it a lost cause? Melzzzzz <mel@zzzzz.com> - 2016-06-13 21:42 +0200
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:43 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 08:12 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:17 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 08:31 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:44 +0100
Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-13 21:25 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:44 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-13 20:29 +0000
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-13 21:48 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-14 08:11 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:49 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 08:14 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:23 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 08:33 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 09:46 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 10:22 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 11:36 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 12:01 +0100
OT was Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-14 12:09 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-14 11:59 +0100
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-14 12:30 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 18:21 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 19:51 +0100
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-06-14 15:24 -0700
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-06-14 17:07 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 17:14 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-14 16:45 +0200
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-14 20:34 -0400
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-15 11:44 +0200
Re: Is it a lost cause? Rob Morley <nospam@ntlworld.com> - 2016-06-15 17:21 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-15 23:15 -0400
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-16 13:42 +0200
Symbolics [Re: Is it a lost cause?] colonel_hack@yahoo.com - 2016-06-15 17:08 -0700
Re: Is it a lost cause? David Wade <dave.g4ugm@gmail.com> - 2016-06-15 10:05 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 09:10 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 10:29 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 09:41 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 10:42 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 11:29 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:47 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-14 06:24 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 11:37 +0100
Re: Is it a lost cause? Rob Morley <nospam@ntlworld.com> - 2016-06-14 13:42 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 13:53 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 15:20 +0100
Re: Is it a lost cause? Brian Reay <no.sp@m.com> - 2016-06-14 08:35 -0700
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-14 11:45 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 15:18 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-14 15:57 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:03 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 16:10 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:36 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:40 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 20:02 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 21:13 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 20:59 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 22:19 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-14 21:58 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 23:15 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 23:23 +0100
Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-15 10:01 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 10:40 +0100
Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-15 12:19 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:37 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-15 11:39 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:10 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 16:19 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:39 +0000
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-06-14 13:53 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-14 18:17 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-14 21:50 +0300
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-15 01:59 +1000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 17:06 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 19:50 +0100
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-15 19:44 +1000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 10:55 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 11:49 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 11:31 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-15 08:27 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:29 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-15 18:20 +0200
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:27 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 17:18 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 20:58 +0100
Re: Is it a lost cause? AndyW <Andy@nojunqmail.com> - 2016-06-16 07:38 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-16 08:59 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-16 11:30 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-16 12:30 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-16 13:34 +0100
Re: Is it a lost cause? Andy Leighton <andyl@azaal.plus.com> - 2016-06-16 07:49 -0500
Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-17 12:26 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-17 12:53 +0000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-17 13:06 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-17 14:10 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-17 20:11 +0100
Re: Is it a lost cause? Steve Hall <sweet_stevie@invalid.invalid> - 2016-06-17 19:42 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 17:04 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-17 22:54 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 10:48 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 12:07 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 11:16 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 12:40 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-18 13:00 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-18 11:49 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 17:10 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-19 13:31 +0000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-18 12:59 +0000
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-18 16:05 -0500
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-06-18 19:04 -0700
Re: Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-06-16 09:37 -0700
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-16 14:42 +0100
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-06-14 13:55 -0400
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-15 20:12 +1000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 11:18 +0100
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-16 01:47 +1000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:53 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 22:37 +0100
Re: Is it a lost cause? "Kerr Mudd-John" <admin@127.0.0.1> - 2016-06-16 09:49 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-15 13:05 +0000
Re: Is it a lost cause? David Wade <dave.g4ugm@gmail.com> - 2016-06-15 10:23 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-15 13:05 +0000
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-16 01:55 +1000
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-16 12:30 +0000
Re: Is it a lost cause? Gordon Levi <gordon@address.invalid> - 2016-06-18 02:03 +1000
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-17 16:24 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-17 18:53 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 17:04 -0400
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-06-17 20:05 -0700
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-17 12:27 -0500
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 17:04 -0400
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-17 16:29 -0500
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-17 22:35 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 19:54 -0400
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-18 10:15 +0200
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-18 10:32 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 12:05 +0100
Re: Is it a lost cause? Gene Wirchenko <genew@telus.net> - 2016-06-18 04:52 -0700
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 12:59 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-18 17:32 +0100
Re: Is it a lost cause? cb@elaine.df.lth.se (Christian Brunschen) - 2016-06-18 17:36 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-18 09:08 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 12:47 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 14:26 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 13:58 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-18 11:49 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 18:52 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-18 17:53 +0200
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-18 15:37 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-18 16:45 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 09:53 +0000
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-06-18 11:02 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 11:13 +0100
Re: Is it a lost cause? Coos Haak <chforth@hccnet.nl> - 2016-06-18 15:19 +0200
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 14:35 +0100
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-18 16:50 +0200
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 16:58 +0100
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-18 19:09 +0200
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-18 13:11 +0200
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-18 12:59 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-18 17:13 +0300
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 14:40 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 16:56 +0100
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-18 21:58 +0300
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 10:49 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 12:03 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-18 11:17 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-18 12:25 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-18 17:04 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 18:31 +0000
Re: Is it a lost cause? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-06-19 18:31 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-19 21:49 +0300
Re: Is it a lost cause? AndyW <Andy@nojunqmail.com> - 2016-06-20 07:41 +0100
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 05:49 -0400
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-19 19:54 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-19 19:55 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-19 15:24 -0400
Re: Is it a lost cause? Andy Leighton <andyl@azaal.plus.com> - 2016-06-19 14:13 -0500
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-19 22:12 +0000
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-19 19:24 -0400
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-20 00:27 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-20 11:25 +0000
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-20 12:10 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-20 17:24 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-20 18:29 +0100
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-20 17:57 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-20 19:18 +0100
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-20 21:18 +0300
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-20 18:38 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-20 20:57 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-20 18:25 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-20 20:17 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-20 19:41 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-20 20:52 +0100
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-20 23:02 +0300
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 06:01 -0400
Re: Is it a lost cause? Charlie <cdknospam@msn.com> - 2016-07-03 13:50 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 20:11 +0100
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-03 23:05 +0000
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-04 07:05 +0100
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-07-05 12:56 +0200
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 12:54 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 13:14 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-07-05 16:19 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-05 16:51 +0100
Re: Is it a lost cause? Charlie <cdknospam@msn.com> - 2016-07-04 01:12 -0400
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-20 21:18 +0000
Re: Is it a lost cause? Dennis Lee Bieber <wlfraed@ix.netcom.com> - 2016-06-20 19:04 -0400
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-21 06:16 +0000
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-06-20 20:01 +0000
Re: Is it a lost cause? Rob Morley <nospam@ntlworld.com> - 2016-06-20 21:29 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-20 13:37 +0100
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-20 00:29 -0400
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-20 06:25 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-20 06:57 +0000
Re: Is it a lost cause? Tauno Voipio <tauno.voipio@notused.fi.invalid> - 2016-06-20 10:09 +0300
Re: Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-06-20 08:31 -0500
Re: Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-06-20 13:50 -0500
Re: Is it a lost cause? jeffj@panix.com (Jeff Jonas) - 2016-07-03 05:43 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-07-03 12:07 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-07-03 13:33 +0000
Re: Is it a lost cause? "A. Dumas" <alexandre@dumas.fr.invalid> - 2016-06-18 10:47 +0200
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-18 10:38 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-18 18:52 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-19 10:55 +0100
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-18 15:58 -0500
Re: Is it a lost cause? JimP <solosam90@gmail.com> - 2016-06-18 15:37 -0500
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 21:07 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-17 22:27 +0000
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-18 10:06 +0200
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 12:31 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-18 11:49 -0400
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-18 18:17 +0000
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-18 18:47 -0400
Re: Is it a lost cause? Andreas Eder <a_eder_muc@web.de> - 2016-06-19 12:13 +0200
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-19 08:10 -0400
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-19 10:59 +0000
Re: Is it a lost cause? Andrew Swallow <am.swallow@btinternet.com> - 2016-06-19 18:13 +0100
Re: Is it a lost cause? Robert Riches <spamtrap42@jacob21819.net> - 2016-06-21 03:09 +0000
Re: Is it a lost cause? David Wade <dave.g4ugm@gmail.com> - 2016-06-17 19:59 +0100
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 17:04 -0400
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-17 17:40 +0000
Re: Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-06-17 17:04 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-17 22:25 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-06-18 10:56 -0400
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-18 19:00 -0400
Re: Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-06-18 19:33 -0400
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-19 10:46 +0100
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-19 10:51 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-19 12:30 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-19 13:03 +0100
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-19 16:32 +0000
Re: Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-06-19 17:17 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-19 18:19 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-20 07:53 +0100
Re: Is it a lost cause? Folderol <general@musically.me.uk> - 2016-06-19 18:44 +0100
Re: Is it a lost cause? mm0fmf <none@invalid.com> - 2016-06-19 21:08 +0100
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-06-20 11:16 +0000
Re: Is it a lost cause? David Taylor <david-taylor@blueyonder.co.uk.invalid> - 2016-06-20 15:26 +0100
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-20 16:44 +0100
Re: Is it a lost cause? alister <alister.ware@ntlworld.com> - 2016-06-20 20:07 +0000
Re: Is it a lost cause? Charlie Gibbs <cgibbs@kltpzyxm.invalid> - 2016-06-19 18:32 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-19 19:35 +0100
Re: Is it a lost cause? Rob <nomail@example.com> - 2016-06-19 19:33 +0000
Re: Is it a lost cause? Michael Black <et472@ncf.ca> - 2016-06-14 12:34 -0400
Re: Is it a lost cause? Morten Reistad <first@last.name.invalid> - 2016-06-14 22:12 +0200
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-14 21:33 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 07:23 +0100
Re: Is it a lost cause? jmfbahciv <See.above@aol.com> - 2016-06-15 13:05 +0000
Re: Is it a lost cause? The Natural Philosopher <tnp@invalid.invalid> - 2016-06-15 14:15 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:50 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:07 +0100
Re: Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-06-14 15:45 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 16:51 +0100
Re: Is it a lost cause? Ahem A Rivet's Shot <steveo@eircom.net> - 2016-06-15 07:58 +0100
Re: Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-06-15 08:41 +0000
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-14 08:46 +0100
Re: Is it a lost cause? "J. Clarke" <j.clarke.873638@gmail.com> - 2016-06-14 06:31 -0400
Re: Is it a lost cause? Steve Drain <steve@kappa.me.uk> - 2016-06-15 12:08 +0100
Re: Is it a lost cause? "gareth G4SDW GQRP #3339" <no.spam@thank.you.invalid> - 2016-06-15 16:36 +0100
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-04 21:31 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-05 14:16 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-05 15:42 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-05 17:54 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-05 18:33 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-06 01:14 +0000
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-06 07:19 +0000
Re: self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-04 21:42 +0000
Re: stacks, was self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-04 21:47 +0000
Re: self-modifying code, Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-04 17:55 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-05 02:46 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? David Wade <dave.g4ugm@gmail.com> - 2016-07-05 08:58 +0100
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-05 07:54 -0700
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-05 15:43 -0700
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 11:57 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-05 16:06 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 14:05 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Lawrence Statton NK1G <lawrence@senguio.mx> - 2016-07-05 13:24 -0500
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 14:29 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 19:59 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-05 18:31 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 15:32 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-05 20:05 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Dan Espen <despen@verizon.net> - 2016-07-05 22:36 -0400
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-06 07:14 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Rob <nomail@example.com> - 2016-07-06 07:59 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 19:59 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-05 20:05 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? scott@slp53.sl.home (Scott Lurndal) - 2016-07-05 19:57 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-05 21:16 +0000
Re: S/360 stacks, was self-modifying code, Is it a lost cause? Anne & Lynn Wheeler <lynn@garlic.com> - 2016-07-05 15:38 -0700
Re: self-modifying code, Is it a lost cause? Dennis <dennis@none.none> - 2016-07-04 19:55 -0500
Re: self-modifying code, Is it a lost cause? "Charles Richmond" <numerist@aquaporin4.com> - 2016-07-05 12:46 -0500
Re: 360 architecture, was self-modifying code, Is it a lost cause? John Levine <johnl@iecc.com> - 2016-07-05 21:11 +0000
Re: self-modifying code, Is it a lost cause? Peter Flass <peter_flass@yahoo.com> - 2016-07-05 20:32 -0400
Re: self-modifying code, Is it a lost cause? Bob Eager <news0006@eager.cx> - 2016-07-06 07:20 +0000
Re: self-modifying code, Is it a lost cause? Martin Gregorie <martin@address-in-sig.invalid> - 2016-07-05 14:28 +0000
Page 39 of 40 — ← Prev page 1 … 37 38 [39] 40 Next page →
| From | Peter Flass <peter_flass@yahoo.com> |
|---|---|
| Date | 2016-07-04 17:55 -0400 |
| Subject | Re: self-modifying code, Is it a lost cause? |
| Message-ID | <1107158795.489361340.954697.peter_flass-yahoo.com@news.eternal-september.org> |
| In reply to | #11730 |
Martin Gregorie <martin@address-in-sig.invalid> wrote: > On Mon, 04 Jul 2016 19:53:46 +0100, The Natural Philosopher wrote: > >> Are you telling me a PDP 8 didnt have a stack pointer? >> > A lot of processors didn't have stack pointers until quite late, e.g. all > the ICL 1900 mainframes. I think the IBM S/360 and S/370 may not have had > them either. > Or any stack instructions. The functions of a stack were performed on OS/360 by a chain of register saveareas maintained mostly by software. I believe VM handled things differently, but I'm not sure exactly how. -- Pete
[toc] | [prev] | [next] | [standalone]
| From | John Levine <johnl@iecc.com> |
|---|---|
| Date | 2016-07-05 02:46 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlf722$1gom$1@miucha.iecc.com> |
| In reply to | #12396 |
>> Or any stack instructions. The functions of a stack were performed on >> OS/360 by a chain of register saveareas maintained mostly by software. I >> believe VM handled things differently, but I'm not sure exactly how. VM was (and is) a virtual machine system, so its programming environment is what the hardware gives you, plus a bunch of stuff implemented via trapping reserved instructions that handle shared memory, the virtual card chutes from one machine's simulated punch to another's reader, and the like. For interactive use the usual environment was CMS, a single user monitor that provded a software environment similar enough to OS that it could run the same compilers.
[toc] | [prev] | [next] | [standalone]
| From | David Wade <dave.g4ugm@gmail.com> |
|---|---|
| Date | 2016-07-05 08:58 +0100 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlfpb7$58u$1@news.albasani.net> |
| In reply to | #12423 |
On 05/07/2016 03:46, John Levine wrote: >>> Or any stack instructions. The functions of a stack were performed on >>> OS/360 by a chain of register saveareas maintained mostly by software. I >>> believe VM handled things differently, but I'm not sure exactly how. > > VM was (and is) a virtual machine system, so its programming > environment is what the hardware gives you, plus a bunch of stuff > implemented via trapping reserved instructions that handle shared > memory, the virtual card chutes from one machine's simulated punch to > another's reader, and the like. > > For interactive use the usual environment was CMS, a single user > monitor that provded a software environment similar enough to OS that > it could run the same compilers. > All the IBM Mainframe "VM" operating systems consist of at least two operating systems. CP which is often called VM, which is there to provide virtual Machines. Originally these were pretty basic Virtual Machines which looked exactly like a real S/370 to any program running in them. Internally CP has a large number of control blocks which are chained together to manage the real hardware, the virtual machines and virtual hardware, and how they are mapped. I am not aware of any stack. There is some use of OS type register save areas. traditionally, when used to provide an interactive computing environment, CP was used to provide each used with a Virtual 370. The user then loads the CMS Operating system into the VM. CMS is a single user operating system that provides a native CMS environment and DOS and OS emulated environments. Internally it uses OS style call/save/return mapping. I don't believe that modern Z hardware has a hardware stack. There are still no PUSH/POP type instructions. For languages that need a stack generally a stack area is allocated when a program is loaded and one of the 16 General Purpose Registers is then used as a stack pointer, but in general it has to be incremented/decremented by a second instruction... Dave G4UGM
[toc] | [prev] | [next] | [standalone]
| From | Anne & Lynn Wheeler <lynn@garlic.com> |
|---|---|
| Date | 2016-07-05 07:54 -0700 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <87bn2cp22s.fsf@garlic.com> |
| In reply to | #12472 |
David Wade <dave.g4ugm@gmail.com> writes: > All the IBM Mainframe "VM" operating systems consist of at least two > operating systems. > > CP which is often called VM, which is there to provide virtual > Machines. Originally these were pretty basic Virtual Machines which > looked exactly like a real S/370 to any program running in them. > > Internally CP has a large number of control blocks which are chained > together to manage the real hardware, the virtual machines and virtual > hardware, and how they are mapped. I am not aware of any stack. > > There is some use of OS type register save areas. > > traditionally, when used to provide an interactive computing > environment, CP was used to provide each used with a Virtual 370. > > The user then loads the CMS Operating system into the VM. CMS is a > single user operating system that provides a native CMS environment > and DOS and OS emulated environments. Internally it uses OS style > call/save/return mapping. > > I don't believe that modern Z hardware has a hardware stack. There are > still no PUSH/POP type instructions. For languages that need a stack > generally a stack area is allocated when a program is loaded and one > of the 16 General Purpose Registers is then used as a stack pointer, > but in general it has to be incremented/decremented by a second > instruction... original cp67 had a form of (software) stack ... 100 pre-allocated save areas. all calls/return were done by SVC call ... SVC interrupt handler would allocate/deallocate savearea for use by called routine. the svc call accounted for significant percentage of total CPU time spent in the kerenel. As undergraduate in the 60s, I made two changes, 1) svc call routine when it ran out of pre-allocated saveareas would extend the number of saveareas by calling the page allocation routine with special parameter ... that would look for first non-changed page for replacement (didn't require delay waiting for write-out replacing changed page) and 2) there were a whole bunch of routines that were simple call/return ... and I changed them to straight BALR/BR call/return and to use a dedicated save area in page0 (works in multiprocessor since each processor has its own dedicated page0). I also cut the instruction time in the SVC call/return by 2/3rds. I also made a whole lot of other pathlength optimizations ... in same cases improvement by factor of 100. Overall as undergraduate in the 60s, I reduced CP67 kernel CPU time by 3/4s. A lot of this was picked up and shipped in standard CP67 product. Part of presentation that I made at 60s SHARE user group meeting http://manana.garlic.com/~lynn/94.html#18 CP/67 & OS MFT14 as undergraduate I was hired by the univ. to be responsible for production operating systems. the above presentation includes references to changes I made of os/360. On 709 IBSYS tape-to-tape (with 1401 front-end doing tape<->unitrecord student fortran jobs ran under 1second elapsed time). Initial move to os/360 360/65 (360/67 running as 360/65), student fortran jobs ran over minute ... because of enormous disk i/o intensive operation. Adding HASP (spooling system), cut elapsed time/job to a little over half a minute. I started hand-crafted OS/360 system build/sysgen to carefully place/order system data on disk which got it down to a little under 13seconds. For CP67 I also redid a lot of the I/O, added ordered seek queuing and for page activity, chained multiple page transfers into single I/O channel program. I also implemented dynamic adaptive resource manager (frequently called "fair share" for default resource policy) http://manana.garlic.com/~lynn/subtopic.html#fairshare I also did global LRU, clock-like page replacement algorithm ... this was at a time when the academic papers were all about local LRU. some past posts http://manana.garlic.com/~lynn/subtopic.html#clock I've mentioned that when Jim Gray left research for Tandem, he palmed off bunch of stuff on me: http://manana.garlic.com/~lynn/2016d.html#104 Is it a lost cause? At Dec81, ACM SIGOPS, Jim asked me if I could help one of his co-workers at Tandem get his Stanford PHD ... which was on global LRU page replacement. The "local LRU" forces (from the late 60s) were strongly lobbying Stanford to not award any PHD that had to do with local LRU. Jim knew I had a lot of performance data comparing local LRU CP67 and global LRU CP67 implementations (showing global LRU much better) ... much of the other claims on the subject were just opinion and hand waving. Past post on the subject http://manana.garlic.com/~lynn/2006w.html#46 with this reply that I wrote http://manana.garlic.com/~lynn/2006w.html#email821019 aka it took me almost a year to get IBM management to send a replay. Conjecture is that IBM management thought it was a form of punishment because they blamed for online computer conferencing on the internal network (larger than the arpanet/internet from just about the beginning until sometime mid-80s). Folkore is that when the corporate management committee were told about online computer conferencing (and the internal network), 5of6 wanted to fire me. Some past posts http://manana.garlic.com/~lynn/subnetwork.html#cmc and http://manana.garlic.com/~lynn/subnetwork.html#internalnet -- virtualization experience starting Jan1968, online at home since Mar1970
[toc] | [prev] | [next] | [standalone]
| From | Anne & Lynn Wheeler <lynn@garlic.com> |
|---|---|
| Date | 2016-07-05 15:43 -0700 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <87r3b7so2j.fsf@garlic.com> |
| In reply to | #12506 |
Anne & Lynn Wheeler <lynn@garlic.com> writes: > At Dec81, ACM SIGOPS, Jim asked me if I could help one of his co-workers > at Tandem get his Stanford PHD ... which was on global LRU page > replacement. The "local LRU" forces (from the late 60s) were strongly > lobbying Stanford to not award any PHD that had to do with local LRU. > Jim knew I had a lot of performance data comparing local LRU CP67 and > global LRU CP67 implementations (showing global LRU much better) ... > much of the other claims on the subject were just opinion and > hand waving. Past post on the subject > http://manana.garlic.com/~lynn/2006w.html#46 > with this reply that I wrote > http://manana.garlic.com/~lynn/2006w.html#email821019 re: http://www.garlic.com/~lynn/ inverted sense: "lobbying Stanford to not award any PHD that had to do with local LRU." ... the "local LRU" forces (dating back to the 60s) were strongly lobbying Stanford to not award any PHD that wasn't "local LRU" ... in particularly not award any PHD for anything to do with "global LRU". trivia: the PHD advisor later becomes president of Stanford. -- virtualization experience starting Jan1968, online at home since Mar1970
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <despen@verizon.net> |
|---|---|
| Date | 2016-07-05 11:57 -0400 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlgldo$tkd$1@dont-email.me> |
| In reply to | #12472 |
David Wade <dave.g4ugm@gmail.com> writes: > I don't believe that modern Z hardware has a hardware stack. There are > still no PUSH/POP type instructions. For languages that need a stack > generally a stack area is allocated when a program is loaded and one > of the 16 General Purpose Registers is then used as a stack pointer, > but in general it has to be incremented/decremented by a second > instruction... The z systems use a "linkage stack". You push entries in the linkage stack with Branch and Stack, or Program Call. You pop entries with Program Return. Control register 0 controls state switching and control register 15 points at the current linkage stack. The linkage stack itself is in protected storage but it's not special hardware, just main memory. How that differs from other machines I'm not clear on. It always seemed very odd to me, that when you write C code, you're always told to always check the malloc() return code. Yet, calling a subroutine needs main storage and the language provides no way to check a return code for that. I'm not sure if it raises a signal. With a language that supports recursion, that could be an issue. I generally avoid recursion for that reason. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Rob <nomail@example.com> |
|---|---|
| Date | 2016-07-05 16:06 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <slrnnnnmno.754.nomail@xs9.xs4all.nl> |
| In reply to | #12520 |
Dan Espen <despen@verizon.net> wrote: > It always seemed very odd to me, that when you write C > code, you're always told to always check the malloc() return code. > Yet, calling a subroutine needs main storage and the language > provides no way to check a return code for that. > I'm not sure if it raises a signal. This is implementation (mostly OS) dependant. Usually there is a signal for stack overflow, but it often is the generic signal for invalid memory accessed (SIGSEGV in Unix/Linux).
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <despen@verizon.net> |
|---|---|
| Date | 2016-07-05 14:05 -0400 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlgstu$qv5$1@dont-email.me> |
| In reply to | #12521 |
Rob <nomail@example.com> writes: > Dan Espen <despen@verizon.net> wrote: >> It always seemed very odd to me, that when you write C >> code, you're always told to always check the malloc() return code. >> Yet, calling a subroutine needs main storage and the language >> provides no way to check a return code for that. >> I'm not sure if it raises a signal. > > This is implementation (mostly OS) dependant. Usually there is a > signal for stack overflow, but it often is the generic signal for > invalid memory accessed (SIGSEGV in Unix/Linux). Which leaves you no way to programmaticly detect the overflow. The end user could add memory to the job if he got an informative message. It's somewhat ironic, you put all that coding in for malloc failure and end up being unable to detect stack allocation failure. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Lawrence Statton NK1G <lawrence@senguio.mx> |
|---|---|
| Date | 2016-07-05 13:24 -0500 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <87d1ms0wp8.fsf@senguio.mx> |
| In reply to | #12536 |
Dan Espen <despen@verizon.net> writes: >> This is implementation (mostly OS) dependant. Usually there is a >> signal for stack overflow, but it often is the generic signal for >> invalid memory accessed (SIGSEGV in Unix/Linux). > > Which leaves you no way to programmaticly detect the overflow. > The end user could add memory to the job if he got an informative > message. While I've never done it, it should be a SMOP to trap the SEGV exception, and write a handler (using a private area of memory set aside for its own stack) to at least report the problem. That'd be some tricky 'battling with the compiler' to get the execution environment set up, but no more than a day of hair extraction. > It's somewhat ironic, you put all that coding in for malloc failure > and end up being unable to detect stack allocation failure. Hysterical Raisins, I think ... At some reference point in history, stack overflow just "never happened" and running out of arena happened all the time. A "stack heavy" algorithm like walking a balanced tree only uses O(log2(N)) levels of stack -- I can walk a billion element tree using 31 stack frames. Twenty years ago, I had cause to instrument a moderately complex system in C, with much recursive code, and the stack never grew to more than 1,100 bytes. On a modern Unix-like system, the stack is given by default 8 mibibytes.
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <despen@verizon.net> |
|---|---|
| Date | 2016-07-05 14:29 -0400 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlguad$qv5$3@dont-email.me> |
| In reply to | #12540 |
Lawrence Statton NK1G <lawrence@senguio.mx> writes: > Dan Espen <despen@verizon.net> writes: >>> This is implementation (mostly OS) dependant. Usually there is a >>> signal for stack overflow, but it often is the generic signal for >>> invalid memory accessed (SIGSEGV in Unix/Linux). >> >> Which leaves you no way to programmaticly detect the overflow. >> The end user could add memory to the job if he got an informative >> message. > > While I've never done it, it should be a SMOP to trap the SEGV > exception, and write a handler (using a private area of memory set aside > for its own stack) to at least report the problem. That'd be some > tricky 'battling with the compiler' to get the execution environment set > up, but no more than a day of hair extraction. Lots of things can cause a SEGV. You can't just trap SEGV and send a message to the user to increase memory space. >> It's somewhat ironic, you put all that coding in for malloc failure >> and end up being unable to detect stack allocation failure. > > Hysterical Raisins, I think ... At some reference point in history, > stack overflow just "never happened" and running out of arena happened > all the time. > > A "stack heavy" algorithm like walking a balanced tree only uses > O(log2(N)) levels of stack -- I can walk a billion element tree using 31 > stack frames. > > Twenty years ago, I had cause to instrument a moderately complex system > in C, with much recursive code, and the stack never grew to more than > 1,100 bytes. On a modern Unix-like system, the stack is given by > default 8 mibibytes. Coming up with nothing on mibibytes. I have: home> ulimit -a ... stack size (kbytes, -s) 8192 ... Admittedly hard to use up. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2016-07-05 19:59 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <hkUez.62169$w13.32183@fx22.iad> |
| In reply to | #12541 |
Dan Espen <despen@verizon.net> writes: >Lawrence Statton NK1G <lawrence@senguio.mx> writes: > >> Dan Espen <despen@verizon.net> writes: >>>> This is implementation (mostly OS) dependant. Usually there is a >>>> signal for stack overflow, but it often is the generic signal for >>>> invalid memory accessed (SIGSEGV in Unix/Linux). >>> >>> Which leaves you no way to programmaticly detect the overflow. >>> The end user could add memory to the job if he got an informative >>> message. >> >> While I've never done it, it should be a SMOP to trap the SEGV >> exception, and write a handler (using a private area of memory set aside >> for its own stack) to at least report the problem. That'd be some >> tricky 'battling with the compiler' to get the execution environment set >> up, but no more than a day of hair extraction. > >Lots of things can cause a SEGV. You can't just trap SEGV and send >a message to the user to increase memory space. siginfo.si_addr gives the VA of the address that wasn't present. It's simple to check if it is in certain bounds, and recover appropriately. BTDT. See also: http://www.in-ulm.de/~mascheck/bourne/segv.html
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0006@eager.cx> |
|---|---|
| Date | 2016-07-05 18:31 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <du2cnfF2lvcU2@mid.individual.net> |
| In reply to | #12536 |
On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: > Rob <nomail@example.com> writes: > >> Dan Espen <despen@verizon.net> wrote: >>> It always seemed very odd to me, that when you write C code, you're >>> always told to always check the malloc() return code. >>> Yet, calling a subroutine needs main storage and the language provides >>> no way to check a return code for that. >>> I'm not sure if it raises a signal. >> >> This is implementation (mostly OS) dependant. Usually there is a >> signal for stack overflow, but it often is the generic signal for >> invalid memory accessed (SIGSEGV in Unix/Linux). > > Which leaves you no way to programmaticly detect the overflow. > The end user could add memory to the job if he got an informative > message. > > It's somewhat ironic, you put all that coding in for malloc failure and > end up being unable to detect stack allocation failure. In practice, a program would have to be *very* badly coded to run out of stack. Most modern stack-based systems use a stack that runs down from the top of virtualy memory, and it's extended automatically if one reaches the end of it. Yes, 'infinite' recursion will use it all up, but we are usually talking a gigabyte or two even on a 32 bit system. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <despen@verizon.net> |
|---|---|
| Date | 2016-07-05 15:32 -0400 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlh20m$eau$1@dont-email.me> |
| In reply to | #12542 |
Bob Eager <news0006@eager.cx> writes: > On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: > >> Rob <nomail@example.com> writes: >> >>> Dan Espen <despen@verizon.net> wrote: >>>> It always seemed very odd to me, that when you write C code, you're >>>> always told to always check the malloc() return code. >>>> Yet, calling a subroutine needs main storage and the language provides >>>> no way to check a return code for that. >>>> I'm not sure if it raises a signal. >>> >>> This is implementation (mostly OS) dependant. Usually there is a >>> signal for stack overflow, but it often is the generic signal for >>> invalid memory accessed (SIGSEGV in Unix/Linux). >> >> Which leaves you no way to programmaticly detect the overflow. >> The end user could add memory to the job if he got an informative >> message. >> >> It's somewhat ironic, you put all that coding in for malloc failure and >> end up being unable to detect stack allocation failure. > > In practice, a program would have to be *very* badly coded to run out of > stack. Most modern stack-based systems use a stack that runs down from > the top of virtualy memory, and it's extended automatically if one > reaches the end of it. > > Yes, 'infinite' recursion will use it all up, but we are usually talking > a gigabyte or two even on a 32 bit system. On z/Series, the stack and heap come from the same pool. The limit is on total storage used, not one limit for heap, another for stack as found on unix type systems. So, you can use up all the storage with malloc, but eventually fail on a stack request. (At least in theory.) -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0006@eager.cx> |
|---|---|
| Date | 2016-07-05 20:05 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <du2i7gF2lvcU4@mid.individual.net> |
| In reply to | #12550 |
On Tue, 05 Jul 2016 15:32:37 -0400, Dan Espen wrote: > Bob Eager <news0006@eager.cx> writes: > >> On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: >> >>> Rob <nomail@example.com> writes: >>> >>>> Dan Espen <despen@verizon.net> wrote: >>>>> It always seemed very odd to me, that when you write C code, you're >>>>> always told to always check the malloc() return code. >>>>> Yet, calling a subroutine needs main storage and the language >>>>> provides no way to check a return code for that. >>>>> I'm not sure if it raises a signal. >>>> >>>> This is implementation (mostly OS) dependant. Usually there is a >>>> signal for stack overflow, but it often is the generic signal for >>>> invalid memory accessed (SIGSEGV in Unix/Linux). >>> >>> Which leaves you no way to programmaticly detect the overflow. >>> The end user could add memory to the job if he got an informative >>> message. >>> >>> It's somewhat ironic, you put all that coding in for malloc failure >>> and end up being unable to detect stack allocation failure. >> >> In practice, a program would have to be *very* badly coded to run out >> of stack. Most modern stack-based systems use a stack that runs down >> from the top of virtualy memory, and it's extended automatically if one >> reaches the end of it. >> >> Yes, 'infinite' recursion will use it all up, but we are usually >> talking a gigabyte or two even on a 32 bit system. > > On z/Series, the stack and heap come from the same pool. > The limit is on total storage used, not one limit for heap, another for > stack as found on unix type systems. > > So, you can use up all the storage with malloc, but eventually fail on a > stack request. > > (At least in theory.) The stack and heap come from the same pool on most systems. The stack grows down, the heap grows up. But if you run out, you run out. There are guard pages on the stack, so you can catch that situation if it ever happens. Frankly, with that much stack available, only a very poorly written program is going to hit the limit. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | Dan Espen <despen@verizon.net> |
|---|---|
| Date | 2016-07-05 22:36 -0400 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <nlhqr9$ql9$1@dont-email.me> |
| In reply to | #12554 |
Bob Eager <news0006@eager.cx> writes: > On Tue, 05 Jul 2016 15:32:37 -0400, Dan Espen wrote: > >> Bob Eager <news0006@eager.cx> writes: >> >>> On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: >>> >>>> Rob <nomail@example.com> writes: >>>> >>>>> Dan Espen <despen@verizon.net> wrote: >>>>>> It always seemed very odd to me, that when you write C code, you're >>>>>> always told to always check the malloc() return code. >>>>>> Yet, calling a subroutine needs main storage and the language >>>>>> provides no way to check a return code for that. >>>>>> I'm not sure if it raises a signal. >>>>> >>>>> This is implementation (mostly OS) dependant. Usually there is a >>>>> signal for stack overflow, but it often is the generic signal for >>>>> invalid memory accessed (SIGSEGV in Unix/Linux). >>>> >>>> Which leaves you no way to programmaticly detect the overflow. >>>> The end user could add memory to the job if he got an informative >>>> message. >>>> >>>> It's somewhat ironic, you put all that coding in for malloc failure >>>> and end up being unable to detect stack allocation failure. >>> >>> In practice, a program would have to be *very* badly coded to run out >>> of stack. Most modern stack-based systems use a stack that runs down >>> from the top of virtualy memory, and it's extended automatically if one >>> reaches the end of it. >>> >>> Yes, 'infinite' recursion will use it all up, but we are usually >>> talking a gigabyte or two even on a 32 bit system. >> >> On z/Series, the stack and heap come from the same pool. >> The limit is on total storage used, not one limit for heap, another for >> stack as found on unix type systems. >> >> So, you can use up all the storage with malloc, but eventually fail on a >> stack request. >> >> (At least in theory.) > > The stack and heap come from the same pool on most systems. The stack > grows down, the heap grows up. Yes, but Linux seems to have separate limits for the stack and heap as evidenced by ulimit output. -- Dan Espen
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0006@eager.cx> |
|---|---|
| Date | 2016-07-06 07:14 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <du3pduF2lvcU6@mid.individual.net> |
| In reply to | #12575 |
On Tue, 05 Jul 2016 22:36:24 -0400, Dan Espen wrote: > Bob Eager <news0006@eager.cx> writes: > >> On Tue, 05 Jul 2016 15:32:37 -0400, Dan Espen wrote: >> >>> Bob Eager <news0006@eager.cx> writes: >>> >>>> On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: >>>> >>>>> Rob <nomail@example.com> writes: >>>>> >>>>>> Dan Espen <despen@verizon.net> wrote: >>>>>>> It always seemed very odd to me, that when you write C code, >>>>>>> you're always told to always check the malloc() return code. >>>>>>> Yet, calling a subroutine needs main storage and the language >>>>>>> provides no way to check a return code for that. >>>>>>> I'm not sure if it raises a signal. >>>>>> >>>>>> This is implementation (mostly OS) dependant. Usually there is a >>>>>> signal for stack overflow, but it often is the generic signal for >>>>>> invalid memory accessed (SIGSEGV in Unix/Linux). >>>>> >>>>> Which leaves you no way to programmaticly detect the overflow. >>>>> The end user could add memory to the job if he got an informative >>>>> message. >>>>> >>>>> It's somewhat ironic, you put all that coding in for malloc failure >>>>> and end up being unable to detect stack allocation failure. >>>> >>>> In practice, a program would have to be *very* badly coded to run out >>>> of stack. Most modern stack-based systems use a stack that runs down >>>> from the top of virtualy memory, and it's extended automatically if >>>> one reaches the end of it. >>>> >>>> Yes, 'infinite' recursion will use it all up, but we are usually >>>> talking a gigabyte or two even on a 32 bit system. >>> >>> On z/Series, the stack and heap come from the same pool. >>> The limit is on total storage used, not one limit for heap, another >>> for stack as found on unix type systems. >>> >>> So, you can use up all the storage with malloc, but eventually fail on >>> a stack request. >>> >>> (At least in theory.) >> >> The stack and heap come from the same pool on most systems. The stack >> grows down, the heap grows up. > > Yes, but Linux seems to have separate limits for the stack and heap as > evidenced by ulimit output. And those limits are flexible and can be turned off. The stack limit is usually high enough that only poor programs will ever hit it. -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | Rob <nomail@example.com> |
|---|---|
| Date | 2016-07-06 07:59 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <slrnnnpei9.dja.nomail@xs9.xs4all.nl> |
| In reply to | #12575 |
Dan Espen <despen@verizon.net> wrote: >>> On z/Series, the stack and heap come from the same pool. >>> The limit is on total storage used, not one limit for heap, another for >>> stack as found on unix type systems. >>> >>> So, you can use up all the storage with malloc, but eventually fail on a >>> stack request. >>> >>> (At least in theory.) >> >> The stack and heap come from the same pool on most systems. The stack >> grows down, the heap grows up. > > Yes, but Linux seems to have separate limits for the stack and heap as > evidenced by ulimit output. It is still the same space. There is a single block of (virtual) memory in which the heap grows up and the stack grows down, but you can define for heap and stack separately how far they allowed to grow. Typically the stack is limited to 8MB and the heap is unlimited. (there still is a limitation based on memory available in the system and memory used by other processes)
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2016-07-05 19:59 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <ZkUez.62170$w13.5429@fx22.iad> |
| In reply to | #12542 |
Bob Eager <news0006@eager.cx> writes: > git://git.gnome.org/pan2) >X-Received-Body-CRC: 3815132622 >X-Received-Bytes: 2460 > >On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: > >> Rob <nomail@example.com> writes: >> >>> Dan Espen <despen@verizon.net> wrote: >>>> It always seemed very odd to me, that when you write C code, you're >>>> always told to always check the malloc() return code. >>>> Yet, calling a subroutine needs main storage and the language provides >>>> no way to check a return code for that. >>>> I'm not sure if it raises a signal. >>> >>> This is implementation (mostly OS) dependant. Usually there is a >>> signal for stack overflow, but it often is the generic signal for >>> invalid memory accessed (SIGSEGV in Unix/Linux). >> >> Which leaves you no way to programmaticly detect the overflow. >> The end user could add memory to the job if he got an informative >> message. >> >> It's somewhat ironic, you put all that coding in for malloc failure and >> end up being unable to detect stack allocation failure. > >In practice, a program would have to be *very* badly coded to run out of >stack. Most modern stack-based systems use a stack that runs down from >the top of virtualy memory, and it's extended automatically if one >reaches the end of it. With a 64-bit virtual address space, you're more likely to run out of backing space (swap) than the VA space itself.
[toc] | [prev] | [next] | [standalone]
| From | Bob Eager <news0006@eager.cx> |
|---|---|
| Date | 2016-07-05 20:05 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <du2i8jF2lvcU5@mid.individual.net> |
| In reply to | #12553 |
On Tue, 05 Jul 2016 19:59:53 +0000, Scott Lurndal wrote: > Bob Eager <news0006@eager.cx> writes: >> git://git.gnome.org/pan2) >>X-Received-Body-CRC: 3815132622 X-Received-Bytes: 2460 >> >>On Tue, 05 Jul 2016 14:05:48 -0400, Dan Espen wrote: >> >>> Rob <nomail@example.com> writes: >>> >>>> Dan Espen <despen@verizon.net> wrote: >>>>> It always seemed very odd to me, that when you write C code, you're >>>>> always told to always check the malloc() return code. >>>>> Yet, calling a subroutine needs main storage and the language >>>>> provides no way to check a return code for that. >>>>> I'm not sure if it raises a signal. >>>> >>>> This is implementation (mostly OS) dependant. Usually there is a >>>> signal for stack overflow, but it often is the generic signal for >>>> invalid memory accessed (SIGSEGV in Unix/Linux). >>> >>> Which leaves you no way to programmaticly detect the overflow. >>> The end user could add memory to the job if he got an informative >>> message. >>> >>> It's somewhat ironic, you put all that coding in for malloc failure >>> and end up being unable to detect stack allocation failure. >> >>In practice, a program would have to be *very* badly coded to run out of >>stack. Most modern stack-based systems use a stack that runs down from >>the top of virtualy memory, and it's extended automatically if one >>reaches the end of it. > > With a 64-bit virtual address space, you're more likely to run out of > backing space (swap) than the VA space itself. Indeed. I thought I'd said '32 bit' in there but I obviously forgot! -- Using UNIX since v6 (1975)... Use the BIG mirror service in the UK: http://www.mirrorservice.org
[toc] | [prev] | [next] | [standalone]
| From | scott@slp53.sl.home (Scott Lurndal) |
|---|---|
| Date | 2016-07-05 19:57 +0000 |
| Subject | Re: S/360 stacks, was self-modifying code, Is it a lost cause? |
| Message-ID | <YiUez.62168$w13.4967@fx22.iad> |
| In reply to | #12536 |
Dan Espen <despen@verizon.net> writes: >Rob <nomail@example.com> writes: > >> Dan Espen <despen@verizon.net> wrote: >>> It always seemed very odd to me, that when you write C >>> code, you're always told to always check the malloc() return code. >>> Yet, calling a subroutine needs main storage and the language >>> provides no way to check a return code for that. >>> I'm not sure if it raises a signal. >> >> This is implementation (mostly OS) dependant. Usually there is a >> signal for stack overflow, but it often is the generic signal for >> invalid memory accessed (SIGSEGV in Unix/Linux). > >Which leaves you no way to programmaticly detect the overflow. >The end user could add memory to the job if he got an informative >message. Linux, and many flavors of Unix, install inaccessible guard pages on either side of the stack to prevent inadvertent corruption. Software could catch the SIGSEGV and manually extend the stack if memory was available. The original bourne shell used that trick to extend the heap on the PDP-11 (http://www.in-ulm.de/~mascheck/bourne/segv.html)
[toc] | [prev] | [next] | [standalone]
Page 39 of 40 — ← Prev page 1 … 37 38 [39] 40 Next page →
Back to top | Article view | comp.sys.raspberry-pi
csiph-web