Post by thread:[OT] Y2K compliance

Hi Everyone, Sorry to perpetuate the off-topic nature of the piclist. How do you answer customer's questions about year 2000 compliance? Especially when they send forms for you to sign? I know better than to sign anyone elses documents. I would rather instead provide them with my own form explaining my Y2K compliance plan. Would anyone who has created such a form care to share its contents for me to copy from? Thanks, Bob Blick

On Tue, 7 Jul 1998, Bob Blick wrote: > How do you answer customer's questions about year 2000 compliance? I guess the following points should be checked: 1. The size of the year stored (2 or 4 digits) 2. Is 2000 leap year [ it should ]. 3. What is the weekday of 1/1/2000? [ should Saturday, especially instead of Monday which is assumed as the year is thought as 1900 ] 4. How old is a man born 1/1/1999 on 1/1/2000? [ exactly one year ] And in days? [ exactly 365 days ] 5. Which day comes after 12/31/1999? [ should 1/1/2000 ] I think this is fair checklist as 1st trial. I elaborated the solution with the `cal` command of Linux. Of course, it IS Y2K-compliant! Imre

> From: Bob Blick <spam_OUTbobTakeThisOuTTED.NET> . > How do you answer customer's questions about year 2000 compliance? >I would rather instead provide them with my > own form explaining my Y2K compliance plan. > > Would anyone who has created such a form care to share its contents for > me to copy from? . For one example look at our web site http://www.bytecraft.com Walter Banks

Which variant of Unix? <G> I'm sure Linux will be fixed in time, given it's rate of change! And a lot better by then than it is now <G> Most 80x86 machines have this problem; I don't think I'll be using current-day hardware in 2037, though. (I still have my original Compaq DeskPro Model 4 {7 MHz XT}, though I've upgraded it somewhat; It's, what, 14 years old, now? I turn it on 3 times a year to play Ancient Art of War & Gato. 70 Mb of RLL drives, "oooh, aaah", nothing special now!) I'm hoping by 2020 to have a properly designed computer but not holding my breath <G> I imagine I'll not fire this machine I'm on now, as often as I fire the old XT up, in 2037! I'm not too worried... (I figure by then we'll all be taking a pill one evening & the next morning waking up with a computer grown in the spaces between our skull's bone crystals or some such. Just hope THAT machine doesn't run out of IRQs, DMA channels, or other resources <G> Mark Craig Lee wrote: > > Just going through and reading some old list messages.... > > Did you know that UNIX itself will be a BOMB in the year 2032? > > The Julian time breaks............(overflows) > > Craig > > {Original Message removed}

Craig Lee <.....craigleeKILLspam@spam@TELUSPLANET.NET> wrote: > Did you know that UNIX itself will be a BOMB in the year 2032? > The Julian time breaks............(overflows) Bzzzt! Try again. Nothing is expected to fail for this reason in 2032. The correct date is left as an exercise to the reader. Hint: it is 2^31 seconds after the start of 1970. And not all Unix variants have this problem; some of them will be fine until 2^32 seconds after the start of 1970. Others will be safe for 2^63 or 2^64 seconds. I haven't heard of anyone worrying about the Y584G problem yet. Eric All of my PIC code is Y2K compliant. Some of it keeps time, but only as a 24-hour clock with no date. :-)

Yup, it stated in the manual that the Unix source code will execute special instructions after 1999 dec30 23:59 to explode the processor, start a thermonuclear war, and eradicate 3 different alien species. Yes it overflows on really old versions, except for the fact that the bios on the machine will implode before the UNIX code. (OMG how could we let the Y2K bomb get so far) I bet $100.00 that Y2K dont do a damn thing except to banks and government cheapskates. tim. "My desing cant be Y2K compliant as the 74ls00's in it aren't!" On Tue, 28 Jul 1998, Craig Lee wrote: > Just going through and reading some old list messages.... > > > Did you know that UNIX itself will be a BOMB in the year 2032? > > The Julian time breaks............(overflows) > > Craig > > > {Original Message removed}

:-) My Cromemco Z-2H minicomputer made in 1984 stores 4 bytes for year in the date. (runs Cromix) some companies had their heads out of their butts quite a few years ago. (Except that DBASE on it doesnt!) On Tue, 28 Jul 1998, Mark Willis wrote: {Quote hidden}> Which variant of Unix? <G> > > I'm sure Linux will be fixed in time, given it's rate of change! And > a lot better by then than it is now <G> > > Most 80x86 machines have this problem; I don't think I'll be using > current-day hardware in 2037, though. (I still have my original Compaq > DeskPro Model 4 {7 MHz XT}, though I've upgraded it somewhat; It's, > what, 14 years old, now? I turn it on 3 times a year to play Ancient > Art of War & Gato. 70 Mb of RLL drives, "oooh, aaah", nothing special > now!) > > I'm hoping by 2020 to have a properly designed computer but not > holding my breath <G> I imagine I'll not fire this machine I'm on now, > as often as I fire the old XT up, in 2037! I'm not too worried... > > (I figure by then we'll all be taking a pill one evening & the next > morning waking up with a computer grown in the spaces between our > skull's bone crystals or some such. Just hope THAT machine doesn't run > out of IRQs, DMA channels, or other resources <G> > > Mark > > Craig Lee wrote: > > > > Just going through and reading some old list messages.... > > > > Did you know that UNIX itself will be a BOMB in the year 2032? > > > > The Julian time breaks............(overflows) > > > > Craig > > > > {Original Message removed}