I did a clean install of VSIDO Jedi on my desktop the other day; this happens to be the computer I dual boot with Windows 7. As usual, Debian (Fedora does this too, Slackware not so much) insists that the computer hardware clock be set to UTC even though I told the installer that the BIOS clock was set to local time - which Windows insists on. Since I don't share any files where a creation time would be an issue (only 5 hours difference any way) this is more of an annoyance than anything else.
This time around, since Windows is the culprit, I decided to fix the problem from the Windows side of the machine and leave Debian/VSIDO alone to do it's thing and keep the hardware clock set to UTC - which is preferable. From the Windows side there are two options -
1. Change your time zone to whatever makes the Windows clock show the right time - in my case, Windows thought the computer was in Hawaii.
2. Make Windows 7 understand that the hardware clock is set to UTC. This can be done with an edit to the registry -
http://crashmag.net/configuring-windows-7-support-for-utc-bios-timeUse notepad so that the text is saved with the proper formatting and create a file with the following:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\TimeZoneInformation]
"RealTimeIsUniversal"=dword:00000001
sace as <filename>.reg -> the .reg is required, I believe.
Start regedit (you will need an administrator password or appropriate permissions) and then import your filename.reg
Next time you log in, the Windows clock should be showing the proper time for your timezone; if you tried option #1 above, reset your time zone and then sync Windows from the clock settings.
For either method, uncheck the box that allows Windows to automatically adjust for Daylight Savings Time; some users have had trouble with that.