Switching to AMD Dual Core CPU without re-installing Windows

[Markoul]

UPDATE: Just to make it clear this thread here applies only for people whose computers report as "Advanced Configuration and Power Interface (ACPI) PC" and had like to switch to "ACPI Multiprocessor PC" or "ACPI Uniprocessor PC" without re-installing windows.

In any other case no additional action should be taken as windows will automatically detect the new X2 dual core cpu installed in their system.


Yesterday i changed my Athlon 3200+ cpu over to a dual core Athlon X2 4200+.

The thing was that my existing Windows XP Pro installation was without  ACPI enabled therefore i had a maximum  of 15 interrupts  and only one of the two cores was enabled at windows (windows task manager showed only one cpu graph).

A quick search to the internet showed that the only feasible solution was to re-install windows   

...solution i was not very happy with...

Further search revealed that the missing "halmacpi.dll" was responsible for my troubles and this could only fixed by installing windows...

...well WRONG!!...

just follow the procedure described in this page here...

How to change between hals without re-installation / repair.

Typical (and worst possible) method to change hal is to repair or reinstall whole system.
Task a little time consuming and not particulary healthy for system itself. Here is better one,
suggested by me few times on this forum. This mini-guide is based on w2k+sp3, but with
minor modifications should apply to XP (directories, different cab, maybe some tinkering with
XP's famous anty piracy *cough* protection).

• from \WINNT\Driver Cache\i386\sp3.cab (I assume sp3 is installed), extract following files:
  
  halacpi.dll
  halaacpi.dll
  hal.dll (and rename to halpic.dll)
  
  copy those files to \WINNT\system32 (or \WINDOWS\system32)
  
  In case some other servicepack is installed, you should use appropriate spX.cab. Also if you have none of them installed, use driver.cab. Be careful about hotfixes - some of them might update specific hal files as well. In that case, you should choose the latest file possible.
  
  
• add to boot.ini floowing lines, remembering to keep numeric values (denoted as 'x') with proper values, specific to your system
  
  in case of windows 2k (usually):
  
  multi(x)disk(x)rdisk(x)partition(x)\WINNT="ACPI+APIC" /fastdetect /hal=halaacpi.dll
  multi(x)disk(x)rdisk(x)partition(x)\WINNT="ACPI+PIC" /fastdetect /hal=halacpi.dll
  multi(x)disk(x)rdisk(x)partition(x)\WINNT="non-ACPI" /fastdetect /hal=halpic.dll
  
  and in case of windows xp (usually):
  
  multi(x)disk(x)rdisk(x)partition(x)\WINDOWS="ACPI+APIC" /fastdetect /hal=halaacpi.dll
  multi(x)disk(x)rdisk(x)partition(x)\WINDOWS="ACPI+PIC" /fastdetect /hal=halacpi.dll
  multi(x)disk(x)rdisk(x)partition(x)\WINDOWS="non-ACPI" /fastdetect /hal=halpic.dll
  
  Now you can switch in bios ACPI and APIC options to you liking.
  
  
• after you succesfully boot you system, you can update driver under Manage -> Device Manager -> Computer,
  so default hal.dll is updated properly (although it's not required). After this step, you can use
  default boot option again.
  
  

Remarks:

- in case M$ releases some pre-sp4 hotfix with modified hal files in some future, you should take specific files from that hotfix.

I'll update this guide (or add separate) with short sysprep manual, which can be used as tool to force full pnp rescan of system and as tool to change ide drivers between different mainboards.

I take no responsibility for all above, if you damage your system. I used it many times both at home and with laboratories at university with no problems. At least one person from forum used it as well.

NOTE: You can easily edit the boot.ini by right-clicking on "My Computer" --> Properties --> Advanced --> Startup and Recovery --> Settings --> Edit

Best Regards,

Manolis aka Markoul

NOTE1: don't forget to add also halmacpi.dll to the above three dlls described in the procedure (4 dlls in total). When you first boot after you edit the boot.ini you choose which hal.dll . Usually it is the halmacpi.dll  but sometimes it can be the halaacpi.dll, repeat until you find the correct dll and your machine boots normally. After that you reboot once more but this time with the default boot screen option "Microsoft Windows XP Professional". Don't forget to delete the added lines after that in the the boot.ini

NOTE2: Usually boot partition is c: therefore as an example the string attribute,

multi(x)disk(x)rdisk(x)partition(x)\WINDOWS="ACPI+APIC" /fastdetect /hal=halaacpi.dll

should be written in the boot.ini as below:

multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="ACPI+APIC" /fastdetect /hal=halaacpi.dll

[Built2Last]

Markoul, Good find. Do I sense a sticky in this post's future?

[Markoul]

Built2Last,

I think there are many people who don't like the idea of re-installing windows and all their third party applications and all the SP3 Internet updates so far.

Yes i believe it would useful to put this as a sticky.

Markoul

[simonmpoulton]

Hi
Most informative might be handy when i change mine to a 4800+ X2! Just a quick question though in device manager under "Computer" What is listed???

[Markoul]

Computer must be shown as

"ACPI Multiprocessor PC"

Anything else is wrong. Try to do right click there update the driver (select "i will choose a location"). If it is not listed there then you have to do the procedure described and change manually the hal.dll or re-install.

Best Regards,

Markoul

[RumaNoV]

Thanks for the information, a bit too late for me because i reinstalled a month ago to run my dual core. Now I'm going to install my dual core in another system and I'm going to place a single core CPU in my system for testing purpose.

Which procedure do I have to follow then ?

[Markoul]

RumaNoV,

To go to single core cpu choose in the boot screen tha halacpi.dll or if this does not work the choose the halpic.dll as described.

Take care,

Markoul

[simonmpoulton]

Worked Perfectly! It's just a pity my windows needed reinstalling anyway 

[Svet]

Hi mates,

switching to ACPI Multiprocessor PC need to use correct kernels also, specified hal is not enough cause they use different kernels too.

Advanced Configuration and Power Interface (ACPI) PC  & ACPI Uniprocessor PC  use the same kernels, etc: only specify hal is enough:
in boot.ini ---> /hal=halacpi.dll (for Advanced Configuration and Power Interface (ACPI) PC) and /hal=halaacpi.dll (for ACPI Uniprocessor PC)
NOTE: files should already exist into system32 folder. file version should match with currently version installed. if you got SP2 get files from here:
"C:\WINDOWS\Driver Cache\i386\sp2.cab", open with winzip and get correct hal which you need:
Advanced Configuration and Power Interface (ACPI) PC  ----> halacpi.dll
ACPI Uniprocessor PC ------->  halaacpi.dll
ACPI Multiprocessor PC -------> halmacpi.dll
or use microsoft expand if you don't have winzip:
cmd, go to C:\WINDOWS\Driver Cache\i386\
type from there:
expand sp2.cab -F:myhal.dll c:\windows\system32
where myhal.dll= your chosen hal (halacpi.dll, halaacpi.dll or halmacpi.dll)
for XP without SP2, same procedure but look for HAL files into "\I386" XP installation folder(and those syntax from there:)
expand HALACPI.DL_ %systemroot%\system32\HALACPI.DLL
or expand HALMACPI.DL_ %systemroot%\system32\HALMACPI.DLL
or expand HALAACPI.DL_ %systemroot%\system32\HALAACPI.DLL
or to force directly to default hal:
booting from recovery console command prompt, or from other location and load NTFS mounter with read&write NTFS support:
navigate to root OS drive and go to OS root directory(%windir%) into system32 folder:
example: (where C is OS root drive, and "windows" is OS root folder)
C:
cd windows\system32
ren hal.dll hal.old
cd "c:\windows\driver cache\i386"
expand sp2.cab -F:myhal.dll c:\windows\system32    /* where myhal.dll should be replaced with one of chosen hal: halacpi.dll, halaacpi.dll or halmacpi.dll */
cd "c:\windows\driver cache\i386"
ren myhal.dll hal.dll  /* where myhal.dll should be replaced with one of chosen hal: halacpi.dll, halaacpi.dll or halmacpi.dll */

for ACPI Multiprocessor PC we need to update kernels too, go to c:\windows\system32 and make backup 1st: (under pure DOS, or different OS)
force ACPI Multiprocessor PC:
cd c:\windows\system32
ren ntkrnlpa.exe ntkrnlpa.old
ren ntoskrnl.exe ntoskrnl.old
ren hal.dll hal.old                                 /* backup hal too, gona replace it also */
cd "c:\windows\driver cache\i386"
expand sp2.cab -F:halmacpi.dll c:\windows\system32
expand sp2.cab -F:ntkrpamp.exe c:\windows\system32
expand sp2.cab -F:ntkrnlmp.exe c:\windows\system32
cd c:\windows\system32
ren halmacpi.dll hal.dll
ren ntkrpamp.exe ntkrnlpa.exe
ren ntkrnlmp.exe ntoskrnl.exe

reboot PC you have done, no modification into boot.ini is required. at XP startup will detect new hal installed and will be asked for reboot. you have switched to ACPI Multiprocessor PC.

other method is to specify into boot.ini (make backup of currently hal.dll, ntkrnlpa.exe, ntoskrnl.exe, extract correct version of ACPI Multiprocessor PC files(from correct location depend of SP1/2 or without), ntkrpamp.exe become as ntkrnlpa.exe and copy it into \system32 folder, halmacpi.dll and ntkrnlmp.exe copy to \system32 folder too.) boot.ini modification:
add as parameters:
/HAL=halmacpi.dll /kernel=ntkrnlmp.exe

you can review default HAL files and restore it if you don't have backup(if you skip or forgot to make backup) from looking here: \Windows\Repair\Setup.log search for "HAL" inside will find original file name locations.
also HAL query can be obtained from this registry key: HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID

[ant177]

Has anyone else experienced issues with their graphics cards stopping working once a dual core processor has been installed?
I am using a MSI K8N Neo2 Platinum and have just upgraded to an AMD X2 4600+, now my X1950 graphics card isn't functioning and is failing at startup with the error code 43 in device manager.
This isn't an isolated issue as I've seen a number of people with the same problem but no one seems to be able to resolve it.

Does anyone have any suggestions how I can resolve this problem without having to disable one of the cores on my new processor (which is what I'm doing at the moment)?

I am running the release version of Vista Ultimate however I have seen complaints that this problem also occurs in Windows XP.
Regards,
Anthony Williams

[Markoul]

BOSSKILLER,

Thank you for your very informative addition to the original post of this thread, however i have changed in my case when switching to the ACPI Multiprocessor PC -------> halmacpi.dll only the hal  without bothering about the kernels.

I checked on the 2 kernels internal names (via properties menu) and they are both check fine as they should be:

ntkrnlpa.exe checks out as ntkrpamp.exe
ntoskrnl.exe checks out as ntkrnlmp.exe   

So why in my case manually changing the 2 kernels was not needed as you describe above?

... but this was obviously done automatically by windows when it saw the new hal...

Best Regards,

Manolis aka Markoul

[Svet]

BOSSKILLER,

Thank you for your very informative addition to the original post of this thread, however i have changed in my case when switching to the ACPI Multiprocessor PC -------> halmacpi.dll only the hal  without bothering about the kernels.

I checked on the 2 kernels internal names (via properties menu) and they are both check fine as they should be:

ntkrnlpa.exe checks out as ntkrpamp.exe
ntoskrnl.exe checks out as ntkrnlmp.exe   

So why in my case manually changing the 2 kernels was not needed as you describe above?

... but this was obviously done automatically by windows when it saw the new hal...

Best Regards,

Manolis aka Markoul

Hello,
i have tried directly with specify HAL only,(halmacpi.dll in boot.ini) like you described, but that cause reboot when starting to load OS. when correcting kernels goes smooth.

Best Regards

[Markoul]

Hello,
i have tried directly with specify HAL only,(halmacpi.dll in boot.ini) like you described, but that cause reboot when starting to load OS. when correcting kernels goes smooth.

I see,

Must have something to do with what the original ACPI configuration was, mine was "Advanced Configuration and Power Interface (ACPI) PC" before switching to "ACPI Multiprocessor PC" by changing hal.

From your signature i see that you do not have a dual core cpu. Did you try changing hal in a single core cpu system? because that might explain things...

...if that is your case the procedure you describe is valid for people with single core cpus and non- APIC window installations (number of interrupts limited to 15) who desire to enable APIC without re-installing windows.

Furthermore, this explains why windows did not automatically updated the 2 kernels you describe since it never detected a X2 dual core cpu in your system therefore manually updating the 2 kernels was the right thing to do as you did in your case.

Fascinating Discovery 

Thanks,

Markoul

[Svet]

mine was also "Advanced Configuration and Power Interface (ACPI) PC", changed to "ACPI Multiprocessor PC" at single CPU.

"Did you try changing hal in a single core cpu system? because that might explain things..."
yep can be perhaps, OS do not detect X2 CPU and do not copy new kernels and cause reboot, sound sense, have to be forced manually

[alg7_munif]

Does this applies when I'm changing my 3800 X2 to an Opteron 175? Thanks.

[Svet]

Does this applies when I'm changing my 3800 X2 to an Opteron 175? Thanks.

nop, should not change it. both are X2 and should use the same: "ACPI Multiprocessor PC"

[Odranoel1]

Hello Folks

I was about to drop a 4400 X2 in my my system (3700 right now, single core).
I am by far not an expert. Can you please help me understand the procedure again?

I am using Win XP SP2 and the system properties say "single processor ACPI PC".

When clicking on "show driver details, I get the following list:
hal.dll
ntkrnlpa.exe
ntoskrnl.exe

1) The goal is to provide the proper (multiprocessor-ready) version of "hal" but without reinstalling. This requires us to fool the system by renaming the multiprocessor version as if it were the uniprocessor driver, correct?

2) What happens next, after the system has booted successfully? This is the part of the procedure that I did not understand.

3) If I do this, do I need to update kernels or not? That does sound a bit scarier to me. I would hate to mess it up and have to reinstall: my system has dual SATA drives and I run into a LOT of misery making it boot on the proper partition every time I reinstall.

