Copyright: Yes2K Help ® 1998 Safetynet, Inc.


Contents

Visit the Safetynet Year 2000 Internet Center at http://www.safetynet.com/yes2k for the most current Year 2000 information and program downloads.

Yes2K Overview

Yes2K detects flaws in the PC hardware that can cause problems when the PC is used after December 31, 1999.  Most of these problems require manual attention or can be corrected automatically by Yes2K.  In a few cases, the only way to correct the problem is to replace the PC BIOS.  After its tests, Yes2K will recommend a solution for bringing the tested PC hardware into year 2000 compliance.

Section 1 - Getting Started

Before running Yes2K

Legal Disclaimer

When to use the Windows and DOS compliance testers

Testing One PC

Testing a standalone PC

Testing a network file server

Yes2K Automatic Correction

Silently monitor and correct Year 2000 problems

Testing Multiple PCs

Saving test results to a central data file

Automatic testing of network workstations

Create a Collection Diskette to test multiple standalone PCs

Section 2 - Compliance Manager Console

Managing the test results of several or hundreds of workstations

Technical Reference

Yes2K test results Type Codes

Yes2K test results file format

Contacting Safetynet


Before Running Yes2K

In performing its Year 2000 tests, Yes2K temporarily changes the PC system date to 1/1/2000 and beyond.

Safetynet strongly recommends that you close down any date dependent software before running this test.  In addition, if the PC runs time-bound software, please backup the system before running this program.

In any event, the developers will not be held responsible for any loss of data or program use because of running Yes2K.

Legal Disclaimer


Legal Disclaimer

Safetynet expressly disclaims any warranty for Yes2K.  Yes2K and any related documentation is provided "as is" without warranty of any kind, either express or implied, including, without limitation, the implied warranties or merchantability, fitness for a particular purpose, or noninfringement.  The entire risk arising out of use or performance of the software product remains with you.

To the maximum extent permitted by applicable law, in no event shall Safetynet or its suppliers be liable for any special, incidental, indirect, or consequential damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising out of the use of or inability to use Yes2K or the provision of or failure to provide Support Services, even if Safetynet has been advised of the possibility of such damages.


Yes2K for Windows and DOS

Yes2K is provided in Windows and DOS versions.

•	The Windows version is named YES2K.EXE.  It should be used to test systems running Windows 98, Windows 95 and Windows 3.x.

NT Note:  Windows NT blocks the hardware tests needed to check for year 2000 compliance.  Because of this, YES2K.EXE cannot be run on a PC running Windows NT.  To test a Windows NT PC or server, shut down NT and boot the computer from a DOS diskette.  Then run YES2KDOS.EXE from diskette.  After the test, check the date and time to make sure they are correct.  Then restart Windows NT from the hard drive.

•	The DOS version is named YES2KDOS.EXE.  It is used to test PCs booted to a DOS prompt.  YES2KDOS should not be run in a DOS Window under Windows.  Use the Yes2K Windows version instead.


Testing a Standalone PC

The following steps will run Yes2K on different operating system platforms.

Important:  Yes2K sets the system date to 1/1/2000 and beyond to do its compliance tests.  Before running Yes2K, make sure that all date sensitive programs are closed.

PCs running Windows 98, Windows 95

1 	Start Windows and bring up the graphical user interface.

2 	Close all date sensitive software.

3 	Select Run from the Start button and Browse to the directory where Yes2K files are located.  Alternately, run Explorer and locate the Yes2K directory.

4 	Run YES2K.EXE.

5 	Follow the on-screen prompts.

PCs running Windows 3.x

1 	Close all date sensitive software.

2 	Activate the Windows Program Manager.

3 	Select the File | Run menu and browse to the directory where Yes2K is located.

4 	Run YES2K.EXE.

5 	Follow the on-screen prompts.

PCs running DOS and Windows NT

1 	Close all date sensitive software.

2 	From DOS (not a DOS window under Windows), switch to the directory where Yes2K is located.

3 	Run YES2KDOS.EXE.

