www.virtualacorn.co.uk/forum

There seem to be issues with the link between the clock in Windows and that in RiscOS.

Symptoms include:

File datestamps are mangled when noving them between RPC and VRPC using ShareFS.

Newer doesn't work reliably as a result

Pipedream "today" function returns 1 Jan 1900

Is anything being done to address this?

Starting with Pipedream, some older versions are not year 2000
compliant and will roll back to 1900 if the year goes past 1999.

Just to confirm can you check that

a) The time/date on the RiscPC is correct
b) The time/date in Windows is correct
c) The time/date in VirtualAcorn is correct

What happens to the datestamps when moving files?

Checking: Windows shows date and time as 10:31, Feb 13th 2004
Alarm shows 10:32 13/2/04
RPC shows 10:32 13/2/04

I created a revised file on the RPC, and using VRPC dragged it from the share over an existing copy on the VRPC disc. It did not replace the older version.

I turned off NEWER and added FORCE and did it again.

The replaced file now has a datestamp of 23:34:29 04 Feb 1904

Can you give me a little more information as I'm unable to reproduce the problem as you describe it.

What version of RISC OS are you using on the RPC?
What version of RISC OS are you using on the VRPC?
What version of Windows are you using on the PC?
Do you have all the latest VRPC upgrades installed?

From what you're describing, you are using ShareFS to share a folder on the RPC and mounting it on the VRPC, is that correct? If so, do the datestamps look correct in the ShareFS filer window before you copy the file, as viewed on the VRPC?

Thanks,
Graeme

We have had another look at this, it could that you are not running the
latest BootUpgrade from the download section of the VirtualAcorn website. Can you install this and see if the problem persists.

OK now I'm puzzled. I am sure I did install the bootupgrade, but to be safe I installed it again, and the problem is fixed.

Before the reinstall after rebooting (Windows + VRPC) the clock reverted to the previous century. After the reinstall it correctly shows 2004.

Actually it doesn't display it, because although I can change Alarm to display the century, I can't make that change permanent. There is no Save option in Alarm's menu. How do I make the format string change permanent?

Glad the datestamp problem is fixed.

To change the time click MENU over Alarm on the iconbar, go to "Set Clock" set the time and click on SET.

To change to config of the Alarm display press MENU over the icon on the icon bar and click on "Setup". Set the display as per your requirements and click on the OK button.

Note that SyncClock (in Boot.Choices.Boot.Tasks and Boot.Choices.Boot PreDesk) will resynce the VA clock to the PC clock every 5 seconds and my override manual changes you have made to the time.