As a side note, I think the above info is VERY useful, and it would be worthwhile summarising the whole thing in ONE well structured post without cut and paste, something like an "Idiot's guide to going dual core".

Have a wonderful 2007 and thanks a lot for sharing this.

Odranoel 1 

[Svet]

Hello Odranoel1,

just install new CPU and follow standard way update HAL to "ACPI Multiprocessor PC". guide above is how to be forced is something goes wrong.
also you may have a look here for latest M$ Dual Core Patch: http://forum-en.msi.com/index.php?topic=103843.0

[Odranoel1]

Thank you Bosskiller. I have managed to install successfully without resorting to above procedure so far. However, i think I need the dual core patch from microsoft and cannot get it: I have a french version of XP Pro / SP2 and the english language patch is rejected. In order to get the french patch I need to contact M$ support and pay them some money (?)

[Svet]

Thank you Bosskiller. I have managed to install successfully without resorting to above procedure so far. However, i think I need the dual core patch from microsoft and cannot get it: I have a french version of XP Pro / SP2 and the english language patch is rejected. In order to get the french patch I need to contact M$ support and pay them some money (?)

"In order to get the french patch I need to contact M$ support and pay them some money (?)"
nop, here i get and upload french version for you:
WindowsXP-KB896256-v4-x86-FRA.exe

