OEM: It is sold by computer manufacturers with computers, that is, the random version.
RTM: It is a version for large-scale tableting by factories. The content is the same as the official version, but RTM. also has a 120-day evaluation version.
RVL: This is the official retail version.
OEM=RVL: Only the default value of its installation content is different, so there will be a difference. Random version - can be installed from a new hard disk, does not support upgrade installation. Upgrade version - uses upgrade installation, does not support new installation. Retail version - both installation methods are supported, which is why the retail version The price is the most expensive. As for the things after installation, they are the same. The difference is only in the supported installation methods! Little knowledge about software versions
Alpha version (internal beta version): Generally only run within software development companies. Not open to the public. Mainly, the developers themselves test the products to check whether there are defects and errors in the products, and verify whether the product functions are consistent with the instructions and user manuals.
Beta version (external test version): For external publicity, software development companies send informal products to typical users for free, allowing users to test the shortcomings and problems of the software so that they can be used in the future. Further improvements and improvements will be made before official release. Generally, it can be downloaded for free through the Internet, or it can be obtained from the software company.
Demo version (demo version): It mainly demonstrates some functions of the official software. Users can learn the basic operation of the software and expand the impact of the official product release. If it were a game, there would only be one or two levels to play. This version can also be downloaded for free from the Internet.
Enhace version (enhanced version or enhanced version): If it is a general software, it is generally called an "enhanced version" and will add some practical new features. If it is a game, it is generally called an "enhanced version" and some new game scenes and game plots will be added. This is the officially released version.
Free version (free version): This is generally software produced by individuals or members of the Free Software Alliance organization. It is intended to be free for everyone to use. It has no copyright and is generally free to download through the Internet.
Full Version: This is the official version, which is the final version officially released for sale.
Shareware version (*** version): In order to attract customers, some companies allow users to download certain software for free through the Internet. However, this version of the software may have some limitations on usage time or frequency, but you can use online registration or electronic registration to become an official version user.
Release version (release version): It is not an official version, has a time limit, and is also one of the publicity strategies to expand influence. For example, the distribution version of Windows Me is limited to a few months and can be downloaded for free from the Internet or given away for free by the company.
Uprgade version (upgrade version): When you have a previous official version of a certain software, you can purchase the upgrade version to upgrade your software to the latest version. The upgraded software has the same functions as the official version, but the price will be lower. This is mainly to provide discounts to the original genuine users.
Software version number naming rules In order to maintain software projects, we have put forward requirements for version management and control. For users, the version is directly reflected in the naming of the version number. So, how to name the version number? What about naming?
Let’s take a look at three common naming formats:
GNU-style version number naming format:
Main version number. Sub Version number [ . Correction version number [ . Compiled version number ] ]
English comparison:
Major_Version_Number . Minor_Version_Number [ . Revision_Number [ . Build_Number ] ]
Example : 1.2.1, 2.0, 5.0.0 build-13124
Windows-style version number naming format:
Main version number. Subversion number [Correction version number [. Compiled version Number] ]
English comparison:
Major_Version_Number . Minor_Version_Number [ Revision_Number [ . Build_Number ] ]
Example: 1.21, 2.0
. Net Framework style version number naming format:
Main version number. Subversion number [. Compiled version number [. Modified version number]]
English comparison:
< p>Major_Version_Number . Minor_Version_Number [ . Build_Number [ . Revision_Number ] ]Official description reference:/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemVersionClassTopic.asp
Note:
GNU-style version number management strategy. When the project is first released, the version number can be 0.1 or 0.1.0, or 1.0 or 1.0.0, if you are very low-key , I think you will choose the method where the main version number is 0; when the project undergoes partial modification or bug correction, both the main version number and the sub-version number remain unchanged, and the revised version number increases by 1; when the project is based on the original When some functions are added, the main version number remains unchanged, the sub-version number is increased by 1, and the revised version number is reset to 0, so it can be ignored; when the project undergoes major modifications or local modifications accumulate, causing the overall project to fail When there is a global change, the major version number is incremented by 1; in addition, the compiled version number is generally automatically generated by the compiler during the compilation process. We only define its format and do not control it manually.
Under Windows Version number management strategy: When the project is first released, the version number is 1.0 or 1.00; when the project undergoes partial modifications or bug corrections, both the main version number and the sub-version number remain unchanged, and the revised version number is increased by 1; when the project is based on the original When some functions are added to the project, the main version number remains unchanged, the sub-version number is increased by 1, and the revised version number is reset to 0, so it can be ignored; when the project undergoes major modifications or a large number of local modifications are accumulated, causing the overall project to When a global change occurs, the major version number is incremented by 1; in addition, the compiled version number is generally automatically generated by the compiler during the compilation process. We only define its format without manual control. In addition, you can also add after the version number Alpha, Beta, Gamma, Current, RC (Release Candidate), Release, Stable and other suffixes, you can also add a 1-digit version number after these suffixes. For users, if the main version number of a certain software is upgraded , the user still wants to continue that software, then
Companies that publish software generally charge users an upgrade fee; if the sub-version number or revised version number is upgraded, it is generally free.