Figure 4 shows the same program with the advanced options also displayed. The advanced options list is very large, and it is not fully displayed in the diagram.

• 30 average width metrics
• Always send NC_PAINT
• Delay comm handshake
• Disable 16 color brush cache and 55ms timer
• Disable EMF spooling
• Disable font associations
• Don't attach input thread when journaling SetActiveWindow SetForgroundWind
• Don't enum device fonts
• Don’t send calcsize on WM_MOVE
• Don’t Shutdown/Ignore certain faults/dequote commandline
• Enable 3.x UI features
• Enua HeIv and Times Roman fonts

Crash Protection: One of the new features of Windows' 95 is the separate message queue. This allows the system to keep running when a 32-bit Windows' application stops responding. This works fine for the 32-bit Windows applications, but the 16-bit Windows applications still use a shared message queue. When one of these applications stops responding, the entire system can grind to a halt. When a 16-bit Windows' application stops responding, you can bring up the Task Manager and close the halted application. In most cases, however, you have probably lost your work and will have to start over again, which makes a good case for using only 32-bit Windows' applications.

Dealing With System Hangs: If your system appears to have halted, but you have not received any blue screen error messages or pop-up box messages, you can do a quick check to see if your system is down. Simply press the Number Lock or the Caps Lock keys on your keyboard. If the indicator lights on your keyboard change, then your entire system is not down. If they do not change, then most likely your system is down.

If your indicator lights change, you can choose to wait and see if your system will begin to respond again. You should wait a minimum of two minutes before trying the next step. If, while you are waiting, you see or hear hard disk activity, that is a signal to wait longer. On the other hand, the lack of hard drive activity usually means an application has stopped responding and you should proceed to the next Step

The next step is to simultaneously press the CTRL ALT and DEL keys. If only one or a few applications have stopped responding but the rest of the system is up, you should see the Close Program dialog box (Task Manager). This dialog box will show you all the programs in memory (executing) and whether any have stopped responding. Click on any programs that have stopped responding and press the End Task button. In most cases, you will see an additional dialog box telling you that the application cannot respond to End Task, and you will be given three choices: To wait five seconds, immediately end the task, or cancel. Select End Task Immediately. If the system remains stable, repeat this procedure with all the applications that are listed as "not responding."

There are, however, a few occasions when critical applications are not responding and a reboot of the system is the only solution. When your system refuses to respond, you will have to use the reset button on your computer to reboot. The list below shows some of these critical applications that will require a reboot if they have halted:

• Kernel32 or Kernel or Kernel386
• User
• Msgsrv32
• Explorer
• Vmm32
• Winoldap