Why is my netmeeting program giving a fatal exception error?

Question

Why can I not get my netmeeting program started again. I have the same problem with my Logitech video phone, and Cu-See program. When I click on the above programs I get a blue screen which says the following "A fatal exception 06 has occurred at 0028:C149B02D in VXD CxLPT(01) + 00000BED. The current application will be terminated.

* Press any key to terminated the current application.

* Press CTRL+ALT+DEL again to restart your computer. You will lose any unsaved information in the applications.

Press any key to continue.

I talked to a few computer people but they can not help me.

Could you please help me get back my microsoft netmeeting program back so that I can talk and see my grand children in Chicago. I was able to do this before this problem happened

thank you Seymour Gray

Answer

This question was answered on August 22, 1999. Much of the information contained herein may have changed since posting.

The information regarding the fatal exception errors was found on the Microsoft support web site However they had a very limited information regarding the problems of netmeeting, the error could be caused due to any one of these problems

Netmeeting errors:

Startup Troubleshooter

Is another program interfering with NetMeeting?

NetMeeting is based on the ActiveX® platform and conforms to the International Telecommunications Union (ITU) T.120 conferencing specification It is compatible with any other conferencing program based on this specification, but it cannot run while another conference or telecommunications program is running on the same computer.

Close any other open conference and telecommunications programs, and then try to start and run NetMeeting If you still have a problem, close any other programs you are not using, and try again.

Can you start and run NetMeeting after you close all unnecessary programs?

Are you using any Hewlett-Packard "Fonts for the Family" fonts?

If your computer stops responding when you start NetMeeting, you may have an incompatible or damaged font.

This behavior may occur when the Hewlett-Packard "Fonts for the Family" set of TrueType fonts is installed Several of these fonts are incompatible with Windows 95 and Windows 98.

Remove any "Fonts for the Family" fonts from your \\Windows\Fonts folder Drag these fonts into another folder instead of deleting them, at least until you verify that they are causing problems with NetMeeting.

Fonts known to be incompatible with Windows 95 and Windows 98

Artistik

Ashely Inline

Boxed In

Broadway

Creepy

Challenge Extrabold

Eclipse

Gallia

Stencil Sans

Harlow

Holidays

Kidprint

Old English

Party

ITC Pioneer

Snowdrift

Thunderbird

Torino Outline

Traffic

Yearbook Outline

To check for other damaged or incompatible fonts

Click Start, point to Settings, and then click Control Panel

Double-click Fonts

Double-click each font in the Fonts folder in turn.

If your computer stops responding when you double-click a font, that font may be damaged or incompatible with Windows Move all such fonts into another folder

Note

If you need a font that appears to be damaged, reinstall it from the appropriate source

After you remove any damaged or incompatible fonts from the Fonts folder, try to start and run NetMeeting.

Can you start and run NetMeeting?

These were some of the reasons listed on the microsoft web site regarding, netmeeting problems If neither works out then it could be a problem in registry in which case you should get it corrected through a professional person Another option could be that your drivers for the logitech video might not be the latest one, you could get more information about it from the manufacturer or the store from where you purchased the video phone.

Fatal exception error

The information in this article applies to:

Microsoft Windows 98

Microsoft Windows 95

Microsoft Windows 98 Second Edition

SUMMARY

When you attempt to start Windows or an application inside of Windows, you may encounter errors similar to the following:

A fatal exception <XY> has occurred at xxxx:xxxxxxxx

Fatal exception errors are codes returned by a program in the following cases:

Access to an illegal instruction has been encountered

Invalid data or code has been accessed

The privilege level of an operation is invalid

When any of these occur, the processor returns an exception to the operating system, which in turn is handled as a Fatal Exception Error In many cases the exception is non-recoverable and the system must either be restarted or shutdown, depending upon the severity of the error

In the following example of a Fatal Exception error

A fatal exception <XY> has occurred at xxxx:xxxxxxxx

the <XY> represents the actual processor exception from 00 to 0F The xxxx:xxxxxxxx represents the enhanced instruction pointer to the code segment and the 32-bit address is the actual address where the exception occurred

Windows does not cause these errors, but has the exception handling routine for that particular processor exception, which displays the above message

The following article details the processor exceptions and their meaning

For more information about troubleshooting strategies for Fatal Exception Errors, see the Knowledge Base articles listed at the end of this document

Fatal exception error 06 means:

06: Invalid Opcode fault

This error is returned if any one of the following conditions are true:

The processor tries to decode a bit pattern that does not correspond to any legal computer instruction

The processor attempts to execute an instruction that contains invalid operands

The processor attempts to execute a protected-mode instruction while running in virtual 8086 mode

The processor tries to execute a LOCK prefix with an instruction that cannot be locked

We hope that the information provided should be able to help you Good Luck!!

Need Help with this Issue?

We help people with technology! It's what we do.
Schedule an Appointment with a location for help!

Author

Posted by Ken of Data Doctors on August 22, 1999