|
Basic TroubleShooting Guide |
Large problems sometimes stem from ridiculously small causes. For example, cables, cards and chips can work themselves loose over time or develop bad connections from oxidation on their contacts. CPU cooling fans can die or malfunction, and dust can block air intakes or exhausts, leading to heat problems and erratic performance. To avoid all this, make sure all cables- inside the case and out-are properly inserted. Ensure that all socketed chips are firmly seated, that your fans are working and that your system case has unobstructed airflow.
1. To determine if it's a real mode driver or other conflict, rename the CONFIG.SYS and AUTOEXEC.BAT files so they do not load at boot. Also remark out any load= and run= lines in the WIN.INI file to skip loading these devices/applications. Remove all items in the StartUp Group (or just rename the \Windows\Start Menu\Programs\StartUp Directory). Reboot the computer and test to determine if the results change.
2. To determine if it's another running application, hit CTRL-ALT-DEL to bring up the active task list. End all tasks except Explorer and the program generating the error. This will help narrow down if another application is conflicting with the program.
3. The Registry file is how Win95 installs it's 32bit device drivers and where installed software does the same. When "Starting Windows..." is displayed on the screen, hit the F8 function key and select step-by-step confirmation. Answer No to Load Registry and answer yes to all other prompts. Run tests to determine if the results change.
4. The video mode and acceleration can also effect running applications. Open the Control Panel then the System folder. Select Performance/Graphics and set the acceleration to none. Run tests to determine if the results change.
5. To determine if it may be a Win95 setup issue, Let's use the Win95 Troubleshooting options will help us narrow it down. Open the Control Panel then the System folder. Select Performance/File System/Troubleshooting. Systematically disable each item to determine if any of these feature are at fault. (I would disable all features/reboot normally and see if things work properly, if yes, try each one individually to determine which feature is at fault.)
These are Basic Win95 trouble shooting guide, the steps are merely a guide for common computer problems and how you can detect the problem and fix it, some might not apply to your situation.
1. Run Scandisk(standard), run defrag(Check Full Optimization).
2. Never say: I have Antivirus and I don't have a virus It will give you one thing out to worry about being the problem. Run antivirus from Real DOS Mode not from windows. Exit from windows to MSDOS or start computer in DOS. Check every file on your computer, about a 10 minute operation. If for example you use Mcafee: (you can download a free evaluation from http://www.mcafee.com) At your dos prompt you would change directories CD MCAFEE\VIRUSCAN Then type C:\Mcafee\Viruscan>SCAN C: /ALL Windows antivirus merely is good to check files for viruses before copying or installing to your machine.
3. Go to Control Panel\System icon\Device manager tab, see if any marked red or yellow, remove the marked ones and restart computer, let Win95 re-detect the hardware.
4. Try remember when those errors started, if you think its something you did or installed.
5. Be sure you have over 100mb free hardisk space, if free space is small defrag daily, normally I leave about 350mb free hardisk space, recommend 250mb and up, the more hard disk space the better it runs.
6. Check your C:\Windows\Temp be sure its empty, so is the recycle Ben specially before you do defrag.
7. Be sure you haven't selected mouse maximum travel speed, in Control panel\Mouse.
8. Uninstall your video driver and restart computer and reinstall it, try lower resolution or different driver if applicable.
9. Don't use any 16bit(win3x) hardware software such as mouse, soundcard, etc, I don’t even run any 16 bit software all together in Win95, using 16bit software degrades Win95 considerably.
10. For testing purposes, rename your autoexec.bat and config.sys.
11. Remove all from the startup folder c:\windows\start menu\programs\startup,
also remove all after Load= and Run= from the Win.ini. Start computer &
click ctrl+alt+del and see what’s running other than the Explorer, end
task all except the explorer and see if the problem still there. Also in
the registry, remove all except Systray if present.
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
12. Go To Control Panel\System Icon\Performance tab, be sure it says "Your System is configured for optimal performance" also says "File System and Virtual memory are 32bit", if you don't that means you missed item2 and item10 in this text.
13. If the problem still exists, Reinstall win95 from the command prompt using (setup /p f ) command. That will clean your system files and replace missing and damaged files, without over-writing your updated dll's vxd's ext. f - This switch enables Clean Registry mode. It forces Detection to clean the root branch of the registry before starting. This switch is ignored when Setup is run in the Windows 95 graphical user interface (GUI). The default is disabled. Example: setup /p f As Always: Backup Your Registry First! NOTE: The Setup /p f command does remove some commands that are pointing to the wrong locations of programs and Win95 files, also does remove commands that are unknown to Win95 from the System.ini, Win.ini and the registry, but no promises can be given due to the nature of Win95's individuality. So ALWAYS backup your registry and system files first. Choose Custum Setup When prompted
14. Windows 95 Service pack could create errors, avoid installing it, but you can install parts of it, such as OLEUPD.EXE, Kernel32upd.exe, Exchange update. Also Power toys maybe convenient but its not healthy for Win95 to have it.
15. Remove screen savers, Wallpaper, Sound themes entering and exiting Win95.
16. Open start\programs\MS_DOS Prompt and type mem /c/p, if you have over 575 kb of Conventional memory then you are OK, best to be over 600kb.
17. Go to Control Panel\ System Icon, in the first tab be sure your RAM is recognized.
Courtesy of Ted Fattaleh 2000ted@gte.net http://www.mslm.com
Microsoft Windows 95 2, 2.1
Microsoft Windows 98
This describes Peripheral Component Interconnect (PCI) bus interrupt request (IRQ) steering.
Windows 95 OEM Service Release 2 (OSR2) and Windows 98 provide support for PCI bus IRQ steering. By using PCI bus IRQ steering, Windows can dynamically assign or "steer" PCI bus IRQs to PCI devices. Note that Microsoft Windows 95 (retail release) and Microsoft Windows 95 OEM Service Release 1 (OSR1) do not provide support for PCI bus IRQ steering.
ISA and PCI IRQs
Multiple Industry Standard Architecture (ISA) devices cannot share an ISA IRQ, however, multiple PCI devices can share a PCI IRQ. On computers that use a PCI bus, the 16 standard IRQs can be programmed to either PCI or ISA mode. An IRQ cannot be programmed for both modes at once.
How IRQs Are Assigned to PCI Devices
In Windows 95 (retail release) and OSR1, the Basic Input/Output System (BIOS) assigns IRQs to PCI devices. With OSR2 and Windows 98, if PCI bus IRQ steering is disabled in Windows the BIOS assigns IRQs to PCI devices, but if PCI bus IRQ steering is enabled, Windows assigns IRQs to PCI devices. When IRQ steering is enabled the BIOS still assigns IRQs to PCI devices, and even though Windows has the ability to change these settings, it generally does not.
CardBus Cards and OSR2
PCI R3 Personal Computer Memory Card International Association (PCMCIA) cards (CardBus cards), look very similar to the more common ISA R2 PCMCIA cards. CardBus cards use 32-bit addressing and require a PCI-type shareable IRQ. R2 PCMCIA cards use 16-bit addressing with an ISA-type non- shareable IRQ. PCI bus IRQ steering gives the operating system the flexibility to reprogram PCI IRQs when it rebalances Plug and Play resources. Without PCI bus IRQ steering, Windows can only rebalance Plug and Play ISA IRQs to resolve resource conflicts.
How OSR2 and Windows 98 Use PCI Bus IRQ Steering
PCI bus IRQ steering gives OSR2 and Windows 98 the flexibility to reprogram PCI interrupts when rebalancing Plug and Play PCI and ISA resources around non-Plug and Play ISA devices. Windows 95 (retail release) and OSR1 cannot rebalance PCI and ISA IRQs for Plug and Play devices around non-Plug and Play ISA devices to solve resource conflicts.
For example, if your computer's BIOS is unaware of non-Plug and Play ISA cards, the operating system does not have PCI bus IRQ steering, and the BIOS has set a PCI device to IRQ 10, you may have a resource conflict when you add a non-Plug and Play ISA device that is configured for IRQ 10.
However, with PCI bus IRQ steering the operating system can resolve this IRQ resource conflict. To do so, the operating system:
Disables the PCI device.
Reprograms a free IRQ to a PCI IRQ, for example IRQ 11.
Assigns an IRQ holder to IRQ 11.
Moves the PCI device to IRQ 11.
Reprograms IRQ 10 to be an ISA IRQ.
Removes the IRQ holder for IRQ 10.
IRQ Holder
An IRQ Holder for PCI Steering may be displayed when you view the System Devices branch of Device Manager. An IRQ Holder for PCI Steering indicates that an IRQ has been programmed to PCI mode and is unavailable for ISA devices, even if no PCI devices are currently using the IRQ. To view IRQs that are programmed for PCI-mode, follow these steps:
1. Click Start, point to Settings, click Control Panel, and then double-click
System.
2. Click the Device Manager tab.
3. Double-click the System Devices branch.
4. Double-click the IRQ Holder for PCI Steering you want to view, and
then click the Resources tab.
How to Determine if Your Computer Is Using IRQ Steering
To determine if your computer is using IRQ Steering, follow these steps:
1. Click Start, point to Settings, click Control Panel, and then double-click
System.
2. Click the Device Manager tab.
3. Double-click the System Devices branch.
4. Double-click PCI Bus, and then click the IRQ Steering tab. You should
see one of the following settings:
- IRQ Steering Enabled
- IRQ Steering Disabled
NOTE: PCI bus IRQ steering is disabled by default in OSR2. If you are using OSR2, and IRQ steering is disabled, verify that the Use IRQ Steering check box is selected on the IRQ Steering tab.
IRQ Steering may be displayed as disabled in Device Manager for any of the following reasons:
The IRQ routing table that must be provided by the BIOS to the operating
system may be missing or contain errors. The IRQ routing table provides
information on how the motherboard is configured for PCI IRQ's. The Use
IRQ Steering check box is not selected. The "Get IRQ table from Protected
Mode PCIBIOS 2.1 call" check box is not selected. Your computers BIOS may
not support PCI bus IRQ steering. For more information, contact the manufacturer
of your BIOS.
This is commonly caused by an incorrect or corrupted version of ole32.dll
and/or the related files olethk32.dll and compobj.dll.
Typically this results from installing an application that improperly
overwrites one of these files. Also, reinstalling Windows 95 without
first uninstalling IE4 can sometimes cause problems with these dlls:
http://support.microsoft.com/support/kb/articles/q174/5/49.asp
There are at least four reasonable methods you can use to get back the proper dlls. Here are your alternatives:
METHOD 1: Appy the DCOM update for Windows 95. This includes
the latest OLE files, as well as many other updates:
http://www.microsoft.com/com/dcom/dcom95/download.asp
METHOD 2: Install the OLE update for Windows 95. This is an older update than the DCOM update so the file versions may not be quite as current, but it's a simpler fix since it only updates three files instead of the 30 or so files in the DCOM update. You could try this method first and then method 1 if it doesn't work.
http://www.microsoft.com/windows95/downloads/contents/wurecommended/s
wuservicepacks/w95ole32update/default.asp?site=95
METHOD 3: You could re-extract the original ole32l.dll and related files from your Windows 95 CD. This will result in older file versions than the other methods, but it may work if the other methods are unsuccessful. Most likely you will need these three files:
ole32.dll from win95_09.cab
olethk32.dll from win95_10.cab
compobj.dll from win95_09.cab
As a last resort you could replace ALL the OLE files with the CD files using the following bat file:
FOR %%A IN (MINI PRECOPY WIN95_02) DO EXTRACT /Y /A /E /L
C:\WINDOWS\SYSTEM D:\WIN95\%%A.CAB OLE*.DLL
METHOD 4: Copy the three files mentioned above from another computer with a current working installation of Windows 95.
Courtesy of Chris Shaw
1.Click the Start button and click Help.
2.On the Contents tab, select Troubleshooting.
3.Select Windows 98 Troubleshooters.
4.Click the topic you need.
Take a minute to set up your screen by closing or minimizing all open applications, resizing the Help window, and placing it on the right side of the screen. This keeps the Troubleshooter instructions handy and gives you a work area on the left side of the screen. To gain additional workspace, you can get rid of the Contents portion of the window by clicking the Hide button on the Help toolbar.
Finding the Troubleshooter You Need
Hardware Conflicts
If a piece of hardware fails to work correctly and Device Manager indicates
a conflict.
Hardware conflicts generally are fixed by changing system settings in Control Panel.
Sound Problems
If sounds are missing or distorted, or if error messages relating
to sound drivers appear.
Most sound problems are the result of a hardware conflict or missing or incorrect versions of drivers, and can be corrected by changing system settings in Control Panel.
Modem Problems
If the computer fails to find the modem or if the modem has trouble
dialing or connecting.
Once a modem is installed and configured correctly, problems can arise due to idiosyncrasies in local phone systems. Work around these by changing the Telephony settings in Control Panel.
Startup or Shutdown Problems
If the computer stops responding during Startup or Shutdown, or if
it gives an Invalid VxD error message.
Many Startup and Shutdown problems can be fixed by making small changes to the settings in the System Configuration Utility (Mscnfig).
Display Problems
If images on the monitor appear distorted, garbled, or out of place;
for problems relating to multimonitor use; or if animations fail.
Most display problems are easily fixed by changing settings in Control Panel.
Dial-Up Networking Problems
If the computer fails to negotiate network protocols or will not save
a Dial-Up Networking password.
These problems are covered in the Modem Troubleshooter.
Printing Problems
If documents fail to print or if the printout is incomplete, distorted,
or garbled.
Check for physical problems (loose connections, jams, and the like) before changing settings in Control Panel or installing drivers.
Memory Problems
If an "Out of Memory" or "Parity" error message appears, or if System
Resources reports less memory than it should.
Often just closing all applications and restarting the computer is all it takes to solve "Out of Memory" problems.
Networking Problems
For problems logging on to the network, locating other computers on
the network, connecting with them, or sharing resources.
Most networking problems are caused by hardware or software incompatibility, and can be fixed by adjusting settings in Control Panel.
DriveSpace Problems
For problems during Startup related to the DriveSpace disk compression
utility, or when the "Compressed Drive Access" error message appears.
The presence of certain files can interfere with DriveSpace compression. Simply removing these files is all it takes to enable DriveSpace to proceed smoothly.
Direct Cable Connection
Problems
To set up a high-speed parallel cable to use with Direct Cable Connection.
The cable for Direct Cable Connection must be acquired from Parallel Technologies (or another vendor that sells compatible cables). Contact information is given in the Networking Troubleshooter.
PC Card Problems
If the PC Card does not work.
A PC Card will not function without a matching driver. If a PC Card fails with the driver present, it is most likely a hardware problem.
Microsoft Network Problems
If the computer has trouble connecting with The Microsoft Network.
If the computer has successfully connected in the past, wait and try again before changing system settings. The problem might be due to temporary network unavailability and require no further action.
DirectX Problems
If DirectX-based programs fail to install or play correctly.
For DirectX-based programs to play correctly, the video or sound card drivers and configurations may need to be changed.
MS-DOS-related Problems
For problems installing or running MS-DOS-based programs, or to run
an MS-DOS-based program in a window.
Troubleshooter must be shut down before solving some MS-DOS-related problems. Print or write down the Troubleshooter instructions before attempting the corrections.
Other Places to look find help:
Windows 98 Home Page
http://www.microsoft.com/windows98/default.asp
Welcome to Microsoft Product Support Services
http://www.microsoft.com/support/
Although it may take some time to copy, it will definitely speed up the setup process dramatically. Because the setup actually copying while extracting .CAB files, copying the entire directory into your hard drive will improve the setup process.
Second, you won't have to bother with inserting the CD when you need to Add/Remove Windows components. Of course you will benefit from not needing to bother with Add New Hardware as well. The drivers or system files are easily accessible from the hard drive. That will save plenty of time from flipping from the Windows 98 CD with your new hardware driver CD.
But on top of all, it will be very useful to solve fatal errors. When you encounter an error and can't log normally into Windows, you need to use the Safe Mode option. But unfortunately, the safe mode won't have your CD ROM drive accessible. Now this really sucks when you really need to re-install Windows. Copying you files into your hard drive will solve this problem.
So, if you really have enough space to spare, don't hesitate to copy
Windows 98 into your hard drive.
Your DISKCOPY.DLL may be corrupt or missing.
Put your Win98 CD in the drive and click Start, Run and enter SFC. When System File checker starts, tell it to extract 1 file, and give it DISKCOPY.DLL for the file name. If asked where to get the file, tell it X:\Win98 where X is your CD drive, and tell it to put the file in C:\Windows\System (assuming Windows is installed on the C: drive)
OR
--------------------
REGEDIT4
[HKEY_LOCAL_MACHINE\Software\CLASSES\Drive\shellex\ContextMenuHandlers\
{59099400-57FF-11CE-BD94-0020AF85B590}]
@=""
[HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{59099400-57FF-11CE-BD94
-0020AF85 B590}]
@="Disk Copy Extension"
[HKEY_LOCAL_MACHINE\Software\CLASSES\CLSID\{59099400-57FF-11CE-BD94
-0020AF85B590}\InProcServer32]
@="C:\\WINDOWS\\SYSTEM\\diskcopy.dll"
"ThreadingModel"="Apartment"
-------------------------------NOTE:
There are no spaces in the above keys.
1. Highlight, right-click and select: Copy
2. Open Notepad, click Edit, select: Paste
3. Click File - Save As
4. Enter: "repair-disk-copy.reg" (no quotes)
5. Note: change the File Types to: All Files
6. Right-click on repair-disk-copy.reg
7. Select: Merge (to enter the info into the Registry)
8. Reboot