headers
Stephen Adolph | 1 Mar 03:29
Picon
Gravatar

Re: REX update.

yah, I could incorporate the client portion of it - would be much
faster.  at the expense of compatibility with TPDD of course.

Right now, I only support TPDD transfers within the REX application,
just to be clear.

..Steve

On Sat, Feb 28, 2009 at 5:28 PM, John R. Hogerhuis <jhoger@...> wrote:
> On Sat, Feb 28, 2009 at 5:09 AM, Stephen Adolph
<twospruces@...> wrote:
>
>>
>> To get all that TEXT out into the real world, you could use TS-DOS to
>> do it, one file at a time, or use TELCOM to transfer the text to a
>> terminal program on a PC - the standard options. I image at some point
>> a tool could be written that makes this happen quickly rather than
>> manually.
>>
>> I'm thinking that a REX dump utility could be good - stream all stored
>> RAM images to an attached PC, where an accompanying tool extracts all
>> the text files.
>>
>
> Could probably leverage fast RAM dump code to send and TBACK to catch
> the images. I need to add checksum support.
>
> I'm also planning to build either into TBACK itself, or as a separate
> utility, something that can embed and extricate files from the RAM
> image. So, you could get a directory of all files in the image, or
(Continue reading)

Permalink | Reply | 3 comments |
headers
John Whitton | 1 Mar 03:45

Re: OT, but not quite: DIY Parallax Propeller laptop

> Yeah, it was slow, but nothing motivated you to write bug-free code like
> the *really* old days when you submitted your program for keypunching
> and got your printout back two or three days later only to find a typo or
> two that meant repeating the process; if you were lucky it'd only take
> a week or so to finally get some object code to actually test.

   'Submitted for keypunching'??? Heck we had to do ourselves..

    You probably also had limited CPU time available to you. I don't 
remember what I got as an undergrad...., but it was no more than 
single-digit minutes per quarter...., maybe only it was only 10's of 
seconds..., heck.., too long ago to remember. What I *do* remember is having 
to go to the Prof, hat in hand (more than once), and ask for more CPU time 
after writing something  that really squandered time.

John W.
Permalink | Reply | 2 comments |
headers
Daryl Tester | 1 Mar 05:18
Picon

Re: OT, but not quite: DIY Parallax Propeller laptop

John Whitton wrote:

> What I *do* remember is having to go to the Prof, hat in hand (more
> than once), and ask for more CPU time after writing something
> that really squandered time.

"And you try and tell the young people of today that - they won't
 believe you!"

--

-- 
Regards,
  Daryl Tester

"Must have scripting experience; Pearl, Shell, Python, VBScript, Born,
 Corn, Awk, Sed" -- Unix job advertisement.
Permalink | Reply | 0 comments |
headers
hudson.ra | 1 Mar 08:03
Picon

Re: OT, but not quite: DIY Parallax Propeller laptop

John Whitton wrote:
>> Yeah, it was slow, but nothing motivated you to write bug-free code like
>> the *really* old days when you submitted your program for keypunching
>> and got your printout back two or three days later only to find a 
>> typo or
>> two that meant repeating the process; if you were lucky it'd only take
>> a week or so to finally get some object code to actually test.
>
>
>   'Submitted for keypunching'??? Heck we had to do ourselves..
>
>    You probably also had limited CPU time available to you. I don't 
> remember what I got as an undergrad...., but it was no more than 
> single-digit minutes per quarter...., maybe only it was only 10's of 
> seconds..., heck.., too long ago to remember. What I *do* remember is 
> having to go to the Prof, hat in hand (more than once), and ask for 
> more CPU time after writing something  that really squandered time.
>
> John W.
>
>
 Hat in hand?? I am so glad I bring my own CPU to school with me.

Ron ..
Permalink | Reply | 0 comments |
headers
M H Stein | 1 Mar 08:47

RE: OT, but not quite: DIY Parallax Propeller laptop


----------
From: 	John Whitton[SMTP:jwhitton@...]
Sent: 	Saturday, February 28, 2009 9:45 PM
To: 	m100@...
Subject: 	Re: OT, but not quite: DIY Parallax Propeller laptop

>> Yeah, it was slow, but nothing motivated you to write bug-free code like
>> the *really* old days when you submitted your program for keypunching
>> and got your printout back two or three days later only to find a typo or
>> two that meant repeating the process; if you were lucky it'd only take
>> a week or so to finally get some object code to actually test.

>   'Submitted for keypunching'??? Heck we had to do ourselves..

You had keypunches? Heaven! In my day, we had to punch each hole by 
hand with a sharp nail...

>    You probably also had limited CPU time available to you. I don't 
>remember what I got as an undergrad...., but it was no more than 
>single-digit minutes per quarter...., maybe only it was only 10's of 
>seconds..., heck.., too long ago to remember. What I *do* remember is having 
>to go to the Prof, hat in hand (more than once), and ask for more CPU time 
>after writing something  that really squandered time.

>John W. 

Ah, no, we didn't have computers when I went to school; I started in this 
business running Unit Record Tab machines, those electromechanical
monsters you see sorting cards in the old scifi movies; when we went
(Continue reading)

Permalink | Reply | 0 comments |
headers
Jan Vanden Bossche | 1 Mar 15:08
Picon
Favicon

