Nicolas 2000 wrote on 2025-09-15, 06:40:

xelizor wrote on 2025-09-14, 22:26:

Nicolas 2000 wrote on 2025-09-14, 20:59:

What do we think of this one, apart from the fact it's dirt cheap? :) You can see all the specs in the photos. […]
Show full quote

What do we think of this one, apart from the fact it's dirt cheap? 😀 You can see all the specs in the photos.

https://www.2dehands.be/v/computers-en-softwa … 2819-desktop-pc

-Runs Debian, but irrelevant as I'll install XP.
-AMD instead of intel, problem for compatibility? And fast enough, too slow, too fast?
-Radeon HD6850 seems XP compatible, good choice?
-onboard audio as far as I can see. I could always add the Audigy from the Dell.
-no idea about HDD and RAM, but given the age of the system, I'd assume plenty for an XP build?

Great opportunity, switch the cpu for a Phenom II (either X2 or X4), I would go with X2 honestly as they're more power efficient and plenty for XP gaming. Make sure it has 4GB at least (it should, it most likely has 8GB already)... Just put an SSD to install the OS, and then use the HDD to store the gamez! Cheers

What would be the motivation for swapping out the current processor, is it too slow/too fast/incompatible? I understand winxp can't use the six cores very well, but how bad would it be compared to a phenom x2?

And, as I'm new to AMD, can a Phenom 2 be dropped into an FX socket?

It seems that the AMD FX process scheduling do not work properly under XP, that's the main reason... Not sure the impact it might have on a real scenario but I would avoid any potential incompatibilities or incoherent performance. IPC wise it's also better on Phenom II... On the same region of the latest Core 2. You can try the AMD FX, coming from a P4 you probably won't notice any difference on most cases... But then you can later on "upgrade" to Phenom II and compare then, for 5$ or something.

Regarding the socket, yes... They're all within AM3 Standard.

Just don't forget to install your Audigy on there too!

Best regards

It looks like I'm going after that AMD desktop! When I have it I'll try it first to see if things work OK, then I'll hunt down a more suitable processor.

Some BIOSes have an option for 1 thread per core, that would tidy up the FX6100 nicely for XP, but it's not as common as just being able to reduce the cores

And if that doesn't work out, Phenom II are cheap.

Nicolas 2000 wrote on Yesterday, 06:42:

And if that doesn't work out, Phenom II are cheap.

Unless you want an X6, and for XP, that would be under utilized, unless really forcing it, XP's multithreading rarely gets much beyond one foreground and one background, so an X4 would have legroom to spare, even an X3 or possibly an X2 would be worth considering, but between X2 and X3, I'd take the extra one for luck, doesn't hurt to have spare threads unless it's at the cost of a lot of money or a significant drop in clock speed - and the X4 is cheap and has decent clocks.

It's not that you can't run XP on an AMD FX, but as it doesn't know cores/threads it would probably run 2 threads on core 1, unless you absolutely barrage everything with affinity settings

Nicolas 2000 wrote on 2025-09-16, 19:58:

It looks like I'm going after that AMD desktop! When I have it I'll try it first to see if things work OK, then I'll hunt down a more suitable processor.

Good choice, I'm confident that you won't regret it! Just tell us how it went in the future... Best regards!

Matth79 wrote on Yesterday, 14:17:

Nicolas 2000 wrote on Yesterday, 06:42:

And if that doesn't work out, Phenom II are cheap.

Unless you want an X6, and for XP, that would be under utilized, unless really forcing it, XP's multithreading rarely gets much beyond one foreground and one background, so an X4 would have legroom to spare, even an X3 or possibly an X2 would be worth considering, but between X2 and X3, I'd take the extra one for luck, doesn't hurt to have spare threads unless it's at the cost of a lot of money or a significant drop in clock speed - and the X4 is cheap and has decent clocks.

It's not that you can't run XP on an AMD FX, but as it doesn't know cores/threads it would probably run 2 threads on core 1, unless you absolutely barrage everything with affinity settings

I don't think your impression of Windows XP multitasking is exactly right. Windows XP, like all versions of NT, will send threads to multiple processors or cores as long as it's working with multithreaded workloads. You can see this in well coded benchmarks with multithreaded support (such as CPU-Z) where multithreaded scores for XP should roughly match newer operating systems as long as the number of cores and clock speeds remain consistent. I will grant that the thread scheduler in XP is pretty unoptimized. Newer operating systems attempt to identify the nature of each thread and attempt to route it to the best suited logical processor/core. XP, on the other hand, just assigns threads to processors/cores in numerical order (CPU 0, then CPU 1, then CPU 2, etc.). XP still assigns threads to multiple processors/cores as needed, though.

Windows XP SP3 is also "Hyperthreading Aware". In ACPI mode, XP can detect Hyperthreading support and attempt to route threads to physical processors/cores first before assignment to logical processors. That prevents two threads going to the same physical processor/core before loading an unused processor/core. MPS mode does not support Hyperthreading for any operating system that I'm aware of.

Windows 2000 is "Hyperthreading Compatible". In ACPI mode, Windows 2000 cannot detect Hyperthreading and instead assigns threads to logical processors in numeric order. If the ACPI tables list the physical processors/cores numerically first in the table (followed by the virtual processors), then two threads should not go to the same physical processor/core before loading an unused processor/core. If the table lists the virtual processor right after the corresponding physical processor/core, then two threads will go to the same physical processor/core before loading an unused processor/core. It's up to the board manufacture to implement the ACPI CPU list in the BIOS (most list the physical processors/cores first, fortunately).

An interesting aspect of modern, high-speed CPUs is that they tend to finish threads very quickly. The CPU actually sits ideal a lot of the time and has to wait to receive the next thread instead of the OS waiting to send the next thread. Older video games have similar behavior. Only until very recently have games actually driven multiple threads. Older games are almost entirely single threaded, so you really only need a single fast core for gaming (other cores can handle the background tasks). That's why Intel for years touted their single threaded performance for game enthusiasts.