• 0

STEAM Installation

Asked by InternalStorm,

 Share

Question

21 answers to this question

Recommended Posts

  • 0
Grand Master

Martog

Posted
Posted

Alright, here we go again, Adobe Creative Suite 2 does NOT like (X86) either, damn it microsoft, that was a poor choice of characters. i would have been fine with "Program Files x86" or something like that, the characters kill other programs. Microsoft shouldn't known that not all programs like () in the path name. A lot do not mind, but some do, IE Steam, CS2 (I don't know if older products are affected)

  • 0
Grand Master

Nexus-

Posted
Posted
Alright, here we go again, Adobe Creative Suite 2 does NOT like (X86) either, damn it microsoft, that was a poor choice of characters. i would have been fine with "Program Files x86" or something like that, the characters kill other programs. Microsoft shouldn't known that not all programs like () in the path name. A lot do not mind, but some do, IE Steam, CS2 (I don't know if older products are affected)

585931483[/snapback]

Anytime you run into an issue installing to "Program Files(x86)" just replace that part of the path with "progra~2" and it will work.

585854047[/snapback]

  • 0
Collaborator

casao

Posted
Posted
Alright, here we go again, Adobe Creative Suite 2 does NOT like (X86) either, damn it microsoft, that was a poor choice of characters. i would have been fine with "Program Files x86" or something like that, the characters kill other programs. Microsoft shouldn't known that not all programs like () in the path name. A lot do not mind, but some do, IE Steam, CS2 (I don't know if older products are affected)

585931483[/snapback]

Adobe is notorious for crappy installers. Infact, when installing the entirety of CS2, there's no way to select individual options for programs, you either install the whole program or not at all. You have to go to the specific program installer to select things like integration and such.

  • 0
Collaborator

Gobelet

Posted
Posted

Since 64-bit programs are newer, I don't understand why they didn't put "Program Files (x64)" for them. I mean, knowing the new restrictions, people who make 64-bit software should know about it, and fix the problem if there was one. But Microsoft did the contrary, and therefore added a big problem for a lot a programs, it seems.

  • 0
Grand Master

Vykranth

Posted
Posted
Since 64-bit programs are newer, I don't understand why they didn't put "Program Files (x64)" for them. I mean, knowing the new restrictions, people who make 64-bit software should know about it, and fix the problem if there was one. But Microsoft did the contrary, and therefore added a big problem for a lot a programs, it seems.

585969337[/snapback]

Because Windows x64 is designed to FIRST run x64 applications, x86 applications can be

used because the OS can handle them but it is a convenience.

The Program Files (x86) is provided for another reason: it is a extremely bad idea to mix x64 and x86 dlls, especially in C:\Program Files\Common Files: you don't want to mix x86 and x64 InstallShield runtimes or MS services

Same reasons why the System32 and SysWOW64 DLLs directories are separated.

Finally, I am terribly sorry but I have to say that Microsoft must not be blamed if some bad developers cannot write installers properly. The brackets are valid directories and files names characters since at least Windows NT 4.0 and that's 1996 .....

  • 0
Neowinian

Aryaniae

Posted
Posted

Short of poor coding there should be no reason that any app would have a problem installing into a dir even with (x86) in the name. There are all valide characters for folders and files.

They are valid characters for FS node names on Windows. It is a great deal simpler for those of us who write apps for more than one OS to not support them at all, rather than add checks all over our code to see if they're supported by whatever OS it's running on.

It is generally considered good coding practice to have your program follow the most restrictive set of rules, not the least. In this case, that means that FS node names may only have alphanumerics, underbars, hyphens, and periods.

This topic is now closed to further replies.
 Share
Go to question listing

  • Recently Browsing   0 members

    • No registered users viewing this page.

  • Posts

    • The official Funny Pictures thread

      By +Edouard · Posted

    • what other retro software do yall use

      By Som · Posted

      My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC

      By hellowalkman · Posted

      Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • EA Sports UFC 6 review: Brutal, satisfying, and surprisingly accessible to newcomers

      By Nick H. · Posted

      Bugger, you beat me to it!
    • EA Sports UFC 6 review: Brutal, satisfying, and surprisingly accessible to newcomers

      By +Good Bot, Bad Bot · Posted

      I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.

  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done

  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
    Show More

  • Tell a friend

    Love Neowin? Tell a friend!