------ 雨 浪 整
Due to time reasons, many local writes are not very detailed, missing something, and there are still many interesting skills, such as increasing optimization functions, installing the themes directly, replacing input methods, etc., have time, slowly Write.
The first chapter makes a Windows XP installation disc for integrated SP2
This chapter tells how to make a Windows XP installation of the integrated SP2?
1 Tools required:
(1) XP installation disc
(2) XP SP2
(3) CDIMAGE
(4) ISOBUSTER
(5) VMware (or Virtual PC)
2 Integration:
First copy all the contents of the XP installation plate to a directory of the hard disk, such as D: / XPCD / WinXP.
Use WinRAR to extract the SP2 package, or enter "D: /XPSP2.exe / x" in "Start / Run" to extract it to the hard disk, such as D: / XPCD / SP2. Then enter "D: /XPCD/SP2/I386/UPDTE.exe -s: / XPCD / WinXP" to integrate.
In fact, SP2 has a direct integration of SP2 packages, and does not need to be unzipped first. You can integrate directly with the "D: / XPSP2.exe -s: / XPCD / WinXP" command.
3 extraction boot file: (detailed method can look at the following skills chapter)
Put the installation disc into the optical drive, open the isobuster, select the optical drive letter where the disc is located, click "Bootimage.IMG" and select "Bootimage.Img" and save it as a file, assume it in the D: / XPCD directory.
Of course, you can also boot files with ready-made CD, such as bootsect.bin, etc., these can be found online, the effect is the same.
4 Making CD ISO:
Put CDIMAGE.EXE in the D: / XPCD directory, enter "CDIMAGE -LINXPSP2 -T08 / 10/2004, 00: 00: 00 -H -M-N -BD: /XPCD/Bootimage.IMG CD D" : /winxpsp2.iso, will pop up a DOS window that is making ISO file processes. After the end, you can see the disc image file you make under your D.
You can directly engrave, if you don't feel relieved, you can load it with a virtual drive such as Daemon Tools, see if it is normal, you can also use the VMware Workstation virtual computer to test whether it can boot, more installed it is perfect.
Chapter II made a multi-in-one Windows XP SP2 installation CD
This chapter tells how to make a plurality of versions of Windows XP SP2 installation discs. That is, now popular multi-1 installation discs. Here we use the Making OEM and VLK two-in-one version as an example, in order to facilitate production and explanation, establish a unified directory, assuming D: / XPCD / WinXP, this directory is the CD root directory.
1 Tools required:
(1) Multiple versions of XP installation CDs, here we take two in one as an example.
(2) XP SP2
(3) CDIMAGE
(4) ISOBUSTER
(5) UltraEdit
(6) xxcopy
(7) WinImage
2 Preparation:
a) To download the boot floppy disk of Windows XP, its role is to let the disc can simulate the floppy disk when startup, do a floppy disk corresponding to a installation file. Everyone is assured, the start-up floppy here is not a Win98 boot floppy disk, but the Windows XP-specific boot disk, which is driven by NTFS, SCSI, RAID, etc., so you can fully identify NTFS partitions. Download address: (This is Pro version, only on the PRO installation disk,)
http://www.microsoft.com/downloads/...b7-4fed408ea73f
After downloading, it is a installation file, but don't install it, unless you have a floppy drive (there is a flour drive is very troublesome), you will directly decompress the WinRAR, and there will be 8 files after the decompression, where 6 is a floppy disk image. As shown below:
b) Unzip the cdboot several files in the same directory with WinImage, assuming D: / XPCD / ROOT.
C) Copy the contents of two installation CDs to D: / XPCD / WinXP / OEM, D: / XPCD / WINXP / VLK, respectively.
3 Integrated SP2:
Use "D: / XPSP2.EXE -S: D: / XPCD / WINXP / OEM" and "D: / XPSP2.EXE -S: D: / XPCD / WINXP / VLK" command SP2 installation file integrated SP2 .
4 Replace the boot disk group file: Use the file below the D: / XPCD / root below the D: / XPCD / WINXP / OEM / I386 directory, that is, the files in the boot floppy group are replaced with the file after integrated SP2. . Note: Do not replace files in System32, otherwise you cannot install it.
To replace this big pile file is cumbersome, you can use xxcopy: put the downloaded xxcopy under D: / XPCD, execute the command "XXCopy D: / XPCD / WinXP / OEM / I386 D: / Win2k / root / / U / e / yy ". XXCopy's role is to copy the same files in the target directory to the original folder. After this replacement, the files in the root directory have been the same as those in the i386 directory.
5 Copy 2 root folders to the D: / XPCD / WinXP directory, a mounting file that is renamed OEMX, a VLKX, separate, and OEM and VLK version.
6 Modify setupldr.bin: Use UltraEdit to open D: /XPCD/winxp/oemx/setupldr.bin, search with ASCII mode to replace "I386" as "OEMX", with a total of 4 places. Note that the OEMX here must be capitalized because these folders and files will be automatically converted to uppercase because they are lowercase, if they are lowercase, they will not find the NTDetect file. Because this file is to tell where to start it.
Use the same method to replace the I386 in D: /XPCD/winXp/vlkx/setupldr.bin to VLKX.
7 Modify TXTSETUP.SIF: Use UltraEdit to open D: /XPCD/WinXp/oemx/txtSetup.sif, search replacement "setupsourcePath =" "" to "setupSourcePath =" / OEM "; open D: / XPCD / WinXP with UltraEdit /vlkx/txtsetup.sif, search replacement "setupsourcePath =" "is" setupSourcePath = "/ VLK" ". When this file tells the installer where to copy the installation file. 8 Modify CD boot file: Use the method in the first chapter to extract the disc boot file, copy two copies, named OEMXP.BIN and VLKXP.BIN. Use UltraEdit to open OEMXP.BIN, search replacement i386 is OEMX; open VLKXP.BIN with UltraEdit, search replacement i3 86 is VLKX. Only one place.
9 Make a startup menu: Methods and tools for making the startup menu, there are many kinds, recommend using the current most popular graphical start menu production tool EasyBoot.
Copy OEMXP.BIN and VLKXP.BIN to the D: / XPCD / WINXP / EZBOOT directory (this folder is the folder of the storage boot file belt with EasyBoot).
In the menu command line, you can divide the XP and VLK version of the XP version of the XP and VLK version of the XP version of the XP and VLK version of the EM version. Please refer to the software help in easyboot. If you have more questions, I have a dedication to the explanation.
10 Making ISO: Put CDImage.exe in D: / XPCD Directory, Enter "CDIMAGE -LINXP_SP2_2IN1-1 -T08 / 10/2004, 00: 00: 00: --H -M-N -BD: / XPCD / Loader .bin CD D: /WINXP_SP2_2IN1.ISO ", will pop up a DOS window that is making the ISO file process, after the end, you can see the disc image file you make under your D.
You can directly engrave, if you don't feel relieved, you can load it with a virtual drive such as Daemon Tools, see if it is normal, you can also use the VMware Workstation virtual computer to test whether it can boot, more installed it is perfect.
If you want to integrate more XP versions, the method of writing is the same, you need to change, you need to increase the boot file corresponding to the original file, such as a boot disk group, boot file, etc.
Chapter III Making Unattended Devices
In the first two chapters, we learned how to make an installation disc for integrated SP, which is a very "clean" installation disk. In fact, we can also do deeper processing of this plate. the main purpose:
1 Integrated Pattern
2 unattended installation
3 replace some crack files
This chapter I don't want to write again, because there is already a good tutorial, huh, lazy, refer to the most complete unattended installation CD production teaching website: http://www.cctips.com/unattended/ XP / INDEX.HTM
Special pointing out:
1 WinXP SP2 has integrated DirectX 9.0C and MediaPlayer 9.0, so we don't need to integrate these two.
2 UXTHEME.DLL is a strict version restriction, uncomfortable, Chinese SP2 RTM 2180 version UXTHEME.DLL and its method can be downloaded here:
http://www.jujumao.com/dispbbs.asp?..&id=8447&page=5
3 In this tutorial about HotFix, everyone is best not to learn, because he is too much trouble. I will tell you how to integrate hotfix in the next chapter. Chapter 4 Integrates various patches and software
Because SP2 has just come out, there is currently no key update available, so I temporarily use the patch of the SP1 era to explain.
1 Traditional integrated method is to use Microsoft's way to complete the call to complete the patch, and then use cmdlines.txt or WinNT.SIF to implement the auto installation of patches and other programs. The content in cmdlines.txt is looking for content when installing, and executes the contents in turn. As long as we join the programs we need to run in "[Commands]", we can automate installation.
Method: Putting all the patches (including DirectX9.0B, MediaPlayer9.0, etc.) to the CD "$ OEM $ / 1 / Install" directory, then write one or more batch to allow them to perform installation. During the installation process, the installer will copy all the files in the "$ 1" directory to the hard disk system disk, and then perform the files in cmdlines.txt or the Runoncee in WinNT.sif.
This method interface is a single and unheatched, it is a very ugly DOS window of the black. There are very few people who have used this method now.
2 xpinstall
Xpinstall is a installer written by a user of Australia that automatically performs scripts and replaces the DOS window with a beautiful interface. In addition, it also supports XML scripts, we only need to write all execution commands in a script file. If you want to make a fully automatic integrated installation CD, it makes your best choice. The latest version of XPinst All is version 4.3, you can go
There are 2 xpinstall main files, as well as a folder, just copy the two files of XPinstall.exe and XPinstall.xml to the "$ / $ 1 / install" directory, and put the patch to install And the program is also copied to the "$ OEM $ / $ 1 / Install" directory.
The rest is to write XPinstall.xml. What you need to modify is like "
Modify all patchs and programs in these rows, delete excess rows, but in then cmdlines.txt or the Runoncee line in Winnt.sif is specified to run XPinstall.exe.
In fact, there are still many places in XPinstall.xml, such as the beginning of the beginning, you can specify the installation window display name, window location, number of times each time. These you go to figure yourself, play more, these are good, huh, huh.
3 installation manager
The installation manager mentioned here is a installation management in the Juju Cat Forum. It is the advantage of free choice and customization of patches, software, drivers, etc. to be installed, very flexible. People who are suitable for integrated large amounts of software and need to have selective installation. It is more headache where you don't have a soft installation parameter. You need to write automatic installation scripts.
This installer only appears in yanghaijun's "Windows 2000 Simplified Chinese Professional Edition Integrated Installation CD", the current version is version 2.0 (should be said to be version 2.1, because YANGhaijun in the 6.1 version is also carried out again. Some small improvements and upgrades).
Here, I will not talk more about it here, what is the problem, everyone or go to the Juju Cat Forum to ask Yanghaijun.
Chapter 5 How to make a perfect VLK SP2 version on the XP of integrated SP1
Many friends want to integrate SP2 on the basis of the VLK version to ensure the perfection of integration. In fact, the perfect is not perfect is your psychological role, because after integrated SP2, the replaced file is the same, that is, the installation file you integrate on the original version and the installation file integrated on SP1, in the effect The same is true, the only difference is just the useless files left on the SP1. Friends with rich integrated SP experience will know.
Seeing that everyone is looking for the VLK original installation disk, can find it is good, it is not necessary, you have to do it, it is to delete the useless documents left in the SP1 era. I can guarantee that SP2 installation discs made in this way are almost exactly the same as it is based on the original top!
Let me talk about how to make a perfect VLK SP2 integration on the basis of the VLK version of the integrated SP1. Of course, if there is a original VLK, it is not discussed. (The problem is what you really can find? Hehe)
1. Prepare:
Any version of the XP installation disk that is not integrated SP1 (actually as long as I386 directory)
Integrated SP1 VLK version XP installation disk
Chinese SP2 RTM 2180
BeyondCompare2 (tools for comparing files and directories)
2, integration:
a copy all files to the hard disk directory to copy the original XP mounting disk and integrated SP1 VLK installation disk
B decompressed SP2 package
c integrate SP2 to two installation disks, respectively.
3, compare:
Open beyondCompare2, select the comparison directory, specify the i386 directory of two version installation discs, confirm, open, then you will see that the software is displayed separately in the two directories.
Select menu "View - Show filters - only match", then you will see a part of file only on the SP1 version VLK. These files are files left by the SP1 era, belonging to excess files, directly deleting. How many files are, I have already deleted the files when I was doing, and I am too lazy to verify. If you are not assured, you can move them to a folder for recovery.
At this time, you will look at the i386 directory, because it is 2766 or 2767 files (a winnt.sif difference), and the volume is more than twenty M. Delete Win51IP.SP1, SPNOTES.htm under the root of the root. Now this disk is basically no difference in the disc that integrates the SP on the original version!
You can install the test, see if the setuperr.log file under your system disk Windows directory has an error message, if not, congratulations, you already have a perfect integrated SP2 VLK version XP installation CD! ! !
Chapter VI Personalization
The content of this chapter is to make some personalized settings after the installation process and installation.
1 beautification installation background picture
In fact, this is the two files for Winntbbu.dll and WinNTBBU.DL_. Winntbu.dll is the installation screen under Windows, WinNTBBU.DL_ is the disc installation background screen when the disc is installed and installed under DOS.
1) Modify Winntbbu.dll
A extract winntbbu.dll to the hard disk from the i386 directory from the installation.
B Tools such as editing DLL file resources such as: Resource Hacker or Exescope and other tools Open the winntbbu.dll file here You can see the pictures, icons, text, copyright information, etc.
C Find - bitmap --- 103, export the image inside, then edit it with image processing software. Or replace this picture directly with other images, but you must ensure that its format is the same.
D Save the file and put the winntbbu.dll back the installation directory. OK!
2) Modify WinNTBBU.dl_
The method of this file is modified with the same, but you need to decompress with the expand command before modifying, and finally use Wincab to compress it back. The use of these two commands is simple, and it is possible to help with the command line.
2 OEM information
OEM's settings I will explain as an example with Lenovo installation disks. To set the OEM information in the system properties, it is very simple, just place OEMLOGO.BMP and OEMINFO.INI files in the "$ O / $ / SYSTEM32 folder. Oemlogo.bmp is a BMP file with a 170x120, too big, will be out of the display, and it is not complete, too small, and it is not very good. Oeminfo.ini's content has a fixed format, as shown below, what you have to do is modifying the text. If you need to add content, just a few lines of "lin en =" can be added.
[Version]
Microsoft Windows WHISTLER EDITION
Winver = 5.01
[General]
Manufacturer = Lenovo (Beijing) Co., Ltd.
MODEL = Lenovo series computer
[Support Information]
LINE1 = "To protect your investment, Lenovo (Beijing) Co., Ltd."
Line2 = "Provide you with a range of services and support, when you encounter hardware
3 advanced OEM information
If you want to do, for example, in the support center and IE navigation bar in the Start menu. Look below:
Windows Registry Editor Version 5.00
[HKEY_CLASS_ROOT / CLSID / {2559A1F6-21D7-11D4-BDAF-00C04F60B9F0}]
@ = "Welcome to Lenovo Computer"
"Infotip" = "Lenovo Computer Support Information"
[HKEY_CLASS_ROOT / CLSID / {2559A1F6-21D7-11D4-BDAF-00C04F60B9F0} / defaulticon] @ = "OEMLINKICON.ICO" (icon file)
[Hkey_classes_root / CLSID / {2559A1F6-21D7-11D4-BDAF-00C04F60B9F0} / instance / initpropertybag]
"Command" = "Lenovo Computer Support Information"
"PARAM1" = "sysdm.cpl" (opened program, the sysdm.cpl here is the system properties)
[HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Windows / CurrentVersion / Explorer / StartMenu / StartPanel / ShowoemLink]
"Nooemlinkinstalled" = dword: 00000000 (tell the system, open OEM information, otherwise all information can not be displayed)
The above section is a registry information, its role is to add a "Lenovo Computer Support Information" menu in the run menu, you only need to modify the red place. In addition, you also need to make a name file that names Oemlinkicon.ico is placed in the CD "$ OEM $ / $ / SYSTEM32" directory, in fact, this directory is to copy all files in this directory to the system "Windows / System32 "directory. This icon will appear in front of the Lenovo Computer Support Information menu.
[HKEY_LOCAL_MACHINE / SOFTWARE / Microsoft / Internet Explorer / Extensions / {6096E38F-5AC1-4391-8EC4-75DFA92FB32F}]
"CLSID" = "{1FBA04EE-3024-11D2-8F1F-0000F87ABD16}"
"Default visible" = "yes"
"ButtonText" = "Lenovo"
"EXEC" = "http://www.lenovo.com"
"Hoticon" = "% windir% // system32 // Oemlinkicon.ico"
"Icon" = "% windir% // system32 // Oemlinkicon.ico"
This section is add OEM information on the IE navigation bar. With the above experience, here you will go to you, huh, huh.
Tips:
1 Crack UXTHEME.DLL
The purpose of cracked UXTHEME.DLL is to use a third-party desktop topic after installing the system. I have already released the specific method and the crack file, I have already released it here:
http://www.jujumao.com/dispbbs.asp?boardid=24&id=8447
I have created the crack UXTHEME.DLL: I have to crack UXTHEME.DLL before, I need to edit UXTHEME.DLL yourself with the 16-letter text editor, modify the two paragraphs, now there is no trouble, because we can use it Tools to crack.
The tool that needs to be used is UXTHEME MULTI-PATCHER, and you can find its download address with Google search. Although it is just for the English version of the XP system, Chinese still can be used. Download it, open it, it will pop up a prompt box instructions can only be used in English systems, do not pay attention to, directly OK, then point Patch. (Note that your operating system must be an XP system) This, UXTHEME in our system is already crack. Below we want to extract it, put it in our installation plate after compression, so that the installation completed system is already cracking UXTHEME. Search the UXTHEME file in the system, copy it out, use the "Make UXTHEME.DLL" command to compress it into the same type of file in the installation disc (Note, makecab is the compressed command with the system), then we can Use the UXTHEME.DL_ replace the same file in the mounting disk after compression.
2 crack TCP / IP connection restrictions
The default maximum number of XP systems is 10. It is simply unbearable for our downloads of our downloads, so we also need to crack it. Here we also use a crack tool, called evid4226patch, you can download directly from its author website, address is [URL] http://www.lvllord.de/4226fix/4226fix-en.htm, the latest version of the latest version Do not limit the maximum number of cracks, it is limited to 50. The method is the same, we also use it first to crack the system tcpip.sys and place it into our installation plate. The method is basically consistent with the above, and I will not say it here.
3 Using the new version of Taskmgr
That is, the task manager, the new version I said here refers to the task manager in Microsoft's next-generation operating system everglar horn lastle. The new version of the task manager function is stronger than XP, it can process the location of the process and its running parameters, with this feature, we don't have to use the third-party tool to know where the files are in the process, this for us The suspicious procedure in the process is very useful. First download the three files of the new task manager from the Internet (don't ask where I download it, this can only go to the forum, huh, huh). After downloading, it cannot be directly compressed, because it is not for XP system development, so the digital signature will not be verified, and it will be prompted to be destroyed when installing will refuse to copy. Here we need a gadget called "setcsum", which can modify the header information of the file to deceive the installer (some netizens said it is a digital signature information to the file, it is not right, because it just deceived This step of copying files, is a letter that is really difficult to install, it will be pointed out in the installation error message, that is, setuperr.log "The installer detected that Microsoft did not correctly signed the ***** System Files……"). Perform "setcsum taskmgr.exe" to modify the file in the command line, and then we use makecab to compress it, override the same file in the mounting disk. With this method, we can also replace more XP systems. For example, we will replace the Zheng code input method that does not have to be used as a king code five input method, but the replacement input method is not so simple, but also Modify a lot of things.
