Upgrade Windows XP 32 to XP 64bit

[Relived]

Hey guys,

Is it possible to upgrade from xp pro 32bit to xp 64bit pro,

without having to do an clean install and installing all applications again?

Thanks..

Relived

[Mannlich]

No.

[+jamesyfx Subscriber²]

Besides, most people (including myself) do not recommend Windows XP x64 - there are many many driver and software issues. If you need a 64-bit system, get Windows Vista or wait for Windows 7.

[Budious]

Besides, most people (including myself) do not recommend Windows XP x64 - there are many many driver and software issues. If you need a 64-bit system, get Windows Vista or wait for Windows 7.

Haven't found any software issues myself, in fact, the WoW64 implementation in XP/2003 x64 is a bit more thorough because certain modes and functions were deprecated for Vista that were formerly available in XP and previous editions. Hence some older games using DirectX 3/5 work on Windows XP x64 that do not run on Vista x64 (in some cases importing XP dll's work but not always).

Driver issues were an initial problem only when XP/2003 x64 first came to market because vendors did not have support ready. Nowdays, most reputable hardware vendors offer XP/2003 x64 drivers for their devices.

I'd recommend XP x64, and if I'm not mistaken, there is an upgrade option for Windows XP x86 Professional but not Home versions, etc.

[abecedarian paradoxious]

Technically, you cannot 'upgrade' from any 32 bit Windows to any 64 bit Windows.

So... if you want to be technical- you can't upgrade. You can "export" x86 files and settings, "install" and "migrate" files from the x86 to x64 system ... and maybe even programs (if the programs didn't use 16 bit installers) but in my experience many hardware as well as software vendors straight-up ignored XP64 since it was primarily a business / academic release and either didn't upgrade their installers or didn't offer XP64 drivers for hardware.

For what it's worth, I require the use of a program at work that was compiled in December 2008 and doesn't even consider Vista and won't install on 64 bit systems at all even though it uses a 32 bit installer. How's that for forward thinking?

[Budious]

Technically, you cannot 'upgrade' from any 32 bit Windows to any 64 bit Windows.

So... if you want to be technical- you can't upgrade. You can "export" x86 files and settings, "install" and "migrate" files from the x86 to x64 system ... and maybe even programs (if the programs didn't use 16 bit installers) but in my experience many hardware as well as software vendors straight-up ignored XP64 since it was primarily a business / academic release and either didn't upgrade their installers or didn't offer XP64 drivers for hardware.

For what it's worth, I require the use of a program at work that was compiled in December 2008 and doesn't even consider Vista and won't install on 64 bit systems at all even though it uses a 32 bit installer. How's that for forward thinking?

Right, well after looking around you're probably right about not being able to upgrade. However, transitioning the installed programs from /Program Files/ to /Program Files (x86)/ and moving the existing registry information from the x86 registry to the SysWoW64 node of the x64 registry would in theory yield a functional upgrade.

Compiling the a program to run on x64 and and compiling the installer for x64 interoperbility are separate issues. I have modified old Windows 95 games that were 32-bit but shipped with 16-bit installers to use a new 32-bit installer compiled from a project created in InstallShield, just specify the original files to be bundled, their destination, and the appropriate keys and everything works. This was about three years ago when XP x64 was relatively new as well. Perhaps your employer uses an outdated version of InstallShield to manage installation of their product?

[Lord Ba'al]

Besides, most people (including myself) do not recommend Windows XP x64 - there are many many driver and software issues. If you need a 64-bit system, get Windows Vista or wait for Windows 7.

Nonsense :pinch:

I've been using XP 64 for three years and never had any driver or software issues.

I can only recommend it :cool: (btw, it's actually not XP, but the desktop version of Windows 2003 Server)

[Udedenkz]

Besides, most people (including myself) do not recommend Windows XP x64 - there are many many driver and software issues.

Have you been living under a rock?

[VMIT]

Nonsense :pinch:

I've been using XP 64 for three years and never had any driver or software issues.

I can only recommend it :cool: (btw, it's actually not XP, but the desktop version of Windows 2003 Server)

Because your hardware supports it? And it is XP just the kernal is based off of Server. Quit with the FUD.

[abecedarian paradoxious]

Right, well after looking around you're probably right about not being able to upgrade. However, transitioning the installed programs from /Program Files/ to /Program Files (x86)/ and moving the existing registry information from the x86 registry to the SysWoW64 node of the x64 registry would in theory yield a functional upgrade.

Compiling the a program to run on x64 and and compiling the installer for x64 interoperbility are separate issues. I have modified old Windows 95 games that were 32-bit but shipped with 16-bit installers to use a new 32-bit installer compiled from a project created in InstallShield, just specify the original files to be bundled, their destination, and the appropriate keys and everything works. This was about three years ago when XP x64 was relatively new as well. Perhaps your employer uses an outdated version of InstallShield to manage installation of their product?

I get what you're saying but the company supplying the program uses a 32 bit installer and compiles 32 bit code which should technically work on 32 or 64 bit as you've stated. But even in late 2008, it won't run at all on XP64. They rely on 32 bit drivers for their hardware (which interfaces via USB so we're at a loss). So even in 2008 they won't supply 64bit drivers.

The waters are muddy and suggesting someone can go from x86 to x64 is a crap shoot.

[VMIT]

Have you been living under a rock?

Have you?

[Relived]

Okay guys, thanks for the answers..

I have a licensed 64bit cd laying around and i'm getting many CTD's with memory hog program's so i wanted to upgrade.

Anyways tommorow i will try and see if it works. I will keep you guys updated ;)

[Budious]

I get what you're saying but the company supplying the program uses a 32 bit installer and compiles 32 bit code which should technically work on 32 or 64 bit as you've stated. But even in late 2008, it won't run at all on XP64. They rely on 32 bit drivers for their hardware (which interfaces via USB so we're at a loss). So even in 2008 they won't supply 64bit drivers.

