Microsoft Y2K  
Microsoft
 This static CD-based web site is representative of the www.microsoft.com/y2k site as of October 15, 1999.

Microsoft Year 2000 Readiness Disclosure & Resource Center
File & Print for Netware (FPNW) 4.0 (Korean) - 32-Bit Win

Product Summary
Product: File & Print for Netware (FPNW)
Version: 4.0
Category: Compliant*
Operating System: 32-Bit Win
Language: Korean Release Date: N/A
Operational Range: -
Prerequisites: Installation of SAP Agent before setup of FPNW
Product Dependencies: SAP Agent, Spooler
Clock Dependencies: Time stamps for file/account creation, expiration of accounts
Last Updated: 22 Feb 1999
Product Details

How the product handles dates:

Product utilizes dates (including the traditional Chinese and Korean special calendar) to maintain current status of FPNW accounts, including (however not limited to): login/logout times, account expiration dates, password expiration dates, restricted login times, file creation dates.

 

Testing guidelines and recommendations:

It is recommended that Year 2000 tests be performed across clients that will be accessing the noted FPNW servers. Year 2000 testing on FPNW is essentially based on the concept of setting the current date on the FPNW server to a noted Year 2000 test scenario date, upon which various date-related tests can be performed to determine any issues relating to the productÆs date handling characteristics.

Below is a listing of potential tests:

FPNW Setup:

  • Install / Uninstall FPNW: Confirm that the service can be installed properly on the scenario test dates, and that the service can be started without error. Installation of FPNW tools should also be tested.

Login/Logout:

  • Client ability to login to/log out of server. Clients being used in the test should be able to access the server and allow the user to log in.
  • Confirm the expected dates are shown in the login / logout time stamps on the various clients. The 16-bit logout.exe utilized by FPNW states the userÆs login and logout times in regards to the connection to the server. The displayed times should display as expected when tested under the scenario test dates.

File and Folder Creation/Deletion:

  • Confirm full functionality of file copy (up to server / down to client machine), file creation, deletion, and renaming. Confirm that timestamps are created and displayed correctly. This would involve testing both in a Graphic User Interface (GUI) environment as well as in an MS-DOS environment. The same tests can be applied to directories/folders.

FPNW Administrative Programs Functionality:

  • Confirm functionality of FPNW-related GUI applications. These tests would include confirming that FPNW-related programs execute without error, and that user interfaces function and display as expected. GUI applications that utilize the date should show the current date properly. This would include testing FPNW properties under Server Manager and the Local User Manager NetWare Compatible properties page.
  • User Accounts: Confirm that user accounts can be created, modified, and deleted on the scenario test dates. This should be tested across available administrative programs.
  • Current 16-bit Administrative Applications: Confirm that accessible 16-bit administrative applications and utilities work as expected. (attach, capture, chgpass, endcap, login, logout, map, setpass, slist, etc.).
  • Account expiration dates expire the account/password. Users should not be able to log in when the account has been disabled, and the expiration date falls under one of the scenario test dates. User expiration dates can be administered through the Local User Manager NetWare Compatible properties page.

Print Functionality:

  • Functionality of print servers. Confirm that buttons/functions under the Server Manager / FPNW / Print Servers menu work as expected. Confirm that print servers can be installed and removed, and that FPNW server can handle print jobs sent to the installed FPNW print servers.

 

 

 

Return to Search Screen

Legend of Symbols:
* The product is compliant with recommended customer action. This indicates a prerequisite action is recommended which may include loading a software update or reading a document.
# The product is compliant with an acceptable deviations from Microsoft's standard of compliance. An acceptable deviation does not affect the core functionality, data integrity, stability, or reliability of the product.
+ The product is compliant with pending Year 2000 software updates. Future maintenance actions will be recommended shortly. See Product Guide for further details.
Note: Compliance ratings given for each product assume that all recommended actions have been taken.

If after reviewing this information you have additional questions related to this product, click here.

 

YEAR 2000 READINESS DISCLOSURE

