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 |
#1
|
|||
|
|||
Win 7 32-bit
Help please?
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. They don't make it easy do they? Many thanks aw56001 --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
Ads |
#2
|
|||
|
|||
Win 7 32-bit
Andrew Wilson wrote:
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 That means those are the operating systems for which the mobo vendor will provide drivers for their hardware. You can use Windows 7 x64 but you risk hardware compatibility. Windows 7 x64 might include the 64-bit drivers for that mobo but maybe not. You should've dug a bit deeper. See: https://www.gigabyte.com/Motherboard...-10#support-dl Notice which Windows versions are available in the drop-down list. --- Not a valid signature delimiter line, and Avast knows that. This email has been checked for viruses by Avast antivirus software. hxxps:// www. avast. c0m/antivirus Do not volunteer to be a spam affiliate of your choice of AV software. Either disable the fake signature which is spam or uninstall their Mail Shield module since it is superfluous and affords no more protection than does their on-demand (real-time) scanner. |
#3
|
|||
|
|||
Win 7 32-bit
"Andrew Wilson" wrote in message ... Help please? 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. They don't make it easy do they? Many thanks aw56001 According to their website, they have drivers for Win7/8.1/10 32-bit, so I would assume (yeah, I know what that means) that 32-bit Windows will run on it. https://www.gigabyte.com/Motherboard/GA-A320M-HD2-rev-10#support-dl -- SC Tom |
#4
|
|||
|
|||
Win 7 32-bit
On 18/02/2018 11:28, Andrew Wilson wrote:
if not I'll have to go out and buy either Win 10 64-bit or Win 7 64-bit. You don't need to buy Windows 7 64 bit. you can download it free of charge from Microsoft Website by inserting your Windows 7 (32 bit) serial number. For Windows 10 , YES you need to buy it. It is not free. Did you just wake up? Why did you not know about Windows 10 free version when it was available? Where did you steal Windows 7 32 bit from? It is no longer available from the official channels. Don't tell me you are eBayer touting pirated software. Microsoft is watching you. If nothing works then please install Linux system and use their NGs to ask your silly questions. They will love you for asking them something. -- With over 600 million devices now running Windows 10, customer satisfaction is higher than any previous version of windows. |
#5
|
|||
|
|||
Win 7 32-bit
Andrew Wilson wrote:
Help please? 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. They don't make it easy do they? Many thanks aw56001 There would be a couple potential issues with Windows 7. 1) Drivers are likely to be OK. If they're offered for x64, then x32 is just as likely. The only company to break with that at the moment, is NVidia, which has promised to discontinue new x32 drivers. I love companies making uncoordinated decisions like this. 2) XHCI and Windows 7. Windows 7 has no USB3 drivers built-in and on XHCI-only motherboards, this can cause a problem if using a USB3 port for installation. This might happen if the user places the Windows 7 installer contents on a USB stick, then plugs it into the USB3 port. Your board has XHCI handoff, and I presume that has something to do with fixing that. Using an optical drive on SATA, solves the problem, but depending on your usage pattern, you might occasionally plug in a USB stick without thinking about it, and be stopped by something like this. Like if you put the Windows 7 emergency boot image on a USB key, didn't set the BIOS properly, and it wouldn't boot or something. This issue is mainly something to keep in mind, when analyzing boot failures. It's not likely to be a drop dead issue (unless it was a tablet or something, with limited I/O choices). (First mentioned as an issue, about 75% of the way down this page...) https://www.anandtech.com/show/9485/...vga-supermicro 3) Windows Update will receive a warning that "you're using an unsupported processor" when using Ryzen. Or Coffee Lake in Windows 7. Skylake is OK. There's a hack to fix Windows Update so it still delivers updates. But you must check the latest developments to see if Microsoft has disabled the hack. You should still be able to install patches manually, say from catalog.update.microsoft.com. And using MBSA 2.3 to figure out what patches are needed for security. MBSA 2.3 doesn't tell you about optional updates, only security ones. And no, they're not trying to make it easy. If you read between the lines, the ecosystem isn't what it used to be. At one time, maybe a little cash would change hands under the table. Like if one company said "I need $10 million to support test of your new hardware in my OS", the money would change hands. And from the outside, the Windows ecosystem would look like one happy family. But things have changed. Microsoft made a port of their OS for ARM, and without ARM paying for it. They did the port because Microsoft wanted a WinRT. Ports for companies where Microsoft didn't want to do that, would be charged $150 million (which is a reasonable price for a port like that). Microsoft makes their own PCs, which ****es off the OEMs. Microsoft has made new pricing structures for Win10 OEM which are graduated (according to CPU performance), and higher than before. Nibbling away at OEM margins. In a word, the industry members are at war with one another, with all this unfriendly activity. For example, Microsoft made an x86 emulator for ARM (which hasn't been deployed yet, but could be seen in the real world soon). And Intel has issued a press release saying they aren't really pleased (and the lawyers are climbing into the Clown Car to see what they can do about it). The end result, is you see a few cracks in the seams here and there. And as a user, you have to put up with any issues created. Paul |
#6
|
|||
|
|||
Win 7 32-bit
On Sun, 18 Feb 2018 11:28:47 +0000, Andrew Wilson
wrote: 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. Probalby you don't need to buy a Win 10 license: despite what MS officially says, that the free offer to upgrade from Win 7 to Win 10 is expired, few days ago I have used a Win 7 product-key to activate a fresh clean installation of Win 10. I have installed Win 10 using the ISO on a USB stick, using the desired version 32 bit or 64 bit, selected the correct Win Home or Pro version depending on the Win 7 PK, skipped inserting it during installation. When Win 10 was up and running then in Settings, Update and Security, Activation, Change product key, I have entered the Win 7 PK. Apparently ther was a problem activating but simply clicking on Tropubleshoot (in the same page) solved it. |
#7
|
|||
|
|||
Win 7 32-bit
On Sun, 18 Feb 2018 11:28:47 +0000, Andrew Wilson
wrote: Help please? 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. They don't make it easy do they? Many thanks Your question has already been answered, but let me make another point: You say "I'm using win 7 32-bit." Does that mean you intend to transfer the Windows 7 license from your old computer to the new one? If so it's possible that you can not do this. If you have a retail version of Windows, no problem. But if it's an OEM version (for example if it came preinstalled on the computer), its license ties it permanently to the first computer it's installed on; it may never be moved to another. |
#8
|
|||
|
|||
Win 7 32-bit
SC Tom wrote:
"Andrew Wilson" wrote in message ... Help please? 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. They don't make it easy do they? Many thanks aw56001 According to their website, they have drivers for Win7/8.1/10 32-bit, so I would assume (yeah, I know what that means) that 32-bit Windows will run on it. https://www.gigabyte.com/Motherboard/GA-A320M-HD2-rev-10#support-dl No 32 bit chipset drivers. |
#9
|
|||
|
|||
Win 7 32-bit
Paul in Houston TX wrote:
SC Tom wrote: "Andrew Wilson" wrote in message ... Help please? 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. They don't make it easy do they? Many thanks aw56001 According to their website, they have drivers for Win7/8.1/10 32-bit, so I would assume (yeah, I know what that means) that 32-bit Windows will run on it. https://www.gigabyte.com/Motherboard/GA-A320M-HD2-rev-10#support-dl No 32 bit chipset drivers. That's a good catch. You can see what happened. I checked the 1.26GB driver and it seems to have 32 bit content in it. The 17.40 is roughly half the size, and 32 bit stuff is missing. So that means the AMD policy changed at the same time as NVidia ??? Support AMD Raven Ridge CPU OS: Windows 10 64bit [17.40] 572.39 MB OS: Windows 7 64bit, [16.50.2601] 1.26 GB Windows 10 64bit The 1.26GB driver package has folders like this. W7 W764A WT64A The 572.39 MB driver package has this folder by comparison. So this is all the "Ryzen with VEGA" support you get. WT64A Then you'd have to run off to a laptop site, and see if they have a 32 bit driver for the mobile version of Raven Ridge. I'm sure though that they'd change the VENEV to prevent reuse of the driver. Even though the silicon might be quite similar. When I checked the AMD driver site, it lists only Win10 x64 for the Raven Ridge desktop too. It's listed as "Ryzen 5 processors with Radeon Vega graphics". I can't find an announcement from AMD to match the announcement that NVidia made at the end of last year. So here we have hardware companies dropping support for an OS, before the Microsoft End Of Life. Gotcha. Paul |
#10
|
|||
|
|||
Win 7 32-bit
Paul wrote:
Paul in Houston TX wrote: SC Tom wrote: "Andrew Wilson" wrote in message ... Help please? 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. They don't make it easy do they? Many thanks aw56001 According to their website, they have drivers for Win7/8.1/10 32-bit, so I would assume (yeah, I know what that means) that 32-bit Windows will run on it. https://www.gigabyte.com/Motherboard/GA-A320M-HD2-rev-10#support-dl No 32 bit chipset drivers. That's a good catch. You can see what happened. I checked the 1.26GB driver and it seems to have 32 bit content in it. The 17.40 is roughly half the size, and 32 bit stuff is missing. So that means the AMD policy changed at the same time as NVidia ??? Support AMD Raven Ridge CPU OS: Windows 10 64bit [17.40] 572.39 MB OS: Windows 7 64bit, [16.50.2601] 1.26 GB Windows 10 64bit The 1.26GB driver package has folders like this. W7 W764A WT64A The 572.39 MB driver package has this folder by comparison. So this is all the "Ryzen with VEGA" support you get. WT64A Then you'd have to run off to a laptop site, and see if they have a 32 bit driver for the mobile version of Raven Ridge. I'm sure though that they'd change the VENEV to prevent reuse of the driver. Even though the silicon might be quite similar. When I checked the AMD driver site, it lists only Win10 x64 for the Raven Ridge desktop too. It's listed as "Ryzen 5 processors with Radeon Vega graphics". I can't find an announcement from AMD to match the announcement that NVidia made at the end of last year. So here we have hardware companies dropping support for an OS, before the Microsoft End Of Life. Gotcha. Paul MB appears to be made for W10/64 with 7/8 64 an afterthought on GA or it just happened to work on 7/8 64. The ASUS equivalent (chipset AMD A320) only lists W10 o/s. I noticed the driver file size difference but did not take them apart to verify. |
#11
|
|||
|
|||
Win 7 32-bit
On 02/18/2018 05:28 AM, Andrew Wilson wrote:
Help please? 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. They don't make it easy do they? Many thanks aw56001 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. |
#12
|
|||
|
|||
Win 7 32-bit
philo wrote:
On 02/18/2018 05:28 AM, Andrew Wilson wrote: Help please? 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. They don't make it easy do they? Many thanks aw56001 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). Paul |
#13
|
|||
|
|||
Win 7 32-bit
On 02/19/2018 11:31 AM, Paul wrote:
philo wrote: On 02/18/2018 05:28 AM, Andrew Wilson wrote: Help please? 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. They don't make it easy do they? Many thanks aw56001 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). Â*Â* Paul Also: Some additional older drivers do not exist for a 64 bit OS. I have an old, professional model slide scanner than was designed for XP. It works fine on Win7 but the only the 32 bit version. There are no drivers at all unless I would want to purchase View Scan |
#14
|
|||
|
|||
Win 7 32-bit
In message , philo
writes: On 02/19/2018 11:31 AM, Paul wrote: [] 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). ** Paul My preferred email/news client (Turnpike) is a shell extension (or parts of it are), that also runs only with the 32 bit shell. (Mailboxes, newsgroups, etc. appear as real folders.) MS had the 32 bit shell available (I think that word WOW came up) right up to the release candidate of W7/64 - Turnpike worked with all the pre-release candidates - but they decided to break it on the final release. (TP _is_ 32-bit software, but needs the 32-bit shell too.) Also: Some additional older drivers do not exist for a 64 bit OS. I have an old, professional model slide scanner than was designed for XP. It works fine on Win7 but the only the 32 bit version. There are no drivers at all unless I would want to purchase View Scan The fact that it - and many other scanners - _does_ work via VueScan increases my irritation that scanner manufacturers haven't come out with a universal interface, since it's obviously possible. Same for printers. (Both could work with the "standard" interface, requiring extra software for any unique features. But there's no incentive for them to do it, and plenty for them not to.) I admire VueScan's initiative in having created their product - I'm just sorry that it costs more than a medium-quality scanner. (Not their fault, I think they're a small company who are unable to make it for less.) -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf I've never really "got" sport or physical exercise. The only muscle I've ever enjoyed exercising is the one between my ears. - Beryl Hales, Radio Times 24-30 March 2012 |
#15
|
|||
|
|||
Win 7 32-bit
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. |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|