讓XP/2000也可以Ghost到不同晶片組

藍鯨

字體大小 16px

10px 32px

人家說 ==> 三個臭皮匠勝過一個諸葛亮
也難怪大陸那邊的人可以想出這樣的"怪招" (因為有十億個嘛?...呵~開玩笑的)
來破XP/2000不能"夠"(Ghost)到不同晶片組的限制
不得不令我由衷的佩服!!

我自己親身的體驗過後,整理出下面簡單的步驟
有玩組裝的人,至少可以省下你安裝軟體三小時的時間唷^^

XP/2000系統完全安裝完後
包括你常用的工具軟體也一起安裝進去
但是注意:先不要裝所有的驅動程式

接著到裝置管理員
照下面步驟做完
中途有要求重新開機皆取消

1,修改 IDE ATA/ATAPI控制器 為 標準雙通道PCI IDE控制器
   不可有任何(ALi,VIA,SIS,Intel,nForce)等關鍵字在裡頭

2,修改 電腦 為 Advanced Configuration and Powerful Interface (ACPI) PC
   如果你原先的是 ACPI Uniprocessor PC, 照樣改成上面這個
   原因嘛...相容性較高(我自己測試的結果)

3,打開每一個樹狀列,把有(ALi,VIA,SIS,Intel,nForce)等關鍵字的裝置一律砍
   帶有問號的裝置也砍

4,關閉電腦

5,備份

然後就皆大歡喜啦

如果你的朋友的電腦太舊
不支援ACPI的話
那麼建議你做兩份
其中一份照著上面做
另一份的第二步驟改成 標準 PC
相容性高的不可言諭
但是你要關機的時候
您可以放心關機
嘿嘿嘿!!久違的大字出現在你面前
真的第一片無法相容時,才試著用第二片
萬一都不行那只好乖乖重灌了

下面是另一個方法:
解除2000認硬體的方法
1.你確定在這個目錄裡（your_drive:winntsystem32drivers）
  是否有這四個檔案
  atapi.sys
  intelide.sys
  pciide.sys
  pciidex.sys

  如果沒有的話，請找到這個檔案（your_drive:winntDriver Cachei386driver.cab）
  把那四個sys檔copy至 your_drive:winntsystem32drivers
2.將下方的文件處理一下存成mergeide.reg並執行
這樣子你的2000作業系統就可以ghost到其他不同硬體的機器了

個人測試過2000/xp都可行

微軟官方資料
"STOP 0x0000007B" Error After Moving Windows 2000 System Disk to Another System

--------------------------------------------------------------------------------
The information in this article applies to:

Microsoft Windows versions 2000, 2000 SP1 Advanced Server
Microsoft Windows versions 2000, 2000 SP1 Professional
Microsoft Windows versions 2000, 2000 SP1 Server

--------------------------------------------------------------------------------


SYMPTOMS
After you move the system (boot) disk to a backup computer, you may receive the following message on your Windows 2000 computer when you try to start the backup computer:

***STOP: 0x0000007B (0xF741B84C,0xC0000034,0x00000000,0x00000000)
INACCESSIBLE_BOOT_DEVICE



CAUSE
The registry entries and drivers for the mass storage controller hardware in the backup computer are not installed in Windows 2000.

For integrated device electronics (IDE) controllers, there are several different chip sets available, such as Intel, VIA, and Promise. Each chip set uses a different Plug-n-Play (PNP) ID to identify it.

The PNP-ID information of mass storage controllers for the backup computer must be in the registry prior to startup for Windows 2000 to initialize the correct drivers.



RESOLUTION
The supported method of moving a Windows 2000 installation to new hardware is documented in the following Microsoft Knowledge Base article:

Q249694 How to Move a Windows 2000 Installation to Different Hardware
However, for quicker disaster recovery, follow these steps:
Use identical hardware for the backup computer.


Replace the problem hardware components in the backup computer with the same manufacturer make and model as the components in the computer you are backing up.


Use the same make and model of small computer system interface (SCSI) controller in the new computer, if the system disk is a SCSI disk.


Use the same kind of motherboard that has the same kind of IDE chip set, and the same PNP-ID as the original, if the system disk is an IDE disk.


