Presentation by:	Robert Proia
Representing:	MICROSOFT CANADA

Written by Bob Rife Robert Proia, a Microsoft Canada senior technology specialist (MS-speak for a certified Systems engineer - a real go-to guy) used a softly modulated voice to SHOUT a Y2K message to the April club meeting. You could have heard a pin hit the carpet during the riveting presentation. The crowd erupted in applause as he concluded the demonstration and then eagerly pursued him in the Q and A sessions (both public and private) that followed. The MS top gun fielded queries skillfully and then sat through the rest of the meeting to do more Q and A as the hall emptied. I was impressed - and a bit concerned. Why concerned? Well, for example: There's much more to Y2K than the millennium bug. What about Sept. 9 this year (9,9,99) - those numbers act as a trigger in some computer code. Then there's a leap year factor - some PCs will also calculate 2001 and 2002 as leap years. The presentation covered a lot of ground: · What is the Year 2000 problem? · Why do we have this problem? · What are some potential consequences? · What is Microsoft's strategy? He reviewed those points and 16 more - (all are also listed and answered on the Microsoft FAQ web page). For members who missed the meeting, or others who didn't write them down, the sites are Canada: www.microsoft.com/canada/year2k and US: www.microsoft.com/year2OOO/ Proia (Please call me Bob) stressed one thing again and again - "Even what I'm saying here tonight may be outdated - check the Y2K site frequently - nothing is forever - check and then check again - software and hardware bugs can show up any time." It sounded like the anti-virus war: Check for the newest virus definitions, Stay Updated! The realization that almost all software (not merely operating Systems) may be affected and PERHAPS not supported started everyone in the audience thinking. One chap even wondered if Win3.1 was, with the misery of the millennium, as good as dead? Bob toe-danced with that one, (answer enough - be wary). He said there is a patch that fixes some, but not all of the Win 3.1 Y2K issues. "People should understand that the issues are not critical and won't halt Win 3.1 operation. The message is, if you are still receiving value from Win 3.1, and you have reviewed the minor issues that Microsoft has published on the Y2K site then there should be no reason why you cannot continue to use it." He pointed out that, of course, this refers only to Win 3.1 itself. Other applications used on that platform must each be treated individually for Y2K readiness. Which means going to the software vendors for any updates or patches. (Microsoft doesn't do other companies work - who could?). He had a news scoop - Microsoft will shortly post a Win95-Y2K software patch. Don Jones, Microsoft's year 2000 product manager in Redmond Wash., says the patch would hit the firm's web site the week of April 19. And it would also be part of the Year 2000 Resource CD (another goodie Bob told about - it's free via the web site). Jones recommends that Windows 95 users upgrade to the Internet Explorer 4.01 Service Pack 1 or greater (IE5?), including any applicable software updates. The Win95-Y2K update patch can be used on all versions of that 0/S including Gold, OSR1, 2, 2.1 and 2.5. The information I have states that it resolves issues such as: · Winfile.exe: Windows File Manager currently does not display or sort dates beyond year 2000 correctly. · Command.com: the DATE command currently does not correctly handle two-digit dates from 00-79. Entering two-digit dates within this range returns the error "invalid date" · Timedate.cpl when the date is set to February 29, the applet Will display the 29th day on years other than leap years when using the tumblers to scroll the year ahead or back; · Comctl32.dll: when Regional Settings from Control Panel is set to use two digits for years, the Date/Time Picker function may not return the proper date. To ensure proper handling of dates, set Regional Settings to four-digit date handling. Y2K also affects Windows 98 - but the solutions again are available at the web site. It's the same with NT and its variants, including the Windows/NT merge now called Windows 2000 (don't confuse that with Office 2000, the new suite of Microsoft office software). So, the best thing to do is read the Microsoft compliance statement (available on the web site). And consider your options! Proia offered no easy answers there aren't any. There's no quick fix - you can't do it once and forget it. His demo was made via a laptop loaded with a Win2OOO beta 3 operating system, which he rated "solid, really great to work with." He noted the beta was available for download at the Microsoft web site. But remember it's still beta - doesn't yet have all the goodies - AND still may have bugs. He said the full release was late (Microsoft historically is tardy), but he expected it to be packaged and out by October. "However, the Office 2000 suite (a copy of which he submitted as a door prize) will be released mid June." His parting shot: PLEASE check the web site!   Article first published in PC Monitor. PC Monitor is the official publication of the Durham Personal Computer Users' Club and is published monthly at Oshawa, Ontario. The DPCUC mailing address is P.0. Box 2463, Oshawa ON L1H 7V7. The PC Monitor cannot be responsible for errors or inaccuracies in the content, although efforts will be make to publish information accurately. The deadline for articles and information is one week following the monthly meeting. Late submissions may not be published due to tight scheduling. Please submit articles by E-mail to the newsletter editor.