what is the difference between x64 and x86

K

Ken Blake

Actually, there were home computers well before the 80286 and 386
6502 (Apple I & II) and others.
8080, Z80 Radio Shack, Heathkit, Zenith, Altar, others.

Yes, certainly. I was referring only to the intel 80... line.
 
K

Ken Blake

He was referring to what IBM released, I don't remember IBM using any of
those except the 8088; did they? IBM has never been an innovator and used
anything 'new'.

Yes, they did. IBM used the 80286, and they also used the 8085 in the
System 23/Datamaster (I was one of the few System 23 customers).
 
R

relic

Ken Blake said:
Yes, they did. IBM used the 80286, and they also used the 8085 in the
System 23/Datamaster (I was one of the few System 23 customers).
"those" were the above list: "Notably, the 8086 & 8088, the 6502 & 6510, the
Motorola 680x0 series"
 
C

Char Jackson

But you're right, one should not post HTML in Usenet, so mulþumesc.
English, please. This is your only warning. ;-)

I had to google mulþumesc and I'm still not sure I got it. My spell
checker is offering "Muslims" as a replacement. :)
 
R

R. C. White

Hi, Bob.
Wrong again, the 8088 was/is 16 bit and the 80386 is/was 32 bit.
Still not exactly correct. The 8088 was 16-bit internally, but communicated
through an 8-bit bus, so each transmission had to be divided into two 8-bit
segments, which were transmitted sequentially and then reassembled at the
other end. Or so I'm told; I'm not a techie.

The 8086 was Intel's first full 16-bit CPU with a 16-bit bus.

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64
SP1


"Bob I" wrote in message
Not exactly correct. The first home computers had what IBM called a 386.
Then went to a 486.
Wrong
http://en.wikipedia.org/wiki/IBM_PCjr

I remember seeing an old show from the 80's where the line was, "A 686?
Hell, the 486 was just put on the market and you've got a 686? What
happened to the 586?"
Then pentium was introduced. As a response to the more powerful AMD.


Beginning with the 80386 chip in 1978, which was a 16 bit one, IBM then
began advancing the chips towards 32 bit.
Wrong again, the 8088 was/is 16 bit and the 80386 is/was 32 bit.
 
G

Gene E. Bloch

English, please. This is your only warning. ;-)

I had to google mulþumesc and I'm still not sure I got it. My spell
checker is offering "Muslims" as a replacement. :)
What shows as an eth (or is it a thorn?) in your copy was, in mine, a t
+ cedilla, pronounced /ts/ in Romanian.

Multsumesc (to spell it in American letters) is "Thanks" in Romanian - I
had noticed Rebecca's country code. That pretty much covers my
vocabulary in Romanian, except for a few dance and song names and such.

I have an LP of Balada Åžarpelui - Ballad of the Snake - with all of the
words (there are many) printed in the insert, and conveniently, they are
translated - into French. Oh well. The first letter of the second word
is an S + cedilla. Sharpelui (in American letters) is a cognate of
serpent, BTW. Same Latin source as our word (lui means of the).

And I am duly warned, Sir!
 
R

R. C. White

Hi, Richard.
Not exactly correct. The first home computers had what IBM called a 386.
Then went to a 486.
You're starting a generation or two late. :^{

Depends on your definition of "home computers".

My first computer was the original TRS-80, in 1977, with the Z80 chip from
Zilog, which was an improvement on Intel's 8080. IBM's first PC (Personal
Computer) used the Intel 8088 CPU, which was 16-bit internally but
communicated over an 8-bit bus, requiring each 16-bit word to be divided
into two 8-bit bytes, transmitted, then reassembled at the receiving end.
The 8086 (in the AT, for Advanced Technology) was the first true 16-bit chip
used by IBM, as I recall. And that was still long before the 32-bit 80386,
or even the 80286.

