is there any plans for a 64bit client for windows tryed to recompile for 64bit it did'nt work lol

---

http://www.boincstats.com/signature/user_602797.gif

is there any plans for a 64bit client for windows tryed to recompile for 64bit it did'nt work lol

NO, the 64 bit chips from AMD do NOT have the part that Boinc uses running at 64 bits, it is still at 32 bits. Just run the optimized 32 bit chip for your OS and you will out perform most of us by a small amount.

---

is there any plans for a 64bit client for windows tryed to recompile for 64bit it did'nt work lol

NO, the 64 bit chips from AMD do NOT have the part that Boinc uses running at 64 bits, it is still at 32 bits. Just run the optimized 32 bit chip for your OS and you will out perform most of us by a small amount.

Okay, I'm confused. There is an optimized version for 64 bit Linux users, but Boinc can't be compiled in 64 bit for Windows? That's the part that doesn't make sense to me.

Everyone that is running Windows XP Professional x64 has to run Boinc in WoW which adds additional overhead to run the program.

It seems ridiculous to me that after eight months of Windows XP Professional x64 has been RTM (released-to-market) that a 64 bit version isn't available. It can't be that difficult for someone that knows how to compile code to do it. I did a quick search on Google last night on compiling 64 bit code in Windows, and someone had listed step-by-step instructions on how to do it using VB6. If I had VB6 and had an understanding of compiling code, I would have done it myself.

I am sure if there was a new flavor of Linux, someone would have one compiled for that new flavor much more quickly than eight months.

I would just like to run Boinc without WoW so that the resources can be used not to emulate 32 bits, but for actual crunching.

Torrey Lauer

---

I could do it... alot of us could.

However we have to purchase a licensed copy the C++ compiler, this costs money. No one wants to compile it with an unregistered compiler and have 200,000 users look at it. Piracy hounds would be all over you.

---

Overclock with the MSI G31M3-L and Intel E8600 3.33Ghz
Intel D865GLC Socket 478 Motherboard
~How To Overclock The Eee ASUS 1005HA Netbook To 1.9Ghz~

Just give us a little time.
Soon enough there will be a 64 bit S@H app. (S@H enhanced) and maybe BOINC (Trux are you reading this ?).

P.S.

It can't be that difficult for someone that knows how to compile code to do it. I did a quick search on Google last night on compiling 64 bit code in Windows, and someone had listed step-by-step instructions on how to do it using VB6. If I had VB6 and had an understanding of compiling code, I would have done it myself.

We need a c++ compiler and not VB ( Visual Basic)
Besides Win64 code is not compatible with Win32 code, so it's not just like pulling out a 64 bit compiler and recompile the app and you're done. ;)

---

Join BOINC United now!

Just give us a little time.
Soon enough there will be a 64 bit S@H app. (S@H enhanced) and maybe BOINC (Trux are you reading this ?).

P.S.

It can't be that difficult for someone that knows how to compile code to do it. I did a quick search on Google last night on compiling 64 bit code in Windows, and someone had listed step-by-step instructions on how to do it using VB6. If I had VB6 and had an understanding of compiling code, I would have done it myself.

We need a c++ compiler and not VB ( Visual Basic)
Besides Win64 code is not compatible with Win32 code, so it's not just like pulling out a 64 bit compiler and recompile the app and you're done. ;)

Well there is another reason for Me not installing My XP64 CD yet.

---

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

Other than reducing the 64/32 bit "thunk over head", a 64 bit Windows version of the Seti application would not buy you that much. You would have to modify all three parts, BOINC Manager, BOINC and the Seti application. And you would not be able to work other projects unless they put out applications for BOINC-64 bit AMD (which would not officially exist).

The main reason there will be little performance increase, is that 64 bits is about address space and data register size. This has little or no effect on Math processor operations which still have their own unique data and register size. (Not to say just getting rid of the overhead would not be worth the effort if you are trying to do other things with Setiathome running in the background.) But I would not expect a big demand for such a program. Users wanting to switch to 64 bit processing would tend to go with Linux where there is more applications available in 64 bit mode right now, than Windows 64 which could be a dead end product with Vista coming soon.

is there any plans for a 64bit client for windows tryed to recompile for 64bit it did'nt work lol

NO, the 64 bit chips from AMD do NOT have the part that Boinc uses running at 64 bits, it is still at 32 bits. Just run the optimized 32 bit chip for your OS and you will out perform most of us by a small amount.

