Well according to Microsoft(Who owns the Legal Copyright to the OS, There is no such OS as "Windows AMD64"

Microsoft can call it anything it wants in its products, the name of the ISA (Instruction Set Architecture) still is AMD64. If all you have to say is about such picayunes, please, feel free to ignore this thread, it's not for you.

Well It just sounds so like Linux to Me, and the two shouldn't be mixed that's all. It's kind a like giving a Megabyte the abbreviation of MiB when It always has been Mb as there is no "i" in Megabyte, But then Megabyte is a term that was invented in the USA, not elsewhere.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

... It's kind a like giving a Megabyte the abbreviation of MiB when It always has been Mb as there is no "i" in Megabyte, But then Megabyte is a term that was invented in the USA, not elsewhere.

I take it that you do know the difference between MByte (base 10) as abused by Sales People, and the very different binary MiByte?

Also, Mb = Mbit! (x8 smaller than MB.)

And the other good cockup is mhz instead of MHz (milli-somethings instead of Mega Hertz)...

Shame the Marketing types are so hopelessly uneducated for anything other than falsely hyping up whatever "object" is to be flogged...

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

FYI, the new x86-64 Linux client, version 5.8.11, can be found at boinc_5.8.11_x86_64-pc-linux-gnu.tgz. Again, the x64 Windows client, version 5.4.11, by Crunch3r, at boinc_5.4.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

---

... It's kind a like giving a Megabyte the abbreviation of MiB when It always has been Mb as there is no "i" in Megabyte, But then Megabyte is a term that was invented in the USA, not elsewhere.

I take it that you do know the difference between MByte (base 10) as abused by Sales People, and the very different binary MiByte?

Also, Mb = Mbit! (x8 smaller than MB.)

And the other good cockup is mhz instead of MHz (milli-somethings instead of Mega Hertz)...

Shame the Marketing types are so hopelessly uneducated for anything other than falsely hyping up whatever "object" is to be flogged...

Happy crunchin',
Martin

I was not talking about Mbit at all, When I started out We didn't have the term Mbit. I was talking about as I spelled It out as Megabyte, I never even mentioned MHz once. Now back then I think It was spelled Mb, I just looked It up and It is now MB. So your right on that, On the rest MiB is not a Megabyte at all It's a mebi-byte whatever that is, Must be a "mebi It is a byte", But I won't use It. A Megabyte is a Megabyte and there is No i in "Megabyte", Never has been.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I take it that you do know the difference between MByte (base 10) as abused by Sales People, and the very different binary MiByte?

I was not talking about Mbit at all, When I started out We didn't have the term Mbit. I was talking about as I spelled It out as Megabyte, I never even mentioned MHz once. Now back then I think It was spelled Mb, I just looked It up and It is now MB. So your right on that, On the rest MiB is not a Megabyte at all It's a mebi-byte whatever that is, Must be a "mebi It is a byte", But I won't use It. A Megabyte is a Megabyte and there is No i in "Megabyte", Never has been.

So I take it then that you do not appreciate the difference between "Mega" as used in base 10 (decimal) compared to that used in base 2 (binary).

Marketing people love to push the decimal version. Computer people use the binary version. There is an inconveniently BIG difference.

Look again?

Maybe it didn't matter in the days when 640kBytes was unimaginable...

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

I take it that you do know the difference between MByte (base 10) as abused by Sales People, and the very different binary MiByte?

I was not talking about Mbit at all, When I started out We didn't have the term Mbit. I was talking about as I spelled It out as Megabyte, I never even mentioned MHz once. Now back then I think It was spelled Mb, I just looked It up and It is now MB. So your right on that, On the rest MiB is not a Megabyte at all It's a mebi-byte whatever that is, Must be a "mebi It is a byte", But I won't use It. A Megabyte is a Megabyte and there is No i in "Megabyte", Never has been.

So I take it then that you do not appreciate the difference between "Mega" as used in base 10 (decimal) compared to that used in base 2 (binary).

Marketing people love to push the decimal version. Computer people use the binary version. There is an inconveniently BIG difference.

Look again?

Maybe it didn't matter in the days when 640kBytes was unimaginable...

Happy crunchin',
Martin

Yes I do know the difference, I've been using computers since 1980(Atari 400 w/a 410 drive) and the computers maximum memory was 64kB, Not KiB, MiB, etc junk. :p
I just support the traditional words and their abreviations not the IEC, IEEE, EU junk(I don't have anything against the EU or anyone in It, But "i" does not belong for the most part where It's been put). As an example I have in My 4 existing PCs a total of 7 Gigabytes or ram and parts for a 5th PC with 2 more Gigabytes, Not something else.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Yes I do know the difference, I've been using computers since 1980(Atari 400 w/a 410 drive) and the computers maximum memory was 64kB, Not KiB, MiB, etc junk. :p
I just support the traditional words and their abreviations not the IEC, IEEE, EU junk...

I agree.

Unfortunately, the Marketing shallow ploy for "bigger numbers" has poisoned the naming scheme for all.

Hence, the bastardised form of the original units have been abandoned to the Marketing people and their base 10 scams.

Engineers and programmers for whom the difference is important have a new recommended standard that explicitly highlights the binary difference.

I'll agree the "Mi", "ki", etc looks ugly, but it is a necessary evil to ward off the even greater evil of Marketing foisted confusion.

There have been many disasters due to confusion over what units were being used...

Happy crunchin',
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)

