Solve : windows 7 64-32 bit?

1.	Solve : windows 7 64-32 bit?
Answer» Ok, let me try that again, I should have proof read that thing before I POSTED. If you are running a 64 Bit OS with say 8 Gb of ram, when you switch to a 32 Bit OS, it will only "see" 4 Gb of ram as that is the max for a 32 bit system and use 3.0 Gb to 3.5 Gb. That could very well cause your performance to take a hit.Quote from: coastie65 on August 13, 2010, 02:18:35 PM Ok, let me try that again, I should have proof read that thing before I posted. If you are running a 64 Bit OS with say 8 Gb of ram, when you switch to a 32 Bit OS, it will only "see" 4 Gb of ram as that is the max for a 32 bit system and use 3.0 Gb to 3.5 Gb. That could very well cause your performance to take a hit. 3.5-4GB is not the maximum for a 32-bit system- it's the maximum for Windows XP home and Professional, Vista 32-bit, and Windows 7 32-bit. Windows server 2003 is a 32-bit OS and it can access up to 32GB of memory; same with MANY versions of Linux. the limit is actually an artificial limit built right into windows, it has nothing to do with the underlying architecture. That being said, I see what you mean. I could see it run faster witn a 64-bit version installed but I don't see how "only" having ~3.5GB could cause it to "run slow". On the other hand, kids these days think that 59 frames per second is jerky animation. bloody spoiled brats they are.OK. I am not familiar with server stuff. I was basing it on standard Windows OS's and the poster didn't specify the OS to begin with. That was the basis of my answer. Actually, it was in relation this by John Getter " My brother runs 64-bit version of windows. When he tried 32 bit his system would lag badly on anything he tried to do. So he went back to 64 bit system. So systems that are made to run 64 bit do better " and I assumed at the time he switched to a 32 Bit OS, but in retrospect maybe not and just swtiched to 32 bit IE. Who knows. Anyway as to the original post, as I had said in an earlier post, in Internet Options under the Programs Tab, first block, it says to not use IE 64 bit as the default browser, in both Vista and Win7. I think a lot of sites are not geared up for the 64 bit Browser and won't open if you are using it. Quote as I had said in an earlier post, in Internet Options under the Programs Tab, first block, it says to not use IE 64 bit as the default browser, in both Vista and Win7. I think a lot of sites are not geared up for the 64 bit Browser and won't open if you are using it. The reason it suggests not to use a 64-bit OS is simple- most content plugins don't run on 64-bit. Specifically, of course, Adobe Flash. Since IE 64-bit is a 64-bit application, it can only link to 64-bit DLLs. Therefore, all plugins will need to be 64-bit. Most other plugin vendors have done rather well and have released 64-bit versions. Adobe is the holdout. The flash problem isn't limited to IE 64-bit. Minefield (a 64-bit build of Firefox) cannot run flash either, for the very same REASONS. the dialog states that "IE 64-bit cannot be set as the default browser". This isn't a case of "can't" as much as it is a case of "won't". The reason was an actual conscious decision not to make it possible to set it as the default browser, for the very reasons I noted PREVIOUSLY- that is, lack of support for popular plugins. The only time a site will have trouble is if it uses flash or another unavailable plugin. a website doesn't need to be written specifically for 64-bit. It's fully possible to run 16-bit browsers and still navigate the web fine. after all, it's just a few files and scripts; the bitness of the interpreters of that markup and script is largely redundant. Quote from: http://blogs.msdn.com/b/ieinternals/archive/2009/05/29/q-a-64-bit-internet-explorer.aspx Q: Why isn't 64bit IE the default browser? Why can't I set the 64bit version of IE as the default browser? A: This was an explicit choice made by the IE team, which may change at some point in the future. The problem is that users might inadvertently get "stuck" using the 64bit version and not realize it. This might cause some problems. Q: Why? What does not work properly with 64bit IE? A: Browser addons, including BHOs, Toolbars, and ActiveX controls, must generally be the same bitness as IE itself. So, if you are running a 64bit version of IE, any site that uses, say, Adobe Flash, isn't going to work until you install the 64bit version of the addon. Sadly, almost no browser addons are currently available in 64bit versions, although that's somewhat likely to change in the future as 64bit Windows becomes more prevalent. Q: So, is there any benefit to using 64bit IE? A: Some users like to use 64bit IE from time to time for a variety of reasons, but in my opinion, none of them are super-compelling. Here are a few reasons I've heard: * DEP/NX is always on for 64bit processes. (Of course, on Vista SP1+, 32 bit IE8 has DEP/NX enabled by default too.) * It crashes less. (Because most addons don't load in 64bit IE, it tends to be more reliable.) * It's faster. (Mostly because most addons aren't loaded. There's also an unsubstantiated claim that image decoding is faster, but I find this very unlikely). Q: Okay, so why offer 64bit IE at all? Because we have to. :-) One thing to keep in mind is that Internet Explorer is basically the combination of a number of platform components, including the networking components (URLMon/WinINET), the rendering components (MSHTML), the script engines (JScript.dll, vbscript.dll) and a variety of other pieces that hold it all together. These components must be made available in 64bit versions so that 64bit APPLICATIONS can be built using these components. Additionally, because Internet Explorer can be launched/created/used as a COM Server, we offer a 64bit version to enable hosting inside 64bit processes. While we could have done work to make it harder for users to get to 64bit IE (e.g. by not creating a Start menu shortcut), I don't think there's any super-compelling reason to do so. One day, 64bit IE might see a lot more use, as 64bit systems take over and 64bit add-ons become available. Time will tell. So, the summary is this: the downside of using 64-bit IE is that fewer addons and toolbars and so forth can run. The upside of this is that fewer addons and toolbars and so forth can run. Yup. There are some that do like their add ons though. I prefer to run as few as possible.Quote So, the summary is this: the downside of using 64-bit IE is that fewer addons and toolbars and so forth can run. The upside of this is that fewer addons and toolbars and so forth can run. Shoot, in my case it is a moot point anyway. I have IE 8 in here, but I use Verizon w/ MSN Premium service and it uses a hybrid browser called MSN Explorer.

