Re: An American perspective on the late great Sir Clive Sinclair, from Fast Company

2021-09-28 Thread Jecel Assumpcao Jr via cctalk
Yeechang Lee wrote on Tue, 28 Sep 2021 10:36:15 -0700 > The US industry thought that the $99 price point needed to be reached, in > part because of the Timex/Sinclair 1000's example; besides the 99/2 and > Commodore 16, the TRS-80 MC-10 is another example of the ultra low-cost > "Sinclair

Re: An American perspective on the late great Sir Clive Sinclair, from Fast Company

2021-09-27 Thread Jecel Assumpcao Jr via cctalk
While the American public were very ignorant of Sinclair's achievements, the US home computer makers were very worried about them. In 1983 both Commodore and Texas Instruments were working on their "ZX81 killers". https://www.99er.net/992.html https://en.wikipedia.org/wiki/Commodore_16 -- Jecel

Re: R.I.P. Clive Sinclair

2021-09-21 Thread Jecel Assumpcao Jr via cctalk
Fred Cisin wrote on Sat, 18 Sep 2021 13:45:04 -0700 (PDT) > On Sat, 18 Sep 2021, dwight via cctalk wrote: > > Of course, Busicom was the first programed microprocessor driven > > calculator, it wasn't the first calculator using calculator ICs. That is > > what Busicom was trying to compete with,

Re: chaos and the LGP-30

2020-07-26 Thread Jecel Assumpcao Jr via cctalk
Jay Jaeger wrote on Sun, 26 Jul 2020 19:24:24 -0500 > So, either he mis-entered something, or possibly the result of a > different state of a random number generator somewhere? He dumped the full state of the simulation to paper with six digits after the decimal point even though the internal

Re: On: raising the semantic level of a program

2020-06-28 Thread Jecel Assumpcao Jr via cctalk
ben wrote on Sat, 27 Jun 2020 19:15:25 -0600 > It would be nice if one could define a new language for problem > solving and run it through compiler-compiler processor for interesting > problems. That is what Alan Kay's group did a few year ago in their "STEPS" project. They wanted to implement

Re: Microsoft open sources GWBASIC

2020-05-29 Thread Jecel Assumpcao Jr via cctalk
Liam Proven wrote on Fri, 29 May 2020 14:20:53 +0200 > And I have had earnest youngsters on Twitter and elsewhere very > seriously tell me that _no_ language could even theoretically be > immune to the problems of C, because _all_ languages are implemented > in C at the lowest level. The modern

ZX81 killers (was: Microsoft open sources GWBASIC)

2020-05-28 Thread Jecel Assumpcao Jr via cctalk
Jim Brain wrote on Thu, 28 May 2020 18:15:19 -0500 > On 5/28/2020 1:24 PM, Liam Proven via cctalk wrote: > > > >> . Evidently, there exists a lower bound of functionality > >> of computing capability in the US, and the little wedge just didn't make > >> it. > > No no. It wasn't that. It was

Re: Microsoft open sources GWBASIC

2020-05-28 Thread Jecel Assumpcao Jr via cctalk
Jim Brain wrote on Thu, 28 May 2020 15:54:10 -0500 > On 5/28/2020 12:38 PM, Liam Proven via cctalk wrote: > > ? TRS-80 Colour, AKA CoCo -- 6809 > Started life as a farming-related Videotex terminal.  Pics will show the > amazing similarity.  Was a joint venture between Motorola and Tandy, and

Re: Living Computer Museum

2020-05-27 Thread Jecel Assumpcao Jr via cctalk
Alan Perry wrote on Wed, 27 May 2020 20:02:06 -0700 > That wasn't an option for most folks. They told me that they didn't accept > items on loan. > > alan > > > On May 27, 2020, at 19:33, Chris Hanson wrote: > > > > This is why people should avoid donating equipment directly to institutions

Re: history is hard (was: Microsoft open sources GWBASIC)

2020-05-24 Thread Jecel Assumpcao Jr via cctalk
Fred, > Quite true that Gary did not have the ruthless personality to compete. > If the roles had been reversed, Gary would NOT have become a bill Gates. > Yes, the final outcome was inevitable, although the one incident set the > path. It is fairly commonly believed that MS-DOS would not

Re: history is hard (was: Microsoft open sources GWBASIC)

2020-05-24 Thread Jecel Assumpcao Jr via cctalk
Fred, > To me, the culture clash aspect makes it one of the greatest stories of > the time. > Was Gary not taking the meeting seriously enough to be there on time, and > as a consequence, ending up being $80B behind Bill Gates, the stupidest > mistake anybody has ever made? > Or the bravest

