asked on

Microsoft Visual C/C++ (16 bit) v1.50 and v1.52 - Y2K compliant???

Does anyone know if MSVC C/C++ v1.50 and v1.52 (16 bit) are year 2000 compliant?

I would assume yes, as the compiler/linker do not deal with dates. The only problem I see might be old BIOS calls for system date?

I have checked the Microsoft web site but found nothing??

Thanks in advance.

gdinse

ASKER

Edited text of question

emmons

Check out:

http://info.sc.cei.gov.cn/ad/topinfo/How%20the%20Year%202000%20Affects%20Microsoft%20Product%20Date%20Fields.htm

They explain the limitations and foibles of the OS etc.

emmons

http://www.microsoft.com/technet/topics/year2k/product/product.htm
also

gdinse

ASKER

I require information of the 16 bit MSVC .. but i suppose if Microsoft isn't interested then it will be difficult to obtain information elsewhere. if nothing else is forth coming then it's yours.

emmons

http://www.microsoft.com/technet/topics/year2k/product/product.htm
also

emmons

Are you using these in Win3.x or in DOS?
It seems like the problem is going to be in the OS, not the libraries themselves, right?
I would have felt better to see references to the MSRT* libraries on the MS site though, but they do talk about the limitations in both 16 bit systems. They also talk about an upgraded WinFile.exe for Win3.1.

gdinse

ASKER

So, if I understand you correctly, the compiler, linker should be ok, its just the system information BIOS calls pick up?

The OS will be Win95.

ASKER CERTIFIED SOLUTION

emmons

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

gdinse

ASKER

Originally, for compatiblility with some clients who use to run Win3.1, but now have upgraded. We're still to convert our systems so still require Y2K compliance.

Thanks for your help.

emmons

Gotcha. The conversion is never trivial. I was worried that you were doing new development.
Good luck.