WinXP and Win.net server are two operating systems produced by Microsoft, but the price is too far off and we want it to be a lot of money. But if you really need it, can you just buy it back?
The answer is of course: "No", smart people always want to come up with a variety of ways to complete their desires, there is a Hungarian 3am labs invented the tool Ntswitch, its introduction is this: Microsoft's. NET services have always been installed in the WindowsNT series of the server version, if you only WinXP Professional Edition, but also want to use their own machine to provide. NET Service project, then use this ntswitch! He can fulfill your desires, and after the conversion you will have all the functionality and features that you have on the server version, leaving you with no sense whatsoever. NET service is actually running in WinXP Professional Edition.
Is it not so magical? Today I will reveal the mystery. But if the experiment is successful, it involves a problem, is Microsoft's sever version of the operating system really worth so much?
In this article, I use an example to test a software that could not be installed under WinXP, and we will try to get it supported.
Here are the specific test steps:
1. Run Ntswitch.exe in Windows XP Professional to convert Windows XP Professional to Windows.NET server
2. Reboot the system and go into normal mode (no Safe mode) and discover:
2.1. The interface before entering the system becomes the Windows.NET server
2.2. After logging into the system, it is found that the operating system does not need to be cumbersome to reactivate the program.
2.3. The relevant information in the converted system's "My Computer" is the same as the one shown in the original Windows XP, as shown in the following illustration:
2.4. The system's virtual memory function cannot be used. If the system runs too many programs, it can lead to insufficient memory.
2.5. Some software that could have been installed on the server's operating system can now be installed (I tested Microsoft SQL Enterprise Server 2000)
3. After loading the software, run Ntswitch.exe to restore Windows. NET Server back to the original Windows XP Professional
4. Reboot the system and find:
4.1. Microsoft SQL Enterprise Server 2000 was successfully installed, as shown in the figure:
4.2. Successful running of Microsoft SQL Enterprise Server 2000 is it amazing? Originally, Windows is also a DIY system, if more brain, we can let Windows 2000 into the Server version, let Windows Server 2003 become WinXP and so on. As shown in the figure:
4.3. After you try to run the Enterprise Manager for SQL Enterprise Server 2000, as shown in the figure
4.4 All the original programs are working properly.
It's so cool! It turns out that you can actually upload SQL Enterprise Server 2000 on Windows XP Professional!
Next run the software, so that the operating system to convert again, to restore the original installed in the machine WinXP, running a variety of programs found that there is no exception, that this software is very useful and will not damage the operating system, but here or to advise you computer players, Before using this software, it is best to first ghost the system, in case there is a real problem, there is room for recovery, so as to avoid reloading the system so troublesome.
Evaluation conclusion: Because the software is only modify the operating system's registry, to deceive the system's purpose, so the memory footprint will not increase, but there is a more serious problem, that is, the system's virtual memory function can not be used, the entire system running all depends on your machine's physical memory! If your memory is small, it will be more difficult to run.