This is a problem caused by my "out of nothing". It may be helpful to record it.
One of our testsProgramIt is written in C #. It reads a configuration file, which contains serial port settings or network IP/port settings.
I once changed this program to "Windows 2000 compatibility mode", and later I found that this program could not parse the configuration file correctly.
The reason is beyond my capability. I think it is related to the differences in the running environment in XP compatibility mode.
In Native XP, the program has sufficient permissions to access or apply for the resources it needs. In Windows 2000 compatibility mode, the operating system creates a different environment for the program to run "virtual". In this environment, there are restrictions on program access and resource application. In other words, running the. NET Framework in XP on Windows 2000 is a problem. I think this is a bug left behind by Microsoft's compatibility model, but few people need to use this model, which is irrelevant.