Answer»

Ok, let me try that again, I should have proof read that thing before I POSTED. If you are running a 64 Bit OS with say 8 Gb of ram, when you switch to a 32 Bit OS, it will only "see" 4 Gb of ram as that is the max for a 32 bit system and use 3.0 Gb to 3.5 Gb. That could very well cause your performance to take a hit.Quote from: coastie65 on August 13, 2010, 02:18:35 PM

Ok, let me try that again, I should have proof read that thing before I posted. If you are running a 64 Bit OS with say 8 Gb of ram, when you switch to a 32 Bit OS, it will only "see" 4 Gb of ram as that is the max for a 32 bit system and use 3.0 Gb to 3.5 Gb. That could very well cause your performance to take a hit.

3.5-4GB is not the maximum for a 32-bit system- it's the maximum for Windows XP home and Professional, Vista 32-bit, and Windows 7 32-bit.

Windows server 2003 is a 32-bit OS and it can access up to 32GB of memory; same with MANY versions of Linux. the limit is actually an artificial limit built right into windows, it has nothing to do with the underlying architecture.

That being said, I see what you mean. I could see it run faster witn a 64-bit version installed but I don't see how "only" having ~3.5GB could cause it to "run slow". On the other hand, kids these days think that 59 frames per second is jerky animation. bloody spoiled brats they are.OK. I am not familiar with server stuff. I was basing it on standard Windows OS's and the poster didn't specify the OS to begin with. That was the basis of my answer. Actually, it was in relation this by John Getter " My brother runs 64-bit version of windows. When he tried 32 bit his system would lag badly on anything he tried to do. So he went back to 64 bit system. So systems that are made to run 64 bit do better " and I assumed at the time he switched to a 32 Bit OS, but in retrospect maybe not and just swtiched to 32 bit IE. Who knows. Anyway as to the original post, as I had said in an earlier post, in Internet Options under the Programs Tab, first block, it says to not use IE 64 bit as the default browser, in both Vista and Win7. I think a lot of sites are not geared up for the 64 bit Browser and won't open if you are using it.
Quote

