Date changes on Boot of XP (not bios prob)

[destructa]

System Spec: athlon Xp 2700, 1gb Ram, radeon 9500, 120gb hd/60gb hd, aopen cdrw, dvd rom, hercules muse 5.1, pci asdl modem. opeating system dual boot: windows 2000 pro, windows XP home.

When I boot into Windows XP my date is set to 11 January 2003, i can change it back, reboot and it changes back agian. However, if i change it then reboot into Windows 2000 it stays at the correct date until i reboot again into XP. I have run a virus scan (Norton 2004 Pro) and found no viruses, and have also used Adaware 6 to see if any spyware etc is on my system and found nothing. Could this be a registry thing?

Any help is greatly appreciated.



If it annoys Microsoft then it's worth doing, and doing well!!

 

[bcastner]

I hate time issues, as they are very hard to track down when they exhibit symptoms as you show.

I believe the issue has to do with how compliant in terms of ACPI your BIOS is for XP, and possibly whether XP mis-identified your ACPI type during installation. Your issue sounds as if your BIOS is APM compliant (fine for Win2k) but not ACPI compliant (not good for XP).

See if you can find an upgrade to the BIOS.

As a direct answer to your question, this is all I have ever seen about the registry entries for W32time:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

The format for the list of entries is:
Value Name : Data Type
Description
Values

W32Time Service Registry Values
AvoidTimeSyncOnWan : REG_DWORD (optional)
Prevents the computer from synchronizing with a computer that is in another site.
0 = the site of the time source is ignored [default]
1 = the computer does not synchronize with a time source that is in a different site
GetDcBackoffMaxTimes : REG_DWORD (optional)
The maximum number of times to double the backoff interval when successive attempts to find a domain controller do not succeed. An event is logged every time a wait of the maximum length occurs.
0 = the wait between successive attempts is always the minimum and no event is logged
7 = [default]
GetDcBackoffMinutes : REG_DWORD (optional)
The initial number of minutes to wait before looking for a domain controller if the last attempt did not succeed.
15 = [default]
LocalNTP : REG_DWORD
Used to start the SNTP server.
0 = do not start the SNTP server unless this computer is a domain controller[default]
1 = always start the SNTP server
NtpServer : REG_SZ (optional)
NtpServer : REG_SZ (optional) Used to manually configure the time source. Set this to the DNS name or IP address of the NTP server to synchronize from. You can modify this from the command line by using the net time command. Value is blank by default
Period : REG_DWORD or REG_SZ
Used to control how often the time service synchronizes. If a string value is specified, it must be one of special ones listed below. If you specify the string value by using the numbers (65535 for example), then create the value as a REG_DWORD. If you use the word to specify the string value (Bidaily for example), then the entry should be created as a REG_SZ.
0 = once a day
65535, "BiDaily" = once every 2 days
65534, "Tridaily" = once every 3 days
65533, "Weekly" = once every week (7 days)
65532, "SpecialSkew" = once every 45 minutes until 3 good synchronizations occur, then once every 8 hours (3 per day) [default]
65531, "DailySpecialSkew" = once every 45 minutes until 1 good synchronization occurs, then once every day
freq = freq times per day
ReliableTimeSource : REG_DWORD (optional)
Used to indicate that this computer has reliable time.
0 = do not mark this computer as having reliable time [default]
1 = mark this computer as having reliable time (this is only useful on a domain controller)
Type : REG_SZ
Used to control how a computer synchronizes.
Nt5DS = synchronize to domain hierarchy [default]
NTP = synchronize to manually configured source
NoSync = do not synchronize time

The Nt5DS setting may not use a manual configured source.
The Adj and msSkewPerDay values are used to preserve information about the computer's clock between restarts. Do not manually edit these values.

Again, If there is a BIOS upgrade available do so, otherwise you should force compliance with a re-installation of XP to a non-ACPI model:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;299340

 

[AP81]

Hard to say exactly what it is. WinXP and W2k run independent of eachother, so any changes to dates in WinXP will not impact on W2k. In WinXP, go to start > run > type: msconfig and go to the startup up. Make a list of everything listed there and post it back up. There may be something in there that is starting up and causing problems.