RE: Phonetics

Hallo,

> -----Original Message-----
> From: John Whitton
> 
> > Ho (as in Santa)
> > Gur (as in purr)
> > Hice (rhymes with Rice)

Ugh!

> > At least, that's the way the Californian Hogerhuises say it.
> >  
> > I'm told native speakers of Dutch pronounce it differently.

Definitely.

> > -- John.
> 
>  John,
> 
> Had dinner Wed. night with a Dutch couple..., happened to 
> remember the 
> above, and asked them how *they* would pronounce the name. Without a 
> moment's hesitation, they both said:
> 
> Ho
> Gur
> House
(Continue reading)

Permalink | Reply | 4 comments |
headers
J Bickhard | 1 Mar 17:09
Picon

Re: OT -- First Equinox of 2009 at 11:44 UTC on March 20

The Mythbusters (one of the coolest reality-tv shows of all time, because
they blow stuff up) have actually disproved that the equinox has anything to
do with being able to balance an egg on end. I did it last September.

Jake, Editor of Micro 100 Magazine

On Fri, Feb 27, 2009 at 7:15 PM, Vic Boudolf <paperbook@...> wrote:

> is this when we can balace an egg on end?
> 73
> vic
>
>
>
> On Fri, Feb 27, 2009 at 6:36 PM, Ron Wiesen <ronw@...> wrote:
>
> > The first Equinox in year 2009 occurs at 11:44 UTC on March 20.  In the
> > Northern Hemisphere, it is the Vernal Equinox (marks first day of
> Spring).
> >  In
> > the Southern Hemisphere, it is the Autumnal Equinox (marks first day of
> > Fall).
> >
> > On that day the folks situated directly on the North pole, and the folks
> > situated directly on the South Pole, enjoy a 24-hour day during which
> > exactly
> > half of the Sun's disk is seen above their horizon as it traces a full
> 360°
> > circle around them.
> >
(Continue reading)

Permalink | Reply | 0 comments |
headers
J Bickhard | 1 Mar 17:12
Picon

Re: OT, but not quite: DIY Parallax Propeller laptop

Jake, Editor of Micro 100 Magazine

On Fri, Feb 27, 2009 at 9:41 PM, John Whitton <jwhitton@...>wrote:

> Pretty cool..., nice to see innovative thinking by young folk..., also the
> realization that a duo-core, speed-of-light processor isn't the elegant
> solution for every task.

I thought all electricity traveled at the same speed (close to the speed of
light). So then a faster processor would just shorten the amount of "stuff"
the electricity would have to travel through?

>
>
> Geeze, a 6502?? Everyone here who ever used a Kim, raise your hand <waving
> mine>.... ;-)
>
> Back in, oh.., 1979, I was using an in-house produced (there was no choice,
> no other 8080/Z-80 cross assembler existed, I don't think) macro cross
> assembler that ran under CPM on a Z-80 S-100 machine to produce 6502
> code..., them was the days...
>
> I can't recall whether it was a 2Mhz or 4Mhz machine, but I do recall that
> compilation was sufficiently slow that I always turned to some other task
> while I was waiting for it to grind through the process. About the same
> time, a friend was working on a Z-8 project using a Zilog MDS(?) development
> system..., seems as though to me it was taking something like 20 mins to do
> a compile...., whatever it was..., it was a long time. It made one
> thoughtful about producing bug-free code..., and by that I mean code that
> would at least produce a clean compile...., the real fun started later.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Rick Herndon | 1 Mar 17:25
Favicon

Re: REX update.

At 07:09 AM 2/28/2009, Steve Adolph wrote:
>I'm tempted to send this out to the beta testers for some real
>testing.   When should I do this?

As soon as you finish:
>* finish the "REX UPDATER" tool, used for flash upgrading REX software.
Seems reasonable to me, since further upgrades beyond the beta sent 
out with the unit would either be impaired or kept from happening 
until you get this 'un going.

<raises hand for BETA, GAMMA or DELTA>
Rick Herndon
K5FNI
Mathis, Texas
Permalink | Reply | 501 comments |
headers
Stephen Adolph | 1 Mar 17:34
Picon
Gravatar

Re: REX update.

The problem is, it will never be  "finished"  will it?

People always want to add this, change that, improve something else.
I was ready to release it a year ago but people did not think it was
good enough, so here we are a year later, and I am still working on
it.

I could always say - good enough - but I would actually like some
feedback some day, and get it in a state that people are satisfied
with, before I shut down this task.

So, I'm basically thinking - sell it now, use it, and make do.
However, I'm not sure I am too keen on spending lots of time
addressing "feature requests".  Bug fixes - ok.

On Sun, Mar 1, 2009 at 11:25 AM, Rick Herndon <k5fni@...> wrote:
> At 07:09 AM 2/28/2009, Steve Adolph wrote:
>>
>> I'm tempted to send this out to the beta testers for some real
>> testing.   When should I do this?
>
> As soon as you finish:
>>
>> * finish the "REX UPDATER" tool, used for flash upgrading REX software.
>
> Seems reasonable to me, since further upgrades beyond the beta sent out with
> the unit would either be impaired or kept from happening until you get this
> 'un going.
>
> <raises hand for BETA, GAMMA or DELTA>
(Continue reading)

Permalink | Reply | 503 comments |

Gmane