First to know Regsvr32 Presvr32 must be familiar to everyone, in some computer tutorials or computer magazines can always see it, but such a high-profile "small star" in the eyes of many of us is very Mysterious, the original general article is rarely introduced to it, at most a few words to introduce how to use it to solve common problems, many friends may have used Regsvr32 many times under the guidance of some articles, but on it The "life experience" still does not understand, today I will use this article to dispel the doubts in everyone's mind, bring everyone to get to know this Regsvr32. Regsvr32 background and function Regsvr32 is a Windows system embedded program, not only exists under Windows 2000 /XP, it is found in the 材 赪 indows 98. Its main function is to register or uninstall the dynamic link library file (DLL) and embedded control (OCX), you can not underestimate it, with it, many software or operating system problems can be solved. Basic article Just now we talked about DLL and OCX. It is estimated that there will be such a problem in the hearts of many readers. What do these two Dongdong mean? What can they do? Don’t worry, let’s listen to the author slowly. . DLL file: The full name of the DLL file is the Dynamic Link Library, and the Chinese name is called "dynamic link library file". In Windows, a DLL file can perform a function like an EXE file, but it cannot run independently like an EXE file. It must be called by other programs, and it is very important for the execution of the program. Most of them are very important. When a program or system component is executed, it must be linked to a DLL file in order to function properly. In other words, DLL files are like a common library of functions in the database. Every designer can call them freely in their own programs, so that you don't have to write some basic functions yourself (because these functions are already used by DLLs). The file is complete, and it also makes the program smaller. Therefore, if a DLL file is lost, it may cause a software or a system module to malfunction and not work properly. OCX file: The full name of the OCX file is Object Linking and Embedding (OLE) Control Extension. The Chinese name is called "embedded object control". Its function is actually similar to the DLL file just mentioned. In fact, the so-called OLE we usually have very Familiar, simply speaking, you can use Excel data in Word, embed image files in WordPad, and so on. For example, the clipboard is like a simple data sharing, while OLE is an "object sharing." Just now we talked about the function of Regsvr32 is to register and uninstall the DLL file, then now there is a problem that bothers us. Since the DLL file plays the role of the public function library, why can't we call it directly in the program? Register once? In fact, the reason for registering a DLL file here is like the first time we entered school. Although you are sitting in the classroom, if you don't write your file, the teacher won't know you, and naturally you won't find it. you. By the same token, if the DLL file is not registered, there is no information about the DLL file in the system registry. Although it already exists on our hard disk, when the call is made, the system can not find the DLL file at all. Can report that there is no such DLL, so we need to register the DLL file at this time. [Small Tips] Windows system DLLs are not registered because they are already registered at the time of installation, but if the system cannot recognize these DLL files because of some circumstances, we still need to manually register again. Regsvr32 command format After finishing the above, I think a lot of friends have heard a bit embarrassed, don't worry, knowing that the above-mentioned plagiarism 傺癛 傺癛 傺癛 egsvr32 command is much easier. Everyone knows that all orders must have a format, and Regsvr32 is no exception. Let's take Windows XP as an example. Execute the "CMD" command in the "Start" menu → "Run" column, open the command prompt window, enter the Regsvr32 command and press Enter. You will see the Regsvr32 command format "Regsvr32 [ /u ][ /s ][ /n ][ /i [ :cmdline ] ] dll file name", as you can see, the Regsvr32 command has a total of four parameters, respectively: /s: After the registration or uninstallation is successful, the operation is not successful. Prompt box /u: Uninstall the installed control or DLL file /n: Do not call DLLRegisterServer, note that this parameter should be used with /i: call DLLInstall and pass it an optional [cmdline]; when using The instructions for uninstalling DLL commands in /u are often boring, so let's take a look at the Regsvr32 command format with an example. For example, if we want to register a shmedia.dll dynamic link library file saved in the C:\\Folder directory, then the command to execute should be "Regsvr32 c:\\folder\\shmedia.dll", and if you plan to uninstall after registration, it will be even more Simple, execute the command "Regsvr32 /uc:\\folder\\shmedia.dll". As shown in Figure 2, the prompt window for completing the task normally shows common mistakes. After using the Regsvr32 command for a long time, you may often see various error prompts. Here I find some representative errors to help everyone. To analyze and analyze. Error one: The specific path of the DLL file is not specified
This kind of error is more common. Generally, when registering a non-system DLL file, the reason is that the Regsvr32 program cannot find the specified DLL file in the default path and cannot complete the registration normally. The solution is also very simple, as long as the specific storage path of the DLL file is specified in the command, such as "Regsvr32 c:\\folder\\abc.dll" is a normal command. Error 2: The file type to be registered is incorrect. This error is relatively rare, but it is easy to appear in the newbie. The reason is that the file that the user wants to register is not a normal DLL file or OCX file at all, and Regsvr32 cannot complete the registration at all. The solution is to specify a normal DLL file or OCX file. For example, the original command is "Regsvr32 c:\\abc\\abc.txt", and the correct command should be "Regsvr32 c:\\abc\\abc.dll" (of course, you must ensure that the abc.dll file already exists and is completely correct. Error 3: The DLL file name is not specified in the command type.
This error is mainly the same as the previous example. The reason is that the DLL file name is not specified at all, so Regsvr32 naturally cannot know. I want to do something about it, so this prompt will pop up. The solution is to specify the DLL file or OCX file to be operated. Common Error Prompts After using the Regsvr32 command for a long time, you may often see a variety of error prompts. Here I find some representative errors to help you analyze and analyze. Error one: The specific path of the DLL file is not specified. This error is more common. It usually occurs when registering a non-system DLL file. The reason is that the Regsvr32 program cannot find the specified DLL file in the default path and cannot complete the registration normally. The solution is also very simple, as long as the specific storage path of the DLL file is specified in the command, such as "Regsvr32 c:\\folder\\abc.dll" is a normal command. Error 2: The file type to be registered is incorrect. This error is relatively rare, but it is easy to appear in the newbie. The reason is that the file that the user wants to register is not a normal DLL file or OCX file at all, and Regsvr32 cannot complete the registration at all. The solution is to specify a normal DLL file or OCX file. For example, the original command is "Regsvr32 c:\\abc\\abc.txt", and the correct command should be "Regsvr32 c:\\abc\\abc.dll" (of course, you must ensure that the abc.dll file already exists and is completely correct. Error 3: The DLL file name is not specified in the command type.
This error is mainly the same as the previous example. The reason is that the DLL file name is not specified at all, so Regsvr32 naturally cannot know. I want to do something about it, so this prompt will pop up. The solution is to specify the DLL file or OCX file to be operated.