history is hard (was: Microsoft open sources GWBASIC)

2020-05-23 Thread Jecel Assumpcao Jr via cctalk
Fred Cisin advised on: Sat, 23 May 2020 20:29:28 -0700 (PDT) > But, read carefully the corrections that others made! Some things are easy to check, like the fact that the Z80 came out in 1976 when Woz was already finishing the Apple II so he couldn't have considered using it for the Apple I. Note

Re: 50 yrs. ago today

2019-10-29 Thread Jecel Assumpcao Jr. via cctalk
We celebrated the 40th anniversary of the Internet less than 2 years ago: > https://computerhistory.org/blog/born-in-a-van-happy-40th-birthday-to-the-internet/ The ARPAnet was a WAN (wide area network) and not an Internet, but it was one of the three networks involved in that first test on

Re: MULTIPROCESSING FOR THE IMPOVERISHED Part 1: a 6809 Uniprocessor

2019-08-06 Thread Jecel Assumpcao Jr. via cctalk
Ben wrote on Tue, 6 Aug 2019 13:47:59 -0600 > It was too bad the 6809 did not have a pin to indicate Instruction or > Data memory bank in use. That would of given a real unix system in the > 8 bit world, as by then (late 70s) 64kb was proving just to small for > any real use. I added a circuit

Re: Question about Apple ///

2019-07-05 Thread Jecel Assumpcao Jr. via cctalk
Adam Thornton wrote on Fri, 5 Jul 2019 11:38:56 -0700 > I have an Apple /// that I've had for many years; it's never worked. > > When you power it up, you get a checkerboard screen, where half the squares > are solid white, and the other half have a little mosaic pattern in them. > > Looks like

Re: One of the deeper dives into RISC vs CISC I've seen

2019-06-12 Thread Jecel Assumpcao Jr. via cctalk
Alan, > I especially appreciated he not only offered an opinion - his specific > ideas on where the boarder between RISC and CISC was - but then provided > an analysis of a bunch of processors based on those criteria and an > analysis of the outliers that challenged his criteria. It's a well

Re: modern stuff

2018-10-25 Thread Jecel Assumpcao Jr. via cctalk
Jim Manley wrote about a professor's experience in the iAPX432 team. Didn't at least part of the team continue the project as the BiiN / 960MX? -- Jecel

Smalltalk (was: Desktop Metaphor)

2018-10-23 Thread Jecel Assumpcao Jr. via cctalk
Josh Dersch wrote on Tue, 23 Oct 2018 07:25:41 -0700 > I've never seen evidence for any Smalltalk having a desktop metaphor (as in > the discussion at hand -- icons and folders representing files and/or data, > not merely windows, etc.). It's certainly possible that the platform was > used for

Re: Int 13h buffer 64k boundaries

2018-04-19 Thread Jecel Assumpcao Jr. via cctalk
Chuck Guzis pointed out that the PC was built from 8 bit peripheral chips, which was where the 64KB problem came from. When I saw the design, I thought it was really cute how they were able to use one of the timer channels and one of the DMA channels to implement a DRAM refresh circuit almost

Re: Speed now & then

2018-04-11 Thread Jecel Assumpcao Jr. via cctalk
Chuck Guzis wrote on Wed, 11 Apr 2018 11:09:23 -0700 > I thought that Moore's "law" dealt only with the number of transistors > on a die. Did Gordon also say something about performance? That is correct. The observation that transistors would be faster and use less power as they became smaller

RE: Why women were the first computer programmers

2017-08-24 Thread Jecel Assumpcao Jr. via cctalk
Jay West wrote (among other things): > On a technical list with adults, I believe that when someone posts something > on-topic which has portions you do not personally like that perhaps the adult > thing is to take the points that are in-common and expand on them, leaving > the points behind that

Re: Kryoflux or Catweasle

2017-05-24 Thread Jecel Assumpcao Jr. via cctalk
Al Kossow wrote on: Wed, 24 May 2017 14:28:19 -0700 > On 5/24/17 12:58 PM, ben via cctalk wrote: > > > With typo in VHDL you have hard problem finding that single gate > > error. > > The world has been debugging 100,000+ gate systems with simulations for > a few decades now. > > Once you've

APL and descendants - was Re: If C is so evil why is it so successful?

