Jump to content











Photo
- - - - -

Time zone and locality - Win7PE


  • Please log in to reply
60 replies to this topic

#51 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 15 June 2012 - 06:09 AM

For some reason I can edit my post above.


I'm finding that if I change the time and date in the runtime, then it's then changed in the BIOS. This is correct behaviour yeah?



I think I've got a work-a-round.


I removed the "LocalizedInfoMore.script" and used Chris R's version 001 script called "Retrieve HostOS information" with the CheckBox "UNTICKED".

And now as long as the BIOS time is correct, it's correct in WinPE.

Edited by Boot_Monkey, 15 June 2012 - 06:22 AM.


#52 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 784 posts
  •  
    France

Posted 15 June 2012 - 08:02 AM

I've downloaded some scripts from this thread but now not sure if they have already been intregrated into Win7PE_SE or not..


The latest scripts are on the server http://w7pese.cwcodes.net/ without any additional download from this topic.

I'm finding that if I change the time and date in the runtime, then it's then changed in the BIOS. This is correct behaviour yeah?


Yes, this is normal, Your PE as your host system changes the CMOS clock.

Locale, TimeZone are correct, but the time is out by 18Hrs................

I removed the "LocalizedInfoMore.script" and used Chris R's version 001 script called "Retrieve HostOS information" with the CheckBox "UNTICKED".

And now as long as the BIOS time is correct, it's correct in WinPE.


Yes that's it :)
I guess you use an Enu Win 7 source, at least not an en-AU dvd and by default the timezone is the one in your source.

To change the time zone information (UTC), indeed, use the HostOS Import Manager script (currently version 004) to retrieve these informations from your Hostos :thumbsup:.
For information, the latest version of the locale script (on server), allows in any case to keep the Bios Time.
You do not need to disable the LocalizedInfoMore script ;)

:cheers:

#53 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 16 June 2012 - 12:06 AM

@Chris R,

Thanks for the info you've provided. I think you've done a fantastic job with your end of the scripts.

My problem is, that If I use the stuff out of the box, it doesn't suit me due to the source zone/time issue.

I believe and this is only my opinion, that we shouldn't be taking the zone information from the source, as this this is what has caused me so much pain, and I'll explain here.

If I understand correctly..................

The mandatory script for "Retrieve More localized Info" takes the zone from the source "UTC -8:00 Pacific Time" and takes the current time on your system and then assumes it is *your* current time at "UTC -8:00 Pacific Time". Let's say 12AM 15/06/2012
Then the script processes your zone "UTC +10:00 Sydney, Canberra & Melbourne"

So, when it comes to runtime, your current time and date will be ("UTC -8:00 Pacific Time" 12AM 15/06/2012 + Your Timezone offset). Therefore your're doomed and end up with a 18+ Hour jump ahead. What ever machine you run it on will be 18+ hours out. eg: 6PM 15//06/2012

At the moment I'm forced to remove the "Retrieve More localized Info" script and make sure I never set the Timezone in the build. This produces the correct time and date.

Taking it from the source disc destroys all hope of ever having the correct settings.

I just don't understand why the script would do this. At the very least, have something in the interface that says...

"Dont' take timezone from Source" and have a drop-down box with the timezones listed.

To change the time zone information (UTC), indeed, use the HostOS Import Manager script (currently version 004) to retrieve these informations from your Hostos :thumbsup:.
For information, the latest version of the locale script (on server), allows in any case to keep the Bios Time.
You do not need to disable the LocalizedInfoMore script ;)


Looks like to do need to so those things, because I couldn't get it to behave unless I did remove it.

What are your thoughts on this?

Oh and thanks again.

Edited by Boot_Monkey, 16 June 2012 - 12:13 AM.


#54 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 19 June 2012 - 08:15 AM

Is my take on this issue correct?

#55 pscEx

pscEx

    Platinum Member

  • Team Reboot
  • 12707 posts
  • Location:Korschenbroich, Germany
  • Interests:What somebody else cannot do.
  •  
    European Union

