y2k problem

Is it y2k problem solved?

Is it any problem arising with 8088, 386 , 486 and pentium?

It is working normally?
Kindly explain
nagusceAsked:
Who is Participating?
 
jhanceConnect With a Mentor Commented:
There are no known Y2K issues associated with 8088, 80386, 80486, or Pentium microprocessors.
0
 
nagusceAuthor Commented:
-
0
 
nagusceAuthor Commented:
no
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
jhanceCommented:
There are no known Y2K issues associated with 8088, 80386, 80486, or Pentium microprocessors.
0
 
cumboCommented:
Y2K problems are associated with the BIOS real time clock not with the processors. Most BIOS's with a 8088. 80386 or 80486 are NOT Y2K ready. Some can be updated some cannot.

Run a good Y2K diagnostic program to find out. ontrack.com has a good one that is free.

Cumbo
0
 
vikiingCommented:
Friend Naqusce: don't forget that Y2K problem is mainly a SOFTWARE question, that relies on the way a certain date is interpreted, no matter what kind of processor make that job.

Basically, Y2K drama is the problem arised when you make the common operation that everybody did in this century: to calculate the amount of elapsed years by subtracting starting year value from current year, but only the LAST TWO DIGITS; so, 1999 - 1988 ==> 99 - 88 = 11 years.

That same process, which worked since 1900, will die in just 3 weeks, because the same guy, born in 1988, will be, in 2000, 00 - 88 = -88 years old.

There's no processor which deal directly with date entities; all date processes are done by specialized programs or specific software which decompose the date in its main fields (year-month-day) and make the job. So, it's too common a machine-instruction sequence that executes:

        mov  ax,[address with year XX]
        mov  bx,[address with year ZZ]
        sub  ax,bx
        mov  [address of result],ax

If programmer prepared the things in such a way that addresses XX and ZZ store the year in a 2-digit fashion, that program will fail because result will be a wrong value, even when the processor involved be the most powerful Cray.

On the other hand, if programmer let dates be a 4-digit expression (the whole year) then that program will run smoothly, be the processor a humble 8086, 286, 386, or whatever.
0
 
cumboCommented:
vikiing,

You are ignoring the fact that all programs derive the date/time from the system bios/real time clock. Even if the programmer uses a 4 digit year his program will fail if the bios gives a 2 digit year.

Cumbo
0
 
vikiingCommented:
I don't ignore that, Cumbo; the problem is that BIOS is not part of the processor. Nagusce is asking for problems in a 8086, 286, etc., and not as a BIOS-related program, this is, specific processor problems.

The majority of 286 machines won't support year 2000 in their clocks. However, you can type a DATE and TIME DOS commands (each time you startup the machine), and everything will run smoothly; that's because, although BIOS clock doesn't tolerate a 4-digit clock, DOS clock effectively does.

From that point of view, the 286 processor has nothing to do with date/time values, and, provided that you supply the right date/time values at startup (have you forgotten the ancient times, when all XT machines needed the date/time commands?), no process will suffer any kind of problem.
0
 
cumboCommented:
Which is what I said in my original comment....

Cumbo
0
All Courses

From novice to tech pro — start learning today.