Now that the AMD64 platform is somehow supported, would you consider supporting windows_amd64 similarly?

Thanks.

---

Unlikely as there are no benefits to writing a specifically 64bit programme. AFAIK the current 32bit version runs under most of the presently available 64bit OSes without problems.

---

Grant
Darwin NT

Now that the AMD64 platform is somehow supported, would you consider supporting windows_amd64 similarly?

HashClash now supports AMD64 on Windows with a 32-bit application...

---

In the past I've run the BOINC client without problems on Windows 64 and 64-Vista using the existing clients. I don't know that a specific XP 64 (waste of time there), or Vista 64 client makes that much sense.

The existing clients also seem to play well with the true dual CPU processors (both AMD and Intel).

Now that the AMD64 platform is somehow supported, would you consider supporting windows_amd64 similarly?

Thanks.

---

FWIW, running two instances of the client, one the 32-bit client, the other, the 64-bit client, on the same 4-core system, but limiting each client to 2 cores, I can compare the relative performance of 32-bit and 64-bit SIMAP's HMMER: the 64-bit version is about 7% faster.

By enabling vectorization (supported by default on AMD64), the SIMAP developers observed other 8% improvement.

Bottom line: porting the project application to AMD64 has the potential to improve performance by 15%!

---

FWIW, running two instances of the client, one the 32-bit client, the other, the 64-bit client, on the same 4-core system, but limiting each client to 2 cores, I can compare the relative performance of 32-bit and 64-bit SIMAP's HMMER: the 64-bit version is about 7% faster.

By enabling vectorization (supported by default on AMD64), the SIMAP developers observed other 8% improvement.

Bottom line: porting the project application to AMD64 has the potential to improve performance by 15%!

just for Info, where you get the 64 Bit Version of Simap Hmmer

this will be interestink....

Greetings from Germany NRW
Ulli

In the past I've run the BOINC client without problems on Windows 64 and 64-Vista using the existing clients. I don't know that a specific XP 64 (waste of time there), or Vista 64 client makes that much sense.

It does in some cases.

The existing clients also seem to play well with the true dual CPU processors (both AMD and Intel).

It does but why running the client & app. in WOW64 emulation if one can get a native 64 bit boinc and s@h application ?!?

---

Join BOINC United now!

just for Info, where you get the 64 Bit Version of Simap Hmmer

this will be interestink....

All one has to do is to run the AMD64 BOINC client and it'll be automatically downloaded (see this).

HTH

---

just for Info, where you get the 64 Bit Version of Simap Hmmer

this will be interestink....

All one has to do is to run the AMD64 BOINC client and it'll be automatically downloaded (see this).

HTH

If You like Linux, I like Windows XP x64 and agree with Crunch3r on this. As any new crunchers will use XP x64 only.

---

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

If You like Linux, I like Windows XP x64 and agree with Crunch3r on this. As any new crunchers will use XP x64 only.

That's why I've suggested the support of the windows_amd64 platform as well.

---

If You like Linux, I like Windows XP x64 and agree with Crunch3r on this. As any new crunchers will use XP x64 only.

That's why I've suggested the support of the windows_amd64 platform as well.

I don't see a need for a "windows_amd64 platform". I do run a native 64 bit boinc and seti application on WinXP64 and it works well.

---

Join BOINC United now!

If You like Linux, I like Windows XP x64 and agree with Crunch3r on this. As any new crunchers will use XP x64 only.

That's why I've suggested the support of the windows_amd64 platform as well.

I think You are confused slightly, I'm talking about the OS, You sound like You're talking about the cpu which I'm not.

---

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

I think You are confused slightly, I'm talking about the OS, You sound like You're talking about the cpu which I'm not.

No, I'm talking about the OS, Windows x64 whose BOINC platform is windows_amd64, much like the BOINC platform for Windows x86 is windows_intelx86.

HTH

---

I don't see a need for a "windows_amd64 platform". I do run a native 64 bit boinc and seti application on WinXP64 and it works well.

If all you run is SETI or you don't mind messing with app_info.xml files, then it's for you.

Given that AMD64 systems running a 64-bit OS is far more common than Solaris/SPARC or Mac/x86, I don't understand why the BOINC community is dragging its feet supporting AMD64...

Ever since I started suggesting the support of AMD64, 3 projects have decided to support it, one of them in full production status.

I apologize for being such a nag, but it makes sense and it's about time.

---

I think You are confused slightly, I'm talking about the OS, You sound like You're talking about the cpu which I'm not.

No, I'm talking about the OS, Windows x64 whose BOINC platform is windows_amd64, much like the BOINC platform for Windows x86 is windows_intelx86.

HTH

Then please start calling the OS XP x64, As that is what the OS is called, is known by and as It's entitled by MS, As You're slightly confusing two different terms, as AMD64 is used by Linux distros and by AMD, Not by Microsoft or Its Windows XP x64 OS...

XP x64 does of course run on the AMD64 and EM64T cpus/chipsets.

---

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

Then please start calling the OS XP x64, As that is what the OS is called, is known by and as It's entitled by MS, As You're slightly confusing two different terms, as AMD64 is used by Linux distros and by AMD, Not by Microsoft or Its Windows XP x64 OS...

That's the name of the ISA and as I'm advocating support for this ISA on several OS'es, I prefer to continue using AMD64 meaning all AMD64 OS'es.

Thanks.

---

Then please start calling the OS XP x64, As that is what the OS is called, is known by and as It's entitled by MS, As You're slightly confusing two different terms, as AMD64 is used by Linux distros and by AMD, Not by Microsoft or Its Windows XP x64 OS...

That's the name of the ISA and as I'm advocating support for this ISA on several OS'es, I prefer to continue using AMD64 meaning all AMD64 OS'es.

Thanks.

Well according to Microsoft(Who owns the Legal Copyright to the OS, There is no such OS as "Windows AMD64", Just "Windows XP Professional x64" as It says on the plastic box that holds My OEM CD(White print on a Blue background with a Green start button in the lower left hand corner). The XP x64 OS runs on more than just AMD64 type cpus, It also runs on EM64T Intel cpus/chipsets, Such as the Conroe, woodcrest cpus(there might be a few more cpu types) and the i975X and the iP965 chipsets(775) and of course the 771 chipsets for the woodcrest type cpus(there might be a few more chipsets too). So far It's just an AMD and Intel club, Unless Via or someone else has a 64 bit cpu.

ISA?

---

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

If there should be a platform added due to win xp64 it should be called (the application for example)
windows_intelx86_64 and nothing else.

---

Join BOINC United now!

If there should be a platform added due to win xp64 it should be called (the application for example)
windows_intelx86_64 and nothing else.

Sorry, it is already defined as windows_amd64 by other projects.

---

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.

---