First post, by infiniteclouds
Windows XP spans such a wide timeline of games -- are there any well known instances where a (XP) game doesn't play well with anything but single-core?
Windows XP spans such a wide timeline of games -- are there any well known instances where a (XP) game doesn't play well with anything but single-core?
A second CPU (or core) marginally increases scheduler overhead, so if you have a strictly single-threaded game and the PC is doing nothing else besides running it, it will be very slightly faster on the single core/CPU system.
I would say no. There are games that don't respond well to being shuffled between cores, but the solution is to either set core affinity in the task manager or use one of those ancient tools that do it for you.
I would not trade the benefit of a MUCH more responsive system when using at least a dual core for having to play around with settings and tools for the few games that don't like multi core CPUs, but your mileage may vary
I haven't seen any game like that. It is generally OS that handles running multiple threads either on single core or on multiple cores. Not saying it is impossible to have such a bug, but I don't know how I could make something like that happen
Also, the first very common dual core was the core 2 duo, which, even if running only one core, would run circles around anything older than it.
So no real advantage to using one of the older processors for windows XP, unless you are explicitly trying to hit a lower performance target.
wrote:I haven't seen any game like that. It is generally OS that handles running multiple threads either on single core or on multiple cores. Not saying it is impossible to have such a bug, but I don't know how I could make something like that happen
Fallout 3 didn't like running on my quad core system until I set the affinity to 2 cores only for it.
Games based on the Allegro 4 game programming library and its GUI routines have problems with multi-threading of any kind. The mouse cursor drawing code can start drawing to the screen at times when it is not allowed to: crash. Cannot fix it with core affinity, but hacking the dll to force it to directdraw emulation mode seems to work pretty well.
--> ISA Soundcard Overview // Doom MBF 2.04 // SetMul
I'd still wager that the vast majority of single threaded applications (but not all) should not have problems running on a dual core system. Outside of what's listed, I would still make my selection based on the performance needs. For a system running games for 2005 or earlier, the fastest P4 or Athlon 64 is all you need anyway and you shouldn't have any problems running any 32 bit win9x/2000/xp code. Outside of multitasking in the OS, I can't think of any games during this time period that used parallel processing yet.
The single core can have an advantage if it has the higher clock speed / IPC e.g., a Pentium 4 HT 3.8ghz will get higher frame rates in most time period games than a Pentium D 645 3.4ghz dual core. Tack on a few compatibility issues with multi-cores and you have your advantages.
When we look at 2007 and beyond (Crysis...), the dual core really becomes a necessity for good performance anyway, and any benefit of the single core (compatibility) will be lost in performance on newer software.
So one could argue that for absolute compatibility and 'advantages' in XP, you would have to break it apart into two machines. For MOST realistic use, a dual core pc is fine for anything windows XP has to offer. I actually use a Core 2 Quad Q9400 with triple boot Win XP x86, Win7 x64, Debian 64 bit and I'm happy as a clam, I play Redneck Rampage on it one minute and the next I'm browsing, chatting, and doing my programming projects on the latest Debian.
Sup. I like computers. Are you a computer?
I don't know about xp, but fallout 3 worked fine in win7 and quad core system.
wrote:I don't know about xp, but fallout 3 worked fine in win7 and quad core system.
I'm not aware that fallout 3 had issues with more than 2 cores either. That being said nowadays it has a whole zoo of other problems. At least the steam version does, the GOG version runs out of the box.
I had to disable the second core in the BIOS to get Prince of Persia: Warrior Within running on a Dell D630 laptop (C2D) a few years ago. I thought it was a pretty new game (2004) to be exhibiting that issue. No idea if that holds true for all machines.
twitch.tv/oldskooljay - playing the obscure, forgotten & weird - most Tuesdays & Thursdays @ 6:30 PM PDT. Bonus streams elsewhen!
wrote:I had to disable the second core in the BIOS to get Prince of Persia: Warrior Within running on a Dell D630 laptop (C2D) a few years ago. I thought it was a pretty new game (2004) to be exhibiting that issue. No idea if that holds true for all machines.
I played that not too long ago on my i7-4790k. I didn't finish it but it ran fine throughout. I have the steam version, not sure what kind of patch history that game has.
Sup. I like computers. Are you a computer?
Yeah I was running the completely un-patched original DVD release. It was on a work trip in the boonies & I had no internet. 😜
twitch.tv/oldskooljay - playing the obscure, forgotten & weird - most Tuesdays & Thursdays @ 6:30 PM PDT. Bonus streams elsewhen!
wrote:wrote:I don't know about xp, but fallout 3 worked fine in win7 and quad core system.
I'm not aware that fallout 3 had issues with more than 2 cores either. That being said nowadays it has a whole zoo of other problems. At least the steam version does, the GOG version runs out of the box.
Certainly could have just been my experience..... Blame Bethesda 😀
wrote:Games based on the Allegro 4 game programming library and its GUI routines have problems with multi-threading of any kind. The mouse cursor drawing code can start drawing to the screen at times when it is not allowed to: crash. Cannot fix it with core affinity, but hacking the dll to force it to directdraw emulation mode seems to work pretty well.
What are some examples of these games?
My current system from 2014 is an Ivy-E... 4802K/760 GTX... but unfortunately this motherboard has no PCI slots and without EAX there's little point to me even bothering trying to install XP on here. I would say that compatibility is probably a greater concern than speed just because there are so many games with no advantage to running in XP over 7. Is any card that is fully supported by XP (including older titles) going to run Crysis at max settings,AA/1080p? I wouldn't try to do it just to say I did. I would say whatever the most demanding game that supports EAX is would be my goalpost for the top end.
wrote:wrote:Games based on the Allegro 4 game programming library and its GUI routines have problems with multi-threading of any kind. The mouse cursor drawing code can start drawing to the screen at times when it is not allowed to: crash. Cannot fix it with core affinity, but hacking the dll to force it to directdraw emulation mode seems to work pretty well.
What are some examples of these games?
Mostly free games from hobby programmers:
https://www.allegro.cc/depot/index/rate
I used Allegro 4 to make a game called Heroquest and a game map editor/viewer called TFDtool. And they both had the mentioned multi-threading issues. The developers acknowledged it as well, but since allegro 5 is out nobody feels like fixing up v4. Allegro 5 has no GUI routines etc. So one cannot simply compile software written for v4 to use v5.
--> ISA Soundcard Overview // Doom MBF 2.04 // SetMul
I remember Star Wars: Knights of the Old Republic started having trouble when I upgraded from single core Athlon XP to Intel Q9550 quad core, had to make the game run on one core to fix it. I think that has been the only game I've played that didn't like multi core cpu at all.
That was with retail copy and Windows XP. Modern operating systems might not have similar problems, and also GOG version doesn't care how many cores you have and presumably neither does Steam version.