....I've been using computers since 1980(Atari 400 w/a 410 drive) and the computers maximum memory was 64kB....

Good grief, someone else who remembers the venerable old Atari!

My first "real" computer was the Atari 400 too, although I replaced the 410 with an 810 at the earliest opportunity. Prior to that I'd used a couple of kit built Sinclair ZX80 and ZX81s....less said about those pieces of junk the better. :-(

Still have all of my old Atari 8-bit machines, around 6 or 7 of them....I wonder how long it would take to crunch a SETI WU on a 1.79MHz 6502...? ;-)


TTFN - Pete.

---

....I've been using computers since 1980(Atari 400 w/a 410 drive) and the computers maximum memory was 64kB....

Good grief, someone else who remembers the venerable old Atari!

My first "real" computer was the Atari 400 too, although I replaced the 410 with an 810 at the earliest opportunity. Prior to that I'd used a couple of kit built Sinclair ZX80 and ZX81s....less said about those pieces of junk the better. :-(

Still have all of my old Atari 8-bit machines, around 6 or 7 of them....I wonder how long it would take to crunch a SETI WU on a 1.79MHz 6502...? ;-)


TTFN - Pete.

Probably 3-6 months, Don't know really The App would have to run all by Itself in 48k of ram and send It off to Seti(If One had the ethernet hardware, If It exists or figure out some other way to do It). To do It quick would require assembler or Machine Language for the 6502c cpu and quick as You and I know is a relative term, But It would If It were successful be the slowest Seti cruncher of all time I'd think, But alas It won't happen of course. ;) Oh and for those out there that wonder Why I said 48k instead of 64k, It's cause the entire OS took up all of 16k total.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

Oh and for those out there that wonder Why I said 48k instead of 64k, It's cause the entire OS took up all of 16k total.

Batman,

You are correct about the Atari 800...with normal hardware. ;) There were add on boards that had bank selectable RAM (usually used as a RAM drive). They had up to 128K (if I recall right) selectable in "windows" of 8K at a time. If you were rich you could buy a Corvus hard drive with a whopping 5 Megabytes of disk storage !!! The Corvus connected to the Atari by using 2 cables plugged into the front joystick ports.

The commodore 64, on the other hand, really did have 64K of RAM. The firmware/OS required 16K but it was bank selectable with the underlying 16K of RAM. I used to optimize that also with fast floppy drive transfer routines :=P

Oh and for those out there that wonder Why I said 48k instead of 64k, It's cause the entire OS took up all of 16k total.

Batman,

You are correct about the Atari 800...with normal hardware. ;) There were add on boards that had bank selectable RAM (usually used as a RAM drive). They had up to 128K (if I recall right) selectable in "windows" of 8K at a time. If you were rich you could buy a Corvus hard drive with a whopping 5 Megabytes of disk storage !!! The Corvus connected to the Atari by using 2 cables plugged into the front joystick ports.