ALL COMMUNICATIONS OR CONVEYANCES OF INFORMATION TO YOU CONCERNING MICROSOFT AND THE YEAR 2000, INCLUDING BUT NOT LIMITED TO THIS DOCUMENT OR ANY OTHER PAST, PRESENT OR FUTURE INFORMATION REGARDING YEAR 2000 TESTING, ASSESSMENTS, READINESS, TIME TABLES, OBJECTIVES, OR OTHER (COLLECTIVELY THE "MICROSOFT YEAR 2000 STATEMENT"), ARE PROVIDED AS A "YEAR 2000 READINESS DISCLOSURE" (AS DEFINED BY THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT) AND CAN BE FOUND AT MICROSOFT'S YEAR 2000 WEBSITE LOCATED AT http://www.microsoft.com/year2000/ (the "Y2K WEBSITE"). EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED PURSUANT TO THE TERMS HEREOF, THE TERMS OF THE Y2K WEBSITE, AND THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT FOR THE SOLE PURPOSE OF ASSISTING THE PLANNING FOR THE TRANSITION TO THE YEAR 2000. EACH MICROSOFT YEAR 2000 STATEMENT CONTAINS INFORMATION CURRENTLY AVAILABLE AND IS UPDATED REGULARLY AND SUBJECT TO CHANGE. MICROSOFT THEREFORE RECOMMENDS THAT YOU CHECK THE Y2K WEBSITE REGULARLY FOR ANY CHANGES TO ANY MICROSOFT YEAR 2000 STATEMENT. EACH MICROSOFT YEAR 2000 STATEMENT IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. CONSEQUENTLY, MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. MOREOVER, MICROSOFT DOES NOT WARRANT OR MAKE ANY REPRESENTATIONS REGARDING THE USE OR THE RESULTS OF THE USE OF ANY MICROSOFT YEAR 2000 STATEMENT IN TERMS OF ITS CORRECTNESS, ACCURACY, RELIABILITY, OR OTHERWISE. NO ORAL OR WRITTEN INFORMATION OR ADVICE GIVEN BY MICROSOFT OR ITS AUTHORIZED REPRESENTATIVES SHALL CREATE A WARRANTY OR IN ANY WAY DECREASE THE SCOPE OF THIS WARRANTY DISCLAIMER. IN NO EVENT SHALL MICROSOFT OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER REGARDING ANY MICROSOFT YEAR 2000 STATEMENT INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS, PUNITIVE OR SPECIAL DAMAGES, EVEN IF MICROSOFT OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, SO THE FOREGOING LIMITATION MAY NOT APPLY TO YOU. THE INFORMATION CONTAINED IN EACH MICROSOFT YEAR 2000 STATEMENT IS FOUND AT THE Y2K WEBSITE AND IS INTENDED TO BE READ IN CONJUNCTION WITH OTHER INFORMATION LOCATED AT THE Y2K WEBSITE, INCLUDING BUT NOT LIMITED TO MICROSOFT'S YEAR 2000 COMPLIANCE STATEMENT, THE DESCRIPTION OF THE CATEGORIES OF COMPLIANCE INTO WHICH MICROSOFT HAS CLASSIFIED ITS PRODUCTS IN ITS YEAR 2000 PRODUCT GUIDE, AND THE MICROSOFT YEAR 2000 TEST CRITERIA.

ANY MICROSOFT YEAR 2000 STATEMENTS MADE TO YOU IN THE COURSE OF PROVIDING YEAR 2000 RELATED UPDATES, YEAR 2000 DIAGNOSTIC TOOLS, OR REMEDIATION SERVICES (IF ANY) ARE SUBJECT TO THE YEAR 2000 INFORMATION AND READINESS DISCLOSURE ACT (112 STAT. 2386). IN CASE OF A DISPUTE, THIS ACT MAY REDUCE YOUR LEGAL RIGHTS REGARDING THE USE OF ANY SUCH STATEMENTS, UNLESS OTHERWISE SPECIFIED BY YOUR CONTRACT OR TARIFF.


 

Friday, August 6, 1999
1999 Microsoft Corporation. All rights reserved. Terms of use.

This site is being designated as a Year 2000 Readiness Disclosure and the information contained herein is provided pursuant to the terms hereof and the Year 2000 Information and Readiness Disclosure Act.