To: ztect who wrote (71 ) 11/18/1998 4:26:00 AM From: ztect Read Replies (1) | Respond to of 277
Regarding PINC in response to Message 6460186 Ted: Thank you for your excellent reply!!!!!!!! Please excuse me when I summarize. An inexpensive fix for the "casual" user should. 1). Diagnose and fix y2k hardware problems 2). Identify software applications and files extensions that are also not y2k compliant. If the y2k software only does the hardware, the y2k product potentially does more harm than good because the "casual" user falsely believes he has corrected the problem by only addressing the various hardware time clocks, whereas the real danger lies in potentailly non y2k compliant software and files which are time sensitive like quicken, excel, spread sheets, et cetera. Is this a good summary? I'm happy to say that MBCK addresses both criteria. Hopefully your review of the product will help determine how well MBCK addressed this criteria established above for an inexpensive product.Source MBCK Online Help: Software Topic: Executable File Scan Option "Hardware compliance is only one side of the issue. Even a perfectly compliant machine may perform erroneous calculations if the application truncates dates to a two-digit format. It is crucial to find out what applications are running on the machine, and then establish whether these applications are known to be compliant. Hence the executable scan. Vendor statements of compliance should not be exclusively relied on, as third party testing often produces dissimilar results. It is important that information used in this assessment be up to date, as the evidence gathering process is a continuous one." Software Topic: Full File System Scan "This option still does the full executable scan but it also scans data files. The user selects the file extensions to be scanned for before the test disk is created. As the scan is run, MILLENNIUM BUG COMPLIANCE KIT searches these files for some common date formats."Software Resource: "Software Database Online" "Finally, if requested, MILLENNIUM BUG COMPLIANCE KIT searches through all your hard drives and compiles a list of all executable programs you have installed. It is then up to you to determine which applications need to be upgraded - unfortunately MILLENNIUM BUG COMPLIANCE KIT cannot do this: there is no simple check to decide whether an individual program is Year 2000 compliant. You must either test it manually, or alternatively if you are a registered user, consult our "Software Database Online" located at our Web Site at www.millenniumbugkit.com and look for the Software Database button (Please have your Serial and Registration numbers handy). If you do not have Internet access, please contact us on information to obtain compliance."Hardware: Normal Testing In Normal Testing, MILLENNIUM BUG COMPLIANCE KIT runs eight tests: -Powered On and Off tests of the Real Time Clock (RTC) (Two tests) -Powered On and Off tests of the BIOS (Two tests) -Powered On and Off tests of the Operating System (OS) (Two tests) -A leap year test on the year 2000 - to ensure that the computer recognises the year 2000 as a leap year, and -A non-leap year test on the year 2001 - to ensure that the computer recognises that the year 2001 is not a leap year. As well as running these tests, MILLENNIUM BUG COMPLIANCE KIT gathers data about your computer's BIOS, OS and Processor. The information gathered is as follows: OS Data - DOS version, DOS type and Windows version BIOS Data - BIOS version, BIOS type, BIOS ID String, BIOS Date and BIOS Manufacturer Processor - type and total hard drive spaceHardware: Extended Testing Extended testing is just that. An extension of the Normal Testing . The eight tests listed above are still run as well as a check for each of the dates listed below. Initial Date Final Date Reason for test 31 Dec 1998 1 Jan 1999 First date where two digit year representation is "99" 8 Sep 1999 9 Sep 1999 The date "9/9/99", is the highest set of values for some representations 30 Dec 1999 31 Dec 1999 Highest date before roll over to 2000 1 Jan 2000 2 Jan 2000 First day change of 2000 3 Jan 2000 4 Jan 2000 First working day of 2000 4 Jan 2000 5 Jan 2000 First working day change of 2000 7 Jan 2000 8 Jan 2000 First end of week for the year 2000 31 Jan 2000 1 Feb 2000 First month change of the year 2000 29 Feb 2000 1 Mar 2000 Leap Year 2000, Transition to month of March 31 Mar 2000 1 Apr 2000 End of the first quarter of the year 2000 28 Feb 2001 1 Mar 2001 Checks that the year 2001 is recognised as not a leap year 31 Dec 2000 1 Jan 2001 First end of year following the year 2000 28 Feb 2004 29 Feb 2004 The year 2004 is a leap year 29 Feb 2004 1 Mar 2004 Leap Year 2004, Transition to month of March One of the aims of the Extended Testing is to test the ability for your computer to accept date transitions above the year 2000. The primary purpose for this is for hardware compliance testing. ----------------------------------------------------