Most people overlook the 80186, which was a true 16-bit CPU with 16-bit data
path. That's what is in the Tandy 2000, which I bought in 1983 (and still
have in the "museum" in my closet). This was from Tandy, not IBM, of
course, and used TRS-DOS, not MS-DOS, and was not bothered by the 64-KB
limit on usable RAM. My machine eventually was upgraded to 768 KB RAM,
which was rare in those days. The Tandy 2000 was featured in ads in
Creative Computing and other magazines of the day with Bill Gates saying it
would be the perfect machine for his forthcoming new "Windows", which would
be released Real Soon Now. And, yes, I did run Windows (1.0) on it - but
not long - before Windows 2.0 and, at last, Windows 3.1, the first really
productive version.

This is from 30+ year-old memory, so there may be some slight slippage, but
I'm sure it's mostly correct.

But Microsoft still should have called it "x32" instead of "x86".

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64
SP1


"richard" wrote in message
x86 refers to the 32 bit architecture/instruction-set from Intel.
x64 refers to the compatible 64 bit architecture, I think this might have
originated from AMD but I'm not sure.
In both cases other manufactures make compatible devices so the
originating
manufacturer doesn't matter.
This article might help: http://everything.explained.at/X86_architecture/
although it focuses more on x86 and less on x64.

The key thing if you are downloading software is that x86 refers to 32
bit,
and x64 to 64 bit.
If your PC is less than 5(ish) years old then its hardware is probably 64
bit, but it might be running a 32 bit operating system in which case if
given a choise when downloading software you should go for the x86
version.
If your are running a 64 bit operating system then go for the x64 version
if
one exists, but you might (depending on what it is) still be able to run
with the 32 bit (x86) version.

Hope this helps.
Not exactly correct. The first home computers had what IBM called a 386.
Then went to a 486.
I remember seeing an old show from the 80's where the line was, "A 686?
Hell, the 486 was just put on the market and you've got a 686? What
happened to the 586?"
Then pentium was introduced. As a response to the more powerful AMD.


Beginning with the 80386 chip in 1978, which was a 16 bit one, IBM then
began advancing the chips towards 32 bit.

Quite frankly, Microsoft's use of x86 and x64 is a nostalgic misgnomer.
Where x86 technically refers to the chip, MS is referring to the 32 bit
stuff, whic is wrong because in the case of windows, it is the operating
system software that is either 32 or 64 bit which has nothing to do with
the chip hardware.
 
V

Vic RR Garcia

I blame the user for not configuring their posting software properly.
Actually, my posting software is OK, it's configured to post 'exactly
the same as the original post', and in this case the OP was HTML....
But it actually warned me that I was posting to a News group in HTML, so
I changed it to be both: HTML and plaintext,
her newsreader was unable to pick the choice... well, we are in 2011,
maybe she does have a real reason to used an outdated reader, but
most people here NO, I actually give then the choice.
You're making quite a few assumptions there that aren't supported by
facts, as far as I can tell. You may want to reconsider, and I hope
you will.
No, I'm NOT, check the past post, MOST of then are HTML, very few text ones.
Check your 'facts' before calling them.
So everyone should accommodate you? Wouldn't it be a lot easier if you
accommodated the rest of us? This isn't an HTML group. Like most of
Usenet, it's a plain text group. HTML has no place here.
NO, nobody should accommodate me, WE should accommodate the times we are
living in.
There is NOT reason for somebody living in the 80's since we are in 2011.
Again, this is NOT a Unix/Linux newsgroup, it's a WINDOWS newsgroup,
tradition means nothing at Redmond.
Thanks for your consideration.
You are welcome, I do understand your position (I'm an old hand, since
1974, before PC's) but, we had to evolve.
 
R

R. C. White

Woops!
and was not bothered by the 64-KB limit on usable RAM.
Make that 640-KB, of course. And, yes, that's KB, not MB. ;^]

RC
--
R. C. White, CPA
San Marcos, TX
(e-mail address removed)
Microsoft Windows MVP (2002-9/30/10)
Windows Live Mail Version 2011 (Build 15.4.3508.1109) in Win7 Ultimate x64
SP1


"R. C. White" wrote in message

Hi, Richard.
Not exactly correct. The first home computers had what IBM called a 386.
Then went to a 486.
<SNIP>
 
V

Vic RR Garcia

x86
- x64
_____
22
Nyet, assumed the 'x' stand for apples, so we have 86 apples minus 64
apples, we have 22 apples left, so correct result is '22 apples' = x22.
 
L

Lee Waun

Tom Lake said:
"Ed Cryer" wrote in message




Corrigendum.

x(86) -x(64) = x(22)
but
x86 -x64 = 22

Ed
So why is 12x - 5x = 7x? 8^)

