VMware Communities
JimmyW
Contributor
Contributor
Jump to solution

Guest system clock doesn't stick

I have a Win98 guest in 6.02 on an XP64 host. I have installed VMware Tools and chose not to sync the guest's clock with the host. I re-set the guest's clock to a different date, but when I reboot the guest, it is synced with the host's. How can make the guest's clock remain at the date that I chose? Thanks.

0 Kudos
1 Solution

Accepted Solutions
AWo
Immortal
Immortal
Jump to solution

Sorry, I made a mistake, Smiley Sad

change

tools.synchronize.tools.startup = "0"

to

time.synchronize.tools.startup = "0"

or

time.synchronize.tools.startup = "FALSE"

AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =

View solution in original post

0 Kudos
14 Replies
continuum
Immortal
Immortal
Jump to solution

see http://sanbarrow.com/vmx/vmx-always-start-tonight.html

description of vmx-parameters:

VMware-liveCD:


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks very much, but I can't seem to get it to work. I added the line, rtc.startTime = 1187395171 to my VMX file. tools.syncTime = "FALSE" When I start the guest, the clock is the current datre/time, although I am advised the Windows has adjusted for DST. Perhaps I'm doing something wrong. I can post the VMX if it will help.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

Hi

yes - let me see the vmx.

For best results I would recommend to NOT install the vmware-tools at all - just install the drivers only.

Ulli


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks! The vmx is attached.

Jimmy

0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks, I sent the vmx by email. I found, however, that I can still adjust the clock in my guest by resetting the host, so that's a workaround for the moment.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

If I start the VM here it says 18.08.2007 - so that seems to be ok.


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Perhaps it has something to do with my host. That was the date I had selected.

0 Kudos
continuum
Immortal
Immortal
Jump to solution

You should not change clock on the host.

Jimmy - copy this next lines to a new file named "test.vmx" and start it in Workstation.

Hit F2 early - enter BIOS and check the time. It should be some time in 2004.

This is what you can get ... have you noticed the start-time calculator on my site ? http://sanbarrow.com/files/time-machine.zip

config.version = "8"

virtualHW.version = "6"

displayName = "I_will_always_start_9th_July_at_19:46_2004_Berlin-Time"

guestOS = "winxppro"

scsi0.present = "TRUE"

memsize = "256"

ide0:0.present = "false"

ide0:0.fileName = "my.vmdk"

ide1:0.present = "false"

ide1:0.fileName = "my.iso"

ide1:0.deviceType = "cdrom-image"

floppy0.fileType = "file"

floppy0.fileName = "my.flp"

floppy0.startConnected = "false"

Ethernet0.present = "TRUE"

Ethernet0.addressType = "generated"

sound.present = "false"

sound.virtualDev = "es1371"

sound.fileName = "-1"

usb.present = "false"

priority.grabbed = "normal"

priority.ungrabbed = "normal"

isolation.tools.hgfs.disable = "TRUE"

isolation.tools.dnd.disable = "TRUE"

redoLogDir = "."

rtc.startTime = 1089395200

tools.syncTime = "false"

time.synchronize.continue = "false"

time.synchronize.restore = "false"

time.synchronize.resume.disk = "false"

time.synchronize.resume.memory = "false"

time.synchronize.shrink = "false"

time.synchronize.tools.startup = "false"


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks very much. I'll give this a try on Monday. I already downloaded your calculator. It's very handy. Is there a way to copy the numeric date value so that I can paste it in a VMX?

Jimmy

0 Kudos
continuum
Immortal
Immortal
Jump to solution

Rob picked up the idea and made a more functional one - see

http://petruska.stardock.net/software/Files/TimeMachineSetup.exe


________________________________________________
Do you need support with a VMFS recovery problem ? - send a message via skype "sanbarrow"
I do not support Workstation 16 at this time ...

0 Kudos
AWo
Immortal
Immortal
Jump to solution

I used the following settings to separate the guests clock from the hosts one:

Time relevant settings in .vmx:

tools.syncTime = "FALSE"

rtc.diffFromUTC=

time.synchronize.continue = FALSE

time.synchronize.restore = FALSE

time.synchronize.resume.disk = FALSE

time.synchronize.shrink = FALSE

where the magic setting was:

tools.synchronize.tools.startup = FALSE

Otherwise you always get the time set to the host time as long as you have the tools installed.

AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks. I added all of the lines you suggested and the value 1187136000. Still, the guest syncs with the host. Maybe it's an issue with an WinME guest on an XP64 host, but I woldn't think so.

0 Kudos
AWo
Immortal
Immortal
Jump to solution

Sorry, I made a mistake, Smiley Sad

change

tools.synchronize.tools.startup = "0"

to

time.synchronize.tools.startup = "0"

or

time.synchronize.tools.startup = "FALSE"

AWo

vExpert 2009/10/11 [:o]===[o:] [: ]o=o[ :] = Save forests! rent firewood! =
0 Kudos
JimmyW
Contributor
Contributor
Jump to solution

Thanks! time.synchronize.tools.startup = "0" worked.

0 Kudos