4 	Follow the on-screen prompts.


Testing a Network File Server

PC-based file server hardware running networks such as Novell Netware, NT Advanced Server and Banyan Vines can be tested for year 2000 compliance as long as they can be booted from a DOS diskette.  Follow the steps below to perform the test.

1 	Down the network.

2 	Boot the file server to a DOS prompt.

3 	Run the YES2KDOS.EXE program.

4 	Follow the on-screen prompts.

5 	After Yes2K is finished with its tests, make sure the server date and time are reset properly before starting the network.


Year 2000 Compliance Monitor

Included with Yes2K is the Yes2K monitor (YES2KMON.EXE) which brings year 2000 hardware compliance to non-Y2K compliant PCs.

Yes2Kmon eliminates having to keep track of PC BIOS and Real-Time Clock problems by analyzing the hardware date each time the PC is booted.  For network administrators, Yes2Kmon can be installed automatically to all PCs that need corrective action. This eliminates the need to visit each PC, greatly reduces time spent diagnosing and correcting PC Y2K hardware compliance issues.

How Yes2Kmon Works

Yes2Kmon is distributed to non-Y2K compliant PCs by the Yes2K Windows or DOS compliance testers.  When Yes2K determines that the PC hardware can support Year 2000 dates, it will install Yes2Kmon automatically (via the /AUTOFIX command-line switch) or manually by the user selecting OK when prompted.

Yes2Kmon is run from the CONFIG.SYS file before any other applications are run.  It silently reads system date settings and determines if corrective action is needed.  If no action is required, Yes2Kmon ends.  Otherwise, it displays the current incorrect system date and prompts the user to supply the correct date.  Once a valid date is entered, Yes2Kmon ends.  Since Yes2Kmon is not a device driver or TSR, no memory overhead is taken from the system after it runs.


Central Data File
Saving test results to a central data file

Yes2K can append the test results of hundreds and thousands of PCs to a central data file.  Using the Yes2K Compliance Manager (YES2KADM.EXE), the administrator can analyze this data and produce Year 2000 PC compliance reports.

Testing multiple standalone PCs

Automatic testing of network workstations

Yes2K test results file format


Collection Diskette
Collection Diskette for Standalone PCs

Testing Multiple Standalone PCs

The Yes2K program and test results can be stored on a 3.5" HD or larger collection diskette.  With this method, the administrator visits each PC and runs the Yes2K program from diskette.  The results of the year 2000-compliance tests for each PC are appended to a diskette data file for later analysis and reporting.

During the initial setup of Yes2K, choose a diskette drive to install its files.  When testing a large number of standalone systems, free diskette space can be increated by removing the YES2K.HLP and YES2KADM.EXE files from the collection diskette.

To instruct Yes2K to write its results to the RESULTS.Y2K data file, the workstation name must be provided as a command-line switch (using /WN= or /WE=) when the program is run.

The following example runs the DOS version of Yes2K, sets the workstation name to PC01 (/WN=PC01), and appends the results to its default RESULTS.Y2K file:

YES2KDOS.EXE /WN=PC01

Select the following link for addition command-line switches and examples.

Yes2K Command-line Switches and Examples


Yes2K Switches and Examples
Yes2K Command-Line Switches and Examples

See also:

Yes2K Test Results File Format

When Yes2K is run in network or collection disk mode, the workstation name must be specified as a command-line switch.  Following is a list of the command-line switches.

Workstation Name Switches (required to save test results to a file)

For Yes2K to write its test results to a file, a workstation name must be specified.  Use one of the following two command-line switches to specify a workstation name.

/WN=<workstation name>

/WE=<workstation_name_from_environment_variable>

Results File Switch (optional)

If a workstation name is specified, Yes2K will append its results to a RESULTS.Y2K file located in its directory.  To specify a different directory and file prefix for its results, use the /RESULTS= switch.

/RESULTS=<results_directory_and_file_prefix>

Switches only available in the Yes2K Windows scanner (YES2K.EXE)

