Windows 7 32 bit to 64 bit or both?

Page 2 - Seeking answers? Join the Tom's Hardware community: where nearly two million members share solutions and discuss the latest tech.
Status
Not open for further replies.

TonyACG51

Distinguished
Aug 4, 2010
92
0
18,630
I have some questions about windows 7 OS.

1) Does windows 7 64 bit support 32 bit still?

2) Can I use windows 64 bit with 4 modules of ddr3?

3) Can windows 7 64 bit configure 32 bit memory channels?

4) Can I expect windows 7 64 bit to configure 128 bit width memory on dual channels 4 modules, or 256 bit width on dual channel 4 modules? (32 bit x 4 ddr3 modules)

5) Do I need to get a windows 7 64 bit + 32 bit OS package to use both 32 bit and 64 bit width memory configure?

7) Can windows run in 64 bit mode while use 32 bit architecture?

8) Can windows 7 64 bit be restricted to 32 bit when needed? or will I need a package that has suport for both 32 bit and 64 bit?

I'm asking because most all games I check on play with 32 bit os and only need 64 bit for DX11 graphics. I think one OS that can run both 32 and 64 bit with a click or switch users could be what I am looking for.
 



This would actually be detrimental to performance.

I don't understand what is difficult about this... There is NO DIFFERENCE if you run a 32bit program in a 32bit Operating system or a 64bit operating system!!!


however running a game in XP mode will bring your performance down, because you are using your Operating system, to run another operating system, to run a game. This will be horrible for performance.


Do this, you can always change later.


1. Install Windows 7 64bit.
2. Install any of your old "Direct X 9" games

you will see that they install into a separate program Files folder on your drive (Program Files (x86)) instead of just (Program Files) this makes sure that windows will run it AS A 32BIT PROGRAM.

You will NOT SEE ANY DIFFERENCE running an older DX9 game on a 32 bit os or a 64bit os.
 



If you dual booted a 64bit / 32bit OS when you turned your computer on and decided which OS you are going to launch windows would then address the max. If you chose 32bit it would only address a max of 4GB, meaning the first 4GB of data blocks the BIOS has access to. Anything above those first 4GB of data blocks the OS CAN NOT SEE AT ALL.

But, if you chose 64Bit mode, it would do the same, except it would see all memory installed.

There is no problem with that at all.


Also, there is NO HOST that can ONLY be 64bit. EVERY PROCESSOR that is 64bit supports a 32bit instruction set.
 


Sorry tony, but the tail end of that sentence makes no sense.

If you've got 6GB of RAM, win764 + some apps = 2GB the virtual machine software perhaps 200MB, leaving 3.8GB for the memory for the virtual machine, all ok whilst you are running just 2GB of host machine, or if you have more than 6GB of Host RAM.

If you are thinking that 64 and 32 bit OS's write to disks differently they don't, so saving a file on the virtual machine is ok, and it will be readable by the host machine, if it is placed in a location they can both see (a bit of setup required).
 


Truth is that was way to easy. I don't have 64 bit windows so I dint think it would divide the difference like that. The sales point of windows 7 pro with XP mode sounds null then. I don't assume these things know any better it's just a computer. Then I have to know that if I buy a cheaper version such as windows 7 home 64 that'll ill get the same options as the windows 7 pro 64. You see the thing is saving money is good. So what you're telling me is that all 64 bit windows can operate 32 bit software?
 
Yes, All versions of win 7 64bit can operate 32bit software. That is how they are designed. They HAVE to be able to run 32bit software, because ALMOST ALL software on the market is 32bit, with few exceptions.

you do NOT need to put 64bit windows into any special mode or settings at all. Just install it, and it will see if it is supposed to be run in 32bit mode or 64bit mode and run it accordingly.

You don't need to do anything at all, just install and run.
 


Cool download! Looks useful. Thank you i'll look into it for sure.
 
Cool that means that when you say that only use 64 bit OS for 4GB or more of memory that's because bit width is not the only factor. I can then use high frequency to allow 64 bit length, height, and depth as needed. That makes passing data to the gpu limited to 64 bit width and the rest is off loaded by the gpu in length, height, and depth. LOL that explains the gap in memory configure from 128 bit to 192 bit. I believe that means network input has another 64 bit width to work with. Cool! So in a 3D modeling API the gap would be hardware accelerated? Maybe want to go with a 256 bit GPU then for better performance (multitask multi-device, dual precision). Then all i'll have to do is learn how to program it LOL.
 