2017-04-13 Thread Jecel Assumpcao Jr. via cctalk
Toby Thain via cctalk wrote on Thu, 13 Apr 2017 19:34:08 -0400 > On 2017-04-13 6:54 PM, Chuck Guzis via cctalk wrote: > > So, whence APL today? > > Still lives on -- Dyalog, J, K, etc. Recently discovered the #jsoftware > channel on Freenode for APL fans. I consider Matlab and Julia to be

dataflow (was: RTX-2000 processor PC/AT add-in card (any takers?))

2017-04-11 Thread Jecel Assumpcao Jr. via cctalk
Chuck Guzis via cctalk wrote on Tue, 11 Apr 2017 18:05:01 -0700 > On 04/11/2017 04:53 PM, Jecel Assumpcao Jr. via cctalk wrote: > > > I consider the heart of any modern high performance CPU to be a > > dataflow architecture (described as an "out of order execution >

Re: RTX-2000 processor PC/AT add-in card (any takers?)

2017-04-11 Thread Jecel Assumpcao Jr. via cctalk
Noel Chiappa via cctalk wrote on Tue, 11 Apr 2017 10:18:00 -0400 (EDT) > > From: Sean Conner > > > I really think it's for *this* reason (the handler() example) that C > > doesn't allow nested functions. > > I wouldn't be sure of that; I would tend to think that nested functions were

Re: RTX-2000 processor PC/AT add-in card (any takers?)

2017-04-11 Thread Jecel Assumpcao Jr. via cctalk
Chuck Guzis via cctalk wrote on Tue, 11 Apr 2017 09:37:27 -0700 > On 04/10/2017 02:23 PM, Eric Smith wrote: > > > When the 432 project (originally 8800) started, there weren't many > > people predicting that C (and its derivatives) would take over the world. > > That's the danger of a

C (was: The iAPX 432 and block languages)

2017-04-11 Thread Jecel Assumpcao Jr. via cctalk
Sean Conner wrote two great posts on Mon, 10 Apr 2017 21:43:29 -0400 These are all very good points. I agree I was exagerating by saying the iAPX432 and 8086 couldn't run C. After all, the language was born on the PDP-11 and that was limited to either 64KB or 128KB. So any C programs for that

Re: RTX-2000 processor PC/AT add-in card (any takers?)

2017-04-10 Thread Jecel Assumpcao Jr. via cctalk
Chuck Guzis via cctalk wrote on Date: Mon, 10 Apr 2017 15:21:08 -0700 > Thanks for the list--I was aware of the various Java engines and the WD > P-code engine, but had never run into the SCAMP. I just found an academic Pascal microprocessor from 1980 called EM-1 and described all the way to the

The iAPX 432 and block languages (was Re: RTX-2000 processor PC/AT add-in card (any takers?))

2017-04-10 Thread Jecel Assumpcao Jr. via cctalk
Sean Conner via cctalk wrote on Mon, 10 Apr 2017 17:39:57 -0400 > What about C made it difficult for the 432 to run? > > -spc (Curious here, as some aspects of the 432 made their way to the 286 > and we all know what happened to that architecture ... ) C expects memory addresses to

Re: RTX-2000 processor PC/AT add-in card (any takers?)

2017-04-10 Thread Jecel Assumpcao Jr. via cctalk
Bill Gunshannon via cctalk wrote on Mon, 10 Apr 2017 20:59:40 + > On 4/10/2017 4:42 PM, Chuck Guzis via cctalk wrote: > > Were there any microprocessor chips that attempted to mimic the > > Burroughs B5000 series and natively execute Algol of any flavor? > > No, but Western Digital

Re: [VideoMagia] Reparando um Vectrex

2017-03-24 Thread Jecel Assumpcao Jr. via cctalk
Geoffrey Oltmans wrote: > I can imagine that they employed a similar vector generator on the Vectrex. The 6809 processor had to go through the display list itself. But the analog design was very clever. To draw a vector you would use the single DAC to set the start x voltage, then use the same

Re: Reading PALs

2017-02-21 Thread Jecel Assumpcao Jr.
Jim Brain wrote: > As a function of "give a man a fish, you feed him for a day; teach a man > to fish, you feed him for all time", I dloaded Logic Friday, and figured > out a quick way to read the two 16L8 (combinatorial only) PALs on the > board with my EPROM reader (cue duct tape and baling

recursive emulation (was: IBM 7074 and then some: "Systems we love" conference)

2017-01-24 Thread Jecel Assumpcao Jr.
Chuck Guzis asked on Mon, 23 Jan 2017 22:00:15 -0800 > Is there a "recursive" emulator setup wherein one machine emulates > another one...where the final emulation is for the original hardware? In 1988 I designed an ARM2 based computer (my Merlin 4, which was only built in 1992 when the ARM2 was

Re: What's the rarest or most unusual computer-related item do you own?

2017-01-12 Thread Jecel Assumpcao Jr.
Andy Cloud wrote on Tue, 10 Jan 2017 22:09:52 + > I thought this would be an interesting question to ask around - What's the > rarest or most unusual computer-related item do you own? Stuff that I designed and built myself but wasn't produced is rare, obviously, but it is likely that this

Meaning of "architecture width" - Re: 68K Macs with MacOS 7.5 still in production use...

2016-09-16 Thread Jecel Assumpcao Jr.
I wrote: > The 68000 has three separate 16 bit ALUs: one for DataLow, one for > AddressLow and another for AdressHigh. DataHigh can be processed by > either the first or the second one. The first one implements all > operations while the other two only do add/subtract and some limited > shifting.

Meaning of "architecture width" - Re: 68K Macs with MacOS 7.5 still in production use...

2016-09-16 Thread Jecel Assumpcao Jr.
The 68000 has three separate 16 bit ALUs: one for DataLow, one for AddressLow and another for AdressHigh. DataHigh can be processed by either the first or the second one. The first one implements all operations while the other two only do add/subtract and some limited shifting. See figure 8 of:

Forth and threading (was: strangest systems I've sent email from)

2016-04-29 Thread Jecel Assumpcao Jr.
Ben, > I liked Forth when it was still threaded. You got the DOES> feature. > Do you still have that with the FORTH chips? All Forth implementations are threaded, but there are several kinds: direct, indirect, token and subroutine. Initially indirect threading was the most popular implementation

smalltalk and lisp (was: strangest systems I've sent email from)

2016-04-27 Thread Jecel Assumpcao Jr.
Sean Conner wrote:on Wed, 27 Apr 2016 16:13:07 -0400 > The 6908 *is* better than either the Z80 or the 6502 (yes, I'm one of > *those* 8-) To be fair, the Z80 and 6502 had to compete against the 8080 while the 6809 came out after the 8086 and 68000. > Citation needed. C derivatives? The

bit slice chips (was Re: Harris H800 Computer)

2016-04-22 Thread Jecel Assumpcao Jr.
Eric Smith mentioned: > [2901 A, B, and C, CMOS versions] > [2903 and 29203] > [Intel 3001 and 3002] > [MMI 5701/6701] > [Motorola MC10800] I'd add the Texas Instruments SN74S481, SN54LS481 and SN74LS481 TTL 4 bit slices. The Schottky version had a 90ns clock cycle and the low power versions

Re: Know any Fortran programmers who need a more interesting job?

2015-10-30 Thread Jecel Assumpcao Jr.
Noel Chiappa wrote: > It's worth teaching a bit of machine/assembler language, so that students > understand how computers _actually work_, underneath. > > [example of students who wrote octal math for CLU] Back in 1983 I needed an assembler for the Motorola 6809, so I wrote one in Lisp on a

Re: Computers in Election Vigils - take two

2015-10-12 Thread Jecel Assumpcao Jr.
Paul Koning wrote on Sat, 10 Oct 2015 11:44:58 -0400: > > On Oct 9, 2015, at 5:39 PM, Jecel Assumpcao Jr. wrote: > > [noticed voter ID terminal had cable to voting machines!] > > That's not the real problem. Indeed, not *the* problem but just *a* problem I noticed while st

Re: Computers in Election Vigils - take two

2015-10-09 Thread Jecel Assumpcao Jr.
John Robertson asked: > >After the fiasco about the Deibold machines changing votes during the > >Bush election of 2000, Brazil opted for them? To which Alexandre Souza replied: > Yep. Welcome to the land of the stupid. Ok, I think we need some facts, here. Note that from the very first

Re: OT: x86 machine code [Was: Re: Self modifying code, lambda calculus - Re: ENIAC programming]

2015-09-18 Thread Jecel Assumpcao Jr.
Just a quick history of x86 implementation styles (from memory, so don't take this very seriously): 8086: Intel's first pipeline, with separate Fetch and Execution units iAPX286: borrowed some ideas from iAPX432's protection model, but I don't know any implementation details 386: traditional

Re: Classic programming

2015-08-07 Thread Jecel Assumpcao Jr.
I am writing this in Celeste, which is the email app in the Squeak Smalltalk programming language and system. The way you normally use Smalltalk is to save a snapshot (called an image file in Squeak) of your full working environment and which you can later restore to have everything back exactly