Im from Windows wrote on Yesterday, 19:46:MagefromAntares wrote on Yesterday, 18:26:
You can use CPU-Z to identify the processor:https://www.cpuid.com/softwares/cpu-z.html
I was more thinking along the lines of actual looking at it, its selft to tell me what it is. or viewing system requirements or something in the BIOS rather then a 64 bit program that will not run on my machine
Actually 32-bit versions of CPU-Z is still available, it is only the default which is 64-bit, in-fact there is a vintage edition for Win9X computers too. However if you have WinXP and you just want to check if the CPU has HT or multiple cores you can open the "Task Manager", click on the "Performance" tab and if there is more than one graph under the CPU usage history it means there are either more than 1 Cores or in case of HT more then 1 thread of execution.
Im from Windows wrote on Yesterday, 20:38:MagefromAntares wrote on Yesterday, 09:27:
Pentium 4 processors often have Hyperthreading, which works like a virtual second CPU (It is actually a way to schedule operations from two threads simultaneously,
zapbuzz wrote on 2026-06-14, 04:15:
they do not like more than 1 core CPU's
I found out! its a Pentium 4 . so no good then? unless anyone knows how to trick it in the BIOS?
If it is a Pentium 4 that supports HT, chances are that the motherboard BIOS contains a setting to disable Hyperthreading, motherboard BIOS manufacturers like to put it into different options however so you might have to look around for it in the BIOS a bit. Most often it is called by its Intel name, Hyperthreading or shortened to HT, but sometimes it goes by the name of "Core Multi-Processing" or something similar when MB makers get creative with the naming.
The interesting thing is that WinXP lets you pin a process to a single core in the "Task Manager", but only after it is started, so if the program cannot start that feature doesn't help, Windows 2000 came with a utility called IMAGECFG.EXE which let you set an executable to be pinned to certain cores on a multiprocessor system, but weirdly Microsoft decided to not include it in WinXP. Also even more weirdly after they realised that programs might need to run on a single core when starting they made a utility called "psexec" that supported setting this, but that utility only supports Win 8.1 or later, so they kinda left WinXP users to disable Hyperthreading in BIOS or use third-party tools.
"A process cannot be understood by stopping it. Understanding must move with the flow of the process, must join it and flow with it." - Dune