[dead_rabbit]

Is this procedure applicable from socket A to AM2 system?

[Odranoel1]

Bosskiller... thank you m8
I will try it tonight and let you know if I can get more performance out of da thing.

Best regards

[Svet]

Is this procedure applicable from socket A to AM2 system?

yes can be used, but you will have problem with chipset drivers. reboot at XP load is expected. new clean OS installation is recommended.

Bosskiller... thank you m8
I will try it tonight and let you know if I can get more performance out of da thing.

Best regards

you are welcome mate. 

[enablerbro]

I was looking into upgrading my current system and, apart from knowing how to bolt it all together, I'm not very computer literate.  Am I right in saying I could remove my single core CPU and swap it for a dual core one?  My hardware manager says that my computer is a "ACPI Uniprocessor PC" is this relevant to what I would need to do to get my system to accept the change in CPU?  I am unsure about memory, my brother said that if I were buying a new CPU and mobo I'd also need new memory (ddr2), would that still be correct?

I was thinking of getting anAthlon 64 X2 4800+ Socket 939, ToledoCore, 2x 2.4GHz, 2MB Cache, am I right in thinking it would be compatible with my neo4?

 

[Svet]

"Am I right in saying I could remove my single core CPU and swap it for a dual core one?"
yes
"My hardware manager says that my computer is a "ACPI Uniprocessor PC" is this relevant to what I would need to do to get my system to accept the change in CPU? "
after switching to X2 CPU, windows should automatically detect changes and install "ACPI Multiprocessor PC" if not do it manually.
"I am unsure about memory, my brother said that if I were buying a new CPU and mobo I'd also need new memory (ddr2), would that still be correct?"
if you use s.939 board and corespond CPU you need DDR1, if you switch to AM2 board(s.940) and corespond CPU you will need DDR2.

