| Forum Home | ||||
| Press F1 | ||||
| Thread ID: 111000 | 2010-07-10 01:40:00 | How to set the computer clock to a defined time? | Renmoo (66) | Press F1 |
| Post ID | Timestamp | Content | User | ||
| 1117483 | 2010-07-10 01:40:00 | Hey all, Good to be back to Auckland after my two week trip :) I have installed an abandonware in the Virtual PC XP environment on my Windows 7 laptop. Unfortunately, the abandonware will not work if it is operated from the year 2010 onwards. As such, I had to manually reset the timezone in the virtual environment to year 2009. However, within a few seconds time, the time would revert back to the correct time despite having uncheck the "time auto-sync" feature in the Time settings. Question: Is there any way that the time can be set to the past and remain as it is? Thanks :) |
Renmoo (66) | ||
| 1117484 | 2010-07-10 01:50:00 | Possibly it is resetting the time from the host os, or system clock? | feersumendjinn (64) | ||
| 1117485 | 2010-07-10 02:15:00 | You could try re-setting in the bios. Or perhaps you might need to remove the battery in the computer and replace it again after a brief few moments. Good luck. | kati kid (14729) | ||
| 1117486 | 2010-07-10 05:32:00 | Possibly it is resetting the time from the host os, or system clock? I don't want to alter the clock of the host computer because my file synching between computers would go haywire. |
Renmoo (66) | ||
| 1117487 | 2010-07-10 06:15:00 | I think you will need a separate virtual machine rather than the integrated Windows 7 one. Give Virtualbox a try, that should be able to do it.. |
Agent_24 (57) | ||
| 1117488 | 2010-07-10 10:40:00 | go back in the posts a few years, and you should find discussion and resolution of this, involving a script in the boot sequence of the virtual machine. original problem was non Y2K compliant SW that was not availably Y2K compliant. | angry (15305) | ||
| 1117489 | 2010-07-10 11:10:00 | go back in the posts a few years, and you should find discussion and resolution of this, involving a script in the boot sequence of the virtual machine. original problem was non Y2K compliant SW that was not available Y2K compliant. | angry (15305) | ||
| 1 | |||||