Thanks for the detailed info and the pointer to the list of Y2K tests.
We'll probably upgrade the system that LV 3.1 is on to Win98 and upgrading
LV to the latest version is also an option.
Are there any gotchas in trying to run a LV 3.1 app on LV 5.1?
The app is pretty simple - data logging only, no control functions.
Greg McKaskle wrote in message
news:38054343.FCE98D7B@austin.rr.com...
> > We've got an old Labview 3.1 system that we use infrequently to log
> > experimental data. The NI web site indicates that Labview 3.X and below
> > "Will Not Be Tested" for Y2K compliance.
> >
> > Does anybody know what sort of problems we may have next year when we
try to
> > run our application?
>
> LV3.1 really doesn't do much with time formatting or
> other routines that might cause problems. On the
> other hand, it was compiled and linked to libraries
> about five years ago. I don't believe there was any
> Y2K information for the versions of the compiler and
> libraries that it was built with.
>
> The OS you are running on will also have a big impact.
> Win3.1 is far from Y2K compliant, and older revs of
> other OSes have some problems as well. I believe that
> the NI Y2K site lists the tests that were used to
> determine correct behavior. If you would like to
> test your OS/LV combination, then follow the steps
> on the web site.
>
> Hopefully, you will not have any problems with the
> product, but if you ever need to reinstall it that
> may be troublesome too since it used installers
> from five years ago, and installers do creation and
> modification date tests along with version checks.
> Again, the installers were licensed off the shelf,
> but I don't believe they are Y2K friendly.
>
> Before someone jumps on my case, these tests were
> done for lots of versions and combinations of LV.
> We decided that it wasn't worth it to go all the
> way back to LV1 on Fat Macs or other antique versions
> of LV. We made our test recipe available on the
> web site in case someone needs it.
>
> Greg McKaskle