Add external program loads to PE)

 

1. add or remove external serversProgram
The external program is in the "external program" directory of the CD. The corresponding configuration file is winpe. ini under this directory.
To delete a program, you only need to delete the subdirectory corresponding to the software in the external program directory, and then delete the corresponding link in winpe. ini to create a shortcut statement line.
Adding a program is the opposite. Put the green software in the external program directory, in winpe. add the corresponding link statement line in ini to create a shortcut (refer to other link statements, copy a line, you only need to change the shortcut location, name/Target Program directory name, and executable file name ).
The green software mentioned here refers to the ability to run green software in PE. Most of the green software seen on the Internet is not really green software. It should be called quasi-green software or installation-free software.
In fact, a lot of software that is not prepared for the PE can also be run in the PE. It is a stupid way to determine whether a common greensoft can be run directly in the PE and start the PE environment, find the directory where the software is located, copy a backup, and change the attributes of all files in the directory and directory to read-only. Double-click the executable files in the directory to check whether the files can run, after running, you can use all the functions to check whether they are normal. If no exception exists, you can simply add them as described above.
If a running exception occurs, some library files may be missing (this is usually prompted), or it writes something in its own directory, or it depends on some key values in the registry, this requires some hands and feet, such as preparing the missing library file and checking whether there is any configuration file under its own directory that can be modified, and running monitoring in XP to monitor which registry items it wants to read. This situation may not be able to be solved for different software solutions.

Appendix: Add office2003 process to PE
Use office2003 in the dark red leaves. Use ultraiso to open the peach PE and modify it directly. Do not unzip it. Save the modification.
1. Copy the red-leaf office directory to an external program.
2. Modify winpe. ini using the above method. You can add it to the file tool, for example:
Link % programs % \ file tool \ word, % curdir % \ Office \ winword.exe
Link % programs % \ file tool \ excel, % curdir % \ Office \ excel. exe
Link % programs % \ file tool \ PowerPoint, % curdir % \ Office \ powerpnt. exe
3. Modify Mao Tao regdoc. cmd, which is the batch file associated with the external program, and add
Call % TP % \ Office. cmd
4. After setting the parameters according to the above method, you will find that the task still cannot run, so the key is
Copy the MSI. dll in the System32 directory of the Local Machine and add it to the Red Leaf office directory.
Finished. Save pai_^.
2. Add a driver
This has never been used, so there is no experience, directly Ctrl + V
There is an important directory "pe_outerpart" in the external program directory, where all the core external components are placed. There are four cab packages, which are NIC/wireless NIC/sound card/graphics card driver packages, and the loaded frameworks are all set up. infcachebuild is automatically called in the CMD script. EXE processing driver. The job we need to do is to get the driver files and put them in the corresponding driver package. There are many driver backup tools to get driver files from the local machine. I am using the most stupid method. In the Device Manager, view the driver details, copy files one by one, and create a directory, in the corresponding driver package.
One step is to change the name of the copied inf file so that it can be sorted by file name at the top (I underline the file name ). I don't know if this step is necessary, because I didn't know which post I had read a few points and did not study it carefully. I honestly changed my name when I did it.
In this way, the extracted driver file may be large, and unnecessary driver files will be deleted after the test is successful. There are many files that can be deleted. You can refer to files of the same type of driver in the original driver package to keep similar files and delete others. Another stupid way is to delete one by one. Each time a test is deleted, a minimum driver file subset is found.

 

This article from the csdn blog, reproduced please indicate the source: http://blog.csdn.net/xiuxiugirl/archive/2010/03/16/5384077.aspx