passionfly,
I meant to say that my mother board has two physical sockets. Each socket has a dual core AMD Opteron processor. In device manager, under processors, it shows:
Dual-Core AMD Opteron Processor
Dual-Core AMD Opteron Processor
Dual-Core AMD Opteron Processor
Dual-Core AMD Opteron Processor
However, in Task Manager the CPU Usuage History only shows two boxes with CPU usuage.
The main recording program I use, has a GUI that shows the real time CPU usuage of each core. (If you have a quad core, 4 separate bars appear).
As of now the program shows only 2 bars when it should be 4.
Keep in mind that I used to use XP64 pro and both the computer and Cakewalk Sonar showed me all 4 CPU usuage meters.
Any help is appreciated.
I'm guessing that everybody on this forum is not in th situation I'm in whereas their motherboard has two physical sockets. Remember, they're showing up in Device manager just not in Task manager. I've done all of the things you've suggested and it's still the same. I know the motherboard has no issues because it worked as a quad core with XP64pro. I've confirmed with a few different people that Windows 7 Home Premium will not support my configuration. Any help is much appreciated.
k, I understand. Since I only have one physical processor socket this guide will work for likewise one processor socket motherboards. Since you have 2 and I completely neglected to include any mention of this I apologize for my mistake and subsequent posts on that topic. I am not 100% positive for the steps necessary to make a double socketed motherboard work since I have no motherboard like this to test it out on.
The one part that I know should work above to get your dual sockets to default status is step 1) Uncheck in MSConfig > Boot tab > Advanced Options > "Number of Processors" and exit MSConfig The other steps are there to forcefully inject the correct core quantities into the OS (registry) substrings via the freeware tool you can download (EasyBCD). Its this part that may fail so you may have to try a different route to assign the correct core total to show up in Task Manager.
Regardless of the amount of physical processor sockets your Mobo has and is correctly being detected by Device Manager, the Task Manager MUST show them correctly or the OS will never take advantage of the true total (hence why I wrote this fix). I would strongly suggest you contact Microsoft Tech Support and tell them you found a very nasty bug in regards to your issue and also refer them to this link that deals with a single processor socket Mobo and not a dual. Their level 3 support engineers should get you a workaround to fix this weird bug.
I'm pretty sure I could fix this problem for you had I a dual socket (and 2 processors) Mobo to test with, but I don't =(