Das Jahr 2000 Problem - Auszug aus dem Risk-Forum (comp.risks)

Die hier angebotenen Informationen haben wir mit freundlicher Genehmigung aus den Beiträgen im Risk-Forum (comp.risks) zusammengestellt. Vorerst alles in englischer Sprache. Das komplette Forum, welches nicht nur Jahr-2000-Probleme thematisiert, kann unter der Adresse catless.ncl.ac.uk betrachtet werden.
Bitte beachten Sie die Hinweise am Ende dieser Seite.

Volume 20 Issue 71 (Friday 31 December 1999)

• Pentagon Y2K preparations (Dave Stringer-Calvert)
• Two possibly unaddressed Y2K problems (Brett Glass via Dave Farber)
• Low-tech Y2K failure (Earl Truss)
• The risks of last minute Y2K patches (Matt Blaze)
• Re: Y2K fear vs. Common sense (Scott Nicol, Eric Roesinger)

Volume 20 Issue 70 (Sunday 19 December 1999)

• Y2K fear vs. Common sense (identity withheld)

Volume 20 Issue 69 (Thursday 16 December 1999)

• Y2K-related viruses (PGN)
• Power-out in Y2K test (Debora Weber-Wulff)
• Risks of Y2K overreaction (Steven Huang)

Volume 20 Issue 68 (14. Dezember 1999)

• Oh, no! Y2K virus competitions

Volume 20 Issue 67 (7. Dezember 1999)

• Worm.Mypic: Will Y2K provide cover for worm/viruses?
• Y2K compliance
• Re: Irish telephone network outage brings Y2K fears

Volume 20 Issue 66 (1. Dezember 1999)

• Irish telephone network outage brings Y2K fears
• Firestation fire blamed on Y2K computer fix

Volume 20 Issue 65 (21. November 1999)

• Re: Y2K creates "horseless carriages"
• Microsoft Y2K liability
• Risks of Office 2000

Volume 20 Issue 64 (4. November 1999)

• Re: Y2K creates "horseless carriages"

Volume 20 Issue 63 (16. Oktober 1999)

• Y2K creates "horseless carriages"
• Millennium Bugs?

Volume 20 Issue 62 (12. Oktober 1999)

• GPS rollover *did* cause DoD Problems
• NT Stung Again by Y2K Bug
• Iraq decides to wait and see on Y2K oil disruption
• FBI warns some Y2K fixes may be suspect

Volume 20 Issue 61 (1. Oktober 1999)

• FBI warns some Y2K fixes may be suspect

Volume 20 Issue 60 (27. September 1999)

• 9/9/99?

Volume 20 Issue 59 (23. September 1999)

• Sweet Y2K angle
• 1 Oct 1999 as a Y2K problem date?

Volume 20 Issue 58 (17. September 1999)

• Indonesian Year 2000 plans
• Yet another date-related problem

Volume 20 Issue 57 (15. September 1999)

• If it quacks on 1/1/2000, it must be a Y2K duck
• Food expiry date misreading risks

Volume 20 Issue 56 (3. September 1999)

• Local company stung by Y2K bug

Volume 20 Issue 55 (27. August 1999)

• Tokyo traffic chaos in GPS date rollover
• GPS rollover hits yacht
• 9/9/99
• Y2K in China

Volume 20 Issue 54 (15. August 1999)

• Y2K upgrade went 'horribly wrong', admits utility giant

Volume 20 Issue 46 (19. Juni 1999)

• Y2K test sends sewage flowing in Los Angeles

Volume 20 Issue 45 (17. Juni 1999)

• Re: GPS and collision risks

Volume 20 Issue 44 (15. Juni 1999)

• GPS kills 8 in air

Volume 20 Issue 43 (4. Juni 1999)

• Y2K Test Knocks Out Fiji's Telecommunications

Volume 20 Issue 42 (25. Mai 1999)

• Y2K testing on weather images

Volume 20 Issue 41 (23. Mai 1999)

• Y1.K9

Volume 20 Issue 40 (18. Mai 1999)

• Nuclear plant Y2K: High risk-readiness or high-risk readiness?

Volume 20 Issue 35 (30. April 1999)

• REVIEW: "The Y2K Survival Guide", Bruce F. Webster

Volume 20 Issue 33 (24. April 1999)

• REVIEW: "Y2K Risk Management", Goldberg/Davis/Pegalis

Volume 20 Issue 32 (20. April 1999)

• Calendar problem with old Calvin and Hobbes comics strips

Volume 20 Issue 31 (18. April 1999)

• Outlook '98 not Y4.501K Compatible
• Leap year 2000 and C

Volume 20 Issue 30 (16. April 1999)

