Manual time set bug

Having said that, as I recall there were peculiarities with time setting as well as display settings that seemed to go away when I fitted the widget. Do you also have loss of DPMS settings?

No loss of DPMS settings & I do have a widget fitted.

Squirrel genetics…

Shared DNA

I now see that the Armini does have a battery whereas my BB -xm doesn’t. I only have the resolver problem at switch on – not restart. Could my clock being reset to 1970(?) be having some unwanted interaction with more recent ROMs that doesn’t show on a system that’s battery backed?

Is there a command I can stick in an obey file to set the clock to a recent time to test my premise?

Fred

I have a BB -xm with no battery backup but do have a CMOS dongle and have noticed some strange things myself on start up on occasions.

I have powerline adaptors acting as the ethernet link through a switch and the BB -xm set up to use NTP time servers but I have to be careful on the order I start up things.

If I start up the Powerline first, the one by the BB -xm as the one by the router is always on, and wait until that has a link and then start up the BB -xm and switch then everything is fine but if I start up the other way round or I’m I do not wait for the Powerline link to go steady then the boot up takes a while longer to get to the main screen and I have noticed sometimes the date is set to 1970 or FreeTime, which I use as well, states it has reset the time.

I have the latest but one ROM and also the latest HardDisc image from Nov12.

Hope this helps

Doug

Thanks Doug but I don’t think that relates to what I’m seeing. The Powerlines are always on and I can re-connect the BBs supply to reproduce the problem consistently anyway. Presumably the resolver is working for you to use FreeTime. Doesn’t explain why the issue is with one ROM & not another either.

Doing a search of the forum I’ve realised I was engaged in this same conversation last June. I’m going to need some extra flash memory between my ears or maybe stick to rebooting the computer rather than myself.

There didn’t seem to be a resolution then, it just stopped being a problem a few ROMs down the line. Perhaps I’ll just rely on the ReInit obey file for now and see if it sorts itself again.

The 5th February ROM fixes the problem. Resolver/time etc. works without Resolver needing ReInit-ing.

The CVS mentions extended permissible file size with a warning about older file cores. Is that something to worry about? For smaller files?