Let's talk about the software needed to make this installation disk:
1, EASYBOOT This is used for CD-ROM startup interface and compressing ISO files. The software of the CD production company is very easy to use, as long as it is opened. You can try if you don't believe me.
2. Resource Hacker This is a very powerful tool that can be used to change resources in exe and dll files.
3.SfxMaker7Zip is used to make automatic installation software, which is convenient for integrated installation when the system is started.
4. Multimedia Generator This is menu-level software, which is used to make the CD run in the system.
5, nMaker This is a program written by a master in this forum, which is used to make the system boot file.
I have thought of the above software for the time being, and I need to add it later. As for the download address of the software, go and search for it yourself. CD production companies have many on the Internet. After preparing the above software, you can officially start working! Kick up the mouse, take the heart of learning, and work hard with me!
Making your own installation system disk is divided into the following steps:
Firstly, establish the system installation directory, copy the installation files, modify the system logo and beautify the installation interface.
Second, integrate driver installation and common software installation. (This is the key and difficult point to make the system installation version as convenient as the GHOST system. But I believe that under my explanation, everyone should understand that O (∩ _ ∩) O. ...
3. Make system startup file with nMaker, and make CD running menu with multimedia generator.
Fourthly, using EASYBOOT as the CD boot interface, the CD production company generates ISO files.
Let's start with the first step. No screenshots. It's all words. Please read it carefully. It's easy for CD production companies.
Firstly, establish the system installation directory, copy the installation files, modify the system logo and beautify the installation interface.
Install EASYBOOT first.
After the installation is completed, open the installation folder and you will see a folder composed of disks. Click enter. Delete all contents except one EZBOOT folder, and empty the contents under that folder.
Then create a new folder under the disk folder and name it system. This folder is used to store system files that need to be integrated. You can put multiple systems that need to be integrated here. The installation files of the system can be extracted from the deep system disk. Take my fairy tale castle V2 as an example. There are three folders under it, namely xp62, vsxp and mcxp. The corresponding systems are deep V6.2 system, VISTA beautification version 6.2 and MAC beautification version 6.2. ..
After doing the above work, start beautifying it. Let's not talk about the production of beautification bags here. You can download it online, and there are many more. Just replace the file after downloading. For example, download a MAC beautification I386 replacement package and copy all the files in it to the I386 file of the system you want to replace. VISTA beautification package will do the same.
If you are not satisfied with the beautification package provided online, you can do it yourself, but this is not the theme of this post, so I won't say it here. In addition to using beautification package instead of beautification method, there is also a method to beautify the system, which is to integrate and install system beautification software.
In my "My Fairy Tale Hall" V2 disk, the beautification of VISTA version was replaced by beautification package, while the beautification of MAC version was completed by integrated installation of beautification software. As for this integrated software installation method, it is necessary to write some script programs to assist the installation, which is also omitted here.
What needs to be changed after the system beautification? OEM, system information, wallpaper, etc. all need to be changed to their own, otherwise how will others know that you made this disc? Isn't that bragging enough? Therefore, these must change.
Pick up a pen and write down the file name below. These files are the key to changing the system logo.
1, WINNTBBU.DLL this DLL can change the screen when the system is installed. Open WINNTBBU.DLL with Resource Hacke, double-click Bitmap-103- Delete 1033, right-click 2052 and replace it with your own picture. Click "Operation" to add a new resource with the name of 103 and the language of 2052. Ok, let's see if 1033 and 2052 in the bitmap103 are the same. Double-click the bitmap-153- and repeat the previous operation.
Upon completion, your system installation interface will be successfully changed. Remember to replace the original I386 file with the changed file.
2.bliss.jp_ file is the desktop diagram of the system. You can choose a good picture and save it in the root directory of disk D. Remember to change the name of the picture to bliss.jpg, and then run the following command to CAB compress the picture: maketab d: \ bliss.jpgd: \ bliss.jp _
After the compression, replace bliss.jp_ in the original I386 folder with bliss.jp_ so that you can successfully set your own desktop wallpaper.
3.OEMINFO。 IN_ This file records the system information. Open it with winrar and change the content to what you want. Where to change, open the document and you will understand. Save the document to the root directory of disk D after modification, and then run the following command for CAB compression: make CAB D: \ oeminfo.ini D: \ oeminfo.in _ Replace the source file after compression.
4.oemlogo.bm_ The pictures in this file are OEM icons. You can make your own icon with the size of 160x 120, which can be slightly larger or smaller, but you should pay attention to aesthetics. After making the icon, save it in BMP format. The icon is named oemlogo.bmp and has a D disk. You should also run the following command to compress CAB: make CABD: \ oemlog.bmpd: \ oemlog.bm _ After compression, remember to replace the original file under I386.
5.SYSDM。 This file records the properties of the system panel. After unzipping with winrar, open it with Resource Hacke and select the dialog box-10 1-2052. You can see how to change it. Remember to compress the cab after modification. The command is as follows: makeCAB d: \ sysdm. CPL d: \ sysdm。 CP _ Remind again, remember to replace the file in the original I386.
Well, after the above modifications, a system with your logo is basically completed. If there are no other requirements afterwards, you can skip the following paragraph and see how to make ISO files with EASYBOOT.
The installation file of the system has been completed, and it is necessary to start integrating drivers and common software. Let's start the second step of making a tutorial.
Second, integrate driver installation and common software installation.
First of all, let me talk about the integrated installation of drivers. There are many people discussing this problem on the forum. There are various methods, including nlite integration and DPS integration ... each method has its own advantages, so I won't comment and explain it. Friends who want to know go to the forum to search for themselves.
Next, I will talk about the method of integrating drivers in V2 CD that I saw in foreign forums. It's very simple to use. I'll say it a little, and everyone will understand.
First download DriverFiles.zip (download address: http://www.msfn.org/staff/alanoll/driverfiles.zip). Do not decompress after downloading. Create a new directory under the system installation folder and name it $OEM$. This directory should be at the same level as the I386 directory. After construction, extract all files in the compressed package to this folder, then open the I386 folder, find the winnt.sif document, open it with notepad, and add the following code in the [GuiUnattended] section:
DetachedProgram=。 \system32\cmd.exe "
(parameter ="/Q /C in %SystemRoot%\SYSTEM32\$WINNT$). INF) DO (FOR %J IN (%I\$OEM$) DO (if there is% j (start/min/d% j NirCmd.exe executes hidden driver. cmd)) "
After the above operations are completed, the drivers are arranged next. If you only need to integrate the local driver, you can use the optimizer to make a backup and then extract the backup file. Put the extracted drivers into $OEM$\Drivers, and the driver folder needs to be created by yourself.
If you need to integrate a universal driver, you must download a universal driver package from the Internet. After downloading, decompress all the driver package, create a folder named Drivers to store these decompressed driver files, and then use 7z compression to compress the Drivers folder. Finally, just put Drivers.7z in the $OEM$ folder.
If anyone doesn't know what the file structure under Drivers should be, please see the following figure:
├———$OEM$
│.......├———Drivers
│................├———C-Media CMI8738 6.39
│................├———medion 7 134 2 . 3 . 1.0
│................├———Monitor
│........................├———AL7 12
│ │ ................ ├———— NVIDIA Force Device 77.72
│................├———Samsung ML- 12 10
│................├———Laptop
│........................├———Touchpad
│........................├———Infared 12.6
│.......7za.exe├———
│.......├———Drivers.cmd
│.......nircmd.exe├———
│.......Process.exe├———
│.......SetupCopyOEMInf.exe├———
│.......WatchDriverSigningPolicy.exe├———
├———I386
│.......├———winnt.sif
After completing the above steps, the driver is integrated. I also mention the principle of this drive installation method here. If you want to study it, just have a look. If you don't want to study, just go with the flow. If you don't want to study it, don't watch it. I'm afraid of making a fool of myself.
Principle: When Windows installer reads the GuiUnattended part of winnt.sif, it will run Drivers.cmd and Drivers.cmd batch processing. First, the Windows installer will be suspended, and then the WatchDriverSigningPolicy.exe will be executed to make Windows accept unsigned driver installation. The batch file will check whether there is a compressed driver package, and if there is, it will be decompressed. Then run SetupCopyOEMInf.exe to scan every subfolder under the $OEM$\Drivers folder, and handle all. Inf file (copy the specified. Inf file to %windir%\Inf), so that Windows will find all drivers of plug and play hardware after checking hardware devices. Then continue the Windows installation process. Because this operation is completed before Windows checks the hardware device, Windows can find the driver in the Drivers folder.
Look at the time, it took more than an hour to write so much. That's a real pity. I'm not free today. I will continue to write tomorrow or the day after tomorrow. Let's take a look at the contents above.
6.24
I feel dizzy. I just wrote a long paragraph, but somehow I refreshed it. I'm falling apart. The mood of sunshine is gone, and depression is like this sultry weather, which makes people feel uncomfortable. There's nothing we can do. Rewrite it.
Yesterday, we completed the integration of drivers. Today we will talk about the integration of common software. Once these two points are achieved, the installed version of the system can be as convenient as the GHOST system. Imagine that your system will automatically install drivers, office and other programs, and it is also an installed version. How cool is that feeling?
How to integrate the installation of software? I often use the following three methods:
1. Use the silent installation parameters of software.
2. Make an automatic installation package using SfxMaker7Zip.
3. Write a script to help with the installation.
To install the software in an integrated way, the biggest difficulty is how to install it unattended. As we all know, the general installation of software requires us to choose the next step for installation. And the system installation is unattended. If you need someone to see how depressing the next step is? It is best to wait until the system is installed before installing the software.
In order to make us no longer depressed, there is a saying of pretending. If you know the silent installation parameters of a software, you can write a batch to perform the automatic installation of the software, and then the software will be installed according to its default settings.
For example, winrar's silent installation parameter is /s, so you can save the following code as a batch file:
Start winrar /s
A short line of batch processing, named winrar.bat after saving. Put the winrar installation files and batch files in the SVCPACK folder under the I386 folder. Then find svcpack.in_ document in the I386 folder, decompress it with winrar, and then add winrar.bat under the [SetupHotfixesToRun] field.
Then save it, and use cab compression to compress svcpack.inf into svcpack.in_. Specific commands are as follows:
make cab c:\ SVC pack . INF c:\ SVC pack . in _
After the above actions are completed, winrar.bat will be called when the component is registered within 13 minutes after the system is installed and installed with winrar.
Having finished the method of integrating and installing common software with silent parameters, let's begin to talk about how to make automatic installation package with SfxMaker7Zip.
Although some parameters of software silent installation can be found online, they are few after all. In order to deal with software without silent installation parameters, we will use SfxMaker7Zip. The function of this software is to make the 7z compressed package into a self-extracting file, and at the same time, you can set shortcuts.
Limited to SfxMaker7Zip, it is a self-extracting installation package, so we can't register it in the registry, so the software we use can only be a portable application. There are many green versions of software, such as QQ, which shows that this tool is still very useful. As for its specific usage, I won't say it here. I will send a tutorial in the attachment.
After the self-extracting installation package is completed, please refer to the operation on the svcpack.inf document for the method of adding it to the system for installation.
Next, let's talk about the last one, writing scripts to assist the automatic installation of software.
For some software that has no green version and does not know the silent installation parameters, we can use this method to solve it. Although you have to write a script, it is very simple. You don't need to know anything, as long as you can modify the script I provide below. Regarding the language of the auxiliary installation script, I recommend using AU3 because it is easier to use.
Below I provide an AU3 script code automatically installed by winrar:
RUN(" winrar 3.7 1 . exe ")………………………………………………………………………………………………
Winwaitactive ("Winrar 3.71Simplified Chinese Beautification Edition", "")
Send ("{enter}")
WinWaitActive("WinRAR Simplified Chinese Version Installation ","")
Send ("{enter}")
WinWaitActive("WinRAR Simplified Chinese Version Installation ","")
Send ("{enter}")
The above lines show that when the window titled' Winrar 3.7 1 Simplified Chinese Beautification Edition' is activated, the analog keyboard presses Enter.
Line Sleep (3000) .....................................................................................................................................................................
Winkiel (", ”)…… 1 1、 12、 13、 14、 14、 15、 16、 16、 17、 18、 18、 19、 / kloc-0/9、 19、 18、 19、 19、 19、 19、 19、 19、 19、 19、 19、 18、 1 9、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 / kloc-0/9、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19、 19
When using AU3 to write an automatic installation script, you need to understand the various processes of software installation first, and then determine how many times you need to press Enter, whether to use the close window command, and so on. If you don't understand anything, please refer to the help document of AU3. Reading more help documents is an important way to improve.
After writing the script, don't forget to compile it into exe format. Remember that the called installer needs to be placed in the same directory as the auxiliary script and can be copied to the svcpack folder together. The method of calling the script during system installation is also to modify the svcpack document.
Don't ask me why I always modify the svcpack document, and I don't know why. If I have to explain, there is only one thing, that is, I am lazy, and I don't want to find the second one if there is one method that can be used.
As long as you learn the above three methods, you can basically integrate all the software into the installation system. There are seven kinds of weapons in Gu Long, but we are only ignorant. It's a shame that you can only travel around the world with three kitchen knives. However, as long as you can create unique martial arts with limited resources, will the ancient predecessors be happy?
Ok, I admit that I made another nonsense mistake, the soldier with a brick in his hand and that, yes, you, the aunt with a tomato in her left hand and a rotten egg in her right hand. I know I was wrong, so please leave me alone this time.
Today we discussed the integrated installation of software. Although there are not many things, it takes a little time to practice and explore, so let's stop here. Tomorrow we will talk about the third step of installing the system disk. Remember to come to class on time and don't forget to bring cheat sheets.
Whispered: don't be like the soldier with the brick. Write your notes on the brick, and it will be gone in one shot. It's too late to cry. And the aunt who took tomatoes and rotten eggs, let's stop learning. Seeing that her left and right hands are not working, can she still write with her feet?
Ok, today's class is over. Class is over!
6.27
I haven't updated it for a few days. I don't know. I am a little busy these two days and have no time to write this tutorial. Let's continue now.
Let's feel the weather first. The sky is gloomy and there is no sunshine, but it doesn't rain and it's stuffy. It's been this kind of weather these days, and I don't know when it will rain happily.
Last time, we completed the installation of how to integrate software in the system. By using the T 13 interface (that is, 13 minutes left in the system installation), we can easily integrate the system installation. Moreover, the T 13 interface is waiting, which means that when the system is installed, it will wait until all the programs on the T 13 interface are installed before continuing. Unlike the T39 interface, you don't have to wait. If you use this interface, the CD production company will continue the following installation regardless of whether the program you set has finished running.
This is also the reason why I said before that the installation of system integration driver needs to be suspended, because it takes a long time for hardware judgment and driver installation, which will definitely exceed the time limit of T39.
Well, there was a lot of nonsense at the beginning. Please have a look around. These are useless for the primary packaging of the system. After two days of courses, our system is basically ready. The rest is to make the CD startup menu in the system and generate the ISO file.
But before that, we must also use nMaker to generate the boot file of the system. You Maker is a program written by an expert in this forum. Download address and usage, CD production company, can be found in the search forum, so I won't say much here.
Let's talk about how to make a CD-ROM running menu with multimedia generator.
Compared with AMS, the multimedia generator is as simple and easy to use, without generating some inexplicable folders, and can also specify files in relative directories.
Using multimedia generator is actually very simple, so I won't talk about the detailed use process, because I don't have this software here now. So I will talk about a few key points and other specific production processes. Let us find out for ourselves. It's simple.
1, you need to create a folder under the disk directory, just name it SOFT, and store the software you need to put on the CD, such as Thunder and QQ.
2. When using the multimedia generator, the link address of the installation software should be relative, not absolute. For example, if your disk directory is under drive D, then the absolute address of QQ is D:\DISK\SOFT\QQ. EXE, not like this, but like this.
3. If you want to call and install the software in the SVCPACK folder on the menu, you can also use the relative address.
Probably the above points. This is easy to do, and you can learn it after a few fumbles.
Then let's talk about using ESAYBOOT to make iso documents.
EASYBOOT is a CD-ROM startup interface software developed by China people, which is very easy to use.
I won't talk about the detailed use process. There are many tutorials on the Internet. In fact, there is no need to go to the tutorial at all, and it will take a while to fully understand. I just want to remind you that when generating ISO, remember to check the optimized ISO structure.
The main reason for this is that when there are multiple systems in the CD, it will only use one file. This is why some system disks contain more than 700 megabytes of files, but the generated CDs are CDs.
The principle will not be explained. Anyway, it's a beginner's course, and it doesn't need to be too in-depth. As long as you can use it, as for understanding the principle, let's talk about it later.