Bones is right, the files are there to support compatability mode for programmes that require it. If you had both versions on your install disk then once you chose to install X64, you're locked into it. To change it would depend on the End User Licence Agreement (EULA) you have. If it's restricted to so many installations then you'd be using up one to install X32 and also be losing the 8Gb support. If your EULA was valid for more than one simultaneous install you could set up the 32bit version on a second drive/petition. However, most home users EULA restrict them to running only one copy and would probably throw up MS's Phone Home (you need to phone MS to validate this copy of windows) when you tried to install the second copy. When you phone MS they would then say you need a purchase second licence. If you were to go down the 32/64 bit duel boot route, you then need to think through the implications of registry entries and whether to install a programme within just the 32 or 64 bit setup or both and the implications that has on folder structures and the individual programmes EULAs. To me the potential problems far outweigh any possible gain, I'd leave it well alone. Paul -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of Fossil Sent: 16 April 2012 18:02 To: jhb@xxxxxxxxxxxxx Subject: [jhb] Re: W7 QUERY My W7 DVD gave me the option to install the 32 or 64 bit versions so I assume this is just to save having to make separate DVD for each version. As I had bought the 32 bit version (or rather the license) I assumed the 64 bit would install but not activate - so I never tried it. Your 32 bit folder may only have some core files rather than the full 32 bit installation.. bones bones@xxxxxxx http://woodair.net -----Original Message----- From: jhb-bounce@xxxxxxxxxxxxx [mailto:jhb-bounce@xxxxxxxxxxxxx] On Behalf Of Gerry Winskill Sent: 16 April 2012 11:06 To: JHB Restricted Subject: [jhb] W7 QUERY I don't think I've asked this one previously but here goes. Despite using the false UIAutomationCore.dll "cure" listed in the forums, I'm still getting the occasional FSX CTD, accompanied by the spinning wheel and spilt milk appearance. Together with a couple of other FSX problems, apparently the fault is only present when running under W7 64bit. I'm using W7 64 only for its ability to access 8Gb of memory. In practice FSX never seems to access anywhere near that amount. I notice that the W7 Windows folder contains a 34 folder as well as the expected 64. Does anyone know whether it's possible for me to boot up in W732, instead of 64 bit? Gerry Winskill