32 and 64 bits
-
hi everybody! i was asking this question in "general" forum, but got no replays... ---- i've got an opportunity to upgrade my system to amd 64 3200+. it's preaty cheap and it would be stupid to miss it, but... i do developing under windows and linux and MOST clients of mine are the users of 32-bit architecture. in the specs of the cpu i found misterious phrase "supports both simulteniously 32 and 64 arc's" huh? so, my dilema is - miss or not miss good chance for the upgrade. What are the issues will i face after upgrade to 64 (with regard to developing under win .NET studio)? What are the consiquences for my end-users? I mean only windows users, if they have win2k (just for example!) and 32-bit cpu (pIII), and they try to run a binary that was built on my winXPpro 64-bit cpu, will they have problems? please, share your opinion and experience, i really need it! thanx alex debug - is my life style
-
hi everybody! i was asking this question in "general" forum, but got no replays... ---- i've got an opportunity to upgrade my system to amd 64 3200+. it's preaty cheap and it would be stupid to miss it, but... i do developing under windows and linux and MOST clients of mine are the users of 32-bit architecture. in the specs of the cpu i found misterious phrase "supports both simulteniously 32 and 64 arc's" huh? so, my dilema is - miss or not miss good chance for the upgrade. What are the issues will i face after upgrade to 64 (with regard to developing under win .NET studio)? What are the consiquences for my end-users? I mean only windows users, if they have win2k (just for example!) and 32-bit cpu (pIII), and they try to run a binary that was built on my winXPpro 64-bit cpu, will they have problems? please, share your opinion and experience, i really need it! thanx alex debug - is my life style
It's been a while since I read my A+ book so forgive me if i'm wrong. I believe 32 and 64 bit arc's are usually determined by the following factors: 1) Register size 2) Number of bits computer can transer per MOV instruction...your bus bandwidth I guess :-O Anyways, most computers now are 32 bit because the internal registers are all 32 bit with I believe the exception of a few floating point registers which are 48 or 128 or something... So you shouldn't have any backwards incompatiability issues when developing on a 64 bit arc becuz so long as your compiler compiles using common 32 bit instruction set it should run on your 64 bit machine or my 32 bit one. Kind of like how I could use 16 bit MOV instruction on my computer, but I could only move 16 bits at a time, whereas I could also use a 32 bit MOV instruction, but now be able to move 32 bits. .NET uses an intermediate language...I can't remember what it's called... IL maybe...? Anyways...the .NET interpreter would determine which actual instruction to send the processor (I believe thats the idea behind .NET) so you shouldn't get any exception becuz of a bad instruction when you compile apps using .NET. Cheers :) The word of the day is legs, let's go back to my house and spread the word ;P
-
It's been a while since I read my A+ book so forgive me if i'm wrong. I believe 32 and 64 bit arc's are usually determined by the following factors: 1) Register size 2) Number of bits computer can transer per MOV instruction...your bus bandwidth I guess :-O Anyways, most computers now are 32 bit because the internal registers are all 32 bit with I believe the exception of a few floating point registers which are 48 or 128 or something... So you shouldn't have any backwards incompatiability issues when developing on a 64 bit arc becuz so long as your compiler compiles using common 32 bit instruction set it should run on your 64 bit machine or my 32 bit one. Kind of like how I could use 16 bit MOV instruction on my computer, but I could only move 16 bits at a time, whereas I could also use a 32 bit MOV instruction, but now be able to move 32 bits. .NET uses an intermediate language...I can't remember what it's called... IL maybe...? Anyways...the .NET interpreter would determine which actual instruction to send the processor (I believe thats the idea behind .NET) so you shouldn't get any exception becuz of a bad instruction when you compile apps using .NET. Cheers :) The word of the day is legs, let's go back to my house and spread the word ;P
right, thanx :) the scenario you've gave requires .NET being installed on the user's computer. or not? debug - is my life style
-
right, thanx :) the scenario you've gave requires .NET being installed on the user's computer. or not? debug - is my life style
If you write an app in .NET and give it to somebody on a Windows 98 machine, I believe they would have to download the .NET framework in order to run you apps on their machine. I remember having to download the win32 SDK on win 3.1 back in the day inorder to run some neat program, I don't image this situation is much different. Cheers :) The word of the day is legs, let's go back to my house and spread the word ;P