BugNet Top 10 Bug/Fix List
HERE ARE some of the more dangerous, comic or widespread bugs affecting PCs right now, selected from among thousands of entries in the BugNet BugMaster Database.
Note: This list changes constantly. Don't assume that software doesn't work because it has bugs listed here. The bugs may not affect you, or they may have been fixed. BugNet recommends contacting the respective software publishers to check the current status of issues that may affect you.
Lotus has received reports from customers on problems using Lotus Enterprise Integrator (LEI) 3.0 to do a Direct Transfer Activity via an ODBC link from Microsoft Access. Before any data is transferred, LEIACT.EXE crashes, which in turn crashes LEI and the Domino server. If this is happening, Lotus says you have to check your version numbers. Go to the ODBC Administrators Driver tab and check which version of MDAC you are using. If it is MDAC 2.1 or higher, you are using the Access ODBC driver 4.00.xx or higher, which according to Lotus is an unsupported configuration. They say that Access ODBC driver 3.50 or 3.51 work correctly.
Microsoft has issued a hot-fix for the
Windows NT Server, Enterprise Edition 4.0 and Windows NT
Server 4.0. It fixes a bug, which apparently caused
Microsoft Exchange and Outlook clients to hang when they
were used with an Exchange Server that had clients
connecting over slower connections. Fixes for both Intel
and Alpha computers are available from ftp://ftp.microsoft.com/bussys/winnt/winnt-public/fixes/usa/NT40/
If you use divisions in Lotus Word Pro
9.5 documents, you run the risk of file corruption. In
particular, if you create or insert divisions or quick
divisions at the insertion point, or create or insert
them when they have different page orientations or
headers/footers, you may see this error message:
"WORDPRO caused an invalid page fault in module
WORDPRO.EXE". As a fix, get the Word Pro 9.5 patch
Cisco says there is a database access protocol in CiscoSecure Access Control Server for UNIX 1.0 through 2.3.2, which may be exploited to allow an outsider to modify the access policies. This was fixed in 2.3.3 and an update is available both for users with a service contract and those without. However, this fix is nothing more than a configuration change, which can be accomplished without the update. You will have to edit your CSCconfig.ini file. For complete details on how to change the configuration, see http://www.cisco.com/warp/public/770/csecure-dbaccess.shtml
According to Dell, there may be a conflict between Microsoft Outlook 98, which they include on their Dimension desktop computers (and other Dell computers) and the 3Com ISDN 128K Accelerator, which is an optional upgrade on their computers. The problem surfaces with the 5.4.10 ISDN Accelerator software and hangs Outlook 98 when you try to add a contact's telephone number. The workaround: You have to use the Windows 98 supplied driver, rather than the 3Com, which Dell says will negate the Multilink PPP function of the ISDN modem, limiting you to only a single ISDN channel. To change drivers: 1) Click Start, Settings, Control Panel, and go to Add/Remove Programs; 2) Go to Install/Uninstall, and select 3Com ISDN Accelerator; 3) Click Add/Remove; 4) You will then have to add the modem driver from the Windows 98 CD.
Microsoft has found out about another security hole in Internet Explorer 5.0. An unscrupulous webmaster could construct a page that takes advantage of IE5's ImportExportFavorites function to run some malicious code on a visitor's computer. Until Microsoft develops a fix for this hole, the only fix is to disable Active Scripting for your browser. Here's how: 1) From IE5, click Tools, Options, and go to the Security tab; 2) Select the Internet zone, and click the Custom button; 3) Scroll down the list of features until you come to Active Scripting and Select Disable. For more information, go to http://www.microsoft.com/security/bulletins/MS99-037faq.asp. Microsoft credits Georgi Guninski for finding this bug.
Microsoft has discovered a capacity
problem with the NTFS file system on Windows NT 4.0 and
Windows 2000. If you have more than four million files on
an NTFS volume, you may end up with a corrupted Master
File Table (MFT), which may cause some of these problems:
deleted files still showing up; non-deleted files
missing, and; error messages reporting corruption and
telling you to run CHKDSK. It seems once the MFT grows
over 4 GB in size, it gets corrupted. If you have over
four million files on the volume, there is a good chance
the MFT will be greater than 4 GB. If you think you will
be running into these capacity restraints, Microsoft has
a hot-fix available at
If you are running Microsoft Outlook 98 on a Windows NT 4.0 Server or Workstation computer, and you try to print something, this error message may pop up: "STOP: 0x00000001E KMODE_EXCEPT_NOT_HANDLE: win32k.sys. (0xC0000005, 0xA00037C4, 0x00000000, 0x00000004)." The last four numbers may be different, says Microsoft. This bug has been fixed in Windows NT 4.0 Service Pack 5.
In the Mac OS X Server, the NetworkManager will let you change the names and IDs of all user accounts and all groups. However, Apple says you should not change names or IDs for any account or group if their ID is less than 100. They don't say what the dire consequences will be, they just say don't do it.
If you have deleted the Real Networks RealPlayer G2, you may find Netscape Communicator 4.x for Windows 95/98 crashes when it gets to the screen that says it is loading plugins. This is due to a stray .DLL left by RealPlayer. Either delete C:\PROGRAM FILES\NETSCAPE\COMMUNICATOR\PLUGINS\NPPL3260.DLL or change its file extension to .OLD. If you had a beta or preview version of RealPlayer, look for this stray and delete or rename -- C:\PROGRAM FILES\NETSCAPE\COMMUNICATOR\PLUGINS\RPCL3260.ZIP
Netscape Communicator 4.61 for both Windows and the Mac OS computer has a bug left over from earlier versions. If you enter a bad server name in Calendar, Netscape says that Calendar may "appear to 'hang'." Appearance must be reality, because the only fix is to restart Communicator.
© BugNet material copyright 1994-1999 by BugNet.
This historic replica of BugNet from the period 1994-1999
BF Communications Inc.
Website by Running Dog