I subscribed to the Legacy user group because I wanted to read comments/discussions related to Legacy. I did not subscribe to a Windows user group, so why do I have to be subjected to these useless discussions about the Windows operating system. For those who feel compelled to demonstrate what they know/don't know and/or hate about the Windows OS, please join a Windows user group.
Ron Bernier Woonsocket, RI On Fri, Dec 27, 2013 at 5:09 PM, Bryan Pratt <[email protected]>wrote: > Sorry Don, but you are wrong. My W 7 was a 64 bit system. So W8 was the > same. Windows Upgrade usually sorts it for you. You only have to read the > Windows forum correspondence on the upgrade process to see how fraught it > was with problems. > Bryan > > Sent from Windows Mail > > *From:* Don Hanson <[email protected]> > *Sent:* Saturday, December 28, 2013 10:35 AM > *To:* Legacy <[email protected]> > > Sorry, I’m slowly catching up. I’m only tossing my comments in, to save > others from having to hire a tech. When you UPDATE Windows, you have to > download the version with the same bits as the Windows that is installed. > The windows store site has very clear and detailed instructions for > determining the current Windows version and ‘bits’. There is also a warning > that they must match. It is only during the upgrade that you need to be > concerned with ‘bits’. You apparently had Win8 32 bit installed and tried > to install the 64 bit upgrade to 8.1. That has nothing to do with Windows 8 > or 8.1. It certainly is not a reason to not recommend Windows 8 or 8.1. > > Don Hanson > > > > > > *From:* Bryan Pratt [mailto:[email protected]] > *Sent:* Thursday, December 19, 2013 9:59 PM > *To:* [email protected] > *Subject:* Re: [LegacyUG] Legacy8 w/Windows 32 or 64 bit (was: > Highlighted colour) > > > > To add again my thoughts on this mix. The only way my paid technician > found to get W8.1 to work was to reconfigure it from 64 to 32 bit and > install W 8.1 as 32 bit. I am totally ignorant of ‘bits’ but I just throw > this in as an experience I had. > > I would still recommend staying away from W.8 > > Bryan > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
