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 |
#31
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On 09/25/2017 06:28 PM, Paul wrote:
[snip] A certain range of versions of DataRAM RAMDisk are capable of using PAE space. The RAMDisk runs in Ring0. Thus, I can have 3.2GB of memory for WinXP (in Ring3 application space), and 4GB for the RAMdisk (in Ring0 driver space), out of 8GB total on a 32-bit OS. I had that installed when I was using XP on a system with 8GB. When that machine died I installed 64-bit Windows 7. The real ****er, is DataRAM removed the PAE capability. Newer versions of their software no longer have that setting. Almost like "someone asked them nicely to remove it" :-( But, I have the capability I need here, so I no longer care about this. My copy works... Â*Â* Paul -- 90 days until the winter celebration (Monday December 25, 2017 12:00:00 AM for 1 day). Mark Lloyd http://notstupid.us/ "There are no sects in geometry." [Voltaire, Philosophical Dictionary, 1764] |
Ads |
#32
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On 09/25/2017 06:54 PM, wrote:
[snip] I guess it would not work with Win 10. Almost all machines come with 8 gigs these days. I went up to 16 gigs on one laptop. Never noticed any difference although I doubt I would. I have one machine with 32GB. It helps when running multiple virtual machines at the same time. KenW -- 90 days until the winter celebration (Monday December 25, 2017 12:00:00 AM for 1 day). Mark Lloyd http://notstupid.us/ "There are no sects in geometry." [Voltaire, Philosophical Dictionary, 1764] |
#33
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Mark Lloyd wrote:
This is still not as completely successful as with Linux (for one thing, there's still that **** registry) Exactly! -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#34
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On Mon, 25 Sep 2017 19:28:42 -0400, Paul
wrote: wrote: On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display Reading posts in the thread, wasn't there some setting one could use to increase memory seen by 32 bit OS. Been a few years if I remember correctly and don't remember who, what, where or when !! KenW That's called PAE, and yes, it can. You can have 64GB of RAM usable in a 32-bit OS. The limit is 16 GB and it requires the computer to have 2 extra address lines. Each process cannot access more than two to four gigabytes, so one 32-bit process is not allowed to own the whole thing. That takes a good deal of the "fun" out of it. However, the implementation of the "Microsoft memory license", prevents this from happening. How the memory license works, is pretty specific. There is 4GB of address space allowed in Ring 3. Ring 0 (kernel and driver space) is not limited. I have 8GB of memory installed on this WinXP Sp3 x32 machine. I had a server with 8 Pentium 3 CPUs and 8 GB RAM using PAE. SP3 enables PAE to get the NX bit in the page table. As a side bonus, that leaves the PAE door open. A certain range of versions of DataRAM RAMDisk are capable of using PAE space. The RAMDisk runs in Ring0. Thus, I can have 3.2GB of memory for WinXP (in Ring3 application space), and 4GB for the RAMdisk (in Ring0 driver space), out of 8GB total on a 32-bit OS. The real ****er, is DataRAM removed the PAE capability. Newer versions of their software no longer have that setting. Almost like "someone asked them nicely to remove it" :-( But, I have the capability I need here, so I no longer care about this. My copy works... Paul |
#35
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On Mon, 25 Sep 2017 06:36:45 -0600, Albert
wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. You can simply upgrade without losing any data or settings. You may need a licence key if you upgraded free from Windows 7 32 bit. |
#36
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Mark Lloyd wrote:
(for one thing, there's still that **** registry). The Registry is journaled. The Registry is saved in Restore Points. The file system (NTFS) is journaled. What's not to like ? :-) And as it turns out, the Registry is a "file system". For the longest while, I thought it was a database, but a discussion thread describes what it does as a file system. Think of it as a bitmap file holding a file system image, and then a file system driver extracts individual "files" (entries). The OS makes at least a couple hundred accesses a second to the Registry, and the hard drive light doesn't even blink. *All* file systems can be corrupted, with enough hardware damage to storage. And you design your storage methods, for the right compromise values to account for that. And no system is completely resistant to bad RAM. "Good" computers have ECC, but the marketing people don't want us to have that on desktops. And that leaves all OSes with an exposure with regard to integrity of operation. You can corrupt anything you read into bad RAM, and copy out again. This is how I was able to make a backup in Macrium, which worked fine when it was done (Macrium Reflect Free didn't complain), but when I later ran a "Verify" on the MRIMG, it failed. Bad RAM used for disk buffering, did that. The checksum was computed on the file, before the RAM buffer was written into the MRIMG. I had a couple backups ruined that way, until the RAM was replaced (on this machine). The single biggest exposure on Windows now, is the possibility of bad RAM. You should test the RAM on your computer, on at least a yearly basis just for safety. Cheap RAM seems to have a median life of 2 years or so, before something happens. The RAM I had die, was Kingston, and the error condition was flighty enough, I was not able to fault isolate to the nearest stick, and had to replace the whole set. Each stick would test good by itself, but only when the whole set of sticks was installed, would the error come back. Paul |
#37
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Lucifer Morningstar wrote:
On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. You can simply upgrade without losing any data or settings. You may need a licence key if you upgraded free from Windows 7 32 bit. With the Digital Entitlement recorded on the Microsoft server, together with the hardware hash that identifies your machine, you should not need to do that if installing to the same machine. It should activate on its own. Just click Skip and it will figure it out. If you change the motherboard, then the computed hash will not be locatable on the Microsoft server, and some other means will be needed. If you do a brand new install (not a repair or upgrade install) on a virgin computer, then obviously a license key is going to have to come from somewhere. Windows 8 and Windows 10 machines, have an ACPI table called MSDM in the BIOS. That contains a license key. Each BIOS chip has a different key stored in it. For a Windows 10 machine that came with Win10 Pro from the factory, it is that MSDM table that authorizes it. If you want to take a retail Win10 Pro 15063 DVD and reinstall a non-OEM OS, that key will activate it. So as well as Digital Entitlement stored on the server (indexed by hardware hash), really modern machines (that shipped with Win10) also have a key in the BIOS. And that's why those machines no longer have a COA sticker on the outside of the chassis. Paul |
#38
|
|||
|
|||
32-bit operating system to a 64-bit operating system
| And while I am writing, remember that even if you have a 64bit OS
| installed, when you go to run a 32bit program, you will still run into | the 4GB memory limitation. Just something to keep in mind. True, each 32-bit process will have that limitation. But you can have many of those processes running at the same time while using no (or very little) swap space. That can speed things up a good deal. -- Tim Slattery tim at risingdove dot com |
#39
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On Mon, 25 Sep 2017 06:36:45 -0600, Albert
wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display If I upgrade from Windows 10 home to Windows 10 Pro will I be able to change to a 64-bit operating system from a 32 bit operating system during the Pro installation? Albert |
#40
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Albert wrote:
On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display If I upgrade from Windows 10 home to Windows 10 Pro will I be able to change to a 64-bit operating system from a 32 bit operating system during the Pro installation? Albert 32-bit to 64-bit requires clean install. Technically, it doesn't really have to (as Program Files could be migrated to Program Files x86), but that's the way it is. Going the other direction, taking a 64 bit OS to 32 bit, would be a disaster. I don't see the other direction to be quite as tough. You can only do things that the migration logic supported during a Repair or Upgrade installation. That's why these limitations exist. Win7 Sp1 -- Win10 (same bitness) Win8.1 -- Win10 (same bitness) Win10 -- Win10 (same bitness) Win10 was unusual in supporting that many options. Normally, only the previous OS (8.1) would have been supported, but that didn't fit the business plan MS constructed. This article, by Andre the voice of Microsoft, shows there is an Anytime Upgrade inside Win10 Home, to take it to Pro. This would take 32 bit to 32 bit. Or, it would take the 64 bit OS to 64 bit. It doesn't allow changing bitness. It cost $99 to do this, when the difference at the store between Home and Pro is *not* $99. And as you can imagine, such a license key is *bound* to cause problems later. The Windows Media Center on my copy of Win8.1 is like that, and it means extra steps if I ever need to re-install. And with the license server, you never know when something will tip over on you. https://www.groovypost.com/howto/upg...grade-feature/ Notice the comments in there, that the process did not go smoothly. It seemed to get stuck at 100%. If you buy a Win10 license key, you should be able to download any media you need. Which will prevent you from being suckered by "kits" on Newegg, for a variety of prices. You should be able to download a 15063 DVD with x64 Home and Pro, or x32 Home and Pro Two OS flavors fit on one DVD, because most of the files are in common between the two OSes. In your case, you would only use the 64 bit DVD, knowing it can only be used (right now) to do a Clean Install of Pro and start all over again. Being stuck in 32 bit land, for $99, isn't helping. And sooner or later, if you want 64 bit, it means a clean install. When you do a Clean Install, by booting the computer with the DVD you downloaded, you are offered the choice to select Home or Pro on the disc. Some Microsoft DVDs have even more choices, but this one would be a "typical" screen. So this screen shows me starting a Clean Install on this VM. https://s26.postimg.org/4o26ae0tl/Clean_Install.gif Paul |
#41
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Paul wrote in news
Albert wrote: On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display If I upgrade from Windows 10 home to Windows 10 Pro will I be able to change to a 64-bit operating system from a 32 bit operating system during the Pro installation? Albert 32-bit to 64-bit requires clean install. Technically, it doesn't really have to (as Program Files could be migrated to Program Files x86), but that's the way it is. Going the other direction, taking a 64 bit OS to 32 bit, would be a disaster. I don't see the other direction to be quite as tough. You can only do things that the migration logic supported during a Repair or Upgrade installation. That's why these limitations exist. Win7 Sp1 -- Win10 (same bitness) Win8.1 -- Win10 (same bitness) Win10 -- Win10 (same bitness) Win10 was unusual in supporting that many options. Normally, only the previous OS (8.1) would have been supported, but that didn't fit the business plan MS constructed. Some recommendations from personal experience. Don't just backup your system drive before doing a clean install. If you have room in your PC, get another physical drive and add it to your system. Then, depending on the size of the new drive and whatever else you might use it for, either clone your system drive to the new drive, or create a partition on the new drive of appropriate size, and clone the current system drive to there. That way, if (more likely when) the need arises you can quickly look at the old system, and copy any data files that you might need without having to restore a backup. It would probably be a good idea to make that new drive large enough for a second partition that you can clone the new system too as well. If you don't have room to install an additional drive, you could get an external drive, either USB or eSATA, and use it for the cloning. I have supported Windows since version 3.1, and have learned a few things about upgrades and system restorations. The biggest thing is never destroy the original document/file if you don't have to. That way you always have something to go back to if you have to start all over again. And plan before starting, and take copious notes while doing whatever. Trust me, you will NOT remember that important piece of data if you need it later. And save those notes for a while. Sometimes things don't pop up right away, and it helps to have your notes on what you did, how you did it, WHY you did it, and when you did it. Whatever is on your current system drive has value, and may not be replaceable/recoverable. When I was doing this for a living I used to tell people that "Paranoia is a useful trait", 'cause Murphy is out there, and he is an ingenious ******* when making things go wrong. Good luck. |
#42
|
|||
|
|||
32-bit operating system to a 64-bit operating system
On Wed, 27 Sep 2017 14:30:26 -0600, Albert
wrote: On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display If I upgrade from Windows 10 home to Windows 10 Pro will I be able to change to a 64-bit operating system from a 32 bit operating system during the Pro installation? If going from home to pro you will need a pro key. You can upgrade from Windows 10 home to pro using the pro key. Albert |
#43
|
|||
|
|||
32-bit operating system to a 64-bit operating system
Paul wrote:
Albert wrote: On Mon, 25 Sep 2017 06:36:45 -0600, Albert wrote: I have Windows 10 Home with a 32-bit operating system, x64-based processor and I would like to go to a 64-bit operating system. Can I and if so how do I without losing any data on my computer change to a 64 bit operating system. Edition Windows 10 Home Version 1703 OS Build 15063.608 Product ID 00326-10000-00000-AA088 Processor Intel (R) Core (TM) i17-479K CPU @ 4.00 Hz 4.00 GHz Installed RAM 16.0 GB (2.69 GB usable) System type 32-bit operating system, x 64-based processor PN and touch No pen or touch input is available for this display If I upgrade from Windows 10 home to Windows 10 Pro will I be able to change to a 64-bit operating system from a 32 bit operating system during the Pro installation? Albert 32-bit to 64-bit requires clean install. Technically, it doesn't really have to (as Program Files could be migrated to Program Files x86), but that's the way it is. Going the other direction, taking a 64 bit OS to 32 bit, would be a disaster. I don't see the other direction to be quite as tough. You can only do things that the migration logic supported during a Repair or Upgrade installation. That's why these limitations exist. Win7 Sp1 -- Win10 (same bitness) Win8.1 -- Win10 (same bitness) Win10 -- Win10 (same bitness) Win10 was unusual in supporting that many options. Normally, only the previous OS (8.1) would have been supported, but that didn't fit the business plan MS constructed. This article, by Andre the voice of Microsoft, shows there is an Anytime Upgrade inside Win10 Home, to take it to Pro. This would take 32 bit to 32 bit. Or, it would take the 64 bit OS to 64 bit. It doesn't allow changing bitness. It cost $99 to do this, when the difference at the store between Home and Pro is *not* $99. And as you can imagine, such a license key is *bound* to cause problems later. The Windows Media Center on my copy of Win8.1 is like that, and it means extra steps if I ever need to re-install. And with the license server, you never know when something will tip over on you. https://www.groovypost.com/howto/upg...grade-feature/ Notice the comments in there, that the process did not go smoothly. It seemed to get stuck at 100%. If you buy a Win10 license key, you should be able to download any media you need. Which will prevent you from being suckered by "kits" on Newegg, for a variety of prices. You should be able to download a 15063 DVD with x64 Home and Pro, or x32 Home and Pro Two OS flavors fit on one DVD, because most of the files are in common between the two OSes. In your case, you would only use the 64 bit DVD, knowing it can only be used (right now) to do a Clean Install of Pro and start all over again. Being stuck in 32 bit land, for $99, isn't helping. And sooner or later, if you want 64 bit, it means a clean install. When you do a Clean Install, by booting the computer with the DVD you downloaded, you are offered the choice to select Home or Pro on the disc. Some Microsoft DVDs have even more choices, but this one would be a "typical" screen. So this screen shows me starting a Clean Install on this VM. https://s26.postimg.org/4o26ae0tl/Clean_Install.gif Paul For the OP, purchasing the 64 bit media(or license) with the Pro key and should be fine for upgrading the 64 bit capable device to 64 bit Win10. For a user with a OEM Win10 Home device with Product Key chip on board(which takes precedent install and activation) the clean install with 64 bit media may very well end up with Home 64 bit thus necessitating using the Change Product key option to go from Home x64 to Pro x64. -- ...winston msft mvp windows experience 2007-2016, insider mvp 2016-2018 |
Thread Tools | |
Display Modes | Rate This Thread |
|
|