/NODSTMSG - Don't display Daylight Savings Time message

/DSTRESTART - Restart Windows when Daylight Savings Time is active

Defining a Workstation Name

/WN=<workstation_name>

Sets the workstation name to whatever is specified for <workstation_name>.  As an example, using /WN=PC01 will set the workstation name to PC01.

In a network environment, it may be possible to use the user's login name and/or workstation network card address.  For example, in Netware networks, the following line can be used to name the workstation as the user's network login name and network card NIC address:

#J:\BIN\YES2K.EXE /WN=%1-%P_STATION

/WE=<name_from_environment_variable>

Instructs Yes2K to take the workstation name from an environment variable.  For example, if an environment variable PCID is set to a unique name on each workstation, then /WE=PCID will set the workstation name to that value.  For example:

#J:\BIN\YES2K.EXE /WE=PCID

In the above example, if environment variable PCID is set to LABPC01, then the workstation name field will be set to LABPC01 in results file RESULTS.Y2K.  When a Y2K problem can be corrected, Yes2K installs the Yes2Kmon monitor locally on each non-Y2K compliant PC.  An entry is made to its log file indicating that the correction was installed.

Saving Test Results to a File

/RESULTS=<results_directory_and_file_prefix>

When collecting year 2000-compliance data for multiple PCs (via /WE= or /WN=), Yes2K writes its test data to a RESULTS.Y2K file in its program directory.  Use the /RESULTS= switch to specify the directory and file prefix of a different location for this file.  For example, use /RESULTS=J:\DATA\RESULTS to write data to a RESULTS.Y2K file in the J:\DATA directory.

Note:  Yes2K always adds a .Y2K file extension to the end of its results files.  This enables its Compliance Console to easily locate Yes2K test results files.

Windows Tip - UNC Names:  Besides using standard drive and directory paths, the Windows version of Yes2K can also save results using UNC naming conventions.  For example, to save results to file server MAIN and drive SYS, you could use /RESULTS=\\MAIN\SYS\DATA\RESULTS.Y2K.  Depending on the Windows version and network client, you may have to format your UNC path differently.

Additional Command-Line Switches

/NODSTMSG

Not available in the Yes2K DOS scanner (YES2KDOS.EXE)

Windows 95 and 98 can automatically adjust the time forward and backward for Daylight Savings Time.  This will prevent Yes2K from properly completing its tests.  To test a PC with this feature enabled, Yes2K will disable the Daylight Savings Time option.  It then displays a message to the user that the system must be restarted to perform the year 2000-compliance test.  Use the /NODSTMSG switch to prevent this message from being displayed.  Used in conjunction with the /DSTREBOOT switch, Windows can be restarted and tested automatically without user intervention.

/DSTREBOOT

Not available in the Yes2K DOS scanner (YES2KDOS.EXE)

When Daylight Savings Time automatic adjustment is set under Windows 95 and Windows 98, Yes2K must disable this setting and restart Windows.  Otherwise, it cannot proceed with the year 2000-compliance test.  Use this switch along with the /NODSTMSG switch to automatically restart Windows, rerun Yes2K from the network login script, and perform its tests.  If this switch is not used, Yes2K will not test the system until it is restarted and the Daylight Savings Time automatic adjustment is disabled.


Yes2K Test Results File Format

See also:

Yes2K Result Type Codes

Yes2K Command-line Switches and Examples

When run with /WN= or /WE= command-line switches, Yes2K will append its year 2000 compliance test results to a data file.  This file is written in tab-delimited format, with the first row containing the field headers, and each additional row containing the test results for a particular computer.  The format of the Results file is as follows:

Field 1: Station Name

Shows the name of the workstation that is tested.  This value is taken from the /WN= or /WE= command-line switch.

Field 2:Y2K Dates

Shows whether the PC can support dates after December 31, 1999.  Value is Pass or Fail.  See Result Type 2 for more details.

Field 3: Y2K Rollover

Shows whether the PC BIOS automatically roll over from December 31, 1999 to January 1, 2000.  Value is Pass or Fail.  See Result Type 3 for more details.