The commodore 64, on the other hand, really did have 64K of RAM. The firmware/OS required 16K but it was bank selectable with the underlying 16K of RAM. I used to optimize that also with fast floppy drive transfer routines :=P

The 800XL could also do the full 64k, plus It had a pbi bus on the back(direct link to the 6502c cpu really) and I had an ICD MIO Board(with a case & psu brick) that could use a scsi drive or a suitable mfm drive with an mfm to scsi adapter(adaptec 4000), It could also had a paralell printer port and a real rs-232c port too, Can't remember what the device was called, But It was good enough for running a BBS off It. :D
I also ran across a rare 1400XL motherboard and put It in a modified 1200XL case with yep a 1200XL keyboard and psu, It worked too, The case was modified as the It didn't have a place for the pbi bus. Sold It a long time back, Wish I'd kept It though.

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I had a Comodore PET which had a Motorolla 1MHz 6502 8-bit processor, basically the same setup as the early Apple computers. The O/S was a version of Microsoft BASIC that lived in a ROM on the motherboard. On the PET, the O/S kept 32KB of the RAM and you got the other 32KB. Oh,and it came with a 40-column, green phosphor monitor built into the top. I also wish I hadn't sold it . . .

Brock

---

The new x64 Windows client, version 5.8.11, by Crunch3r, can be found at boinc_5.8.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

---

An updated x86-64 Linux client, version 5.8.15, can be downloaded from boinc_5.8.15_x86_64-pc-linux-gnu.tgz (make sure to read the file "README.x86_64-pc-linux-gnu" in it).

Crunch3r's x64 Windows client, version 5.8.11, can be found at boinc_5.8.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

---

Here's the new recommended version for the x86-64 Linux client:

• Untar the file boinc_5.8.17_x86_64-pc-linux-gnu.tgz at the BOINC working directory.
  
• Read the file "README.x86_64-pc-linux-gnu".
  

Again, Crunch3r's x64 Windows client can be found at boinc_5.8.11_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

---

Here's the new recommended version for the x86-64 Linux client:

• Untar the file boinc_5.8.17_x86_64-pc-linux-gnu.tgz at the BOINC working directory.
  
• Read the file "README.x86_64-pc-linux-gnu".
  

Crunch3r's x64 Windows client can be found at boinc_5.8.16_windows_amd64.zip.

For more information, see BoincStats Forum.

HTH

;)

---

Join BOINC United now!

is there an seti client that supports SSE 3 but for AMD?

---

is there an seti client that supports SSE 3 but for AMD?

Yes. There are SSE3 apps and even 64 bit seti APPLICATIONS (that's what you mean) and those are ...reportedly on INTEL EM64T capable cpus are 10 to 15 % faster than 32 bit optimized ones AND there are some 64 bit apps. "MODIFIED" with another software that i won't mention here...

Those are tested on AMD opterons and are 20% faster than 32 bit optimized apps....


HTH

---

Join BOINC United now!

Yes. There are SSE3 apps and even 64 bit seti APPLICATIONS (that's what you mean) and those are ...reportedly on INTEL EM64T capable cpus are 10 to 15 % faster than 32 bit optimized ones AND there are some 64 bit apps. "MODIFIED" with another software that i won't mention here...

Those are tested on AMD opterons and are 20% faster than 32 bit optimized apps....

What about 64 bit linux apps?

mic.

---

mic.

Yes. There are SSE3 apps and even 64 bit seti APPLICATIONS (that's what you mean) and those are ...reportedly on INTEL EM64T capable cpus are 10 to 15 % faster than 32 bit optimized ones AND there are some 64 bit apps. "MODIFIED" with another software that i won't mention here...

Those are tested on AMD opterons and are 20% faster than 32 bit optimized apps....

What about 64 bit linux apps?

mic.

Those are for linux ;) i'm having a look at windows at this weekend... if there's no party ahead :D

---

Join BOINC United now!