Don't get me wrong, I'm happy as can be, but I don't understand. Fully expected my puter to go down and stop running to never work again after the rollover. But that didn't/hasn't happened (yet). I'm happy but very confused!!!!!!

Didn't/couldn't download any patches, cause not enough memory on my hard drive. So, the only thing that I did was to set my date to a four (4) digit year - Windows 95 defaults to (a two digit year mm/dd/yy, so I set it (some time ago) to mm/dd/yyyy. I am running an old (1993) 386 Pentium laptop (Toshiba) with Window's 95 and Office 97.

Not complaining mind you - happy as can be that it still works. BUT, should I be expecting my puter to crash and burn in the near future or what? This is a sincere honest question? Or is it like a good ol Timex, and should I expect it to keep running as is???? Confused but happy......

Thanks to any puter guru who can shed some light on this for me.

-- fran (fben4077@yahoo.com), January 05, 2000

Answers

BTW, my clock on the puter reads Jan 5, 2000, as it should?

-- fran (fben4077@yahoo.com), January 05, 2000.

The Win/95 Y2K update fixes the following problems: <:)=

1. Find "File or Folders" Dialog (shell32.dll) The Date tab in Find "File or Folders" dialog displays the year in YY format. This format results in incorrect displays for years greater than 2000. For example, entering 03/20/2003 will incorrectly display 03/20/C3. However this does not effect the search. When searching for files changed within a certain date range, enter a 2-digit or 4-digit date and the search will be performed based on the dates entered. This file will be updated only if you are running Windows 95 version 950 or 950a. This issue does not exist in later Windows 95 versions.

2. Windows File Manager (winfile.exe) Windows File Manager does not display or sort dates beyond the year 2000 correctly. When using Windows File Manager to view the contents of folders, and you have selected to view "all file details", the dates of files created in the year 2000 and beyond may appear as follows:

January 1st, 2000 would appear as 1/1/;1

February 3rd, 2023 would appear as 2/3/>3

March 5th, 2036 would appear as 3/5/=6

3. Command Interpreter (command.com) The DATE command (internal to COMMAND.COM) does not correctly handle 2-digit dates from 00-79. Entering 2-digit dates within this range returns the error "Invalid Date".

4. Date/Time Picker (comctl32.dll). Previously, when you set your Regional Settings in the Control Panel to handle years as two digits, the Date/Time Picker function did not correctly reflect the date. This patch addresses that issue.

5. Phone Dialer applet (dialer.exe) The Show View Call Log option doesn't display the date properly after successful completion of a telephone call. If the system date is adjusted to the year 2000, the date is displayed as 100, 101,102, and so on.

For example, in the year 2000, you make a call using the Dialer applet. The log file created or appended to after the completion of the phone connection displays the year portion of the call date incorrectly, such as 101, 102, 103, and so on.

6. Time and Date Control Panel applet (timedate.cpl) When you select the date February 29 and change the year using the up and down arrows in the Date/Time Properties dialog box, the calendar displays February 29 every year, whether it's a leap year or not. This is a display issue in the applet.

7. DHCP Virtual Driver (vdhcp.386) Winipcfg /all - IP Leases obtained on or after 3/01/2000 are reported as being obtained the previous day. The system date is displayed properly but the DHCP client reports a date one day prior.

For example, if you log on to a LAN after March 1, 2000, and you run Winipcfg /all from Start\Run or Ipconfig /all from a DOS VM, the lease obtained date is one day behind. After 2/28/2000, the lease obtained date is one day behind the expected date.

8. Microsoft Foundation Class Library file (mfc40.dll) After the year 2000, programs that use the built in operators of the COleDateTime class may incorrectly parse a date . For example, 02/05/2000 may display as 2/05/100. Microsoft has modified the COleDateTime class so that it is less sensitive to program assumptions.

9. DOS Xcopy (xcopy.exe, xcopy32.exe) When using xcopy in real mode with the optional parameter /D:date, xcopy does not accept years entered as two digits, except for the years 80 through 99. The message "Invalid date" is displayed. When using xcopy in protected mode (from within Windows) two-digit dates are accepted but are recognized as being within the 20th century (02/05/01 is seen as 02/05/1901).

10. Microsoft Run Time Library file (msvcrt40.dll) Some applications that utilize this runtime library may behave as if the current time is one hour earlier than the correct time shown on the Windows clock. The problem will continue for one week from April 1 through April 8, 2001, after which these applications will shift to daylight savings time and again be in sync with the operating system. The problem results from the fact that April 1, 2001, falls on a Sunday, which confused a small algorithm in the run time library file that checks for the start of daylight savings time.This is not a year 2000 issue but rather a daylight savings time issue. It could occur in the years 1973, 1979, 1984, 1990, 2001, 2007, 2012, 2018, 2029, and 2035. What is common about these years is that April 1st falls on a Sunday.

11. OLE AUTOMATION (oleaut32.dll, olepro32.dll, stdole2.tlb, asycfilt.dll) The Microsoft Automation library contains routines for interpreting two digit years and provides a convenient way for applications to create unambiguous (serial) dates. In Windows 95 the current two digit year cutoff is 1999. This means that two digit years beginning with 00 will be interpreted as being in the 20th century, i.e. 1/1/00 is converted to 1/1/1900

-- Sysman (y2kboard@yahoo.com), January 05, 2000.

Also, see this link for Y2K info on Office 97: <:)=

http://support.microsoft.com/support/kb/articles/Q233/5/37.ASP

-- Sysman (y2kboard@yahoo.com), January 05, 2000.

fran: Do you like to mudwrestle?

-- King of Spain (madrid@aol.cum), January 05, 2000.

Hey K.O.S.,

How about chocolate pudding wrestling? At least then you could lick all the pudding off when the ladies were done.

-- (Vincent@manof.God), January 05, 2000.

Sysman. Thank you for taking the time to answer my post, and giving me a great deal of information. You are one of the many here that I have always respected.

King of Spain. Thought you would never ask. ;-)

Under all that 'mud' you're really a very smart guy. I've seen some of your more serious post.

-- fran (fben4077@yahoo.com), January 06, 2000.

You're welcome fran. Just trying to help where I can. <:)=

-- Sysman (y2kboard@yahoo.com), January 06, 2000.