The Latest Versions of all Tenberry Products are Year 2000 Compliant!

Is DOS/16M Year 2000 compliant?

Yes. DOS/16M does not use dates for any processing or logic. Therefore, DOS/16M is Year 2000 compliant.

DOS/16M does pass the DOS interrupts relating to getting and setting the system dates through without processing. Since these interrupts should support dates through 2099, there is no Year 2000 problem -- unless DOS (or the DOS emulation you are using) is not Year 2000 compliant.

Will my DOS/16M program be Year 2000 compliant?

No, not automatically. Your DOS/16M program depends upon a number of different systems: DOS and the BIOS (or the simulation you are using), DOS/16M, and your program's code. It will only be Year 2000 compliant if all three are.

Yes, as far as DOS/16M is concerned.

Are earlier versions of DOS/16M Year 2000 compliant?

Probably, for the same reason version 6.01 is.

However, we have not inspected the source of earlier versions for Year 2000 compliance, and can therefore make no definitive statements about earlier versions. If you need to insure Year 2000 compliance of your DOS/16M-based application, you should upgrade to the the latest version of DOS/16M.

Is DOS/4G Year 2000 compliant?

Yes. DOS/4G does not use dates for any processing or logic. Therefore, DOS/4G is Year 2000 compliant.

DOS/4G does pass the DOS interrupts relating to getting and setting the system dates through without processing. Since these interrupts should support dates through 2099, there is no Year 2000 problem -- unless DOS (or the DOS emulation you are using) is not Year 2000 compliant.

Will my DOS/4G program be Year 2000 compliant?

No, not automatically. Your DOS/4G program depends upon a number of different systems: DOS and the BIOS (or the simulation you are using), DOS/4G, and your program's code. It will only be Year 2000 compliant if all three are.

Yes, as far as DOS/4G is concerned.

Are earlier versions of DOS/4G Year 2000 compliant?

Probably, for the same reason version 2.60 is.

However, we have not inspected the source of earlier versions for Year 2000 compliance, and can therefore make no definitive statements about earlier versions. If you need to insure Year 2000 compliance of your DOS/4G-based application, you should upgrade to the the latest version of DOS/4G.

Is DOS/4GW Year 2000 compliant?

Yes. DOS/4GW does not use dates for any processing or logic. Therefore, DOS/4GW is Year 2000 compliant.

DOS/4GW does pass the DOS interrupts relating to getting and setting the system dates through without processing. Since these interrupts should support dates through 2099, there is no Year 2000 problem -- unless DOS (or the DOS emulation you are using) is not Year 2000 compliant.

Will my DOS/4GW program be Year 2000 compliant?

No, not automatically. Your DOS/4GW program depends upon a number of different systems: DOS and the BIOS (or the simulation you are using), DOS/4GW, and your program's code. It will only be Year 2000 compliant if all three are.

Yes, as far as DOS/4GW is concerned.

Are earlier versions of DOS/4GW Year 2000 compliant?

Probably, for the same reason version 2.01 is.

However, we have not inspected the source of earlier versions for Year 2000 compliance, and can therefore make no definitive statements about earlier versions. If you need to insure Year 2000 compliance of your DOS/4GW-based application, you should upgrade to the the latest version of DOS/4GW.

Is DOS/4GW Professional Year 2000 compliant?

Yes. DOS/4GW Professional does not use dates for any processing or logic. Therefore, DOS/4GW Professional is Year 2000 compliant.

DOS/4GW Professional does pass the DOS interrupts relating to getting and setting the system dates through without processing. Since these interrupts should support dates through 2099, there is no Year 2000 problem -- unless DOS (or the DOS emulation you are using) is not Year 2000 compliant.

Will my DOS/4GW Professional program be Year 2000 compliant?

No, not automatically. Your DOS/4GW Professional program depends upon a number of different systems: DOS and the BIOS (or the simulation you are using), DOS/4GW Professional, and your program's code. It will only be Year 2000 compliant if all three are.

Yes, as far as DOS/4GW Professional is concerned.

Are earlier versions of DOS/4GW Professional Year 2000 compliant?

Probably, for the same reason version 2.01 is.

However, we have not inspected the source of earlier versions for Year 2000 compliance, and can therefore make no definitive statements about earlier versions. If you need to insure Year 2000 compliance of your DOS/4GW Professional-based application, you should upgrade to the the latest version of DOS/4GW Professional.

Is DOS/4G for Watcom Year 2000 compliant?

Yes. DOS/4G for Watcom does not use dates for any processing or logic. Therefore, DOS/4G for Watcom is Year 2000 compliant.

DOS/4G for Watcom does pass the DOS interrupts relating to getting and setting the system dates through without processing. Since these interrupts should support dates through 2099, there is no Year 2000 problem -- unless DOS (or the DOS emulation you are using) is not Year 2000 compliant.

Will my DOS/4G for Watcom program be Year 2000 compliant?

No, not automatically. Your DOS/4G for Watcom program depends upon a number of different systems: DOS and the BIOS (or the simulation you are using), DOS/4G for Watcom, and your program's code. It will only be Year 2000 compliant if all three are.

Yes, as far as DOS/4G for Watcom is concerned.

Are earlier versions of DOS/4G for Watcom Year 2000 compliant?

Probably, for the same reason version 2.01 is.

However, we have not inspected the source of earlier versions for Year 2000 compliance, and can therefore make no definitive statements about earlier versions. If you need to insure Year 2000 compliance of your DOS/4G for Watcom-based application, you should upgrade to the the latest version of DOS/4G for Watcom.