Very cool :-)
>
-- John.
Great story! Thanks.
> On Dec 10, 2018, at 7:51 PM, Mitch Parker wrote:
>
> Good evening,
>
> Today I had to give a presentation to my daughter's early childhood education
> class on "What Does Daddy Do?". I talked about working with computers, and
> keeping computers safe for the people tha
Good evening,
Today I had to give a presentation to my daughter's early childhood
education class on "What Does Daddy Do?". I talked about working with
computers, and keeping computers safe for the people that use them at Riley
Hospital for Children. I also brought a computer with me that would
Thanks Stephen! got mine today
https://photos.app.goo.gl/MQFt5ijgar3XvaRJ9
On Tue, Nov 13, 2018 at 6:05 PM Stephen Adolph wrote:
> All,
> I have an updated software load for REX which I will be posting shortly.
> Now that it is working well again, I feel ok selling REXNEC.
> I have 3 units avai
On Mon, Dec 10, 2018 at 10:35 AM Jerry Stratton wrote:
> It was very common back in the day to start all subroutines at line 1000,
> or some other large round number, and then just before that large number
> have an END statement.
>
>
I agree Jerry, that's a good practice.
Still need to be caref
It was very common back in the day to start all subroutines at line 1000, or
some other large round number, and then just before that large number have an
END statement.
999 END
1000 REM SUBROUTINES FOLLOW
1100 REM ADD ONE TO A
1110 A = A + 1
1199 RETURN
1200 REM MULTIPLE A BY 1
1210 A = A *1
12
In other languages you can't call into the middle of a function. There is
one entry point, possibly multiple exit points. There's no chance
unbalanced CALL and RETURN. once you return you're jump to the stacked
address and you're no longer in the subroutine.
In basic subroutines, because every lin
There is no way to interpret what John described, as "forget that it is in
a subroutine and not understand the return statement", and no way to
interpret what you described as a stack.
You definitely said very different things, not the same thing in diffrent
ways.
--
bkw
On Mon, Dec 10, 2018,
those ram modules are tough to solder. I think there was some kind of high
temp solder used between the ceramic carrier and the SMT chips.. I'd be
interested to know how it goes. I recently tossed one out that I also
could not debug.
On Mon, Dec 10, 2018 at 8:23 AM wrote:
> Hi Jan, yes I knew
Hi Jan, yes I knew that, but thank you!
In this days I payed a bit
with my restored M10 and I'm so happy with it :)
Since there are 4 IC in
each SRAM module and I have 2 broken modules, I was hoping to test the
single IC to find the individual broken IC and restore one module mixing
the IC of th
FYI: the M-10 uses the same modules als the M100.
Greetings from the TyRannoSaurus
Jan-80 "
@ work( @ @ )
--.ooo--(_)--ooo.---
-Original Message-
From: M100 [mailto:m100-boun...@lists.bitchin100.com] On Behalf Of Francesco
Messineo
Sent: woensdag 5
Nope.
On Mon, Dec 10, 2018 at 12:13 AM Peter Vollan wrote:
> That is just a more verbose way of saying what I already said.
>
>
That is just a more verbose way of saying what I already said.
On Sun, 9 Dec 2018 at 19:04, John R. Hogerhuis wrote:
>
> " It seems that a limitation of the model
> 100 is that if you gosub to a subroutine, and then gosub again, it
> will forget that it is it in a subroutine, and not understand t
13 matches
Mail list logo