For SCSI-based system disks, you can prime the registry, and ensure that the drivers you want are in place by installing the SCSI controller that is used by the backup computer before you transfer the system disk contents. Windows 2000 PNP will detect the controller, set up critical registry entries, and copy the appropriate driver.

After you see the SCSI controller in Device Manager, you can safely remove the alternate controller. If, at a later time, you need to move the system drive to another computer with that make and model of SCSI controller, Windows 2000 will start successfully because it has already used that controller once, and has retained the correct configuration information.



MORE INFORMATION
Although Microsoft does not support this method, it is possible to import, or to merge the required registry entries, and copy the drivers ahead of time to support all IDE controllers that are natively supported by Windows 2000. This method may enable the moved system drive to start successfully, but other hardware differences may result in other problems.

This solution will provide support for IDE controllers whose PNP-ID matches the following list. However, if you want to determine ahead of time which IDE controllers are used in your current, and backup computers, you can search the Systemrootsetupapi.log file for the PNP-ID detected during Setup.

After you determine which PNP-IDs are used in your computers, you can choose to merge, or populate the registry with only the PNP-IDs that you need.

The following list is a list of the PNP-IDs of natively supported IDE controllers in Windows 2000:

   ;***********(Standard IDE ATA/ATAPI controllers)*********
   Primary_IDE_Channel=%systemroot%infmshdc.inf
   Secondary_IDE_Channel=%systemroot%infmshdc.inf

   ;*********** Generic_ESDI_Hard_Disk_Controller **********
   *PNP0600=%systemroot%infmshdc.inf

   ;*********** Aztech IDE Controller **********************
   *AZT0502=%systemroot%infmshdc.inf

   ;*********** Device ID for generic Dual PCI IDE *********
   PCICC_0101=%systemroot%infmshdc.inf

   ;************Acer Labs Inc ******************************
   PCIVEN_10B9&DEV_5215=%systemroot%infmshdc.inf
   PCIVEN_10B9&DEV_5219=%systemroot%infmshdc.inf
   PCIVEN_10B9&DEV_5229=%systemroot%infmshdc.inf

   ;************Appian Technology **************************
   PCIVEN_1097&DEV_0038=%systemroot%infmshdc.inf

   ;************CMD Technology *****************************
   PCIVEN_1095&DEV_0640=%systemroot%infmshdc.inf
   PCIVEN_1095&DEV_0646=%systemroot%infmshdc.inf

   ;************Compaq *************************************
   PCIVEN_0E11&DEV_AE33=%systemroot%infmshdc.inf

   ;*************Intel *************************************
   PCIVEN_8086&DEV_1222=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_1230=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_7010=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_7111=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_2411=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_2421=%systemroot%infmshdc.inf
   PCIVEN_8086&DEV_7199=%systemroot%infmshdc.inf

   ;*************PC Technology *****************************
   PCIVEN_1042&DEV_1000=%systemroot%infmshdc.inf

   ;*************Silicon Integrated System *****************
   PCIVEN_1039&DEV_0601=%systemroot%infmshdc.inf
   PCIVEN_1039&DEV_5513=%systemroot%infmshdc.inf

   ;*************Symphony Labs *****************************
   PCIVEN_10AD&DEV_0001=%systemroot%infmshdc.inf
   PCIVEN_10AD&DEV_0150=%systemroot%infmshdc.inf

   ;*************Promise Technology ************************
   PCIVEN_105A&DEV_4D33=%systemroot%infmshdc.inf

   ;*************VIA Technologies, Inc. ********************
   PCIVEN_1106&DEV_0571=%systemroot%infmshdc.inf
To import this information, use the following procedure on two different test computers that exhibit the "stop 0x0000007B" error message after changing drives between computers. After you follow this procedure on each test computer, you should be able to move the hard disks, and start both computers without receiving the "stop 0x0000007B" error message. However, other hardware differences may result in other problems.
Copy the following information into Notepad, and then save the file on a 3.5-inch disk. Name the file mergeide.reg, without the .txt file name extension.