Field 4: Y2K Century

Shows whether the CMOS century is updated to 20 when the year changes from 1999 to 2000.  Value is Pass or Fail.  See Result Type 1 for more details.

Field 5: Y2K Leap Support

Shows whether the BIOS supports leap year dates in year 2000 and beyond.  Value is Pass or Fail.  See Result Type 4b for more details.

Field 6: Y2K Leap Roll

Shows whether the system will automatically roll to leap year dates in year 2000 and beyond.  Value is Pass or Fail.  See Result Type 4a for more details.

Field 7: Correctable

A field value of Yes indicates that Yes2Kmon can detect and correct the Y2K-compliance problem.  A 'No' value means that the problem is not correctable by Yes2Kmon.  A 'n/a' value indicates that the workstation does not require or will not benefit from Yes2Kmon.

Field 8: Yes2Kmon Installed

Shows whether Yes2Kmon has been installed on the workstation.  This will correct the Y2K problem during the workstation boot process.

Field 9: Test Date

The date that the Yes2K compliance test was performed.

Field 10: Test Time

The time of day that the Yes2K compliance test was performed.


Result Types
Result Type Codes

Contacting Safetynet

Following is a list of result type codes that Yes2K may display after running its tests. If Yes2K detected a problem, its Compliance Test Results window will display the type code of the problem.  When Yes2K is run in network or collection diskette mode, the heading of each data column maps to a Type code as follows:

Y2KDates - Type 2
Y2KRoll - Type 3
Century - Type 1
LeapYr - Type 4b
LeapRoll - Type 4a

Type 1 - CMOS Century Does Not Roll from 19 to 20

Severity - Low

Action Needed - Probably Not

Problem Correctable by Yes2Kmon - Yes

When the year changes from 1999 to 2000, the BIOS does not increment the century setting in the CMOS.  However, the BIOS contains code to the correct this error as long as the system uses the BIOS to read the date.  If a program bypasses the BIOS and reads the date directly from CMOS, the year will be interpreted as 19xx instead of 20xx.  Since most programs use the BIOS to read the date, the likelihood of this error occurring is small.

Solution

In most cases, you will never notice this error since the operating system and many programs make calls to the BIOS to read the date and time.  This will automatically fix the problem.  However, to be on the safe side, the first time the PC is booted in the year 2000, check the date and set the correct date manually if necessary.  Year 2000+ dates will then be correctly supported.

Type 2 - No Year 2000 Date Support

Severity - High

Action Needed - Yes

Problem Correctable by Yes2Kmon - No

This code is returned when Yes2K cannot change the system date to support a date after December 31, 1999.

Solution

The problem can be caused by the PC BIOS not supporting year 2000 dates, or it could be due to a program (e.g. security system) preventing the date from being changed.  If there is no program in place to prevent date change, then the BIOS must be replaced with a BIOS that is Year 2000 compliant.  Otherwise, year 2000+ dates will not be supported by this computer.

Type 3 - Date Does Not Roll from 1999 to 2000

Severity - Medium

Action Needed - Yes

Problem Correctable by Yes2Kmon - Yes

After 1999, the BIOS date will not automatically change to year 2000.  Programs that read the date will receive an incorrect year.

Solution

The first time the PC is started in the year 2000, the date should be checked and adjusted manually.  It will then support year 2000+ dates correctly.

Type 4a - Leap Years Dates Not Set in Year 2000+

Severity - Medium

Action Needed - Yes

Problem Correctable by Yes2Kmon - No

This problem code indicates that the PC will not automatically set leap year dates in year 2000 and beyond.

Solution

The first time the PC is started on or after year 2000+ leap year dates, the date should be checked and adjusted manually.

Type 4b - Leap Years Dates Not Supported in Year 2000+

Severity - High

Action Needed - Yes

Problem Correctable by Yes2Kmon - No

This problem code indicates that the BIOS does not support year 2000+ leap year dates.  Yes2K tried to set the date to February 29, 2000 and the date was not accepted.

