I had the same problem with Lucid Puppy 5.1, except the difference was far more than just an hour, and completely random. Like, I'd start Windows or Puppy v.2, and the clock could be off by 6 hours or 9...you get the idea. I also had problems with shutdown.

I have no idea how it happened, but all of a sudden, Lucid doesn't do that anymore. IIRC, the only thing I did differently was to reboot into Puppy v.2 instead of trying to do a full shutdown. Now, my clock's okay, and no more shutdown problems.

I hope somebody here can give more concrete advice...I'm new at all this.....

Some say it is solved and some say it is us users that get the Devs intentions wrong and others maybe feel unsure what intention the Dev had setting up the script.

So my naive conclusion is that one have to experiment until one get it right by accident or pure luck or by smartness or by logical consistent grasp of what goes wrong.

I have none of the above so I used brute force testing some 20 or so Puppies until my computer always show the right time but I have no idea what cured it or how to get it right if it get wrong again.

One wild suggestion would be to start by deciding on what the cmos clock that the BIOS has access to should be. Should one use GMT or local time and what if the local time is DST due to summer or winter?

Logically GMT or UTC would be cool to use. One can go here to find out?

Quote:

UTC is also known as Universal Coordinated Time
Current Time Friday, 5 August 2011, 13:46:10

Then set up the BIOS CMOS Clock as utc and then answer the logical question as the Dev has set up that version of Puppy by clicking on the Clock and changing it if needed _________________I use Google Search on Puppy Forum
not an ideal solution though

I was looking to the config file where this info is stored, but no success on that. I wanted to manually edit that file ...

By now, I've set the hardware clock to Local time, and told to Puppy that it's UTC tme, and set my timezone to UTC instead of changing it, so Time is shown properly, but I don't know how it will affect other apps like e-mails and saved documents... Perhaps they are saved as UTC time, and shown incorrectly in other computers....

Iĺl try a "ram" boot, and try to copy settings to my current puppy install

Joined: 18 May 2005Posts: 11132Location: The Peoples Republic of California

Posted: Fri 05 Aug 2011, 10:20 Post subject:

wildirish wrote:

I hope somebody here can give more concrete advice...I'm new at all this.....

I figured it out. I got my system working perfectly on three clocks: (1) RTC, (2) system clock, (3) time servers.

Linux boots using RTC time and uses it for system time. RTC time is UTC unless told differently.

It could work perfect out of the box for our friends in England.

Before Linux, I used Microsoft and it worked out swell with no modifications because I'm in the same time zone as Bill and Steve.

Puppy, I think ships at a default offset of Perth time, which displays the same offset as Bill Gates time.

Now things start getting complicated. Maybe one of these days, I'll make an article on the web and post a lengthy step-by-step on going through all involved between booting with local RTC on the presumption that it is UTC, at what point we export the TZ variable and contact the time servers and what files to modify.

Simply stated, it worked best if I did all the work before the login. This meant establishing a network connection before the login to contact the time servers and export the TZ variable.

This involves an explanation which is very detailed and requires a person modify scripts.

I suppose a person could make a patch kind of thing for one Puppy version. But considering that Puppy changes the scripts between versions and none know the future, I think the best thing to do is a detailed explanation sufficient to work backward and hopefully forward in Puppy versions.

This is one reason why I found it worked great to sync with the time server, reset the RTC and export the TZ before the first Bash shell, which starts X runs._________________New! Puppy Linux Links Page

I never used or sync to a time server, I'm just using my hardware clock as Local Time, and configured Puppy according to that, telling Puppy that my hardware clock is Local Time, and that I'm in the -3 GMT.

It worked fine since frugal install until I did that "pfix=clean" bootup.

Now, I change the timezone settings to "-3", the clock changes, it shows the right time. I go to the "timezone" setting again to check, and it's changed to "UTC" instead of the "-3" I just set up.

When I reboot, clock time is wrong again. I go to "timezome" setting, and it's again set to "UTC".

It seems that when I change it to "-3" , it's not saved.

Goin to BIOS SETUP, before puppy boots, and the clock is OK, local time, it never changed.

Joined: 18 May 2005Posts: 11132Location: The Peoples Republic of California

Posted: Sat 06 Aug 2011, 10:21 Post subject:

fernan wrote:

Actually what solved the problem was to re-create that link file called "localtime".

There is something wrong with the puppy countrywizard , since if I run that, the link file is created wrong.

Both commands you gave work OK. I've tried both to avoid changing the clock through the countrywizard.

But I don't need to run it at every boot. Now it works fine.

I don't know if this should be informed as a bug, but it looks like...

I don't recommend reporting it. It is best classified as, well, let me think, how about a Puppy peculiarity?

This so called 'peculiarity' is extremely mind and doesn't affect most users. Since way back I thought there was a problem. Then, well maybe not.

It wasn't until I introduced the third clock, a time server clock did I realize it will take some thinking.

There have been some GUI pets added for this chore.

In my case I modified low level scripts to sync with the time service. I couldn't offer a pet package for this, not even close.

The closest I could think of is a lengthy howto. But posting such a howto on the forum would produce devastating results.

Probably best is a page on the Internet. Even at that, the page would be for people who don't mind modifying Puppy's scripts a little or a lot.

Moreover, it would have to be fairly generic because Puppy changes how it does things.

If people want to use a time server, I think the best step is to install an already made .pet package. If the package doesn't work right, then report a bug on the package.

Also, if you posted a how-to on how you solved the problem with your version, that might be good. I think you do well with English, but if you aren't comfortable with it, we also have a forum in Espanol and you can post a howto thread there very comfortably.

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot vote in polls in this forumYou cannot attach files in this forumYou can download files in this forum