The waters are muddy and suggesting someone can go from x86 to x64 is a crap shoot.

Right, well for smaller proprietary vendors that sell specialized software in conjuction with hardware components such as point of sale workstations, or similar situations I can understand the reluctance to invest any additional development cost for maintaining a x64 driver. If the application does not benefit from additional memory then no reason for the additional overhead in this instance. However, since XP x64 is a compiled workstation version of Windows 2003 Server x64 then any applications or hardware which may rely on server side installations would be more inclined to support a x64 driver model.

[Lord Ba'al]

Because your hardware supports it? And it is XP just the kernal is based off of Server. Quit with the FUD.

Quit your Fud :pinch: You should really put an 'o' in your name, it would be so fitting :laugh:

Oh, and what's a "kernal"? :blink:

It *is* 2003, not XP. It has the same version version as 2003: 5.2 :yes:

Okay guys, thanks for the answers..

I have a licensed 64bit cd laying around and i'm getting many CTD's with memory hog program's so i wanted to upgrade.

Anyways tommorow i will try and see if it works. I will keep you guys updated ;)

Ok. As I said, you're unlikely to have any problems.

[Vakerorokero]

why don't you wait a couple days for windows 7 RC 64? if you machine supports 64bit you will have tons more fun with something that works.

Check if you hardware actually has drivers for it first, any non massively popular won't work, even the ipods have problems.

[Relived]

Hehe, i would like to do it. But since Vista & 7 have limitations on videocard drivers. (you can only have 1 driver with 2 same vc's not 2 different vcs with 2 drivers)

I can't so i have to stick with XP

[abecedarian paradoxious]

Right, well for smaller proprietary vendors that sell specialized software in conjuction with hardware components such as point of sale workstations, or similar situations I can understand the reluctance to invest any additional development cost for maintaining a x64 driver. If the application does not benefit from additional memory then no reason for the additional overhead in this instance. However, since XP x64 is a compiled workstation version of Windows 2003 Server x64 then any applications or hardware which may rely on server side installations would be more inclined to support a x64 driver model.

I'd hardly consider RFS Cablewave a 'small proprietary vendor' considering they sell coaxial cable to AM, FM, TV, CableTV, cellular / mobile phone, and terrestrial as well as satellite communications companied. ;)

[Budious]

I'd hardly consider RFS Cablewave a 'small proprietary vendor' considering they sell coaxial cable to AM, FM, TV, CableTV, cellular / mobile phone, and terrestrial as well as satellite communications companied. ;)

Well they are certainly not alone as major vendors that do not support it either; if it's just a piece of management software for an external device that doesn't benefit from additional memory to improve performance, it's better to avoid having the overhead associated with supporting additional driver models. In fact, I forsee the inclusion of XP Virtual Mode in Windows 7 will probably keep companies such as this from adopting native Windows 7 support and just keeping their XP version maintained to reduce costs.

[notuptome2004]

Hehe, i would like to do it. But since Vista & 7 have limitations on videocard drivers. (you can only have 1 driver with 2 same vc's not 2 different vcs with 2 drivers)

I can't so i have to stick with XP

ok so let me get this right if i may you want to use 2 graphics cards with 2 drivers from 2 different vender's. umm do you mean 2 cards from 2 different manufactures like ATI + Nvidia or 2 different cards same company chipset cause you can SLI and Tri SLI and Quad SLI in vista and windows 7 just fine

please explain

ya know what just upgrade to windows 7 64bit cause windows XP is well old ass and well microsoft has hardly any support for it now and well ya know what Windows XP X64 is hated by most of the damn community out their gamers alike . if you want 2x video cards go buy 2 new nvidia or ATI cards and SLI or crossfire them and i am sure what ever the hek your needs are they will support that and if by chance your only wanting this cause of some old old software you need i am sure ther is something better out now on the market that does a better job

[+jamesyfx Subscriber²]

I knew I'd get some negative responses to my post - there are always some people that have used Windows XP x64 and have had no problems. Congratulations, you're a minority!

But that's why I said 'most people'.

[Budious]

But that's why I said 'most people'.

Most people have never tried to install it. Most people can't identify XP x64 as NT 5.2 codebase. Most people can't explain the difference between XP IA64 and XP x64. Most people repeat word of mouth. So I ignore most people. ;)

[Relived]

Hey guys.. i just installed windows xp 64 clean.

I installed all the drivers and stuff.. and also some programs.

Then now after restarting i get a BSOD saying *** STOP: 0x0000001E (0xFFFFFFFFC0000005,...)

and some more numbers.. anyone know what this means?

Thx

[DDStriker]

^ google is your friend :)

http://support.microsoft.com/kb/307128

http://technet.microsoft.com/en-us/library/cc939475.aspx

[Budious]

Hey guys.. i just installed windows xp 64 clean.

I installed all the drivers and stuff.. and also some programs.

Then now after restarting i get a BSOD saying *** STOP: 0x0000001E (0xFFFFFFFFC0000005,...)

and some more numbers.. anyone know what this means?

Thx

Run a thorough memory diagnostic and make sure your system memory is reliable before researching the particular error code further, but as the previous poster pointed out, Google can tell you far more about specific codes as we can.

[Relived]

Run a thorough memory diagnostic and make sure your system memory is reliable before researching the particular error code further, but as the previous poster pointed out, Google can tell you far more about specific codes as we can.

Anyways guys.. I have started the pc in the morning and it started working fine!

So there we go.. till now its working smooth with all my applications!