[enablerbro]

after switching to X2 CPU, windows should automatically detect changes and install "ACPI Multiprocessor PC" if not do it manually.
if you use s.939 board and corespond CPU you need DDR1, if you switch to AM2 board(s.940) and corespond CPU you will need DDR2.

So as long as I get an s939 I can keep my current memory and I shouldn't need to do anything other than maybe install "ACPI Multiprocessor PC" if Windows doesn't automatically detect it?  Doesn't sound too painful.  Thanks for the swift reply.

[Svet]

So as long as I get an s939 I can keep my current memory and I shouldn't need to do anything other than maybe install "ACPI Multiprocessor PC" if Windows doesn't automatically detect it?  Doesn't sound too painful.  Thanks for the swift reply.

yep if your currently memory is DDR1 that is what you need.

[Markoul]

ooops!

it is a long time i've last visited this forum, seems i have totally missed to support some guys 

my apologies...

Thanks to Bosskiller for taking care of this thread here   

Just to make it clear this thread here applies only for people whose computers report as

"Advanced Configuration and Power Interface (ACPI) PC" and had like to switch to

"ACPI Multiprocessor PC" or "ACPI Uniprocessor PC" without re-installing windows.

In any other case no additional action should be taken as windows will automatically detect the new X2 dual core cpu installed in their system.