Tom L
Go look it up on Google!
 
V

Vic RR Garcia

Hi, Richard.


You're starting a generation or two late. :^{

Depends on your definition of "home computers".

My first computer was the original TRS-80, in 1977, with the Z80 chip
from Zilog, which was an improvement on Intel's 8080. IBM's first PC
(Personal Computer) used the Intel 8088 CPU, which was 16-bit
internally but communicated over an 8-bit bus, requiring each 16-bit
word to be divided into two 8-bit bytes, transmitted, then reassembled
at the receiving end. The 8086 (in the AT, for Advanced Technology)
was the first true 16-bit chip used by IBM, as I recall. And that was
still long before the 32-bit 80386, or even the 80286.

Most people overlook the 80186, which was a true 16-bit CPU with
16-bit data path. That's what is in the Tandy 2000, which I bought in
1983 (and still have in the "museum" in my closet). This was from
Tandy, not IBM, of course, and used TRS-DOS, not MS-DOS, and was not
bothered by the 64-KB limit on usable RAM. My machine eventually was
upgraded to 768 KB RAM, which was rare in those days. The Tandy 2000
was featured in ads in Creative Computing and other magazines of the
day with Bill Gates saying it would be the perfect machine for his
forthcoming new "Windows", which would be released Real Soon Now.
And, yes, I did run Windows (1.0) on it - but not long - before
Windows 2.0 and, at last, Windows 3.1, the first really productive
version.

This is from 30+ year-old memory, so there may be some slight
slippage, but I'm sure it's mostly correct.

But Microsoft still should have called it "x32" instead of "x86".

RC
Pretty much on the ball park, but the 8086 was not used on the 'AT' it
was used on the 'XT' and in most other clones, plus several mainframe
terminals (smart ones). The advanced clones used the 80186, a great CPU,
but too expensive for the times.
The 'AT' used the 286 and was able to break the 640K barrier since it
implemented 'protect mode', later perfected on the 386 series, Motorola
chips never had such problems since their design was way ahead of the
Intel ones, but were harder to program, at that time there were not too
many 'good, experienced' programmers available, so Intel took over.
 
C

charlie

"those" were the above list: "Notably, the 8086 & 8088, the 6502 & 6510,
the Motorola 680x0 series"
As I remember, in the 1990's IBM put out a "Value line" sold to DOD and
Corporates that was initially a 386 machine, then later, a 486. The AF
bought a large number of them, to replace old Zenith 286 systems. The
major reason was to convert to windows 3.11. By that time the 386'es
were up to a whopping 66Mhz clock speed. During the day my desktop at
work was, well, a typical windows desktop. At night, it transformed into
a .gov server, and allowed me to access it via a dialup mainframe
connection. In turn, with remote operation enabled, it allowed me to use
the mainframe as if I was at my desk. Those were the days! Use an Apple
II to access an IBM P/C via a mainframe, then use the mainframe from the
IBM P/C. At one point, a collective effort used idle mainframe time to
capture the Simtel library. (The Simtel server was on a .gov server
(Army) back then.)
 
C

Char Jackson

