All About Windows 95 Operating System Release 2 OSR2 Bugs? Sean Erwin
This section contains information only about bugs that Microsoft has not yet addressed (not in the knowledge base), and that are unique to OSR2. To see if Microsoft has addressed an issue, see my list of links to Knowledge Base articles which reference OSR2.
Bug #1:
The EMM386 NOEMS bug (thanks to Andrew J. Miller, Paul Antico, Gerhard Wallin, and Bob Kurke):
If you are using the EMM386 memory manager with the NOEMS or RAM switch, your upper memory and extended memory is lost when restarting in DOS mode. All drivers and devices then load into low memory (causing a shortage of low memory). Here's a sample config.sys line which causes the bug.
DEVICE=C:WINDOWSEMM386.EXE NOEMS X=A000-C7FF
Solution: None. Workaround: Don't use the NOEMS or RAM switch with EMM386.EXE.
Bug #2:
The Novell network 32-bit driver bug (thanks to Edward Van Every).
This bug is documented in the 27 January 1997 issue of Communications Week. It can currently be found at this URL.
Bug #3: DirectX is generally buggy at this point. Since DirectX 2 is integrated into OSR2 (and can't be removed), this is an issue for OSR2. The current version of DirectX is 3A, and is a massive download available from Microsoft. I don't have good information on what specific effects these DirectX bugs have, unfortunately. I am currently researching the issue.
That's it! Feel free to submit bug reports, however they must conform to the following criteria to make it into this space:
The effects of the bug must be replicable.
The bug must be unique to OSR2.
The bug must not be documented in Microsoft's Knowledge Base.