No no no and no

in order to read and write from memory you have have to know where you have put it (think draws in a filing cabinet), in a 32bit OS you have 3.5 million of them each holding 1000 things.

In a 64bit OS you have trillions of trillions of draws each holding 1000 things.

Thats it, there's nothing more to it.

Some mother boards have supper fast trollies that fetch things from the drawers, some have slow ones, some fetch from 2, 3 or 4 drawers at conce, some from only 1.

With graphics cards the number of trollies working at any time is really important, this equates to bandwidth.
 



Yeah and when you visualize 100 yards of a viewpoint you'll want trillions of drawers so that 3D viewpoint can be changed asap. Like looking down a road traveling 60 MPH, you can see all 100 yards but it's moving the viewpoint 60 mph, so the viewpoint changes with you @ 60 mph. With more memory blocks the viewpoint can change more times, and with multi-channel memory you can make a right or left turn at any point while traveling and still have 100 yards of viewpoint. Now what needs to be done is with in that viewpoint I need to see 100 yards but not all 100 yards as clearly as say the first 20 yards. So addressing those of blocks of data as 16 bit x 2 x 2 (or 32 x 2 x 2, then means dual-channel 16 x2 x2 x16 x2 x2 I think) would allow me to blur the difference with maintaining 3D axis. With 64 bit I could divide 64 down to 16 @ 4 x and allow blur @ 5, 10, 15 and 20 yards I think, then add 3D axis and I can maintain that blur as well as depth in one swift read.
 
This is why I said forget everything you read about bus width. The only thing you should concern yourself with is 64bit windows can use more than 4gb ram, everything else is hardware related and you have no control over. Even bus width in a gpu really makes no difference, a gpu with 512 bit bus can be slower than a 32 bit bus width as that's not the only factor for performance.

It would be easier to help pick parts and then explain those choices rather than explaining electronic engineering, unless that's what you want to do.
 
I have no idea what you are talking about, the number of filing cabinets is OS related. Everything else is hardware related and not at all related to the OS in a way you can effect. You cannot ask the OS to access memory in a specific way, it will just ask for stuff from memory and the hardware will deal ensuring that all of the data is provided efficiently.
You cannot ask that the OS splits the dual channel memory into segments and pulls different daya from each segment. You'd need to re-write very lowelevel pieces of OS that talk to the mobo.
 
A lot of people seem to think that 64 bits of address space can be accessed twice as fast as 32 bit address space - 'cos you know, a 64 bit wide bus is twice as wide as a 32 bit wide bus, so obviously you can pump twice as much data over it, right? Wrong. They really need to do some reading as what addressing 64 bits actually means with respect to RAM.
 

Yeah I think I need more info about it too. It's kinda hard to see through. Math comes first then again in frequency. Bit width must be used to call info from one spot on memory to complete the frequent task. The higher the bit width the more option you have. but all it comes down to in the end (so it seams) is capacity. I still believe that a higher bit width will allow to cpu to complete 3D tasks faster, being that the memory's not shared leaving each channel to its job. Maybe I should just go to school for it XD. People really pay for this info.
 
This thread perfectly illustrates why OS / hardware is largerly independent and we have various layers of abstraction in modern day programming. It's so we can actually get something done without needing to worry about all this c5ap.

TonyACG51 you are an a55hole looking for cheap thrills wallowing around in this like a semi retard probably giggling and laughing at yourself and how clever you are wasting peoples time with this nonsense. I am only taking the time to reply because I want you to know I realized what you were doing from pretty much post 1 and I think you are peice of ****.
 



;;;;; All I want to know is how to multiply a processors bit rate read from the memory so that it could divide faster. Using a 32 bit os was simply so that a 64 bit processor could divide twice as much data, like half of what 64 bit process is. But I think it's kinda funny to think that the only benefit is data capacity. Whatever... answer is to use more for less.... The only reason I replied was to get the last word, I got my answer. {solved} Add a cool app HAHAHA!
 
Status
Not open for further replies.

Latest posts