The question before us, NOT will Y2K cause civilization to cease as we know it, BUT, can a computer function if it 'reads' 00, and not 2000. Cause if it can't, and I've read lots and lots of examples that it can't, then there ain't enough time, resources, expertise to fix it...

-- zaza (---@---.com), October 12, 1999

Answers

uhhhhh....are you new around here?

The answer is YES - NO !

-- Cory Hill (coryh@strategic-services.net), October 12, 1999.

Depends on what your definition of 'function' is (sorry to sound Clintonesque here).

Will they start shooting sparks and spewing smoke? No (although I *have* had a computer do that once many years ago).

Will they produce correct results? Probably not.

Can this cause computers and devices with date sensitive chips to crash? Yes.

Can crashed computers or computers producing incorrect results cause other systems (such as pipelines and refineries) to explode? Yes.

-TECH32-

-- TECH32 (TECH32@NOMAIL.COM), October 12, 1999.

I thought the answer was No - Yes? :) Actually, the answer is, it depends. :) What kind of computer are you talking about? PC, Macintosh, Mainframe, embedded chips, etc? How old are we talking about? A year, 2, 5, 10? Define "Function".

My PC that I just replaced (a 3 year old P166) would have had clock problems (the bios wasn't compatible). Did it crash? No, but the clock would never go past 12/31/99. Did it function? Yeah, I could access the Internet, play games, etc. My finances might have come up a bit funky though.

How did I fix it? I replaced it with a newer one that was compliant. Does that mean it is totally fixed? No, because there can also be issues with the software (totally seperate from the hardware issues). Some you wont be able to find until after using the software for a bit after 2000.

PS: Define "Real Programmer". I program in Visual Basic for my company, and have a bunch of applications used internally. However, some guys might say i'm not a "Real programmer" since I use Visual Basic... :)

-- James Collins (jacollins@thegrid.net), October 12, 1999.

In some cases, as when the operating system fails completely (as in locks up), the answer is no. In others, the system may seem to function normally. The problem could be that the data is slowly being corrupted...until your entire data base is unusable. This would be a horrendus problem for a major insurance company (policyholder files), pharmacy company (inventory files), refinery (process data), nuclear reactor, school (student records, including grades), etc.

Yeah, it could be (and most likely will be) a problem...which is why many of us, who are long time IT professionals, are increasing our "hurricane supplies" like mad!

-- Mad Monk (madmonk@hawaiian.net), October 13, 1999.

Wait a second here... a thread titled, "Will a REAL programmer please stand up," generates only four measly responses? And only two of which claim to actually be programmers! I'm beginning to question the credibility of the advice given out here. Without referring to their "extensive" experience with embedded chips, someone tell me why I should believe a single word on this thread. (Don't tell me that you don't care what I believe - I already know that. Tell me why you are credible.)

-- J. Cellphone (tsrwireless@memco.com), October 13, 1999.

I'm a real programmer. Almost 32 years. Assembly language expert (not my humble opinion) on IBM S/3x0 mainframe, AND x86 based PCs. Cobol, Fortran, Basic, I can't count them all. Systems and application programming. On-line, real-time and batch systems. Tech support. Operations support. Etc. etc. etc...

We're in deep sh*t.

Tick... Tock... <:00=

-- Sysman (y2kboard@yahoo.com), October 13, 1999.

PS

J. Cellphone,

I did a survey here a while ago. At least 875 man-years of programming experience on this forum. Only a couple of pollys in the crowd.

We're just tired. Tired of fighting with the eyes-closed know-it-all pollys. I know I am. <:)=

-- Sysman (y2kboard@yahoo.com), October 13, 1999.

Yes, I consider myself as a real programmer too, the reason not many replied on this thread is that the original post did not warrant a reply.

RonD

-- Ron Davis (rdavis@ozemail.com.au), October 13, 1999.

Ok, fair enough guys. I'll remember to take that into consideration when I'm reading your comments, specifically. Still, we now have a grand total of only four self-proclaimed programmers.

The other problem I'm having is I work or associate with many talented programmers (of many flavors), JCL gurus, network techs, service techs, and DB admins - with collective experience spanning a large range of platforms and applications - none of whom have expressed anywhere near the level of concern I've found on this forum. My real life experience has repeatedly come up with cautious optimism from these people; and I've asked them directly. I've been told to buy batteries, flashlights, blankets, two weeks of water, two weeks of food, extra meds, and a first aid kit. To me, this is preparation for a minor to moderate disturbance. I don't think anyone is going to be able to explain this phenomenon properly (since you don't know me and I can't verify your "authenticity"), but I feel like there is a gaping inconsistency between statements from people I trust and the prevailing attitude / frame of thought on this forum. End rant.

-- J. Cellphone (tsrwireless@memco.com), October 13, 1999.

I am a self taught programmer. I've been
programming for 9 years (Assembly, Basic,
C). Early on I realized the two digit date
problem and mitigated the problem in my own
programs. I expanded all date entries to
four digit years (not Y10K compliant) and
windowed all two digit year entries between
1950-2049 (At 2050 one must enter 4 digit years).
I also correctly identified the year 2000 as
a leap year in my algorithms.

I don't understand why so many programmers did
not understand these issues, but I do understand
what havoc these errors will create when an
incorrect date is used to figure out a span
between dates (pay checks with incorrect amounts,
inventories not replenished, maintenance schedules
disrupted).

This problem is widespread and hidden in billions
of lines of code.

"then there ain't enough time, resources, expertise
to fix it..." is correct.

-- spider (spider0@usa.net), October 13, 1999.