Brave new world
-
As you may recall, I moved to Windows 7 64 bit last week. I am finally done with support and web dev tasks, and working on our main app again. It's amazing, I've built the app at least 15 times, because I am doing fiddly UI work. I actually got the preview working in VS, which is amazing enough, but in the past, the app never built more than twice without having to close VS and reopen it. Looks like VS is able to find the extra RAM in 64 bit and use it, so that's just awesome. This would have been SO slow under XP 32 bit....
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Ok, who hacked CG's account? :)
I was HollyHooo but got tired of it and Sebastien was taken.
-
As you may recall, I moved to Windows 7 64 bit last week. I am finally done with support and web dev tasks, and working on our main app again. It's amazing, I've built the app at least 15 times, because I am doing fiddly UI work. I actually got the preview working in VS, which is amazing enough, but in the past, the app never built more than twice without having to close VS and reopen it. Looks like VS is able to find the extra RAM in 64 bit and use it, so that's just awesome. This would have been SO slow under XP 32 bit....
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
OK, Christian seems to be delirious. Try some cold compresses and perhaps the fever will subside.
CQ de W5ALT
Walt Fair, Jr., P. E. Comport Computing Specializing in Technical Engineering Software
-
As you may recall, I moved to Windows 7 64 bit last week. I am finally done with support and web dev tasks, and working on our main app again. It's amazing, I've built the app at least 15 times, because I am doing fiddly UI work. I actually got the preview working in VS, which is amazing enough, but in the past, the app never built more than twice without having to close VS and reopen it. Looks like VS is able to find the extra RAM in 64 bit and use it, so that's just awesome. This would have been SO slow under XP 32 bit....
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
Good for you. :) I remeber reading sometime back that there is no 64-bit version for VS. Hence, I am not able to understand the extra RAM thing. Of course if you were running your 32-bit computer on 1 GB RAM, it's a differnt story.
"The worst code you'll come across is code you wrote last year.", wizardzz[^]
-
As you may recall, I moved to Windows 7 64 bit last week. I am finally done with support and web dev tasks, and working on our main app again. It's amazing, I've built the app at least 15 times, because I am doing fiddly UI work. I actually got the preview working in VS, which is amazing enough, but in the past, the app never built more than twice without having to close VS and reopen it. Looks like VS is able to find the extra RAM in 64 bit and use it, so that's just awesome. This would have been SO slow under XP 32 bit....
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
somehow you managed to get rid of the spell that has haunted you for years; seems like gavindon[^] now has it. :thumbsup:
Luc Pattyn [My Articles] Nil Volentibus Arduum
-
Good for you. :) I remeber reading sometime back that there is no 64-bit version for VS. Hence, I am not able to understand the extra RAM thing. Of course if you were running your 32-bit computer on 1 GB RAM, it's a differnt story.
"The worst code you'll come across is code you wrote last year.", wizardzz[^]
Nish said that some of the processes that the IDE spawns, have a 64 bit version, so I guess it installs both and runs as needed. It's the build process that was my issue, so that explains why it works.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Nish said that some of the processes that the IDE spawns, have a 64 bit version, so I guess it installs both and runs as needed. It's the build process that was my issue, so that explains why it works.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
So MSBuild has a 64 bit version in it? That's nice. :) :thumbsup:
My Blog My Achievements: * Posted 25,000th message in GIT O_O * Official supporter of the "thatraja's GIT Meet Sponsor Foundation" :D What you do, when you don't know what to do is what you do when you don't want to do what you do.
-
Nish said that some of the processes that the IDE spawns, have a 64 bit version, so I guess it installs both and runs as needed. It's the build process that was my issue, so that explains why it works.
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
-
Good for you. :) I remeber reading sometime back that there is no 64-bit version for VS. Hence, I am not able to understand the extra RAM thing. Of course if you were running your 32-bit computer on 1 GB RAM, it's a differnt story.
"The worst code you'll come across is code you wrote last year.", wizardzz[^]
d@nish wrote:
Hence, I am not able to understand the extra RAM thing.
The OS (64 bit) would be able to use all the RAM, and 32 bit processes also get the full 4 GB of virtual address space to themselves (would have been only 2 - 3 GB on a 32 bit OS). Both should help memory hungry applications run faster.
Regards Senthil _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
As you may recall, I moved to Windows 7 64 bit last week. I am finally done with support and web dev tasks, and working on our main app again. It's amazing, I've built the app at least 15 times, because I am doing fiddly UI work. I actually got the preview working in VS, which is amazing enough, but in the past, the app never built more than twice without having to close VS and reopen it. Looks like VS is able to find the extra RAM in 64 bit and use it, so that's just awesome. This would have been SO slow under XP 32 bit....
Christian Graus Driven to the arms of OSX by Vista. Read my blog to find out how I've worked around bugs in Microsoft tools and frameworks.
You mean you've found something you like? Wow: that really is news! :-)
"If you think it's expensive to hire a professional to do the job, wait until you hire an amateur." Red Adair. nils illegitimus carborundum me, me, me
-
d@nish wrote:
Hence, I am not able to understand the extra RAM thing.
The OS (64 bit) would be able to use all the RAM, and 32 bit processes also get the full 4 GB of virtual address space to themselves (would have been only 2 - 3 GB on a 32 bit OS). Both should help memory hungry applications run faster.
Regards Senthil _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
32 bit processes *can* get a full 4GB (minus a few small reserved areas); but they have to explicitly set a flag saying that they're safe to do so. MS initially tried enabling it by default but too many badly written apps puked (eg using a 32bit signed int for a pointer and setting magic values in the negative range).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
-
32 bit processes *can* get a full 4GB (minus a few small reserved areas); but they have to explicitly set a flag saying that they're safe to do so. MS initially tried enabling it by default but too many badly written apps puked (eg using a 32bit signed int for a pointer and setting magic values in the negative range).
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius
I don't know of any way to get more virtual address space beyond 3 GB for a 32 bit process on a 32 bit OS, and that's with the /3 GB switch enabled (without resorting to "window" based tricks). Raymond[^] also says the same thing.
Regards Senthil _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
-
I don't know of any way to get more virtual address space beyond 3 GB for a 32 bit process on a 32 bit OS, and that's with the /3 GB switch enabled (without resorting to "window" based tricks). Raymond[^] also says the same thing.
Regards Senthil _____________________________ My Home Page |My Blog | My Articles | My Flickr | WinMacro
I guess I was unclear. I meant to say that a 32bit process needs to indicate it can handle unsigned pointers to get access to >2GB of ram when running in 64 bit windows. Programs that aren't marked as such are still limited to 2GB even if running under win64.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius