• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Help with Netmeeting... Error Message

S

SpyderX

Member
Well, just in case you don't know what Netmeeting is, it's a program that's included with Windows where you can basically talk and control or see other person's PC, etc (with their permission of course) Anyways I'm trying to fix my friend's PC over the internet but he can't open Netmeeting. So he wanted a fresh clean start so he does a fresh format of his PC and etc. He reinstalled the basic utlilities in his PC and now he still can't open Netmeeting. The error he gets is the following
---
conf.exe has generated errors and will be closed by windows. you will need to restart the program
---

Does anyone know how he can bypass this or fix this so he can use Netmeeting? Thanks
BTW he is using Windows 2000 Pro
 
Weird. Never seen this with clean installs of the OS. Could be something affecting GDI, but I don't think so in this case...

When NM fails to launch with errors, it usually has to do with loading of the T.120 protocol (app sharing). W2K has an advanced DDML layer, for which a specific build of NM was created (this is why you cannot install publicly downloadable builds from MS). One part of this code is that it allows NM to dynamically load/unload T.120 when NM is opened/exited. NM also hooks GDI in order for input to work correctly while sharing an app/desktop.

My first guess is that it's a hardware issue. It could be the video card, or the specific drivers being used. If it's a professional OpenGL card, that could also be a factor.

However, you don't mention what the "basic utilities" are that he installed. For example, there are known issues with NM when another app sharing program is installed, such as PCAnywhere (i.e. stuff breaks...a lot). If he has a different T.120 app already installed, it probably doesn't dynamically unload its own T.120 stack...in fact, it may load T.120 at boot, whether you use the program or not (otherwise known as "invasive coding"). And because you cannot have two instances of T.120 running at the same time, the second instance always fails to load. If NM is the "second instance", it will fail to load, with errors.

More specifics on hardware, software, DX version, drivers, etc would help to narrow this possibilities a bit more...
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top