Recommended Posts

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.

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.

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?

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?

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)

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.

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.

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.

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.

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. ;)

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.

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

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'.

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.

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!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • As I've been usually saying lately - we all can thank "AI" for this.
    • Friday Windows 11 preview builds are here. Insiders in the Experimental (formerly Dev) and Beta Channel can download builds 26300.8697 and 26220.8690. My Windows11 device on the Preview Channel just got 26220.8728. My guess is this build is a nightly update from 26220.8690.
    • Traffic has a surprisingly unexpected impact on your surroundings by Sayan Sen Image by Radik 2707 via Pexels A collaborative study by researchers from several Israeli institutions found that everyday pollution from traffic and industrial activity measurably changed the atmospheric electric field over the Tel Aviv metropolitan area, providing new evidence of how human activity can influence the lower atmosphere. The research was led by Dr. Roy Yaniv of the Hebrew University of Jerusalem and the Gertner Institute at Sheba Medical Center, Dr. Assaf Hochman of the Fredy & Nadine Herrmann Institute of Earth Sciences at the Hebrew University, and Prof. Yoav Yair of Reichman University. The study also involved Itay Froomer, a student from Hadera High School and the Israeli Museum of Medicine and Science (Technoda), who carried out the work as part of the Ministry of Education's 5-unit physics research track. The researchers focused on the atmospheric electric field under fair-weather conditions. Even in the absence of storms, a weak electric field naturally exists between Earth's surface and the atmosphere. One of the main ways scientists measure this field is through the Potential Gradient (PG), which is the inverse of the vertical component of the electric field. PG is a key part of the global electric circuit, a planet-wide system of electrical currents maintained by thunderstorms and electrified clouds around the world. Scientists have long known that the atmospheric electric field can be influenced by factors ranging from large-scale atmospheric processes to local weather conditions such as dust, fog and clouds. Human-made pollution is also known to play a role, but understanding exactly how urban emissions affect the electric field close to the ground has remained an area of ongoing research. To investigate this relationship, the team analyzed measurements from a newly installed electric field mill, an instrument used to continuously monitor the strength of the atmospheric electric field. The instrument was installed at the Center for Technological Education (Roter House) in Holon and became operational in August 2024. It was funded by Israel's Ministry of Education and the Holon municipality. The electric field mill forms part of a broader monitoring network that includes nearby meteorological stations and air-quality monitoring sites. This allowed researchers to compare electric field measurements with detailed weather data and pollution records to better understand what was driving changes in the Potential Gradient. The study focused on two major urban pollutants: fine particulate matter (PM2.5) and nitrogen oxides (NOx), both commonly produced by vehicle traffic and industrial activity. PM2.5 refers to microscopic airborne particles small enough to remain suspended in the atmosphere for extended periods, while NOx is a group of gases released during fuel combustion. Researchers examined daily, weekly and seasonal patterns in the atmospheric electric field and compared them with changes in pollutant concentrations. Their analysis revealed a clear relationship between NOx levels and changes in the Potential Gradient, particularly during morning and evening rush hours when traffic emissions were at their highest. “What we observe is a direct physical link between emission peaks and electrical variability,” explained Dr. Roy Yaniv. “NOx reduces atmospheric conductivity very quickly, so the electric field responds almost instantaneously during traffic rush hours.” Atmospheric conductivity describes how easily electrical charges move through the air. According to the researchers, nitrogen oxides rapidly alter this conductivity, causing a near-immediate response in the electric field. PM2.5, however, was associated with a delayed response. The researchers attributed this difference to the particles' longer atmospheric residence time, meaning they remain in the atmosphere for longer periods, as well as their different microphysical interactions with surrounding air and atmospheric components. The study also identified a pronounced "weekend effect." In Israel, traffic volumes and some industrial activity decline significantly on Fridays and Saturdays. During these periods, concentrations of both NOx and PM2.5 dropped, and corresponding changes were observed in the atmospheric electric field. “The weekend signal demonstrates just how sensitive the electric field is to changes in human activity,” the researchers noted. “When emissions decline, the electrical environment adjusts at once, providing a high-resolution indicator of urban atmospheric conditions.” The findings showed that pollution levels can influence not only the chemical composition of the atmosphere but also its electrical properties. Researchers said the results strengthened the case for using atmospheric electricity as an additional tool for environmental monitoring, particularly in densely populated urban areas where anthropogenic, or human-caused, influences are most pronounced. The study also pointed to potential public health applications. By combining air-quality measurements with observations of atmospheric electricity, researchers said they could gain a more complete picture of how urban atmospheric conditions change over time. “Integrating air-quality data with electric-field measurements gives us a clearer picture of how the lower atmosphere evolves moment by moment,” the researchers added. “It’s a framework that can support both scientific insight and practical environmental decision-making.” Beyond the scientific findings, the project highlighted a collaboration between universities, public institutions and secondary education. Researchers said the work demonstrated how students could take part in real-world environmental research while contributing to studies of air quality, atmospheric processes and their potential effects on society. Source: Hebrew University, ScienceDirect This article was generated with some help from AI and reviewed by an editor. Under Section 107 of the Copyright Act 1976, this material is used for the purpose of news reporting. Fair use is a use permitted by copyright statute that might otherwise be infringing
    • We aren't even at the all-star game and Microsoft is talking about an update that will most likely be released during the World Series if not after. A lot can happen in the world between now and the 2026 World Series, including the 2026 FIFA Cup. Tell me about it again after the FIFA Cup is concluded. That should allow plenty of time to prepare for it.
    • Great, tell me when I have a "Bad Pool Caller" elsewhere not in Windoze.
  • Recent Achievements

    • Week One Done
      AMV earned a badge
      Week One Done
    • One Month Later
      AMV earned a badge
      One Month Later
    • Collaborator
      ryansurfer98 went up a rank
      Collaborator
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      542
    2. 2
      +Edouard
      186
    3. 3
      Michael Scrip
      77
    4. 4
      PsYcHoKiLLa
      77
    5. 5
      Steven P.
      71
  • Tell a friend

    Love Neowin? Tell a friend!