Laptop recommendation
-
Maxwell Chen wrote:
Four years ago I bought a motherboard with 64-bit AMD Athlon64 3200+ and installed Windows Longhorn 64-bit version (pre-Vista) for some project. I installed WinZip 32-bit and Microsoft Visual Studio 6 on this 64-bit system.
Thanks. What I understand from your reply is: "Yes, we can write applications which would run on 32 bit applications, sitting on a 64 bit OS" I got it right?
Nobody can give you wiser advice than yourself. - Cicero
-
Sorry, WOWEXEC is something different. I was asking if I could write code and compile and build an image which would run on 32 bit windows, if I am working on a VS 2005 (64 bit, if one such thing exists) on a 64 bit OS?
Nobody can give you wiser advice than yourself. - Cicero
-
Paul, sorry, you're wrong on this - the AMD/Intel 'x64' processors run 32-bit code natively even on a 64-bit operating system. The problem with that is that there are still relatively few drivers for the 64-bit OS, although all the hardware in the system will have drivers. You may be confused with the older Itanium IA-64 architecture, which does have 32-bit x86 compatibility in hardware, but the implementation was so poor that later versions of the Itanium version of Windows include a software emulator that JIT-compiles to native Itanium code. There are of course other 64-bit processor families such as Sun Sparc, MIPS, Alpha, PowerPC, and you're right that these do not execute x86 code natively and require emulation. However, they don't run Windows natively either.
Stability. What an interesting concept. -- Chris Maunder
Mike Dimmick wrote:
there are still relatively few drivers for the 64-bit OS
I don't think so. In my experience (I'm running Vista 64) all the drivers I needed were available.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
Sorry, WOWEXEC is something different. I was asking if I could write code and compile and build an image which would run on 32 bit windows, if I am working on a VS 2005 (64 bit, if one such thing exists) on a 64 bit OS?
Nobody can give you wiser advice than yourself. - Cicero
If you compile an application for 32-bit system, it will work on 64-bit systems too. If you compile it for 64-bit, it will work only on 64-bit systems.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
Vasudevan Deepak Kumar wrote:
HP seems to be sleek and light-weighted.
So true. This particular model is under 2 Kilos. It has killer looks :cool:
Nobody can give you wiser advice than yourself. - Cicero
The model I was intending to mention is hp compaq nc4400
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
-
If you compile an application for 32-bit system, it will work on 64-bit systems too. If you compile it for 64-bit, it will work only on 64-bit systems.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
That leaves a question unanswered, still. Where am I compiling the application from? Will I be able to compile an application for 32 bit, sitting on an 64 bit OS? :~ I am clear about the fact that a 32 bit app will run on both 32 and 64 bit OS.
Nobody can give you wiser advice than yourself. - Cicero
-
That leaves a question unanswered, still. Where am I compiling the application from? Will I be able to compile an application for 32 bit, sitting on an 64 bit OS? :~ I am clear about the fact that a 32 bit app will run on both 32 and 64 bit OS.
Nobody can give you wiser advice than yourself. - Cicero
brahmma wrote:
Will I be able to compile an application for 32 bit, sitting on an 64 bit OS?
Yes, of course. BTW, if you're using .NET, you don't have to take care of that stuff.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
The model I was intending to mention is hp compaq nc4400
Vasudevan Deepak Kumar Personal Homepage Tech Gossips
For that reason, all hp laptops are weighing less, when compared to an almost equivalent DELL.
Nobody can give you wiser advice than yourself. - Cicero
-
That leaves a question unanswered, still. Where am I compiling the application from? Will I be able to compile an application for 32 bit, sitting on an 64 bit OS? :~ I am clear about the fact that a 32 bit app will run on both 32 and 64 bit OS.
Nobody can give you wiser advice than yourself. - Cicero
Visual Studio 2005 is still 32-bit and still generates 32-bit code (unless you use the x64 cross-compiler). The Solution Platform drop-down in 2005 gains an 'x64' entry in addition to the 'Win32' option. The 'native' x64 compiler (64-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\amd64, while the cross-compiler (32-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\x86_amd64. .NET Framework 2.0 supports both 32-bit and 64-bit processes on an x64 system. What code loads where depends on how the assemblies are marked. If marked 'MSIL' they are register-width independent, and will load into either width process - if an EXE, it will (I believe) start a 64-bit process. If marked 'x64' it will only load into a 64-bit process. If marked 'x86' it will only load into a 32-bit process and an EXE will start a 32-bit process. By default a new project in VS is marked 'Any CPU' (MSIL) - to add a different configuration, go into the Build/Configuration Manager dialog.
Stability. What an interesting concept. -- Chris Maunder
-
I am looking at hp Pavilion tx1016AU[^], which is a 64 bit tablet pc. It looks like a good buy, but I have a few questions. This one being a 64 bit computer, will I be able to write applications for 32 bit computers sitting on it? I guess there has to be a setting in VS wherein I can specify if I need my app to run on 32 or 64 bit. I have never worked with 64 bit computers and so I do not know this for sure. Is there anything else that you think is bad about this notebook? I cannot think outside HP since my company has a tie-up with them. Moreover, can someone tell me if the AMD processor that it has will be good? :~ Is there an HP alternative that you would suggest? My budget is 85000 INR. Thank you very much.
Nobody can give you wiser advice than yourself. - Cicero
I was looking at one of those in my quest for a performant tablet PC. Its not a 'real' tablet - its an x-y digitizer not a proper wacom tablet with pressure / angle sensitivity. If you haven't used one, trust me you can tell the difference. I ended up getting a high end Tecra M7 (refurbished for about £800), that has pretty good video, 1440x900 display and a 1.66 core 2 duo. If you really want the 64 bits though..
-
brahmma wrote:
Will I be able to compile an application for 32 bit, sitting on an 64 bit OS?
Yes, of course. BTW, if you're using .NET, you don't have to take care of that stuff.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
Dario Solera wrote:
Yes, of course
Thank you very much.
Dario Solera wrote:
BTW, if you're using .NET, you don't have to take care of that stuff.
How? Any link or a pointer? That must be an interesting read. (Anyways, we are using MFC and our next project is going to be on .NET; I can't wait).
Nobody can give you wiser advice than yourself. - Cicero
-
Visual Studio 2005 is still 32-bit and still generates 32-bit code (unless you use the x64 cross-compiler). The Solution Platform drop-down in 2005 gains an 'x64' entry in addition to the 'Win32' option. The 'native' x64 compiler (64-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\amd64, while the cross-compiler (32-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\x86_amd64. .NET Framework 2.0 supports both 32-bit and 64-bit processes on an x64 system. What code loads where depends on how the assemblies are marked. If marked 'MSIL' they are register-width independent, and will load into either width process - if an EXE, it will (I believe) start a 64-bit process. If marked 'x64' it will only load into a 64-bit process. If marked 'x86' it will only load into a 32-bit process and an EXE will start a 32-bit process. By default a new project in VS is marked 'Any CPU' (MSIL) - to add a different configuration, go into the Build/Configuration Manager dialog.
Stability. What an interesting concept. -- Chris Maunder
Quite informative. Thank you very much.
Nobody can give you wiser advice than yourself. - Cicero
-
Visual Studio 2005 is still 32-bit and still generates 32-bit code (unless you use the x64 cross-compiler). The Solution Platform drop-down in 2005 gains an 'x64' entry in addition to the 'Win32' option. The 'native' x64 compiler (64-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\amd64, while the cross-compiler (32-bit compiler generating 64-bit code) lives in C:\Program Files\Microsoft Visual Studio 8\VC\bin\x86_amd64. .NET Framework 2.0 supports both 32-bit and 64-bit processes on an x64 system. What code loads where depends on how the assemblies are marked. If marked 'MSIL' they are register-width independent, and will load into either width process - if an EXE, it will (I believe) start a 64-bit process. If marked 'x64' it will only load into a 64-bit process. If marked 'x86' it will only load into a 32-bit process and an EXE will start a 32-bit process. By default a new project in VS is marked 'Any CPU' (MSIL) - to add a different configuration, go into the Build/Configuration Manager dialog.
Stability. What an interesting concept. -- Chris Maunder
-
Dario Solera wrote:
Yes, of course
Thank you very much.
Dario Solera wrote:
BTW, if you're using .NET, you don't have to take care of that stuff.
How? Any link or a pointer? That must be an interesting read. (Anyways, we are using MFC and our next project is going to be on .NET; I can't wait).
Nobody can give you wiser advice than yourself. - Cicero
brahmma wrote:
How?
It's just that .NET compiles to IL (Intermediate Language) which is JIT-compiled to native code on the target machine running the proper version of the .NET runtime. This way you don't have to take care of the target operating system, you just write your application. The nice thing of this structure is that (theoretically), your application runs as fast as possible on the target hardware (and OS), regardless of the configuration of the development machine.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
I was looking at one of those in my quest for a performant tablet PC. Its not a 'real' tablet - its an x-y digitizer not a proper wacom tablet with pressure / angle sensitivity. If you haven't used one, trust me you can tell the difference. I ended up getting a high end Tecra M7 (refurbished for about £800), that has pretty good video, 1440x900 display and a 1.66 core 2 duo. If you really want the 64 bits though..
I was not looking for a 'real' tablet. The device has tablet capabilities too and that makes me glad. :) I will be happy if it could perform as a 'real' notebook.
Nobody can give you wiser advice than yourself. - Cicero
-
brahmma wrote:
How?
It's just that .NET compiles to IL (Intermediate Language) which is JIT-compiled to native code on the target machine running the proper version of the .NET runtime. This way you don't have to take care of the target operating system, you just write your application. The nice thing of this structure is that (theoretically), your application runs as fast as possible on the target hardware (and OS), regardless of the configuration of the development machine.
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
I've done reading on the IL and JIT compilation, but I never knew it takes care of 32bit and 64 bit OS too. :omg:
Nobody can give you wiser advice than yourself. - Cicero
-
I've done reading on the IL and JIT compilation, but I never knew it takes care of 32bit and 64 bit OS too. :omg:
Nobody can give you wiser advice than yourself. - Cicero
brahmma wrote:
I never knew it takes care of 32bit and 64 bit OS too.
It's nice, isn't it? :-D
If you truly believe you need to pick a mobile phone that "says something" about your personality, don't bother. You don't have a personality. A mental illness, maybe - but not a personality. - Charlie Brooker My Blog - My Photos - ScrewTurn Wiki
-
I am looking at hp Pavilion tx1016AU[^], which is a 64 bit tablet pc. It looks like a good buy, but I have a few questions. This one being a 64 bit computer, will I be able to write applications for 32 bit computers sitting on it? I guess there has to be a setting in VS wherein I can specify if I need my app to run on 32 or 64 bit. I have never worked with 64 bit computers and so I do not know this for sure. Is there anything else that you think is bad about this notebook? I cannot think outside HP since my company has a tie-up with them. Moreover, can someone tell me if the AMD processor that it has will be good? :~ Is there an HP alternative that you would suggest? My budget is 85000 INR. Thank you very much.
Nobody can give you wiser advice than yourself. - Cicero
have you considered HP's dv9330us or dv9339us they come loaded with 2 GB RAM and 160 HDD, NVidia and wot not and still cost less than 1500 USD...
-
Mine was/is the most crash prone and poorly put together notebook I have ever owned.
Christian Graus - Microsoft MVP - C++ Metal Musings - Rex and my new metal blog "I am working on a project that will convert a FORTRAN code to corresponding C++ code.I am not aware of FORTRAN syntax" ( spotted in the C++/CLI forum )
HP install a bunch of crud software by defaulkt but the hardware istelf isn't so bad. My recommenddation if you do get an HP is spend half a day uninstalling all the "free" programs they give you. That said, my current dev machine is an Asus Aspire. Sparkly fashion statements and labels aside it is a very capable machine at a very competitive price.
'--8<------------------------ Ex Datis: Duncan Jones Merrion Computing Ltd
-
Paul, sorry, you're wrong on this - the AMD/Intel 'x64' processors run 32-bit code natively even on a 64-bit operating system. The problem with that is that there are still relatively few drivers for the 64-bit OS, although all the hardware in the system will have drivers. You may be confused with the older Itanium IA-64 architecture, which does have 32-bit x86 compatibility in hardware, but the implementation was so poor that later versions of the Itanium version of Windows include a software emulator that JIT-compiles to native Itanium code. There are of course other 64-bit processor families such as Sun Sparc, MIPS, Alpha, PowerPC, and you're right that these do not execute x86 code natively and require emulation. However, they don't run Windows natively either.
Stability. What an interesting concept. -- Chris Maunder
Thanks for the information. I need not know of the architecture change from the IA-64, and my other experience was with the 64 bit Alpha. Best regards, Paul.
Jesus Christ is LOVE! Please tell somebody.