Just wanted to give people a heads up that Windows 95 is still not fully y2k compliant. But Microsoft is working on it....

-- Saint Francis (STFrancis@heaven.com), May 28, 1999

Answers

what about windows 98?

-- Daryll Smallwood (twinck@wfeca.net), May 28, 1999.

Do you have a link for this info...

Thanks

-- newlurker (no@no.com), May 28, 1999.

No link... internal MS info...

Not authorized to post it...

-- Saint Francis (STFrancis@heaven.com), May 28, 1999.

thanks for the info, will be keeping my eyes open

-- newlurker (no@no.com), May 28, 1999.

Troll Alert

-- TW (TrollWatcher@:P.com), May 28, 1999.

Troll Alert... where...???

or does it bother you that I would like to honor the non-disclosure I have with MS....????

Windows 95 Year 2000 Update

May 3, 1999

THE INFORMATION BELOW IS MICROSOFT CONFIDENTIAL

Alert number: Q230173

Before you acuse someone of being a troll get your facts straight...

-- Saint Francis (STFrancis@heaven.com), May 28, 1999.

Saint Francis --- how serious is the non-compliancy and where is it likely to bite hardest if not fixed?

-- BigDog (BigDog@duffer.com), May 28, 1999.

Are you talking about the known problems, or are you saying there are new ones? Microsoft has already issued patches for Win95.

http://www.microsoft.com/technet/year2k/product/user_view68382EN.htm

-- Buddy (.@...), May 28, 1999.

Does Win95 and Win98 say 2000 in their name? So why would you expect them to be compliant? Seriously, Windows 98 also has Y2K "issues". ("Issues" is Microsucks microspeak for "bugs".)

The Microsucks site has pages where you can find out the status of various of Microsucks products and what patches/upgrades/"service releases" (whatever) are available. You want to spend a few frustrating and unproductive days, check it out. Happy hunting and watch out for the quicksand.

-- vbProg (vbProg@MicrosoftAndIntelSuck.com), May 28, 1999.

Buddy, did not see the last patch they released on May 26th. Should've spent less time at Microsoft TechEd... They still haven't updated their partnering website though. Just read the resolution and have to add that it was about time...

Now let's hope that all Win95 users know how to update there machines....

-- STFrancis (STFrancis@heaven.com), May 28, 1999.

Hmmm. . .some folks really DO believe there might be some problems for which fixes have not been released. For example, next week's issue of 'Access Control & Security Systems Integration' features these interesting points:

True or not? 'Beats me.

(Excerpt)

Access Control & Security Systems Integration

Protecting against chemical, biological and Y2K threats

05/30/99

Several locations of a Washington, D.C., federal agency are highly susceptible to chemical and biological attack and are unaware of Y2K-related threats to the integrity of their access control computer systems. Such was the outcome when a team of security professionals was asked to assess the susceptibility of the sites to attacks from chemical and biological agents, and to assess the Year 2000 readiness of the access control computer systems.

(Snip)

Latent Y2K defects: The plausible Y2K scenario considered by the assessment team was that the facility considers that the access control computer system is completely Y2K compliant, and does nothing more to assure resistance to Y2K malfunctions. To date, those in charge of safeguarding mission-critical computer systems from Year 2000 malfunctions have focused primarily on older computer systems and components. This is because older systems include hardware containing computer chips with two-digit date algorithms. For example, when the date changes from 1999 to 2000, the two digits in the algorithm change from 99 to 00, which the computer reads as out of sequence, causing malfunction.The newest systems consist of hardware components that have solved this problem.

However, a potentially bigger problem exists because of problems with the operating system software and applications.

What most people do not realize is that nearly all Windows operating systems have prerequisite patches or fixes. Of the four versions of Windows 95 available (A, B, C and Plus), three of the versions require the replacement of the WINFILE.EXE and COMMAND.COM files.

In Windows 98,the comctl32.dll file needs to be replaced. In Windows NT 4.0, Service Pack and several Hot Fixes need to be installed or the operating system does not correctly recognize the year 2000 as a Leap Year. The same problem exists in the Microsoft office suites. For example, Office 95 needs two files replaced, and Office 97 requires a service patch. To make things even more complicated, it is certain that not all patches have been discovered.

Periodically, as more Y2K problems are identified, new fixes will be added to the Microsoft prerequisite list.

Problems are magnified by the common perception that new computers have no Y2K problems. Failure to install required updates and service patches usually will not prevent computers from booting or cause an immediate crash on Jan.1, 2000. In many cases, a missing patch will impact only a specific function.

(snip)

While the Y2K hardware malfunction affects mostly older PCs, the operating system and office suite application glitches will require service patches or upgrades for nearly every PC. This is a time-consuming process that will require identification and resolution, computer by computer. Service patches are available free at the Microsoft web site:

www.microsoft.com/technet/year2k/product/product.htm

-- FM (vidprof@aol.com), May 28, 1999.

 Here is some interesting info on Microsoft from the Army Y2K page.

Technology Integration Center Y2K Resource Center

http://www.hqisec.army.mil/y2kweb/
 

WARNING!

Certain Y2K tools have been reported to corrupt Windows 95 systems.
Read the disclaimer at the top of the Y2K Results page before you attempt
to use any software tools to check your PC for Y2K compliance.

Also, we received this note from a user in the Air Force community
regarding flash BIOS upgrades:

"In two cases at our base, people downloading flash BIOS
upgrades and installing them got the wrong BIOS [patch].
This resulted in disabling their PC. We did not have the
capability to reprogram the BIOS chips, so we could not fix
the problem without replacing the BIOS chip. It might be a
good idea for you to put a disclaimer somewhere in the
information on the BIOS upgrades that they must only be
used on those specific PC configurations because they could
damage other PCs. This is not a case in which someone can
safely experiment to see if it works!"

(Update, Dec. 98--I have had several additional e-mails from users who
have seriously "injured" their PCs by attempting to apply an incorrect BIOS
patch. Be Careful!!!)
 

Microsoft Y2K Compliance
Info.

Microsoft Corporation has released Y2K compliance information on their
web site. This is an excellent site for obtaining current information on
Microsoft products and obtaining patches or "work-arounds" for Microsoft
software. However, you should ensure a patch is absolutely necessary
and fully tested by your organization in a non-production environment
before utilizing ANY Y2K software patches!

-- Brian (imager@home.com), May 28, 1999.