Solution

The BIOS must be replaced for proper handling of year 2000+ dates.

Type 5 - System Date Could Not Be Changed

Severity - Low

Action Needed - Yes

Problem Correctable by Yes2Kmon - No

Yes2K did not perform its tests since the system date could not be changed.  Year 2000 compliance tests were not performed.

Solution

Check the system and disable any programs (e.g. security software) which may prevent changing the system date.  Then run Yes2K again to perform its Year 2000 compliance tests.

Type 6 - Real Time Clock (RTC) Could Not Be Read

Severity - Low

Action Needed - Yes

Problem Correctable by Yes2Kmon - No

Yes2K could not access the date and time from the Real Time Clock chip (RTC).  Year 2000 compliance tests were not performed.

Solution

If this is an original PC or XT, the system date must be changed each time the computer is started, so make sure to set the proper date.  If this PC is IBM PC AT-compatible, try resetting the computer and running Yes2K again.  If the test still does not work on an AT-class or higher computer, please notify Safetynet technical support.


Contacting Safetynet

Safetynet can be contacted at the following address:

Mailing Address

Safetynet, Inc.
140 Mountain Ave.
Springfield, NJ 07081
United States of America

Phone Numbers

973-467-0465 (Support - 9am to 5pm EST)
973-467-1611 (Fax)

EMail

yes2k@safetynet.com

WWW

http://www.safetynet.com


Testing Network Workstations

While Yes2K is easily run in standalone mode to scan an individual computer, its has been designed to automatically test and correct all workstations in a networked environment. Workstation testing can be done without the admnistrator having to visit each workstation.  To accomplish this, Yes2K provides both Windows (YES2K.EXE) and DOS (YES2KDOS.EXE) compliance scanners, and a central Compliance Manager console (YES2KADM.EXE).  The steps required to scan multiple networked workstations are as follows:

1 	Install Yes2K to a file server directory.

2 	Run the Yes2K Compliance Manager console (YES2KADMN.EXE) and set the appropriate scanner options under the Options | Network Options... menu.

3 	Allow access to the Yes2K server directory for all users.

4 	Determine how each workstation will be identified (via /WE= or /WN= switches) in the central results file

5 	Run the Yes2K workstation scanner from each workstation using either the /WN= or /WE= workstation name switches. Use YES2K.EXE for testing Windows PCs and YES2KDOS.EXE for DOS PCs. Either program can be added to the login script to automatically scan network workstations.

6 	After workstation test data has been collected, run the Yes2K Compliance Manager console and open the RESULTS.Y2K file.  If you used the /RESULTS= switch to specify another data file location and name, select that file instead.

7 	Yes2K collection data for all tested PCs will be displayed in the Test Results list for analysis, sorting and printing.

8 	Once a PC has been added to the Test Results list, the Yes2K scanners will not test those PCs again.  To retest one or more PCs, highlight them and select the Delete / Retest... menu choice.

Yes2K Command-line Switches and Examples


Yes2K Compliance Manager

The Compliance Manager (YES2KADM.EXE) is the management console for Yes2K.  It allows the administrator to centrally manage and analyze Year 2000 tests from several to over 10,000 PCs.

The Compliance Manager program is made up of the following:

Menus

File Menu

Open Results File...

Save Results File...

Print...

Exit...

Edit Menu

Delete / Retest...

Options Menu

Network Options...

View Failed PCs in Red

Help Menu

Contents

Register

Yes2K Internet Site

Results Area

Sort Results By:

Test Results List

Workstation Compliance Table


Open Results File...
Select this menu option to open a Results file created by the Yes2K Windows or DOS scanners.  Yes2K files have an extension of .Y2K.


Save Results File...
Select this menu option to save the Yes2K results file.  The file should be saved if you have removed any workstations from the list for deletion or retest.


Print...
The Print menu allows you to print the list of test results in column format.  Select "All" to print all workstations in the list.  Choose "Selected" to only print the highlighted workstations.  If "Selected" is chosen, the Pass/Fail statistics that appear at the bottom of the tests results list will be recalculated and printed for the selected workstations.  The test results will be printed in the sort order that they are displayed.


