Solved

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

Posted on 1998-11-17
10
529 Views
Last Modified: 2013-12-14
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.
0
Comment
Question by:gdinse
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 6
  • 4
10 Comments
 

Author Comment

by:gdinse
ID: 1254346
Edited text of question
0
 
LVL 4

Expert Comment

by:emmons
ID: 1254347
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:gdinse
ID: 1254349
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
 
LVL 4

Expert Comment

by:emmons
ID: 1254351
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
 

Author Comment

by:gdinse
ID: 1254352
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
 
LVL 4

Accepted Solution

by:
emmons earned 100 total points
ID: 1254353
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
 

Author Comment

by:gdinse
ID: 1254354
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
 
LVL 4

Expert Comment

by:emmons
ID: 1254355
Gotcha. The conversion is never trivial. I was worried that you were doing new development.
Good luck.
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Preface I don't like visual development tools that are supposed to write a program for me. Even if it is Xcode and I can use Interface Builder. Yes, it is a perfect tool and has helped me a lot, mainly, in the beginning, when my programs were small…
This is a short and sweet, but (hopefully) to the point article. There seems to be some fundamental misunderstanding about the function prototype for the "main" function in C and C++, more specifically what type this function should return. I see so…
The goal of this video is to provide viewers with basic examples to understand and use conditional statements in the C programming language.
The goal of this video is to provide viewers with basic examples to understand and use switch statements in the C programming language.

705 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question