|
Top Support Issues for Win95 Win98 |
Personal Online Support Highlights
MS-DOS
Compatibility Mode Problems with PCI-IDE Controllers
Reported
Memory Does Not Match Amount of Installed Memory
Fix all Internet-related
Bugs and Nuke Security
NukeNabber Freeware. Must See!!
Application Program
Interface @ 95 File Limitations
NOIDE
Security Restrictions
without using Policy Editor
All About Networking with Windows 98
Why Your
System Automatically Dials ISP on Bootup; and How to Fix it
Windows Update
http://www.microsoft.com/windows/downloads/default.asp
=========================
Microsoft's Driver Resource
http://www.windrivers.com/script/drivers.asp?company=Microsoft
======================
Utilities and Freeware
Programs
http://www.helponthe.net/nathan/utility/index.html
=====================
Windows 98 Troubleshooter
http://support.microsoft.com/support/tshoot/tshooterlist.asp
=====================
Woody's
Office Watch; All you need to know about Office!!
http://www.wopr.com/wow/wowarch.shtml
MS-DOS Compatibility Mode Problems with PCI-IDE Controllers IMPORTANT: This article contains information about editing the registry. Before you edit the registry, you should first make a backup copy of the registry files (System.dat and User.dat). Both are hidden files in the Windows folder.
Some IDE hard drive controllers don't seem to allow the full 32-bit optimal performance, thus forcing compatibility mode. I found a trick that will fix this problem: RUN REGEDIT.EXE and find NOIDE when you find it, right click on it and change it's value from 01 to 00. When this is done close REGEDIT and restart your Windows. This has came in very handy many times. Much faster performance than before. Not only that, brings back your animated cursors and lost drives. It helps the system a lot. HKEY_LOCAL_MACHINE\SYSTEM\CURRENT CONTROLSET\SERVICE\VXD\IOS There make your "String value key" NIODE=00
SYMPTOMS
If your computer contains a PCI-IDE hard disk controller that employs serialization between the two IDE channels, you may experience the following problems:
* 32-bit file system access and 32-bit virtual memory are not available. * Device Manager displays an exclamation point in a yellow circle for the primary and secondary IDE channels.
Removing and reinstalling the hard disk controller does not resolve the problem.
CAUSE
The protected-mode driver for the hard disk controller was not properly initialized when you started Windows 95 previously. When this occurs, a NOIDE entry is placed in the registry, preventing Windows 95 from making future attempts to initialize the protected-mode driver.
RESOLUTION
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall Windows 95. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
NOTE: For information about how to edit the registry, view the Changing Keys And Values online Help topic in Registry Editor (Regedit.exe). Note that you should make a backup copy of the registry files (System.dat and User.dat) before you edit the registry.
To cause Windows 95 to attempt to reinitialize the protected-mode IDE driver, remove the NOIDE entry from the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENT CONTROLSET\SERVICES\VXD\IOS
After you update the registry, restart Windows 95. Windows 95 will then attempt to initialize the protected-mode driver for the controller. If no problems are encountered, the file system and virtual memory will operate in 32-bit mode, and Device Manager will not display an exclamation point in a yellow circle for the IDE channels.
If the protected-mode driver is not initialized properly, an error message will be displayed and the NOIDE registry entry will be re-created. Windows 95 will use the MS-DOS compatibility mode file system the next time you start the computer.
MORE INFORMATION
This problem can occur with an IDE controller that requires serialization between the primary and secondary IDE channels. The protected-mode drivers for these IDE controllers can fail to be initialized if one of the following situations occurs:
* One IDE channel has a supported hard disk, and the second channel has a CD-ROM or other type of drive that requires real-mode drivers to be loaded. Because of the serialization between the two IDE channels, it is impossible to access the hard disk in protected mode and use the other device in real mode. This causes the protected-mode driver to fail initialization, and the NOIDE switch is placed in the registry to prevent future errors. Both disk devices then operate in real mode. * The driver for the IDE controller is manually removed from Device Manager and then reinstalled, or the protected-mode driver is disabled and then re-enabled. Some PCI controller drivers are not designed for dynamic enabling and disabling, and can cause the protected-mode driver to fail initialization.
The Windows 95 device drivers for the following controllers are known to exhibit this behavior:
* CMD PCI-0640 PCI-IDE controller * Standard Dual PCI-IDE controller * Opti Dual PCI-IDE controller
Other PCI-IDE controllers that use serialization between the IDE channels may also exhibit this behavior.
This behavior can occur for any of the following reasons:
1. Himem.sys is not using all the memory on an EISA computer.
2. A driver or program loading from the Config.sys or
Autoexec.bat file is claiming a portion of RAM.
3. A virtual device driver loading from the System.ini file is
claiming a portion of RAM.
4. A protected-mode driver is causing the memory mismatch.
5. The registry is damaged.
6. A CMOS setting is disabling some of the RAM.
7. You have the "maxphyspage=" setting in your System.ini file
set to restrict Windows 95 from using some of the installed memory.
8. Ramdrive.sys is being loaded in the Config.sys file.
METHOD 2
When you view the Performance tab in System properties, the amount of memory reported may differ from the actual amount of memory installed in the computer.
This behavior can occur for any of the following reasons:
- Himem.sys is not using all the memory on an EISA computer.
- A driver or program loading from the Config.sys or Autoexec.bat file is claiming a portion of random access memory (RAM).
- A virtual device driver loading from the System.ini file is claiming a portion of RAM.
- A protected-mode driver is causing the memory mismatch.
- The registry is damaged.
- A CMOS setting is disabling some of the RAM.
- You have the "maxphyspage=" setting in your System.ini file set to restrict Windows from using some of the installed memory.
- Ramdrive.sys is being loaded in the Config.sys file.
- You are using a video adapter that is integrated into the motherboard.
Patches for Microsoft Windows 95
Use the following steps to upgrade to Winsock 2.2 and patch the Internet
bugs in
Windows 95. Be sure to perform these steps in the order as they appear.
1.Install the MS DUN 1.2 Upgrade (MSDUN12.EXE) and reboot.
2.Install the Winsock 2.2 Upgrade (WS2SETUP.EXE) and reboot.
3.Install the Winsock 2.2 Patch (VIPUP20.EXE) and reboot. This step
fixes the IP
nukes such as SSPING and Teardrop.
4.Install the Land patch (VTCPUP20.EXE) and reboot.
5.Rename VNBT.386 to VNBT.BAK or use the VNBT.386 Fix (VNBT.EXE) and
reboot. This step fixes the WinNuke bug.
Patches for Microsoft Windows NT
1.Install Service Pack 3 (NT4SP3_I.EXE)
2.Install the Bonk, Boink and Teardrop2 patch (TEARFIXI.EXE). This
patch
supercedes the ICMP-fix, OOB-fix, Simptcp-fix and Land hotfixes.
Because many people ask about API and WIN95 FILE LIMITS, I have this
API definition I keep;
"Abbreviation of application program interface, a set of routines,
protocols, and tools for building software applications.
A good API makes it easier to develop a program by providing all the
building blocks.
A programmer puts the blocks together."
The file-open limitations are at the API input at the programming level,
but in the end-user
arena, the limitations are imposed only by such things as Ram, HDD
space, swapfile configuratin and the like.
Or in plain talk, the only Win95 file limitations are imposed by phsyical
memory.
Other than a non-95 program where a programmer specifies a "file-open
limitation"; There are no limits.
Full protection from being Nuked. Who ever thought it would come to
this??
http://www.dynamsol.com/puppet/software.html
There may times when you may not want users to shut down Windows. You
can prevent that by editing your Registry. Launch Regedit and drill down
to the key
"HKEY_CURRENT_USER\Software\Microsoft\ Windows\CurrentVersion\Policies\Explorer\NoClose."
Right-click on the NoClose subkey, select Modify and type a 1 (the
number one) in the Value data box. Exit Regedit, saving changes. Reboot.
Now click on the Start Menu and the Shut Down menu will be gone. To restore
the Shut Down menu, change the value back to 0.
For many other restrictions see:
Restrictions
without running Poledit
-You use a program that automatically checks for updated components or Web pages.
- A program that dials your ISP is located in the StartUp folder.
- Your computer is infected with a Trojan horse virus such as System32.exe that starts when you start your computer. Note that most anti-virus programs do not currently detect or remove Trojan horse viruses.
- Symantec WinFax or HotFax Message Center is installed on your computer.
- You are using a Lexmark printer. The Lexmark printer software may add Lexstart.exe to the Run key in the registry to handle print commands that you send to the printer. This can cause Dial-Up Networking to prompt you to dial your ISP.
- You are using Microsoft Personal Web Server 4.0, and the Microsoft Distributed Transaction Coordinator (MSDTC) service is being loaded from the StartUp folder.
- You have installed a Beta version of RealAudio 5 on your computer.
- This behavior can occur if Internet Explorer is configured to connect using a modem, and the following registry key is set to "Y":
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE EnableRemoteConnect
RESOLUTION
-----------------------------------------------------
WARNING: Using Registry Editor incorrectly can cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that problems resulting from the incorrect use of Registry Editor can be solved. Use Registry Editor at your own risk.
For information about how to edit the registry, view the "Changing Keys And Values" Help topic in Registry Editor (Regedit.exe) or the "Add and Delete Information in the Registry" and "Edit Registry Data" Help topics in Regedt32.exe. Note that you should back up the registry before you edit it.
To resolve this behavior, use one of the following methods:
Configure
Program That Dials ISP Not to Start Automatically
------------------------------------------------------
Configure the program that automatically checks for updated components
or Web pages so that it does not start when Windows 95/98 starts. To do
so, refer to the documentation included with the program.
Remove
Program That Dials ISP from the StartUp Folder
-----------------------------------------------------
Remove the program that automatically checks for updated components
or Web pages from the StartUp folder. To do so, follow these steps:
1. Right-click Start, and then click Open.
2. Double-click the Programs folder.
3. Double-click the Startup folder.
4. Drag the program that automatically checks for updated components
or Web pages from the Startup folder to another folder. This prevents the
program from starting when Windows 95/98 starts. To start the program once
you move it from the Startup folder, locate and click the program on the
Start menu.
Remove System32.exe
Trojan Horse Virus
--------------------------------------
1. Delete or rename the System32.exe file in the Windows\System folder.
2. Use Registry Editor to remove the SystemHandler value from the following registry key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
Modify Symantec
WinFax or HotFax Message Center
-----------------------------------------------
1. Close WinFax and the Controller, or close or HotFax Message Center.
2. Start Registry Editor, and then click Export Registry File on the Registry menu.
3. In the Save In box, click C:\.
4. In the File Name box, type "Regold" (without quotation marks), and then click OK.
5. Change the following registry key to "N":
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE\EnableRemoteConnect
6. Reconfigure your modem in WinFax or or HotFax Message Center.
You Are Using a Lexmark
Printer
-------------------------------
Using Registry Editor, remove the Lexstart.exe value from the following
registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
MSDTC
Service Is Being Loaded from the StartUp Folder
-----------------------------------------------------
Remove the MSDTC service from the StartUp folder. To do so, follow
these steps:
1. Click Start, point to Settings, and then click Taskbar & Start Menu.
2. On the Start Menu Programs tab, click Remove.
3. Double-click the StartUp folder.
4. Click the MSDTC service, and then click Remove.
5. Click Close, click OK, and then restart your computer.
If you do not want to remove the MSDTC service from the StartUp folder, configure Internet Explorer to connect to your ISP using a local area network (LAN). When you want to connect to the Internet, first connect to your ISP using Dial-Up Networking, and then start Internet Explorer. To configure Internet Explorer to use a LAN, follow these steps:
1. Right-click the Internet Explorer icon on the desktop, and then click Properties.
2. Click the Connection tab, click "Connect to the Internet using a local area network," and then click OK.
NOTE: If the MSDTC service is not being loaded from the StartUp folder, remove the Msdtc value from the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\RunServices
RealAudio 5 Beta Is Installed
-----------------------------
A Beta release of RealAudio 5 may cause the modem to connect to the
ISP. To resolve this issue, remove the Beta version of RealAudio, or upgrade
to the release version of the product.
Registry Entry Set to Dial
--------------------------
To resolve this issue, configure Internet Explorer to not connect using
a modem, or set the value of the following registry key to "N":
WARNING: Some programs may configure the registry to dial automatically, and altering this registry value may impact these program's functionality.
HKEY_LOCAL_MACHINE\Software\Microsoft\OLE EnableRemoteConnect