/ fshoeyellow92's Library/ Notes/ The hardware operation of the Ghost system disk is driven ahead of time. The particular operations and principles of .DLL file backup and recovery three.txt
The hardware operation of the Ghost system disk is driven ahead of time. The particular operations and principles of .DLL file backup and recovery three.txt
from web site
Section 1: Very first talk nonsense
I always see some netizens online saying that it truly is too difficult to make the Ghost version with the system disk...I tell you that it is not hard at all. A set of tutorials looks incredibly difficult, and it is actually very very simple to appear at separately. You will find a great deal of issues You would have, you appear in the following 4 items. Not surprisingly, it is also quite difficult to do, we will not discuss it for the time getting. The technique we are speaking about now could make a great Ghost program disk so long as you make it carefully. It's versatile, speedy and stable. (The Ghost-XPsp2 membership research method disk I created generally uses this approach, but it can be a tiny extra complex, and it's controlled by xplode. Considering the fact that it was released in January, I made use of it to set up dozens of units, and no blue screen phenomenon was identified. Exceptional, mother machine-VIA motherboard, CPU two.66). It really is advised to utilize a computer with P4-CPU-2.4G or higher, preferably a Through motherboard, which features a powerful versatility.
The process of packaging program: (XPVSP2 as an example) Install the system-patch-install the software-lose weight-system optimization and settings-install the background image setup.BMP below system32-delete the hardware driver and adjust the IDE ...Transform the pc...——remove the garbage—defragmentation—run SRS—decompress DEPLOY.CAB—drive the operation ahead of time see section III—run setupmgr to make an automatic answer inf file—run msprep dragon Empire package program-autohal1 import registry-DLL file backup-completed.
[1] You need to set up the system, the original version of WindowsXP (installation version, typically CD to start DOS installation), install the computer software to set the system optimization.
[2] It is actually not hard to streamline the system (you are able to do it with tools).
[3] It's not hard to delete the hardware driver and transform to a dual-channel PCIIDE controller and transform the computer energy management mode StandardPC.
[4] Run SRS... and WindowsXPServicePack2 deployment tool DEPLOY.CAB to generate the sysprep.inf automatic answer file by so-called encapsulation, etc., will be the next step. The subsequent step.
You'll do all the above 4 products. If you will discover not a lot of tutorials on the web that may teach you all of the above 4 things, you'll be able to just follow the instructions. The hard component would be the hardware advance drive and DLL file backup and recovery (in truth, these two are certainly not tough).
Let's speak regarding the hardware's advance drive and DLL file backup and recovery
Advance driving of hardware: Some on the internet tutorials really need to manually modify the registry and inf automatic answer files, and so on., to make newbies appear dizzy and usually do not understand how to begin. In actual fact, anything is implemented with no tools with no manual modification. These tools are readily offered, fast and correct.
Self-extracting advance driver (just after Gho restarts, automatically decompresses, the hardware has been driven prior to getting into the desktop) The tools utilised are: integrated driver GhostXP.EXE and driver package self-extracting command script ns_sys.cmd file, restart tool restart.com Files, registry add items autohal1.reg and autohal2.reg, these five things are very little, you could upload to everybody. Then you ought to come across a driver self-extracting driver package Drivers.exe, which is usually found on the internet or taken in the Gho version technique disk.
____________________________________________________________________________________________________________
Section two: Preparation
Immediately after operating the SRSV9.6.0819.exe tool, a folder referred to as sysprep are going to be generated inside the root directory from the C drive, with two files inside, as shown in Figure 1:
Download (42KB)
2007-6-2017:07
Inside the sysprep folder, setup a new folder named Tools, which consists of the restart tool restart.com file, registry entries autohal1.reg and autohal2.reg and directed self-extracting driver package Drivers.exe, see Figure 2 :
Download (40KB)
2007-6-2017:07
Then unzip the Windows deployment tool DEPLOY.CAB in to the C:\\\\sysprep folder, and install the integrated driver GhostXP.EXE into the C:\\\\sysprep folder, as shown in Figure 3:
Download (60KB)
2007-6-2017:07
____________________________________________________________________________________________________________
Section 3: Distinct operations
[A] Open the C:\\\\sysprep\\\\Tools directory-double-click Drivers (driver package)-decompress the file-wait for the decompression to finish (create C:\\\\WINDOWS\\\\Drivers).
[B] Open the C:\\\\sysprep directory and double-click GhostXP using the integrated driver-(within the modest frame), click Browse-find the C:\\\\WINDOWS\\\\Drivers point Blue Drivers folder-OK-(smaller frame There's a new line C:\\\\WINDOWS\\\\Drivers) Click SETPATH-OK-click red X to exit. Delete http://www.yahoo.com :\\\\WINDOWS\\\\Drivers driver package folder (it will also be generated when the program is installed) and finish. See Figure four:
Download (17KB)
2007-6-2017:07
[C] The driver package self-extracting command script ns_sys is placed in the C:\\\\WINDOWS directory. (The registry essential autohal2 is imported by ns_sys)
[D] Begin the registry entry from the self-extracting command script ns_sys of the driver package, open the C:\\\\sysprep\\\\Tools directory-double-click autohal1 (registry entry)-yes, the startup command is imported into the registry.
Soon after operating these three items of ABC, the pre-driven operate is fundamentally completed, spend consideration! The fourth item [D]autohal1 (registry crucial) do not operate 1st, be sure to restart the Gho file after the program package is completed then import the registry, the operation from the registry crucial worth will be modified by other tools and trigger Failure.
____________________________________________________________________________________________________________
Section 4: The two things A and B inside the earlier section are integrated drivers. Let me speak concerning the principle below (you can ignore this section)
This is the so-called integrated driver. The integrated driver GhostXP can be a driver path designation tool. It tells the operating program that the driver file is within the C:\\\\WINDOWS\\\\Drivers..... directory. You need to use it to find it. It cannot be discovered). You can also manually modify the registry without the need of saying a great deal and it is also much more error-prone. (Manually modify the right-click DevicePath item-modify)
The location with the driver path within the registry is: HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersionDevicePath.
The original crucial worth is:
%SystemRoot%\\\\inf;%SystemRoot%\\\\dell\\\\aac;%SystemRoot%\\\\dell\\\\aarich;%SystemRoot%\\\\dell\\\\cercsr6;%SystemRoot%\\\\dell\\\\a320raid;%SystemRoot% \\\\dell\\\\iastor;%SystemRoot%\\\\dell\\\
vraid
Right after operating the integrated driver GhostXP, alter the key value to:
%SystemRoot%\\\\Inf;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\ati;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\Intel\\\\sp;C:\\\\WINDOWS\\\\Drivers\\\\ Board\\\\Intel;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force2;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide\\\\pataraid;C:\\\\WINDOWS\\\\Drivers\\ \\Board\\\
Force4\\\\ide\\\\sataraid;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide\\\\sata_ide;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide ;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\SMBus;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51\\\\ sata_ide;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51\\\\SMBus;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C61; C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Board;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\3com;C:\\\\WINDOWS\\\\Drivers \\\\Lan\\\\broadcom;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\IC_Plus;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Intel_100_1000;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\ Intel_Wireless;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Marvell;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\
Force2;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\
Force4;C:\\ \\WINDOWS\\\\Drivers\\\\Lan\\\
V idia_C51;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Realtek;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\sis900;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Uli_M5263;C:\\ \\WINDOWS\\\\Drivers\\\\Lan\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Lan;C:\\\\WINDOWS\\\\Drivers\\\\modem\\\\ECOM56HAM;C:\\\\WINDOWS\\\\Drivers\\\\modem \\\\Intel5628;C:\\\\WINDOWS\\\\Drivers\\\\modem;C:\\\\WINDOWS\\\\Drivers\\\\Others\\\\FlashMedia;C:\\\\WINDOWS\\\\Drivers\\\\Others;C:\\\\WINDOWS\\\\ Drivers\\\\Sound\\\\ad188x;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\cmi8738;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\cmi9738;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\ \\HDaudio;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\Realtek_AC97;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\Realtek_HD;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\SigmaTel_STAC9750;C: \\\\WINDOWS\\\\Drivers\\\\Sound\\\\SiS7012;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Sound;C:\\\\WINDOWS\\\\Drivers\\\\ vga\\\\ATi_Radeon\\\\b_36872;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\ATi_Radeon;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\Intel_845G;C:\\\\WINDOWS\\\\Drivers\\\\vga\\ \\Intel_865G-945G;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\
VIDIA;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\sis;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\via; C:\\\\WINDOWS\\\\Dri vers\\\\vga
____________________________________________________________________________________________________________
Section five: Compression of self-extracting driver package Drivers.exe (you can also ignore this section and use ready-made)
I usually do not advise that you simply make the driver package your self, for the reason that it really is tough to do effectively, and it's simple to bring about driver recognition errors and failures. The driver master is wooden bird. It can be slightly modified and improved or decreased, nevertheless it must also be tested and reused without the need of complications. My driver package was originally 231MB, along with the size right after compression was 65MB.
The driver package is compressed with the NSIS folder compressor. It might make the driver package into a directional self-extracting EXE file (EXE file is definitely an executable file). The NSIS folder compressor consumes memory when compressing the driver package, so you'll want to turn off the anti-virus monitoring as well as other operating applications.
Double-click the folder compressor software, the following operating screen seems, as shown in Figure five:
Download (55KB)
2007-6-2017:07
[1] Add directory: uncover the driver package folder you prepared, the folder name will have to be Drivers
[2] Decompression path: C:\\\\WINDOWS This compressed driver package ought to be decompressed in to the C drive WINDOWS folder.
[3]Title: The driver package will likely be unzipped through installation, please wait
[4] Compression dictionary: the larger the worth, the greater the compression rate. Below the configuration of P4. memory 512MB, your pc can use as much as 32MB, if it truly is 256 memory, it can use up to 16MB.
[5] Icon: You may opt for an icon to add.
[6] Quiet decompression: have to be chosen, otherwise a manual selection dialog will seem.
All other items are default. To press for any long time, it may be finished in 20-40 minutes based on the configuration from the computer system.
____________________________________________________________________________________________________________
Section six: Backup and recovery of DLL files
DLL file backup and recovery is very basic, but 1 thing to spend consideration to! Make sure to restart the Gho file immediately after the technique packaging is completed, then back up. When the backup is earlier, the backup tool might be activated and restored when the SRS packaging tool is run. The backup tool can use the backup and recovery tool DLLCache.exe offered in the attachment.
[A] Set up the DLLCache.exe tool into the C:\\\\WINDOWS\\\\system32 directory.
[B] Soon after the method is packaged, the DLL file is backed up, as shown in Figure six:
Download (23KB)
2007-6-2017:07
This version in the tool does not must modify the registry to start, it is possible to accurately start off the recovery prior to getting into the desktop, immediately after restarting... that item need to be checked, if not, it's essential to use other solutions to begin the recovery. Unsuccessful backups could be deleted without having profitable backup (simply because there is absolutely no corresponding file in the program, it really is lost as a result of weight-loss optimization), and this really is completed.
____________________________________________________________________________________________________________
Section 7: Backup of DLL files could make the system disk less than 400 MB files (when the software program is installed), and there is absolutely no loss, what is the principle? (It is possible to also ignore this section and make a fantastic Gho program with no figuring out it)
The DLL file we are talking about is in the XP system C:\\\\WINDOWS\\\\system32\\\\dllcache directory. The very critical files within the system are backed up there. When the system file is broken, it is actually identified to become employed for patching, which can make certain the stability of the program. Windows protected hidden files.
As the name implies, it can be not a copy of the backup file, there is also a working file. In order to reduce the size on the Gho file, 1 copy is usually removed but there must be a method. Which one particular to take away? Of course, remove the DLL files backed up in the C:\\\\WINDOWS\\\\system32\\\\dllcache directory, and restore them when installing the Gho technique.
The DLL backup tool solves this dilemma quite well. Through the backup, the tool appears for the operating file inside the program in accordance with the files inside the system32\\\\dllcache directory. Immediately after discovering it, it makes a path record and generates a list. Then delete the files backed up within the dllcache directory, and those which might be not identified are files that don't correspond for the prosperous backup.
When restoring, uncover the files in the program in accordance with the path records around the list, and copy them to the system32\\\\dllcache directory. Within this way, there is no a lot more than 400 MB of files in the method disk devoid of loss (the Gho file is really much less than 200MB, since the Gho file is compressed, and typically non-solid files is often compressed for the original size 50%).
Backing up DLL files is basic, in fact, there are plenty of other forms of files below the C:\\\\WINDOWS\\\\system32\\\\dllcache directory-EXE.NLS.SYS, and so on., DLL files account for many of them.
____________________________________________________________________________________________________________
Please see part of the backup file path list C:\\\\windows\\\\explorer.exeC:\\\\windows\\\\hh.exeC:\\\\windows\\\\NOTEPAD.EXEC:\\\\windows\\\egedit.exeC:\\\\windows\\\\ TASKMAN.EXEC:\\\\windows\\\\twain.dllC:\\\\windows\\\\twain_32.dllC:\\\\windows\\\\twunk_16.exeC:\\\\windows\\\\twunk_32.exeC:\\\\windows\\\\vmmreg32.dllC:\\ \\windows\\\\winhelp.exeC:\\\\windows\\\\winhlp32.exeC:\\\\windows\\\\AppPatch\\\\AcGenral.dllC:\\\\windows\\\\AppPatch\\\\AcLayers.dllC:\\\\windows\\\\AppPatch\\\\AcLua .dllC:\\\\windows\\\\AppPatch\\\\AcSpecfc.dllC:\\\\windows\\\\AppPatch\\\\AcXtrnal.dllC:\\\\windows\\\\AppPatch\\\\apphelp.sdbC:\\\\windows\\\\AppPatch\\\\apph_sp.sdbC :\\\\windows\\\\AppPatch\\\\drvmain.sdbC:\\\\windows\\\\AppPatch\\\\msimain.sdbC:\\\\windows\\\\AppPatch\\\\sysmain.sdbC:\\\\windows\\\\DriverCache\\\\i386\\\\aec. sysC:\\\\windows\\\\DriverCache\\\\i386\\\\kmixer.sys....... A total of far more than 2000 files. ____________________________________________________________________________________________________________
A couple of extra words in the finish
After operating the integrated driver GhostXP, the C:\\\\WINDOWS\\\\Drivers driver package folder is deleted because it must be decompressed and released for the duration of installation. If it is actually not deleted, the Gho file are going to be significant, and precious space are going to be wasted. Start off the driver package to decompress autohal1 (registry entry), and it should be imported last, plus the backup in the DLL file should also be placed in the end before running (before restarting to make the Gho file).
To be much more advanced, the Gho version of the technique really should automatically delete the employed C:\\\\WINDOWS\\\\Drivers driver package folder following installation. In the event you usually do not automatically delete the WINDOWS folder, there's a massive trash left. Large application installation (post-installation can reduce the size in the Gho file) as well as other actions is usually controlled with xplode, or is usually controlled with batch commands, registry startup commands, or sysprep.inf files Start off command...
lxg951753 production-07.6.11
____________________________________________________________________________________________________________
Reference short article:
Study from me to create Ghost version technique disk
http://www.xtzj.com/read-htm-tid-103964-fpage-2.html
____________________________________________________________________________________________________________
Interested netizens can ask questions, as well as other netizens who I can't answer may also answer, do not be polite, all of us discuss collectively. Find out. Boost.
Can I repost or share? But ntfs data recovery free should be indicated.
____________________________________________________________________________________________________________
Attached are: [1] GhostXP.EXE integrated driver [2] self-extracting command script ns_sys.cmd [3] restart tool restart.com [4] registry add items autohal1.reg and autohal2.reg [5] NSIS file Folder compressor [6] DLLCache.exe backup and recovery tool
Please download attachment: attachment.rar(421KB)
I always see some netizens online saying that it truly is too difficult to make the Ghost version with the system disk...I tell you that it is not hard at all. A set of tutorials looks incredibly difficult, and it is actually very very simple to appear at separately. You will find a great deal of issues You would have, you appear in the following 4 items. Not surprisingly, it is also quite difficult to do, we will not discuss it for the time getting. The technique we are speaking about now could make a great Ghost program disk so long as you make it carefully. It's versatile, speedy and stable. (The Ghost-XPsp2 membership research method disk I created generally uses this approach, but it can be a tiny extra complex, and it's controlled by xplode. Considering the fact that it was released in January, I made use of it to set up dozens of units, and no blue screen phenomenon was identified. Exceptional, mother machine-VIA motherboard, CPU two.66). It really is advised to utilize a computer with P4-CPU-2.4G or higher, preferably a Through motherboard, which features a powerful versatility.
The process of packaging program: (XPVSP2 as an example) Install the system-patch-install the software-lose weight-system optimization and settings-install the background image setup.BMP below system32-delete the hardware driver and adjust the IDE ...Transform the pc...——remove the garbage—defragmentation—run SRS—decompress DEPLOY.CAB—drive the operation ahead of time see section III—run setupmgr to make an automatic answer inf file—run msprep dragon Empire package program-autohal1 import registry-DLL file backup-completed.
[1] You need to set up the system, the original version of WindowsXP (installation version, typically CD to start DOS installation), install the computer software to set the system optimization.
[2] It is actually not hard to streamline the system (you are able to do it with tools).
[3] It's not hard to delete the hardware driver and transform to a dual-channel PCIIDE controller and transform the computer energy management mode StandardPC.
[4] Run SRS... and WindowsXPServicePack2 deployment tool DEPLOY.CAB to generate the sysprep.inf automatic answer file by so-called encapsulation, etc., will be the next step. The subsequent step.
You'll do all the above 4 products. If you will discover not a lot of tutorials on the web that may teach you all of the above 4 things, you'll be able to just follow the instructions. The hard component would be the hardware advance drive and DLL file backup and recovery (in truth, these two are certainly not tough).
Let's speak regarding the hardware's advance drive and DLL file backup and recovery
Advance driving of hardware: Some on the internet tutorials really need to manually modify the registry and inf automatic answer files, and so on., to make newbies appear dizzy and usually do not understand how to begin. In actual fact, anything is implemented with no tools with no manual modification. These tools are readily offered, fast and correct.
Self-extracting advance driver (just after Gho restarts, automatically decompresses, the hardware has been driven prior to getting into the desktop) The tools utilised are: integrated driver GhostXP.EXE and driver package self-extracting command script ns_sys.cmd file, restart tool restart.com Files, registry add items autohal1.reg and autohal2.reg, these five things are very little, you could upload to everybody. Then you ought to come across a driver self-extracting driver package Drivers.exe, which is usually found on the internet or taken in the Gho version technique disk.
____________________________________________________________________________________________________________
Section two: Preparation
Immediately after operating the SRSV9.6.0819.exe tool, a folder referred to as sysprep are going to be generated inside the root directory from the C drive, with two files inside, as shown in Figure 1:
Download (42KB)
2007-6-2017:07
Inside the sysprep folder, setup a new folder named Tools, which consists of the restart tool restart.com file, registry entries autohal1.reg and autohal2.reg and directed self-extracting driver package Drivers.exe, see Figure 2 :
Download (40KB)
2007-6-2017:07
Then unzip the Windows deployment tool DEPLOY.CAB in to the C:\\\\sysprep folder, and install the integrated driver GhostXP.EXE into the C:\\\\sysprep folder, as shown in Figure 3:
Download (60KB)
2007-6-2017:07
____________________________________________________________________________________________________________
Section 3: Distinct operations
[A] Open the C:\\\\sysprep\\\\Tools directory-double-click Drivers (driver package)-decompress the file-wait for the decompression to finish (create C:\\\\WINDOWS\\\\Drivers).
[B] Open the C:\\\\sysprep directory and double-click GhostXP using the integrated driver-(within the modest frame), click Browse-find the C:\\\\WINDOWS\\\\Drivers point Blue Drivers folder-OK-(smaller frame There's a new line C:\\\\WINDOWS\\\\Drivers) Click SETPATH-OK-click red X to exit. Delete http://www.yahoo.com :\\\\WINDOWS\\\\Drivers driver package folder (it will also be generated when the program is installed) and finish. See Figure four:
Download (17KB)
2007-6-2017:07
[C] The driver package self-extracting command script ns_sys is placed in the C:\\\\WINDOWS directory. (The registry essential autohal2 is imported by ns_sys)
[D] Begin the registry entry from the self-extracting command script ns_sys of the driver package, open the C:\\\\sysprep\\\\Tools directory-double-click autohal1 (registry entry)-yes, the startup command is imported into the registry.
Soon after operating these three items of ABC, the pre-driven operate is fundamentally completed, spend consideration! The fourth item [D]autohal1 (registry crucial) do not operate 1st, be sure to restart the Gho file after the program package is completed then import the registry, the operation from the registry crucial worth will be modified by other tools and trigger Failure.
____________________________________________________________________________________________________________
Section 4: The two things A and B inside the earlier section are integrated drivers. Let me speak concerning the principle below (you can ignore this section)
This is the so-called integrated driver. The integrated driver GhostXP can be a driver path designation tool. It tells the operating program that the driver file is within the C:\\\\WINDOWS\\\\Drivers..... directory. You need to use it to find it. It cannot be discovered). You can also manually modify the registry without the need of saying a great deal and it is also much more error-prone. (Manually modify the right-click DevicePath item-modify)
The location with the driver path within the registry is: HKEY_LOCAL_MACHINE\\\\SOFTWARE\\\\Microsoft\\\\Windows\\\\CurrentVersionDevicePath.
The original crucial worth is:
%SystemRoot%\\\\inf;%SystemRoot%\\\\dell\\\\aac;%SystemRoot%\\\\dell\\\\aarich;%SystemRoot%\\\\dell\\\\cercsr6;%SystemRoot%\\\\dell\\\\a320raid;%SystemRoot% \\\\dell\\\\iastor;%SystemRoot%\\\\dell\\\
vraid
Right after operating the integrated driver GhostXP, alter the key value to:
%SystemRoot%\\\\Inf;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\ati;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\Intel\\\\sp;C:\\\\WINDOWS\\\\Drivers\\\\ Board\\\\Intel;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force2;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide\\\\pataraid;C:\\\\WINDOWS\\\\Drivers\\ \\Board\\\
Force4\\\\ide\\\\sataraid;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide\\\\sata_ide;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\ide ;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4\\\\SMBus;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Force4;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51\\\\ sata_ide;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51\\\\SMBus;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C51;C:\\\\WINDOWS\\\\Drivers\\\\Board\\\
Vidia_C61; C:\\\\WINDOWS\\\\Drivers\\\\Board\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Board;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\3com;C:\\\\WINDOWS\\\\Drivers \\\\Lan\\\\broadcom;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\IC_Plus;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Intel_100_1000;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\ Intel_Wireless;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Marvell;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\
Force2;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\
Force4;C:\\ \\WINDOWS\\\\Drivers\\\\Lan\\\
V idia_C51;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Realtek;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\sis900;C:\\\\WINDOWS\\\\Drivers\\\\Lan\\\\Uli_M5263;C:\\ \\WINDOWS\\\\Drivers\\\\Lan\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Lan;C:\\\\WINDOWS\\\\Drivers\\\\modem\\\\ECOM56HAM;C:\\\\WINDOWS\\\\Drivers\\\\modem \\\\Intel5628;C:\\\\WINDOWS\\\\Drivers\\\\modem;C:\\\\WINDOWS\\\\Drivers\\\\Others\\\\FlashMedia;C:\\\\WINDOWS\\\\Drivers\\\\Others;C:\\\\WINDOWS\\\\ Drivers\\\\Sound\\\\ad188x;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\cmi8738;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\cmi9738;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\ \\HDaudio;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\Realtek_AC97;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\Realtek_HD;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\SigmaTel_STAC9750;C: \\\\WINDOWS\\\\Drivers\\\\Sound\\\\SiS7012;C:\\\\WINDOWS\\\\Drivers\\\\Sound\\\\via;C:\\\\WINDOWS\\\\Drivers\\\\Sound;C:\\\\WINDOWS\\\\Drivers\\\\ vga\\\\ATi_Radeon\\\\b_36872;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\ATi_Radeon;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\Intel_845G;C:\\\\WINDOWS\\\\Drivers\\\\vga\\ \\Intel_865G-945G;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\
VIDIA;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\sis;C:\\\\WINDOWS\\\\Drivers\\\\vga\\\\via; C:\\\\WINDOWS\\\\Dri vers\\\\vga
____________________________________________________________________________________________________________
Section five: Compression of self-extracting driver package Drivers.exe (you can also ignore this section and use ready-made)
I usually do not advise that you simply make the driver package your self, for the reason that it really is tough to do effectively, and it's simple to bring about driver recognition errors and failures. The driver master is wooden bird. It can be slightly modified and improved or decreased, nevertheless it must also be tested and reused without the need of complications. My driver package was originally 231MB, along with the size right after compression was 65MB.
The driver package is compressed with the NSIS folder compressor. It might make the driver package into a directional self-extracting EXE file (EXE file is definitely an executable file). The NSIS folder compressor consumes memory when compressing the driver package, so you'll want to turn off the anti-virus monitoring as well as other operating applications.
Double-click the folder compressor software, the following operating screen seems, as shown in Figure five:
Download (55KB)
2007-6-2017:07
[1] Add directory: uncover the driver package folder you prepared, the folder name will have to be Drivers
[2] Decompression path: C:\\\\WINDOWS This compressed driver package ought to be decompressed in to the C drive WINDOWS folder.
[3]Title: The driver package will likely be unzipped through installation, please wait
[4] Compression dictionary: the larger the worth, the greater the compression rate. Below the configuration of P4. memory 512MB, your pc can use as much as 32MB, if it truly is 256 memory, it can use up to 16MB.
[5] Icon: You may opt for an icon to add.
[6] Quiet decompression: have to be chosen, otherwise a manual selection dialog will seem.
All other items are default. To press for any long time, it may be finished in 20-40 minutes based on the configuration from the computer system.
____________________________________________________________________________________________________________
Section six: Backup and recovery of DLL files
DLL file backup and recovery is very basic, but 1 thing to spend consideration to! Make sure to restart the Gho file immediately after the technique packaging is completed, then back up. When the backup is earlier, the backup tool might be activated and restored when the SRS packaging tool is run. The backup tool can use the backup and recovery tool DLLCache.exe offered in the attachment.
[A] Set up the DLLCache.exe tool into the C:\\\\WINDOWS\\\\system32 directory.
[B] Soon after the method is packaged, the DLL file is backed up, as shown in Figure six:
Download (23KB)
2007-6-2017:07
This version in the tool does not must modify the registry to start, it is possible to accurately start off the recovery prior to getting into the desktop, immediately after restarting... that item need to be checked, if not, it's essential to use other solutions to begin the recovery. Unsuccessful backups could be deleted without having profitable backup (simply because there is absolutely no corresponding file in the program, it really is lost as a result of weight-loss optimization), and this really is completed.
____________________________________________________________________________________________________________
Section 7: Backup of DLL files could make the system disk less than 400 MB files (when the software program is installed), and there is absolutely no loss, what is the principle? (It is possible to also ignore this section and make a fantastic Gho program with no figuring out it)
The DLL file we are talking about is in the XP system C:\\\\WINDOWS\\\\system32\\\\dllcache directory. The very critical files within the system are backed up there. When the system file is broken, it is actually identified to become employed for patching, which can make certain the stability of the program. Windows protected hidden files.
As the name implies, it can be not a copy of the backup file, there is also a working file. In order to reduce the size on the Gho file, 1 copy is usually removed but there must be a method. Which one particular to take away? Of course, remove the DLL files backed up in the C:\\\\WINDOWS\\\\system32\\\\dllcache directory, and restore them when installing the Gho technique.
The DLL backup tool solves this dilemma quite well. Through the backup, the tool appears for the operating file inside the program in accordance with the files inside the system32\\\\dllcache directory. Immediately after discovering it, it makes a path record and generates a list. Then delete the files backed up within the dllcache directory, and those which might be not identified are files that don't correspond for the prosperous backup.
When restoring, uncover the files in the program in accordance with the path records around the list, and copy them to the system32\\\\dllcache directory. Within this way, there is no a lot more than 400 MB of files in the method disk devoid of loss (the Gho file is really much less than 200MB, since the Gho file is compressed, and typically non-solid files is often compressed for the original size 50%).
Backing up DLL files is basic, in fact, there are plenty of other forms of files below the C:\\\\WINDOWS\\\\system32\\\\dllcache directory-EXE.NLS.SYS, and so on., DLL files account for many of them.
____________________________________________________________________________________________________________
Please see part of the backup file path list C:\\\\windows\\\\explorer.exeC:\\\\windows\\\\hh.exeC:\\\\windows\\\\NOTEPAD.EXEC:\\\\windows\\\egedit.exeC:\\\\windows\\\\ TASKMAN.EXEC:\\\\windows\\\\twain.dllC:\\\\windows\\\\twain_32.dllC:\\\\windows\\\\twunk_16.exeC:\\\\windows\\\\twunk_32.exeC:\\\\windows\\\\vmmreg32.dllC:\\ \\windows\\\\winhelp.exeC:\\\\windows\\\\winhlp32.exeC:\\\\windows\\\\AppPatch\\\\AcGenral.dllC:\\\\windows\\\\AppPatch\\\\AcLayers.dllC:\\\\windows\\\\AppPatch\\\\AcLua .dllC:\\\\windows\\\\AppPatch\\\\AcSpecfc.dllC:\\\\windows\\\\AppPatch\\\\AcXtrnal.dllC:\\\\windows\\\\AppPatch\\\\apphelp.sdbC:\\\\windows\\\\AppPatch\\\\apph_sp.sdbC :\\\\windows\\\\AppPatch\\\\drvmain.sdbC:\\\\windows\\\\AppPatch\\\\msimain.sdbC:\\\\windows\\\\AppPatch\\\\sysmain.sdbC:\\\\windows\\\\DriverCache\\\\i386\\\\aec. sysC:\\\\windows\\\\DriverCache\\\\i386\\\\kmixer.sys....... A total of far more than 2000 files. ____________________________________________________________________________________________________________
A couple of extra words in the finish
After operating the integrated driver GhostXP, the C:\\\\WINDOWS\\\\Drivers driver package folder is deleted because it must be decompressed and released for the duration of installation. If it is actually not deleted, the Gho file are going to be significant, and precious space are going to be wasted. Start off the driver package to decompress autohal1 (registry entry), and it should be imported last, plus the backup in the DLL file should also be placed in the end before running (before restarting to make the Gho file).
To be much more advanced, the Gho version of the technique really should automatically delete the employed C:\\\\WINDOWS\\\\Drivers driver package folder following installation. In the event you usually do not automatically delete the WINDOWS folder, there's a massive trash left. Large application installation (post-installation can reduce the size in the Gho file) as well as other actions is usually controlled with xplode, or is usually controlled with batch commands, registry startup commands, or sysprep.inf files Start off command...
lxg951753 production-07.6.11
____________________________________________________________________________________________________________
Reference short article:
Study from me to create Ghost version technique disk
http://www.xtzj.com/read-htm-tid-103964-fpage-2.html
____________________________________________________________________________________________________________
Interested netizens can ask questions, as well as other netizens who I can't answer may also answer, do not be polite, all of us discuss collectively. Find out. Boost.
Can I repost or share? But ntfs data recovery free should be indicated.
____________________________________________________________________________________________________________
Attached are: [1] GhostXP.EXE integrated driver [2] self-extracting command script ns_sys.cmd [3] restart tool restart.com [4] registry add items autohal1.reg and autohal2.reg [5] NSIS file Folder compressor [6] DLLCache.exe backup and recovery tool
Please download attachment: attachment.rar(421KB)