• Y10K: not just for April Fools
• GPS setup error affects dredging in California

Volume 20 Issue 29 (2. April 1999)

• Re: Apple Y2K

Volume 20 Issue 28 (1. April 1999)

• Professor wants Y2K jokes banned on the Net
• Y2K: Help for the Weary Programmer
• Y2K alert!

Volume 20 Issue 27 (1. April 1999)

• RFC2550 - Y10K and Beyond

Volume 20 Issue 26 (1. April 1999)

• The Y9Z Problem
• Yet another Y2K debacle
• Vatican announces all computer systems ready for new millennium
• Y10K opportunity

Volume 20 Issue 25 (20. März 1999)

• Y2K is the least of it
• Sri Lankan Banks to close on 31 Dec 1999 for Y2K tests
• Banks warn public about Y2K scam

Volume 20 Issue 24 (11. März 1999)

• Risks of testing a nuclear power plant for Y2K compliance
• Outlook Express Date: parsing
• Bringing Y2K fears to a new high -- or low

Volume 20 Issue 23 (1. März 1999)

• Limiting liability for Y2K breakdowns
• CIA predicts serious Y2K problems around the globe
• Y2K Test Fine Test Data Causes Problem
• Re: Store Baelt Bridge not Y2K safe

Volume 20 Issue 22

• Store Baelt Bridge not Y2K safe
• Re: Computer fraud as another kind of Y2K risk?

Volume 20 Issue 20

• State of the states in Y2K readiness

Volume 20 Issue 18

• Y2K update turns city into deadbeat

Volume 20 Issue 16

• Y2K in Swiss hospitals
• 1 Apr 2001 flaw in Windows
• Quicken 1999 bug
• A good Y2K bug
• Utilities and Y2K: not to worry
• Y2K testing tools
• REVIEW: "Year 2000 in a Nutshell", Norman Shakespeare

Volume 20 Issue 15

• UAL clock wraparound
• Y2K hits Singapore and Swedish taxi meters
• The Windows April Fools 2001 Bug (from Richard Smith)

Volume 20 Issue 14

• Swedish Giroguide also hit by 99
• Y1999: Risk of re-using data fields for error signaling
• 99-Year retrospective health insurance - or Y2K problem

Volume 20 Issue 13

• British Government admits Y2K missile problem
• 2,000 Texans get false overdraft notes in Y2K test
• Y2K expansion
• Unexpected date behavior in Windows 95
• Microsoft Trojan Horse

Volume 20 Issue 12

• San Francisco power outage and Y2K (RISKS-20.11)

Volume 20 Issue 11

• San Francisco power outage delays this issue (PGN)
• Y2K panic could be as disruptive as computer problems

Volume 20 Issue 10

• DoD falsified Y2K data but has "good feeling" about future
• Y2K inflation risk

Volume 20 Issue 09

• 100-year-old woman "too old to vote"

Volume 20 Issue 03

• Some good Y2K news: whisky will be on tap for Hogmanay 1999
• Military preparations to mobilize for Y2K
• Void where prohibited by date

Volume 20 Issue 02

• Risks of Upgrades: Florida fingerprint system
• Y2K police planning
• Re: Y2K risk in Netscape cookies (Seymour, RISKS-20.01)

Volume 20 Issue 01

• Calling All Traffic Lights in Dublin!
• Y2K "fix" causes Dublin traffic jams
• Y2K risk in Netscape cookies

Volume 19 Issue 97

• REVIEW: "Computer Crisis 2000", W. Michael Fletcher

Volume 19 Issue 91

• Win98 Yx problem, not Y2K?
• REVIEW: "Time Bomb 2000", Edward Yourdon/Jennifer Yourdon

Volume 19 Issue 90

• New Jersey Y2K car inspection stickers
• Bug-free millennium for Railtrack
• White House Calm, DoD Nervous About Y2K

Volume 19 Issue 89

• Y2K OK on Wall Street
• No Y2K insurance for household electrical items
• Re: Y2K contingency plans (RISKS-19.88)

Volume 19 Issue 88

• Re: Y2K contingency plans needed (Frankston, RISKS-19.85)
• Y2K dig-gerel

Volume 19 Issue 85

• Y2K as a necessary event: Contingency plans needed

Volume 19 Issue 84

• Y2K problem worries CIA
• Galaxy IV, 600 days and Y2K
• No manual switching for railroads; result, famine
• REVIEW: "The Year 2000 Software Problem", Capers Jones

Volume 19 Issue 83

