Vintage computing forum?

I think the confusion is because people can't decide whether the 68000 CPU was 16-bit or 32-bit.. (It is 32)
 
unlike the 8086 or the 8088 - Can we include these on the vintage list, along with my old Atari 65XE, Acorn Electron, and zx spectrum?
 
I personally don't have any more of the old equipment around anymore, but a friend of mine does....

I remember driving down to a computer shop in Novi (near Detroit, MI) to pick up his first Amiga....the 1000. Inside the cover are the signitures of the developers of the machine, including the paw print of their dog. He's still got that machine....along with my Amiga 500 and a few Atari's and C-64's.
 
well I can see this amiga argument going on ad nauseum......


in any case I'm rebuilding my atari 8bit collection.... proving to be quite expensive and it's becoming very hard to find some stuff...
 
wikipedia said:
When the 68000 was introduced, 16-bit buses were really the most practical size. However, the 68000 was designed with 32-bit registers and address spaces...

It is important to note that even though the 68000 had 16-bit ALUs, addresses were always stored as 32-bit quantities, i.e. it had a flat 32-bit address space. This meant that the 68000 was, and is, a 32-bit microprocessor...

The original 68000 was internally a 16-bit part, but it was executing and existing within the parameters of a 32bit ISA, as its instruction set describes a 32-bit architecture. The importance of architecture cannot be emphasized enough. Throughout history, addressing pains have not been hardware implementation problems, but always architectural problems (instruction set problems, i.e. software compatibility problems). The successor 68020 with 32-bit ALU and 32-bit databus runs unchanged 68000 software at "32-bit speed", manipulating data up to 4 gigabytes, far beyond what software of other "16-bit" CPUs (for example, the 8086) could do. Contrast this with the problems posed by segmented architectures such as the 80286 which eventually had to be emulated entirely in software. It is seen as an act of great foresight for the 68000 series to have been 32-bit from the beginning.

I think it is 32 bit as much as a 8086 is 16 bit.
 
Wikipedia said:
It is important to note that even though the 68000 had 16-bit ALUs, addresses were always stored as 32-bit quantities, i.e. it had a flat 32-bit address space. This meant that the 68000 was, and is, a 32-bit microprocessor...

The original 68000 was internally a 16-bit part, but it was executing and existing within the parameters of a 32bit ISA, as its instruction set describes a 32-bit architecture. The importance of architecture cannot be emphasized enough. Throughout history, addressing pains have not been hardware implementation problems, but always architectural problems (instruction set problems, i.e. software compatibility problems). The successor 68020 with 32-bit ALU and 32-bit databus runs unchanged 68000 software at "32-bit speed", manipulating data up to 4 gigabytes, far beyond what software of other "16-bit" CPUs (for example, the 8086) could do.

So was the 68000 the first of it's kind in personal systems??
 
any old fashioned atari bbses still around (dial up)

Any old fasioned bbses still up that anyone knows about?
 
well, I know that.. but was it the first (32bit processor or processor that worked the way it did) of it's kind
 
I'm being 100% serious... Unproper use of grammar and capitalization make posts look bad, and information in general unreliable. I would appreciate if you make a better effort on polishing your posts.

Also, double posting goes against our Community guidelines.

Avoid double posting. Make good use of the 'Edit' function and do not “reply to yourself” in a same thread unless it's completely necessary.
https://www.techspot.com/extras/forum_guidelines/index.shtml
 
The gods have spoken. We must use proper grammer.....

A few errors here! ;)

"[...]have spoken. We must[...]" A comma is going here, no?

What is grammer?

And 5 dots? It's not just 3 or nothing?

I'm laughing out loud. (We should type these too?)
 
Back