Time woes - application doesn't work after year 2000

[firewall]

I have a software which contains data for various ICs. I want to make it available over a Windows network.

The problem is that the software only works when the year is set to before 2000 (Y2K bug perhaps?). Is there some way that the application is made to see the time as some date before the year 2000 while other programs keep working with the current system/server time?

Any help would be appreciated.

 

[EagleKeeper]

1) Contact the vendor that originally did the S/W

2) Check to see if the issue is the time on the host system or on the client system.

 

[bwatson283]

Timemachine?

 

[MrChad]

How are you just discovering this problem now, over 7 years later?

 

[Red Squirrel]

You could run it from a VM and set the year to like 1907 (so you can still use '07 notation) But I'd see if there is a patch.

I'm suprised some software is affected by this as most if all time stuff on a pc is based on the unix epoch. We will hvae issues in 2040ish or so though when the number of seconds since 1970 will be higher then 32 bits.

 

[firewall]

Originally posted by: MrChad
How are you just discovering this problem now, over 7 years later?

That is because there is a need for this software now after all these years... It's been quite some time since it was last needed.

 

[firewall]

Originally posted by: RedSquirrel
You could run it from a VM and set the year to like 1907 (so you can still use '07 notation) But I'd see if there is a patch.

That is a possible solution. Thanks.

I will see how it works out.