Exit
Choose Exit to end the Yes2K Compliance Manager console.  If any list items were deleted, you will be prompted to save the new list.


Delete Retest...
Workstations that appear in the results list will not be tested again, so to retest a workstation, it must be deleted from the list.  Use the Delete / Retest menu option to remove a tested workstation from the results list.


Network Options

Fix Non-Compliant PCs

When a PC has a correctable Y2K compliance problem, Yes2K can install its Yes2Kmon program to monitor and correct the problem.  In network mode (with /WN= or /WE=), the default is to automatically install Yes2Kmon when needed.  Remove the check box from this setting to prevent this protection from being installed.  In standalone mode, the user is given the option of installing protection each time the Yes2K tester is run.

Date Warning

In performing its Year 2000 tests, Yes2K temporarily changes the PC system date to 1/1/2000 and beyond.  By default, Yes2K displays a warning to the user to exit any date dependent software before continuing with the Y2K-compliance tests.  We strongly recommend that you keep this warning message displayed.

If your environment does not contain any active date-dependant software or data files, you may wish to suppress this warning.  Remove the check from this option to prevent the date warning message from being displayed.

Disclaimer - Before Running Yes2K

Pre-scan Delay

When logging into a network, sometimes it takes a few seconds for the network client to synchronize the workstation time with the file server.  This unexpected change of date and time can cause problems with the Yes2K tests.  Use the pre-scan delay option to tell Yes2K to wait a specified number of seconds before beginning its year 2000 tests.


View Failed PCs in Red
Workstations that cannot be corrected by the Yes2K monitor are displayed in the test results list with red text.  Place a check mark in front of this option to display failed workstations in red, or remove the check mark to display all workstations with black text.


Registering Yes2K
This menu choice displays the Yes2K registering information window, which describes the various purchasing options for Yes2K.


Internet Site
Yes2K is distributed and supported from the Safetynet Internet site located at http://www.safetynet.com/yes2k

Contacting Safetynet


Sort Results By
The test results table is initially sorted by workstation name.  Select the desired field and the Compliance Manager will sort the test results by that field.  The test results will be printed in the sort order that they are displayed.


Test Results List

The Test Results List is the main window of the Yes2K Compliance Manager.  Each row contains the compliance results for a specific workstation.  Ten columns of data are listed for each workstation.  By default, workstations that have a Year 2000 hardware problem that cannot be corrected by Yes2K are highlighted with red text.

The results list resizes dynamically to the size of the Compliance Manager window. If columns appear off the right side of the list, maximize the Compliance Manager or use the horizontal scroll bars at the bottom of the list window.

Test Results Columns

Station Name - Name of workstation tested (via /WN= or /WE= switches)
Y2KDates - Can the workstation support dates after 12/31/1999
Y2KRoll - Did the BIOS roll correctly from 12/31/1999 to 1/1/2000
Century - Did the CMOS century byte roll from 19 to 20
LeapYr - Are leap year dates after 12/31/1999 supported
LeapRoll - Do leap year dates roll properly
Fixable - Can the Yes2K workstation monitor correct this problem
Fixed - Was the workstation monitor installed to the PC to fix the problem
TestDate - Date that workstation was tested (mm-dd-yyyy)
TestTime - Time in 24 hour format that workstation was tested (hh:mm:ss)

Click here to view specifics of the compliance test columns

Test Results Statistics

The bottom line of the Test Results List displays the number of workstations in the list, and the percent of workstations passing each test.  For the Fixable column, the statistic shows the percent of PCs that either don't need a fix (n/a) or can be fixed by the Yes2K monitor (Yes).  For the Fixed column, the statistic shows the percent of PCs that either don't need a fix (n/a) or have the Yes2K monitor installed to their local hard drive (Yes).


Workstation Compliance Table
Displays the results of a highlighted workstation in table format.  Tests which did not pass are displayed in red.