Posted 19 June 2012 - 06:28 PM

Have a look here: http://reboot.pro/17086/#entry156547

Peter

#56 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 784 posts
  •  
    France

Posted 19 June 2012 - 09:13 PM

Is my take on this issue correct?


Sorry for the late response, I am currently busy on other things (real life) ;)

I know that currently the solution for the localization is not the easiest.
This is owed to the historical.

The local parameters are defined and save in the project in Main Configuration with
Auto,"Belgian French",French,German,Greek,Hebrew,Hungarian,Italian,Portuguese,Russian,Spanish,Swedish,Turkish,"UK English"

The location is then treated in the local script (called from the 1 - Copy Files script).
With parameters for Locale (NLS, fonts), International Format, keyboards and TimeZone.

This locale script was updated over time by various contributors :good: to offer more language.
and the Auto setting allows, him to retrieve automatically the location information from the source CD.

The latest version (v27) on w7pese server was recently updated (in May) to recover the CMOS clock in all cases B).

#
The "Retrieve More Localized Info" script Provides detailed Localization informations of Source and HostOS :)
These are only additional information interresting for support and to be used by others scripts (so no need to remove it).

#
As the setup for localization was not complete and sufficient, it was added a new script to retrieve information from the host OS (Locale, International Format, keyboards and TimeZone) :thumbsup:
In your case, I believe that leaving the default configuration, this last script should satisfy your needs.

#
The idea, then, is to have the choice of location in only one place "Main configuration" with the choices for Host OS, Auto (or source CD), and other localizations (perhaps Host OS by default).
And this for Locale and International Format, keyboards and TimeZone (keeping in all cases the time of Bios).

I have all the informations (I believe) and some stuff in preparation, I have to reorganize all this to make it easier for all.
but this requires timeeee.

:cheers:

#57 paraglider

paraglider

    Gold Member

  • .script developer
  • 1729 posts
  • Location:NC,USA
  •  
    United States

Posted 20 June 2012 - 04:08 AM

There is also the case to consider where there is no host os - PE could be run on a totally new machine. Think an option to prompt for timezone offset / country during startup is also needed.

#58 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 20 June 2012 - 06:00 AM

The idea, then, is to have the choice of location in only one place "Main configuration" with the choices for Host OS, Auto (or source CD), and other localizations (perhaps Host OS by default).
And this for Locale and International Format, keyboards and TimeZone (keeping in all cases the time of Bios).

I have all the informations (I believe) and some stuff in preparation, I have to reorganize all this to make it easier for all.
but this requires timeeee.

:cheers:


Thank you Chris R.

Great work. Just what I wanted to hear. You make sure you look after your personal affairs. I have a work-a-round that works, until you get time to make the above changes.


AWESOME !!

Edited by Boot_Monkey, 20 June 2012 - 06:01 AM.


#59 ChrisR

ChrisR

    Silver Member

  • .script developer
  • 784 posts
  •  
    France

Posted 20 June 2012 - 05:25 PM

There is also the case to consider where there is no host os - PE could be run on a totally new machine. Think an option to prompt for timezone offset / country during startup is also needed.

What I meant by Hostos is to Import HostOS setting when building, not at startup ;)
I think it is better, if possible, to avoid questions at startup and a shortcut already exist for Regional and Language Settings or Date/Time Properties.
Also, without the need to run "rundll32.exe shell32.dll,Control_RunDLL intl.cpl" or " rundll32.exe shell32.dll,Control_RunDLL timedate.cpl" or others, before shell.

:cheers:

#60 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 21 June 2012 - 11:48 PM

In the mean time, can I hack my source disk so it looks like it comes from Australia?

Or even hard code the code line that determines that variable? Come 5pm my time, the Disc turns into a pumpkin because it's 12 midnight in Pacific Time

Edited by Boot_Monkey, 22 June 2012 - 12:21 AM.


#61 Guest_Boot_Monkey_*

Guest_Boot_Monkey_*
  • Guests

Posted 28 June 2012 - 06:28 AM

Bump




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users