seconds function giving wrong time

[Jim Ault]

This script works as expected on   MacOSX 10.5.8    Rev 4.0.0 Build 950

get  the internet date
convert it to seconds
put the seconds - it into test3

put the seconds into test
convert test to dateItems
put the internet date into test2
convert test2 to dateItems
put test & return & test2 & return & test3
---------------------
2010,11,3,0,56,12,4
2010,11,3,0,56,12,4
0
-------------------
... when run 56 minutes after midnight PDT, Nov 3rd


Could be parallels + Win 7 + MacOSX and time clock sharing.



On Nov 2, 2010, at 10:55 PM, David Beck wrote:

>
> I do not remember this ever happening before. Something very strange  
> seems to be going on here. I'm hoping somebody can shed some light  
> on what it is. After typing in these commands in the message box:
>
> put the seconds into test
> convert test to dateItems
> put the internet date into test2
> convert test2 to dateItems
> put test & return & test2
>
> I get the following result:
>
> 2010,11,2,20,23,46,3
> 2010,11,2,22,48,44,3
>
> The second result matches the system date correctly (Windows 7  
> running on Parellels). The first result is 2 hours and 25 minutes  
> behind. Does anybody have any idea what is going on here?
>
> Thanks.
>
> David Beck

Jim Ault
Las Vegas