as I had said in an earlier post, in Internet Options under the Programs Tab, first block, it says to not use IE 64 bit as the default browser, in both Vista and Win7. I think a lot of sites are not geared up for the 64 bit Browser and won't open if you are using it.

The reason it suggests not to use a 64-bit OS is simple- most content plugins don't run on 64-bit. Specifically, of course, Adobe Flash. Since IE 64-bit is a 64-bit application, it can only link to 64-bit DLLs. Therefore, all plugins will need to be 64-bit. Most other plugin vendors have done rather well and have released 64-bit versions. Adobe is the holdout.

The flash problem isn't limited to IE 64-bit. Minefield (a 64-bit build of Firefox) cannot run flash either, for the very same REASONS.

the dialog states that "IE 64-bit cannot be set as the default browser". This isn't a case of "can't" as much as it is a case of "won't". The reason was an actual conscious decision not to make it possible to set it as the default browser, for the very reasons I noted PREVIOUSLY- that is, lack of support for popular plugins. The only time a site will have trouble is if it uses flash or another unavailable plugin. a website doesn't need to be written specifically for 64-bit. It's fully possible to run 16-bit browsers and still navigate the web fine. after all, it's just a few files and scripts; the bitness of the interpreters of that markup and script is largely redundant.

Quote from: http://blogs.msdn.com/b/ieinternals/archive/2009/05/29/q-a-64-bit-internet-explorer.aspx

Q: Why isn't 64bit IE the default browser? Why can't I set the 64bit version of IE as the default browser?

A: This was an explicit choice made by the IE team, which may change at some point in the future. The problem is that users might inadvertently get "stuck" using the 64bit version and not realize it. This might cause some problems.

Q: Why? What does not work properly with 64bit IE?

A: Browser addons, including BHOs, Toolbars, and ActiveX controls, must generally be the same bitness as IE itself. So, if you are running a 64bit version of IE, any site that uses, say, Adobe Flash, isn't going to work until you install the 64bit version of the addon. Sadly, almost no browser addons are currently available in 64bit versions, although that's somewhat likely to change in the future as 64bit Windows becomes more prevalent.

Q: So, is there any benefit to using 64bit IE?

A: Some users like to use 64bit IE from time to time for a variety of reasons, but in my opinion, none of them are super-compelling. Here are a few reasons I've heard:

* DEP/NX is always on for 64bit processes. (Of course, on Vista SP1+, 32 bit IE8 has DEP/NX enabled by default too.)
* It crashes less. (Because most addons don't load in 64bit IE, it tends to be more reliable.)
* It's faster. (Mostly because most addons aren't loaded. There's also an unsubstantiated claim that image decoding is faster, but I find this very unlikely).

Q: Okay, so why offer 64bit IE at all?

Because we have to. :-)

One thing to keep in mind is that Internet Explorer is basically the combination of a number of platform components, including the networking components (URLMon/WinINET), the rendering components (MSHTML), the script engines (JScript.dll, vbscript.dll) and a variety of other pieces that hold it all together. These components must be made available in 64bit versions so that 64bit APPLICATIONS can be built using these components. Additionally, because Internet Explorer can be launched/created/used as a COM Server, we offer a 64bit version to enable hosting inside 64bit processes.

While we could have done work to make it harder for users to get to 64bit IE (e.g. by not creating a Start menu shortcut), I don't think there's any super-compelling reason to do so.

One day, 64bit IE might see a lot more use, as 64bit systems take over and 64bit add-ons become available. Time will tell.

So, the summary is this:

the downside of using 64-bit IE is that fewer addons and toolbars and so forth can run. The upside of this is that fewer addons and toolbars and so forth can run.

Yup. There are some that do like their add ons though. I prefer to run as few as possible.Quote

So, the summary is this:

the downside of using 64-bit IE is that fewer addons and toolbars and so forth can run. The upside of this is that fewer addons and toolbars and so forth can run.

Shoot, in my case it is a moot point anyway. I have IE 8 in here, but I use Verizon w/ MSN Premium service and it uses a hybrid browser called MSN Explorer.

Solve : windows 7 64-32 bit?

Discussion

No Comment Found

Related InterviewSolutions

Reply to Comment