********* START COPY FROM HERE *************
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabaseprimary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasesecondary_ide_channel]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase*pnp0600]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabase*azt0502]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="atapi"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasegendisk]
"ClassGUID"="{4D36E967-E325-11CE-BFC1-08002BE10318}"
"Service"="disk"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#cc_0101]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_0e11&dev_ae33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1039&dev_0601]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1039&dev_5513]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1042&dev_1000]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_105a&dev_4d33]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1095&dev_0640]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1095&dev_0646]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1097&dev_0038]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_10ad&dev_0001]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_10ad&dev_0150]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_10b9&dev_5215]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_10b9&dev_5219]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_10b9&dev_5229]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="pciide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_1106&dev_0571]
"Service"="pciide"
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_1222]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_1230]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_2411]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_2421]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_7010]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_7111]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlCriticalDeviceDatabasepci#ven_8086&dev_7199]
"ClassGUID"="{4D36E96A-E325-11CE-BFC1-08002BE10318}"
"Service"="intelide"

;Add driver for Atapi (requires atapi.sys in drivers directory)

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesatapi]
"ErrorControl"=dword:00000001
"Group"="SCSI miniport"
"Start"=dword:00000000
"Tag"=dword:00000019
"Type"=dword:00000001
"DisplayName"="Standard IDE/ESDI Hard Disk Controller"
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,61,00,74,00,61,00,70,00,69,00,2e,
  00,73,00,79,00,73,00,00,00

;Add driver for intelide (requires intelide.sys in drivers directory)

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesIntelIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000004
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,69,00,6e,00,74,00,65,00,6c,00,69,
  00,64,00,65,00,2e,00,73,00,79,00,73,00,00,00


;Add driver for pciide (requires pciide.sys and pciidex.sys in drivers directory)

[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetServicesPCIIde]
"ErrorControl"=dword:00000001
"Group"="System Bus Extender"
"Start"=dword:00000000
"Tag"=dword:00000003
"Type"=dword:00000001
"ImagePath"=hex(2):53,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,
  52,00,49,00,56,00,45,00,52,00,53,00,5c,00,70,00,63,00,69,00,69,00,64,00,65,
  00,2e,00,73,00,79,00,73,00,00,00
************ END COPY HERE ***************
Extract the Atapi.sys, Intelide.sys, Pciide.sys, and Pciidex.sys files from the SystemrootDriver Cachei386driver.cab file, or copy them to the Systemrootsystem32drivers directory from the most recently installed Service Pack distribution media (if the Service Pack is already installed on your computer).


In Windows Explorer, right-click the Mergeide.reg file in the floppy drive, and then click Merge. Windows 2000 will display the following message:
Are you sure you want to add the information in a:mergeide.reg to the registry?
Click Yes.

After the import process is completed, Windows 2000 will display another message:


Information from a:mergeide.reg was successfully entered into the registry.
Shut down, and then turn off the computer, and move the system disk drive to the other test computer that previously produced a "stop 0x0000007b" error message, and then see if you can successfully start the second computer.



Additional query words: eide 0x7b chipset setupapi Atapi Intelide Pciide Pciidex

Keywords : kbenv
Issue type : kbprb

ovsmowen

聽起來滿好玩的樣子  改天有時間來試試看

hummoon2

太高深了，看不懂。但也謝過。]

2003-06-17.

lrs12345

沒玩過快學起來謝謝拉

webyang

沒試過,真的這樣就可以了嗎??

謝謝分享.

kaku

並不十分了解，但終於解開酗[的疑惑!
多謝高手的指點。

ucch

真有一套

refuce

剛好可派上用場.試試囉***

chungjac

後面的官方文件是什麼,可以說明一下
謝謝

tpss12

連這個方法連想出來，
真是厲害哦!!!!
不過應該是try很久才得到的結果吧!!!!!

sky0510

好好玩滴感覺...
改天也要玩看看~~

newp

困擾大家好久的問題了耶
有解決的辦法真好
謝謝分享喔

pyh

儲存下來慢慢研究
謝謝分享了

taiku

沒有聽過這套軟體, 下載來看看好了......thanks

sane

又學起來了...
TXH

shau

困擾大家好久的問題了耶
有解決的辦法真好
謝謝分享喔

roverto

謝謝分享.
這辦法真好

studim

如果真的可以就
太棒了,以後重還
原就好,謝了...

a8329630

如果可以作成程式執行檔較方便
還是不很懂

haibow

好厲害阿
這樣就不用擔心我的電腦升級還要重新安裝WINXP了