- This topic is empty.
-
AuthorPosts
-
November 23, 2007 at 2:44 pm #762
I’ve been exploring this issue with a Wyse representative over the last week but have not really gotten a satisfactory answer. I’m wondering if anyone else has experienced this and if they found a solution for it.
I have several V10L’s with the 5.3.0_09.01 version of WTOS. I have SignOn=yes and a few user.ini files that designate privilege levels. In my wnos.ini file I have a line that designates when Daylight Savings Time starts and ends.
TimeZone=’GMT – 07:00′ ManualOverride=no Daylight=yes Start=030207 End=110107
TimeZoneName=”Mountain Standard Time” DayLightName=”Mountain Daylight Time”
This configuration works out great and I have no problems with it on the 5.3 version of the software. We just recently bought a new V10L and it has WTOS version 6.0.0_14 on it. When I boot it up and look and the DST settings it fills all the fields except the day. Just out of curiosity I changed the start and end dates toStart=030206 End=110106
This will fill the day field with Sat as it should, and in fact 01-06 at the end of the number will fill in the day field with the corresponding day. It only goes blank when 07 is entered (which is of course the only one we really need).
After bringing this to the attention of Wyse and working with support for a few days we discovered that if SignOn=no and the user.ini is not loaded with the wnos.ini it will fill the day field correctly. My user.ini only contains a privilege level and the info for the RDP connection
PRIVILEGE=LowCONNECT=RDP
Host=ourhost.com
Description=”The host our clients connect to”
Colors=256
Icon=default
Fullscreen=yes
Experience=0
LowBand=yes
Resolution=1024×768
Autoconnect=1
LocalCopy=noDeskColor=”0 128 255″
I’ve tried it with the privilege level set to high or deleting that line completely but it still leaves the day field blank. It’s like the mere fact that it loads a user.ini causes it to happen.
I reset to factory defaults in between each time I change my ini files to ensure no local settings are interfering.
Thanks again for all the help I’ve received from this site. You guys rock!
November 27, 2007 at 1:59 pm #10882That’s a good one alright! It looks like you have tested the issue well so I am not sure what I can offer here.
What happens if you place the timezone= in the user.ini?
I will test this in my lab and see if I can recreate in the next few days. In the mean time can you load the 5.3x firmware for the V10L again until its solved. I would also continue with Wyse support as in may need a bug fix in the firmware,
Cheers,
-TT -
AuthorPosts
- You must be logged in to reply to this topic.