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.
gdinseAsked:
Who is Participating?
 
emmonsConnect With a Mentor Commented:
That is the way that I read it.
The target will need to have the Y2K complient version of the OS (i.e. the update to WinFile and command.com) but that should be it. All of the calls will go through their, and life should be just ducky. Or so says Microsoft <G>

Why are you building 16 bit applications for W95?
0
 
gdinseAuthor Commented:
Edited text of question
0
 
emmonsCommented:
0
Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

 
gdinseAuthor Commented:
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.
0
 
emmonsCommented:
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.

0
 
gdinseAuthor Commented:
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.
0
 
gdinseAuthor Commented:
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.
0
 
emmonsCommented:
Gotcha. The conversion is never trivial. I was worried that you were doing new development.
Good luck.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.