Solved

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

Posted on 1998-11-17
10
524 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
  • 6
  • 4
10 Comments
 

Author Comment

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

Expert Comment

by:emmons
ID: 1254347
0
 
LVL 4

Expert Comment

by:emmons
ID: 1254348
0
Live: Real-Time Solutions, Start Here

Receive instant 1:1 support from technology experts, using our real-time conversation and whiteboard interface. Your first 5 minutes are always free.

 

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: 1254350
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

Courses: Start Training Online With Pros, Today

Brush up on the basics or master the advanced techniques required to earn essential industry certifications, with Courses. Enroll in a course and start learning today. Training topics range from Android App Dev to the Xen Virtualization Platform.

Question has a verified solution.

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

Suggested Solutions

Title # Comments Views Activity
memory leak detection 9 80
In Notepad++ how to tell if tab files have been changed? 4 64
c++ getting the first 10 characters of a char* string 11 93
valid enum? 6 74
An Outlet in Cocoa is a persistent reference to a GUI control; it connects a property (a variable) to a control.  For example, it is common to create an Outlet for the text field GUI control and change the text that appears in this field via that Ou…
Update (December 2011): Since this article was published, the things have changed for good for Android native developers. The Sequoyah Project (http://www.eclipse.org/sequoyah/) automates most of the tasks discussed in this article. You can even fin…
The goal of this video is to provide viewers with basic examples to understand opening and reading files in the C programming language.
THe viewer will learn how to use NetBeans IDE 8.0 for Windows to perform CRUD operations on a MySql database.

776 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