Take Care,

Markoul

[Built2Last]

edited out by B2L

[Markoul]

done. 

Built2Last,

Thanks for the Great Tip!   


Markoul

[enablerbro]

Well my new CPU arrived today and Windows recognised it, so no problems there. 

Now though I have an alarm sounding from Core Centre. CPU fan is listed as 3000+ rpm and NB 8000, is that normal?  I also fitted an Enermax Liberty 500, I don't think that could be causing the problem.

 

[Built2Last]

enablerbro, Core Center is not without faults i.e. it sets off for no apparent reason even if everything is ok. If you are looking for a monitoring program try "Speed Fan". It shows fan speeds, temps, volts, etc and is way more reliable than CC.

[enablerbro]

enablerbro, Core Center is not without faults i.e. it sets off for no apparent reason even if everything is ok. If you are looking for a monitoring program try "Speed Fan". It shows fan speeds, temps, volts, etc and is way more reliable than CC.

I shall give that a go, thanks.

[enablerbro]

Solved bleeping.  Had plugged PSU fan connector into SFAN1, unplugged it and bleeping stopped.  New problem.  PC boots up fine, no bleeping from Core but when I try to play a video file (Divx, AVI) the PC restarts.

I get an error msg on startup WER59e2.dir00\Mini012907-04.dmp, I've googled it and read lots of stuff but none seem to help.

[Svet]

Solved bleeping.  Had plugged PSU fan connector into SFAN1, unplugged it and bleeping stopped.  New problem.  PC boots up fine, no bleeping from Core but when I try to play a video file (Divx, AVI) the PC restarts.

I get an error msg on startup WER59e2.dir00\Mini012907-04.dmp, I've googled it and read lots of stuff but none seem to help.

open a new thread in A64 NV(http://forum-en.msi.com/index.php?board=28.0) and describe the problem, also read Moan Guide and provide full system specification including PSU details(can be found on the PSU sticker). example into my signature.

[enablerbro]

Will do 

[enablerbro]

 

[cedricn]

Is there anything that needs to be done under Vista? Running 3200+ and considering upgrading to X2 4400+.

[B00gjuice]

When I went from an FX 55 to an FX 60 (dual core), Windows XP SP2 booted in and detected the processor just fine and worked dual core just fine.

[kangi26]

Markoul,

I am curious, I have a MSI K8N- Neo4 Plat V1.0 and a X2 3800+. During the POST there is only 1 CPU detected, and when it goes into Windows(XP Pro w/ SP2); the task manager and CPUID only show 1 CPU. BUT, during POST, if I restart the system, it'll then detect 2 CPU's as will Windows Task Manager and CPUID.
Will the fix you have detailed above fix this issue? Or am I dealing with something different?