The Date Timezone module requires you to set the site timezone name.

I am having exactly the same problem, using Drupal Core 6.3 and Windows XP.

I have set the Time Zone and saved the settings but it says that I need to set it each time I review the Status Report.

I am having the same issue. I will set the time zone to US/Central. Then, every time I check the status or run cron, it resets the time zone back to Africa/Addis.

I am using Drupal Core 6.3

I'm pretty sure that has been fixed since beta3, try the latest -dev version of the code.

It does not seem to be fixed yet. I'm still having the problem, and I just updated...

You updated to what? I don't see this in the current -dev version.

Sorry det version is 6.x-2.0-beta3

You need to get the -dev version to see the changes. The beta3 version does not have them. It never changes. The changes will then make it into the next release, but for now they are in the -dev version.

Installed the -dev version, and the problem is still there... No change...

I had the same issue so I updated to the latest dev version as suggested. Now whenever I try to set the timezone, I click save, it says my configuration has been saved yet the timezone resets to the default value. So at this point neither dev or beta 3 are working for me.

Ok, so after dev version didn't work I tried to disable it... but I can't.

under admin/build/modules I uncheck timezone and click save. The page reloads and timezone is checked. Date api cannot be disabled because timezone depends on it so the checkbox is ghosted.

-- I had to upgrade to beta3 again and then disable.

I solved this problem in my environment.

I had the Event module still enabled. After disabling it I noticed that the listings in the timezone drop down had changed. For example "EST" no longer appeared on the list. So I set it to America/NewYork and saved my changes. After that, date timezone module did not complain ;)

You cannot use the Event module with the Date API because the Event module takes over the timezone settings form so there is no way to set a timezone for the Date API. There is an issue on the Event issue queue and the Date issue queue about this, and it is noted in all the documentation and on the Date project page. So for anyone trying to use both, that is the problem and you must disable one or the other.

Automatically closed -- issue fixed for two weeks with no activity.

Is that right. The event mod doesnt seem towork without the calendar and date stuff so why would they clash? This drove me crazy for a bit. Did anyone ever figure out a work around on this?

I had it working, by only activating the Date API module, and not the Date Timezone module. In that way, Event module handles all timezone handling.

You absolutely cannot use Date API without using the Date Timezone module!!! You should not be able to turn it off, since it is a dependency.

The Event module does not use anything in Date or Calendar, it has its own methods for handling dates and drawing calendars, and it has it's own methods for handling timezones, using a timezone id and a different name for the timezone. Plus it has some timezone names that are now deprecated that the Date API doesn't use. So each must have it's own settings in the database to work right.

I originally posted that you couldn't use them together, because of this, but I have since fixed this in the -dev version. The Date Timezone module now fixes this by having you set the things that the Date API needs and then, if the Event module is enabled, it updates the things that the Event module needs so that Event will work, too.

If you are using both, go to the timezone settings page while they are both turned on and make your selections and save the changes and both modules will get updated correctly.