Okay, I'm confused. There is an optimized version for 64 bit Linux users, but Boinc can't be compiled in 64 bit for Windows? That's the part that doesn't make sense to me.

That is NOT what I said...what I said was that there is not point in it! The AMD 64 bit chip still has parts of it running at 32 bit. THAT is the part that Boinc uses! It makes no sense to compile a 64 bit program if you cannot use it to its full advantage!!!
Some Linux user sat down and did it on his own, are you willing and able to do it for Windows? NEITHER IS ANYONE ELSE!!!
[/quote]

---

is there any plans for a 64bit client for windows tryed to recompile for 64bit it did'nt work lol

NO, the 64 bit chips from AMD do NOT have the part that Boinc uses running at 64 bits, it is still at 32 bits. Just run the optimized 32 bit chip for your OS and you will out perform most of us by a small amount.

You have no idea what you are talking about. There are two issues with going 64bit. First are pointers. You have to change anything that is using a 32bit data type to represent a pointer to a datatype representing a 64bit pointer. Because this requires more memory, this could actually slow down the program. So BOINC could end up slower while all the project specific dll would be much faster.

The second issue is 64bit programs can only use 64bit DLLs. So you might have a 64 bit BOINC with no project software to run.

---

NEITHER IS ANYONE ELSE!!!

THE SKY IS FALLING!

---

me@rescam.org

Other than reducing the 64/32 bit "thunk over head", a 64 bit Windows version of the Seti application would not buy you that much. You would have to modify all three parts, BOINC Manager, BOINC and the Seti application. And you would not be able to work other projects unless they put out applications for BOINC-64 bit AMD (which would not officially exist).

The main reason there will be little performance increase, is that 64 bits is about address space and data register size. This has little or no effect on Math processor operations which still have their own unique data and register size. (Not to say just getting rid of the overhead would not be worth the effort if you are trying to do other things with Setiathome running in the background.) But I would not expect a big demand for such a program. Users wanting to switch to 64 bit processing would tend to go with Linux where there is more applications available in 64 bit mode right now, than Windows 64 which could be a dead end product with Vista coming soon.

Jack, maybe I'm mis-reading your last sentence? Windows x64 is not going to be a dead end product with the upcoming Vista release near the end of this year. Windows Vista will be available for retail purchase (as well as pre-installed from Dell, HP, etc.) in 32 bit AND 64 bit. In fact, in order for ANY software to have the Microsoft Vista Certified sticker on it, it MUST be compatible with BOTH Vista 32 bit AND Vista 64 bit. That is good news for everyone that wants to use a 64 bit version of Windows.

Torrey Lauer

---

Just give us a little time.
Soon enough there will be a 64 bit S@H app. (S@H enhanced) and maybe BOINC (Trux are you reading this ?).

P.S.

It can't be that difficult for someone that knows how to compile code to do it. I did a quick search on Google last night on compiling 64 bit code in Windows, and someone had listed step-by-step instructions on how to do it using VB6. If I had VB6 and had an understanding of compiling code, I would have done it myself.

We need a c++ compiler and not VB ( Visual Basic)
Besides Win64 code is not compatible with Win32 code, so it's not just like pulling out a 64 bit compiler and recompile the app and you're done. ;)




Thanx Cruncher

---

http://www.boincstats.com/signature/user_602797.gif

Just give us a little time.
Soon enough there will be a 64 bit S@H app. (S@H enhanced) and maybe BOINC (Trux are you reading this ?).

P.S.

It can't be that difficult for someone that knows how to compile code to do it. I did a quick search on Google last night on compiling 64 bit code in Windows, and someone had listed step-by-step instructions on how to do it using VB6. If I had VB6 and had an understanding of compiling code, I would have done it myself.

We need a c++ compiler and not VB ( Visual Basic)
Besides Win64 code is not compatible with Win32 code, so it's not just like pulling out a 64 bit compiler and recompile the app and you're done. ;)

In other words a Boinc client and application can't be made that takes a given WU made by Boinc and spit out results that Boinc can handle? Sorry I don't buy that one bit. So a c++ compiler for XP x64 is needed, Have any particular one in mind? I know some ares of the code would possibly need changing(maybe), But I'm not a programmer, I did once learn programming in Basic, I got a B+ too, But It didn't help with anything but My math skills as I still didn't know where to start.

---

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

Quick question. Who actually needs 64 bit processing?

I'm not asking about 64 bit addressing.

---

Quick question. Who actually needs 64 bit processing?

I'm not asking about 64 bit addressing.

I do. Why? Because I can.

---