signature="$Windows NT$"
DriverVer=07/01/2001
[hal]
MPS_MP = halmps.dll
MPS_UP = halapic.dll
E_ISA_UP = halstnd.dll
ACPIPIC_UP = halacpi.dll
ACPIAPIC_UP = halaacpi.dll
ACPIAPIC_MP = halmacpi.dll
[ACPIOptions]
ACPIEnable = 2
ACPIBiosDate = 01,01,1999
Extract all HAL files and kernels into system32 and rename them according the names in DTECTHAL.INF. For Windows 2000 take files from SP4.CAB, for Windows XP SP2 from SP2.CAB, for WINDOWS 2003 from SP*.CAB. Files:
halacpi.dll
halapic.dll
halmps.dll
halaacpi.dll
halmacpi.dll
hal.dll----> change to halstnd.dll
ntkrnlmp.exe
ntkrnlpa.exe
ntkrpamp.exe
ntoskrnl.exe----> change to ntkrnlup.exe
==============
- ACPI multiprocessor computer = Halmacpi.dll
- ACPI uniprocessor computer = Halaacpi.dll
- Advanced Configuration and Power Interface (ACPI) computer = Halacpi.dll
- MPS multiprocessor computer = Halmps.dll
- MPS uniprocessor computer Halapic.dll standard computer = Hal.dll
- Compaq SystemPro multiprocessor or 100% compatible = Halsp.dll
==============
read the first replay DAZ posted:
hxxp://support.microsoft.com/kb/324764
This article describes how to disable agp440. you can do the same with intelppm
but its too early for disabling any of these services.
you have to solve it step by step. dont jump in to the middle of the solution. it may not be nessasary or even it may cause new problems.
1. The first concern is about HAL. but since both your old and new mobos are ACPI Multiprocessor mobos, the HAL is the same.
please note that switching between Single Core and Multi Core processors does not cause any problems. Windows will always load the approprate kernel and hal, provided that the underlying harware architecture is the same(ACPI, APIC, PIC,..)
And yes, Hyperthreading is considered multicore.
So HAL is not a problem.
2. The second concern is the presence of critical boot drivers. (SCSI, IDE, RAID, AHCI,...). if thay are not installed windows can not go any further. my previous post contains the solution. I can prepare the registry script and required driver files for you. It will not take much time. but you have to import the settings in to your windows registry before attaching the Harddisk to your new mobo. if the old mobo is still functional, the simplest way to do this is to boot windows by your old mobo, import the settings to the registry and copy driver files to system32\drivers directory and attach the Harddisk to the new mobo. if its not possible to boot by the old mobo, things will get a little tricky but its not too hard. but at this this time I cant go any further. I need to know if your old mobo is functional and you can boot with that or not.
3. After you've done completing the step 2, there is a high chance that windows will able to boot. But if failed, its time to identify the driver(s) that causes the problem. Since you have switched from Intel to AMD, the first candidate is intelppm.sys
and there may be other drivers that will cause the failure. this should be checked after completing step 2.
Motherboard is still able to boot using that hdd. It would be great if you can prepare the registry script, because I've tried to boot using "Disable automatic restart on system failure" and got 0x0000007B(usually SATA driver problems)
sepehrst
17 Jan 2012, 07:21 AM
Here you go:
Generic IDE Registry script and drivers:
http://mediafire.com/file/ayx7s7nhg0742m1/Generic_IDE_Merge.zip
Asus K8U-X M5289 SATA/RAID Controller Registry script and drivers:
http://mediafire.com/file/e7z0do9z3h7l8z9/K8U-X-M5289_SATA-RAID_Merge.zip
As you said, while you are booting with your old mobo you can disable intelppm and agp440 services.
setting the value HKLM\SYSTEM\CurrentControlSet\Services\intelppm\St art to 4 will do the job.
Good Luck.
==============
This method is definately the best way to universal imaging as far as I can see.
How nice it is to: Just deploy any XP image (sysprepped or not, drivers or not) to any (virtual/real) machine and change some files/registry on the harddisk with a universal tool before you boot from it.
BTW, there are already 2 commercial tools doing this:
-Symantec Restore Anywhere
-Acronis Universal Restore
Their disadvantage is that they only handle massstorage and HAL, but don't handle pnpdrivers and they're add-ons to the company's own image-product. (Ghost, True Image)
BUT: You can also write such a tool yourself. It's not rocket science...
detect the HAL from the following key in BartPE:
HKLM\SYSTEM\CurrentControlSet\Enum\Root\ACPI_HAL\0000\HardwareID
and if that does not exist
HKLM\SYSTEM\CurrentControlSet\Enum\Root\PCI_HAL\0000\HardwareID
If the HAL in the offline image is different from the one detected, then extract the right latest HAL + kernel on the offline image (usually SP2.CAB) and rename them to their proper names in C:\Windows\system32
load the C:\Windows\system32\config\system to a temp hive
empty the "Enum" branch in the loaded hive so it will be filled properly at boot.
detect the Processor vendor from BartPE with:
HKLM\HARDWARE\DESCRIPTION\System\CentralProcessor\0\VendorIdentifier
... if AMD then change the Startvalue of the intelppm service to 4 in the loaded hive, otherwise most AMD's will bluescreen.
So... that's pretty much the HAL detection/changing routine
That HAL script you mention in your link does not work when run from BartPE/WinPE, because it does't handle the registry in the offline image... it's also not always right on the HAL to be installed.
Now for the Mass Storage drivers it's more difficult. But basically comes down to: Detect the PNP-ID of the boot-device, find the correct .inf file on a driver distribution share mounted from BartPE and install the .sys, .cat files in the offline image. AND very important to import the proper entries in the CiriticalDeviceDatabase and Services section of the loaded hive so the pc will not get a bluescreen (7B error). To do this is too much to explain here in detail.
PNP-drivers is easy: detect the PNP-IDS of the hardware (also within BartPE) and find their corresponding .inf files (and .dll, .cat, .sys...etc...) in the extracted BTS driverpacks on a distribution share and throw them in the offile image in a folder i.e. C:\drivers.
If mini-setup or OOBE is set to run because sysprep was the last action taken before capturing the image (See certain: HKLM\System\Setup values) then,
Save the HKLM\System\Setup\Cmdline string value of the to i.e. C:\setup.cmd.
Change the value to "C:\mysetup.cmd"
copy over setupcopyoeminf.exe to C:\
Copy over/or create the C:\mysetup.cmd with the following lines:
C:\setupcopyoeminf C:\drivers
call C:\setup.cmd
del C:\*setup.cmd
del C:\setupcopyoeminf.exe
If sysprep was not used, then mysetup.cmd should be set to run from a runonce entry where also devcon.exe is being injected and a "devcon rescan" is being run from within mysetup.cmd
So...I'm probably forgetting some stuff, but that's basically it. A universal XP (image) changer. Let's make this a BartPE plugin called: "SysWrap" :-)
But hey, besides the obvious sys-admins/deployers, it could also be used for people changing motherboards/computer and wanting to keep their installation, and what about P2V, V2P, P2P, V2V.
For an imaging product I definately would use Vista's WAIK "ImageX" or script it's API "WIMGAPI.DLL"
This post has been edited by Scrapple: 12 July 2006 - 12:06 PM
===================
We've been updating HAL on sysprepped image using a .bat file to expand the correct source files into HAL.dll and ntoskrnl.exe. The method I'm talking about is (1) create generic image w/ ACPI HAL (2) blow the image to target computer using Bart and Ghost or rDeploy (3) after imaging, before booting to mini-setup, replace the HAL on target system using the .bat file below. So far, it's been working perfectly on 15 + target models.
There are three things to note about this .bat file:
1) .bat file assumes that the i386 folder from the original windows source disk has been copied to c:\i386 before the system was sysprepped and ghosted. The source files you will need are referenced in the "expand" sections of the script. If you want, you can just copy the files you need from your source disk, put them in a folder somewhere under your sysprep folder, then edit the set source= line to match the path.
2) I was never able to find the correct source file for ntkrnlpa.exe needed by the ACPI Multiprocessor HAL. The file version info lists the source file as ntkrpamp.exe, but was unable to find this file in the XpSp2 source files. So instead I copied the ntkrnlpa.exe from a working XpSp2 halmacpi machine and put it in c:\sysprep\i386\halmacpi\ntkrnlpa.exe. Then I just copy that file instead of expanding.
3) You don't have to run this .bat from Bart - you can run it at the end of sysprep mini-setup by putting the .bat file in c:sysprep\i386\$oem$ and adding the line ".\pickHAL.bat" to your cmdlines.txt. If you do this, I recommend using straight ACPI HAL on your base system before sysprepping. The ACPI HAL appears to allow mini-setup to run for most models, then the .bat file runs after mini-setup to replace the HAL before first windows boot.
***************************************
@echo off
REM choose HAL after mini-setup
REM expands correct dll from i386 folder to c:\windows\system32\hal.dll (can set alternate source below)
REM set source path - no trailing slash, use quotes around long paths
REM Dest needs to be c:\windows\system32
set source=c:\i386
set dest=c:\windows\system32
:reset
cls
set hal=
:menu
echo.
echo Please select the correct HAL for this system
echo.
echo Choose 1-5
echo.
echo 1 ACPI PC
echo 2 ACPI Uniprocessor PC
echo 3 ACPI Multiprocessor PC
echo 4 Standard PC - Use only on old PC systems if ACPI (#1) does not work
echo.
echo.
if .%hal% == . set /p hal= ?
if "%hal%" == "1" goto :1
if "%hal%" == "2" goto :2
if "%hal%" == "3" goto :3
if "%hal%" == "4" goto :4
goto :menu
:1
REM Advanced Configuration and Power Interface (ACPI) PC - Standard PC (ACPIPIC_UP)
expand %source%\Halacpi.dl_ %dest%\hal.dll
expand %source%\ntoskrnl.ex_ %dest%\ntoskrnl.exe
goto :eof
:2
REM ACPI Uniprocessor PC (ACPIAPIC_UP)
expand %source%\Halaacpi.dl_ %dest%\hal.dll
expand %source%\ntoskrnl.ex_ %dest%\ntoskrnl.exe
goto :eof
:3
REM ACPI Multiprocessor PC (ACPIAPIC_MP)
expand %source%\Halmacpi.dl_ %dest%\hal.dll
expand %source%\NTKRNLMP.EX_ %dest%\ntoskrnl.exe
copy /y c:\sysprep\i386\halmacpi\ntkrnlpa.exe %dest%\ntkrnlpa.exe
goto :eof
:4
REM Standard PC (Non ACPI PC) - for PC Jadul beut
expand %source%\Hal.dl_ %dest%\hal.dll
expand %source%\ntoskrnl.ex_ %dest%\ntoskrnl.exe
goto :eof
***********************************************************
===================
Problems when Windows XP tries to load the Agp440.sys service
Article ID: 324764 - View products that this article applies to.
System Tip
This article applies to a different version of Windows than the one you are using. Content in this article may not be relevant to you. Visit the Windows 7 Solution Center
This article was previously published under Q324764
The quick way:
1) Boot PC dgn CD Windows XP
2) Pilih masuk Recovery Console (R)
3) ketik : listsvc (enter)
4) ketik : stop agp440 (enter)
5) ketik exit (enter)
Untuk mendisable service "intelppm.sys" (driver prosesor Intel)
ketik: stop intelppm (enter)
exit (enter)
Kasus yang biasa terjadi yang disebabkan oleh masalah diatas adalah:
ketika kompi master WinXP dibuat di kompi berprosesor Intel dicloning ke kompi bermesin (pros) AMD.
=========
Fix for continuous reboot after installing Service Pack 3 in Windows XP
After contacting HP Technical Support and speaking to a supervisor we were able to solve the problem of Windows continuously rebooting after installing SP3. Here are the steps that fixed the problem with my HP Pavilion running on an AMD processor. The steps are actually fairly straight forward and easy....
Issue:
The computer reboots continuously after installing Windows XP service pack 3
Computer reboots continuously after installing Windows XP service pack 3 on AMD systems. The problem is that with some configurations, SP3 causes the computer to crash during boot, and Windows XP, by default, is set up to automatically reboot when it crashes. That is why you end up in the endless rebooting scenario.
Cause:
On HP computers, the same Windows installation disc image for Intel processor based PC's is deployed for the AMD processor based computers as well. Because the original installation image for both Intel and AMD is the same, all have the intelppm.sys driver installed and running. That driver provides power management on Intel-based computers. On an AMD-based computer, amdk8.sys provides the same functionality for power management.
Symptoms:
Ordinarily, having intelppm.sys running on an AMD-based computer appears to cause no problems. However, on the first reboot after a Service Pack 3 installation, it causes a big problem. The computer either fails to boot, or crashes with a STOP error code of 0x0000007e.
You may not see the error code because the computer reboots too fast. In order to get the error message, you need to set an option during startup. To do so, open the windows advanced menu by tapping the f8 key on startup. Then select the "Disable automatic restart on system failure" option.
Solution:
If you have an AMD-based computer, however, you do not need the intelppm.sys driver and can disable it. There are three methods in order to do this.
Step 1: Please try to log on the system in safe mode.
1. While using Safe mode open the command prompt.... Start, All Programs, Accessories, Command Prompt
Run the following command in the command prompt just like it's typed: sc config intelppm start= disabled
Step 2:
If the issue persists, please try to log on or boot the system in recovery console (refer to the web document)
2. Using recovery console:
If you booted into the recovery console, from a command prompt, type: disable intelppm
Step 3: Please check in registry.
3. Using windows registry:
- Run regedit
- Click on HKEY_LOCAL_MACHINE
- From the File menu, select "Load hive"
- Navigate to %systemdrive%\Windows\System32\Config on the dead (crashed) system and select the file name "System" (without extension)
- Name it something you can remember, such as "Offline"
- Navigate to Offline\ControlSet001\Services\IntelPPM
- Double click the Start value and set it to "4" --> to disable service
- If you did what I did and completely messed things up by running a disk check previously, navigate to:
- "ControlSet001\Control\SessionManager". Open the "BootExecute" value and clear out the autochk entries.
- Repeat steps 6-8 for the other control sets.
- Reboot
From CMD console, run these two commands:
reg add HKLM\System\CurrentControlSet\Services\Intelppm /v Start /d 4 /t REG_DWORD
sc config intelppm start= disabled
Reference:
http://support.microsoft.com/kb/888372
Additional information:
Computer Restarts after Displaying Stop Error 0x0000007E (After Updating with Service Pack 3 for Windows XP):
http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=c01457284&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN
For future reference: Service pack 3 Installation steps:
Before installing the service pack 3 update, please follow the steps listed above and save yourself much time and effort.
To uninstall service pack 3, I suggest that you uninstall it from add/remove programs.
Step 1:
Uninstall service pack 3 from add/remove programs:
1. Click Start.
2. Select Run.
3. Type appwiz.cpl in the run field.
4. Click OK.
5. Click change or remove programs.
6. Select the program -service pack 3 that you want to uninstall or remove.
7. Click Remove button.
8. It will pop up the message stating that "Are you sure you want to remove the programs".
9. Click Yes. It will help you to remove or uninstall the installed programs from add and remove programs.
Step 2: If the issue persists, I suggest you to perform system restore and then try to install the service pack 3 after performing the steps mentioned above in regards to removing the intelppm.sys Driver.
Using Microsoft System Restore in Windows Me and XP:
http://h10025.www1.hp.com/ewfrf/wc/genericDocument?docname=bph07103&cc=us&dlc=en&lc=en&jumpid=reg_R1002_USEN
Step 3:
How to obtain the latest Windows XP service pack :
http://support.microsoft.com/kb/322389/
Steps to take before you install Windows XP Service Pack 3:
http://support.microsoft.com/kb/950717/en-us
I hope this helps someone who is having this problem. It sure took me a minute to get it all figured out. :0)
==============
Scenario 2
Source computer: ACPI Uniprocessor (ACPI APIC UP)
Destination computer: ACPI Multiprocessor (ACPI APIC MP)
In this scenario, use the following entry:
UpdateHal=ACPIAPIC_MP, %windir%\inf\hal.inf
Note This entry is required only for Windows 2000 Server. Windows XP and Windows Server 2003 automatically upgrade to the ACPI Multiprocessor HAL.
==============
4. Add a switch to BOOT.INI:
multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect /detecthal
TO DISABLE AUTOMATICALLY RESTART DURING WINDOWS START-UP ERROR:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\CrashControl]
"AutoReboot"=dword:00000000
From now on, when a problem causes a BSOD or another major error that halts the system,
the PC will not automatically reboot. Rebooting manually will be necessary.
==================
HOW TO SET AUTOLOGON FOR ADMINISTRATOR DURING WINDOWS LOGON
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultUserName=Administrator
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\DefaultPassword=admin
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoAdminLogon="1"
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\AutoLogonCount="3"
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\ForceAutoLogon="1"
HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\IgnoreShiftOverride="0"
No comments :
Post a Comment
Silahkan kasih komentar atau pertanyaan Anda.