So, it seems, we figured out the theory, now we turn to practice, and so, at the beginning we load according to our windows, run the console as administrator and execute commands, for a 32h bit system FORCE WINDOWS TO USE UTC CLOCK DUAL BOOT SOFTWAREBut when loading and synchronizing the time, Windows subtracts 3 hours from the hardware time (or some other correction for the time zone) so that the software time is correct. For the user, there is no difference, you still need to add an amendment to your time zone. Localtime- in this version, the software clock also runs according to Greenwich Mean Time, but the hardware clock runs according to the time of the local time zone. This is done on servers so that each user can get the correct time for their time zone. And already users locally add to this time a correction for the time zone, for example, plus +3. For example, if your time zone is GMT + 3, Moscow, then the clock will be three hours behind. That is, the clock gives the universal time in the zero time zone. UTC- both hardware and software clocks are in Greenwich Mean Time. There are times when, when installing a second system, it usually happens linux, the time in the systems starts to get lost, for example, you worked under your linux "ohm and decided to go to windows, and found that the time and date are completely wrong, or vice versa, this is due to differences in the time format, these operating systems work with it differently, a little theory, and so, we start with linux, these operating systems work with UTC
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |