Things in Win XP but not in Windows 2003 Server


Recommended Posts

I recently purchased an Asus A6Vm and just because I use Windows Server 2003 as a workstation on my desktop machine, I decided to install the same on my notebook as well. The system is working without any problems, except I can't install the driver for the built in webcam (1.3 MP, USB 2.0 - D-MAX Drivers provided by Asus), I tried it on XP first, and everything is working, but with Server 2003 it simply don't. Did someone tried the same thing and eventually succeed?

The other questions are how to install Adobe Audition and Premiere Pro 2, on Windows Server 2003? The installer just rejects you with the message: "... for Windows XP SP2..."

Thanks.

  • 3 weeks later...
  • 2 months later...

I recently purchased an Asus A6Vm and just because I use Windows Server 2003 as a workstation on my desktop machine, I decided to install the same on my notebook as well. The system is working without any problems, except I can't install the driver for the built in webcam (1.3 MP, USB 2.0 - D-MAX Drivers provided by Asus), I tried it on XP first, and everything is working, but with Server 2003 it simply don't. Did someone tried the same thing and eventually succeed?

The other questions are how to install Adobe Audition and Premiere Pro 2, on Windows Server 2003? The installer just rejects you with the message: "... for Windows XP SP2..."

Thanks.

at least for drivers you can usually unpack files (even .exe with winrar, if they are archives), and then install by using the add hardware wizard and telling it to search in the right directory, or use the .inf file.

I did it for xbox 360 controller, and for a printer.

these braindead installers suck. (and could harm win 2000 and XP SP1 users as well)

you can try the compatibility options for programs, didn't work for me with driver installers.

  • 3 weeks later...

Not sure if this has been mentioned before, but....

After running Server 2003 workstation conversion for the past couple of months, an error on startup produced a message about "fldrclnr.dll could not be loaded" or something. This has to do do with the desktop cleanup wizard. There's 2 ways to get rid of the error.

1. Right-click on the desktop>properties>desktop> and uncheck the "Run Desktop Cleanup Wizard every 60 days" box

2. Or, find a copy of "fldrclnr.dll" from a XP cd, or another pc, and copy it to your C:\windows\system32\ folder. Make sure you cancel any "windows file protection" messages.

  • 2 months later...

Here are some things that are supported in Windows XP but not in Windows 2003 Server. If you've read the thread and still want to configure Windows 2003 server as a workstation, I suggest you read the Windows Server 2003 as a Workstation Guide

link doenst work for me

also Aim Triton doesnt' work after its installed (i ran it with compatibility mode XP) and even before I ran xpconv and after. Anyone?

Edited by RobNyc
  • 2 months later...
  • 4 weeks later...

The other questions are how to install Adobe Audition and Premiere Pro 2, on Windows Server 2003? The installer just rejects you with the message: "... for Windows XP SP2..."

Google Answers your question

Hope that helps, it did with me! :D

  • 3 months later...
Excuse me ! I've read all topics and done a lot things but I cant play Need For Speed Underground 2 and Need For Speed Most Wanted ! What's wrong ! Graphics driver is installed ! Help me !

Thanks in advance !

Did you make sure you got Hardware Acceleration for your graphics enabled?

deltatux

  • 6 months later...
  • 2 years later...
  • 1 year later...
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • In the boot options in the UEFI is set to legacy or CMS? It needs to be set to UEFI if it's not already.
    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!