• Shuttle imaging Y2K problem? (O'Leary via Wood, RISKS-19.81)

Volume 19 Issue 82

• World shipping full-speed ahead to beat Y2K torpedo
• Will we have power on Jan. 1, 2000?
• Re: 15th century time machine and Y2K (RISKS-19.79,81)

Volume 19 Issue 81

• Shuttle imaging Y2K problem?
• Re: 15th century time machine and y2k (RISKS-19.79)

Volume 19 Issue 79

• Y2K financial risks

Volume 19 Issue 78

• Senate talks martial law and Y2K; Indian nuke-hackers
• Corporate insurance excludes Y2K

Volume 19 Issue 77

• Millions of small firms at Y2K risk

Volume 19 Issue 76

• GPS correction (Re: RISKS-19.75)

Volume 19 Issue 74

• Two-digit years, Swedish Y2K woes
• More on GAO Report on Y2K problem
• Y2K: now the year 2021

Volume 19 Issue 73

• Microsoft using Y2k to force sales? (Re: Stalzer, RISKS-19.69)
• More on limited-number risks: GPS, D10K

Volume 19 Issue 72

• Glitch delays 85,000 transactions
• Y2K bug in IE4?

Volume 19 Issue 71

• Y2K Testing Bugs
• Y2K bug and public health concerns
• Re: Y2K on the road (McLain, RISKS-19.69)

Volume 19 Issue 70

• Re: Worried about Y2K? Now there's D10K!
• Re: 1/3 of Microsoft apps Y2K compliant (Stalzer, RISKS-19.69)

Volume 19 Issue 69

• Euro changeover tougher than Y2K?
• Re: Only 1/3 of popular Microsoft apps are Y2K compliant (R-19.68)
• Re: Only 1/3 of popular Microsoft apps are Y2K compliant (R-19.68)
• Y2K on the road
• Re: Y2K and the eagle talon (RISKS-19.68)

Volume 19 Issue 68

• IRS to spend $1 billion to fix Y2K problems
• FC: Only 1/3 of popular Microsoft apps are Y2K compliant
• Y2K and the eagle talon

Volume 19 Issue 67

• 'Inverse Y2K' ?

Volume 19 Issue 65

• Y2K in China

Volume 19 Issue 64

• Funding for a new software paradigm
• The Computer Anti-Defamation Law
• Y2K: British Government moves to save civilisation as we know it
• Y2K and The Aviation Industry
• Worried about Y2K? Now there's D10K!
• Microsoft EXCEL date error

Volume 19 Issue 62

• Re: Year 2100 compliance? (Shimomura, RISKS-19.60)

Volume 19 Issue 61

• Y2K Problem Hits Graveyards
• Re: Year 2100 compliance? (Shimomura, RISKS-19.60)

Volume 19 Issue 60

• CyberAttack on the Pentagon
• A little accidental porn-in-the-morn

Volume 19 Issue 59

• California legislation proposed to limit Y2K liability

Volume 19 Issue 58

• Y2K bug at major bank?

Volume 19 Issue 57

• Y2K correction at IRS threatens 1,000 taxpayers
• Y2K bug may lead to lawsuits
• Y2K affects miniature enthusiasts

Volume 19 Issue 56

• PDP-11 Y2K leap-year-day bug
• Bad advice on Y2K

Volume 19 Issue 55

• A thought on backup and recovery after Y2K

Volume 19 Issue 54

• British Prisoners to Fix Y2K Problem

Volume 19 Issue 48

• Date-based random numbers and Y2K
• Re: Y2K and canned-goods expiration dates (Pereira, Risks-19.47)

Volume 19 Issue 47

• Y2K and canned-goods expiration dates
• Ottawa firm registers "Y2K" as trademark

Volume 19 Issue 46

• First Y2K spam

Volume 19 Issue 40

• C's data types; was: Re: Y2K and C (Sapovits, RISKS-19.38)

Volume 19 Issue 38

• Java Date Problems (Ryan, RISKS-19.37)
• Re: Y2K and C (Rosenthal, RISKS-19.37)

Volume 19 Issue 37

• Re: Tcl 8.0 Y2K Risk (Anderson-Lee, RISKS-19.36)
• Re: Tcl 8.0 Y2K Risk (Wood, RISKS-19.36)
• Re: Y2K and C (RISKS-19.36)

Volume 19 Issue 36

• Re: Tcl 8.0 Y2K Risk
• Re: Tcl 8.0 Y2K Risk (Miller, RISKS-19.36)
• Re: Tcl 8.0 Y2K Risk (Wood, RISKS-19.35)

Volume 19 Issue 35

• Tcl 8.0 Y2K Risk

Volume 19 Issue 32

• Can Y2K problems be cured by executive fiat?

Volume 19 Issue 29

• Y2K lawsuits begin

Volume 19 Issue 27

• Re: Y2K: a different solution (Driss, RISKS-19.26)
• Re: Y2K: a different solution (Driss, RISKS-19.26)
• CfP: Y2K in Health Informatics Journal

Volume 19 Issue 26

• Y2K: a different solution

Volume 19 Issue 25

• Medical computer crashes

Volume 19 Issue 19

• Oklahoma bombing trial transcripts

Volume 19 Issue 18

• DEC's OpenVMS has Y2K problem on 19 May 97: UNIX compatibility
• Re: Clock synchronization and relativity (Klossner, RISKS-19.17)

Volume 19 Issue 15

• Re: Year 2069 problem (Shostack, RISKS-19.13)

Volume 19 Issue 14

• Y2K fixed? But what about the month?

Volume 19 Issue 10

• Y2K and PARSLEY: Upgrade woes

Volume 19 Issue 08

• Y2K scenarios: a call for a vote

Volume 19 Issue 07

• UK and Y2K: $50 billion
• UK MoD and Y2K: 100 million pounds to reboot missiles
• On the naming of names (was Re: Y2K, (Rosenthal, RISKS-18.95)

Volume 19 Issue 06

• Re: Y2K: revenge of originality (Rosenthal, RISKS-18.95)

Volume 19 Issue 03

• Another Y2K Problem for Banks

Volume 19 Issue 01

• French computer systems found to be immune to Y2K problems
• The Year 2100 Problem: a simple solution

Volume 18 Issue 96

• Printing with different resolutions in MS Word 7.0
• Re: More Y2K Cost Estimations (Schroeppel, RISKS-18.95)
• Re: More Y2K Cost Estimations (RISKS-18.94,95)
• Re: Risks Associated with the Year 2000 Problem
• Y2K: the revenge of originality / reserved words in Cobol
• Re: Retiring hardware after Y2K
• Y2K risks and Cobol
• The unique risks related to the Year 2000

Volume 18 Issue 95

• re: Y2K: revenge of originality (RISKS-18.90,92)
• Y2k costs

Volume 18 Issue 94

• UK Banks clearing system salary payment problems
• Catastrophic Y2K risk
• Re: Splendour of the Seas not so Splendid (Kabay, RISKS-18.93)

Volume 18 Issue 93

• Splendour of the Seas not so Splendid
• The Year 2000 Problem -- a new principle for Y2K tools (RISKS-18.53)
• Retiring hardware after Y2K

Volume 18 Issue 92

• Re: Y2K: the revenge of originality

Volume 18 Issue 91

• Experiences with a Year-2000 credit card
• Re: Y2K: the revenge of originality (Vaneynde, RISKS-18.90)

Volume 18 Issue 90

• Keith Rhodes: Y2K duns contractor for 97-year delinquency
• Y2K: the revenge of originality
• Y2K & UNIX & Netscape, the end is HERE
• Y2K "problem" in virus?

Volume 18 Issue 88

• Re: 12/99 problem
• Re: 12/99 problem

Volume 18 Issue 83

• Y2K "problem" in virus?

Volume 18 Issue 82

• Re: Y2K? Y1990 strikes again!

Volume 18 Issue 79

• Re: Macintoshes and Y2K (Wood, RISKS-18.78)
• Re: Macintoshes and Y2K (Wood, RISKS-18.78)
• Y2K on non-Unix/Microsoft systems (Wood, RISKS-18.78)

Volume 18 Issue 78

• Macintoshes and Y2K

Volume 18 Issue 77

• Re: More Y2K humor: Split the difference (Brader, RISKS-18.76)

Volume 18 Issue 76

• More Y2K humor: Split the difference

Volume 18 Issue 75

• Y2K problems? What about 1997 problems for Coast Guard?
• British Telecom plan for Y2K noncompliance fines
• Re: VISA fines banks with Y2K problems (Wood, RISKS-18.73)

Volume 18 Issue 74

• VISA fines banks with Y2K problems
• Y2K: Blessing in Disguise
• April 1 considered harmful

Volume 18 Issue 63

• Y2K *Guardian* article on retroactive liability

Volume 18 Issue 62

• Effects of the next cycle of solar interference
• The current score is: Y2K 1, Visa 0

Volume 18 Issue 53

• Announcement: Year-2000 Software Crisis Conference

Volume 18 Issue 42

• Y2K - Yet another risk

Volume 18 Issue 38

• Year 2000 Bites the Budget

Volume 18 Issue 29

• Y2K hits divorcing couples in the UK

Volume 18 Issue 06

• 888 Risks

Volume 17 Issue 90

• How I lost my Y2K innocence

Volume 17 Issue 89

• Re: bleep-year (Mulligan, RISKS-17.88)

Hinweise