If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
#16
|
|||
|
|||
Win 7 32-bit
On 20/02/2018 02:46, VanguardLH wrote:
Paul wrote: philo wrote: Andrew Wilson wrote: Someone is building me a new computer. I told him I was currently using Win 7 but didn't mention which version (I'm using win 7 32-bit). Just read the documentation with the GA-A320M-HD2 and it says it only supports Operating System Support for Windows 10 64-bit Support for Windows 7 64-bit Will Win 7 32-bit definitely not work on this board as if not I'll have to go out and buy either Win 10 64-bit or Win 7 64-bit. If you plan to use more than 3 gigs of RAM you should go with the 64bit version. Even if you do not plan to use more than 3 gigs of RAM I'd still go with the 64 bit version because you very well may want to use more RAM some day. The only reason the 32-bit version comes up, is for its ability to run 16-bit software. And that's not the kind of software you think it is either. There are quite a few 32 bit programs, where the installer for the program is 16-bit, and that prevents installation of the 32 bit program [that would have run in a 64-bit OS]. Just the installer used, a particular free installer, is the source of a lot of grief. Running old 16-bit games, is a second use-case for the x32 OS. Microsoft apparently could have made a WOW subsystem so 16 bit ran on the 64 bit OS too. But they chose not to. And this is why some users continue to like the 32-bit OS, for compatibility with large collections of existing software (software with installer issues, or actual 16-bit software from long ago). https://en.wikipedia.org/wiki/Windows_on_Windows This subsystem is available in 32-bit editions of Windows NT only. The 64-bit editions (including Windows Server 2008 R2 and later which only have 64-bit editions) cannot run 16-bit software without third-party emulation software (e.g. DOSBox). "64-bit versions of Windows do not support 16-bit components, 16-bit processes, or 16-bit applications" https://support.microsoft.com/en-us/...nts-16-bit-pro To get around the 16-bit installer (wrapped around a 32-bit app), there are many of suggestions, like those at: https://stackoverflow.com/questions/...on-64-bit-win7 A long time ago (when I moved to x64 for Windows), I lost some x16 DOS games. They were pretty old so I really didn't mind that much that I lost them. Later I found DOSBOX ran under Windows x64 can be used to play x16 DOS games but I had already gotten rid of the old games. http://www.freezenet.ca/guides/compa...rating-system/ That suggests using DOSBOX as the emulator to provide a 16-bit environment for the old game or app. I've not used DOSBOX to know how well it supports old x16 apps under Windows x64. I suspect there will be some problems with any old app that attempt direct access to hardware that emulation won't handle. For example, I remember some games were bitches to get running and stay running because of their protection mechanisms. Some protections would check for emulation, redirection, or other tricks and refuse to let the game load. If they wouldn't allow the game to run using an emulated CD drive, they probably won't run inside an emulator or virtual machine, either. 32-bit support will eventually get phased out, too, just as what happened to 16-bit support in Windows x64. When you see Microsoft release an x64-only version of Windows as their lowest bidtwidth is when the expiration timer starts on 32-bit apps. As the OP has discovered, hardware makers are already starting to abandon 32-bit support. There was pressure from consumers for more than ~3.8GB of user space in system RAM, the limit for 32-bit processors (2^32 = 4,294,967,296 but remember the OS reserves some space so user space was less than 4GB). Having more user space (without having to swap around blocks of memory) meant going to 64-bit processors. Those can address 16 exabytes of memory (but are throttled by what the OS will allow). So we will have 64-bit processors around for a long time since it will take a long time before memory is cheap enough to make 16 exabytes look restricting on user space. I don't think 128-bit processors will show up before I die but it could happen. That doesn't mean the OS vendors or hardware makers will want to continue supporting 32-bit interfaces or translations to the 64-bit hardware. Many thanks everyone for your help and advice (except ignorant, arsehole, dickhead 'Good Guy'). After a lot of tinkering around I have installed Win 7 32-bit and all Windows Updates. The chipset software CD wouldn't install any Win 7 32-bit drivers but I managed to get only the USB3 driver to work by selecting the 'unknown device' with exclamation mark in USB in Device Manager and then update driver. No driver found on the internet but I forced it to look for a driver on the chipset software CD which happily it found and installed. Another 'unknown device' then popped up and I did the same as before and it installed USB2 drivers. I've been running all day with occasional restarts and it is running fine I'm delighted to say. The Windows 7 32-bit was on a UK school multi-licence and I had authority to install it on my home PC and I like it far better than Win 10. When support ends in 2020 probably the school and I will switch to Windows 10. So 'Good Guy' you should really find out the facts before sticking your big nose in where it's not wanted! Thanks again peeps aw56001 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
Ads |
#17
|
|||
|
|||
Win 7 32-bit
On 02/20/2018 11:59 AM, Andrew Wilson wrote:
On 20/02/2018 02:46, VanguardLH wrote: Paul wrote: philo wrote: Andrew Wilson wrote: Someone is building me a new computer. I told him I was currently using Win 7 but didn't mention which version (I'm using win 7 32-bit). Just read the documentation with the GA-A320M-HD2 and it says it only supports Â*Â* Operating System Â*Â*Â*Â*Â* Support for Windows 10 64-bit Â*Â*Â*Â*Â* Support for Windows 7 64-bit Will Win 7 32-bit definitely not work on this board as if not I'll have to go out and buy either Win 10 64-bit or Win 7 64-bit. If you plan to use more than 3 gigs of RAM you should go with the 64bit version. Even if you do not plan to use more than 3 gigs of RAM I'd still go with the 64 bit version because you very well may want to use more RAM some day. The only reason the 32-bit version comes up, is for its ability to run 16-bit software. And that's not the kind of software you think it is either. There are quite a few 32 bit programs, where the installer for the program is 16-bit, and that prevents installation of the 32 bit program [that would have run in a 64-bit OS]. Just the installer used, a particular free installer, is the source of a lot of grief. Running old 16-bit games, is a second use-case for the x32 OS. Microsoft apparently could have made a WOW subsystem so 16 bit ran on the 64 bit OS too. But they chose not to. And this is why some users continue to like the 32-bit OS, for compatibility with large collections of existing software (software with installer issues, or actual 16-bit software from long ago). https://en.wikipedia.org/wiki/Windows_on_Windows Â*Â* This subsystem is available in 32-bit editions of Windows NT only. The Â*Â* 64-bit editions (including Windows Server 2008 R2 and later which only Â*Â* have 64-bit editions) cannot run 16-bit software without third-party Â*Â* emulation software (e.g. DOSBox). "64-bit versions of Windows do not support 16-bit components, 16-bit processes, or 16-bit applications" https://support.microsoft.com/en-us/...nts-16-bit-pro To get around the 16-bit installer (wrapped around a 32-bit app), there are many of suggestions, like those at: snip Very glad you got it working. BTW: I put that troll in my KF years ago |
#18
|
|||
|
|||
Win 7 32-bit
On Mon, 19 Feb 2018 12:31:51 -0500, Paul
wrote: The only reason the 32-bit version comes up, is for its ability to run 16-bit software. And that's not the kind of software you think it is either. There are quite a few 32 bit programs, where the installer for the program is 16-bit, and that prevents installation of the 32 bit program [that would have run in a 64-bit OS]. Just the installer used, a particular free installer, is the source of a lot of grief. Quite a lot of the software I use is 16-bit, or even 8-bit. So if I have to replace one of my computers I'll be looking for a 32-bit version of Windows. Having more than 3 Gb of memory is no use at all if you cant run the programs you need to access your data. And I never play games, so that's not the only reason either. -- Steve Hayes http://www.khanya.org.za/stevesig.htm http://khanya.wordpress.com |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|