What shows as an eth (or is it a thorn?) in your copy was, in mine, a t
+ cedilla, pronounced /ts/ in Romanian.

Multsumesc (to spell it in American letters) is "Thanks" in Romanian - I
had noticed Rebecca's country code. That pretty much covers my
vocabulary in Romanian, except for a few dance and song names and such.

I have an LP of Balada ?arpelui - Ballad of the Snake - with all of the
words (there are many) printed in the insert, and conveniently, they are
translated - into French. Oh well. The first letter of the second word
is an S + cedilla. Sharpelui (in American letters) is a cognate of
serpent, BTW. Same Latin source as our word (lui means of the).
I'm pretty sure that's more than I expected to learn!
And I am duly warned, Sir!
As if I had the power to warn anyone. ;-)
 
C

Char Jackson

Actually, my posting software is OK, it's configured to post 'exactly
the same as the original post', and in this case the OP was HTML....
That's not really a good enough reason though, is it?
But it actually warned me that I was posting to a News group in HTML, so
I changed it to be both: HTML and plaintext,
Cool. You almost had it right then.
her newsreader was unable to pick the choice... well, we are in 2011,
maybe she does have a real reason to used an outdated reader, but
most people here NO, I actually give then the choice.
And last year was 2010 and the year before that was 2009, but yet
Usenet remains a plain text medium. Besides, who are you (who are any
of us?) to decide which newsreaders are outdated or not?
No, I'm NOT, check the past post, MOST of then are HTML, very few text ones.
Check your 'facts' before calling them.
Yes, you are. You're assuming that most Windows 7 users use a
newsreader that's capable of HTML. Where is the data to back that up?
Windows 7 doesn't even come with a newsreader. You also state that
this is a Windows newsgroup, but it's first and foremost a Usenet
newsgroup. The topic only happens to be Windows 7. There's nothing in
that statement to indicate HTML would be welcome here.
NO, nobody should accommodate me, WE should accommodate the times we are
living in.
Good, so you'll be posting in plain text, then? After all, that
accommodates the rest of us quite nicely.
There is NOT reason for somebody living in the 80's since we are in 2011.
Again, this is NOT a Unix/Linux newsgroup, it's a WINDOWS newsgroup,
tradition means nothing at Redmond.
Redmond has nothing to do with anything here, and as stated above,
this is a Usenet newsgroup. Plain text is still the default on Usenet.
You are welcome, I do understand your position (I'm an old hand, since
1974, before PC's) but, we had to evolve.
Some say the beauty of Usenet is that it hasn't followed all of the
fads of the web, with blinking text and the other stuff that just gets
in the way of open communication.

Anyway, all of this is just a friendly suggestion. Do what you like.
 
V

Vic RR Garcia

That's not really a good enough reason though, is it?
Is good for me, if the OP is HTML, my reply should be HTML too.
Cool. You almost had it right then.

And last year was 2010 and the year before that was 2009, but yet
Usenet remains a plain text medium. Besides, who are you (who are any
of us?) to decide which newsreaders are outdated or not?
I should had said that her reader was miss-configured, since she used
Windows Live Mail.
And yes you are right, most of Usenet is still a plain text medium.
No, I'm not, most post in this group and in every 'Windows related'
groups, are HTML.
Of course in the rest of Usenet, about everything is text.
Good, so you'll be posting in plain text, then? After all, that
accommodates the rest of us quite nicely.
Nyet, if I'm posting, then yes, I use text; if I'm replying to somebody
else, I use the same format the OP used.
For me that is common courtesy.
Redmond has nothing to do with anything here, and as stated above,
this is a Usenet newsgroup. Plain text is still the default on Usenet. Agree.
Some say the beauty of Usenet is that it hasn't followed all of the
fads of the web, with blinking text and the other stuff that just gets
in the way of open communication.

Anyway, all of this is just a friendly suggestion. Do what you like.
And that's also the beauty of Usenet, we can agree to disagree.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top